Topics

locked UDP Error With JTDX


Ed Wilson
 

Laurie,

I am having the same problem with 2.13.4...any suggestions?

Laurie,

When using 2.13.3 with JTDX I get a UDP setup error message which I do not get with 2.13.2. I am using JTDX v2.0.1-rc136_10 which worked fine with JTAlert 2.13.2.

Ed, K0KC

k0kc@...
http://k0kc.us/



Ed, K0KC

k0kc@...
http://k0kc.us/


Ed Wilson
 

By the way, both 2.13.3 and 2.13.4 work fine with WSJT-X.

Ed, K0KC

k0kc@...
http://k0kc.us/


On Wednesday, May 1, 2019, 5:00:54 AM EDT, Ed Wilson via Groups.Io <ed.wilson@...> wrote:


Laurie,

I am having the same problem with 2.13.4...any suggestions?

Laurie,

When using 2.13.3 with JTDX I get a UDP setup error message which I do not get with 2.13.2. I am using JTDX v2.0.1-rc136_10 which worked fine with JTAlert 2.13.2.

Ed, K0KC

k0kc@...
http://k0kc.us/



Ed, K0KC

k0kc@...
http://k0kc.us/


Anton Iriawan
 

Same problem here with JTDX v2.0.1 rc136-10 with JTalert 2.13.3 and 2.13.4, now downgrade back to 2.13.2 which worked fine.

 

73

Anton – YB5QZ

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Ed Wilson via Groups.Io
Sent: Rabu, 01 Mei 2019 16.01
To: Hamapps Groups Support <support@hamapps.groups.io>
Subject: [HamApps] UDP Error With JTDX

 

Laurie,

 

I am having the same problem with 2.13.4...any suggestions?

 

Laurie,

 

When using 2.13.3 with JTDX I get a UDP setup error message which I do not get with 2.13.2. I am using JTDX v2.0.1-rc136_10 which worked fine with JTAlert 2.13.2.

 

 

 

 


HamApps Support (VK3AMA)
 

On 1/05/2019 7:00 pm, Ed Wilson via Groups.Io wrote:
When using 2.13.3 with JTDX I get a UDP setup error message which I do not get with 2.13.2. I am using JTDX v2.0.1-rc136_10 which worked fine with JTAlert 2.13.2.

Please post an image of the error window (not your entire desktop), I need to see the detail presented in the dialog.

It may be related to the change made in 2.13.3.
    - Not reading correct WSJT-X config file for 64bit compiled versions of
       WSJT-X running with a --rig-name parameter.

de Laurie VK3AMA


Ed Wilson
 

Laurie,

Here is the screen shot:

Inline image


Ed, K0KC

k0kc@...
http://k0kc.us/


On Wednesday, May 1, 2019, 5:29:15 AM EDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 1/05/2019 7:00 pm, Ed Wilson via Groups.Io wrote:
When using 2.13.3 with JTDX I get a UDP setup error message which I do not get with 2.13.2. I am using JTDX v2.0.1-rc136_10 which worked fine with JTAlert 2.13.2.


Please post an image of the error window (not your entire desktop), I need to see the detail presented in the dialog.

It may be related to the change made in 2.13.3.
    - Not reading correct WSJT-X config file for 64bit compiled versions of
       WSJT-X running with a --rig-name parameter.

de Laurie VK3AMA


Ed Wilson
 

Laurie,

FYI, I am not using the 64-bit compiled version of WSJT-X (The error occurs with JTDX) but I am usiing a --rig-name parameter for JTDX.

Ed, K0KC

k0kc@...
http://k0kc.us/


On Wednesday, May 1, 2019, 5:29:15 AM EDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 1/05/2019 7:00 pm, Ed Wilson via Groups.Io wrote:
When using 2.13.3 with JTDX I get a UDP setup error message which I do not get with 2.13.2. I am using JTDX v2.0.1-rc136_10 which worked fine with JTAlert 2.13.2.


Please post an image of the error window (not your entire desktop), I need to see the detail presented in the dialog.

It may be related to the change made in 2.13.3.
    - Not reading correct WSJT-X config file for 64bit compiled versions of
       WSJT-X running with a --rig-name parameter.

de Laurie VK3AMA


HamApps Support (VK3AMA)
 

On 1/05/2019 8:22 pm, Ed Wilson via Groups.Io wrote:
Here is the screen shot:




Ed, K0KC
OK, I have been able to replicate the problem.
It is caused by the 2.13.2 changes made to work with 64bit WSJT-X when it is using a --rig-name parameter.

Until I release a new JTAlert build, you will need to run JTDX without a --rig-name parameter or stay with 2.13.2

de Laurie VK3AMA


Ed Wilson
 

Thanks, Laurie!

I may go back to 2.13.2 although I have been testing FT4 and would like to have the changes that you  made to at least partially accommodate that mode. Take  your time...I am patient!

Ed, K0KC

k0kc@...
http://k0kc.us/


On Wednesday, May 1, 2019, 8:16:38 AM EDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 1/05/2019 8:22 pm, Ed Wilson via Groups.Io wrote:
Here is the screen shot:

Inline image


Ed, K0KC
OK, I have been able to replicate the problem.
It is caused by the 2.13.2 changes made to work with 64bit WSJT-X when it is using a --rig-name parameter.

Until I release a new JTAlert build, you will need to run JTDX without a --rig-name parameter or stay with 2.13.2

de Laurie VK3AMA