Status Codes of the Sercos Communication Profile (SCP)

Sercos LED: Pattern #2. CP0 is running

Sercos LED: Pattern #3. CP1 is running

Sercos LED: Pattern #4. CP2 is running

Sercos LED: Pattern #5. CP3 is running

Contact your local Schneider Electric representative.

Contact your local Schneider Electric representative.

Contact your local Schneider Electric representative.

Contact your local Schneider Electric representative.

Sercos LED: Pattern #1. No Sercos communication is running

Contact your local Schneider Electric representative.

Sercos LED: Pattern #7. HP0 is activated

Sercos LED: Pattern #8. HP1 is activated

Sercos LED: Pattern #9. HP2 is activated

Sercos LED: Pattern #6. CP4 is running

Occurs when changing from FF to L&F.

Removed when changing from L&F to FF

Sercos LED: Pattern #10.

The DHCP client has received network settings. The contents of S-0-1020.0.1 Current IP address, S-0-1021.0.1 Current subnet mask, S-0-1022.0.1 Current gateway address, and S-0-1039.0.1 Current hostname are updated to these settings.

For internal use only. Contact your local Schneider Electric representative.

Transition from CP2 to CP3 is still in processing

Data block elements required in CP3 are missing or invalid

During calculation of parameters, the limit of parameters are exceeded.

After conversion of several parameters the result is invalid or is greater than the maximum possible value (for example, greater than 232).

Slave does not support one or more configured IDNs in the used configuration lists (for example, S-0-1050.x.06 Configuration List)

Slave recognizes, that the configured real-time data exceeds the maximum length of MDT

