RFC 4072S
146 / 272
PHOENIX CONTACT 108580_en_02
5.4.1 Errors with error codes
Table 5-1 RFC 4072S error codes
Error code (hex) Error cause Remedy or response
0x8001 (0x9001)
to
0x8007 (0x9007)
Internal error
Please contact your nearest Phoenix Contact represen-
tative.
0x8008 (0x9008)
The boot project is missing or incom-
plete.
• Check whether the non-safety-related project is
loaded on the standard controller.
– If the non-safety-related project is not loaded
on the standard controller, download the
safety-related project to the iSPNS 3000 again.
– If the non-safety-related project is not loaded
on the standard controller, follow the instruc-
tions in the note on “Order of project down-
loads” above this table.
0x8009 (0x9009)
to
0x8012 (0x9012)
Internal error
Please contact your nearest Phoenix Contact represen-
tative.
0x8013 (0x9013) The CPU load is higher than 90%.
• Reduce the processor load.
• Analyze the safety-related project. Optimize the
program code for better performance.
• Avoid redundancies in the safety-related project so
that the CPU load is not increased unnecessarily.
• Check if the maximum number of F-Devices to be
configured was exceeded. Reduce the number
according to the information in Section “Technical
data” on page 223, if necessary.
To Next Page
Loading...
Need help?
General
