System variables
108580_en_02 PHOENIX CONTACT 185 / 272
F_ADDR_XXXXX_CE_CRC *) BOOL Communication error (F_CE_CRC)
This parameter is set if at least one of the following reasons applies:
– The F-Device has detected a communication error during opera-
tion that was caused by an incorrect CRC checksum.
– Inconsistent parameterization between PROFIsafe controller and
F-Device.
– Communication error between PROFIsafe controller and F-
Device.
If this variable was set to TRUE during operation, the cause of the error
must be removed first so that acknowledgment can be carried out
using the F_ADDR_XXXXX_ACK_REI or ACK_REI_GLOBAL vari-
able. If the cause has been removed, the F_ADDR_XXXXX_CE_CRC
variable is set to FALSE again.
F_ADDR_XXXXX_WD_TIME_OUT *) BOOL Communication error (F_WD_TIME_OUT)
Set if the F-Device has detected a communication error caused by the
parameterized F_WD_Time being exceeded.
If this variable was set to TRUE during operation, the cause of the error
must be removed first so that acknowledgment can be carried out
using the F_ADDR_XXXXX_ACK_REI or ACK_REI_GLOBAL vari-
able. If the cause has been removed, the F_ADDR_XXXXX_WD_-
TIME_OUT variable is set to FALSE again.
F_ADDR_XXXXX_IPAR_OK *) BOOL F-Device indicates that the iParameters have been applied
This variable is set when the F-Device indicates that it has applied the
iParameters.
Table 8-6 Management/diagnostic variables for each configured F-Device
System variable Ty pe Meaning
In terms of system availability, this type of CRC error
should only occur once every ten hours at the most (see
PROFIsafe specification regarding “SIL Monitor” and
“Operator Acknowledge”).
During PROFIsafe system startup, e.g., following a pro-
gram download in PLCnext Engineer, this variable is
briefly set as a result of the PROFIsafe system startup
behavior. This is not relevant for the 10-hour monitoring
period described above following a CRC error that
occurred during operation.
To Next Page
Loading...
Need help?
General
