While developing my mapping program, I have discovered some
inconsistencies in the ALL.TXT file format. The entry for a local
transmission looks like this:
1308 Transmitting 18.104 MHz JT9: CQ KB1EHD EL99
While the received version of a similar message looks like this:
1400 -9 -0.4 1315 # CQ PY1FR GG87
1. The "Transmitting" message gives the dial frequency rather than the
audio
offset freqeuency. So there is no record of the exact
frequency
of transmission, which makes it difficult to match up with
later
'received' messages. For received messages, the actual signal
frequency
can be obtaied by adding the audio offset (1315 in the second
example)
to the dial frequency from an earler date-stamp/mode message.
2. The "Transmitting" message encodes the mode with a string like
"JT9"
rather than "@" or "#".
I hope to eventually be able to track the progress of individual QSOs,
and it
is currently impossible to analyze a message like the following without
being able to place it precisely within a QSO by matching time AND
frequency:
1409 -1 0.3 455 # ZF1EJ F6ECI RR73
That could either be F6ECI ending a QSO with a "Roger and 73", or
responding
to a CQ with "I am at grid square RR73, somewhere in the Arctic Ocean
north of Eastern Siberia".
Would there be any big problem if the format of a transmission as
recorded in ALL.TXT was more like the received format, with an "X" in
the dB column to
distinguish the two:
1308 X 0.0 1315 @ CQ KB1EHD EL99
------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
