Date   

locked Re: Single/double click within callsigns window not working

BOB K5HX
 

Mike,

Other than WSJT-X (interfaced to HRD),  I only sometimes launch Grid Tracker which is using UDP Multicast.

Bob  K5HX


locked Auto Close intermittent

Ed Fuller
 

This may just be a quirk of my system: Win7 home Premium, DXLab, WSJTX 2.4.0, JTAlert 2.50.1, Net 5.0.6.  Have Auto-start set to wsjtx. works fine, except when I close jtalert it closes  the wide graph, but sometimes the main wsjtx window remains open and decoding. 

 

First noticed this after upgrading to wsjtx 2.4.0, but rolling back to 2.3.0 makes no difference.  Using "taskkill /im wsjtx.exe" in command prompt shows similar results:

 

C:\Users\PSDR>taskkill /im wsjtx.exe

SUCCESS: Sent termination signal to the process "wsjtx.exe" with PID 5532.

 

After this is returned the process wsjtx.exe still shows in task manager processes even after a refresh and wsjtx still shows in the application pane.

 

taskkill with /t /f /im wsjtx.exe always works.

 

Not a big deal, just curious.

 

Ed Fuller WA5RHG


locked Re: #FT8 Clear decode screen #FT8

 

Yes Laurie the the call sign window was not checked. That did the job. Thanks
--
73 NU4N Dave


locked Re: #FT8 Clear decode screen #FT8

HamApps Support (VK3AMA)
 

On 28/05/2021 6:36 am, Dave Tucker Nu4N wrote:
I am new to the latest version.
Is there a shortcut to deleting the decode screen the same time u clear the decode screen in WSKT-X?

Thanks
--
73 NU4N Dave

For the Decodes window, no there is not.

The Decodes window is not new, so I suspect you're referring to another window, perhaps the Callsigns window. What does the titlebar show for the window in question?

de Laurie VK3AMA


locked #FT8 Clear decode screen #FT8

 

I am new to the latest version.
Is there a shortcut to deleting the decode screen the same time u clear the decode screen in WSKT-X?

Thanks
--
73 NU4N Dave


locked Re: JTAlert Grids not matching LOTW VUCC

Dave AA6YQ
 

Your attachment(s) do not show what DXKeeper has marked as "Confirmed" - only what LotW has received. I suggest you use the DXKeeper "RAT" -> Select the VUCC tab -> Set Band = 6M
-> Check "Confined" *ONLY* and see what DxKeeper says.

If what you originally logged does not match what the other station uploaded to LotW and you do not allow DXKeeper to update the grid to match LotW, DXKeeper will not record "Z"
in the LotW CFM box and will not consider *the grid in LotW* "confirmed".

+ The letter "G" in the "LoTW CFM" textbox indicates that LoTW considers the QSO's gridsquare confirmed for VUCC; the letter "Z" means that LoTW considers the QSO's Zone confirmed for WAZ.

73,

Dave, AA6YQ


locked Re: JTAlert Grids not matching LOTW VUCC

Joe Subich, W4TV
 

Your attachment(s) do not show what DXKeeper has marked as
"Confirmed" - only what LotW has received. I suggest you
use the DXKeeper "RAT" -> Select the VUCC tab -> Set Band = 6M
-> Check "Confined" *ONLY* and see what DxKeeper says.

If what you originally logged does not match what the other
station uploaded to LotW and you do not allow DXKeeper to
update the grid to match LotW, DXKeeper will not record "Z"
in the LotW CFM box and will not consider *the grid in LotW*
"confirmed".

73,

... Joe, W4TV

On 2021-05-27 10:40 AM, Dan R wrote:
Didn't see attachments.Trying again.
--
Dan KG0AQ


locked Re: reverting to previous version

HamApps Support (VK3AMA)
 

On 27/05/2021 11:25 pm, Tory Wiedenkeller wrote:
So, aside from the 10,000 users, why do I keep seeing requests for 'help' in the group forum? 
Obviously it is NOT working for some people. 

