A
A-32
User manual IC220SDL953 - September 2011
GFK-2731
A 13.2
Parameterization or configuration errors
All errors that are detected during the plausibility check of parameters and configuration
data are assigned to this class. This check is usually carried out during the initialization
phase of the system. Following the detection of an error in this class, the devices enter the
safe state and are still able to send diagnostic information or receive new parameter or
configuration data.
It is not possible to acknowledge the error or continue operating without modifying the
parameter or configuration data of the affected device.
A 13.3
Communication errors
Errors detected in the safe protocol during network communication can lead to "operator
acknowledge requested" (acknowledgement by the user; see "Dev-Diag-LPSDO (LPSDO
diagnostics)" on page A-18). For example, these include:
– Transmission errors
– Data inconsistency when copying
– t
FWD
setting is incorrect (the network is too slow for the t
FWD
setting)
– Standard controller in STOP
These errors can be acknowledged. Do not acknowledge these errors from within the
application program. Acknowledgment must be triggered by an intentional user action.
A 13.4
I/O errors
All errors that can occur and are detected within the I/O devices connected to the safe I/O
devices are assigned to this class. For example, these include:
– Short/cross circuits at the inputs or outputs
– Other application-specific errors
These errors are usually detected in the operating phase of the system. When an error is
detected, the affected input or output is disabled and a diagnostic message is sent to the
IC220SDL953 and the standard controller. The standard system remains ready for
operation. Ongoing operation of the application depends on the application itself.
I/O errors can be acknowledged individually by the user in the standard application
program.
