SmartPLC SafeLine AC4S with fieldbus interfaces
8.3.5 Local I/O interface: Provide diagnostic information
43107
To control the provision of the internal diagnostic information of the logical device of a safe sensor at
the local I/O interface the following function block is available:
Provide diagnostic information of 2 safe inputs of the
local I/O interface
→CtrlLocalInputs (→ S. 194)
The safe device that is to be controlled by means of the FB must be added to the device tree.
>
8.3.6 Local I/O interface: Access non-safe inputs/outputs
43106
To access the non-safe inputs and outputs of the local I/O interface the following function blocks are
available:
Read process data of a non-safe input of the local I/O
interface
→GetLocalInput (→ S. 198)
Provide process data at a non-safe output of the local I/O
interface
→SetLocalOutput (→ S. 199)
The process data of the local inputs detected by means of the FB GetLocalInput is not safe
(data type: BOOL).
► Do not implicitly use non-safe process data for a safe function.
To access non-safe process data of the local inputs and outputs with Standard PLC of AC4S:
► Use global exchange variables. (→Data exchange between standard PLC and fail-safe
PLC (→ S. 82))
>
8.3.7 PLCopen Safety: Provide diagnostic information
43125
The function blocks of the PLCopen Safety library SafetyPLCopen.lib provide information about
their internal state at the output DiagCode. To be able to use this diagnostic information in the safe
application the following function block is available:
Provide diagnostic information of the function blocks of
the safety PLCopen library SafetyPLCopen.lib in OSC
→Ctrl_SetDiagInfo (→ S. 196)
The FB generates a separate message for each change of state in the online support centre
(OSC). The ring memory of the OSC therefore reaches its capacity limits within a short time.
► Use FB Ctrl_SetDiagInfo only for debugging.
To Next Page
Loading...