By its nature, a Support Forum is going to attract messages from people requiring support. It is rare to get a message indicating there are no issues to resolve.

Your UDP error is very likely due to WSJT-X set to use unicast UDP and the introduction of a new application that is trying to work with WSJT-X directly resulting in a blocking of UDP comms to JTAlert.

Once you have more than one application concurrently trying to work with WSJT-X, all applications and WSJT-X itself need to be switched to using multicast UDP.

A recent influx of UDP support messages to this group have been the result of the recent release of ACLog 7.0 which now has support for direct interaction with WSJT-X.

Did you install ACLog 7.0 recently? If so that is the likely cause.

See the JTAlert Help file (NOT the JTAlert 2.50.0 features Help), WSJT-X UDP Setup topic.
   

de Laurie VK3AMA


locked Re: JTAlert Grids not matching LOTW VUCC

HamApps Support (VK3AMA)
 

On 28/05/2021 12:40 am, Dan R wrote:
Didn't see attachments.Trying again.
--
Dan KG0AQ

You never did provide the result of running the VUCC report in DXKeeper. That would provide the clue as to where the problem is.

de Laurie VK3AMA


locked Re: JTAlert Grids not matching LOTW VUCC

HamApps Support (VK3AMA)
 

On 28/05/2021 12:35 am, Dan R wrote:
I could do a manual comparison but I still could not change Grids worked in JTAlert.

JTAlert doesn't support manual changes to the confirmed Grids list. All updates to the unneeded grids list are made by running the Alert Database Rebuild which under the hood is interrogating your master log file.

de Laurie VK3AMA


locked Re: JTAlert Grids not matching LOTW VUCC

HamApps Support (VK3AMA)
 

On 28/05/2021 2:05 am, Dan R wrote:
Your both geniuses! I am almost certain that is the discrepancy. I will take a quick look and see. I bet the 59 missing are SSB contacts. DUH!

Thanks! 73
--
Dan KG0AQ

If that is the case, and you want to have matching numbers between JTAlert and LoTW, you will need to switch the Grid Tracking in JTAlert to "Any Mode" rather than a more restrictive individual or digital only mode tracking.

de Laurie VK3AMA


locked Re: window not showing decoded callsigns

HamApps Support (VK3AMA)
 

On 27/05/2021 11:01 pm, Tory Wiedenkeller wrote:
Ok, I did as you suggested.  When I got in to the Decodes pane, the box was already 'enabled.'

Additionally, I do have the .net file installed. I also installed the 64 bit version for WSJT-X, which is what I'm running.
No offense, but the previous version was much more easily installed and used. 

In other posts I've read, they indicate that the UDP is also handled differently.

In your original message, there was no indication that you were experiencing UDP failure messages. That is the root of your problem. If JTAlert is not receiving decodes from WSJT-X because of a UDP failure, it is normal for the Decodes window to not display any new entries.

Get the UDP to work and the Decodes window will start updating as it receives decodes from its controlling parent, JTAlert.

There are not any new UDP requirements introduced with JTAlert 2.50.x, they are the same as the old 2.16.x versions. The only changes to UDP handling were required when WSJT-X 2.3.x changed how it distributed multicast UDP packets. JTAlert had to change to accommodate those changes.

Recent message traffic involving UDP changes have been typically due to the introduction of additional applications trying to work directly with WSJT-X resulting in JTAlert being blocked from interacting with WSJT-X. This is not due to any defect in JTALert, but misconfigured UDP handling. Once an additional WSJT-X interacting application is added into the mix, WSJT-X needs to be switched from using unicast to mulitcast UDP and all applications that want to talk to WSJT-X concurrently also need to be changed to using multicast. This is a not a new requirement of JTAlert. Multicast support by JTAlert was introduced back in August 2020.

Proper setup for mulitcast UDP has a dedicated section in the help file. It covers what needs to change in WSJT-X and the simple, single menu-entry enable needed  by JTAlert.

de Laurie VK3AMA


locked Re: reverting to previous version

