Date   

locked Re: Regarding JTAlert 2.16.5 randomly stopping display of Callsigns

HamApps Support (VK3AMA)
 

On 21/05/2020 8:53 am, Bobby Chandler wrote:
With the Beta version, when I do a configuration change FT8 to FT4 and FT4 to FT8, I lose docking, but after restart OK until I change configs again.

Bobby/N4AU

Bobby,

Confirmed. This is only happening with the new WSJT-X 2.2.0 -rc1, caused by the pre-release popup window.

JTAlert uses the window handle of the main WSJT window to provide the docking functionality. When WSJT-X changes configs, it causes a restart of WSJT-X causing the window handles for the wsjt.exe process to change. Normally JTAlert will update the window handle after detecting the config change allowing docking to continue to work. With the release candidate, it is presenting a modal pre-release advisory window which is breaking the JTAlert code.

I have a workaround coded for the next JTAlert release, it involves delaying the WSJT-X window handles lookup, executing 15 seconds after the WSJT-X config change was first detected.

de Laurie VK3AMA


locked Re: Saving configs

HamApps Support (VK3AMA)
 

On 21/05/2020 9:52 am, Jeff Campbell wrote:
Thanks Laurie.  I've located the files but I'm not sure how I should revert to one of the earlier configs.  Is it just a matter of selecting the desired one (based on the time and date) and renaming it config.sqlite or is that incorrect?

Jeff - G4IUA
Yes, just rename the backup file to config.sqlite after first stopping JTAlert

BTW, the future JTAlertV3 allows for restoring the config from a backup file while JTAlert is running, but that is not possible within the current code.

de Laurie VK3AMA


locked Re: Saving configs

Jeff - G4IUA
 

On Wed, May 20, 2020 at 10:00 PM, HamApps Support (VK3AMA) wrote:
%localappdata%\HamApps\<YOUR_CALLSIGN>\config\JTAlertX\
Thanks Laurie.  I've located the files but I'm not sure how I should revert to one of the earlier configs.  Is it just a matter of selecting the desired one (based on the time and date) and renaming it config.sqlite or is that incorrect?

Jeff - G4IUA


locked Re: Regarding JTAlert 2.16.5 randomly stopping display of Callsigns

Bobby Chandler
 

With the Beta version, when I do a configuration change FT8 to FT4 and FT4 to FT8, I lose docking, but after restart OK until I change configs again.

Bobby/N4AU
--
bobbye@...
n4au@...


locked Re: UDP Messages to GridTracker

Dave Garber
 

I have jtalert listening on 2237 from wsjtx, then I tell it to rebroadcast to 2239 to gridtracker, on a different ip address
so wsjtx must have 2237 ( with the check boxes marked )
in jtalert I have set 2239 under the rebroadcast option, under applications in the setup

if i decide to run on same pc, all I do is change the ip number

also have upd from gridtracker sending spots to a tablet on 2238 with the tablets ip number



Dave Garber
VE3WEJ / VE3IE


On Wed, May 20, 2020 at 4:49 PM Jim WA3ERQ <wa3erq@...> wrote:
For some reason it only works on 2237.  Don't know why.  I changed to 2239 since 2238 is also being used but when I have it on 2237 and just enter into the Applications settings, it sends "one" message only.  When I changed to another port in both applications, nothing happens even when I take the same steps as using 2237 (strange).  I believe that it has to do with JTAlert only sending one initial message and not rebroadcasting the packets.    GridTracker is able to receive but JTAlert only sends one packet when I enter into the settings menu.

Jim
WA3ERQ


locked Re: More "no sound" problems

Don Roden
 

I have no sound.  Does HDMI count as a sound device ? 
Don W4DNR 

-------- Original message --------
From: "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...>
Date: 5/20/20 5:01 PM (GMT-06:00)
To: Support@HamApps.groups.io
Subject: Re: [HamApps] More "no sound" problems

On 21/05/2020 1:53 am, lmeeny wrote:
Your suggestion's  a good one. An incorrect PC setting would explain my problem. I looked for a specific PC setting that  enables or disables speaker use by JTALERT but could not find one. Can you suggest where I should look?
Windows maintains per-application volume & mute settings independent of the values set in the application.

Check the Windows Volume Mixer to see what it has set for the JTAlertV2.Manager application.
Select the sound device as used for JTAlert. If you don't see the volume slider for JTAlert perform a test sound (in JTAlert) as this will trigger Widows to display the slider. Make sure it is not muted or the volume set to zero.

           

de Laurie VK3AMA