Slave does not support one or more configured IDNs in the used configuration lists (for example, S-0-1050.x.06 Configuration List.

Slave recognizes, that the configured real-time data exceeds the maximum length of AT

t1, t6, or t7, and so on are greater than the Sercos cycle time

At least one telegram offset is outside of MDT or AT

At least one corresponding MDT has an odd length.

Reserved by Sercos II

Contact your local Schneider Electric representative.

Contact your local Schneider Electric representative.

Contact your local Schneider Electric representative.

Contact your local Schneider Electric representative.

Contact your local Schneider Electric representative.

Contact your local Schneider Electric representative.

Order of cyclic command value configuration incorrect

Contact your local Schneider Electric representative.

Contact your local Schneider Electric representative.

Contact your local Schneider Electric representative.

MST window = TTref ± S-0-1023 SYNC jitter, Timing events are t1, t4, t6, t7, and so on.

Slave does not support one or more configured IDNs in the corresponding configuration lists

Slave does not support one or more configured IDNs in the corresponding configuration lists.

Slave does not support one or more configured IDNs in the S-0-1050.x.06 Configuration List.

The sum of the configured application data exceeds the maximum length of this connection.

The master did not activate this procedure command during startup

The maximum number of supported connections is exceeded

Setting in S-0-1050.x.01 Connection setup is incorrect or not allowed

Limitation of S-0-1060.x.03 Maximum quantity of this connection capability is exceeded

Producer cycle time is invalid or not supported

Configured SCP Classes or its combination in S-0-1000.0.1. List of active SCP classes & versions are not supported by the slave

Slave has calculated new timing parameter during procedure command, which are necessary for CP3. Master shall repeat CP2 once again to read and evaluate these parameters for CP3.

Slave needs a reboot to activate a changed configuration

The MDT number in S-0-1009 Device Control (C-DEV) Offset in MDT is greater than the number of configured MDTs in S-0-1010 Lengths of MDTs

The configured offset of C-Dev in S-0-1009 Device Control (C-DEV) Offset in MDT plus the length of C-Dev is greater than the configured telegram length in S-0-1010 Lengths of MDTs

The configured offset of C-Dev in S-0-1009 Device Control (C-DEV) Offset in MDT of MDT0 is too small and overlapping the extended field (configurable with bit 2 of S-0-1032.0.00 Communication control).

The AT number in S-0-1011 Device Status (S-DEV) Offset in AT is greater than the number of configured ATs in S-0-1012 Lengths of ATs

The configured offset of S-Dev in S-0-1011 Device Status (S-DEV) Offset in AT plus the length of S-Dev is greater than the configured telegram length in S-0-1012 Lengths of ATs

The MDT number in S-0-1013 SVC offset in MDT is greater than the number of configured MDT in S-0-1010 Lengths of MDTs

The configured offset of SVC in S-0-1013 SVC offset in MDT plus the length of SVC is greater than the configured telegram length in S-0-1010 Lengths of MDTs

S-0-1009 >= S-0-1013 && S-0-1009 < (S-0-1013 + 6)

The configured offset of SVC in S-0-1013 SVC offset in MDT of MDT0 is too small and overlapping the extended field (configurable with bit 2 of S-0-1032.0.00 Communication control).

The AT number in S-0-1014 SVC offset in AT is greater than the number of configured ATs in S-0-1012 Lengths of ATs

The configured offset of SVC in S-0-1014 SVC offset in AT plus the length of SVC is greater than the configured telegram length in S-0-1012 Lengths of ATs

S-0-1011 >= S-0-1014 && S-0-1011 < (S-0-1014 + 6)

S-0-1050.x.01 (bit 14) == producer && S-0-1015.x.03 (bit 11) == MDT

S-0-1050.x.05 > S-0-1050.x.04

(S-0-1050.x.03[offset] + S-0-1050.x.05) > 1494

The configured offset in S-0-1050.x.03 Telegram Assignment of the connection in MDT0 is too small and overlapping the extended field (configurable with bit 2 of S-0-1032.0.00 Communication control).

(S-0-1050.x.03[offset] + S-0-1050.x.05) > (S-0-1010[S-0-1050.x.03(number)])

(S-0-1050.x.03[offset] + S-0-1050.x.05) > (S-0-1012[S-0-1050.x.03(number)])

((S-0-1009(offset)+1) >= S-0-1050.x.3(offset)) &&

(S-0-1009(offset) < S-0-1050.x.3(offset) + S-0-1050.x.04) &&

(S-0-1009(number) == S-0-1050.x.03(number))

((S-0-1011(offset)+1) >= S-0-1050.x.3(offset)) &&

(S-0-1011(offset) < S-0-1050.x.3(offset) + S-0-1050.x.04) &&

(S-0-1011(number) == S-0-1050.x.03(number))

((S-0-1013(offset)+5) >= S-0-1050.x.3(offset)) &&

(S-0-1013(offset) < S-0-1050.x.3(offset) + S-0-1050.x.04) &&

(S-0-1013(number) == S-0-1050.x.03(number))

((S-0-1014(offset)+5) >= S-0-1050.x.3(offset)) &&

(S-0-1014(offset) < S-0-1050.x.3(offset) + S-0-1050.x.04) &&

(S-0-1014(number) == S-0-1050.x.03(number))

End of MDT block + Jitter (S-0-1023) > tScyc (see Timing of CP3 and CP4 in FG Timing)

End of MDT block + Jitter (S-0-1023) > S-0-1006 (see Timing of CP3 and CP4 in FG Timing)

t1 + AT block + Jitter (S-0-1023) > tScyc (see Timing of CP3 and CP4 in FG Timing)

S-0-1017 (t6) + Jitter (S-0-1023) > tScyc (see Timing of CP3 and CP4 in FG Timing)

S-0-1017 (t7) + Jitter (S-0-1023) > tScyc (see Timing of CP3 and CP4 in FG Timing)

End of MDT block + Jitter (S-0-1023) > S-0-1017 (t6) (see Timing of CP3 and CP4 in FG Timing)

((S-0-1017 (t6) >= S-0-1006 (t1)) && (S-0-1017(t7) <= (S-0-1006 (t1) + AT-block + S-0-1023(Jitter))))

or

((S-0-1017 (t7) >= S-0-1006 (t1)) && (S-0-1017(t7) <= (S-0-1006 (t1) + AT-block + S-0-1023(Jitter)))).

(see Timing of CP3 and CP4 in FG Timing)

Check only if SCP Sync is supported:

S-0-1007 + Jitter (S-0-1023) > S-0-1002 * (S-0-1061 + 1)

(see Timing of CP3 and CP4 in FG Timing)

Check only if SCP Sync is supported:

S-0-1005 > S-0-1050.x.10 (see FG_Data_processing)

Check only if SCP Sync 0x02 is supported:

S-0-1047 > S-0-1050.x.10 (see FG_Data_processing)

Check only if SCP Sync and SCP Cap is supported:

S-0-1060.x.07 > S-0-1050.x.10 (see FG_Data_processing)

Transition from CP3 to CP4 is still in processing

The procedure command is still in processing

For example, S-0-1015 Ring delay is less than 1 µs

If the measured value of SYNCCNT-P1 or SYNCCNT-P2 was eight times 0

or eight consecutive MST losses occurs. Reason: S-0-1015 Ring delay is too small or transmission line is disturbed

Sum of 8 delay measurements (SYNCCNT-P1 & SYNCCNT-P2) was outside the valid range

The procedure command is still in processing

The settings of S-0-1020 IP address, S-0-1021 Subnet Mask, and S-0-1022 Gateway address for one or more Ethernet networks do not match

S-0-1020 IP address = (x.x.x.0) or (x.x.x.255) or (127.0.0.1)

S-0-1027.0.1 Requested MTU is not accepted or write protected by the slave

Device function setup still in processing

Finish of connection configuration still in processing

For internal use only. Contact your local Schneider Electric representative.

Amount of MST losses are half of S-0-1003 in CP3 & CP4

Sercos LED: Pattern #12.

-

-

Addressing is outside of range of configuration list or of list parameter related to MDT data container

Addressing is outside of range of configuration list or of list parameter related to AT data container

-

See CPS state machine of the slave

Note: for new implementation use diagnostic code 0xC30A4020

Reason: Slave does not receive data on port 1 during a given time

Reason: Slave does not receive data on port 2 during a given time

OVS state machine in error, see S-OVS/Error

For example, OVS container length is greater than connection length

Selected factor in S-0-1150.x.10 Number of Samples is not possible

For example, the corresponding configuration lists are incorrect

For example, different length of corresponding lists

-

-

-

-

-

Requested Communication Version is not supported by the HP slave

Configured S-0-1002 Communication Cycle time (tScyc) is not in a valid range

Configured S-0-1010 Lengths of MDTs is not in a valid range

Configured S-0-1012 Lengths of ATs is not in a valid range

Configured S-0-1027.0.1 Requested MTU is not accepted or write protected by the slave

Configured S-0-1017 UC transmission time are invalid or do not match (for example, t6 > t7)

During HP the master has canceled the hot-plug procedure

During HP the master has disabled the hot-plug procedure

For internal use only. Contact your local Schneider Electric representative.

Amount of MST losses is exceeded in CP3 & CP4. The slave switches to NRT state. See CPS state machine of the slave

Amount of data losses > S-0-1050.x.11 in CP4. See FG Connection.

Note: for new implementation use diagnostic code 0xC30F4019

Note: for new implementation use diagnostic code 0xC30F4019

Note: for new implementation use diagnostic code 0xC30F4019

Note: for new implementation use diagnostic code 0xC30F4019

See CPS state machine of the slave

The OVS state machine switched to the state error. The container values are invalid. The OVS.Status.Error is set to 1 in order to show this error.

See CPS state machine of the slave

or Hot-plug of slave

Occurs if cable is broken on active port

Slave does not support the Communication Version announced in MDT0 of CP0 and used in CP1 and CP2

MST timeout = 130 ms

-