Date   

locked Re: JTAlert with JTDX and WSJT-X at the same time.

K0GU
 

Unfortunately you are likely right. It will be interesting to see if Q65 can produce some EU results on 50.305 that don't happen on FT8. But I run JTDX for everything else except Q65 so no JTAlert on Q65 unless I use two computers. JTAlert on 6m FT8 is my morning alarm clock during summer Es DX season. :o)

73,  Jay  K0GU


locked Re: Problem with JTAlert 2.16.17

Laurie, VK3AMA
 

On 25/02/2021 9:00 am, Michael Black via groups.io wrote:
Got him fixed -- change him over to 224.0.0.1 on 2237 to loopback device.

Working fine now.

Mike W9MDB
Tnx Mike.
What was wrong with his setup?
He should have still worked even when using the unicast address. The difference in Multicast address shouldn't have mattered or was it that he had the WSJT-X 2.3.0 bug where there was no output interface selected?

de Laurie VK3AMA


locked Re: JTAlert got a 3 page coverage in FUNK Amateur magazine

Paul A. Ramey
 

Glad to see that other are seeing how great your program is and how well you are supporting it!

Congregates Laurie!

--
73 Paul WG0G


locked Re: Problem with JTAlert 2.16.17

Michael Black
 

Got him fixed -- change him over to 224.0.0.1 on 2237 to loopback device.

Working fine now.

Mike W9MDB




On Wednesday, February 24, 2021, 03:44:18 PM CST, Laurie, VK3AMA <hamapps.support@...> wrote:




On 25/02/2021 8:21 am, Norman Heyen wrote:
> Thank you for your input but no success. Nothing appears in the
> JTAlert window. After these changes, now versions 2.16.10 no longer
> works either. It should have been a simple upgrade but seems to have
> eliminated JTAlert from being useful.
> Will uninstall it and try again at some point. But ham radio is a
> hobby, not a vocation. Trying to track down some obscure problem is
> what I did for decades and it is no longer fun.
> Thanks to all for attempting to help but I am done with JTAlert for now.
> Norman


Clearly, more than a JTAlert upgrade has occurred. What other changes
did you make to your software at the time you first upgraded JTAlert?

In previous messages you mentioned DXLab. That could be the issue.

If Multicast UDP doesn't work and unicast is not working, the likely
culprit is that you are trying to use DXLab Spotcollector configured to
work with WSJT-X directly. SpotCollector doesn't support Multicast and
if it is started before JTAlert, it will take exclusive control of the
UDP port (2237 by default), thus preventing JTAlert from receiving
decodes from WSJT-X. Try starting JTAlert and WSJT-X before starting the
DXLab components (Commander is fine).

There may be some evidence in your JTAlert session files as to what is
happening. Please use the "Help" -> "Contact Support" menu, on the main
JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA









locked JTAlert got a 3 page coverage in FUNK Amateur magazine

Gordon Brown
 

Congrats to the JTAlert developer. 3 full color pages in a national Ham magazine. November 2020 edition just landed here and surprised to see the extensive review of JTAlert.


locked Re: Problem with JTAlert 2.16.17

Laurie, VK3AMA
 

On 25/02/2021 8:21 am, Norman Heyen wrote:
Thank you for your input but no success. Nothing appears in the JTAlert window. After these changes, now versions 2.16.10 no longer works either. It should have been a simple upgrade but seems to have eliminated JTAlert from being useful.
Will uninstall it and try again at some point. But ham radio is a hobby, not a vocation. Trying to track down some obscure problem is what I did for decades and it is no longer fun.
Thanks to all for attempting to help but I am done with JTAlert for now.
Norman

Clearly, more than a JTAlert upgrade has occurred. What other changes did you make to your software at the time you first upgraded JTAlert?

In previous messages you mentioned DXLab. That could be the issue.

If Multicast UDP doesn't work and unicast is not working, the likely culprit is that you are trying to use DXLab Spotcollector configured to work with WSJT-X directly. SpotCollector doesn't support Multicast and if it is started before JTAlert, it will take exclusive control of the UDP port (2237 by default), thus preventing JTAlert from receiving decodes from WSJT-X. Try starting JTAlert and WSJT-X before starting the DXLab components (Commander is fine).

