If, as you say, there are no decoded callsigns appearing the UDP BandMap, then it is possible/probable that Logger32 and JTDX (or whatever) are not talking to each other by UDP messages. One of the numerous messages is the all important 'Log this contact' message.
?
You should probably check that the UDP port in JTDX (or whatever) and Logger32 are both open, and they are both using?the same port #. You could also look at the UDP port debug window to see in JTDX (or whatever) is talking to Logger32.
?
SeventyThree(s).
On 02/28/2025 8:44 AM EST Ron Rushton via groups.io <cqdxer@...> wrote:
?
?
?
Sorry about ?little information , the call signs don¡¯t show up in the band map panel and I also checked the tcp/adif is and it was unchecked Bob, ?every thing working on the 26th of Feb and nothing was installed on or after shutdown my evening time, using windows 10 pro and to be honest I¡¯ve had this as the only issue in a hell of a while
?
Ron G6GA
On 27 Feb 2025, at 7:49?pm, Bob via groups.io <k4cy@...> wrote:
Precious little information ....I'll assume you're using UDP logging. I'll further assume the Logger32 UDP BandMap is alive as well, and showing decoded stations callsigns.
?
If my assumptions are correct, then on the UDP BandMap click CONFIG. Click LOGGING OPTIONS. Make sure the TCP/ADIF LOGGING option is UNchecked. If it is checked, it turns UDP logging off.
?
SeventyThree(s).
On 02/27/2025 2:36 PM EST Ron Rushton via groups.io <g6ga@...> wrote:
?
?
Anyone had any problems today as regard to logging FT8 and FT4 qso¡¯s direct into to logger32
none of qso¡¯s were logged into my logbook using?
JTDX WSJTX luck has if the went info there respective logbooks. Everything worked as normal yesterday nothing added today or removed?
73 Ron G6GA
