GE PROFINET PACSystems RX3i Quick Start Manual page 9

IC695PNC001-AJ PROFINET Controller Module
Restrictions and Open Issues
Restrictions and Open Issues related to PNC Operational Behavior
Issue
PNC indicates premature MRP Ring
closure and logs extra Ring Closed/Ring
Open faults when network cable
reconnected
Store of HWC to the PNC may result in 3
IOC Software Faults
STXPNS001 Firmware revision is not
displayed correctly when viewed using
Proficy Machine Edition PROFINET
Explorer
Clearing RX3i controller memory when it
contains a mismatched configuration of
Slice I/O causes the programming
software to disconnect and the RX3i PNC
to reset
Loss of IO Device following hot insertion
of mismatched VersaMax I/O module
Unintended LED blink pattern
There are 2 scenarios that can cause the PNC to indicate that an MRP Ring is closed
when in fact it is still open. The scenarios are:
1. When either an RX3i PNS or PNC that participate in the MRP ring as an MRP
Client communicating via Copper or Fiber SFPs is powered-up in the MRP ring,
extra Ring Closed/Ring Open faults are logged in the I/O fault table. A Ring
Closed fault occurs during the initial stage of the PNS/PNC power-up, followed
by a Ring Open fault in the middle of the PNS/PNC power-up sequence, and
finally a Ring Closed fault occurs when the PNS/PNC completes power-up (OK
LED on).
2. When the first of two MRP ring breaks is restored, extra Ring Closed/Ring Open
faults are logged in the I/O fault table. Upon restoration of the first ring break,
a Ring Closed fault occurs, followed by a Ring Open fault. Then upon
restoration of the second ring break, a final Ring Closed fault occurs. The
duration between faults is a function of the PNC's configured MRP Default Test
Interval and Test Monitoring Count.
When either of the two scenarios is invoked, the user sees extra Ring Closed/Ring
Open faults in the I/O Fault Table. The extra Ring Closed/Ring Open fault may be
ignored.
On very rare occasions, storing a very large I/OLAN intensive hardware
configuration to the PNC may result in 3 IOC Software faults. The faults tend to
occur after a large number of changes are made to the hardware configuration or
the current hardware configuration in the system is cleared prior to storing a new
configuration.
If the controller is Faulted, clear the I/O Fault Table to recover. Otherwise, no
additional steps need be taken and the faults may be ignored.
Proficy Machine Edition does not display firmware revision information correctly for
the STXPNS001. To view the correct firmware revision information, use
HyperTerminal.
Downloading a mismatched configuration for a Slice IO node and then clearing the
RX3i CPU's memory causes Proficy Machine Edition to disconnect and the RX3i PNC
to reset itself.
To recover from this fault, either:
Wait for PNC to auto reset and the OK LED to turn on (solid green), then clear

the PLC user memory.
Power cycle the PLC without a battery/energy pack attached.

Storing the valid configuration will allow the system to start up without any faults.
In very rare cases, hot insertion of a mismatched VersaMax I/O module (for
example, an MDL650 in a slot configured for an MDL640) into the VersaMax PNS
can cause a loss of connection between the PNS and the controlling PNC(s).
No user action is required. When this behavior is seen, the controlling PNC(s) will
automatically reconnect to the VersaMax PNS.
When an overtemperature condition occurs, the PNC001 will blink this pattern:
PORT 1, PORT 2, and STATUS LEDs on red for 0.5 seconds (all other LEDs off),
then PORT 3 and PORT 4 LEDs on red for 0.5 seconds (all other LEDs off).
This is not the correct pattern, as documented in the PACSystems RX3i PROFINET
Controller Manual (GFK-2571).
Description
9
GFK-2573K