Phoenix Contact RFC 4072S, Руководство пользователя

Страница: 144 / 272

RFC 4072S
144 / 272
PHOENIX CONTACT 108580_en_02
Diagnostic messages for the iSPNS 3000 are available as follows:
– Entries are stored in the diagnostic memory of the iSPNS 3000
(can be read with PLCnext Engineer)
– Indication on the display (“Safety PLC” tile)
– As a hexadecimal value in the diagnostic parameter registers of the iSPNS 3000. The
registers are elements of the SPNSV2_TYPE structure, see Table 8-1 on page 176 .
Diagnostic parameter register 1: DIAG.PARAM_REG and
Diagnostic parameter register 2: DIAG.PARAM_2_REG
5.4 Possible errors
This section describes possible errors, their causes, effects, and remedy. Section “Errors
with error codes” on page 146 lists errors according to their error code.
Important notes:
Exiting the failure state of the iSPNS 3000
Note that you can only leave the failure state by doing the following:
• Download the safety-related project in the PLCnext Engineer software again, or
• Switch off the supply voltage of the RFC for at least 30 s and then switch it back on
again (power UP), or
• Restart the RFC via the display or in the “Cockpit” editor of the standard controller in
the PLCnext Engineer software.
For detailed information on diagnostics in the PLCnext Engineer software, please refer to
the online help for the software.
Please contact your nearest Phoenix Contact representative if:
– One of the errors described in Section “Errors with error codes” on page 146 occurs
again.
– Errors occur that are not listed in Section “Possible errors” on page 144 .
FS LED/FS bit/failure state
Please note that for all error codes listed in Table 5-1 on page 146 , the FS LED is always
on in the diagnostic display of the RFC 4072S and the FS bit is set in the SPNS_DI-
AG_STATUS_REG register.
The iSPNS 3000 enters the failure state.