Skip to main content
Version: 4.3.x {testing}

Setup periodic sending of driver 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 driver API you can set up periodic sending of status messages.

Message - Setup driver sampling

info

Message is unicast, with SID = 24

Payload byteBitDescription
00x08
10Motor 3
11Motor 4
12-3reserved
14Driver state 2
15-7reserved
20:1reserved
22Driver state 1
23Range and reference
24Supply 1
26Motor 1
27Motor 2
3-4[uint16]Sending period in [ms]
5-6[uint16]First period in [ms]. (How lond will device wait to send first message). Set to 0, to stop sending message.

You can set different sampling time for each status message. Just setup sampling individually for each message.

Status messages content overview

Message nameSend values
Driver state 1/driver/state, /driver/mode, "driver/temp, /driver/limit, /driver/error
Driver state 2/driver/cmd, /driver/totallimit
Range and referenceVoltage range, Current range, /driver/uref, /driver/iref
Supply 1/driver/supply/currentf and /driver/supply/voltage in relative units, Total charge in [mAh]
Motor 1/driver/motor/currentf and /driver/motor/voltage in relative units. /driver/energy
Motor 2/driver/power, motor angle, /driver/motor/rpmf, /driver/motor/odo in relative units.
Motor 3/driver/currentq, /driver/currentd + current references
Motor 4Rthermistor, /driver/motor/mres, Actual motor torque, Maximum possible motor torque