CANgate User's Manual - dataTaker

Overload Errors
If CANgate is heavily loaded (many slot definitions, rapid slot poll rate, fast host/CAN baud rates), errors such as:
CAN1 RX OVERFLOW
may be issued, indicating that one or more incoming CAN messages have been dropped. Even though these events are not
reported in non-verbose mode, they are still counted, and the event counts may be displayed using the STATS command
(P26).
In a similar vein,
PROC TIME OVERFLOW
indicates that CANgate may not have satisfied the requested slot sample rate. This error may sometimes occur if a
diagnostic command is entered that produces a large volume of output text (eg STATUS).
Comms Errors
If a large number of communications errors occur on a CAN port, the port will be briefly shut down and the following message
returned (if in verbose mode):
CAN1 BUS ERROR – DISCONNECTED
The most common cause for this is an incorrectly configured bit rate, although it may also be caused by noise or an
intermittent electrical connection. After two seconds CANgate will re-enable the port and attempt communication again.
All comms errors on the CAN, host and GPS ports are counted and counts may be displayed using the STATS command
(P26).
Certain ECU responses will also be indicated via an error message (if in Verbose mode), eg.
ISO14230 NEGATIVE REPLY – 11
which in this case indicates that the requested service is not available.
Internal Errors
If the CANgate firmware detects a serious internal inconsistency it will force a hardware reset and display a message such
as:
DATA ABORT EXCEPTION AT 000049F8
or
INTERNAL ERROR 1 (00000008)
Following the reset, CANgate will attempt to resume normal operation.
If one of these errors ever occur, please note the circumstances of the failure and contact dataTaker support.
UM-0086-A2 CANgate User’s Manual Page 36