I¡¯m using Log4OM based on the youtube tutorial produced by Ant NU1U. At the end of the event I should be able to produce a .adi file that has the following 8 fields that will satisfy LoTW?for a satellite QSO:
Band (tx)
Call
Mode
Propagation Mode (satellite)
QSO Date
Sat name
Submode (in case of FT4)
Time on
It was my understanding going into this that this was an?acceptable way to log for the event. Please let me know asap if not. Thanks!
Ray KN2K
On Friday, July 1, 2022, 5:47 PM, Steve KO4ENU <steveramlogan1@...> wrote:
David,
?
this is what our input interface looks like for SATOPS using TQSL/Logbook of the World.
I have a paper log but I have also been entering in N1MM using the 13 Colonies template (see below image).
In your previous email I know you wanted the logs in Cabrillo format if possible and that is why I went with N1MM. The N1MM is limited to Call, RST, S/P/C, Name (I have been using the name field to input the name of satellite). I agree,
that it is limited by ¡°birdwatching standards¡± it does capture the official exchange for event.
?
Would these N1MM fields satisfy the requirement?
?
What was done last year for satellite logging?
?
?
TQSL/Logbook of the world
?
?
13 Colonies generic interface on N1MM
?
Steve
KO4ENU
Sent from for Windows
?
?
David - Will we (e.g. you) be submitting logs to LoTW in addition to paper QSLs?? If we are also doing LoTW, satellite QSOs are slightly different (they add the "SAT" propagation mode and the "SAT_NAME" fields.? RX Band, freq are optional).
If you need LoTW, one of us satellite ops can send you a sample file to give you an idea of what to expect.??
73 Steve KS1G
