MoTeC Global Forum

Hey,

I couldn't find a listing describing what the CAN diag error values mean. It does not seem that they are the same like ADL3 (these are described in ADL3 manual).

Where do I find this?

thanks,
Robin

The errors are listed below. There are RS232 errors (first), then CAN errors, then VIMCOM errors from talking to a VIM, SVIM or other VIMCOM device....

what in particular are you looking for?



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: A RS232 error of 9 = parity + overrun.

The error values have the following definitions:

RS232 Errors
Errors generated by RS232 communications.

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 Dash 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 Dash Logger and the other device.

2048
WRONG DATA
Could not decode the protocol.


General CAN Errors
Errors Generated by general CAN communications.

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 (eg 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 (VIM, ADL2, SDL).

Note: VIMCOM devices are connected via CAN.

Dash Logger Errors (ADL3)
These errors are generated by the Dash Logger's communications system.

2
FRAMING
Incorrect number of samples received.

256
BAD CONFIG
Configuration mismatch between Dash Logger and device. Resend the configuration.

512
NO DATA
VIMCOM packets have not been found. Either there is a wiring fault or Dash 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).


VIMCOM Device Errors.
These error codes are sent once by the VIMCOM device on resuming data transmission and therefore indicate why data was previously not being transmitted.

4097
STARTUP
Device has restarted (normally due to power up) Data is not sent until sync is achieved.

4098
HALT
Data not sent due to deliberate halt. For example configuration or firmware being sent.

4099
OVERRUN
Data not sent due to transmit buffer overrun (possibly due to CAN bus too busy)

4100
SYNC TIMEOUT
Data not sent due to Dash Logger sync message timeout (sync not received from Dash Logger)

4101
CAN ERROR
Data not sent due to error on CAN bus

4102
SYNC EXCEEDED
Data not sent due to excessive sync error (synchronisation too far out)

Hi Jamie,

I have nearly all types of CAN errors I attached a little log-file screenshot including the diag-channels...

This is with an ADL2 in a roadcar with OEM ECU and other OEM stuff. Just did some little testing, the car is not completly finished yet. So many of the OEM controllers will have errors etc.

I guess error 256 means that I can't use these IDs (here 0x200 and 0x208) beacuse they are reserved by the ADL2?

For now, I don't care much about the other errors, because the car is not ready to run...

regards,
Robin

yes 0x200 and 0x208 are reserved ID's for dash to PC comms. But if you change it over to secondary can, these id's will change also, but they may go to another id that you want to use...

the CAN errors are suggesting that you either have something on the bus transmitting at the wrong rate, or have some can wiring fault.

what sort of a car is this?

thanks.

-Jamie

oh, never bevor looked into the communications setup.
Secondary IDs would be 0x240 and 0x380. 0x240 would conflict again

Will this issue be the same with ADL3?

It is a Mercedes SLR

thanks,
Robin

okay, with ADL3 everything looks much better

So it was just the Comms IDs on the ADL2 that was causing the problem?

Just what are you doing on this SLR? Seems like a very interesting project...what else can you read from it?

Also, why is the turn signal -1, 0, 1? does it ever go to -1 or did you just scale it that way?

yes I guess it was just the comms ID on the ADL2, since I did not change anything to the wiring or something else, just plugged in the ADL3 and the errors were gone.

Turn signal scaling is what i2 did automatically. You're right, should never go to -1.

I am not sure what else I can get from the CAN because the car is not yet running. But the ADL should receive some information from ECU, GCU and ESP. Also it may be that some things (like the turn signals maybe) may not work without the OEM instrument cluster. There are still many ??? on that project. Pretty much a trial and error job.
The car gets a custom body work and some other modifications...