ADIF TIME_ON/TIME_OFF

Moderator: DL7UCX

Antworten
YO5LD
Beiträge: 9
Registriert: Freitag 23. Dezember 2016, 21:35

ADIF TIME_ON/TIME_OFF

Beitrag von YO5LD »

Hello,

I think there is an issue with the QSO import from MSHV/WSJT/JTDX, mostly concerning Meteor-Scatter QSOs.
There are two fields in the ADIF, TIME_ON, TIME_OFF. These are correctly imported into UCXLog.
The bad thing is that when I do a LoTW export, TIME_ON is used rather than TIME_OFF.
This is only concerning Meteor-Scatter QSOs which could easily be longer than 15 minutes and LoTW or other QSL platforms won't match the QSO.

I think the correct way is to export the Clublog/eqsl/LoTW QSOs with "TIME_OFF" rather than "TIME_ON".

Thanks,
Dani
YO5LD
Benutzeravatar
DL7UCX
Beiträge: 6000
Registriert: Donnerstag 8. August 2002, 19:23
Wohnort: Dabendorf
Kontaktdaten:

Re: ADIF TIME_ON/TIME_OFF

Beitrag von DL7UCX »

Hello Dani,

How do you import the ADIF file from WSJT ?
The automatic background import by "Settings - Station - Other interfaces - WSJT ADIF log"
sets "end time :arrow: begin time" because of possible large time differences from WSJT.
LOTW should tolerate time difference up to 30 minutes.

73 Ben
YO5LD
Beiträge: 9
Registriert: Freitag 23. Dezember 2016, 21:35

Re: ADIF TIME_ON/TIME_OFF

Beitrag von YO5LD »

Hello Ben,

I'm using simple ADIF imports because I'm running these programs on different computers, often remote.
I don't think end time :arrow: begin time is a correct way of modifying, rather the "QSO" should be confirmed at the end time (so begin time :arrow: end time). We write the end time to the QSL card, rather than the begin time :)
What is the idea behind using the begin time in LoTW exports? :)
Often 2m (or even 70cm) meteorscatter QSOs can take more than 30 minutes.

Thanks,
Dani
YO5LD
Benutzeravatar
DL7UCX
Beiträge: 6000
Registriert: Donnerstag 8. August 2002, 19:23
Wohnort: Dabendorf
Kontaktdaten:

Re: ADIF TIME_ON/TIME_OFF

Beitrag von DL7UCX »

Hello Dani,
I don't think end time :arrow: begin time is a correct way of modifying
Possibly I have explain it more clearly:
Some user WSJT-X observed that the begin time was set at the first try to start the QSO.
But then it can need a long time to get the confirmation of the QSO.
Example:
WSJT sets in FT8 the BeginTime = 20:00
QSO was confirmed at EndTime = 20:09
Real QSO duration in FT8 is not longer than 1 minute.
So the "truly begin time" of the QSOs is 20:08 or 20:09.
Therefore UcxLog sets the BeginTime to 20:09.
What is the idea behind using the begin time in LoTW exports?
The idea is to avoid trouble and so to do exactly the same like TQSL.
If you use the TQSL ADIF editor, it asks for "UTC Time".
If you enter 20:09 it will generate an ADIF field <TIME_ON:6>200900

73 Ben
Antworten