Emerson PACSystems RX3i, User Manual

Page: 111 / 164

RSTI-EP PROFINET I/O Controller User Manual Section 5
GFK-2571R May 2021
Diagnostics 104
Hot Standby CPU Redundancy systems do not support output point faults. For details, refer
to the PACSystems Hot Standby CPU Redundancy User’ s Manual, GFK-2308.
In order to be used, I/O point faults must be enabled in the CPU configuration. For details,
refer to the PACSystems RX7i, RX3i and RSTi-EP CPU Reference Manual, GFK-2222 and to
the PACSystems RX7i, RX3i and RSTi-
EP CPU Programmer’s Ref erence Manual, GFK-2950.
5.5 Fault Locating References
The Fault-Locating References for a PNC001 module can be used for rack-level and slot-level
faults. These names can be programmed on the FAULT and NOFLT contacts:
• #RACK_000r
• #SLOT_0rss
where r represents the rack number and ss represents the slot number
These names cannot be used to check for faults on a PROFINET IO-Device, remote module,
or remote sub-module.
The reserved fault names are always available. These fault names do not correspond to %SA,
%SB, %SC, or to any other reference type. They are mapped to a memory area that is not user
accessible.
Fault Locating References are not supported by embedded PROFINET Controllers.
5.6 Fatal Error Reporting
If the PNC001 module encounters a Fatal error, it tries to save diagnostic information to non-
volatile storage. The RX3i CPU then resets the PNC001 module.
Diagnostic information can be viewed from the Command Line Interface using the show
debug fatalInfo command.
5.7 PROFINET IO Alarms
PROFINET I/O uses Alarms to transfer indications of changes or problems in the remote IO
Device. For example, Diagnosis Alarms are used to indicate a problem with a channel such
as a short circuit, a blown fuse, or overtemperature condition. The PROFINET Controller
translates PROFINET alarms into CPU faults for the PACSystems CPU. Figure 94 shows what
happens when a problem is detected on one of the channels of a module within a remote IO
Device, in this case, a VersaMax PROFINET Scanner.
1. The PROFINET Controller establishes Application Relationship (AR) and then Alarm
Communication Relationship (CR) with the PROFINET IO-Device
2. Module detects a problem (such as a short circuit) and reports it to the IO-Device
(PROFINET Scanner)
3. IO-Device sends Alarm to PROFINET Controller via Alarm CR.
4. PROFINET Controller logs fault in its Local Log and passes it to the CPU Fault Table.
5. PROFINET Controller sends Alarm ACK to IO-Device via Alarm CR.