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 phase-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 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 At least one Sercos slave does not react on time after the phase change to phase 3. |
Reset the Sercos slave and start Sercos phase-up again. |
ExtDiagMsg For at least one Sercos slave, an error is detected during synchronization command execution. |
|
ExtDiagMsg The number of configured additional real-time parameters is exceeded. |
Verify and correct if necessary the parameters AdditionalIDNListMDT and AdditionalIDNListAT. |
ExtDiagMsg
Automatic distribution of unique Sercos addresses to the devices not using |
Refer to 8042 Sercos phase switched. |
ExtDiagMsg
Using |
Verify and modify if necessary the Identification Mode if using an unsupported topology. |
ExtDiagMsg Timeout while reading all parameters necessary for timing and telegram calculation from all Sercos slaves. |
|