There may be some evidence in your JTAlert session files as to what is happening. Please use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA


locked Re: Problem with JTAlert 2.16.17

Norman Heyen
 

Thank you for your input but no success. Nothing appears in the JTAlert window. After these changes, now versions 2.16.10 no longer works either. It should have been a simple upgrade but seems to have eliminated JTAlert from being useful.
Will uninstall it and try again at some point. But ham radio is a hobby, not a vocation. Trying to track down some obscure problem is what I did for decades and it is no longer fun.
Thanks to all for attempting to help but I am done with JTAlert for now.
Norman


On Wed, Feb 24, 2021 at 1:02 PM Laurie, VK3AMA <hamapps.support@...> wrote:


On 25/02/2021 2:12 am, Norman Heyen wrote:
> Thank you for the suggestion Tom,
> But I am still getting the same error message after closing the apps
> and doing a hard reboot of the laptop.
> Open for more suggestions. Just seems there was some change that I
> missed when I went from 2.16.10 to 2.16.17 that is causing this problem.
> Thanks to everyone for all the help,
> Norman

You keep posting about using 127.0.0.1 on port 2237. Clearly that is not
working, likely due to a port sharing problem.
Move to using Multicast UDP as previously advised. see
https://hamapps.groups.io/g/Support/message/33400


de Laurie VK3AMA









locked Re: Issues with PTT not working #FT8

K9MTH@...
 

I was able to get the PPT working as I wanted by changing the PTT settings button to RTS and to CAT in the pull down.  Now to add in JTAlerts.


locked Re: Problem with JTAlert 2.16.17

Laurie, VK3AMA
 

On 25/02/2021 2:12 am, Norman Heyen wrote:
Thank you for the suggestion Tom,
But I am still getting the same error message after closing the apps and doing a hard reboot of the laptop.
Open for more suggestions. Just seems there was some change that I missed when I went from 2.16.10 to 2.16.17 that is causing this problem.
Thanks to everyone for all the help,
Norman
You keep posting about using 127.0.0.1 on port 2237. Clearly that is not working, likely due to a port sharing problem.
Move to using Multicast UDP as previously advised. see https://hamapps.groups.io/g/Support/message/33400


de Laurie VK3AMA


locked Re: Problem with JTAlert 2.16.17

Norman Heyen
 

Thanks Bill,
Unfortunately neither JTAlert or WSJTX (or any of the DX Lab apps) are running in elevated permissions.
Norman


locked Re: Problem with JTAlert 2.16.17

g4wjs
 

On 24/02/2021 15:51, Norman Heyen wrote:
Hi Bill,
I start both WSJT-X and JTAlert from a batch file called from DXLab Suite Launcher. As far as I know, it is not using admin rights.
How could I check that to be certain?
Thanks!
Norman
Hi Norman,

you can check using Windows Task Manager, go to the "Details" tab, click the Name column heading to sort by name, right-click any column heading and click "Select columns", check the "Elevated" option in the list. Find wsjtx.exe and JTAlert.exe, neither should have "Yes" in the elevated column.



--
73
Bill
G4WJS.


locked Re: Problem with JTAlert 2.16.17

Tom Melvin
 

Norman

You could just (under your own ID) run wsjt-x from desktop, then JTAlert from desktop - it will take the batch file and DXLab Suite out of the equation.

The other thing to check if are you running any form of anti-virus it may be blocking activity on 2237 - that should not really have changed if all you did was upgrade JTAlert but no harm in checking

Tom
GM8MJV


On 24 Feb 2021, at 15:51, Norman Heyen <norman.heyen@...> wrote:

Hi Bill,
I start both WSJT-X and JTAlert from a batch file called from DXLab Suite Launcher. As far as I know, it is not using admin rights.
How could I check that to be certain?
Thanks!
Norman


locked Re: Problem with JTAlert 2.16.17

Norman Heyen
 

Hi Bill,
I start both WSJT-X and JTAlert from a batch file called from DXLab Suite Launcher. As far as I know, it is not using admin rights.
How could I check that to be certain?
Thanks!
Norman


locked Re: Problem with JTAlert 2.16.17

