8506 Sercos Master comm. not possible

Description

Refer to Diagnostic class (standard): 3

Sercos communication interrupted because no link is detected on either port.

Cause

Solution

Wiring error (cable separated).

Verify and correct if necessary the wiring.

Non-operating Sercos slave after the controller.

Verify the state of the device and reset or replace if necessary.

Sercos communication interrupted because more than the allowed numbers of sequentially DTs are not operating.

Cause

Solution

Wiring error (cable separated).

Verify and correct if necessary the wiring.

Non-operating Sercos slave.

Verify the state and condition of the device and reset or replace if necessary.

In two consecutive cycles, an error is detected on the Sercos bus while receiving data. The Sercos bus is shut down.

NOTE: Erroneous reporting of position of the axes and physical encoders (SinCos, incremental encoder) is possible as a consequence of error acknowledgment of diagnostic message 8506 Sercos Master communication not possible without restarting the controller.
 CAUTION
POSITION LOSS DUE TO SERCOS BUS ERROR
Only acknowledge the diagnostic message after reinitialization or homing.
Failure to follow these instructions can result in injury or equipment damage.

The capability to acknowledge the diagnostic message can be switched off with the function FC_DiagNoQuitSet(). If necessary, use the function FC_SysReset() or FC_PrgResetAndStart().

NOTE: The diagnostic message 8112 Sercos telegram invalid is not sent for invalid data or telegrams to the system since the Sercos slave can no longer report the diagnostic code to the controller via the Sercos bus. In this case, diagnostic code 8506 Sercos Master communication not possible is reported in the controller (Sercos master).