wrote in message
...
On Mon, 15 Dec 2003 16:05:40 GMT, L. M. Rappaport
wrote:

Well, my last response didn't make it to the newsgroup, so I'll try
again. Basically, I agreed with the others who said there certainly
are awards for satellite qso's, but even if there weren't, the
question still remains:

What is the proper method of logging satellite qso's so they can be
converted to ADIF?

Thanks,

There isn't any proper method. ADIF only supports one frequency field,
so you can't save uplink/downlink frequencies unless you do it in
another field. If your logging program supports the field SAT NAME or
SAT MODE, use those. But don't be surprised if not many programs do
support those fields.

The ADIF spec is he

http://www.hosenose.com/adif/adif.html

73, Jim KH2D


Put your transmit frequency in the frequency field and put the receive
frequency in any available blank field that won't confuse you. The comment
field would be appropriate as you can then indicate not only the frequency
but that it was a satellite contact.

Dee D. Flint, N8UZE

On Mon, 15 Dec 2003 23:11:27 GMT, "Dee D. Flint"
wrote (with possible editing):


wrote in message
.. .
On Mon, 15 Dec 2003 16:05:40 GMT, L. M. Rappaport
wrote:

Well, my last response didn't make it to the newsgroup, so I'll try
again. Basically, I agreed with the others who said there certainly
are awards for satellite qso's, but even if there weren't, the
question still remains:

What is the proper method of logging satellite qso's so they can be
converted to ADIF?

Thanks,

There isn't any proper method. ADIF only supports one frequency field,
so you can't save uplink/downlink frequencies unless you do it in
another field. If your logging program supports the field SAT NAME or
SAT MODE, use those. But don't be surprised if not many programs do
support those fields.

The ADIF spec is he

http://www.hosenose.com/adif/adif.html

73, Jim KH2D


Put your transmit frequency in the frequency field and put the receive
frequency in any available blank field that won't confuse you. The comment
field would be appropriate as you can then indicate not only the frequency
but that it was a satellite contact.

Dee D. Flint, N8UZE

Thanks, folks,

I'll log the transmit frequency and put the receive somewhere
else.
--

73,
Larry W1HJF

On Mon, 15 Dec 2003 23:11:27 GMT, "Dee D. Flint"
wrote (with possible editing):


wrote in message
.. .
On Mon, 15 Dec 2003 16:05:40 GMT, L. M. Rappaport
wrote:

Well, my last response didn't make it to the newsgroup, so I'll try
again. Basically, I agreed with the others who said there certainly
are awards for satellite qso's, but even if there weren't, the
question still remains:

What is the proper method of logging satellite qso's so they can be
converted to ADIF?

Thanks,

There isn't any proper method. ADIF only supports one frequency field,
so you can't save uplink/downlink frequencies unless you do it in
another field. If your logging program supports the field SAT NAME or
SAT MODE, use those. But don't be surprised if not many programs do
support those fields.

The ADIF spec is he

http://www.hosenose.com/adif/adif.html

73, Jim KH2D


Put your transmit frequency in the frequency field and put the receive
frequency in any available blank field that won't confuse you. The comment
field would be appropriate as you can then indicate not only the frequency
but that it was a satellite contact.

Dee D. Flint, N8UZE

Thanks, folks,

I'll log the transmit frequency and put the receive somewhere
else.
--

73,
Larry W1HJF

ARRL requires the following fields for satellite QSOs uploaded to LotW:

1. CALL
2. QSO_DATE
3. TIME_ON
4. MODE
5. FREQ or FREQ_RX
6. FREQ_RX or BAND_RX
7. SAT_NAME
8. PROP_MODE (must be set to SAT)

See http://www.amsat.org/amsat/news/ans2003/ans03292.html for additional
information.

73,

Dave, AA6YQ



"L. M. Rappaport" wrote in message
...
I'm using AALog2, but I think this would apply to any logging program.
How are you supposed to log split band satellite contacts? I did it
by using 144/29 or 432/144 in the band, but they don't validate when
exported as ADIF for sending to LOTW.

Thanks,
--

73,
Larry W1HJF

ARRL requires the following fields for satellite QSOs uploaded to LotW:

1. CALL
2. QSO_DATE
3. TIME_ON
4. MODE
5. FREQ or FREQ_RX
6. FREQ_RX or BAND_RX
7. SAT_NAME
8. PROP_MODE (must be set to SAT)

See http://www.amsat.org/amsat/news/ans2003/ans03292.html for additional
information.

73,

Dave, AA6YQ



"L. M. Rappaport" wrote in message
...
I'm using AALog2, but I think this would apply to any logging program.
How are you supposed to log split band satellite contacts? I did it
by using 144/29 or 432/144 in the band, but they don't validate when
exported as ADIF for sending to LOTW.

Thanks,
--

73,
Larry W1HJF

On Wed, 17 Dec 2003 04:27:04 GMT, "Dave, AA6YQ"
wrote (with possible editing):

ARRL requires the following fields for satellite QSOs uploaded to LotW:

1. CALL
2. QSO_DATE
3. TIME_ON
4. MODE
5. FREQ or FREQ_RX
6. FREQ_RX or BAND_RX
7. SAT_NAME
8. PROP_MODE (must be set to SAT)

See http://www.amsat.org/amsat/news/ans2003/ans03292.html for additional
information.

73,

Dave, AA6YQ

Thank you Dave! Finally, someone who knows the answer. Ok, I guess
the best technique is to export from AALOG2, then edit the ADIF file
before signing.
--

