Date   

locked Re: 2.50.3 problems

Dave Miller
 

Hi Laurie, thanks for the updated version. All worked great after just installing over the old version. The new features are really good - thanks for some great software!

73 Dave G6AWF


locked Re: ATNO #JTDX

Jim N6VH
 


On 7/30/2021 11:17 AM, Inbody, Don via groups.io wrote:
Is a special alert for an ATNO in the works? The ATNO (regardless of band or mode) would be most helpful.

73, Don AD0K
EM10bc
Buda, TX
_._,_._,_


Don,

Will this do what you want? See attached.

Settings - Alerts - DXCC

73,

Jim N6VH


locked Re: .net

HamApps Support (VK3AMA)
 

On 30/07/2021 9:56 pm, Keith Lynn wrote:
I'm loading jt alert for the first time. It keeps asking for .net 5.0. I have downloaded it several times. It still says I need to download .net 5.0. I have no idea what's wrong with it

Keith
Kc3ndu

You need to install the "DESKTOP" version of the .NET runtime.
Also the architecture type needs to match that of the JTAlert installer, both need to be X64 for 64bit Windows or X86 for 32bit Windows.

see this pinned message. https://hamapps.groups.io/g/Support/message/35794

de Laurie VK3AMA


locked ATNO #JTDX

Inbody, Don
 

Is a special alert for an ATNO in the works? The ATNO (regardless of band or mode) would be most helpful.

73, Don AD0K
EM10bc
Buda, TX


locked .net

Keith Lynn
 

I'm loading jt alert for the first time. It keeps asking for .net 5.0. I have downloaded it several times. It still says I need to download .net 5.0. I have no idea what's wrong with it

Keith
Kc3ndu


locked Re: JTAlert , WSJT-X and HRD v 6.7.0.357 trying to log FT4 contacts

Jim Nortron
 

My HRD shows the sub mode (grayed out) as FT4 while the mode is MFSK. If you submit the mode of FT4 to LoTW, it will reject the QSO and never get confirmed. Experience speaking here. Once I resubmitted, as MFSK, it immediately confirmed all my FT4 contacts. WD4T 


locked Re: JTAlert , WSJT-X and HRD v 6.7.0.357 trying to log FT4 contacts

ZF1RC Roger
 

It wasn't showing the sub mode which I discovered was because HRD Log needed to be updated to include an additional column. Once that was done everything functions as expected.
Thanks for your support of JTAlert.

73 Roger ZF1RC


locked Re: JTAlert and WSJTX in linux

Adrian Fewster <vk4tux@...>
 

Yes if the IP could also be set. It would be good, These type programs run great under crossover in linux.

If a manual/auto option was added at install, it could provide the option, under applications > wsjtx, where the fwd rx traffic port config exists, to add the main porting config.


vk4tux

On 31/7/21 12:02 am, Don Melcher wrote:
Wouldn’t making the UDP port configurable also allow JTAlert running on a Windows PC to connect to an instance of WSJT-X on another - no matter what system WSJT-X is running under?
--
Don
W6CZ
DM07


locked Re: JTAlert and WSJTX in linux

Don Melcher
 

Wouldn’t making the UDP port configurable also allow JTAlert running on a Windows PC to connect to an instance of WSJT-X on another - no matter what system WSJT-X is running under?
--
Don
W6CZ
DM07


locked Re: JTAlert and WSJTX in linux

Adrian Fewster <vk4tux@...>
 

Laurie, Just to be clear JTAlert is running on the same debian 10 PC under crossover (advanced version of wine with excellent NET support).

So for this to be successful the process detection requirement would need to be disabled and the UDP port configurable.

If that was possible it would work wonderfully in this combination. I have read others linux blogs on issue trying to use JTalert under linux in emulator software,

and see now why they said it did not work out. They usually turn to gridtracker which is supported in linux directly.

If there is an accessible file or register IU can modify to let it work , that would be wonderful. I am very sure it is possible.

I run also windows HRD under crossover with linux wsjtx for FT-897 HRD selection cat bridging via DDE etc,  and other localhost porting, and it all works great.


Thankyou


vk4tux

On 30/7/21 6:35 am, HamApps Support (VK3AMA) wrote:
On 29/07/2021 8:23 pm, Adrian Fewster wrote:
I have JTAlert installed under crossover in debian 10 and also have linux wsjtx 2.5.0rc3 running.
JTAlert is waiting to see wsjtx to start before it will continue startup.
What is the detection method please, as I thought the udp port activity may have been the trigger ?

