Log4OMV2 2.29.0.0 UDP Coms

[W4KCM]

Log4OMV2 not processing QSO

New install of all new programs on a new computer.
Net 6 Runtime installed and confirmed.

Computer OS Windows 10 Pro
Intel I7 137000 KF CPU - not overclocked (yet)
2 Solid State Drives
990 Pro 1 TB PCLe 4
870 1 TB PCLe 3
One SATA Hard Drive 2 TB

All COM ports are USB, all ports/hubs have a power plan to never sleep.

Log4OMV2 is running as administrator. The associated programs, WSJT-X, JT Alert, and PST Rotator are not running as administrator.

What I think I know:

I tried to install all of the Ham programs on the PCle 4 solid-state drive. I'm sure some of the information and directories will have to be sorted out between the drives.

The QSO information from JT Alert is arriving at Log4OM via UDP 2236 but the process stops and the QSO is not logged to Log4OM.

Greater details:

My WSJT-X 2.6.1 communicates on UDP 2237 (default port) with JT Alert and Log4OM as the callsigns selected by a left click in WSJT-X will auto-populate in the appropriate fields in each of the programs. JT Alert will display additional information for the callsign after the look-up is completed.

My JT Alert 2.60.10 is set to UDP Port 2236, Remote control port is set to 2241 (Default) and also enabled. Under Manage Settings, Logging - I have increased the delay timer to 30 seconds before checking on the logging success. I have set up JT Alert as shown in the current help files of JT Alert (five steps - some in Log4OM and some in JT Alert) to configure the logging UDP Ports. All the associated reporting checkboxes are checked in WSJT. I do not rebroadcast any info by use of a proxy server.

My Log4OMV2 2.29.0.0, Under Settings / Configurations / Software / Connections, Inbound UDP Port Tab is set to WSJT Alert Message on port 2236

The diagnostic Tab in Log4OM confirms that UDP Ports 2236 and 2241 are both open. Netstat also shows ports 2236, 2237, and 2241 as UDP, with no other designation as listening or otherwise.

When I log a contact (see the log file from Log4OMV2 below) in this case WD4KCN, there is an error message "cannot confirm contact was logged but is available in the ...." generated after a few seconds, and after waiting for 60 seconds - there is not a log entered into Log4OM. The working database is a SQ.lite

Example follows: WD4KCN was logged at 17:03:10 2023/10/02

L4OM V2 Log file below is in Debug / UDP Logging Enabled: level.

2023-10-02 17:03:10.0422 DEBUG: [dje_z5N35MTKBA8R2KGTAKPJ4XTN2R26Q_ejd][MoveNext] : ##### UDP MESSAGE RECEIVED ##### : JTAlert<EOH>

<CALL:6>WD4KCN<QSO_DATE:8>20231002<QSO_DATE_OFF:8>20231002<TIME_ON:6>170300<TIME_OFF:6>170300<FREQ:9>28.075767<FREQ_RX:9>28.075767<BAND:3>10m<BAND_RX:3>10m<MODE:3>FT8<DXCC:3>291<COUNTRY:13>United States<CQZ:1>5<ITUZ:1>8<CONT:2>NA<RST_SENT:2>00<RST_RCVD:2>00<COMMENT:14>FT8 Rcvd: -20<PFX:3>WD4<A_INDEX:1>9<K_INDEX:4>1.67<SFI:3>161<MY_GRIDSQUARE:6>EM95XL<MY_CQ_ZONE:1>5<MY_ITU_ZONE:1>8<OPERATOR:5>W4KCM<STATION_CALLSIGN:5>W4KCM<QSO_COMPLETE:1>Y <EOR>
on UDP port 2236 (INCOMING JT MESSAGE/JT_MESSAGE) from 127.0.0.1:63550 #####

2023-10-02 17:03:10.0422 DEBUG: [dje_zFLNKT3A92LGYUEUF7285229LTF6A_ejd][MoveNext] : JTAlert<EOH> <CALL:6>WD4KCN<QSO_DATE:8>20231002<QSO_DATE_OFF:8>20231002<TIME_ON:6>170300<TIME_OFF:6>170300<FREQ:9>28.075767<FREQ_RX:9>28.075767<BAND:3>10m<BAND_RX:3>10m<MODE:3>FT8<DXCC:3>291<COUNTRY:13>United States<CQZ:1>5<ITUZ:1>8<CONT:2>NA<RST_SENT:2>00<RST_RCVD:2>00<COMMENT:14>FT8 Rcvd: -20<PFX:3>WD4<A_INDEX:1>9<K_INDEX:4>1.67<SFI:3>161<MY_GRIDSQUARE:6>EM95XL<MY_CQ_ZONE:1>5<MY_ITU_ZONE:1>8<OPERATOR:5>W4KCM<STATION_CALLSIGN:5>W4KCM<QSO_COMPLETE:1>Y <EOR>
2023-10-02 17:03:13.0578 DEBUG: [dje_zY6YQMNBVT6RMWXFNBVDARQZ5TKJMC485GS_ejd][MoveNext] : Performing QSO search on callsign N6ACA
2023-10-02 17:03:13.0578 DEBUG: * [Countries][SearchCallsign][13396 ms] : Performing Search Callsign on call N6ACA on date 10/2/2023 5:03:13 PM

The message appears to have arrived at Log4OM on UDP 2236 but the QSO was not processed.

I have spent days trying to figure this out. I have been a LOG4OM user for several years and never experienced something this difficult to troubleshoot.

Any and all advice would be welcomed.

Thanks guys,
Jim Austin
W4KCM

[m0fox]

I'm just revisiting the group after a year, I'm using log4om, Grid Tracker and WSJTX. All have been running 100% for the last year until several days ago.
After several hours playing FT8 I realised Log4om had stopped logging and hasn't since. Reinstalled it several times, went back to Win10 still the same, back to Win11 no go, went back a couple of versions...same out come.
CAT and lookup works fine, just no longer reads via the UDP ports, new settings, old settings tried everything....Gridtracker is working fine with WSJTX, does all the external logging etc, i'm stuck now....3 days of trying everything i can think of...still a no go for me

[KI5IO]

All is spelled out in the Release Notes from V 2.27.0.0 forward.

You have to REMOVE your old/current UDP Inbound connections and build new ones.

Be sure you first make note of the ports you are using as you will use those same ports as you assemble the new UDP Inbound Ports.

Take a look here: https://forum.log4om.com/viewtopic.php?t=8260

and here: https://forum.log4om.com/viewtopic.php?t=8690

[m0fox]

For some reason the settings used previously decided NOT to work and as I'd gone back to Win10 and then back to win11 the UDP connections had to be renewed.

So late last night I went back to watching K0PIR videos and used his settings exactly - YESSSSSS success at last, he also made the point of starting the programs in order - WSJT>LOG4OM>GRIDTRACKER, not sure if its important but whatever works....

I'll attach my settings (K0PIR) just in case it helps anyone else that's struggling

Cheers All

[m0fox]

Not sure if this JPG loaded previously

[W4KCM]

Thanks to Nolan, KI5IO - we are back in business. All programs now function as designed and the UPD debacle has been resolved. I did see the warning that Terry put up concerning how the different applications now interface with version 2, starting in 2.27.0 but in the fog of building a new computer and the massive brain load, I didn't grasp all that I needed to be successful. It has been a long time since I set up all the programs and as a true OM, forgot to consider that all things change. The best advice for anyone experiencing an issue is to read the current manual - again.
Thanks again,

Jim,
W4KCM