Time_on: 00:00:00.

[va3vf]

I would not call it an error, I prefer to call it an anomaly.

Setup: JTAlert 2.51.0, JTDX, and Log4OM 2 v.2.20.0.0.

If I call a station, and the station returns to another caller, I stop TX.

If the station I called calls me a couple of cycles later, after completing its previous contact, with an R-XX, JTDX will reply with an RR73. The contact is complete, I log it.

The anomaly is, the time_on is logged as 00:00:00. The time_off is correct. Here is the ADIF record:

<call:5>AA0AA <gridsquare:0> <mode:3>FT8 <rst_sent:3>+01 <rst_rcvd:3>-02 <qso_date:8>20220217 <time_on:6>000000 <qso_date_off:8>20220217 <time_off:6>224444 <band:3>80m <freq:8>3.575324 <station_callsign:5>VA3VF <my_gridsquare:4>FN25 <eor>

What this causes is that the contact is placed as the first contact of that day on the Recent QSO's window, like it had actually happened at 00:00:00.

Thanks and 73.

Vince, VA3VF

[N6VH]

Vince,

This might be a JTDX issue. The next time this situation occurs, check the times in the JTDX "Log QSO" box before you click "OK". Does the start time show "00:00:00? If so, it is a JTDX issue.

73,

Jim N6VH

[va3vf]

Vince,

This might be a JTDX issue. The next time this situation occurs, check the times in the JTDX "Log QSO" box before you click "OK". Does the start time show "00:00:00? If so, it is a JTDX issue.

73,

Jim N6VH

Hi Jim,

Yes... it's a JTDX issue. I just adjusted the 'anomaly' to my 'preference'.

I edited Log4OM's Recent QSO table layout by unchecking QSO Date and checking QSO End Date.

Thank you very much for your reply.

73 de Vince, VA3VF

[N6VH]

Vince,

Glad you got it working.

73,

Jim N6VH