QSL
Confirm a chaser’s contact. When the OTA bot relays a DE message to you,
answer with QSL and that chaser’s callsign. The QSO is logged, scored, and
relayed back to them.
Send the QSL from the same station you started your op from or it won’t be recognized.
Note
Similar to the HOST command, your QSL commands must be sent via RF. Many
APRS software applications like to use APRS-IS to be helpful. Make sure you have yours
configured to send your QSL messages via RF.
Tips and tricks
- You have to provide a callsign, but you can leave the SSID off:
QSL W1XYZis the same asQSL W1XYZ-5.
- Instead of starting with
QSL, you can start with@:
See Make a contact for the whole QSO, step by step.
Reference
QSL <callsign | station> [message...] | @<callsign | station> QSL [message...]
Confirm a chaser's contact and log the QSO.
- callsign | station
- The chaser you are confirming. The SSID is optional, so W1XYZ and W1XYZ-5 both work.
- message
- Free text relayed back to the chaser with the QSL. optional
Replies
qsl_relayDE {station} QSL {message}
Hints
- a QSL not sent via RF
Your QSL for {callsign} must be sent via RF.limited to 2 per minute and 10 per 15 minutes, then silent- a QSL with no op on the air
QSL needs an op on the air. Send HOST to start one.limited to 1 per 24 hours, then silent- a QSL from a different SSID than the op's
Your op is run by {station}. Send QSL from it.limited to 1 per 24 hours, then silent- a QSL with no relayed chase by that operator
No chase from {callsign} to confirmlimited to 1 per 24 hours, then silent- a host naming a chaser who is waiting on their QSL, with no keyword in the message
{callsign} is waiting on your QSL. Send QSL {callsign}.limited to 3 per 15 minutes and 5 per 24 hours, then silent- a QSL with no callsign
QSL needs a callsign. Send QSL callsign to confirmlimited to 1 per 24 hours, then silent