73

vk4tux

JTAlert will trigger on detected UDP activity, BUT to do that JTAlert has to know on what UDP port to listen. It determines the port automatically by examining the config file of detected WSJT-X instances. To know which config file to read JTAlert has to know if WSJT-X was started with a --rig-name parameter or not, it does this by examining the command-line used to start a detected WSJT-X instance. JTAlert enumerates the processes on the JTAlert PC looking for running WSJT-X instances. JTAlert will not find the Debian WSJT-X process because it is not running on the JTAlert PC.

de Laurie VK3AMA


locked Re: Issue with JTAlert v2.50.4

HamApps Support (VK3AMA)
 

On 30/07/2021 10:34 am, KI4RFM wrote:
Hey Laurie,

Just wanted to let you know that I haven't had anymore issues with JTAlert since removing the Asus GameFirst service. I have it completely uninstalled now so it shouldn't create anymore issues. Turns out it was network traffic optimization tool so that would probably explain why it was causing issues with the UDP connection.

Hopefully this may help out anyone else that has an Asus laptop with this same software.

Thanks
Jacob KI4RFM

Tnx for the update.

de Laurie VK3AMA


locked Re: Empty Callsign box

HamApps Support (VK3AMA)
 

On 30/07/2021 11:20 am, Jim Johnson KC4HW wrote:
GE all.  I have been following this thread for the last couple of days.  I too was having trouble with JTAlert populating it boxes.  I followed the instructions below very carefully and it still did not work. 
 
So, today I looked in N3FJP and under the Setting, Application Program Interface (API)... brings up a N3FJP APR 1.7 dialog and in the middle of this dialog with a title "WSJT-X Interface", and a check in the Listen for WSJT-X I selected the button Configure.  It brought up another WSJT Configuration Dialog and found that the IP was set to the 127.0.0.1 IP address, I changed it to 224.0.0.1 and then clicked Done at the bottom and all started working in my installation. 
 
Finally, I after it ran for a few minutes, I rebooted the computer and then restarted everything and it is still working.  So it appears that I have stumbled into the solution that fixed the problem that existed in my setup.  Your mileage may vary. 
 
Jim/KC4HW

Setting WSJT-X to use Multicast UDP and switching ACLog to use the Multicast IP is the only way to have both JTAlert and ACLog work with WSJT-X concurrently. With ACLog set to use 127.0.0.1, a non-multicast address, was causing ACLog to take exclusive control of the UDP port thus preventing JTAlert from receiving UDP traffic from WSJT-X. Multicast is the only way to have multiple concurrent applications working with WSJT-X. JTAlert doesn't require any IP address setting changes (there are none) as it automatically uses the correct IP address.

de Laurie VK3AMA


locked Re: Empty Callsign box

Jim Johnson KC4HW
 

GE all.  I have been following this thread for the last couple of days.  I too was having trouble with JTAlert populating it boxes.  I followed the instructions below very carefully and it still did not work. 
 
So, today I looked in N3FJP and under the Setting, Application Program Interface (API)... brings up a N3FJP APR 1.7 dialog and in the middle of this dialog with a title "WSJT-X Interface", and a check in the Listen for WSJT-X I selected the button Configure.  It brought up another WSJT Configuration Dialog and found that the IP was set to the 127.0.0.1 IP address, I changed it to 224.0.0.1 and then clicked Done at the bottom and all started working in my installation. 
 
Finally, I after it ran for a few minutes, I rebooted the computer and then restarted everything and it is still working.  So it appears that I have stumbled into the solution that fixed the problem that existed in my setup.  Your mileage may vary. 
 
Jim/KC4HW
 

----- Original Message -----
From: HamApps Support (VK3AMA) <vk3ama.ham.apps@...>
Sent: 7/28/2021 10:43:43 PM
Subject: Re: [HamApps] Empty Callsign box

If the Callsigns window is not being populated it will be because JTAlert is not receiving UDP traffic from WSJT-X. The same applies to JTAlert not showing the logging confirmation window, if it never sees the UDP logging message it wont log to ACLog and will not display a confirmation/failure popup because it didn't perform the logging as it was unaware that WSJT-X logging took place.

It sounds like you have WSJT-X set for unicast UDP, using 127.0.0.1 on port 2237 (the default values) and that ACLog has taken exclusive control of the UDP port effectively locking JTAlert out because it was started before JTAlert.

