8508 Sercos run-up not possible
Refer to Diagnostic class (standard): 3
Cause |
Solution |
---|---|
At least one Sercos slave does not react on time after the phase change to phase 3. |
Reset the Sercos slave and start Sercos run-up again. |
No telegrams were received in phase 0.
Cause |
Solution |
---|---|
Wiring error detected (cable separated). |
Verify and correct if necessary the wiring. |
Non-Operating Sercos slave after the controller. |
Verify the state and condition of the device and reset or replace if necessary. |
ExtDiagMsg C_Time=20000 An error is detected during the parameter transfer for the configuration of the Sercos timing. For example: One set ProducerCycleTime of a Sercos I/O device is not supported by the device. |
Verify and correct if necessary the Sercos timing for the device. |
ExtDiagMsg C_SP3-2000B At least one Sercos slave does not react on time after the phase change to phase 3. |
Reset the Sercos slave and start Sercos run-up again. |
ExtDiagMsg C_SP3-20037 For at least one Sercos slave, an error is detected during synchronization command execution. |
oReset the Sercos slave and start Sercos run-up again. oVerify and correct if necessary the Sercos device. |
ExtDiagMsg C_SP4 =20028 The number of configured additional real-time parameters is exceeded. |
Verify and correct if necessary the parameters AdditionalIDNListMDT and AdditionalIDNListAT. |
ExtDiagMsg ReconfSercAddr Automatic distribution of unique Sercos addresses to the devices not using IdentificationMode SercosAddress was not successful. The Sercos run-up is aborted. |
Refer to 8042 Sercos phase switched. |
ExtDiagMsg Wrong Topology Using IdentificationMode TopologyAddress /2 the Sercos bus can only run-up in bus-topology 'Line' on port 1 or in bus-topology 'Ring'. |
Verify and modify if necessary the Identification Mode if using an unsupported topology. |