locked Ver 2.50.0 issues


Bill Barrett
 

Hello Laurie-

See attached screenshots.

1.) Running 8 instances of WSJT-X and JTAlert. Receiving UDP Comm Failure on instance 8.
Each instance of WSJT-X has a unique UDP Port number.

2.) Instance #1 does not always display the Band and Mode.

3.) If all 8 instances of WSJT-X are up and starting JTAlert instances, JTAlert sometimes misses an instance of WSJT-X. Best to start one instance of WSJT-X along with JTAlert and go on until all 8 instances are up.

The new call window is very flexible.

Thanks;
Bill W2PKY


HamApps Support (VK3AMA)
 

On 13/04/2021 10:40 am, Bill Barrett wrote:

1.) Running 8 instances of WSJT-X and JTAlert. Receiving UDP Comm Failure on instance 8.
Each instance of WSJT-X has a unique UDP Port number.

2.) Instance #1 does not always display the Band and Mode.

3.) If all 8 instances of WSJT-X are up and starting JTAlert instances, JTAlert sometimes misses an instance of WSJT-X. Best to start one instance of WSJT-X along with JTAlert and go on until all 8 instances are up.

The new call window is very flexible.

Thanks;
Bill W2PKY

Bill,

I suggest you move over to using UDP multicast for the WSJT-X UDP Server settings. With multicast there is no need for unique ports, all instances can use the same port.

As for auto-starting WSJT-X, you could try adding in an additional delay for each startup entry. Alternatively, setup a batch file to start WSJT-X then JTAlert followed by a pause and repeat that for the additional instance pairs.

de Laurie VK3AMA


Bill Barrett
 

Hello Laurie-

Switched over to Multicast but no help. Notice the band and mode are still not found.
Any other suggestions?
Thanks;
Bill W2PKY

On Mon, Apr 12, 2021 at 10:54 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 13/04/2021 10:40 am, Bill Barrett wrote:

1.) Running 8 instances of WSJT-X and JTAlert. Receiving UDP Comm Failure on instance 8.
Each instance of WSJT-X has a unique UDP Port number.

2.) Instance #1 does not always display the Band and Mode.

3.) If all 8 instances of WSJT-X are up and starting JTAlert instances, JTAlert sometimes misses an instance of WSJT-X. Best to start one instance of WSJT-X along with JTAlert and go on until all 8 instances are up.

The new call window is very flexible.

Thanks;
Bill W2PKY

Bill,

I suggest you move over to using UDP multicast for the WSJT-X UDP Server settings. With multicast there is no need for unique ports, all instances can use the same port.

As for auto-starting WSJT-X, you could try adding in an additional delay for each startup entry. Alternatively, setup a batch file to start WSJT-X then JTAlert followed by a pause and repeat that for the additional instance pairs.

de Laurie VK3AMA


Bill Barrett
 

I think it's the "MSK144" mode.


On Tue, Apr 13, 2021 at 7:59 AM Bill Barrett via groups.io <billbarrett174=gmail.com@groups.io> wrote:
Hello Laurie-

Switched over to Multicast but no help. Notice the band and mode are still not found.
Any other suggestions?
Thanks;
Bill W2PKY

On Mon, Apr 12, 2021 at 10:54 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 13/04/2021 10:40 am, Bill Barrett wrote:

1.) Running 8 instances of WSJT-X and JTAlert. Receiving UDP Comm Failure on instance 8.
Each instance of WSJT-X has a unique UDP Port number.

2.) Instance #1 does not always display the Band and Mode.

3.) If all 8 instances of WSJT-X are up and starting JTAlert instances, JTAlert sometimes misses an instance of WSJT-X. Best to start one instance of WSJT-X along with JTAlert and go on until all 8 instances are up.

The new call window is very flexible.

Thanks;
Bill W2PKY

Bill,

I suggest you move over to using UDP multicast for the WSJT-X UDP Server settings. With multicast there is no need for unique ports, all instances can use the same port.

As for auto-starting WSJT-X, you could try adding in an additional delay for each startup entry. Alternatively, setup a batch file to start WSJT-X then JTAlert followed by a pause and repeat that for the additional instance pairs.

de Laurie VK3AMA


Fred Roberts
 

Good morning Laurie.....
      A bit of help needed. Installed 2.50.0 and after a minute or two wait I get the following pop up window:
     I am running Windows 10 Home. I did get the warning that . Net 5 wasn't installed, and I installed it (I choose the x86 version - should I have used x64?)  
I've also included a shot of the WSJT-x settings.
     Thanks for your help, and a great program!
73,
Fred
WB4QOC



On Tue, Apr 13, 2021, 7:59 AM Bill Barrett <billbarrett174@...> wrote:
Hello Laurie-

