Date   

locked Re: FT4

Neil Foster
 

Now that makes sense Laurie....sometimes the simple things are obvious and we just do not see it.
Thanks
Neil   N4FN


locked Re: JTAlert 2nd or 3rd instance does not start if WSJT-X and JTDX are running in parallel

JTAlert Support (VK3AMA)
 

On 2/05/2019 8:55 pm, Uwe wrote:
I am currently doing some tests where I am running WSJT-X and JTDX in parallel. Works well, however I have troubles starting JTAlert for all of them in parallel. Once WSJT-X is running, JTDX is not recognized as running. When JTDX is running alone JTAlert is working together with it in a normal way. Of course I am starting JTAlert for WSJT-X via "WSJT-X - JTAlertX" and JTAlert for JTDX via "JTDX - JTAlert" link, and under settings I ensured that both are using separate UDP server port numbers (see screenshot).
What am I doing wrong?
73 de Uwe, DG2YCB

Running multiple instances of JTAlert against both WSJT-X and JTDX simultaneously is not supported

From the 2.10.0 (21-JUL-2017) release notes
    - The multi-instance support has also been changed. Running multiple copies
       of JTAlert against both WSJT-X and JTDX simultaneously is not supported.
       You can run multiple instances of JTAlert against either WSJT-X OR JTDX
       only. Both types of applications can be running simultaneously on the PC,
       but only one JTAlert operating mode (against WSJT-X or JTDX) is allowed.

de Laurie VK3AMA


locked JTAlert 2nd or 3rd instance does not start if WSJT-X and JTDX are running in parallel

Uwe, DG2YCB
 

Hi,
I am currently doing some tests where I am running WSJT-X and JTDX in parallel. Works well, however I have troubles starting JTAlert for all of them in parallel. Once WSJT-X is running, JTDX is not recognized as running. When JTDX is running alone JTAlert is working together with it in a normal way. Of course I am starting JTAlert for WSJT-X via "WSJT-X - JTAlertX" and JTAlert for JTDX via "JTDX - JTAlert" link, and under settings I ensured that both are using separate UDP server port numbers (see screenshot).
What am I doing wrong?
73 de Uwe, DG2YCB

Btw. In my head-to-head comparison JTDX wins the race in terms of decoding sensitivity.


locked Re: Odp: [HamApps] New JTAlert 2.13.4 available.

g4wjs
 

On 02/05/2019 06:09, Henryk Skalimowski wrote:
Laurie,
 
what do you think about the new version (FT4 mode) for old Windows XP?
 
Many radiohams still use use this.
 
Henryk
SP4L

Henryk,

WSJT-X will be dropping support for Windows XP and Vista soon, the new 64-bit version for Windows has already dropped XP support. The tools that Laurie is using for new development do not support them either, continuing to support obsolete operating system versions is counter productive and reduces functionality and quality for those that feel insecure operating systems should be replaced.


--
73
Bill
G4WJS.


locked Odp: [HamApps] New JTAlert 2.13.4 available.

Henryk SP4L
 

Laurie,
 
what do you think about the new version (FT4 mode) for old Windows XP?
 
Many radiohams still use use this.
 
Henryk
SP4L
 


locked Re: FT4

JTAlert Support (VK3AMA)
 

On 1/05/2019 9:32 am, Neil wrote:
I have downloaded the new version of JTAlert (.4) and I have only listened to FT4 and not tried to TX. I notice a periodic tone  happening and wonder if this is generated by JTAlert or is it from WSJT-X? I never had that before
Thanks Laurie for a great program addition and support
Neil   N4FN
The easiest way to test if it is JTAlert generated audio is turn mute the sound in JTAlert. Repeatedly click the "Sound ..." menu in the title bar until it says "Sound OFF". If the tone persists it is not coming from JTAlert.

de Laurie VK3AMA


locked Re: TX not enabled

JTAlert 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@...>
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.

JTAlert 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

JTAlert 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

16361 - 16380 of 40358