Diagnosing The Safety Unit Using The Command Interface - Pepperl+Fuchs AS-i Compact Manual

Ethernet/ip + modbus tcp gateways
Hide thumbs Also See for AS-i:
Table of Contents

Advertisement

EtherNet/IP + Modbus TCP-Gateways
Diagnostics
Important!
The following points must be noted for processing:
The information for switching state and error status are not processed time-
synchronous.
When there is a configuration error all bits having value 0 are sent; this must
be noted when processing the data.
When the Monitor is stopped the device color is "gray".
When regularly switching, the status "yellow flashing" can be recognized as a
transition status. This depends on the component model set. This status can-
not be understood as a testing request until it is stably reported (see Monitor
Info and Safety Control/Status Byte). This is not the case until bit '6' is set in
the Monitor Info and Safety Control/Status Byte ("At least one module in Test
status"). This means the diagnostics information in the input data image does
not serve as a trigger for the testing request, but rather only as detailed infor-
mation after the Monitor Info and Safety Control/Status byte have indicated
that at least one component has reported a testing request.
Changing the base setting
Note!
Available only with gateways.
Setting and changing the diagnostics type is done using the device display
([SAFETY]->[AS-I SAFETY]->[SAFE SUBST VAL])
7.2.2

Diagnosing the safety unit using the command interface

All the diagnostics data can also be queried individually and acyclic using the
command interface commands. This method does however involve greater pro-
gramming effort.
32

Advertisement

Table of Contents
loading

Table of Contents