58-40 / Troubleshooting

CAN frame validation

Diagnose rejected identifiers, payload lengths, padding, and numeric values.

Incorrect DLC or padding#

Use the smallest legal CAN-FD DLC that contains the message. Trailing bytes must be zero. For example, command contains 38 bytes and occupies a 48-byte payload. A shorter frame or nonzero padding is rejected by the codec.

Invalid numeric value#

Floating-point fields must be finite IEEE-754 binary32. NaN, infinity, integer overflow, missing fields, and unknown fields are rejected by the standalone codec.

Identifier mismatch#

Use an extended 29-bit identifier. Check the service, priority, source, destination, and protocol-major fields against the wire reference.

Valid frame but rejected command#

The command guard also checks session, sequence, synchronization, feedback age, enabled state, and configured limits. Valid encoding does not imply that a command may execute.

Run the offline codec example to isolate encoding from board integration. No live CAN dispatcher or qualified controller image is included in the reference software.