System Words for M580 Safety PACs

The following system words apply to the M580 safety PAC. For a description of system words that apply to both the M580 safety PAC and non-safety M580 PACs, refer to the presentation of System Words in the EcoStruxure™ Control Expert System Bits and Words Reference Manual.

These system words and values are related to the SAFE task. They can be accessed from application program code in the non-safety sections (MAST, FAST, AUX0 or AUX1), but not from code in the SAFE task section.

Word

Function

Type

%SW4

Period of the SAFE task defined in the configuration. The period is not modifiable by the operator.

R

%SW12

Indicates the operating mode of the Copro module:

  • 16#A501 = maintenance mode

  • 16#5AFE = safety mode

Any other value is interpreted as a detected error.

R

%SW13

Indicates the operating mode of the CPU:

  • 16#501A = maintenance mode

  • 16#5AFE = safety mode

Any other value is interpreted as a detected error.

R

%SW42

SAFE task current time. Indicates the execution time of the last cycle of the SAFE task (in ms).

R

%SW43

SAFE task max time. Indicate the longest task execution time of the SAFE task since the last cold start (in ms).

R

%SW44

SAFE task min time. Indicate the shortest task execution time of the SAFE task since the last cold start (in ms).

R

%SW110

Percentage of system CPU load used by the system for internal services.

R

%SW111

Percentage of system CPU load used by the MAST task.

R

%SW112

Percentage of system CPU load used by the FAST task.

R

%SW113

Percentage of system CPU load used by the SAFE task.

R

%SW114

Percentage of system CPU load used by the AUX0 task.

R

%SW115

Percentage of system CPU load used by the AUX1 task.

R

%SW116

Total system CPU load.

R

%SW124

Contains the cause of the non-recoverable detected error when the M580 Safety PAC is in Halt state:

  • 0x5AF2: RAM detected error in memory check.

  • 0x5AFB: Safety firmware code error detected.

  • 0x5AF6: Safety watchdog overrun error detected on CPU.

  • 0x5AFF: Safety watchdog overrun error detected on coprocessor.

  • 0x5B01: Coprocessor not detected at start-up.

  • 0x5AC03: CIP safety non-recoverable error detected by CPU.

  • 0x5AC04: CIP safety non-recoverable error detected by coprocessor.

NOTE: The above does not constitute a complete list. Refer to the EcoStruxure™ Control Expert System Bits and Words Reference Manual for more information.

R

%SW125

Contains the cause of the recoverable detected error in the M580 Safety PAC:

  • 0x5AC0: CIP safety configuration is not correct (detected by CPU).

  • 0x5AC1: CIP safety configuration is not correct (detected by coprocessor).

  • 0x5AF3: Comparison error detected by main CPU.

  • 0x5AFC: Comparison error detected by coprocessor.

  • 0x5AFD: Internal error detected by coprocessor.

  • 0x5AFE: Synchronization error detected between CPU and coprocessor.

  • 0x9690: Application program checksum error detected.

NOTE: The above does not constitute a complete list. Refer to the EcoStruxure™ Control Expert System Bits and Words Reference Manual for more information.

R

%SW126

These two system words contain information that is for Schneider Electric internal use to help analyze a detected error in more detail.

R

%SW127

%SW128

With CPU firmware 3.10 or earlier, force time synchronization between NTP time and Safe time into the safe IO modules and Safe CPU task:

R/W

%SW142

Contains the safety COPRO firmware version in 4 digits BCD: for example firmware version 21.42 corresponds to %SW142 = 16#2142.

R

%SW148

Count of error correcting code (ECC) errors detected by the CPU.

R

%SW152

Status of the NTP CPU time updated by Ethernet communications module (e.g BMENOC0301/11) over the X Bus backplane via the optional forced time synchronization feature:

  • 0: the CPU time is not refreshed by the Ethernet communications module.

  • 1: The CPU time is refreshed by the Ethernet communications module.

R

%SW169

Safety Application ID: Contains an ID of the safety code part of the application. The ID is automatically modified when the safe application code is modified.

NOTE:

  • If the safe code has been changed and a Build Changes command has been executed since the previous Rebuild All command (thereby changing the Safety application ID), execution of a Rebuild All command may again change the Safety application ID.

  • The SAFE program unique identifier can be read using the SAID output of the S_SYST_STAT_MX system function block.

R

%SW171

State of the FAST tasks:

  • 0: No FAST tasks exist

  • 1: Stop

  • 2: Run

  • 3: Breakpoint

  • 4: Halt

R

%SW172

State of the SAFE task:

  • 0: No SAFE task exists

  • 1: Stop

  • 2: Run

  • 3: Breakpoint

  • 4: Halt

R

%SW173

State of the MAST task:

  • 0: No MAST task exists

  • 1: Stop

  • 2: Run

  • 3: Breakpoint

  • 4: Halt

R

%SW174

State of the AUX0 task:

  • 0: No AUX0 task exists

  • 1: Stop

  • 2: Run

  • 3: Breakpoint

  • 4: Halt

R

%SW175

State of the AUX1 task:

  • 0: No AUX1 task exists

  • 1: Stop

  • 2: Run

  • 3: Breakpoint

  • 4: Halt

R