Switched over to Multicast but no help. Notice the band and mode are still not found.
Any other suggestions?
Thanks;
Bill W2PKY

On Mon, Apr 12, 2021 at 10:54 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 13/04/2021 10:40 am, Bill Barrett wrote:

1.) Running 8 instances of WSJT-X and JTAlert. Receiving UDP Comm Failure on instance 8.
Each instance of WSJT-X has a unique UDP Port number.

2.) Instance #1 does not always display the Band and Mode.

3.) If all 8 instances of WSJT-X are up and starting JTAlert instances, JTAlert sometimes misses an instance of WSJT-X. Best to start one instance of WSJT-X along with JTAlert and go on until all 8 instances are up.

The new call window is very flexible.

Thanks;
Bill W2PKY

Bill,

I suggest you move over to using UDP multicast for the WSJT-X UDP Server settings. With multicast there is no need for unique ports, all instances can use the same port.

As for auto-starting WSJT-X, you could try adding in an additional delay for each startup entry. Alternatively, setup a batch file to start WSJT-X then JTAlert followed by a pause and repeat that for the additional instance pairs.

de Laurie VK3AMA


Fred Roberts
 

Laurie.....
       Good news! The answer to my question....should I have chosen the x64 version is YES!!!!....no problem uninstalling the x86 version, I just sorted by date installed, followed the link you provided in your install instructions, choose the CORRECT version, and 2.50.0 is up and running!
Tnx es 73,
Fred
WB4QOC



Sent from my phone.....Fred


On Tue, Apr 13, 2021, 8:26 AM Fred Roberts via groups.io <fred5352=gmail.com@groups.io> wrote:
Good morning Laurie.....
      A bit of help needed. Installed 2.50.0 and after a minute or two wait I get the following pop up window:
     I am running Windows 10 Home. I did get the warning that . Net 5 wasn't installed, and I installed it (I choose the x86 version - should I have used x64?)  
I've also included a shot of the WSJT-x settings.
     Thanks for your help, and a great program!
73,
Fred
WB4QOC



On Tue, Apr 13, 2021, 7:59 AM Bill Barrett <billbarrett174@...> wrote:
Hello Laurie-

Switched over to Multicast but no help. Notice the band and mode are still not found.
Any other suggestions?
Thanks;
Bill W2PKY

On Mon, Apr 12, 2021 at 10:54 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 13/04/2021 10:40 am, Bill Barrett wrote:

1.) Running 8 instances of WSJT-X and JTAlert. Receiving UDP Comm Failure on instance 8.
Each instance of WSJT-X has a unique UDP Port number.

2.) Instance #1 does not always display the Band and Mode.

3.) If all 8 instances of WSJT-X are up and starting JTAlert instances, JTAlert sometimes misses an instance of WSJT-X. Best to start one instance of WSJT-X along with JTAlert and go on until all 8 instances are up.

The new call window is very flexible.

Thanks;
Bill W2PKY

Bill,

I suggest you move over to using UDP multicast for the WSJT-X UDP Server settings. With multicast there is no need for unique ports, all instances can use the same port.

As for auto-starting WSJT-X, you could try adding in an additional delay for each startup entry. Alternatively, setup a batch file to start WSJT-X then JTAlert followed by a pause and repeat that for the additional instance pairs.

de Laurie VK3AMA

Attachments:


HamApps Support (VK3AMA)
 

On 13/04/2021 9:59 pm, Bill Barrett wrote:
Hello Laurie-

Switched over to Multicast but no help. Notice the band and mode are still not found.
Any other suggestions?
Thanks;
Bill W2PKY

On Mon, Apr 12, 2021 at 10:54 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 13/04/2021 10:40 am, Bill Barrett wrote:

1.) Running 8 instances of WSJT-X and JTAlert. Receiving UDP Comm Failure on instance 8.
Each instance of WSJT-X has a unique UDP Port number.

2.) Instance #1 does not always display the Band and Mode.

3.) If all 8 instances of WSJT-X are up and starting JTAlert instances, JTAlert sometimes misses an instance of WSJT-X. Best to start one instance of WSJT-X along with JTAlert and go on until all 8 instances are up.

The new call window is very flexible.

Thanks;
Bill W2PKY

Bill,

I suggest you move over to using UDP multicast for the WSJT-X UDP Server settings. With multicast there is no need for unique ports, all instances can use the same port.

As for auto-starting WSJT-X, you could try adding in an additional delay for each startup entry. Alternatively, setup a batch file to start WSJT-X then JTAlert followed by a pause and repeat that for the additional instance pairs.

de Laurie VK3AMA




Likely its the port 2333 you're trying to use. That should not be a problem, but I have seen many users set to use 2333 and things stop working because they also have the WSJT-X secondary server enabled and it is set to 2333.
   

