Emerson PACSystems RX3i, User Manual

Page: 106 / 164

RSTI-EP PROFINET I/O Controller User Manual Section 5
GFK-2571R May 2021
Diagnostics 99
When the PNC001 is restarted, it retains any entries in its Local Log table and its non-volatile
configuration parameters. Any debug data in non-volatile storage can be viewed from the
Command Line Interface using the log or show log commands.
Restart Triggered by Reset Signal from the PACSystems CPU
The PACSystems RX3i CPU resets/restarts a resident PNC001 module if:
• The application logic executes SVC_REQ #24, specifying the rack and slot of a PNC001
module.
• The RX3i CPU loses communications with the PNC001.
• The PNC001 requests the RX3i CPU to reset / restart it (for example, as a result of a
restart or default Command Line Interface command execution).
Note
: This feature applies to PNC001 modules but does not apply to CPUs with embedded
PROFINET Controllers.
Restart Triggered by Restart Pushbutton
Pressing and releasing the Restart pushbutton on the PNC001 module resets the hardware,
turns OFF all LEDs briefly and initiates the module’s pow er-up sequence. The Restart
pushbutton may also be used to restart the module if the OK LED is blinking an error code
upon hardware or runtime failure, or if the module locks up.
Restart Triggered by Restart and Default Command
Issuing a restart or default command from the Command Line Interface causes the PNC001
to restart. Modify-level privileges are required to issue these commands.
Restart Triggered by Hardware Watchdog Timer
The PNC001 maintains a hardware watchdog timer that will restart the module if it is unable
to carry out its normal processing. The PACSystems RX3i CPU is not able to access the
PNC001 module’s shared memory while the PNC001 is restarting.
After the res tart, the module’s Local Log table is restored from NVRAM. The PNC001 logs a
Wat chdog Timer Expired fault in the RX3i CPU’s IO Fault Table, and a Restart Event in its
Local Log table.