What are the Comms error codes?

Comms Error Codes

Comms Error Codes

The "Comms CAN x Diagnostic" and "Comms RS232 Diagnostic" channels can be used to diagnose communications problems.

Multiple errors are shown by error codes added together. For example, an RS232 error of 9 = parity + overrun.

The error values have the following definitions:

RS232 Errors

Errors generated by RS232 communications.

Comms Error Codes

1	PARITY	Parity bit incorrect. The comms parity setup is wrong, or there is electrical interference causing errors in the data.
2	FRAMING	Not seeing the stop bit. The baud rate or stop bit setup is wrong or there is electrical interference causing errors in the data.
4	NOISE	Glitch in the data. Electrical interference is causing glitches in the signal. (The Display/Logger does not generate this error.)
8	OVERRUN	A byte was received before the previous byte was read, indicating that the processor was too busy to read the message.
512	NO DATA	A valid message header was not found - either there is a wiring fault or comms is setup incorrectly.
1024	CHECKSUM	A valid message header was found, but the checksum was wrong. If seen in combination with other errors there is electrical noise. If only checksum errors occur there may be a software incompatibility between the Display/Logger and the other device.
2048	WRONG DATA	Could not decode the protocol.

General CAN Errors

Errors generated by general CAN communications.

Comms Error Codes

2	FRAMING	Only generated when used with an E888/E816 expander. Inconsistent message length.
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 set up 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

Display/Logger Errors

These errors are generated by the Display/Logger's communications system.

Comms Error Codes

2	FRAMING	Incorrect number of samples received.
256	BAD CONFIG	Configuration mismatch between Display/Logger and device. Resend the configuration.
512	NO DATA	VIMCOM packets have not been found. Either there is a wiring fault or Display/Logger Connections is setup incorrectly.
2048	WRONG DATA	VIMCOM packet has bad length.
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).