Make sure it is turned off. Also check that you don't have JTAlert set to rebroadcast UDP messages on the same port (under the "Applications -> WSJT-X /JTDX" section of the main JTAlert Settings window).

If you still have problems, use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA



Bill Barrett
 

Hello Laurie-

Moved over to Multicast and all is well now.

Couple of "Nice to Haves"

1. Filter USA calls only. I run HF - 6M on my 6700 so want to see: Caribbean, Mexico, Canada which are filtered out by the N.A. filter. 
   Filtering out USA calls in the Callsigns window would reduce the number of entries on busy bands like 40 & 20M. 
   Finally, it would be nice if each Callsigns window could have it's own filters.

2. Sort Callsigns window by 1, CQ  2. 73 3. DX 4. all others.

Thanks, could not operate FT8 without this app.

Bill W2PKY

On Tue, Apr 13, 2021 at 8:25 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 13/04/2021 9:59 pm, Bill Barrett wrote:
Hello Laurie-

Switched over to Multicast but no help. Notice the band and mode are still not found.
Any other suggestions?
Thanks;
Bill W2PKY

On Mon, Apr 12, 2021 at 10:54 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 13/04/2021 10:40 am, Bill Barrett wrote:

1.) Running 8 instances of WSJT-X and JTAlert. Receiving UDP Comm Failure on instance 8.
Each instance of WSJT-X has a unique UDP Port number.

2.) Instance #1 does not always display the Band and Mode.

3.) If all 8 instances of WSJT-X are up and starting JTAlert instances, JTAlert sometimes misses an instance of WSJT-X. Best to start one instance of WSJT-X along with JTAlert and go on until all 8 instances are up.

The new call window is very flexible.

Thanks;
Bill W2PKY

Bill,

I suggest you move over to using UDP multicast for the WSJT-X UDP Server settings. With multicast there is no need for unique ports, all instances can use the same port.

As for auto-starting WSJT-X, you could try adding in an additional delay for each startup entry. Alternatively, setup a batch file to start WSJT-X then JTAlert followed by a pause and repeat that for the additional instance pairs.

de Laurie VK3AMA




Likely its the port 2333 you're trying to use. That should not be a problem, but I have seen many users set to use 2333 and things stop working because they also have the WSJT-X secondary server enabled and it is set to 2333.
   

Make sure it is turned off. Also check that you don't have JTAlert set to rebroadcast UDP messages on the same port (under the "Applications -> WSJT-X /JTDX" section of the main JTAlert Settings window).

If you still have problems, use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA



HamApps Support (VK3AMA)
 

On 14/04/2021 10:41 am, Bill Barrett wrote:
Moved over to Multicast and all is well now.

Couple of "Nice to Haves"

1. Filter USA calls only. I run HF - 6M on my 6700 so want to see: Caribbean, Mexico, Canada which are filtered out by the N.A. filter. 
   Filtering out USA calls in the Callsigns window would reduce the number of entries on busy bands like 40 & 20M. 
   Finally, it would be nice if each Callsigns window could have it's own filters.

2. Sort Callsigns window by 1, CQ  2. 73 3. DX 4. all others.

Thanks, could not operate FT8 without this app.

Bill W2PKY

Good stuff!

1. USA only filtering is on the todo list along with every other Country. It's unlikely to happen in the near future however. The same applies for Filtering at the Callsigns window level. Everything displayed in the Callsigns window is still coming from the old JTAlert code and there are issues with trying to implement this currently.

2. Sorting, very unlikely to happen. Sorting by its nature consumes extra CPU resources, depending on the algorithm used adding to a slowdown of the Callsigns display. The biggest problem however is that to sort a list of decodes, by any criteria (frequency, db, message type, country, etc) requires that all the decodes are available prior to sorting which means hanging onto the decodes and waiting till they have all been received and then applying the sort.  That would add seconds to the time to display the Callsigns. With WSJT-X now supporting early decoding and up to 3 passes, holding off the Callsigns display until all have been received is a show-stopper, IMO.

There are alternate solutions to sorting in batches but they will result in a continuous shuffling of the Callsigns in the display as each is received from WSJT-X, with the shuffling ending only after all decodes have been received.


de Laurie VK3AMA




Bill Barrett
 

Hello Laurie-

Yes sorting multiple sets of data would be unacceptable of course. After thinking about it, I came up with this brainstorm.
How about multiple Callsigns windows where one contains CQ calls, second has 73 calls and a third with all the rest?
These windows could be re-sizeable. Or one window with multiple partitions? Okay, hope you get a laugh [or at least a giggle] out of this.

73. Bill W2PKY

