Skip to main content
FW version: Stable

Setup periodic sending of cmio states (status messages)

warning

Payload byte position is not corresponding with byte position in transfer layer (CAN, UART, USB, bluetooth...) Before continuing, read carefully how to create a message for:

Using common block API you can set periodic sending of cmio status messages.

Using Setup cmio sampling message you can select multiple cmio states. Then the states are periodically sent. The states are selected using cmio input id. You can set up to 4 ranges of states.

Message - Setup cmio sampling

info

All here listed messages are unicast with SID = 40

Payload byteData-typeDescription
0uint8Which bank is being set: 8 = bank 0, 9 = bank 1, 10 = bank 2, 11 = bank 3
1uint8Start IID of set range
2uint8End IID of set range
3-4uint16Period of data sent in [ms]
5-6uint16First period in [ms]. (How lond will device wait to send first message). Set to 0, to stop sending the bank.

Response

info

Message is multicast The SID is different for each bank

  • bank 0 SID = 42
  • bank 1 SID = 43
  • bank 2 SID = 44
  • bank 3 SID = 45

The message length depends on the used interface. If the payload does not fit into a message, multiple messages are sent. Only the Offset is different.

Payload byteData-typeDescription
00-6Product signature
07Error bit - if ist value is 1 - common block is in error state. Send values may not be valid.
1uint8Offset - IID of first state.
2-3int16First state with IID = Offset
4-5int16Second state with IID = Offset + 1
6-7int16Third state with IID = Offset + 2
...int16Size of this message depends on used interface.