Date   

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

BOB K5HX
 

I shut down all other running applications other than WSJT-X and HRD and still have the same result.
Also,  the netstat -ano command produced the following which contains the correct port number.   UDP  0.0.0.0:2237 and a process number which corresponded to JTAlertV2.Manager.exe

Bob  K5HX


locked Re: Suggestion for the TXT messages

John C
 

Laurie, I am already using 2.50.1 but I cant find this setting...     would you mind pointing this dumb one where to look please...

 

John


locked Re: Suggestion for the TXT messages

Laurie, VK3AMA
 

Also, The Messaging window has an option to not follow the DXCall changes.
If you want to leave that activated, then simply having any text in the message compose area will stop any DXCall changes being actioned.

de Laurie VK3AMA


locked Re: Suggestion for the TXT messages

Laurie, VK3AMA
 

On 28/05/2021 2:32 pm, John C wrote:

Several times now, the TXT messager has sent a message I have been typing to the wrong person...   Can we please get this fixed.......  what happens is this.........

While I am working people, I start to type a message to a previous contact.   Part way through typing I work another call and the messages facility changes the "to" callsign to that of the latest station I am working and I end up sending the message to the wrong person.

Is there a way that you ciould please "lock" the callsign in that I am typing to so as to prevent this happening ???

regards

John
That's already available. Upgrade your JTAlert version.

From the 2.50.1 release notes...
  Changed:

    - Messaging window: WSJT-X DX Call changes now no longer auto populate the
       Callsign field if a message is already being composed. That is if the
       message field contains text, the DX Call change is ignored.
de Laurie VK3AMA


locked Re: Suggestion for the TXT messages

Michael Black
 

Would seem reasonable while that window is the active window that it wouldn't change.

Mike W9MDB




On Thursday, May 27, 2021, 11:32:11 PM CDT, John C <vk7xx.radio@...> wrote:


Several times now, the TXT messager has sent a message I have been typing to the wrong person...   Can we please get this fixed.......  what happens is this.........

While I am working people, I start to type a message to a previous contact.   Part way through typing I work another call and the messages facility changes the "to" callsign to that of the latest station I am working and I end up sending the message to the wrong person.

Is there a way that you ciould please "lock" the callsign in that I am typing to so as to prevent this happening ???

 

regards

John


locked Suggestion for the TXT messages

John C
 

Several times now, the TXT messager has sent a message I have been typing to the wrong person...   Can we please get this fixed.......  what happens is this.........

While I am working people, I start to type a message to a previous contact.   Part way through typing I work another call and the messages facility changes the "to" callsign to that of the latest station I am working and I end up sending the message to the wrong person.

Is there a way that you ciould please "lock" the callsign in that I am typing to so as to prevent this happening ???

 

regards

John


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

Michael Black
 

The easy way to find out is to shut down everything except WSJT-X and JTAlert.
Then test clicking....if it works then some other app is intercepting the response.

Mike W9MDB




On Thursday, May 27, 2021, 07:15:42 PM CDT, BOB K5HX via groups.io <k5hx@...> wrote:


As far as I can tell HRD is not configured for multicast UDP on the same port. 

Bob K5HX


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

BOB K5HX
 

As far as I can tell HRD is not configured for multicast UDP on the same port. 

Bob K5HX


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

Dave Garber
 

yes, multicast is supported.... in GT

Dave Garber
VE3WEJ / VE3IE


On Thu, May 27, 2021 at 6:57 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Are you sure Grid Tracker does multicast?  

Do you have HRD listening to the WSJT-X port too maybe?

Mike W9MDB




On Thursday, May 27, 2021, 05:47:18 PM CDT, BOB K5HX via groups.io <k5hx=yahoo.com@groups.io> wrote:


Mike,

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

Bob  K5HX


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

Michael Black
 

Are you sure Grid Tracker does multicast?  

Do you have HRD listening to the WSJT-X port too maybe?

Mike W9MDB




On Thursday, May 27, 2021, 05:47:18 PM CDT, BOB K5HX via groups.io <k5hx@...> wrote:


Mike,

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

Bob  K5HX


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

2661 - 2680 of 37662