communication:binary_protocol
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| communication:binary_protocol [2013/09/10 18:54] – [GPS Requirements] mbrejza | communication:binary_protocol [2013/09/10 19:07] (current) – [Example Telemetry] mbrejza | ||
|---|---|---|---|
| Line 68: | Line 68: | ||
| ===== Example Telemetry ===== | ===== Example Telemetry ===== | ||
| - | sync, length, [callsign, packetID, checksum, (date)time, lat, long, alt, sensor1, ... ,sensorN, [intervals, resolution, [GPS_delta1, | + | sync, length, checksum, [callsign, packetID, (date)time, lat, long, alt, sensor1, ... ,sensorN, [intervals, resolution, [GPS_delta1, |
| [...] means msgpack arrays | [...] means msgpack arrays | ||
| + | (sync, length, checksum are included for the example but not part of the source code specification - they depend on the line coding used - rtty will have $$ as sync, no length and checksum at the end for example) | ||
| ===== Requirement of a Payload Document ===== | ===== Requirement of a Payload Document ===== | ||
| The protocol should be designed such that a receiver can plot GPS data without needing a payload document. As far as sensors go, the receiver should be able to interpret a series of values, but will not necessarily know what these values physically represent, or whether some scaling is required | The protocol should be designed such that a receiver can plot GPS data without needing a payload document. As far as sensors go, the receiver should be able to interpret a series of values, but will not necessarily know what these values physically represent, or whether some scaling is required | ||
communication/binary_protocol.1378839259.txt.gz · Last modified: 2013/09/10 18:54 by mbrejza