g4wjs
 

On 24/02/2021 15:12, Norman Heyen wrote:
Thank you for the suggestion Tom,
But I am still getting the same error message after closing the apps and doing a hard reboot of the laptop.
Open for more suggestions. Just seems there was some change that I missed when I went from 2.16.10 to 2.16.17 that is causing this problem.
Thanks to everyone for all the help,
Norman
Hi Norman,

one way this can happen is if one of WSJT-X and JTAlert is running with Adminstrator rights.



--
73
Bill
G4WJS.


locked Re: Problem with JTAlert 2.16.17

Norman Heyen
 

Thank you for the suggestion Tom,
But I am still getting the same error message after closing the apps and doing a hard reboot of the laptop.
Open for more suggestions. Just seems there was some change that I missed when I went from 2.16.10 to 2.16.17 that is causing this problem.
Thanks to everyone for all the help,
Norman


locked Re: JTAlert with JTDX and WSJT-X at the same time.

neil_zampella
 

FWIW ... I seriously doubt that the clone will include Q65. Q65 is really not meant for HF, and the clone has ripped out anything pertaining to EME, VHF, contests, EME, MS, and so on.

 

Neil, KN3ILZ


locked Re: Problem with JTAlert 2.16.17

Tom Melvin
 

Norman

UN-Tick the 'Resend WSJT-X UDP Packets' in JTalert.

JTA will automatically work out the settings - having that option ticked will cause a loop.

Tom
GM8MJV


On 24 Feb 2021, at 02:56, Norman Heyen <norman.heyen@...> wrote:

Hi Laurie,
These are the two areas I was asking if they should match IP Address and UDP Port

Like I said, everything works well for v2.16.10 but when I updated to 2.16.17 (and a couple prior versions) it doesn't work. I get an error message. 
Windows info is:
Edition Windows 10 Pro
Version 20H2
Installed on ‎11/‎26/‎2020
OS build 19042.804
Experience Windows Feature Experience Pack 120.2212.551.0
 
WSJTx populates and works like it should but the contacts never populate the JTAlert windows

Thanks for any pointers,
Norman


locked Re: Problem with JTAlert 2.16.17

Norman Heyen
 

Hi Laurie,
These are the two areas I was asking if they should match IP Address and UDP Port

Like I said, everything works well for v2.16.10 but when I updated to 2.16.17 (and a couple prior versions) it doesn't work. I get an error message. 
Windows info is:
Edition Windows 10 Pro
Version 20H2
Installed on ‎11/‎26/‎2020
OS build 19042.804
Experience Windows Feature Experience Pack 120.2212.551.0
 
WSJTx populates and works like it should but the contacts never populate the JTAlert windows

Thanks for any pointers,
Norman


locked Re: Problem with JTAlert 2.16.17

HamApps Support (VK3AMA)
 

On 24/02/2021 8:36 am, Norman Heyen wrote:
Should the UDP Port and IP Address in JTAlert match the 2237 and 127.0.0.1 in WSJT-X ? Or have I messed those up as well?


What JTAlert UDP address & port are you referring to? If it is the Resend UDP settings, definitely DON'T change them to match WSJT-X, doing so will create a feedback loop with received UDP messages being sent back to the input ad infinitum.

An alternative to using 127.0.0.1, is to use a multicast IP address, like 239.255.0.1. See the JTAlert Help File, "WSJT-X / JTDX UDP Setup" topic (at root level of the help).
Missing in that help topic is the need to set JTAlert to use multicast on the loopback interface, via the "Settings -> WSJT-X UDP Multicast on Loopback" menu, make sure it is ticked. AND, due to recent changes in WSJT-X 2.3.0 is the need to ensure a loopback outgoing interface is selected in the UDP Server settings.

eg  my WSJT-X setup.

   

de Laurie VK3AMA


locked Re: JTAlert with JTDX and WSJT-X at the same time.

K0GU
 

  Thanks for the reply. I was afraid of that. I'm working on using two computers and making one a JTDX computer and one a WSJT-X computer. If Q65 gets popular enough to be adopted by JTDX in the future that would fix most of my problem.

thanks

73,  Jay  K0GU

3281 - 3300 of 36469