locked Re: More "no sound" problems

HamApps Support (VK3AMA)
 

On 21/05/2020 1:53 am, lmeeny wrote:
Your suggestion's  a good one. An incorrect PC setting would explain my problem. I looked for a specific PC setting that  enables or disables speaker use by JTALERT but could not find one. Can you suggest where I should look?
Windows maintains per-application volume & mute settings independent of the values set in the application.

Check the Windows Volume Mixer to see what it has set for the JTAlertV2.Manager application.
Select the sound device as used for JTAlert. If you don't see the volume slider for JTAlert perform a test sound (in JTAlert) as this will trigger Widows to display the slider. Make sure it is not muted or the volume set to zero.

           

de Laurie VK3AMA


locked Re: UDP Messages to GridTracker

HamApps Support (VK3AMA)
 

On 21/05/2020 6:48 am, Jim WA3ERQ wrote:
but JTAlert only sends one packet
That's incorrect. JTAlert doesn't restrict the number or type of UDP packets it resends.

ALL UDP packets JTAlert receives on the WSJT-X defined port (2237 is the default) are resent regardless. The UDP packet could contain erroneous data orare not from WSJT-X, JTAlert doesn't care it simply resends what is received (on port 2334, the default if you haven't changed).

de Laurie VK3AMA


locked Re: McAfee

Malcolm Pelham <malcolm.pelham@...>
 

Thanks I will give it a try and report back

Malcolm Pelham
WF5K

On May 20, 2020, at 3:31 PM, DamianM0BKV via groups.io <kammdp@...> wrote:

I had the problem. All you need to do is open McAfee, click on PC Security, Click on Real-Time Scanning. Excluded Files click on V.  Add file
Find where you unzipped 'JTAlert.EXE' (proberly Folder JTAlert/JTALERT/) copy and paste it to the Add file. Make sure his is the same JTAlert.EXE file you will be running. Now and ONLY now open JTAlert for the first time otherwise McAfee will remove it AGAIN.


locked Re: Regarding JTAlert 2.16.5 randomly stopping display of Callsigns

Marty Tressell
 

I noticed this a few days ago and wasn't sure it was an issue and find this message and then was on WSJT-X with JTAert and it would just stop populating the JTAlert Call Sign Box so stopped it and then restarted it...would like to try the fix. And Promise to report back!!!

Thank you!
--
Marty, K0BBK
mtressell@...


locked Re: Alert 2.16.5 not showing country

HamApps Support (VK3AMA)
 

On 19/05/2020 3:12 am, Mike Rhodes wrote:
Didn't JTAlert used to show the country in the pop-up window that you get when you hover over a callsign? Seems like that happens in a very inconsistent (if at all) manner

The display of Country names in the Callsign tooltip has not been removed.
It is broken in the 2.16.5 release. This defect as been previously acknowledged in Group messages. It is already corrected for the next release.

de Laurie VK3AMA
 


locked Re: Saving configs

HamApps Support (VK3AMA)
 

On 20/05/2020 4:06 am, Jeff Campbell wrote:

Is there a way to save configs?  I recently made some changes which had undesirable consequences, and it took some effort to remember what I'd incorrectly changed.  If it was easy to revert to an earlier known good configuration that would be much safer.  Is there a way of doing this?

 

Jeff - G4IUA

Config backups are automatically created by JTAlert. The most recent 7 days of backups are retained.
The backup files are located in the same directory as the active config file (config.sqlite), here -->

    %localappdata%\HamApps\<YOUR_CALLSIGN>\config\JTAlertX\

The backup files have the utc data/time of creation as part of the filename.

de Laurie VK3AMA


locked Re: UDP Messages to GridTracker

Jim WA3ERQ <wa3erq@...>
 

For some reason it only works on 2237.  Don't know why.  I changed to 2239 since 2238 is also being used but when I have it on 2237 and just enter into the Applications settings, it sends "one" message only.  When I changed to another port in both applications, nothing happens even when I take the same steps as using 2237 (strange).  I believe that it has to do with JTAlert only sending one initial message and not rebroadcasting the packets.    GridTracker is able to receive but JTAlert only sends one packet when I enter into the settings menu.

Jim
WA3ERQ


locked Re: McAfee

DamianM0BKV
 

I had the problem. All you need to do is open McAfee, click on PC Security, Click on Real-Time Scanning. Excluded Files click on V.  Add file
Find where you unzipped 'JTAlert.EXE' (proberly Folder JTAlert/JTALERT/) copy and paste it to the Add file. Make sure his is the same JTAlert.EXE file you will be running. Now and ONLY now open JTAlert for the first time otherwise McAfee will remove it AGAIN.