Tory Wiedenkeller
 

Ok, good to know. How do I update it?


locked Re: reverting to previous version

Tory Wiedenkeller
 

So, aside from the 10,000 users, why do I keep seeing requests for 'help' in the group forum? 
Obviously it is NOT working for some people. 

Virus-free. www.avast.com


On Thu, May 27, 2021 at 6:23 AM Tory Wiedenkeller <k6tgw.slo@...> wrote:
I also keep getting this error message (shown in the attachment). Something about a udp error.

Virus-free. www.avast.com

On Wed, May 26, 2021 at 10:48 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 27/05/2021 3:29 pm, AOL/ CompuServe Mail via groups.io wrote:
DITTO   This new version is broken. 
 
Gerald Muller K9GEM


JTAlert 2.50.1 is not broken! What makes you think it is broken? What is not working for you?

There are currently close to 10,000 JTAlert users of JTAlert 2.50.0 & 2.50.1 who have enabled spotting to HamSpots, not bad for a broken program IMO.

de Laurie VK3AMA


locked Re: reverting to previous version

Tory Wiedenkeller
 

I also keep getting this error message (shown in the attachment). Something about a udp error.

Virus-free. www.avast.com


On Wed, May 26, 2021 at 10:48 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 27/05/2021 3:29 pm, AOL/ CompuServe Mail via groups.io wrote:
DITTO   This new version is broken. 
 
Gerald Muller K9GEM


JTAlert 2.50.1 is not broken! What makes you think it is broken? What is not working for you?

There are currently close to 10,000 JTAlert users of JTAlert 2.50.0 & 2.50.1 who have enabled spotting to HamSpots, not bad for a broken program IMO.

de Laurie VK3AMA


locked Re: window not showing decoded callsigns

Tory Wiedenkeller
 


Ok, I did as you suggested.  When I got in to the Decodes pane, the box was already 'enabled.'

Additionally, I do have the .net file installed. I also installed the 64 bit version for WSJT-X, which is what I'm running.
No offense, but the previous version was much more easily installed and used. 

In other posts I've read, they indicate that the UDP is also handled differently.

Additionally, I can't get jt-alert to work with ACL. I click the 'log' button at the end of a QSO but it doesn't log the QSO.
On Wed, May 26, 2021 at 9:50 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 27/05/2021 1:40 pm, Tory Wiedenkeller wrote:

I'm not sure what setting I messed up. I had the decode window showing the incoming callsigns, but now it's not showing them.

What do I need to change so this window shows decoded callsigns? Thanks


Open the Settings of the Main JTAlert window and navigate to the "Window -> Decodes" section and tick the enable box.

de Laurie VK3AMA


Virus-free. www.avast.com


locked Re: JTAlert Grids not matching LOTW VUCC

Dan R
 

Paul and Tom,

Your both geniuses! I am almost certain that is the discrepancy. I will take a quick look and see. I bet the 59 missing are SSB contacts. DUH!

Thanks! 73
--
Dan KG0AQ


locked Re: JTAlert Grids not matching LOTW VUCC

Paul W5PF
 

Dan,

Are all of your LoTW confirmations FT8?

Paul W5PF

On 5/27/2021 9:40 AM, Dan R wrote:
Didn't see attachments.Trying again.
--
Dan KG0AQ


locked Re: JTAlert Grids not matching LOTW VUCC

Tom Melvin
 

Dan

Suggest you do a manual check to find a couple that have not come through and then see what they have in common - maybe you have a date restriction in JTA, different mode e.g. ssb/cw where jta is looking at digital.

Just hitting re-build time after time will not make a difference, little bit of investigation at your end will be needed.

Tom
GM8MJV


On 27 May 2021, at 15:40, Dan R <kg0aq1@...> wrote:

Didn't see attachments.Trying again.
--
Dan KG0AQ


locked Re: JTAlert Grids not matching LOTW VUCC

Dan R
 

Didn't see attachments.Trying again.
--
Dan KG0AQ

3541 - 3560 of 38532