If you want to have both ACLog and JTAlert working with WSJT-X concurrently, you need to have WSJT-X configured to use multicast UDP. Use the JTAlert "Help -WSJT-X UDP Setup" menu to bring up the relevant section in the help file, it contains very simple 4 step instructions with pictures on how to enable multicast UDP in WSJT-X.

de Laurie VK3AMA


locked Re: Issue with JTAlert v2.50.4

KI4RFM
 

Hey Laurie,

Just wanted to let you know that I haven't had anymore issues with JTAlert since removing the Asus GameFirst service. I have it completely uninstalled now so it shouldn't create anymore issues. Turns out it was network traffic optimization tool so that would probably explain why it was causing issues with the UDP connection.

Hopefully this may help out anyone else that has an Asus laptop with this same software.

Thanks
Jacob KI4RFM


locked Re: JTAlert and WSJTX in linux

Jim Nortron
 

Speaking for myself only, in the JTAlert Settings I copy, then paste the command line from wsjtx or JT dx,  which ever you prefer, from that’s programs startup icon properties to JTAlerts Applications Auto-Start item. Then I put a tick in the Start box and the Close box. Mine reads, C:\JTDX\156\bin\jtdx.exe I hope this helps. WD4T 


locked Re: JTAlert and WSJTX in linux

HamApps Support (VK3AMA)
 

On 29/07/2021 8:23 pm, Adrian Fewster wrote:
I have JTAlert installed under crossover in debian 10 and also have linux wsjtx 2.5.0rc3 running.
JTAlert is waiting to see wsjtx to start before it will continue startup.
What is the detection method please, as I thought the udp port activity may have been the trigger ?

73

vk4tux

JTAlert will trigger on detected UDP activity, BUT to do that JTAlert has to know on what UDP port to listen. It determines the port automatically by examining the config file of detected WSJT-X instances. To know which config file to read JTAlert has to know if WSJT-X was started with a --rig-name parameter or not, it does this by examining the command-line used to start a detected WSJT-X instance. JTAlert enumerates the processes on the JTAlert PC looking for running WSJT-X instances. JTAlert will not find the Debian WSJT-X process because it is not running on the JTAlert PC.

de Laurie VK3AMA


locked Re: Empty Callsign box

HamApps Support (VK3AMA)
 

On 29/07/2021 11:29 pm, Gilles beaulieu wrote:
Would you have any idea why the callsign window is always blank

That is because you still are not using UDP Multicast.

de Laurie VK3AMA


locked Re: Decode line not appearing after upgrade to 2.50.4

Laurie, VK3AMA
 

On 30/07/2021 2:03 am, Robin WA7CPA wrote:
Realized I had downloaded wrong version of new .net platform. I had downloaded console version, not desktop version. Downloading correct .net platform solved everything
This is why in all my messages, release notes & help files, I deliberately use the word "Desktop". Not much more I can do if that advice goes unheeded or ignored.

de Laurie VK3AMA


locked Re: Empty Callsign box

Laurie, VK3AMA
 

On 30/07/2021 12:51 am, Jim Cooper wrote:
I am surprised nobody has mentioned it yet,
but the screen shot you posted clearly shows
you are NOT using the multicast setup ... you
are using the 127.0.0.1 address and that is
causing you the problems
Sorry Jim, you're incorrect.

The first reply (mine) to the initial post in the thread advised setting up multicast UDP along with instructions on how to find the setup instructions.

Subsequent messages shows that the OP is still using unicast UDP (127.0.0.1) resulting in JTAlert being locked out by ACLog taking exclusive control of the UDP Server port.

de Laurie VK3AMA


locked Re: Empty Callsign box

Laurie, VK3AMA
 

On 29/07/2021 10:51 pm, Gilles beaulieu wrote:
Hi Laurie, I think I have followed the steps you mentioned but still no further ahead. The problem still persist. If ACLog starts first and locks everything like you mentioned, is there a way that I could "unlock" it so that it would work? Just a thought.
I'm also sending you a pic, maybe you can figure it out.
Thanks
Gilles VE3NPI
It is not working since you didn't follow the setup advice. You have not setup UDP Multicast in WSJT-X. Without doing that you cannot have ACLog and JTAlert concurrently working.

While you continue to use unicast UDP (127.0.0.1) and start ACLog first JTAlert will be locked out. Eithe setup Multicast UDP in WSJT-X OR turn off the WSJT-X  integration in ACLog.

de Laurie VK3AMA

2161 - 2180 of 38532