CAN Time-Out

What does ce5 mean?

A CAN communication timeout has occurred. This could be due to a slave device not responding during remote parameterization (C0370), incorrect parameter set changeover configuration with application I/O, or an internal error with a module on the FIF. A communication timeout means commands or data are not being exchanged, leading to operational halts or incorrect behavior.

• Slave device not powered on or improperly addressed on the CAN bus during remote parameterization (C0370).
• Incorrect CAN timeout settings configured (e.g., P8-06 for CAN-IN1 timeout, P8-16 for CAN-IN2 timeout) which are too short for the network response time.
• High bus load causing significant delays in message transmission and reception, exceeding the timeout period.
• Faulty CAN bus cabling or intermittent connections leading to lost messages.
• Incorrect parameter set changeover configuration (e.g., P0-02, P0-03) preventing the drive from accepting remote commands.

Click steps to track your progress.

1. 1

   Verify that all slave devices involved in the remote parameterization (C0370) are powered on and their CAN node IDs are correctly set (P8-02 or P8-12).

2. 2

   Increase the CAN timeout parameter (e.g., P8-06 for CAN-IN1, P8-16 for CAN-IN2) by 10-20% and re-attempt communication.

3. 3

   Monitor the CAN bus load using a suitable analyzer to ensure it does not consistently exceed 70-80% capacity.

4. 4

   Check the integrity of the CAN bus cable and connectors for any loose contacts or damaged sections.

5. 5

   Review parameter P0-02 (Parameter set source) and P0-03 (Parameter set changeover mode) to ensure they permit remote parameter changes.