Datasheet

Command ID field should always be present.

A long response (>16 bytes payload) must be divided into multiple packets. Similar to long

commands, the More data field (bit 7 of byte 3) is used to indicate whether additional packets

are available for the same response. On responses that span more than one packet, the

More data bit on the final packet will be set to 0 to indicate that this is the last packet in the

sequence. The SDEP receiver must re-assemble all sub-packets in into one payload when

necessary.

If more precise command/response correlation is required a custom protocol should be

developed, where a unique message identifier is included in the payload of each

command/response, but this is beyond the scope of this high-level protocol definition.

A sample response message would be:

The first byte is the Message Type (0x20), which identifies this as a response message.

The second and third bytes are 0x1234, which is the unique command ID that this

response is related to.

The fourth byte indicates that we have a message payload of 1 byte.

The fifth byte is the 1 byte payload: 0xFF

Alert Messages

Alert messages (Message Type = 0x40) are sent whenever an alert condition is present on

the system (low battery, etc.), and have the following structure:

20 34 12 01 FF

0: Message Type (U8)

1+2: Command ID (U16)

3: Payload Len (U8)

4: Payload

0x20

0x34 0x12

0x01

0xFF