On Tue, Apr 13, 2021 at 9:26 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 14/04/2021 10:41 am, Bill Barrett wrote:
Moved over to Multicast and all is well now.

Couple of "Nice to Haves"

1. Filter USA calls only. I run HF - 6M on my 6700 so want to see: Caribbean, Mexico, Canada which are filtered out by the N.A. filter. 
   Filtering out USA calls in the Callsigns window would reduce the number of entries on busy bands like 40 & 20M. 
   Finally, it would be nice if each Callsigns window could have it's own filters.

2. Sort Callsigns window by 1, CQ  2. 73 3. DX 4. all others.

Thanks, could not operate FT8 without this app.

Bill W2PKY

Good stuff!

1. USA only filtering is on the todo list along with every other Country. It's unlikely to happen in the near future however. The same applies for Filtering at the Callsigns window level. Everything displayed in the Callsigns window is still coming from the old JTAlert code and there are issues with trying to implement this currently.

2. Sorting, very unlikely to happen. Sorting by its nature consumes extra CPU resources, depending on the algorithm used adding to a slowdown of the Callsigns display. The biggest problem however is that to sort a list of decodes, by any criteria (frequency, db, message type, country, etc) requires that all the decodes are available prior to sorting which means hanging onto the decodes and waiting till they have all been received and then applying the sort.  That would add seconds to the time to display the Callsigns. With WSJT-X now supporting early decoding and up to 3 passes, holding off the Callsigns display until all have been received is a show-stopper, IMO.

There are alternate solutions to sorting in batches but they will result in a continuous shuffling of the Callsigns in the display as each is received from WSJT-X, with the shuffling ending only after all decodes have been received.


de Laurie VK3AMA




HamApps Support (VK3AMA)
 

On 15/04/2021 9:26 am, Bill Barrett wrote:
Or one window with multiple partitions? Okay, hope you get a laugh [or at least a giggle] out of this.

73. Bill W2PKY

Not as far-fetched as you think. Are you aware the Callsigns window already has an additional partition that display Stations calling you?

Rather than multiple partitions, perhaps one additional partition with the ability for the user to assign what sort of decodes appear there, say CQs or 73s or a specific Alert type (like Dxcc or State) with the ability for the Callsigns to persist for a period of time (ie they don't automatically get cleared at the end of a period like the main display partition).

The beauty with the new code and desktop UI creation tools is the flexibility it gives me in adding new functionality with minimal fuss, aka headaches. Not that this is an acknowledgement of what you propose will happen, but I am not apposed to the idea.

de Laurie VK3AMA


Russ Ravella
 

An assignable window sounds like a great idea to me, Laurie  !

As it is, the more I use this the more I love it - again, thanks so much  !

Russ KR6W


On Apr 14, 2021, at 4:52 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:

On 15/04/2021 9:26 am, Bill Barrett wrote:
Or one window with multiple partitions? Okay, hope you get a laugh [or at least a giggle] out of this.

73. Bill W2PKY

Not as far-fetched as you think. Are you aware the Callsigns window already has an additional partition that display Stations calling you?

Rather than multiple partitions, perhaps one additional partition with the ability for the user to assign what sort of decodes appear there, say CQs or 73s or a specific Alert type (like Dxcc or State) with the ability for the Callsigns to persist for a period of time (ie they don't automatically get cleared at the end of a period like the main display partition).

The beauty with the new code and desktop UI creation tools is the flexibility it gives me in adding new functionality with minimal fuss, aka headaches. Not that this is an acknowledgement of what you propose will happen, but I am not apposed to the idea.

de Laurie VK3AMA



Bill Barrett
 

Hello Laurie-

  Are you aware the Callsigns window already has an additional partition that display Stations calling you?

Yes, saw that, Very COOL!
Looking forward to additional enhancements, Elon Musk calls them Easter Eggs.

73;

Bill W2PKY

On Wed, Apr 14, 2021 at 7:53 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 15/04/2021 9:26 am, Bill Barrett wrote:
Or one window with multiple partitions? Okay, hope you get a laugh [or at least a giggle] out of this.

73. Bill W2PKY

Not as far-fetched as you think. Are you aware the Callsigns window already has an additional partition that display Stations calling you?

Rather than multiple partitions, perhaps one additional partition with the ability for the user to assign what sort of decodes appear there, say CQs or 73s or a specific Alert type (like Dxcc or State) with the ability for the Callsigns to persist for a period of time (ie they don't automatically get cleared at the end of a period like the main display partition).

The beauty with the new code and desktop UI creation tools is the flexibility it gives me in adding new functionality with minimal fuss, aka headaches. Not that this is an acknowledgement of what you propose will happen, but I am not apposed to the idea.

de Laurie VK3AMA