A 11 Achievable Safety Depending On The Modules Used; A 12 Behavior In The Event Of An Error - Phoenix Contact Axioline F User Manual

Module with integrated safety logic and safe digital outputs
Hide thumbs Also See for Axioline F:
Table of Contents

Advertisement

AXL F LPSDO8/3 1F
Error messages
Service information
Error classes
Acknowledgment
90
PHOENIX CONTACT
A 11
Achievable safety depending on the modules used
Phoenix Contact recommends using the SISTEMA software utility to determine the
achievable safety.
The SISTEMA software utility for the safety of control systems on machines can be
downloaded free of charge from the website for the Institute for Occupational Safety and
Health of the German Social Accident Insurance, see
http://www.dguv.de/ifa/en/pra/softwa/sistema/index.jsp.
This Windows tool provides assistance in evaluating the safety of control systems within the
scope of EN ISO 13849-1.
According to SISTEMA, performance level PL e can be achieved with the maximum
configuration of 5 serial chains (6 x AXL F LPSDO8/3 1F plus the relevant satellites).
However, you should always check your actual application to ascertain the level of safety
that can be achieved.
A 12
Behavior in the event of an error
Errors that occur on the safe devices can be detected using process data, function blocks,
device LEDs, and SAFECONF in online mode.
These error messages can be evaluated in the standard application program or can be
displayed by means of a visualization.
In addition to error messages, service information can also be output. This information takes
the form of device message warnings that do not affect the safety function. These warnings
are either unacknowledged messages or messages that are acknowledged via the
controller.
The response of all devices connected to the system and the safety functions to an error
depends on the error class detected.
There are five different error classes in the SafetyBridge system:
Critical system and device errors
Parameterization and configuration errors
Communication errors
I/O errors
Application errors
A distinction is made based on:
The severity of the error
The reciprocal effects on other components in the system
The acknowledgment and restart options
The acknowledgment of an error is an intentional user action (controlled via the application
program) with the aim of showing the system (or subsystem) that an error has been
removed and that the system (or subsystem) can reactivate the faulty component.
106889_en_00

Advertisement

Table of Contents
loading

This manual is also suitable for:

Axl f lpsdo8-3 1fAxioline f axl f ssdo8/3 1f

Table of Contents