Faults Unique To Local Log Table - GE PACSystems RX3i User Manual

Profinet io-controller
Hide thumbs Also See for PACSystems RX3i:
Table of Contents

Advertisement

5.8.1

Faults Unique to Local Log Table

The following faults are registered in the Local Log table of the PROFINET Controller and in no other table.
When viewed using the CLI log details command, they have an Entry Type of Local Fault.
The Local Log Table also contains faults that are passed to the PACSystems CPU. Those faults, which are listed
in the PROFINET Controller Faults in the PACSystems Fault Tables section of this chapter, are not repeated
here.
Group/
Error
Description
Code
2-1
PNC001 restarted.
2-2
Time
synchronization with
PACSystems RX3i
controller failed.
2-4
Invalid Media
Redundancy
Configuration
4-1
Socket close failed
5-1
CLI null environment
pointer
5-3
CLI Ethernet
command failure
5-4
CLI PNC specific
command failure
5-5
CLI initialization
failure
6-1
Write to nonvolatile
memory failure
GFK-2571N
Cause
The PNC001 has experienced a restart.
Possible causes include:
PNC001 power-cycled
-
PNC001 reset button pushed
-
PNC001 command shell command to
-
reset board issued
PNC001 firmware updated
-
PNC001 exceeded safe operating
-
temperature
PNC001 hardware watchdog timer
-
expired
PNC001 internal fatal error
-
encountered
The reason for the reset is indicated by the
description shown when displaying the fault.
The PNC001 was unable to synchronize its
current time with the PACSystems RX3i
controller.
PROFINET Controller encountered an error
related to applying Media Redundancy
configuration parameters.
PROFINET Controller was unable to close an
opened OS socket.
PNC001 encountered a null pointer while
processing a command via the CLI.
PNC001 encountered an error while
processing an Ethernet related command.
PNC001 encountered an error while
processing a PNC001-specific CLI command.
The Command Line Interface functionality
on the PNC001 failed to initialize correctly.
The PROFINET Controller failed to write data
to non-volatile memory, which could result
from configuration store/clear operations
from the programmer, or Command Line
Interface commands.
May 2018
Chapter 5. Diagnostics
Recommended
Correction
If the PNC001 restart is
due to a hardware
watchdog timer
expiration, or internal
fatal error, note the Fault
Extra Data and contact
customer service.
Contact customer service.
Contact customer service.
Contact customer service.
Contact customer service.
Contact customer service.
Contact customer service.
Contact customer service.
Contact customer service.
111

Advertisement

Table of Contents
loading

Table of Contents