HamLib WSJT-x, JTdx, JTAlert, GridTracker, FT101D, ATAUTO
Posted: 11 Jan 2024, 00:26
OK,
I have no hair left. I just can't seem to get this combination of software to work repeatedly/consistently. I've done a LOT of research and I should be able to have Hamlib be the CAT interface to my FTdx101D thru which all of the other programs communicate. I can verify that hamlib starts up and opens UDP port 4532.
both WSJT-x and JTdx do not consistently broadcast their UDP packets such that JTAlert sees them. despite whatever port number I use. In addition, when WSJT-x and JTAlert ARE working, Log4OM will show the CAT Management-->Hamib; CAT Status: as OFFLINE. Even though the frequency display will follow the radio when I use one of the digital programs to change bands or frequency.
If someone has time to setup a sched of remote session with me to go thru everything and figure out what I'm doing wrong, I'd appreciate it. Just send me an email direct; k7iu.marv@gmail.com
Meanwhile I'll keep playing around with things.
Marv K7IU
I have no hair left. I just can't seem to get this combination of software to work repeatedly/consistently. I've done a LOT of research and I should be able to have Hamlib be the CAT interface to my FTdx101D thru which all of the other programs communicate. I can verify that hamlib starts up and opens UDP port 4532.
both WSJT-x and JTdx do not consistently broadcast their UDP packets such that JTAlert sees them. despite whatever port number I use. In addition, when WSJT-x and JTAlert ARE working, Log4OM will show the CAT Management-->Hamib; CAT Status: as OFFLINE. Even though the frequency display will follow the radio when I use one of the digital programs to change bands or frequency.
If someone has time to setup a sched of remote session with me to go thru everything and figure out what I'm doing wrong, I'd appreciate it. Just send me an email direct; k7iu.marv@gmail.com
Meanwhile I'll keep playing around with things.
Marv K7IU