Date   

locked Re: TX not enabled

HamApps Support (VK3AMA)
 

On 2/05/2019 6:55 am, Michael Wheatley wrote:
I'm running JTAlertX 2.13.4, which I start after WSIT-X has been started.  Often, if I click a call sign displayed by JTAlertX, it is not enabled for TX in WSIT-X.  If I restart JTAlertX, the correct behavior is restored.

Any suggestions to fix this?

Michael -- KM6LHD

There is no fix because there is nothing to fix.

Enabling TX within WSJT-X is the exclusive responsibility of WSJT-X. The WSJT-X api doesn't allow for third party applications like JTAlert to enable TX. If the WSJT-X DX Call is changing in response to a Callsign click in JTAlert then all is working as it should.

Internally WSJT-X makes the decision as to whether TX should be enabled depending on the decode type and I believe the operating mode (I am not certain on that last part however).

de Laurie VK3AMA


locked New jt-alert

SEAN MURDOCH <sean195@...>
 

Great job Laurie , new update. Fast. Just need eqsl to catch up.  You deserve a medal 🥉. Love jt alert   Thanks again for your hard work. 😁 


locked Re: New JTAlert 2.13.4 available.

John
 

Laurie,

Never give in to pressure from your fans, it's ready when it is ready and not
before.
They'll wait... because they have to wait.

John
VE3KKQ

---------- Original Message ----------
From: "HamApps Support (VK3AMA)" <vk3ama.ham.apps@gmail.com>
Date: May 1, 2019 at 5:12 PM


On 1/05/2019 11:49 pm, Michael Black via Groups.Io wrote:
It appears the CQ "*" and "#" indicators are not working for FT4.

de Mike W9MDB
Mike,

That's a defect.
This is what happens when, in an effort to appease the clamouring
masses, a release is fast-tracked without adequate testing.

This is now corrected for the next release.

de Laurie VK3AMA




locked Re: New JTAlert 2.13.4 available.

HamApps Support (VK3AMA)
 

On 1/05/2019 11:49 pm, Michael Black via Groups.Io wrote:
It appears the CQ "*" and "#" indicators are not working for FT4.

de Mike W9MDB
Mike,

That's a defect.
This is what happens when, in an effort to appease the clamouring masses, a release is fast-tracked without adequate testing.

This is now corrected for the next release.

de Laurie VK3AMA


locked TX not enabled

Michael Wheatley
 

I'm running JTAlertX 2.13.4, which I start after WSIT-X has been started.  Often, if I click a call sign displayed by JTAlertX, it is not enabled for TX in WSIT-X.  If I restart JTAlertX, the correct behavior is restored.

Any suggestions to fix this?

Michael -- KM6LHD


locked Re: New JTAlert 2.13.4 available.

igwt1939 <igwt1939@...>
 

Last night I downloaded JTAlert and followed instructions on how to work FT4.
I made some contacts AND then read where I was supposed to delete a couple of files.
In fact I could not find the Windows File Explorer or the two files to be deleted.
What’s going to happen in the future?
KO4PU


locked Re: New JTAlert 2.13.4 available.

David Chema
 

Unbelievable level of support Laurie!   Your contributions to amateur radio are greatly appreciated!  Thank you so much for the quick support of FT4!  Now I think you deserve a vacation!

73, Dave KC8V


On May 1, 2019, at 11:49 AM, Carey Fisher <careyfisher@...> wrote:

Laurie,
Thank you for this amazing piece of software and your incredible ability to turn on a dime to support new developments in the other apps!
73, Carey, WB4HXE

On Wed, May 1, 2019 at 11:14 AM Howard W6HDG <w6hdg@...> wrote:
Laurie, 
Thank you for all you do. I can't believe you updated for FT4 call sign display within hours. Amazing.  You deserve a raise :) 

73, Howard W6HDG 



--
Carey Fisher


locked Re: New JTAlert 2.13.4 available.

Carey, WB4HXE
 

Laurie,
Thank you for this amazing piece of software and your incredible ability to turn on a dime to support new developments in the other apps!
73, Carey, WB4HXE

On Wed, May 1, 2019 at 11:14 AM Howard W6HDG <w6hdg@...> wrote:
Laurie, 
Thank you for all you do. I can't believe you updated for FT4 call sign display within hours. Amazing.  You deserve a raise :) 

73, Howard W6HDG 



--
Carey Fisher


locked Re: New JTAlert 2.13.4 available.

Howard W6HDG
 

Laurie, 
Thank you for all you do. I can't believe you updated for FT4 call sign display within hours. Amazing.  You deserve a raise :) 

73, Howard W6HDG 


locked Re: New JTAlert 2.13.4 available.

Michael Black
 

Thanks ever-so-much for the FT4 capability Laurie.  Helps a lot during the testing.....

It appears the CQ "*" and "#" indicators are not working for FT4.

de Mike W9MDB


locked Re: UDP Error With JTDX

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


locked New JTAlert 2.13.4 available.

Bob WB2NVR
 

TNX for the quick release of this update, Laurie.

The new release works FB.  Amazing how lost I felt using FT4 without JTAlert showing B4!

JTAlert and DXKeeper, along with WSJT, are great programs, and the support is phenomenal.

I just wanted to say Thank You one more time - I really appreciate all your hard work to make this software available.

73 ES GUD DX,

Bob WB2NVR


locked Re: FT4

Neil Foster
 

Hello Neil
Glad to see we both spell our name correctly!  
No it was on 20 meters

Neil    N4FN


locked Re: UDP Error With JTDX

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


locked Re: UDP Error With JTDX

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


locked Re: UDP Error With JTDX

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


locked Re: UDP Error With JTDX

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


locked Re: UDP Error With JTDX

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.

 

 

 

 


locked Re: UDP Error With JTDX

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/


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/

13321 - 13340 of 37312