QSO dates missing in HRD from JTAlert UDP/2333 #HRD


Ronald Panetta
 

I encountered the same issue recently posted by David over a year ago here: https://hamapps.groups.io/g/Support/message/26679?p=,,,20,0,0,0::relevance,,hrd+udp+2333,20,2,0,67711266. Reference his screen snapshot in his post. 

I opened a ticket with HRD and they're position is this is a JTAlert issue. Here is their latest response "We only Support UDP Logging from N1MM and WSJTX not JTAlert, it has its own defects. Since QSO Forward works perfect for the 1st 2 there is an issue in JTALert."

I have captured via Wireshark the UDP/2333 packet generated by JTAlert as part of the fault isolation. The data portion of the packet is as follows: 

<CALL:5>K7RQN<QSO_DATE:8>20210111<TIME_ON:6>225145<TIME_OFF:6>225315<FREQ:9>14.075683<FREQ_RX:9>14.075683<BAND:3>20m<BAND_RX:3>20m<MODE:3>FT8<RST_SENT:3>-05<RST_RCVD:3>-08<LOTW_QSL_SENT:1>R<LOTW_QSL_RCVD:1>R<EQSL_QSL_SENT:1>R<EQSL_QSL_RCVD:1>R<STATE:2>AZ<CQZ:1>3<ITUZ:1>6<PFX:2>K7<CONT:2>NA<DXCC:3>291<COUNTRY:13>United States<GRIDSQUARE:4>DM33<DISTANCE:4>3353<A_INDEX:2>12<K_INDEX:1>4<SFI:2>73<COMMENT:25>FT8 Sent: -05 Rcvd: -08<MY_GRIDSQUARE:6>FN13VD<MY_CQ_ZONE:1>5<MY_ITU_ZONE:1>8<STATION_CALLSIGN:6>WB2WGH<QSO_COMPLETE:1>Y<EOR>

Anyone have a solution? Is this an HRD or a JTAlert issue? Versions as follow:
WSJT-X v2.2.2
JTAlert, v2.16.17
HRD Logbook v6.7.0.323
 

Thanks in advance, 
Ron WB2WGH

Join Support@HamApps.groups.io to automatically receive all group messages.