8042 Sercos phase switched

Description

A Sercos phase change has been detected. In the message logger, the new phase is displayed in Ext. diagnosis.

The table shows the values for DiagExtMsg for diagnostic message 8042 Sercos phase change

DiagExtMsg	Meaning
CP0	Phase change after phase 0.
CP1	Phase change after phase 1.
CP1/scan=(x)	The Sercos has been changed to CP1. Here, (x) Sercos III slaves have been found.
CP=1/xxx	Error xxx detected during phase change after phase 1.
CP=2	Phase change after phase 2.
CP2/use=(x)	The Sercos phase has been changed to CP2. Here, (x) Sercos III slaves have been assigned to device objects from the Devices tree. The remaining Sercos III devices are taken to phase 4 without a connection to device objects in order to help ensure ring healing and redundancy.
CP=2/xxx	Error xxx detected during phase change after phase 2.
CP=3	Phase change after phase 3.
CP=3/xxx	Error xxx detected during phase change after phase 3.
CP=4	Phase change after phase 4.
CP=4/xxx	Error xxx detected during phase change after phase 4.
C2C CP0	The C2C Slave changed into Sercos communication phase 0.
C2C CP1	The C2C Slave changed into Sercos communication phase 1.
C2C CP2	The C2C Slave changed into Sercos communication phase 2.
C2C CP3	The C2C Slave changed into Sercos communication phase 3.
C2C CP4	The C2C Slave changed into Sercos communication phase 4.
C2C NRT	The C2C Slave changed into Sercos NRT state.

CP=<Phase number>/<error number>:

Cause	Solution
oAn error occurred when the phase changed.	oVerify the message logger for other Sercos diagnostic messages. oNote the description of these diagnostic messages.

Cause

Solution

oAn error occurred when the phase changed.

oVerify the message logger for other Sercos diagnostic messages.

oNote the description of these diagnostic messages.

ReconfSercAddr:

Cause	Solution
oWhile changing from CP2 to CP3, the firmware verifies whether the Sercos devices have unique Sercos addresses. If not, the PacDrive LMC firmware automatically tries to distribute unique addresses to the devices not using IdentificationMode SercosAddress.	oThis is indicated with ExtDiagMsg ReconfSercAddr. oIf there is any error detected during this distribution (for example, write protected Sercos address because of address switch != 0) a diagnostic message 8508 with the same ExtDiagMsg is set and the Sercos run-up is aborted (Sercos_Master.State = 11). oIf the addresses could be assigned correctly, the Sercos master automatically restarts the run-up beginning with CP0. This can be seen in the message logger with a sequence of diagnostic message 8042 with ExtDiagMsgs CP0 - CP1 - CP2 - ReconfSercAddr - CP0 - CP1 - CP2 - CP3 - CP4.

Cause

Solution

oWhile changing from CP2 to CP3, the firmware verifies whether the Sercos devices have unique Sercos addresses. If not, the PacDrive LMC firmware automatically tries to distribute unique addresses to the devices not using IdentificationMode SercosAddress.

oThis is indicated with ExtDiagMsg ReconfSercAddr.

oIf there is any error detected during this distribution (for example, write protected Sercos address because of address switch != 0) a diagnostic message 8508 with the same ExtDiagMsg is set and the Sercos run-up is aborted (Sercos_Master.State = 11).

oIf the addresses could be assigned correctly, the Sercos master automatically restarts the run-up beginning with CP0. This can be seen in the message logger with a sequence of diagnostic message 8042 with ExtDiagMsgs CP0 - CP1 - CP2 - ReconfSercAddr - CP0 - CP1 - CP2 - CP3 - CP4.