Pricing
Free public developer tool

Payload Optimizer Tool

Turn readable sensor values into compact, bit-packed satellite telemetry messages. Define your fields, preview the exact hex, and generate an editable C payload builder.

Local encoding and decodingBit-level packingEditable C output
Current example
21 bytes
SBD limit
340 bytes
Certus limit
100,000 bytes
0x5dbe258bf867204bffcb742554f592d3031301ff10

Build locally. Save your configuration when ready.

Field definitions, example values, generated hex, and C code are calculated locally. Download a JSON file to keep your work or load it again later. If you choose to email your configuration, your email address, name (optional), saved fields, and code are sent to Telemetry Station to deliver that email.

No account requiredJSON save and restore
Ordinary page requests may still produce standard infrastructure logs as described in the Privacy Policy.
1 · Choose a transport

Set the payload limit

The optimizer checks both your example message and the worst-case field sizes against the selected Iridium transport.

2 · Define the message

Configure payload fields

Fields are encoded from top to bottom. Reorder them deliberately: a future parser must use this same schema and order.

Integers: value or length firstEnter an example to calculate its smallest length in the selected unit. Finish editing the length to generate a random valid value. The allowed range appears below each field.
Decimals: value or range firstEnter a decimal to infer a range and precision, or define your own range, accuracy, or length to generate an example. Inferred sizes fit this sample; choose bounds for future readings.
Text and bytes: value or cap firstAn example sets the content cap. Finish editing a cap to create a random example within it. The total includes a length prefix.
1
Latitude
latitude · Decimal / float
Example value
32.87051
Encoding
25 bits
Status
Ready
2
Longitude
longitude · Decimal / float
Example value
-117.24103
Encoding
26 bits
Status
Ready
3
Message sequence
message_sequence · Unsigned integer
Example value
37
Encoding
12 bits
Status
Ready
4
Temperature (tenths °C)
temperature_tenths_c · Signed integer
Example value
-27
Encoding
16 bits
Status
Ready
5
GPS fix
gps_fix · Boolean
Example value
true
Encoding
1 bit
Status
Ready
6
Device ID
device_id · ASCII text
Example value
BUOY-01
Encoding
100 bits
Status
Ready
7
Diagnostic bytes
diagnostic_bytes · Raw bytes
Example value
01ff10
Encoding
68 bits
Status
Ready

Decode · Inspect · Integrate

From hex to sensor values.

Paste the application payload from your firmware to inspect every field in definition order. Decoding uses the fields above and runs entirely in your browser.

Load a saved schema ↑

Accepts a leading 0x, spaces and newlines. Paste payload bytes only, without transport headers. Changing the schema reinterprets these bytes; use the exact schema used by the sending firmware.

Decoded 7 fields · 168 data bits · 0 zero padding bits

Byte inspector

21 bytes

Select a field below to highlight its bytes, including its length prefix. Click a byte to select its field; click again to cycle through fields sharing that byte.

Latitude

Bits [0, 25) · 25 bits
Fixed-width field · no alignment gap

Decoded fields

Definition order · zero-based bit offsets · MSB first
Values decoded using the configured payload schema, with actual offsets.
#FieldTypeDecoded valueBit offsetBits used
1Scaled decimal32.87051025
2Scaled decimal-117.241032526
3Unsigned integer375112
4Signed integer-276316
5Booleantrue791
6ASCII text"BUOY-01"8060incl. 4-bit prefix
7Raw bytes01ff1014028incl. 4-bit prefix

Numeric values export as decimal strings to preserve precision, including 64-bit counters. Variable-length fields shift subsequent offsets according to their actual length. A successful decode checks this layout, lengths and padding; it does not verify message authenticity or identify a mismatched schema with the same layout.

3 · Build the payload

Editable C program

The example variables are defined at the top of main. Edit the generated starter code here, copy it, or download a .c file.

telemetry_payload.c
Editable

Generated code is a transparent starting point. Validate the byte order and schema against your receiving decoder before deploying it to production firmware.

Ready to deploy?

Price and activate your Iridium service.

Use the optimized payload size in the Telemetry Station calculator to estimate the right plan for your deployment.