Documentation
Onboarding
Getting Started
Power & Battery
Hardware & Components
Build & Assembly
Radio & RF Design
Frequencies & Regulations
Firmware & Software
USB & Connectivity
GPS & Navigation
Morse & Communication
Modes & Operation
Field Operations & Rescue
Building Effectively
Build Variants
Project & Reference
Docs Morse & Communication Payload Examples

Payload Examples

Edit on GitHub

Real examples of the beacon's Morse payload, from the minimal SOS to the full identity-plus-coordinates transmission.

Payload Examples

The best way to understand the payload format is to read actual transmissions. This page shows the range, from the minimal to the complete.

The format in one line

CODE
SOS DE <IDENTITY> <LATITUDE> <LONGITUDE>

Full details and the field-by-field rules are on Config Payload Format.

Example 1: the minimal emergency

With identity and GPS disabled:

CODE
SOS

Three characters, seconds of airtime, unmistakable. This is the fallback when nothing else is configured (see GPS Failure Contingency).

Example 2: identity added

CODE
SOS DE IK2XYZ

The distress signal plus the callsign: the receiving side now knows WHO. This is the Callsign Identification requirement in its minimal form.

Example 3: the full payload

CODE
SOS DE IK2XYZ 45.8325 6.8650

Identity plus position: the complete report. The coordinates are in decimal degrees, 5 decimals (see GPS Coordinate Systems).

Example 4: the name variant

For the unlicensed builder, the identity can be a name:

CODE
SOS DE MARIO ROSSI 45.8325 6.8650

Only capital letters A-Z and digits transmit (see Config Payload Format), so names are converted to uppercase.

The airtime math

At 12 WPM, the full payload is roughly 30 - 35 seconds of key-down time (see Firmware TX Scheduler for the timing consequences). Keeping the identity short is a battery and duty-cycle decision, not just a style one.