locked Re: Regarding JTAlert 2.16.5 randomly stopping display of Callsigns

xoxoxo48@...
 

Please add me to the list of users having this problem of decodes randomly stopping. Since the problem was reported and was identified as a problem I felt no need to speak out until now "re: level of feedback."  Running windows 7 SP1 - 64 bit here. No problems until this release. I chose to revert back to 2.6.14 until resolved. Please announce when update is again available with the fix. Thanks for your fine program Laurie

de John K2WJ


locked Re: Alert 2.16.5 not showing country

Andrew Buza
 

Thanks Chip;  That did the trick. working fine  73


locked Re: More "no sound" problems

Rob Kivell
 

ED, not sure if you are using WIN10 or not. If you are try this:

Take your pointer and hover over the microphone icon on your bottom tray. It will indicate the App or program that is currently using the microphone.

Next thing to do is click on the microphone and it will take you to the microphone settings page

Make sure ALLOW Apps to access your microphone is turned ON

Next scroll down the page to ALLOW desk top apps to access your microphone and turn on

Next scroll all the apps listed below and make sure wsjtx is listed. Finally, if all is set correctly and you have wsjtx activated it should indicate in red:
Currently in use

Hope this helps if not it might help someone else.

Good luck

Rob kk4eun



On May 20, 2020, at 10:53 AM, lmeeny <emachak@...> wrote:

Peter,

Your suggestion's  a good one. An incorrect PC setting would explain my problem. I looked for a specific PC setting that  enables or disables speaker use by JTALERT but could not find one. Can you suggest where I should look?

Thank you,

Ed W2GHD.




On Tue, May 19, 2020 at 09:59 AM, Peter van IJperen wrote:
Take care no checks are by properties playing and recording..... Listen to this device..... My was ticked and this override the soundcard.  73 de PC1Y. Peter


locked Re: More "no sound" problems

WB8ASI Herb
 

If you are getting sounds from Windows, you should get sound from JTAlert.   It should be using your normal default sound card.  Check on the Sound Card page in JTAlert.  Do you have the default sound card entered at the top of the page?   Do you have the volume turned up?  Remember to save.  73 Herb WB8ASI

On May 20, 2020 at 11:53 AM lmeeny <emachak@...> wrote:

Peter,

Your suggestion's  a good one. An incorrect PC setting would explain my problem. I looked for a specific PC setting that  enables or disables speaker use by JTALERT but could not find one. Can you suggest where I should look?

Thank you,

Ed W2GHD.




On Tue, May 19, 2020 at 09:59 AM, Peter van IJperen wrote:
Take care no checks are by properties playing and recording..... Listen to this device..... My was ticked and this override the soundcard.  73 de PC1Y. Peter

 


locked Priority Alert not persistent still a problem

jushamn@...
 

Priority Alert still returns to default order. I changed other options restarted JTAlert and the changed options remained changed as expected but priority alert returned to default order. After I shut down JTAlert and renamed config.sqlite and tried again. The Priority Alert still returned to default order after I changed it following a restarted. So a new config.sqlite file did not solve it for me. Suggestions?


locked Re: Regarding JTAlert 2.16.5 randomly stopping display of Callsigns

Hasan Schiers N0AN
 

I did do one configuration change from my FT8 Config to my MSK144 Config (I use separate configs for each mode), and it continued to work. Will do some more config changes to confirm that it holds.
73, N0AN
Hasan


On Wed, May 20, 2020 at 10:45 AM Jim - N4ST <newsgroup@...> wrote:

The Beta runs for hours without issue for me, until I do a WSJT-X configuration change.

Then I have to restart JTAlert and then it runs for hours again.

 

______________

73,

Jim – N4ST

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Hasan Schiers N0AN
Sent: Wednesday, May 20, 2020 11:13
To: Support <Support@hamapps.groups.io>
Subject: Re: [HamApps] Regarding JTAlert 2.16.5 randomly stopping display of Callsigns

 

I downloaded the Beta and have not seen the problem since then. It's been three days, using different configurations and different bands (in WSJT-X)

 

I think the Beta fixes it, at least it did for me.

 

73, N0AN

Hasan

 

 

On Wed, May 20, 2020 at 9:59 AM afa1yy <arthur@...> wrote:

I also experience this problem.  My cure has been to shut down JTAlert and restart it.  I'm sure Laurie will have this fixed with the next update,
--
Art  K0AY