Larry
Email to rapp at lmr dot com

On Wed, 17 Dec 2003 04:27:04 GMT, "Dave, AA6YQ"
wrote (with possible editing):

ARRL requires the following fields for satellite QSOs uploaded to LotW:

1. CALL
2. QSO_DATE
3. TIME_ON
4. MODE
5. FREQ or FREQ_RX
6. FREQ_RX or BAND_RX
7. SAT_NAME
8. PROP_MODE (must be set to SAT)

See http://www.amsat.org/amsat/news/ans2003/ans03292.html for additional
information.

73,

Dave, AA6YQ

Thank you Dave! Finally, someone who knows the answer. Ok, I guess
the best technique is to export from AALOG2, then edit the ADIF file
before signing.
--

Larry
Email to rapp at lmr dot com

Or you could import your ADIF into DXKeeper, which is free, provides the
ability to capture the required fields (e.g. FREQ_RX, BAND_RX, SAT_NAME, and
PROP_MODE), export them for upload to LotW, and (the best part) can
automaticially download QSLs from LotW and update your logged QSOs to
reflect these QSLs. DXKeeper tracks paper, eQSL, and LotW QSLs independently
for each QSO, and generates reports that show progress by "confirmation
kind".

DXKeeper is a member of the freeware DXLab Suite, which includes transceiver
control, rotator control, realtime DX spot collection and analysis, world
map display of the solar terminator and DX spots, propagation forecasting
and monitoring, soundcard PSK31 and PSK63 with broadband decoding, soundcard
RTTY using the MMTTY engine, and QSL route discovery (Pathfinder). All DXLab
applications are free, and available via www.qsl.net/dxlab .

73,

Dave, AA6YQ




"L. M. Rappaport" wrote in message
...
On Wed, 17 Dec 2003 04:27:04 GMT, "Dave, AA6YQ"
wrote (with possible editing):

ARRL requires the following fields for satellite QSOs uploaded to LotW:

1. CALL
2. QSO_DATE
3. TIME_ON
4. MODE
5. FREQ or FREQ_RX
6. FREQ_RX or BAND_RX
7. SAT_NAME
8. PROP_MODE (must be set to SAT)

See http://www.amsat.org/amsat/news/ans2003/ans03292.html for additional
information.

73,

Dave, AA6YQ

Thank you Dave! Finally, someone who knows the answer. Ok, I guess
the best technique is to export from AALOG2, then edit the ADIF file
before signing.
--

Larry
Email to rapp at lmr dot com

Or you could import your ADIF into DXKeeper, which is free, provides the
ability to capture the required fields (e.g. FREQ_RX, BAND_RX, SAT_NAME, and
PROP_MODE), export them for upload to LotW, and (the best part) can
automaticially download QSLs from LotW and update your logged QSOs to
reflect these QSLs. DXKeeper tracks paper, eQSL, and LotW QSLs independently
for each QSO, and generates reports that show progress by "confirmation
kind".

DXKeeper is a member of the freeware DXLab Suite, which includes transceiver
control, rotator control, realtime DX spot collection and analysis, world
map display of the solar terminator and DX spots, propagation forecasting
and monitoring, soundcard PSK31 and PSK63 with broadband decoding, soundcard
RTTY using the MMTTY engine, and QSL route discovery (Pathfinder). All DXLab
applications are free, and available via www.qsl.net/dxlab .

73,

Dave, AA6YQ




"L. M. Rappaport" wrote in message
...
On Wed, 17 Dec 2003 04:27:04 GMT, "Dave, AA6YQ"
wrote (with possible editing):

ARRL requires the following fields for satellite QSOs uploaded to LotW:

1. CALL
2. QSO_DATE
3. TIME_ON
4. MODE
5. FREQ or FREQ_RX
6. FREQ_RX or BAND_RX
7. SAT_NAME
8. PROP_MODE (must be set to SAT)

See http://www.amsat.org/amsat/news/ans2003/ans03292.html for additional
information.

73,

Dave, AA6YQ

Thank you Dave! Finally, someone who knows the answer. Ok, I guess
the best technique is to export from AALOG2, then edit the ADIF file
before signing.
--

Larry
Email to rapp at lmr dot com

On Wed, 17 Dec 2003 23:23:20 GMT, "Dave, AA6YQ"
wrote (with possible editing):

Or you could import your ADIF into DXKeeper, which is free, provides the
ability to capture the required fields (e.g. FREQ_RX, BAND_RX, SAT_NAME, and
PROP_MODE), export them for upload to LotW, and (the best part) can
automaticially download QSLs from LotW and update your logged QSOs to
reflect these QSLs. DXKeeper tracks paper, eQSL, and LotW QSLs independently
for each QSO, and generates reports that show progress by "confirmation
kind".

DXKeeper is a member of the freeware DXLab Suite, which includes transceiver
control, rotator control, realtime DX spot collection and analysis, world
map display of the solar terminator and DX spots, propagation forecasting
and monitoring, soundcard PSK31 and PSK63 with broadband decoding, soundcard
RTTY using the MMTTY engine, and QSL route discovery (Pathfinder). All DXLab
applications are free, and available via www.qsl.net/dxlab .

73,

Dave, AA6YQ

Again, thank you! As it turned out, I had a copy (older, version 2)
of DXKeeper. I'll follow your advice. In fact, I perhaps should have
a closer look at DXKeeper and the rest of the suite as it seems to
have surpassed AALOG2 at this point.
--

73,
Larry W1HJF