On 01/27/2016 01:47 AM, Yannick DEVOS (XV4Y) wrote:
Hi Yannick and all,
> That's right John. While ADIF does not specify any require field
> because it wants to stay "open" and able to carry any radio related
> data,
This is a big problem with ADIF. The specification is imprecise and
incomplete
On 01/27/2016 12:31 AM, John Nogatch wrote:
Hi John,
> When I tried uploading QSO data which had only TIME_OFF and without
> TIME_ON, LoTW incorrectly recorded the QSO time as 00:00.
This is a wrong behavior because an absent information cannot be
replaced by a value of zero.
Best 88 de Claude
Hi,
That's right John.
While ADIF does not specify any require field because it wants to stay "open"
and able to carry any radio related data, the norm for logging related software
is to use time_on as the QSO time, non withstanding it really being the end of
start of the QSO.
By default, most
On Tue, Jan 26, 2016 at 10:36 AM, Claude Frantz
wrote:
> On 01/26/2016 02:52 PM, Michael Black wrote:
...
>> The ADIF logging from WXSJT-X inserts TIME_ON which is really TIME_OFF.
>> Should be easy enough to add a start time with either a transmitted CQ or
>> Tx 1 message or 1st message received
On 01/26/2016 02:52 PM, Michael Black wrote:
> Have we discussed this before?
I cannot remember.
> The ADIF logging from WXSJT-X inserts TIME_ON which is really TIME_OFF.
> Should be easy enough to add a start time with either a transmitted CQ or
> Tx 1 message or 1st message received with your
Have we discussed this before?
The ADIF logging from WXSJT-X inserts TIME_ON which is really TIME_OFF.
Should be easy enough to add a start time with either a transmitted CQ or
Tx 1 message or 1st message received with your call sign which gets reset
to zero after loggin.
If start_time is not set
