MoTeC ESDL3 - Manual (Page 66)

62 Appendices
8 OVERRUN Receive or transmit overrun error. In the
receive case a byte was received before the
previous byte was read indicating that the
processor is too busy to read the message.
In the transmit case the transmit buffer is full
which could happen if the CAN bus is too
busy.
256 BAD CONFIG The device configuration is not valid (e.g.
overlapping CAN addresses)
512 NO DATA A valid message header was not found -
either there is a wiring fault or comms is
setup incorrectly, (problem could be at either
end). E.g.: transmit and receive CAN IDs do
not match.
1024 CHECKSUM Only generated when used with an Async
Expander. See RS232 errors
2048 WRONG DATA Only generated when used with an Async
Expander or E888/E816 Expander. Async
Expander: Could not decode the protocol.
E888/E816: Compound ID incorrect.
4096 BUS WARNING More than 96 errors have occurred on the
CAN bus. Check wiring and termination
resistors. The CAN bus may still be
operational.
8192 BUS OFF More than 255 errors have occurred on the
CAN bus. CAN communications is
suspended when this error occurs. Check
wiring, termination resistors and the CAN
baud rate. Also check that CAN HI and CAN
LO are correct (not swapped).
16384 CAN TRANSMIT CAN bus transmit warning
"VIMCOM" Errors
Errors generated by "VIMCOM" devices (SVIM, Dash Loggers).
Note:
VIMCOM devices are connected via CAN.
Dash Logger Errors (SDL3)
These errors are generated by the Dash Logger's communications system.
2 FRAMING Incorrect number of samples received.