Emerson PACSystems RX3i PROFINET Important Product Information page 15

GFK-2573Z
Restrictions and Open Issues
Restrictions and Open Issues related to PNC001 Operational Behavior
Issue
PNC001 indicates premature MRP
Ring closure and logs extra Ring
Closed/Ring Open faults when
network cable reconnected
Store of HWC to the PNC001 may
result in three IOC Software Faults
STXPNS001 Firmware revision is
not displayed correctly when
viewed using PAC 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 PNC001
to reset
Loss of IO Device following hot
insertion of mismatched
VersaMax I/O module
There are two scenarios that can cause the PNC001 to indicate that an MRP Ring is
closed when, in fact, it is still open. The scenarios are:
1. When either an RX3i PNS001 or PNC001 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 PNS001/PNC001 power-up, followed by a Ring
Open fault in the middle of the PNS001/PNC001 power-up sequence, and finally a
Ring Closed fault occurs when the PNS001/PNC001 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 PNC001'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/O LAN intensive hardware configuration to
the PNC001 may result in three 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.
PAC 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 PAC Machine Edition to disconnect and the RX3i PNC001 to reset
itself.
To recover from this fault, either:
Wait for PNC001 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.
Description
Sep 2020
13