Refer to Diagnostic class (standard): 3
|
Default reaction |
||
|---|---|---|
|
BD2 |
BD2 |
|
|
BP2 |
BP2 |
The device (Sercos Slave) did not receive a valid telegram or valid data over the real-time bus (Sercos) during the Sercos phases 3 or 4. The diagnostic message is triggered after two consecutive data breakdowns or 10 consecutive telegram breakdowns.
NOTE: The diagnostic message 8112 Sercos telegram invalid is not triggered for telegram breakdowns within 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.
|
|
|
IMPOSSIBLE TO EVALUATE THE DIAGNOSTIC MESSAGE DUE TO INTERRUPTED CONNECTION |
|
Evaluate the diagnostic message 8506 Sercos Master communication not possible when evaluating the diagnostic message 8112 Sercos telegram invalid in order to help ensure specific reaction also during telegram breakdowns. |
|
Failure to follow these instructions can result in injury or equipment damage. |
|
Cause |
Solution |
|---|---|
|
Detected hardware error: Cable is disconnected or inoperable. |
Verify and replace if necessary the cable. |
|
Detected hardware error: Device is inoperable. |
Replace the device. |
