The Push and Hold behavior of
the PNC001 Restart
Pushbutton results in the
CRU320 taking up to 1 second
to detect that PNC001 is no
longer available
When the PNC001 reset button is held down for more than 1 second, the
CRU320 can take up to 1 second to detect the loss of the PNC001 (after the
PNC001 module resets). This causes a delay in the CPU signaling the Loss of
IOC, and in taking the appropriate fault actions (setting point faults, stopping
the controller if Loss of or Missing I/O Controller faults are configured as Fatal,
etc.)
In a Hot Standby Redundancy System, if the system is synchronized and the
PNC001 in question is in the active unit, this also causes a delay in the
redundant system failing over to the backup unit. If this delay exceeds the
Redundancy Data Hold Time (RDHT) for a given I/O Device, that IO Device will
disconnect from the backup unit before the failover occurs.
It is not recommended to use the PNC001 reset button in a normal operating
system. If the reset button must be used, it is recommended to first attempt a
brief press and release of the PNC001 reset button (the PNC001 should reset
as soon as the button is released). Only if the first attempt fails should the
PNC001 button be depressed until the PNC001 resets (approximately 2-3
seconds).
Breaking and reconnecting an
MRP ring by pulling either of
the two MRM ports of the
PNC001 causes extra ring
open/close faults
In some cases, if the network is broken and repaired at either of the two ring
ports of a PNC001 configured to be the MRM, an extra I/O Bus Fault-
Redundant Ethernet network ring is broken (open) and the I/O Bus Fault-
Redundant Ethernet network ring okay (closed) faults are logged in both the
I/O Fault Table and the PNC001 Local Log when the ring is repaired.
These additional faults can safely be ignored as long as the last fault to be
logged is the I/O Bus Fault-Redundant Ethernet network ring okay (closed).
Additional verification of ring status can be obtained by issuing a show
rdnMedia command using the PNC001’s CLI interface.
Restrictions and Open Issues related to the Command
Line Interface
(-Ax Version Only)
Invalid help response for
invalid CLI commands
Occasionally, the CLI will return invalid help suggestions if the user attempts to
get help on an invalid command by using the question mark key. Attempting to
issue the command based on this help text will result in an Error: Bad command
response from the CLI.
Use the help command to view a list of available commands.
For more information on available CLI commands, please refer to the
PACSystems RX3i High-Speed I/O LAN Command Line Interface Manual,
GFK-2572A, or later.
To Next Page
Loading...
Need help?
General
