Pacsystems Rx3I & Rsti-Ep Profinet Io-Controller User Manual

GE
Automation & Controls

Programmable Control Products
RX3i & RSTi-EP PROFINET IO-Controller User

PACSystems*
Manual GFK-2571P
RX3i & RSTi-EP

PROFINET IO-Controller
User Manual
GFK-2571P
July 2018
For Public Disclosure

Legal Information
Warnings, Cautions, and Notes as Used in this Publication GFL-002
Warning notices are used in this publication to emphasize that hazardous

voltages, currents, temperatures, or other conditions that could cause
personal injury exist in this equipment or may be associated with its use.
In situations where inattention could cause either personal injury or
damage to equipment, a Warning notice is used.
Warning
Caution notices are used where equipment might be damaged if care is

not taken.
Caution
Note: Notes merely call attention to information that is especially significant to understanding and
operating the equipment.
These instructions do not purport to cover all details or variations in equipment, nor to provide for
every possible contingency to be met during installation, operation, and maintenance. The
information is supplied for informational purposes only, and GE makes no warranty as to the
accuracy of the information included herein. Changes, modifications, and/or improvements to
equipment and specifications are made periodically and these changes may or may not be reflected
herein. It is understood that GE may make changes, modifications, or improvements to the
equipment referenced herein or to the document itself at any time. This document is intended for
trained personnel familiar with the GE products referenced herein.
GE may have patents or pending patent applications covering subject matter in this document. The
furnishing of this document does not provide any license whatsoever to any of these patents.
GE PROVIDES THE FOLLOWING DOCUMENT AND THE INFORMATION INCLUDED THEREIN AS-IS AND
WITHOUT WARRANTY OF ANY KIND, EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
IMPLIED STATUTORY WARRANTY OF MERCHANTABILITY OR FITNESS FOR PARTICULAR PURPOSE.
* indicates a trademark of General Electric Company and/or its subsidiaries.

All other trademarks are the property of their respective owners.
©Copyright 2011-2018 General Electric Company.

All Rights Reserved
For Public Disclosure

Contact Information
If you purchased this product through an Authorized Channel Partner, please contact the seller directly.
General Contact Information
Online technical support and GlobalCare www.geautomation.com/support
Additional information www.geautomation.com
Solution Provider solutionprovider.ip@ge.com
Technical Support
If you have technical problems that cannot be resolved with the information in this manual, please contact us
by telephone or email, or on the web at www.geautomation.com/support
Americas
Phone 1-800-433-2682
1-780-420-2010 (if toll free 800-option is unavailable)
Email digitalsupport@ge.com
Primary language of support English
Europe, Middle East, & Africa

Phone +800-1-433-2682
+ 420-296-183-331 (if toll free 800-option is unavailable or
if dialing from a mobile telephone)
Email digitalsupport.emea@ge.com
Primary languages of support English, French, German, Italian, Spanish
Asia
Phone +86-400-820-8208
+86-21-3877-7006 (India, Indonesia & Pakistan)
Email digitalsupport.apac@ge.com
Primary languages of support Chinese, English
Table of Contents
RX3i & RSTi-EP PROFINET IO-Controller User Manual GFK-2571P
Table of Contents ............................................................................................................................................ i
Table of Figures .............................................................................................................................................. vi
Chapter 1 Introduction ......................................................................................................................... 1
1.1 Revisions in this Manual ........................................................................................................... 2
1.2 PROFINET Controller Description ......................................................................................... 4

1.2.1 PNC001 Description ...................................................................................................................................................4
1.2.2 Embedded PROFINET Controller ...........................................................................................................................5
1.3 PNC001 Module Specifications ............................................................................................... 6
1.4 Operating Range for Surrounding Air Temperature ......................................................... 9

1.4.1 Operating Temperature De-Rating: ......................................................................................................................9
1.5 PNC001 Module Controls and Indicators ...........................................................................10

1.5.1 PNC001 Hardware Implementions (-Ax & -Bxxx) ........................................................................................ 11
1.5.2 Ethernet Network Ports ......................................................................................................................................... 12
1.5.3 USB Port(s) .................................................................................................................................................................. 13
1.5.4 Reset Pushbutton ..................................................................................................................................................... 13
1.5.5 LEDs on the CPUs with Embedded PROFINET .............................................................................................. 13
1.5.6 LEDs on the PNC001 Module ............................................................................................................................... 13
1.6 PROFINET Networks for PACSystems ...............................................................................14

1.6.1 Compression ............................................................................................................................................................... 15
1.6.2 Basic System: One RX3i CPU and One PROFINET Controller using a single port ............................ 16
1.6.3 Basic System: One RX3i CPU and One PROFINET Controller using multiple ports ........................ 17
1.6.4 Basic System: Third-Party Devices and PME Programmer ....................................................................... 18
1.6.5 Systems with One RX3i CPU and Two PROFINET Controllers ................................................................ 19
1.6.6 One RX3i CPU with Four Controllers on Separate Networks.................................................................. 21
1.6.7 Two RX3i CPUs with Two PROFINET Networks and One Ethernet Network .................................... 22
1.6.8 Systems that use PROFINET System Redundancy (PNSR) ...................................................................... 23
1.6.9 Systems that use Hot Standby CPU Redundancy ........................................................................................ 24
1.6.10 RSTi-EP Standalone CPU with embedded PROFINET Controller using a single port .................... 25
1.6.11 RSTi-EP Standalone CPU with embedded PROFINET Controller using multiple ports ................. 26
1.6.12 RSTi-EP Standalone CPU with embedded PROFINET Controller using MRP .................................... 27
1.7 Glossary......................................................................................................................................28
1.8 Documentation.........................................................................................................................30
GFK-2571P July 2018 i

Contents
Chapter 2 Installation ......................................................................................................................... 31
2.1 Pre-Installation Check ............................................................................................................ 32
2.2 Installation in Hazardous Areas .......................................................................................... 33

2.2.1 ATEX Marking .............................................................................................................................................................. 33
2.3 Removing the Backplane Knockout .................................................................................... 34
2.4 Module Installation ................................................................................................................. 35
2.5 Module Removal ...................................................................................................................... 35
2.6 Hot Insertion and Removal ................................................................................................... 36
2.7 Ethernet Port Connections ................................................................................................... 37

2.7.1 PROFINET Network Connections ....................................................................................................................... 37
2.7.2 RJ45 Port Connections ........................................................................................................................................... 37
2.7.3 Installing SFP Devices.............................................................................................................................................. 40
2.7.4 Removing SFP Devices ............................................................................................................................................ 42
2.8 PNC001 LED Behavior ............................................................................................................. 43

2.8.1 Power-up LED Patterns .......................................................................................................................................... 43
2.8.2 Detailed LED Descriptions ..................................................................................................................................... 44
2.9 Installing the USB Port Driver .............................................................................................. 46
2.10 Firmware Updates................................................................................................................... 47

2.10.1 PNC001 Firmware Updates .................................................................................................................................. 47
2.10.2 Firmware Updates for Embedded PROFINET ................................................................................................ 47
2.11 PNC001 Time Synchronization with the Host RX3i CPU ................................................ 48
Chapter 3 Configuration ..................................................................................................................... 49
3.1 Configuration Overview ........................................................................................................ 50

3.1.1 System Planning ........................................................................................................................................................ 50
3.1.2 Basic Configuration Steps ..................................................................................................................................... 51
3.2 Configuration Tools ................................................................................................................ 52

3.2.1 Non-Volatile Configuration Parameters .......................................................................................................... 52
3.3 Configuring an RX3i PROFINET Controller ........................................................................ 53

3.3.1 Configuring a Rack-Mounted RX3i PROFINET Controller (PNC001) ..................................................... 53
3.3.2 Configuring an Embedded RX3i PROFINET Controller ............................................................................... 53
3.3.3 Configuring an Embedded RSTi-EP PROFINET Controller ........................................................................ 54
3.4 Configuring PROFINET System Redundancy .................................................................... 55
3.5 Exploring PROFINET Networks ............................................................................................ 56

3.5.1 Configuring a PROFINET Controller on a LAN ................................................................................................ 57
ii PACSystems* RX3i & RSTi-EP PROFINET IO-Controller User Manual GFK-2571P

Contents
3.5.2 Configuring PROFINET Controller Parameters ............................................................................................. 58
3.6 Configuring PROFINET LANs .................................................................................................62

3.6.1 Configuring the LAN Properties .......................................................................................................................... 63
3.7 Adding a VersaMax PROFINET Scanner to a LAN.............................................................65

3.7.1 Configuring VersaMax PROFINET Scanner Parameters ............................................................................ 66
3.7.2 Adding VersaMax PROFINET Scanner Power Supplies .............................................................................. 70
3.7.3 Adding VersaMax Modules to a Remote Node ............................................................................................. 71
3.7.4 Installing Power Supplies Between Modules ................................................................................................. 72
3.7.5 Configuring VersaMax Module Parameters ................................................................................................... 73
3.8 Adding a Third-Party IO-Device to a LAN ..........................................................................75

3.8.1 Editing Third-Party IO-Device Parameters ..................................................................................................... 76
3.8.2 Configuring Sub-Modules of a Third-Party IO-Device ................................................................................ 78
3.9 Viewing / Editing IO-Device Properties ..............................................................................79
3.10 Assigning IO-Device Names...................................................................................................81
3.11 After the Configuration is Stored to the RX3i CPU .........................................................83
Chapter 4 PROFINET System Operation .........................................................................................85
4.1 PROFINET Operation Overview ...........................................................................................86

4.1.1 PROFINET Communications ................................................................................................................................. 87
4.2 Operations of the PROFINET Controller in the PACSystems System ........................90

4.2.1 Duplicate PROFINET IO-Device IP Address .................................................................................................... 90
4.2.2 Duplicate PROFINET IO-Controller IP Address ............................................................................................. 91
4.2.3 Resolving Duplicate IP Addresses ...................................................................................................................... 91
4.3 I/O Scanning ..............................................................................................................................92
4.4 Data Coherency ........................................................................................................................93
4.5 Performance Factors ..............................................................................................................94
4.6 PROFINET IO Update Rate Configuration ..........................................................................95
4.7 PACSystems CPU Operations for PROFINET ....................................................................96

4.7.1 Reference ID Variables for the PACSystems Application ......................................................................... 96
4.7.2 PNIO_DEV_COMM Function Block ..................................................................................................................... 97
4.7.3 Reset Smart Module for the PROFINET Controller ...................................................................................... 98
4.7.4 DO I/O for Remote IO Modules ............................................................................................................................ 98
4.7.5 Scan Set I/O for Remote I/O Modules ............................................................................................................... 99
4.7.6 PACSystems CPU Defaults - Inputs ................................................................................................................... 99
4.7.7 PACSystems CPU Defaults - Outputs ............................................................................................................... 99
GFK-2571P July 2018 iii

Contents
Chapter 5 Diagnostics ....................................................................................................................... 101
5.1 Power-up and Reset (PNC001 Module) ............................................................................ 102

5.1.1 Module Restart ....................................................................................................................................................... 102
5.1.2 Problems During Power-up and Reset .......................................................................................................... 103
5.1.3 Transitioning to Firmware Update Mode ..................................................................................................... 103
5.2 Special LED Blink Patterns .................................................................................................. 104

5.2.1 Special LED Pattern - Module Identification ............................................................................................... 104
5.2.2 Special LED Pattern - Microprocessor Overtemperature ...................................................................... 104
5.2.3 Firmware Update ................................................................................................................................................... 104
5.2.4 Internal Update ....................................................................................................................................................... 104
5.3 Status Reporting ................................................................................................................... 105
5.4 I/O Fault Contacts ................................................................................................................. 106
5.5 Fault Locating References ................................................................................................... 107
5.6 Fatal Error Reporting ............................................................................................................ 108
5.7 PROFINET IO Alarms ............................................................................................................. 109
5.8 Local Log Table of the PROFINET Controller .................................................................. 110

5.8.1 Faults Unique to Local Log Table ..................................................................................................................... 111
5.8.2 Viewing and Clearing the Local Log Table .................................................................................................... 113
5.9 PROFINET Controller Faults in the PACSystems Fault Tables ................................... 116
5.9.1 Clearing the PACSystems Fault Tables ......................................................................................................... 116
5.9.2 Faults Reported to the PACSystems Controller Fault Table ................................................................ 116
5.9.3 Faults Reported to the PACSystems I/O Fault Table ............................................................................... 118
Chapter 6 Redundant Media............................................................................................................ 127
6.1 PROFINET Media Redundancy Protocol........................................................................... 128

6.1.1 MRP Failover Performance ................................................................................................................................. 129
6.1.2 Bumpless Operation with MRP ........................................................................................................................ 130
6.1.3 MRP Operation for I/O Update Rates of 16ms or Greater ..................................................................... 131
6.1.4 MRP Operation at I/O Update Rates Less Than 16ms ............................................................................ 131
6.1.5 Minimum I/O Rate When Configured in an MRP Ring ............................................................................. 131
6.1.6 Minimum I/O Update Rates for Bumpless Operation in an MRP Ring Topology .......................... 132
6.1.7 MRP Ring Ethernet Traffic Storm Prevention ............................................................................................. 133
6.1.8 Third-party MRP Manager Use with PROFINET Controller as MRP Client ....................................... 134
6.2 Ring Topology with One Controller .................................................................................. 135
6.3 Ring Topology with Multiple Controllers ........................................................................ 136
6.4 Setting Up Media Redundancy Protocol .......................................................................... 137

6.4.1 Media Redundancy Setup for a PROFINET Controller ............................................................................. 137
iv PACSystems* RX3i & RSTi-EP PROFINET IO-Controller User Manual GFK-2571P

Contents
6.5 Sequence for Enabling Media Redundancy..................................................................... 138
6.6 Sequence for Replacing a Media Redundancy Manager .............................................. 139
6.7 Procedure for Disabling Media Redundancy .................................................................. 140
Chapter 7 Network Management .................................................................................................. 141
7.1 SNMP ........................................................................................................................................ 142

7.1.1 Overview of SNMP ................................................................................................................................................. 142
7.1.2 Supported SNMP Features ................................................................................................................................. 143
7.1.3 SNMP Read Access ................................................................................................................................................ 143
7.1.4 SNMP Write Access .............................................................................................................................................. 143
7.1.5 MIB-II Groups Supported .................................................................................................................................... 144
7.1.6 MIB-II System Group Values .............................................................................................................................. 145
7.2 LLDP ......................................................................................................................................... 146

7.2.1 Overview of LLDP ................................................................................................................................................... 146
7.2.2 LLDP Operation ...................................................................................................................................................... 146
7.2.3 LLDP TLVs.................................................................................................................................................................. 147
Appendix A PROFINET IO Performance Examples ............................................................................ 151
A-1 Systems with RX3i PNS .................................................................................................................... 152

A-1.1 RX3i System Performance Summary ............................................................................................................. 152
A-1.2 RX3i System Descriptions .................................................................................................................................. 152
A-2 Systems with VersaMax PNS .......................................................................................................... 153

A-2.1 VersaMax System Performance Summary .................................................................................................. 153
A-2.2 VersaMax System Descriptions ....................................................................................................................... 154
A-3 Systems with RSTi-EP EPSCPE100/CPE115 ................................................................................. 156

A-3.1 RSTi-EP CPE100/CPE115 Embedded PROFINET Controller System Performance Summary . 156
A-3.2 RSTi-EP System Descriptions ............................................................................................................................ 157
GFK-2571P July 2018 v

Contents
Table of Figures
Figure 1: IC695PNC001-Bxxx Front View ___________________________________________________________ 4
Figure 2: IC695PNC001-Ax Controls & Indicators ____________________________________________________ 10
Figure 3: IC695PNC001-Bxxx Controls & Indicators __________________________________________________ 10
Figure 4: PNC001 Ethernet Ports Location and Type _________________________________________________ 12
Figure 5: CPE100/CPE115 Ethernet Ports Location and Type __________________________________________ 12
Figure 6: RX3i System with one PROFINET Controller and one PROFINET LAN _____________________________ 16
Figure 7: RX3i System with one PROFINET Controller and multiple PROFINET LANs ________________________ 17
Figure 8: RX3i System interfacing with Third-Party Devices and with PME Programmer ____________________ 18
Figure 9: RX3i System with two PNC001 Modules and one Daisy-Chain PROFINET LAN _____________________ 19
Figure 10: RX3i System with two PNC001 modules and two Daisy-Chain PROFINET LANs ___________________ 20
Figure 11: RX3i System with four PNC001 modules and four Daisy-Chain PROFINET LANs ___________________ 21
Figure 12: RX3i System with two PROFINET LANs & one Ethernet LAN __________________________________ 22
Figure 13: PROFINET System Redundancy S2 _______________________________________________________ 23
Figure 14: RX3i Hot Standby CPU Redundancy Network with MRP Ring Topology _________________________ 24
Figure 15: RSTi-EP System with embedded PROFINET Controller and one PROFINET LAN ____________________ 25
Figure 16: RX3i System with one PROFINET Controller and multiple PROFINET LANs _______________________ 26
Figure 17: RX3i System with one PROFINET Controller and PROFINET IO Network MRP _____________________ 27
Figure 18: RX3i Backplane showing Removable Plastic Knockout _______________________________________ 34
Figure 19: Install Module into RX3i Backplane ______________________________________________________ 35
Figure 20: Remove Module from RX3i Backplane ___________________________________________________ 35
Figure 21: Ethernet Ports on PNC001 Module ______________________________________________________ 37
Figure 22: Interconnect using Copper Cables / RJ45 Connectors ________________________________________ 38
Figure 23: Interconnect using Multi-Mode Fiber ____________________________________________________ 38
Figure 24: Interconnect using Single-Mode Fiber ____________________________________________________ 38
Figure 25: CAT5e/CAT6 (shielded or unshielded) with RJ 45 Connector __________________________________ 39
Figure 26: Multi-Mode Fiber with LC connector _____________________________________________________ 39
Figure 27: Single-Mode Fiber with LC connector ____________________________________________________ 39
Figure 28: Method for Attaching SFP Device Connector to PNC001 Port _________________________________ 40
Figure 29: Fiber SFP showing LC Connector ________________________________________________________ 42
Figure 30: Copper SFP showing RJ45 Connector ____________________________________________________ 42
Figure 31: PNC001-Bxxx Front View showing LEDs __________________________________________________ 43
Figure 32: RX3i Configuration showing PNC001 slot location __________________________________________ 53
Figure 33: Embedded PROFINET Controller Configured on LAN2 _______________________________________ 53
Figure 34: CPE100/CPE115 Embedded PROFINET Controller Configured on LAN2 __________________________ 54
Figure 35: Setting PROFINET System Redundancy Parameters in PME Inspector __________________________ 55
Figure 36: Explore PROFINET Network from PNC001 ________________________________________________ 56
Figure 37: Explore PROFINET Network from Embedded PROFINET Controller _____________________________ 56
Figure 38: LAN View showing PROFINET Controller on LAN2 __________________________________________ 57
Figure 39: LAN View showing PROFINET Controller on LAN1 __________________________________________ 57
Figure 40: PROFINET Controller Settings Tab (PNC001) _______________________________________________ 58
Figure 41: PROFINET Controller Settings Tab (Embedded PNC) ________________________________________ 58
Figure 42: Setting the Status Reference Address ____________________________________________________ 59
Figure 43: Select SFP Device from Catalog _________________________________________________________ 59
Figure 44: Setting Media Redundancy Parameters __________________________________________________ 61
Figure 45: Setting Media Redundancy Client Parameters _____________________________________________ 61
Figure 46: Setting Media Redundancy Manager Parameters __________________________________________ 61
Figure 47: Configuring the PROFINET LAN _________________________________________________________ 62
Figure 48: LAN Associated with PROFINET Controller ________________________________________________ 62
Figure 49: Adding a New LAN to the Configuration __________________________________________________ 62
vi PACSystems* RX3i & RSTi-EP PROFINET IO-Controller User Manual GFK-2571P

Contents
Figure 50: Setting the Communication Properties of a LAN ____________________________________________ 63

Figure 51: Select PNS from Catalog ______________________________________________________________ 65
Figure 52: Select PNS Type _____________________________________________________________________ 65
Figure 53: PNS Attached to PNC001 in PME Navigator _______________________________________________ 65
Figure 54: Select PNS for Parameter Configuration __________________________________________________ 66
Figure 55: PNS Parameters Settings Tab __________________________________________________________ 66
Figure 56: PNS Parameters Redundancy Tab _______________________________________________________ 67
Figure 57: PNS Parameters Media Redundancy Tab _________________________________________________ 67
Figure 58: Select PNS Ring Ports Usage ___________________________________________________________ 67
Figure 59: PNS Parameters Module Parameters Tab _________________________________________________ 68
Figure 60: PNS Parameters GSDML Details Tab _____________________________________________________ 68
Figure 61: PNS Interface Parameter Details ________________________________________________________ 69
Figure 62: PNS Port Parameter Details ____________________________________________________________ 69
Figure 63: Selecting Power Supply for PNS Rack ____________________________________________________ 70
Figure 64: Power Supplies Displayed in PNS Rack ___________________________________________________ 70
Figure 65: Adding VersaMax I/O Modules to Remote Node ___________________________________________ 71
Figure 66: Select VersaMax Module from Available List ______________________________________________ 71
Figure 67: Adding Power Supplies between Modules in PNS Rack ______________________________________ 72
Figure 68: VersaMax PNS Rack showing Power Supply Located between I/O Modules ______________________ 72
Figure 69: Analog Modules Requiring Jumper-Setting Designation _____________________________________ 73
Figure 70: Selecting the Sub-Module Configuration with Jumper Settings Declared ________________________ 74
Figure 71: Analog Modules Showing Configuration Mismatch Cleared __________________________________ 74
Figure 72: Selecting Third-Party Modules for Addition to LAN _________________________________________ 75
Figure 73: Finding GSDML File for Third-Party Device ________________________________________________ 75
Figure 74: Third-Party I/O: Use of IO-Device Access Point Tab _________________________________________ 76
Figure 75: Third-Party I/O: Use of Media Redundancy Tab ____________________________________________ 76
Figure 76: Third-Party I/O: Select Ring Ports for Media Redundancy Client _______________________________ 76
Figure 77: Third-Party I/O: Configure Ring Ports for Media Redundancy Manager _________________________ 77
Figure 78: Third-Party I/O: Additional Parameter Settings (Product Dependent) ___________________________ 77
Figure 79: Expand Third-Party I/O Device __________________________________________________________ 78
Figure 80: Editing Port Parameters on Third-Party I/O Device _________________________________________ 78
Figure 81: Display of GSDML for Third-Party I/O Device ______________________________________________ 78
Figure 82: Inspector View of IO-Device Properties ___________________________________________________ 79
Figure 83: Setting of IO-Device Update Rate _______________________________________________________ 79
Figure 84: Assigning Reference Variable to IO-Device ________________________________________________ 80
Figure 85: Use of Connection Drop-Down List ______________________________________________________ 81
Figure 86: Equivalent Windows Network Settings ___________________________________________________ 81
Figure 87: Assign LAN _________________________________________________________________________ 81
Figure 88: List of Device Names on LAN with Status Indications ________________________________________ 82
Figure 89: Application Relationship ______________________________________________________________ 87
Figure 90: Real-Time and Non-Real-Time Data Communications _______________________________________ 88
Figure 91: Diagram of Multiple Asynchronous I/O Scans ______________________________________________ 92
Figure 92: PNIO_DEV_COMM Function Block ______________________________________________________ 97
Figure 93: PNIO_DEV_COMM Example ___________________________________________________________ 98
Figure 94: Alarm Processing Phases _____________________________________________________________ 109
Figure 95: Local Log Display ___________________________________________________________________ 113
Figure 96: Log Details Display __________________________________________________________________ 114
Figure 97: Log Details of a Specific Log Entry ______________________________________________________ 115
Figure 98: Timeline for Successful MRP Ring Repair at 16ms I/O Update Rate ___________________________ 131
Figure 99: Ring Topology with One Controller _____________________________________________________ 135
Figure 100: Ring Topology with Multiple Controllers ________________________________________________ 136
GFK-2571P July 2018 vii

Chapter 1 Introduction
This chapter introduces the PACSystems RX3i & RSTi-EP PROFINET system and describes the various forms of
RX3i & RSTi-EP PROFINET Controllers:
1. The IC695PNC001 module (abbreviated PNC001), which is a rack-mounted module residing in the
CPU Rack; there are two hardware versions of this module: IC695PNC001-Ax and IC695PNC001-Bxxx.
The differences are explained in Section 1.5.1.
2. The embedded PROFINET Controllers available in certain RX3i & RSTi-EP CPUs. At publication, the
IC695CPL410 (CPL410), IC695CPE400 (CPE400), IC695CPE330 (CPE330) and EPSCPE100/EPSCPE115
(CPE100/CPE115) permit LAN2 to be configured as a PROFINET Controller.
The last two pages of this chapter are a glossary that summarizes many terms used in the manual.
Chapter 2, Installation explains how to install a PNC001, how to complete port connections, and how to
update the PNC001 module firmware. Chapter 2 also explains how to install the USB port driver on the
PNC001 module (PNC001-Ax only), and describes how the module synchronizes its internal clock with the RX3i
CPU. Since embedded PROFINET Controllers require no installation per se, refer to the installation instructions
for the corresponding PLC CPU.
Chapter 3, Configuration explains how to complete and download the PACSystems RX3i & RSTi-EP
configuration for target PROFINET Controller, as well as devices present on the associated PROFINET network.
The associated devices typically include RX3i and VersaMax PROFINET Scanners and third-party PROFINET
devices, but may also include additional PROFINET Controllers present on the network.
Chapter 4, PROFINET System Operation describes I/O scan operation and application program function blocks
for use with any RX3i & RSTi-EP PROFINET Controller (slot-mounted or embedded). This chapter also provides
an overview of PROFINET communications between the controller and IO-Devices.
Chapter 5, Diagnostics explains the power-up and reset process, special LED blink patterns, status reporting,
and fatal error reporting. It also describes faults and corrective actions.
Chapter 6, Redundant Media, explains how a PROFINET system can be set up for PROFINET Media Redundancy
Protocol (MRP), and describes ring topologies that might be used.
Chapter 7, Network Management explains the use of SNMP (Simple Network Management Protocol) and Link
Layer Discovery Protocol (LLDP) to assist network management. These features are available in PNC001
firmware version 1.10 or later, and in all firmware versions of CPL410, CPE400, CPE330 and CPE100/CPE115.
GFK-2571P July 2018 1

Chapter 1. Introduction
1.1 Revisions in this Manual
Rev Date Description

P Jul- ▪ Updated for IC695CPL410 (new CPU with Linux)
2018 ▪ Updated for IC695PNS101 (Advanced PROFINET Scanner module)
N May ▪ Corrected the units associated with Network Transit Time, which is a millisecond.
2018 ▪ Clarification added for footnote 3.
▪ Added introductory section on PROFINET System Redundancy (Section 1.6.8).
▪ Added a note on Compression at Section 1.6.1.
M Apr ▪ Added information about embedded PROFINET Controllers in RSTi-EP CPU CPE115
2018 module
L Feb ▪ Compatibility with CPE302.
2018
K Dec- ▪ Updates for new hardware version, IC695PNC001-Bxxx.
2017
J Oct- ▪ Updated content for CPE400.
2017 ▪ Added Section 3.4, Configuring PROFINET System Redundancy
▪ Correction made in Section 4.2.2, Duplicate PROFINET IO-Controller IP Address.
H Aug- ▪ Added MRP information for embedded PROFINET Controllers in RSTi-EP CPU
2017 EPSCPE100 (CPE100).
G Apr- ▪ Added information about embedded PROFINET Controllers in RSTi-EP CPU EPSCPE100
2017 (CPE100)
▪ Noted max loading and performance differences between embedded and rack-
mounted PROFINET controllers.
F Dec- ▪ Added information about embedded PROFINET Controllers in CPE400 and CPE330
2016 ▪ Noted max loading and performance differences between embedded and rack-
mounted PROFINET controllers.
E Mar- ▪ PNC001 Module Specifications section updated to include CPE305, CPE310 and CPE330
2015
D Nov- ▪ Added/modified information to include critical network port feature.
2014 ▪ Increased maximum I/O-device support from 64 to 128 devices per PNC001 (star
topology).
▪ Increased maximum redundant I/O-device support from 128 to 255 for the system.
▪ In section 5.9.2 Faults Reported to the PACSystems Controller Fault Table, added new
Controller Fault description for Unable to deliver configuration to module fault.
▪ In section 5.9.3 Faults Reported to the PACSystems I/O Fault Table, changed details
about PROFINET Controller Heavily Loaded and Loading has Improved faults.
▪ In section 6.1 PROFINET Media Redundancy Protocol, Added additional MRP
performance information (table from the PUN, and new information).
▪ In sections 7.1.3 SNMP Read Access and 7.1.4 SNMP Write Access, Changed PROFINET
Controller SNMP access credentials and capabilities to reflect differences between
firmware versions 2.05 or earlier and 2.10 or later.
2 PACSystems* RX3i & RSTi-EP PROFINET IO-Controller User Manual GFK-2571P

Rev Date Description

C Mar- ▪ Chapter 1, Introduction: made edits to clarify that products other than VersaMax
2014 support redundancy.
▪ Chapter 4, PROFINET System Operation: made edits to support redundancy.
▪ Chapter 6, Redundant Media: added table to show which PROFINET Scanner/Device
supports PROFINET Media Redundancy Protocol (MRP), and made other edits to clarify
that products other than VersaMax support redundancy.
GFK-2571P July 2018 3

1.2 PROFINET Controller Description

This manual covers two types of PROFINET Controller:
1. The traditional Rack-mounted RX3i PROFINET Controller, IC695PNC001;
2. A PROFINET Controller that is embedded within a CPU.
1.2.1 PNC001 Description
The PACSystems RX3i PROFINET Controller module, IC695PNC001,
connects a PACSystems RX3i controller to a PROFINET network. It enables
the RX3i controller to communicate with IO-Devices on the network. The
PNC001 provides all the functions, services, and protocols required for
certification as a PROFINET IO Version 2.2 IO Controller, running at both
100Mbps and 1Gbps.
The PNC001 supports 10/100/1000Mbps Copper, 100/1000Mbps Multi-
mode Fiber, and 100/1000Mbps Single-mode Fiber. The network can
include media interfaces of more than one type. PROFINET
communications on the network require 100 and 1000 Mbps link speed.
10Mbps cannot be used for PROFINET communications. However, 10Mbps
can be used for other types of Ethernet traffic, such as ping, and telnet.
Features of the RX3i PNC001 module include:
▪ Full programming and configuration services for the PROFINET
Controller, PROFINET Scanners (PNS), and other third-party IO-
Devices using PROFICY Machine Edition.
▪ Firmware upgrades using the WinLoader software utility.
▪ Built-in Command Line Interface function that provides direct
monitoring and partial configuration via the module’s micro USB port
or using telnet. (PNC001-Ax only)
Note: The USB port is for system set-up and diagnostics only.
It is not intended for permanent connection.
▪ Support for star, ring, and daisy-chain/line network topologies.
▪ Four switched Ethernet ports — two 8-conductor RJ45 shielded
twisted pair 10/100/1000 Mbps copper interfaces and two Small
Form-factor Pluggable (SFP) cages for user-supplied SFP devices.
▪ Support for media redundancy
▪ Internal clock synchronized with the RX3i CPU for time-stamped
diagnostics entries.
▪ Restart pushbutton to manually restart the module without power
cycling the system.
▪ LEDs: OK, LAN, STATUS, CONFIG, ACTIVE, USB (PNC001-Ax only), and
Port Number LEDs as shown in Figure 2 and Figure 3.
Figure 1: IC695PNC001-Bxxx
Front View

1.2.2 Embedded PROFINET Controller

CPL410, CPE400, CPE330 and CPE100/CPE115 feature an Embedded PROFINET IO-Controller function. This
feature permits LAN2 to be configured as a PROFINET Controller similar to PNC001 in functionality, but
without requiring the presence of a PNC001 rack-mounted module.
In the following Specifications section, the physical specifications related to rack mounting do not apply to the
embedded PROFINET Controllers. Refer to the corresponding product documentation for CPL410, CPE400,
CPE330 and CPE100/CPE115 in the PACSystems RX7i, RX3i and RSTi-EP CPU Reference Manual, (GFK-2222AE
or later).
GFK-2571P July 2018 5

1.3 PNC001 Module Specifications

PROFINET Support PROFINET Version 2.2 General Class A IO-Controller
Redundantly controlled operation conforms to PROFINET V2.3 Type S-2
System Redundancy.
Note that the CPE100/CPE115 is a simplex PROFINET IO-Controller.
CPU Compatibility Requires CPU315, CPU320, CPE305, CPE310 or CPE330 with firmware
version 7.0 or higher. Also compatible with all versions of CPE302.
Simplex or redundantly-controlled PROFINET I/O requires CRU320 release
8.00 or higher.
For the current status of CPE330 features refer to PACSystems RX7i, RX3i
and RSTi-EP CPU Reference Manual, (GFK-2222Z or later).
Note that CPL410, CPE400 and CPE100/CPE115 features an embedded
PROFINET IO-Controller; these are standalone CPUs and do not support
IC695PNC001.
Power Requirements1 , Rev. –Ax: Rev. –Bxxx:
with no SFP devices installed 3.3Vdc: 0.5A 3.3Vdc: 0.5A
with two SFP devices installed, 0.35A per SFP 3.3Vdc: 1.2A maximum 3.3Vdc: 1.2A maximum
5 Vdc: 1.5A maximum 5 Vdc: 0.75A maximum
Operating Temperature Range 1
Rev. -Axxx: Rev. -Bxxx:
0°C to 60°C -25°C to 60°C
Note: See section 1.4 for de-rating conditions
Number of PROFINET Port Connectors 1
PNC001 –2 RJ45 and 2 SFP Cages located on the underside of module
(SFP devices not included, available separately).
Embedded PROFINET IO-Controller – 2 RJ45.
Front Panel Connectors1 PNC001-Ax: One micro USB for communication with a computer using
Command Line Interface.
PNC001-Bxxx: One RJ45. Disabled.
Command Line Interface Supported PNC001-Ax – Yes. PNC001-Bxxx: No.
Embedded PROFINET IO-Controller – No.
LAN1 IEEE 802.2 Logical Link Control Class I
IEEE 802.3 CSMA/CD Medium Access Control 10/100/1000 Mbps
Maximum I/O Memory 128 Kbytes of combined input/output memory per PROFINET Controller
Note: RSTi-EP CPE100/CPE115 supports a maximum of 8 IO Devices.
The combined input and output memory is equivalent to the input
/output memory requirements of those 8 devices.
Hot-swappable PNC001 – Yes;
Embedded PROFINET IO-Controller – No.
CPU Status Bits 32
PROFINET IO-Device Data Update Rates Configurable: 1ms, 2ms, 4ms, 8ms, 16ms, 32ms, 64ms, 128ms, 256ms and
on the PROFINET Network 512ms
Note: For CPE100/CPE115, Update Rates below 16ms are not
recommended.
Number of IP Addresses One
Number of MAC Addresses PNC001 – 5. One per external PROFINET port and one internal.
Embedded PROFINET IO-Controller – 1.
1
For CPL410, CPE400, CPE330 and CPE100, CPE115 refer to the equivalent product specifications in the PACSystems RX7i,
RX3i and RSTi-EP CPU Reference Manual, (GFK-2222AE or later).

System Maximum Limits

PROFINET Controllers per RX3i CPU Four PNC001 maximum. Must be located in main CPU rack. Cannot be
located in a remote node.
CPE330 supports one embedded PROFINET Controller plus up to four
PNC001.
CPL410, CPE400 & CPE100/CPE115 support one embedded PROFINET
Controller. Since these are standalone CPUs they do not support any
PNC001 in their hardware configuration.
IO-Devices per IO-Controller 128 max per PNC001 at maximum update interval.
32 max (simplex) or 20 max (Hot Standby Redundancy) per embedded
PROFINET Controller at maximum update interval.
8 max per RSTi-EP CPE100/CPE115 embedded PROFINET Controller.
For limits at shorter update intervals, refer to PROFINET Controller Loading
Limits in Chapter 3.
Max MRP Clients when configured as MRP PNC001 – 63
Manager Embedded PROFINET Controller - 31
Embedded PROFINET Controller CPE100/CPE1152 - 8
IO-Devices per Network Maximum of 255 simplex or 255 redundant I/O Devices per network,
spread across a maximum of 8 I/O Controllers.
The actual total number of devices supported per network depends on the
topology. For details, refer to Maximum Number of Nodes per Network
based on Topology, below.
IO-Devices per RX3i CPU Maximum of 255 simplex or 255 redundant I/O Devices per RX3i CPU,
spread across up to four PROFINET Controllers.3
IO-Devices per RSTi-EP CPU Maximum of 8 simplex I/O Devices for CPE100/CPE115.
IO-Controllers per Network Eight maximum
Input and output memory per IO-Controller Maximum of 128 Kbytes combined input and output memory
Note: RSTi-EP CPE100/CPE115 supports maximum 8 IO Devices so the
combined input and output memory is equivalent to maximum input
/output memory supported by 8 devices.
Number of PROFINET Slots per device 256
Number of PROFINET Subslots per slot 256
Number of PROFINET Submodules per RX3i 2048
CPU
Programmer Limits
Number of IO-Controllers 128 (32 RX3i CPU targets × 4 IO-Controllers per RX3i CPU)
Number of IO-Devices 2048 (128 per network × 16 PROFINET networks)
Total number of devices 2176 (does not include backplanes, power supplies, or I/O modules)
For product standards, general operating specifications, and installation requirements, refer to the
PACSystems RX3i System Manual, GFK-2314.
2
Effective with firmware v9.30, CPE100/CPE115 supports MRP.
3
In the case of CPE330, with embedded PROFINET activated, it is possible to have five PROFINET Controllers. However, in
the rare case of having all 5 PNCs configured on the same LAN, and then invoking redundancy, each CPU is again
restricted to a limit of 4 PNCs (in order to satisfy the overall limit of 8 PNCs per LAN).
GFK-2571P July 2018 7

Maximum Number of Nodes per Network based on Topology

• For a network using MRP ring topology, the maximum number of nodes is 64 (consisting of the PNC001
PROFINET Controller(s) plus up to 62 or 63 IO-Devices). If the ring uses Media Redundancy Protocol, this
means one Media Redundancy Manager and up to 63 clients.
• For a network using MRP ring topology and an Embedded PROFINET IO-Controller as the MRP Ring
Manager, the maximum number of nodes is
o for CPE330/CPE400/CPL410: 32 (1 MRP Manager and 31 MRP clients)
o for CPE100/CPE115: 9 (1 MRP Manager and 8 MRP clients).
• For a network using star topology, the maximum number of nodes configurable is 263 (consisting of up to
8 PNC001 PROFINET Controllers plus up to 255 IO-Devices).
• For a network using star, line topology, or MRP Ring (where the Embedded PROFINET IO-Controller is not
the MRP Ring Manager) the maximum number of nodes configurable of the system is 264. This may consist
of up to eight IC695PNC001 PROFINET Controllers and one Embedded PROFINET IO-Controller (CPL410,
CPE400 or CPE330) plus up to 255 I/O-Devices.

1.4 Operating Range for Surrounding Air Temperature

PNC001-AX 0 to 60°C surrounding air temperature
PNC001-BXXX -25 to 60°C surrounding air temperature
1.4.1 Operating Temperature De-Rating:

The operating temperature range is specified for the module and not the system as a whole. As a
guideline, if the module is next to hot neighbor modules on each side the maximum operating
ambient temperature should be de-rated as described below:
• If 100 MB Fiber SFPs installed, then reduce by 5°C
• If Copper SFPs operating at 1 GB, then reduce by 6°C
GFK-2571P July 2018 9

1.5 PNC001 Module Controls and Indicators
Figure 2: IC695PNC001-Ax Controls & Indicators Figure 3: IC695PNC001-Bxxx Controls &

Indicators

1.5.1 PNC001 Hardware Implementions (-Ax & -Bxxx)

In January 2018, an updated hardware implementation(-Bxxx) replaced the earlier version (-Ax) of the rack-
mounted PNC001. The following are the differences between these two hardware implementations.
Topic -Ax -Bxxx

Appearance Figure 2 Figure 3
Case Plastic Metal
Attachment to Rack Via plastic case latch and heatsink screw Via two Phillip’s head machine screws
Heatsink Remove plastic knockout from rack No knockout removal required
Status LEDs 6 LEDs 5 LEDs (no USB LED)
LED Behavior See Section 2.8 See Section 2.8
4 banks of LEDs (bottom of faceplate)
Ethernet Port LEDs 4 singleton LEDs (top of faceplate) The digits representing the port
numbers are backlit by LEDs.
µUSB Port Present Absent
Command Line
Uses µUSB Port Not available
Interface
RJ45 Connector on
Absent Present (Disabled)
Faceplate
Power Requirements Higher (see Section 1.3) Lower (see Section 1.3)
Operating
0 to 60°C -25 to 60°C
Temperature Range
Module Reset Pushbutton “Restart” Membrane “Reset”
With the exception of the Command Line Interface, the -Bxxx version is functionally compatible with the -Ax
version.
GFK-2571P July 2018 11

1.5.2 Ethernet Network Ports

Figure 4 shows the underside of the PNC001 module.
• Ports 1 and 2 are standard RJ45 connections.
• Ports 3 and 4 offer Small Form-factor Pluggable (SFP) cages
The PROFINET Controller connects to a PROFINET network via one or more of its four external switch ports.
Two 8-conductor RJ45 shielded twisted pair 10/100/1000 Mbps copper interfaces and two SFP cages provide
flexibility in media selection and the ability to use redundant media for the PROFINET network. Use of
redundant media must first be set up in the module configuration. Chapter 6 provides additional information
about Redundant Media.
The PROFINET protocol supported by the PACSystems RX3i PROFINET modules can be sent and received over
any of the four external ports on PNC001.
The PNC001 module is assigned five Ethernet MAC addresses: one for each of the four external Ethernet ports
and one for the internal switch.
Figure 4: PNC001 Ethernet Ports Location and Type

For the Embedded PROFINET LAN (LAN2), CPL410, CPE400 and CPE330 provide two RJ45 ports identical to
those shown as Port 1 and Port 2 in Figure 4. The operational behavior, configuration parameters and
diagnostics are also identical. Refer to the corresponding product documentation for further details.
Small Form-factor Pluggable (SFP) cages (like Port 3 and Port 4 in Figure 4) are not offered on CPL410, CPE400,
CPE330, nor on CPE100/CPE115.
Figure 5: CPE100/CPE115 Ethernet Ports Location and Type

The CPE100/CPE115 Embedded PROFINET LAN (LAN2) supports three switched 8-conductor RJ45 shielded
twisted pair 10/100 Mbps copper interfaces ports as shown in Figure 5. The operational behavior, configuration
parameters and diagnostics are identical to PROFINET port of CPE400. Refer to the corresponding product
documentation for further details.
CPE100/CPE115 LAN2 Port 2 and Port 3 have the ability to use redundant media for the PROFINET network.
Use of redundant media must first be set up in the module configuration. Chapter 6 provides additional
information about Redundant Media.

Ethernet Port Status Indicators

Each external switched port has an associated link-up/link-down status bit that can be monitored by the RX3i
CPU to check the operating status of the port (see Status Reporting in Chapter 5, Diagnostics, for information
about the PROFINET Controller status bits). In addition, the Port Number LEDs on the front of the module
provide a visual indication of the port status.
1.5.3 USB Port(s)

The USB ports on the CPUs that support embedded PROFINET operate independently of the PROFINET
function. Refer to the corresponding product documentation for further details.
The PNC001-Bxxx module has no micro USB port, and therefore does not support the Command Line Interface.
The PNC001-Ax module has a micro USB port for connection to a computer running Windows® 2000, Windows
XP, Windows Vista®, Windows 7 or Windows 10. On the PNC001 module (-Ax version) only, the USB port can
be used to access the Command Line Interface (CLI) function using a terminal emulation application such as
HyperTerminal.
The Command Line Interface function can be used to monitor a PROFINET Controller module and check its
operation. If a problem occurs, the Command Line Interface can be used help determine the cause.
A driver-install application is provided to set up a computer to communicate with the USB port (see Chapter 2,
Installation, for instructions).
1.5.4 Reset Pushbutton

The Reset pushbutton on a PNC001 module can be used to manually reset the module without cycling power.
The restart operation commences when the pushbutton is released.
1.5.5 LEDs on the CPUs with Embedded PROFINET

Refer to the corresponding product documentation for further details.
1.5.6 LEDs on the PNC001 Module

The table below summarizes LED functions on the PNC001 module. More detailed information about error
indications and special blink patterns is given in Chapter 2, Installation and Chapter 5, Diagnostics.
OK Green ON indicates that the module is able to perform normal operation.
LAN Indicates network packets are being processed by the network interface (not just passing through the
embedded switch).
STATUS Indicates the condition of the PROFINET Controller during normal operation. It indicates whether an entry
other than the start-up event is present in the module’s Local Log. STATUS can also indicate whether any of
the MAC addresses are invalid.
CONFIG Indicates whether the module has received its configuration from the RX3i CPU.
ACTIVE Indicates the status of PROFINET connections.
USB Indicates activity on the USB port. (PNC001-Ax only)
Port Indicate link speed, link connection and link activity corresponding to the four possible external Ethernet
LEDs ports.
GFK-2571P July 2018 13

1.6 PROFINET Networks for PACSystems

PROFINET is an open standard for industrial automation that is based on Industrial Ethernet. The PROFINET IO
framework allows the creation of I/O data exchanges between controllers and distributed devices. It also
allows configuration, parameterization, and diagnostics communication between controllers and devices.
Note: The PROFINET Controller operates only in auto-negotiate mode. All PROFINET bus devices and
switches that are connected to the PROFINET Controller should be configured to use auto-
negotiation.
The following products support PROFINET I/O:
Catalog # Product Notes
IC695CPE400 RX3i Rackless CPU with LAN2 may be configured as PROFINET Controller
IC695CPL410 embedded PROFINET
Controller
IC695CPE330 RX3i CPU with embedded LAN2 may be configured as PROFINET Controller
PROFINET Controller Supports up to 4 PNC001 in its rack
IC695CPUxxx All other RX3i CPUs without Supports up to 4 PNC001 in its rack
Redundancy
IC695CRUxxx All other RX3i CPUs with Supports up to 4 PNC001 in its rack
Redundancy
IC695PNC001 RX3i Rack-Mounted PROFINET Controls IO-Devices on PROFINET network
Controller
IC695PNS001 RX3i Rack-Mounted PROFINET Head-End for RX3i I/O Rack. Exchanges I/O data and Alarms
IC695PNS101 Scanner with PROFINET Controller. Scans modules installed in its
I/O Rack.
IC695CEP001 RX3i CEP I/O Drop PROFINET Head-End for RX3i CEP I/O Drop. Exchanges I/O data and
Scanner Alarms with PROFINET Controller. Scans modules installed
in its backplane and expansion rack.
IC200PNS001 VersaMax PROFINET Scanner Head-End for VersaMax I/O Rack. Exchanges I/O data and
IC200PNS002 Alarms with PROFINET Controller. Scans modules installed
in its I/O Rack.
EPSCPE100/CPE115 RSTi-EP Standalone CPU with LAN2 may be configured as PROFINET Controller
embedded PROFINET
Controller
EPXPNS001 RSTi-EP PROFINET Scanner Head-End for RSTi-EP I/O system. Exchanges I/O data and
Alarms with PROFINET Controller. Scans modules installed
in its I/O system.
Components of the RX3i PROFINET network consist of a PACSystems RX3i PROFINET Controller
communicating with IO Devices on the PROFINET bus.
The PROFINET Controller may be an embedded PROFINET Controller (CPL410, CPE400 or CPE330 or CPE100/
CPE115) or a rack-mounted PNC001 module located in the RX3i CPU rack. For rack-mounted PNC001 units, the
main RX3i rack can include up to four PNC001 modules, each communicating with its own high-speed network.
IO Devices on the network can consist of the I/O modules installed in a rack, each containing a PROFINET
Scanner (PNS) as its head-end, such as the GE products listed above. The network may also include a wide
range of third-party IO Devices, such as pressure gauges and motor actuators, that are connected directly to
the PROFINET network.

1.6.1 Compression
Due to the smaller memory capacities of CPE302, CPE305 and CPE310, these CPUs require "Compression"
when attaching RX3i PNS or CEP to their PROFINET configuration.
• CPE302: User MUST use Target PLC parameter with "Compression" set to HIGH.
• CPE305: User MUST use Target PLC parameter with "Compression" set to MODERATE.
• CPE310: User can use Target PLC parameter "Compression" set to NORMAL.
• All other CPUs: User can choose to use "Compression" or not.
GFK-2571P July 2018 15

1.6.2 Basic System: One RX3i CPU and One PROFINET Controller using
a single port
Figure 6 shows a basic system with one PACSystems RX3i CPU node having one PROFINET Controller, and one
PROFINET network with three VersaMax Scanners and one third-party IO-Device. Up to 128 IO-Devices can be
installed on an RX3i PROFINET network. The VersaMax PNS and many types of third-party IO-Devices interface
multiple devices such as I/O modules to the PROFINET network.
RX3i CPU Node with

PROFINET Controller
PROFINET IO LAN
...
3rd Party
IO-Device 3
IO-Device 1 IO-Device 64
IO-Device 2
Figure 6: RX3i System with one PROFINET Controller and one PROFINET LAN
.

1.6.3 Basic System: One RX3i CPU and One PROFINET Controller using
multiple ports
The illustration below shows a basic system with one PACSystems RX3i CPU node that has one RX3i PROFINET
Controller module controlling one PROFINET network. The network can connect up to 128 compatible IO-
Devices, including any combination of GE PROFINET Scanners and third-party IO-Devices.
Figure 7 shows one RX3i PROFINET Controller that is directly connected to four separate IO-Devices in a Star
topology. Although each IO-Device is connected to a separate Ethernet port on the PNC001, they are all on the
same network segment (IO LAN1). The IO-Devices in this example are all VersaMax PROFINET Scanners, but
RX3i PROFINET Scanners (PNS001, PNS101) and third-party IO-Devices may also be used.
IO-Device IO-Device
IO LAN 1 IO LAN 1
RX3i CPU Node

w/ one PNC
IO LAN 1 IO LAN 1
IO-Device IO-Device
Figure 7: RX3i System with one PROFINET Controller and multiple PROFINET LANs
GFK-2571P July 2018 17

1.6.4 Basic System: Third-Party Devices and PME Programmer

Third-party IO Devices can be used with the RX3i PROFINET Controller if their manufacturer provides a GSDML
file that can be imported into Proficy Machine Edition (PME). The GSDML file defines the characteristics of the
IO-Device and its I/O modules. Importing a third-party IO-Device GSDML file and configuring third-party IO-
Devices are described in Chapter 3, and in the Proficy Machine Edition online help.
After receiving a third-party device’s configuration, the RX3i PROFINET Controller connects to the third-party
IO-Device if the device is available, transfers the configuration to the device, and starts exchanging I/O and
alarm data with the device.
Figure 8 shows a programmer connection (for configuration, user logic programming, and monitoring), the
concept of GSDML import, an optional external Ethernet switch, and the ability to connect field buses to a
PROFINET IO-Device. Third-party IO-Devices that have only one Ethernet port may require the use of an
external switch.
Import
Prog/Config Connection
3rd Party
GSDML File
Serial Ethernet
(Optional)
Programmer (PME)
RX3i CPU Node

with PROFINET Controller PROFINET IO LAN Industrial
Ethernet Switch
IO-Device (Optional)
Fieldbus Network
IO-Device
3rd Party
PROFINET
IO-Device
Figure 8: RX3i System interfacing with Third-Party Devices and with PME Programmer

1.6.5 Systems with One RX3i CPU and Two PROFINET Controllers
Both examples in this section show systems with one RX3i CPU that has two PROFINET Controller modules.
The PROFINET network can serve up to 63 IO-Devices (ring topology) or 128 IO-Devices (in star topology).
Note that multiple PNC001 modules in the same rack are not synchronized; that is, no two PNC001 modules
are guaranteed to power up at the same time. PNC001 configuration differences (SFPs, etc.) can also cause
variations in PNC001 power-up times.
If two (or more) PNC001 modules are in a main rack and devices owned by one PNC001 are routed through the
switch on a different PNC001 in the same rack, devices may show a Loss of Device fault followed by an Addition
of Device fault during RX3i power-up because the first PNC001 can power up before the second PNC001 has
enabled its Ethernet switch, causing the Loss of Device. Then when the second PNC001 powers up, the device
will show an Addition of Device fault, which is to be expected under these circumstances. Devices will function
normally once added.
As shown in Figure 9, both PROFINET Controllers are connected to the same network.
NOTE:
Daisy-chain shown for clarity.
RX3i CPU Node with A star or ring topology
2 PROFINET Controllers is preferred.
IO LAN 1 IO LAN 1 IO LAN 1
Figure 9: RX3i System with two PNC001 Modules and one Daisy-Chain PROFINET LAN
GFK-2571P July 2018 19

In Figure 10, the two PROFINET Controllers are connected to separate networks. The maximum number of IO-
Devices with multiple PROFINET Controllers in the same RX3i controller is 255.
NOTE:
Daisy-chain shown for clarity.
A star or ring topology
is preferred.
RX3i CPU Node
w/ two PNCs
IO LAN 1 IO LAN 2
IO-Device IO-Device
IO-Device IO-Device
Figure 10: RX3i System with two PNC001 modules and two Daisy-Chain PROFINET LANs

1.6.6 One RX3i CPU with Four Controllers on Separate Networks

Figure 11 shows a system with one RX3i CPU node containing the maximum of four RX3i PROFINET
Controllers, with each PROFINET Controller connected to a different network. In this architecture, up to 255 IO-
Devices are allowed, spread across the four networks. Up to 128 IO-Devices can be controlled by any given
PROFINET Controller.
Note that multiple PNC001 modules in the same rack are not synchronized; that is, no two PNC001 modules
are guaranteed to power up at the same time. PNC001 configuration differences (SFPs, etc.) can also cause
variations in PNC001 power-up times.
If two (or more) PNC001 modules are in a main rack and devices owned by one PNC001 are routed through the
switch on a different PNC001 in the same rack, devices may show a Loss of Device fault followed by an Addition
of Device fault during RX3i power-up because the first PNC001 can power up before the second PNC001 has
enabled its Ethernet switch, causing the Loss of Device. Then when the second PNC001 powers up, the device
will show an Addition of Device fault, which is to be expected under these circumstances. Devices will function
normally once added.
IO-Device IO-Device
RX3i CPU Node
with four PNCs
IO-Device IO-Device
IO LAN 1 IO LAN 4
IO LAN 2 IO LAN 3
IO-Device IO-Device
Note: Daisy chain shown for clarity.

A star or ring topology is
preferred.
IO-Device IO-Device
Figure 11: RX3i System with four PNC001 modules and four Daisy-Chain PROFINET LANs
As in the other examples, other GE IO-Devices can be substituted for the VersaMax PROFINET Scanners.
GFK-2571P July 2018 21

1.6.7 Two RX3i CPUs with Two PROFINET Networks and One Ethernet
Network
Figure 12 shows two RX3i CPU nodes, each with one RX3i PROFINET Controller module and one RX3i Ethernet
Transmitter Module (ETM). The PROFINET Controller modules are connected to separate networks (IO LAN1
and IO LAN2 in the illustration). IO LAN1 and IO LAN2 are used for PROFINET IO traffic.
The RX3i Ethernet Transmitter Modules are connected to the same Ethernet LAN (LAN3 in the illustration).
Proficy Machine Edition (PME), HMI, and Historian use LAN3 to configure and monitor the application. LAN3 is
also used for inter-node communication such as EGD, SRTP, and Modbus/TCP. The three separate networks do
not compete for network bandwidth or interfere with one another.
Prog/Config
Connection
Proficy HMI
Programmer
(PME) LAN 3 Historian
EGD/SRTP/ModbusTCP/etc.
RX3i Controller CPU Node RX3i Controller CPU Node

IO LAN 1 with one PROFINET IO LAN 2 with one PROFINET
Controller and one ETM Controller and one ETM
NOTE:
Daisy-chain shown for
clarity. A star or ring
topology is preferred.
IO-Device 3
Figure 12: RX3i System with two PROFINET LANs & one Ethernet LAN

1.6.8 Systems that use PROFINET System Redundancy (PNSR)
PACSystems support S2 type PNSR, as diagrammed in Figure 13. The ‘S’ denotes that the IO Device has single
network support. PROFINET defines an ‘R’ option in which the IO Device may have redundant network
interfaces which could be on different networks. The ‘2’ denotes that the network supports two connections as
a set.
Note that in each case the firmware installed in the PROFINET Controller and in the PROFINET Device must
themselves support PNSR. PNSR allows a set of Hot standby CPU controllers to have an active and hot backup
connection to an IO device, so that if something fails in one CPU controller, the other CPU controller can
continue IO operations without disruption.
PNSR relies entirely on PROFINET features to support this configuration. PACSystems only supports PNSR in
Dual HWC Hot Standby systems. Within a PNSR system, simplex IO devices may be controlled by one CPU
Controller in addition to redundant IO devices which are controlled by the Active CPU of the Hot Standby
system. When the CPU controller which is controlling a simplex IO Device is stopped, that IO Device is lost.
The PROFINET PNSR Network may be either Ring or Star formation. Using a Ring formation with the Media
Redundancy Protocol (refer to Chapter 6), is often useful with PNSR systems since a single cable failure is
handled by MRP allowing both IO Controllers to maintain connection with the IO devices.
Figure 13: PROFINET System Redundancy S2
GFK-2571P July 2018 23

1.6.9 Systems that use Hot Standby CPU Redundancy

Figure 14 shows a Hot Standby CPU Redundancy system that uses a PROFINET I/O network with
MRP ring topology. Use of MRP ring topology is recommended because it eliminates the I/O network
as a single point of failure. If elimination of a single point of failure is not required, a star topology can
be used.
These systems are described in the PACSystems Hot Standby CPU Redundancy User’s Manual,
GFK-2308F or later.
1.6.9.1 Hot Standby CPU Redundancy Network with MRP Ring Topology
Supervisory Ethernet Network
(Up to 8 separate networks
allowed)
HMI Historian PME HMI
Redundant IP
Redundancy Links
RX3i C E R R P RX3i C E R R P
P P
Primary P S S
P T M M N Secondary PS S
P T M M N
Controller U M X X C Controller U M X X C
PROFINET I/O Network

RING
(Up to 4 separate networks allowed)
P P P P
P P I I I I P P I I I I P P I I I I P P I I I I
N N N N
1 2 O O O O 1 2 O O O O 1 2 O O O O 1 2 O O O O
S S S S
Remote IO Device Remote IO Device Remote IO Device Remote IO Device
Figure 14: RX3i Hot Standby CPU Redundancy Network with MRP Ring Topology

1.6.10 RSTi-EP Standalone CPU with embedded PROFINET Controller

using a single port
Figure 15 shows a basic system with one PACSystems RSTi-EP CPU node with embedded PROFINET Controller,
and one PROFINET network with two VersaMax, one RSTi-EP Scanners and one third-party IO-Device. Up to 8
IO-Devices can be installed on an RSTi-EP PROFINET network.
RSTi-EP EPSCPE100
With Embedded
PROFINET
PROFINET IO LAN
...
3rd Party
IO-Device 3
IO-Device 2
Figure 15: RSTi-EP System with embedded PROFINET Controller and one PROFINET LAN
GFK-2571P July 2018 25


using multiple ports
The illustration above shows a basic system with one PACSystems RSTi-EP CPU node with embedded
PROFINET Controller controlling one PROFINET network. The network can connect up to 8 compatible IO-
Devices, including any combination of GE PROFINET Scanners and third-party IO-Devices.
Figure 16 shows one RSTi-EP CPE100/CPE115 embedded PROFINET Controller that is directly connected to
three separate IO-Devices in a Star topology. Although each IO-Device is connected to a separate Ethernet
port, they are all on the same network segment (IO LAN1). The IO-Devices in this example are one VersaMax
two RSTi-EP PROFINET Scanners, but RX3i PROFINET Scanners (PNS001, PNS101) and third-party IO-Devices
may also be used.
Figure 16: RX3i System with one PROFINET Controller and multiple PROFINET LANs


using MRP
Figure 17 shows one RSTi-EP CPE100/CPE115 embedded PROFINET Controller that uses a PROFINET
I/O network with MRP ring topology. CPE100/CPE115 LAN2 Port 2 & Port 3 support Media
Redundancy and on configuring MRP as Manager / Client LAN2 Port 4 can be used for connecting
Simplex PROFINET devices or any other Ethernet Protocols such as Modbus, SRTP, and EGD. Use of
MRP ring topology is recommended because it eliminates the I/O network as a single point of failure.
If elimination of a single point of failure is not required, a star topology can be used.
Figure 17: RX3i System with one PROFINET Controller and PROFINET IO Network MRP
GFK-2571P July 2018 27

1.7 Glossary
AR Application Relationship. PROFINET term for a relationship that is established between an
IO-Controller/Supervisor and IO-Device. For any data to be exchanged between an IO-
Controller/Supervisor and a given IO-Device, an Application Relationship must be established.
Within the Application Relationship, various Communication Relationships (CRs) are then
established for the different types of data to be exchanged.
Broadcast In Ethernet, the transmission of a network message to all hosts on the network.
CLI Command Line Interface
CPU Node In a PACSystems RX3i PROFINET network, a CPU Node is a node in which a PACSystems RX3i CPU
is connected to the PROFINET network.
CR Communication Relationship. PROFINET term for a channel that is established within an
Application Relationship (AR) to transfer specific data between an IO-Controller/Supervisor and a
given IO-Device. Multiple CRs are established within an AR to transfer data.
Critical An Ethernet port connection on the PROFINET I/O Controller that is configured as a critical port.
Network Port When the last Critical Network Port is disconnected from its network, a diagnostic fault is logged.
In a redundancy system where the PROFINET I/O Controller is controlling redundant devices, this
results in a CPU redundancy role-switch with the CPU placed into Stop/Fault mode.
DAP Device Access Point. This access point is used to address an IO-Device as an entity.
Gratuitous An Address Resolution Protocol (ARP) request sent by the host to resolve its own IP Address.
ARPs
GSDML General Station Description Markup Language - definition of PROFINET Device Characteristics.
IOC PROFINET IO-Controller
IOD PROFINET IO-Device
IOCR Input Output Communication Relationship – describes the type (input/output) and amount of I/O
data to be transferred, the sequence of the transfers and the transfer cycle between a PROFINET
IO-Controller (or IO-Supervisor) and a PROFINET IO-Device.
IOCS PROFINET Input/Output Consumer Status is transmitted on the PROFINET network to provide
feedback on Input Data for an IO controller and Output Data for an IO device.
IOPS PROFINET Input/Output Provider Status is transmitted on the PROFINET network to provide
feedback on Output Data for an IO controller and the Input Data for an IO device.
IOxS PROFINET abbreviation for the IOCS and/or IOPS (see above).
LLDP Link Layer Discovery Protocol. IEEE standardized protocol used by network devices to advertise
their identity and capabilities.
LLDPDU Link Layer Discovery Protocol Data Unit.
MAC Media Access Control address (MAC address)
MAU Medium Attachment Unit
MIB Management Information Basis
MRC Media Redundancy Client. Within Media Redundancy Protocol, an MRC is responsible for helping
the MRM detect breaks/no breaks in the ring.
MRM Media Redundancy Manager. Within Media Redundancy Protocol, an MRM is responsible for
ensuring that the ring does not have a closed loop, while simultaneously ensuring maximal
connectivity between nodes on the ring.
MRP Media Redundancy Protocol. An Ethernet protocol that provides redundant paths for PROFINET-IO
cyclic traffic by supporting a ring topology.
Multicast In Ethernet, the transmission of a network message to all hosts within a host group.
NOS Name of Station
OID Object Identifier
Phase If the IOCR Update Period is greater than the Send Clock time, the Update Period is divided into
multiple phases where each phase is equal to one Send Clock.

Glossary, continued
PNC PROFINET Controller: Typically, the generic PROFINET Controller function. PNC001 represents a
slot-mounted product (IC695PNC001). Embedded PROFINET Controllers may be configured on
LAN2 for CPL410, CPE400, CPE330 and CPE100/CPE115. Both embedded and slot-mounted
perform the same functions on the PROFINET network, but there are differences to be noted in
installation, configuration, operation and performance.
PNS PROFINET Scanner. Head-end module that controls I/O in rack and communicates with PROFINET
network. Both RX3i (IC695PNS001, IC695PNS101) and VersaMax (IC200PNS001, IC200PNS002)
modules are discussed in this manual.
PNSR PROFINET System Redundancy: the PROFINET processes and mechanisms by which an IO-Device
is controlled by multiple IOCs in redundant PLCs.
RDO Record Data Object. Services used to read and write structured data stored in a PROFINET IO-
Device.
Reduction Ratio Along with Send Clock determines the Update Period for a PROFINET cyclic data transfer between
two devices (see IOCR). The Update Period equals the Reduction Ratio multiplied by the Send Clock
time. For example, if the Reduction Ratio is 4 and the Send Clock is 1ms, the Update Period is 4ms.
Remote Node For an RX3i PROFINET network, a Remote Node is any PROFINET IO-Device, such as a rack of I/O
modules with a Remote Scanner or a third party PROFINET IO-Device.
RIV Reference ID Variables
RTA Real-Time Acyclic. A PROFINET-IO Mechanism used to exchange non-periodic data such as alarms.
RTC Real-Time Cyclic. A PROFINET-IO Mechanism used to exchange input and output data.
Send Clock Value between 1 and 128 inclusive in units of 31.25 µs (equivalent to a range of 31.25 µs to 4 ms)
used to calculate the Update Period for a PROFINET cyclic data transfer between two devices (see
IOCR). The Send Clock is the basis for all other scheduling parameters.
Send Offset The time to delay a scheduled PROFINET cyclic data transfer frame.
Measured in nanoseconds from 0 to 3,999,999. Must be less than the Send Clock time.
SFP Small Form-factor Pluggable. Pluggable, hot-swappable transceivers.
SNMP Simple Network Management Protocol. UDP-based network protocol that facilitates the exchange
of management information between network devices.
Status Bits Module status data in RX3i CPU reference memory.
Submodule PROFINET-IO representation of the smallest configurable entity of a PROFINET Module.
SVC_REQ Service Request Function Block. A control system service initiated by the RX3i CPU.
TLV Type-Length-Value
Unicast In Ethernet, the transmission of a network message to an individual host.
Update Period The time between PROFINET cyclic data transfers between an IO-Controller and an IO-Device.
USB Universal Serial Bus
WinLoader A software utility used to download and install firmware upgrades via a serial port.
GFK-2571P July 2018 29

1.8 Documentation
PACSystems Manuals
PACSystems RX7i, RX3i and RSTi-EP CPU Reference Manual GFK-2222
PACSystems RX7i, RX3i and RSTi-EP CPU Programmer’s Reference Manual GFK-2950
PACSystems Hot Standby CPU Redundancy User Manual GFK-2308
PACSystems Battery and Energy Pack Manual GFK-2741
Proficy Machine Edition Logic Developer Getting Started GFK-1918
Proficy Process Systems Getting Started Guide GFK-2487
PACSystems RXi, RX3i, RX7i and RSTi-EP Controller Secure Deployment Guide GFK-2830
RX3i Manuals
PACSystems RX3i System Manual GFK-2314
PACSystems RX3i PROFINET Controller Command Line Interface Manual GFK-2572
PACSystems RX3i Max-On Hot Standby Redundancy User’s Manual GFK-2409
PACSystems RX3i PROFINET Scanner Manual GFK-2737
PACSystems RX3i CEP PROFINET Scanner User Manual GFK-2883
PACSystems HART Pass Through User Manual GFK-2929
PACSystems RX3i PROFINET Scanner Important Product Information GFK-2573
VersaMax Manuals
VersaMax PROFINET Scanner Manual GFK-2721
In addition to these manuals, datasheets and product update documents describe individual modules and
product revisions. The most recent PACSystems documentation is available on the support website
www.geautomation.com.
.

Chapter 2 Installation
This chapter provides instructions for installing PACSystems RX3i PROFINET Controller modules.
• Pre-Installation check
• Removing the backplane knockout
• Module installation and removal
• Hot insertion and removal
• Port connections
• Installing SFP devices
• LED indications
• Installing the USB Port Driver
• Firmware updates
• Time synchronization with RX3i CPU
For additional information about system installation, also refer to the PACSystems RX3i Systems Manual, GFK-
2314.
GFK-2571P July 2018 31

Chapter 2. Installation
2.1 Pre-Installation Check

Upon receiving your RX3i equipment, carefully inspect all shipping containers for damage. If any part of the
system is damaged, notify the carrier immediately. The damaged shipping container should be saved as
evidence for inspection by the carrier.
As the consignee, it is your responsibility to register a claim with the carrier for damage incurred during
shipment. However, Automation & Controls at GE Energy Connections will fully cooperate with you, should
such action be necessary.
After unpacking the RX3i equipment, record all serial numbers. Serial numbers are required if you should need
to contact Customer Care during the warranty period. All shipping containers and all packing material should
be saved should it be necessary to transport or ship any part of the system.
Verify that all components of the system have been received and that they agree with your order. If the system
received does not agree with your order, contact Customer Care.
If you need technical help, contact Technical Support. For phone numbers and email addresses, see the
Contact Information page in the front of this manual.

2.2 Installation in Hazardous Areas

EQUIPMENT LABELED WITH REFERENCE TO CLASS I, GROUPS A, B, C & D, DIV. 2 HAZARDOUS LOCATIONS IS
SUITABLE FOR USE IN CLASS I, DIVISION 2, GROUPS A, B, C, D OR NON-HAZARDOUS LOCATIONS ONLY
EXPLOSION HAZARD - SUBSTITUTION OF COMPONENTS MAY IMPAIR

SUITABILITY FOR CLASS I, DIVISION 2.
Warning
EXPLOSION HAZARD - WHEN IN HAZARDOUS LOCATIONS, TURN OFF POWER

BEFORE REPLACING OR WIRING MODULES.
Warning
EXPLOSION HAZARD - DO NOT CONNECT OR DISCONNECT EQUIPMENT

UNLESS POWER HAS BEEN SWITCHED OFF OR THE AREA IS KNOWN TO BE
NON-HAZARDOUS.
Warning
EXPLOSION HAZARD - USB PORT IS ONLY FOR USE IN NON-HAZARDOUS

LOCATIONS, DO NOT USE UNLESS AREA IS KNOWN TO BE NON-HAZARDOUS.
Warning
2.2.1 ATEX Marking

II 3 G Ex nA IIC T5 X Ta: 0 - 60C
GFK-2571P July 2018 33

2.3 Removing the Backplane Knockout

The IC695PNC001 must be installed in the main (CPU) rack of the RX3i system, using a Universal Backplane
such as IC695CHS007, CHS012 or CHS016. For details, refer to the PACSystems RX3i System Manual,
GFK-2314.
The rear of the PNC001-Ax module has an exposed heat sink and backplane connector. Before inserting the
module into the backplane, remove the plastic knockout in the slot into which the module will be placed. The
installation slot must match the slot selected for the module in the Proficy Machine Edition (PME) hardware
configuration. This action is not required for PNC001-Bxxx. However, if the knockout has been previously
removed, the PNC001-Bxxx can still be inserted into that slot location.
Figure 18: RX3i Backplane showing Removable Plastic Knockout

2.4 Module Installation

• RX3i rack power may be off or on (see Hot
Insertion and Removal for details).
• Holding the module firmly, align the module
with the correct slot and connector.
• Engage the module’s rear pivot hook in the
notch on the top of the backplane (1).
• Swing the module down (2) until the module’s
connector engages the backplane’s backplane
connector, and the release lever (PNC001-Ax
only) on the bottom of the module snaps into
place in the bottom module retainer (3).
• Visually inspect the module to be sure it is
properly seated.
• PNC001-Ax: Tighten the heat sink screw on the
front of the module in the threaded hole in the
back plate to 6 in-lbs (0.68 Nm), using a flat-tip Figure 19: Install Module into RX3i Backplane
screwdriver.
• PNC001-Bxxx: Secure the bottom of the module
to the backplane using the two captive Phillip’s
head machine screws provided with the module
(not shown in diagram).
2.5 Module Removal

• RX3i rack power may be off or on (see Hot
Insertion and Removal for details).
• PNC001-Ax: Loosen the heat sink screw on the
front of the module to release the heat sink
from the backplane’s aluminum back plate.
• PNC001-Ax: Locate the release lever at the
bottom of the module and firmly press upward
(1), toward the module.
• PNC001-Bxxx: Loosen the two captive Phillip’s
head machine screws at the bottom of the
module.
• While holding the module firmly and fully
depressing the release lever (PNC001-Ax only),
pivot the module upward until its connector is
out of the backplane (2).
• Lift the module up and away from the
backplane to disengage the pivot hook (3). Figure 20: Remove Module from RX3i Backplane
GFK-2571P July 2018 35

2.6 Hot Insertion and Removal

Modules in a Universal Backplane can be installed or removed while power is applied to the system. This
includes backplane power and field power supplied to the module. For a full discussion of this topic, refer to the
Hot Insertion and Removal section in the PACSystems RX3i System Manual, GFK-2314.
The PNC001 module must be properly seated with the latch engaged (PNC001-Ax only) and all pins connected
within 2 seconds. For removal, the module must be completely disengaged within 2 seconds. It is important
that the module not remain partially inserted during the insertion or removal process. There must be at a
minimum of two seconds between the removal and insertion of modules.
Inserting or removing a module with power applied to the system may cause an
electrical arc. This can result in unexpected and potentially dangerous action by
field devices. Arcing is an explosion risk in hazardous locations. Be sure that the
area is non-hazardous or remove system power appropriately before removing
or inserting a module.
Warning
If the surrounding air operating temperature of the PNC001 module is greater

than 40°C (104°F), SFP devices could reach operating temperatures over 70°C
(158°F). Under these conditions, for your safety, do not use bare hands to
remove an SFP device from the SFP cage. Use protective gloves or a tool
(needle-nose pliers) to avoid handling the hot SFP device directly when
Warning removing the SFP device.
If an RX3i PROFINET Controller is extracted from a powered RX3i backplane, it

loses power immediately, which may result in data loss. Do not remove or
insert the device while downloading hardware configuration to the system.
When the module is plugged back into a powered backplane, the PNC001
module restores data from the internal non-volatile memory. If, however, the
RX3i CPU has configuration data for the PROFINET Controller, it re-delivers the
Caution data to the PNC001 module, superseding parameters previously stored in non-
volatile PNC001 memory.
2.6.1.1 Fault Notifications

Removing a PROFINET Controller causes a Loss of IOC fault in the RX3i CPU’s I/O Fault Table and inserting a
PROFINET Controller causes an Addition of IOC fault in the I/O Fault Table.

2.7 Ethernet Port Connections

Each port on an RX3i PROFINET Controller operates independently. This is true for all ports on the PNC001
module and for ports assigned to embedded PROFINET Controllers. In this way, devices that operate at
different speeds and/or duplex modes may be attached to a compatible port. Each port automatically detects
the attached cable and functions properly with either straight-through or crossover cables.
Note: All PROFINET Controller ports operate in auto-negotiate mode only. All PROFINET devices and
switches that are connected to the PROFINET Controller should be configured to use auto-
negotiation.
Figure 21: Ethernet Ports on PNC001 Module
2.7.1 PROFINET Network Connections

Connections to the PROFINET Controller can be made using standard cables. The PROFINET Controller can be
connected to only one PROFINET network. However, different devices on the same LAN can be connected via
more than one port.
Note: Shielded cable is required for 1 Gbps operation.
Do not connect two or more ports on the PROFINET Controller to the same
device, either directly or indirectly, unless Media Redundancy is enabled in
the PROFINET Controller’s configuration. If Media Redundancy will be used,
do not close the network ring until after a Media Redundancy configuration
that contains one node as a Media Redundancy Manager (MRM) has been
downloaded to the PROFINET Controller. If a Media Redundancy Manager is
not present, packets can continuously cycle on the network, preventing
Caution normal operation. For more information refer to Chapter 6, Redundant
Media.
2.7.2 RJ45 Port Connections

The RJ45 ports on the underside of the PNC001 module can be used for PROFINET network connections or for
general Ethernet communications on a 10BaseT, 100BaseTX, or 1000Base-T IEEE 802.3 network. Typical
switches, hubs, or repeaters support 6 to 12 nodes connected in a star wiring topology.
For embedded PROFINET Controllers, LAN2, when configured as an Ethernet port, does not permit PROFINET
functions. However, once configured as a PROFINET Controller, LAN2 continues to support the Ethernet
modality. In other words, it is possible to have Ethernet protocols running on the network while it is configured
for PROFINET. This can be tolerated so long as the Ethernet traffic does not impede or degrade PROFINET
operations.
GFK-2571P July 2018 37

10BaseT: uses a twisted pair cable of up to 100 meters in length between a node and another node, switch,
hub, or repeater. 10Mbs may be used for the Command Line Interface (CLI) and general Ethernet traffic, but
not for PROFINET communications.
100BaseTX: uses a cable of up to 100 meters in length between a node and another node, switch, hub, or
repeater. The cable should be data grade Category 5 or better unshielded twisted pair (UTP) or shielded
twisted pair (STP).
1000BaseT: uses a cable of up to 100 meters in length between a node and another node, switch, hub, or
repeater. The cable should be data grade Category 5 or better shielded cable.
2.7.2.1 Network Cabling and Connector Types
Copper: up to 100 Meters between Devices
All Automation & Controls products from GE Energy Connections use RJ45 connectors for copper connections.
Copper cabling and connections are easily available in the general market and support distances of up to
100m.
Figure 22: Interconnect using Copper Cables / RJ45 Connectors

Multi-Mode Fiber: up to 2 km between Devices
Multi-Mode Fiber supports two types of connectors, LC and SC. The LC connector is used on SFPs on the RX3i
PNC001 and on the PNS modules. The SC connector is used on the VersaMax PNS. Cables are available with
LC-to-LC connectors and LC-to-SC connectors to match the different connector formats. Multi-Mode fiber can
support distances up to 2Km at 100Mbps. When using fiber, pay particular attention to the cable connector
and cable radius clearance requirements in cabinet planning and layout.
Figure 23: Interconnect using Multi-Mode Fiber

Single-Mode Fiber: up to 70 km between Devices
Single-Mode Fiber is supported between SFPs using the LC connector. Single-Mode fiber can support distances
up to 70 km. As with the Multi-mode fiber, pay attention to the cable connector, radius, and minimum length
requirements in planning the installation.
Figure 24: Interconnect using Single-Mode Fiber

2.7.2.2 Network Cabling and Connector Examples
Figure 25: CAT5e/CAT6 (shielded or unshielded) with RJ 45 Connector
Figure 26: Multi-Mode Fiber with LC connector
Figure 27: Single-Mode Fiber with LC connector
GFK-2571P July 2018 39

2.7.3 Installing SFP Devices

SFP (Small Form-Factor Pluggable) devices can be installed in Port 3 and Port 4 of the PROFINET Controller.
See section 2.7.3.1, SFP Modules for Ethernet Ports, for a list of supported SFP devices, media types and
distances. The specific SFP module installed in each cage must be defined in the Proficy Machine Edition
configuration of the PNC001.
Keep the protective plug installed in the SFP device. Following the manufacturer’s installation instructions,
insert the device with its electrical contacts oriented toward the inside of the PNC001 until it clicks into place.
Figure 28: Method for Attaching SFP Device Connector to PNC001 Port
Optical SFPs use an invisible laser to generate a fiber-optic signal. Always

keep the port covered if a cable is not installed. Do not peer into the open
port if a cable is not installed
Warning
Remove the protective plug to install the cable.

When the PNC001 powers up, it automatically detects devices plugged into the SFP cages, their type (fiber,
copper, etc.) and their link speed. If an SFP device has been included in the configuration but is not present in
the specified cage, the PNC001 logs a Loss of Network Port entry to its Local Log Table. If possible, the
PROFINET Controller also logs a fault to the associated RX3i I/O Fault Table. The module continues to operate
with a Loss of Network Port fault.
If the installed SFP device is different from what has been configured, the PNC001 logs a mismatch entry to its
Local Log table. If possible, it also logs an informational fault to the associated RX3i controller’s Fault Table. The
module tries to configure and use the SFP if it is compatible (as listed in SFP Modules for Ethernet Ports). If the
PROFINET Controller detects an unsupported SFP type on power-up or when the SFP is inserted, the PNC001
adds an entry into its Local Log Table and the RX3i I/O Fault Table (if possible) and turns the associated port
LED red.

2.7.3.1 SFP Modules for Ethernet Ports

Each Small Form-Factor Pluggable (SFP) cage on the bottom of a PROFINET Controller module can accept a:
• 10/100/1000 Mbps copper SFP,
• 100Mbps Single-Mode Fiber SFP,
• 100Mbps Multi-Mode Fiber SFP,
• 1000Mbps Single-Mode Fiber SFP, or
• 1000Mbps Multi-Mode Fiber SFP device.
SFP devices can be removed/replaced during module operation. The RX3i PROFINET Controller
supports the SFP devices listed below. An SFP type other than those listed below can be configured
as a GENERIC SFP in Proficy Machine Edition. The RX3i PROFINET Controller will attempt to operate
with a generic SFP that identifies itself as an Ethernet SFP. Since SFP types other than those listed
below have not been validated, correct operation cannot be guaranteed.
SFP Type Wavelength Media Type Core Size Modal Distance

(nm) (µm) Bandwidth (MHz (m)
– km)
100BASE-FX 1300 MMF 62.5 500 2 – 2,000 (Full-Duplex)
50 400 2 – 400 (Half-Duplex)
50 500
100BASE-LX10 1300 SMF 9 - 2 – 10,000
1000BASE-SX 850 MMF 62.5 160 2 – 220
200 2 – 275
50 400 2 – 500
500 2 – 550
1000BASE-LX 1300 SMF 9 - 2 – 10,000
1000BASE-ZX 1550 SMF 9 - 2 – 70,000
10/100/1000BASE-T - CAT5/CAT5e/CAT - - 100 (maximum)
6
GFK-2571P July 2018 41

2.7.3.2 Typical SFP Modules

Below are images of the two types of Ethernet SFPs. The Single- and Multi-Mode Fiber SFPs accept an LC
Connector. The Copper SFPs accept an RJ45 connector.
Figure 29: Fiber SFP showing LC Connector Figure 30: Copper SFP showing RJ45 Connector
2.7.4 Removing SFP Devices

If the surrounding air operating temperature of the PNC001 module is greater
than 40°C (104°F), SFP devices could reach operating temperatures over 70°C
(158°F). Under these conditions, for your safety, do not use bare hands to
remove an SFP device from the SFP cage. Use protective gloves or a tool
(needle-nose pliers) to avoid handling the hot SFP device directly when
Warning removing the SFP device.
Remove the cable from the SFP device. If the device has a latching mechanism such as a bale clasp, open it
gently. Do not pull on the latching mechanism. Hold the sides of the SFP device and pull it out of the PROFINET
Controller port.

2.8 PNC001 LED Behavior

2.8.1 Power-up LED Patterns
At power-up, the LEDs show the blink patterns described below. The LEDs also blink diagnostic patterns for
certain operating errors and for module identification. See Chapter 5, Diagnostics for a description of those
special blink patterns.
Step LED/Blink pattern Description
1 All LEDs OFF Normal operation
1.1 ACTIVE LED solid green Normal operation

(PNC001-Bxxx only)
1.2 CONFIG LED solid green Normal operation

(PNC001-Bxxx only)
2 STATUS LED solid green Normal operation
OK LED blinks Amber with Fatal Initialization or Diagnostics Failure,

special blink code Hardware Module Identity Information not
available
OK, LAN, and STATUS LEDs Invalid firmware detected. Module is waiting
blink green in unison (1 Hz) for firmware update. Blink pattern continues
during firmware update.
3 LAN and STATUS LED solid Normal operation

green (PNC001-Ax only)
4 LAN LED solid green Normal operation
LAN and STATUS LED blink Update of module firmware. After the
green (1 Hz) automatic update completes, the LEDs blink
Amber and the module resets, which restarts
the power-up process.
5 OK LED solid green Normal operation. Power up completed and
backplane communications established.
Figure 31: PNC001-Bxxx
Front View showing LEDs
OK LED blinks green (1 Hz) Module power-up completed, but
communication not yet established over the
RX3i backplane.
Note: Under certain ambient operating temperatures, the PROFINET Controller may momentarily display
the overtemperature pattern during power up, while it is calibrating its thermal protection functions.
This indication may be ignored, and no overtemperature entry is added to the Local Log table, the
Controller Fault Table or I/O Fault Table.
For details, see Special LED Blink Patterns in Chapter 5, Diagnostics.
GFK-2571P July 2018 43

2.8.2 Detailed LED Descriptions

2.8.2.1 OK LED
The OK LED indicates whether the module is able to perform normal operation.
Green, ON OK
Green, blink pattern Fatal error. Flashes once between error codes blinked on the OK LED
Amber, blink pattern Fatal error
OFF Not OK
2.8.2.2 LAN LED

The LAN LED indicates access to and activity on the Ethernet network. The LAN LED indicates network packets
are being processed by the network interface (not just passing through the embedded switch).
Blinking ON The module’s network interface is active
Blink pattern Fatal error. Flashes once between error codes blinked on the OK LED
OFF No activity
2.8.2.3 STATUS LED

The STATUS LED indicates the condition of the PROFINET Controller during normal operation. It indicates
whether an entry other than the startup event is present in the module’s Local Log. STATUS can also indicate
whether any of the MAC addresses are invalid.
The STATUS LED state is reset when the Local Log is cleared. For more information see the Command Line
Interface clear log command.
Green, ON No new Local Log table entries
OFF New Local Log table entry
Green, blink pattern Fatal error. Flashes once between error codes blinked on the OK LED. Chapter 5,
Diagnostics provides more detailed information about this LED’s additional
behavior during fatal error conditions.
Red, blinking Invalid MAC address (all MAC addresses are validated; error indicates if any
address is bad).
2.8.2.4 CONFIG LED

The CONFIG LED indicates whether the module has received its configuration from the RX3i CPU.
Green, ON Configured
OFF Not configured
2.8.2.5 USB LED

The USB LED (PNC001-Ax only) indicates activity on the USB port.
Green, Blinking USB port activity
OFF No USB port activity

2.8.2.6 ACTIVE LED

The ACTIVE LED indicates the overall status of PROFINET connections.
Green, ON All configured PROFINET devices have established PROFINET connections
Amber, ON At least one configured PROFINET device has established a PROFINET

connection, but other configured PROFINET devices are not connected
OFF No configured PROFINET Devices have established PROFINET connections to
the PROFINET Controller, or hardware configuration is cleared.
2.8.2.7 Port LEDs

The PNC001 has LEDs that indicate link speed, link connection and link activity corresponding to the four
possible external switched Ethernet ports. The layout and behavior of these LEDs is different depending on the
revision of the PNC as shown below.
Revision -Bxxx:
Port Number LED (Note: here the digit representing the port number is backlit by the corresponding LED).
Red, ON Port 3 and 4 only: Error such as incompatible SFP.
OFF No Port error.
1000 Speed LED (individual LED for each port)
Green, ON Link connected, 1000 Mbps
Green blinking Port active, 1000 Mbps
OFF The associated Ethernet port is not connected to an active link at 1000Mbps
Green, ON Link connected, 100 Mbps.
Green, blinking Port active, 100 Mbps
Green, ON Link connected, 10 Mbps.
Revision -Ax:
LEDs marked 1,2,3,4 behave as follows:
Blue, ON Link connected, 1000 Mbps
Blue, blinking Port active, 1000 Mbps
Green, ON Link connected, 100 Mbps
Purple, ON Link connected, 10 Mbps
Purple, blinking Port active, 10 Mbps
OFF The associated Ethernet port is not connected to an active link
Red, ON Port 3 and port 4 only. Incompatible SFP plugged into port.
GFK-2571P July 2018 45

2.9 Installing the USB Port Driver

The USB Ports on CPUs which support the embedded PROFINET function operate independently of the
PROFINET Controller function itself. Refer to the documentation for the related CPU.
For the slot-mounted PNC001 (-Ax module only), set up use of the module’s USB port in either of these ways:
1. Run the provided driver-install application before connecting the computer’s USB port to the USB port on
the PNC001 module for the first time.
2. With the provided installation files accessible on either a local or network drive, attach the PC USB port to
the Rx3i IO LAN USB port.
a) Windows opens a New Hardware Found Wizard dialog. Within the wizard application, enter the
location of the provided installation files.
b) Windows then installs the USB driver compatible with the USB port.
The computer automatically assigns a serial port name for the USB port on the PNC001 module. A unique serial
port number will be used for each PNC001 module. The serial port name is COM followed by the next available
number from 1 to 256. After the computer assigns the module’s USB port a COM port name, it uses the same
name each time it connects to the module (except for a special case described below).
If the computer has already assigned all its available port names (COM1 through COM256), the next device to
attach is assigned a previously-used COM Port name:
1. If the last assigned COM port name was COM256, the next COM port name assigned is the first
unconnected COM port after the physical serial communications ports.
2. If the last assigned COM port name was not COM256, the next COM port name assigned is the first
unconnected COM port in sequence.
After the initial installation process, the same computer can be attached to other RX3i PNC001 modules
without additional installation steps. The virtual serial port name is automatically assigned when the device is
attached to the computer.
Serial port settings must be 115200 baud, 8-None-1, with no flow control.

2.10 Firmware Updates

2.10.1 PNC001 Firmware Updates
Firmware for PNC001-Ax is only compatible with PNC001-Ax hardware. Firmware for PNC001-Bxxx is only
compatible with PNC001-Bxxx hardware. They are not interchangeable.
The RX3i PROFINET Controller firmware is updated via the CPU in the rack in which the PNC001 module is
located. If the CPU is equipped with a serial port, use the WinLoader utility. If the CPU is not equipped with a
serial port, use the http/web-based firmware update method. For detailed instructions, see the firmware
upgrade instructions included in the ZIP file, along with the firmware image file.
The current firmware version of the RX3i PROFINET Controller may be obtained using either the Proficy
Machine Edition programmer (Online Commands->Show Status->Details), or (for PNC001-Ax only) the
Command Line Interface node command.
2.10.2 Firmware Updates for Embedded PROFINET

For firmware updates to those CPUs that support embedded PROFINET, refer to the documentation for the
related CPU. Updating the CPU firmware automatically updates the embedded PROFINET component.
GFK-2571P July 2018 47

2.11 PNC001 Time Synchronization with the Host RX3i CPU

The internal clock value of a PNC001 module may be displayed in Command Line Interface (CLI) commands,
and it is used to timestamp entries in the PROFINET Controller Local Fault Log as they occur.
The internal clock of the PNC001 module is synchronized with the RX3i CPU clock whenever the PNC001
module is:
• powered up, or
• hot-inserted, or
• reset via the Reset pushbutton, or on command from the Command Line Interface.
Storing hardware configuration to the PNC001 module does not cause clock synchronization.
If the host CPU’s time is changed after the PNC001 module synchronizes its own internal clock, the PROFINET
Controller’s internal clock is not automatically synchronized until the PNC001 module is again powered up,
hot-inserted, or reset.
The internal clock of the PNC001 module may be set from the Command Line Interface at any time, using the
time command.

Chapter 3 Configuration
This chapter explains how to configure an RX3i PROFINET Controller and its IO devices in a PACSystems RX3i
controller system. Additional information about RX3i configuration is available in other PACSystems
documentation and in the Logic Developer online help.
This chapter discusses the following topics:
• Configuration Overview
o Basic Configuration Steps
• Configuration Tools
• Configuring an RX3i PROFINET Controller
o The PROFINET Controller’s LAN
o Configuring PROFINET Controller Parameters
• Configuring PROFINET LANs
o Configuring the LAN Properties
• Adding a VersaMax PROFINET Scanner to a LAN
o Configuring VersaMax PNS Parameters
o Adding VersaMax PNS Power Supplies
o Adding VersaMax Modules to a Remote Node
o Adding Power Supplies Between Modules
o Configuring VersaMax Module Parameters
o Configuring Analog Modules that have Jumpers
• Adding a Third-Party IO-Device to a LAN
o Editing Third-Party IO-Device Parameters
o Configuring Sub-modules of an IO-Device
• Viewing / Editing IO-Device Properties
• Assigning IO-Device Names
• Configuring IO-Devices
• After the Configuration is Stored to the RX3i CPU
o Clearing the RX3i Controller Configuration
GFK-2571P July 2018 49

Chapter 3. Configuration
3.1 Configuration Overview

The Proficy Machine Edition PLC Logic Developer programmer is used to create and download the configuration
for an RX3i PROFINET network and its devices.
3.1.1 System Planning

3.1.1.1 Device Ownership
Note that all modules in an IO-Device must belong to the same PROFINET network, that is, they are all owned
by the same PROFINET Controller. I/O modules within an IO-Device cannot be split between PROFINET
Controllers.
3.1.1.2 PROFINET Controller Loading Limits
To prevent overloading of the PROFINET Controller, the maximum number of IO-Devices that can be configured
is limited, per the table below. Note that the loading threshold is different for embedded PROFINET Controllers
(in the CPL410, CPE400, CPE330 and CPE100/CPE115) than in the rack-mounted IC695PNC001. The PROFINET
Controller loading limits are enforced by Proficy Machine Edition.
Devices configured with a longer update periods present smaller data loads to the PROFINET Controller. For
example, a device with an update rate of 2ms presents a load equivalent to that of two devices at 4ms.
3.1.1.3 Maximum Configuration at Each Update Rate
The maximum number of devices allowed is determined by their update rates as shown in the following
calculations:
𝑁𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝐷𝑒𝑣𝑖𝑐𝑒𝑠 𝑎𝑡 𝑈𝑝𝑑𝑎𝑡𝑒 𝑅𝑎𝑡𝑒 𝑥
PNC001 𝑆𝑈𝑀 ( ) ≤ 8 𝑑𝑒𝑣𝑖𝑐𝑒𝑠/𝑚𝑠
𝑈𝑝𝑑𝑎𝑡𝑒 𝑅𝑎𝑡𝑒 𝑥
𝑁𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝐷𝑒𝑣𝑖𝑐𝑒𝑠 𝑎𝑡 𝑈𝑝𝑑𝑎𝑡𝑒 𝑅𝑎𝑡𝑒 𝑥
CPL410, CPE400 & CPE330 𝑆𝑈𝑀 ( ) ≤ 2 𝑑𝑒𝑣𝑖𝑐𝑒𝑠/𝑚𝑠
𝑈𝑝𝑑𝑎𝑡𝑒 𝑅𝑎𝑡𝑒 𝑥
Update Rate (x) per Total Number of Devices Total Number of Devices per Embedded
Device (ms) per PNC001 PROFINET IO-Controller
CPL410, CPE400 & CPE100/CPE115
CPE330
1 8 2 0
2 16 4 0
4 32 8 0
8 64 16 0
16 – 512 128 (total device limit) 32 8
In the case of PNC001, if the configuration exceeds the equivalent of eight devices with 1ms update rates,
Machine Edition will not store the configuration.
For the embedded PROFINET Controllers in CPL410, CPE400 and CPE330, if the configuration exceeds the
equivalent of two devices with 1ms update rates, Machine Edition will not store the configuration.
For the embedded PROFINET Controller CPE100/CPE115, it is not recommended to use Update Rates below
16ms even though it is configurable using Machine Edition.

3.1.2 Basic Configuration Steps

The basic configuration steps, described in this chapter, are:
• In the hardware configuration, configure LAN2 as an embedded PROFINET LAN, or, for slot-mounted
hardware, add a PNC001 module to the RX3i main rack. This automatically associates a LAN with the
• Configure the parameters of the PROFINET Controller itself.
• Select the PROFINET Controller and add IO-Devices to its LAN. These IO-Devices can be VersaMax PNS
modules or third-party IO-Devices. Third-party IO-Devices and VersaMax PNS modules use GSDML files to
describe their capabilities. Proficy Machine Edition imports these GSDML files and incorporates the devices
into the configuration.
Configure the parameters of the VersaMax PNS modules and third-party IO-Devices.
• Using the Machine Edition Inspector pane, configure the communications properties of the PROFINET
Controller and any attached RX3i PNS modules, VersaMax PNS modules, and/or third-party IO-Devices.
• Add supported RX3i modules to the RX3i PNS remote nodes.
• Add supported VersaMax modules to the VersaMax PNS remote nodes.
• Configure the parameters of the RX3i I/O modules, VersaMax I/O modules and third-party sub-modules in
the remote nodes.
• When the configuration is ready, use the Discovery and Configuration Protocol (DCP) tool in Machine
Edition to assign a Device Name to each IO-Device so the PROFINET Controller can connect to the devices
and deliver their configuration.
• Store the configuration data from the programmer to the RX3i CPU.
3.1.2.1 Configuration Notes for Slot-Mounted PNC001

In the PME hardware configuration, add a PNC001 to the RX3i main rack. This automatically creates a LAN for
the PNC001.
3.1.2.2 Configuration Notes for Embedded PROFINET IO-Controller
When LAN2 is configured for Ethernet, the corresponding ports support SRTP Client/Server, Modbus TCP
Client/Server, OPC UA Server, and EGD. All PROFINET controller services (Including Explore PROFINET
Networks) are disabled when LAN2 is configured for Ethernet.
Configuring LAN2 for PROFINET retains standard Ethernet operation and enables PROFINET controller
services.
GFK-2571P July 2018 51

3.2 Configuration Tools

Proficy Machine Edition (PME) is the primary tool used to configure an RX3i PROFINET network. In addition, for
the PNC001 module only, certain parameters can be set from a computer through the Command Line Interface
(CLI).
The Command Line Interface can be used to set the non-volatile parameters in the PNC001-Ax module, as
listed below. These parameters are initially set up in the PME configuration. If any of these parameters is
subsequently changed using CLI, the PNC001 module uses the new setting. Regardless of their source, the
PNC001 module retains these settings in non-volatile memory, thus ensuring they can be re-asserted following
a power cycle.
3.2.1 Non-Volatile Configuration Parameters
Default
Parameter Description
Value
IP Address IP Address of the PNC001. 0.0.0.0
Subnet Mask Subnet mask of the PNC001. 0.0.0.0
Default Gateway Default Gateway for the PNC001. 0.0.0.0
PNC001’s PROFINET Device Name. Defaults to empty string -
Device Name ””
indicating the PNC001 is not named.
Specifies whether media redundancy is disabled, or if it is enabled
Redundant Media Role Disabled
as a Client, or if it is enabled as a Manager.
Redundant Media Ring Indicates one of the two network ports involved in Media
1
Port 1 ID Redundancy. Valid values are 1 to 4.
Redundant Media Ring Indicates one of the two network ports involved in Media
2
Port 2 ID Redundancy. Valid values are 1 to 4.
Redundant Media test Interval for sending test frames on ring ports in millisecond units.
20 ms
interval Valid values are 1 to 1000 ms.
Redundant Media Indicates the number of consecutive failed test frames before
3
monitor count declaring a ring failure. Valid values are 2 to 10.

3.3 Configuring an RX3i PROFINET Controller

3.3.1 Configuring a Rack-Mounted RX3i PROFINET Controller (PNC001)
This section describes one technique to configure the parameters of an RX3i IC695PNC001. The PROFICY
Machine Edition InfoViewer describes alternative menus and keyboard operations that can be used to perform
the same functions.
1. In the Project tab of the Navigator, expand the
PACSystems Target, the hardware configuration, and the
main rack (Rack 0).
2. Right-click an empty slot and choose Add Module. The
Module Catalog opens.
3. Open the Bus Controller tab, select the IC695PNC001
module and click OK.
4. The PNC001 is displayed as having been placed in the
selected rack/slot location.
- Its parameters appear in the Parameter Editor
window.
- Its communications properties appear in the
Inspector pane.
- Edit the PNC001’s parameters and its
communications properties as described in this
chapter.
Figure 32: RX3i Configuration showing
PNC001 slot location
3.3.2 Configuring an Embedded RX3i PROFINET Controller

CP400 and CPE330 both support configuring LAN2 as an embedded PROFINET Controller. Instead of
Configuring a PNC001 into a rack/slot location (Figure 32), LAN2 in the target is configured as a PROFINET
Controller (Figure 33).
Figure 33: Embedded PROFINET Controller Configured on LAN2
GFK-2571P July 2018 53

3.3.3 Configuring an Embedded RSTi-EP PROFINET Controller

CP100 support configuring LAN2 as an embedded PROFINET Controller. Instead of Configuring a PNC001 into a
rack/slot location (Figure 32), LAN2 in the target is configured as a PROFINET Controller (Figure 34).
Figure 34: CPE100/CPE115 Embedded PROFINET Controller Configured on LAN2

3.4 Configuring PROFINET System Redundancy

To enable PROFINET System Redundancy in a CPE400 project, select the CPE400 target in the PME
Navigator and use the Property Inspector to change the Enable Redundancy target property to True.
To enable PROFINET System Redundancy in a CPL410 project, select the CPL410 target in the PME
To enable PROFINET System Redundancy in a CPE330 project, select the CPE330 target in the PME
The Dual HWC property then defaults to True and must remain True.
To enable PROFINET System Redundancy for a PNC001, select the CPE330 or CRU320 target in the
PME Navigator and use the Property Inspector to change the Enable Redundancy target property to
True. The Dual HWC property then defaults to True and must remain True.
Figure 35: Setting PROFINET System Redundancy Parameters in PME Inspector
CPE100/CPE115 does not support PROFINET System Redundancy.
Note: For LED behavior and operator-initiated Role Switching in Hot Standby Systems, refer to the Quick
Start Guide or product manual of the device itself. These topics are not covered in this manual.
GFK-2571P July 2018 55

3.5 Exploring PROFINET Networks

To explore the PROFINET networks in the system while PROFICY Machine Edition is online with the RX3i
system, and while the PROFINET Controller is connected to its network, right-click on the Target icon (not the
PNC) and select Explore PROFINET Networks under the Online Commands menu item.
The Explorer view shows version information about all the devices on the associated network. Figure 36 shows
a PNC001 (located in Slot 6 of its CPU rack) with a single VersaMax PNS on its network. Figure 37 shows an
embedded PROFINET Controller (embedded in a CPL410 / CPE400 / CPE330 / CPE100/CPE115) connected to
an RX3i PNS module.
Note that all modules physically present in the remote nodes controlled by the PNS are displayed, regardless of
whether the devices are configured or not.
Figure 36: Explore PROFINET Network from PNC001
Figure 37: Explore PROFINET Network from Embedded PROFINET Controller

3.5.1 Configuring a PROFINET Controller on a LAN

Adding the first PROFINET Controller to a project automatically creates a LAN associated with it. For each
subsequent PROFINET Controller that is added to a project, an existing LAN can be selected or a new LAN can
be created. Opening the LAN View shows PROFINET Controllers on their assigned LANs. (To view the LANs in
the project, click Tools in the Machine Edition toolbar, and select LAN View, or right-click.)
Figure 38: LAN View showing PROFINET Controller on LAN2
A PROFINET Controller can be moved to a different LAN by selecting the module in the Navigator and dragging
it to the target LAN. Here, the PROFINET Controller has been moved from LAN02 (Figure 38 ) to LAN01 (Figure
39):
Figure 39: LAN View showing PROFINET Controller on LAN1
GFK-2571P July 2018 57

3.5.2 Configuring PROFINET Controller Parameters

Configure the PROFINET Controller parameters by editing the tabs as appropriate. The parameters are divided
among the tabs, and the options are available in the Inspector view.
3.5.2.1 PROFINET Controller Parameters (Settings Tab)
Figure 40: PROFINET Controller Settings Tab (PNC001)
Figure 41: PROFINET Controller Settings Tab (Embedded PNC)
Note that the embedded PROFINET Controller does not have any SFP cages, and therefore has
options for two ports, versus the four ports available in the PNC001.

Status Address, Length: The Status Address is the reference memory location for the 32 bits of status data
associated with the PROFINET Controller itself. The Status address can be assigned to valid %I, %Q, %R, %AI,
%AQ, %W, %G, %T or %M memory by right-clicking on the Status Address field and selecting the Data Entry
tool. The default value is the next available %I address. See Chapter 5, Diagnostics, for definitions of the status
bits that the module writes to this address.
Figure 42: Setting the Status Reference Address

Note: Because point faults are not supported by %G, %T and %M, the other available memory types, or I/O
Symbolics, are preferred.
SFP Cage 1 / 2 / 3 / 4: If the PNC001module will use plug–in Small Form-factor Pluggable devices in Port 3
and/or Port 4, specify the SFP devices in the appropriate field(s). On the Settings tab, right-click in the Values
field for the port, and select Data Entry tool to open the Catalog window. In the Catalog window, select the
type of SFP device for the port, as shown in Figure 43, and click OK. If the device is not listed, choose
GENERIC_SFP to add it to the configuration.
Figure 43: Select SFP Device from Catalog
GFK-2571P July 2018 59

I/O Scan Set: The scan set for the PROFINET Controller defaults to scan set 1. Scan sets are defined in the
CPU’s Scan Sets tab. The valid range is 1 through 32; the default value is 1. Refer to the PACSystems RX7i and
RX3i CPU Reference Manual, GFK-2222, for a discussion of CPU scan sets.
The embedded PROFINET Controllers and the PNC001 behave the same as far as this parameter is concerned.
Critical Network Ports: The default critical network port setting for all PROFINET Controller ports is
False. Setting one or more network ports on the PROFINET Controller as a critical network port
provides for triggering a CPU redundancy role switch when the last of all of the critical network port
links associated with that PROFINET Controller are lost (disconnected). Basically, when the last
critical network port is disconnected from its network, a diagnostic fault is logged by the PROFINET
Controller. In a redundancy system, where the PROFINET Controller is controlling redundant devices,
this results in a fatal IOC Software Fault and a Hot Standby CPU redundancy role switch with the CPU
placed into Stop/Fault mode.
When using the critical network ports feature, the following PROFINET speeds are strongly
recommended:
PROFINET Network Speed Recommended Network Type

100 Mbps Copper and/or Fiber based networks
1000 Mbps Fiber based networks ONLY.
Network ports 3 and 4 support fiber based networks via the SFP interface
Copper-based networks are not recommended at 1000 Mbps due to the extremely slow link down
detection associated with both fixed and SFP-based copper ports at this network speed. Using
copper-based networks at 1000 Mbps may result in the loss of I/O Devices when the last critical
network port is disconnected from the network. For this reason, the PROFINET Controller has a built-
in feature that forces any Cu port (fixed or Cu SFP) that is configured as a critical port to 100M.
Note: Critical network ports are allowed in simplex systems. However, the logging of the diagnostic fault,
when the last of the critical network ports is disconnected, does not invoke any role switch, and does
not place the CPU in Stop/Fault mode.

3.5.2.2 PROFINET Controller Parameters (Media Redundancy Tab)

By default, a PROFINET Controller is not set up for Media Redundancy. If the system will use Media Redundancy
(see Chapter 6 for more information), open the Media Redundancy tab and select either Client or Manager:
Figure 44: Setting Media Redundancy Parameters
If the PROFINET Controller will be a Media Redundancy Client, click on Ring Port 1 and Ring Port 2 to choose the
module ports and Domain Name that will be used.
Figure 45: Setting Media Redundancy Client Parameters
If the PROFINET Controller will be a Media Redundancy Manager, edit the Ring Port settings as above. You can
also change the Default Test Interval in the range of 10 to 1000ms and the Test Monitoring Count (2 to 10). For
the Media Redundancy Manager, the Domain Name can be edited by typing over the default name.
Figure 46: Setting Media Redundancy Manager Parameters
Note: In an MRP ring with a large number of clients, storing a configuration that causes all clients to
reconfigure (for example, changing the Domain Name) may generate a large number of Loss/Addition
of Device faults. This is expected behavior and all devices should automatically return to operational
status.
Note: If one of the module ports chosen as a Ring Port is configured as a critical network port, PROFICY
Machine Edition automatically sets the other Ring Port as a critical network port.
GFK-2571P July 2018 61

3.6 Configuring PROFINET LANs

To view the LANs in the project, click on Tools in the Machine Edition toolbar, and select LAN View from the
menu. If no LANs and no PROFINET Controllers have been added to the project, the LAN View is empty:
Figure 47: Configuring the PROFINET LAN

Adding a PROFINET Controller to the project automatically creates a new LAN.
Figure 48: LAN Associated with PROFINET Controller

Expand the LAN icon in the LAN View to see the modules it includes.
A LAN can also be added to the project by right-clicking on the PROFINET icon in the LAN View and selecting
Add LAN.
Figure 49: Adding a New LAN to the Configuration

3.6.1 Configuring the LAN Properties

Machine Edition automatically assigns a set of default properties to the LAN. Select the LAN icon in the LAN
viewer to display or edit its communications properties in the Inspector pane:
Figure 50: Setting the Communication Properties of a LAN

LAN Name: this can be edited or the default name can be used. Space characters are not permitted.
Description: an optional description of up to 255 characters can be entered for the LAN.
LAN ID: (read-only) this number identifies the LAN in the Machine Edition project.
Network Speed: the bandwidth available on the network. The default of 1Gbps can be changed to 100Mbps.
Maximum Utilization (%): the maximum percentage of total network bandwidth that can be used for
PROFINET I/O traffic. It can be edited to any value between 10 and 80 (do not enter the % character). Consider
other network traffic when changing this parameter.
IP Range Lower Limit: the lowest IP Address for automatically assigning IP Addresses to PROFINET
Controllers and LAN devices. Default is 192.168.x.1, where x is the lowest number not used by another LAN in
the project.
IP Range Upper Limit: the highest IP Address for automatically assigning IP Addresses to PROFINET
Controllers and LAN devices. Default is 192.168.x.254, where x is the lowest number not used by another LAN
in the project.
GFK-2571P July 2018 63

If the subnet mask is improperly set, devices may be unable to

communicate on the network and might disrupt network communications.
Contact your network administrator to assign values that work with an
existing network.
Caution
Subnet Mask: Mechanism that filters network communications so that they are routed only to subnets to
which they are addressed. The value defined here propagates to PROFINET Controllers and I/O devices
throughout the network.
PROFINET can only communicate to nodes in the local subnet. All nodes on the LAN must be in the same
subnet. The IP Range Lower/Upper Limits indicate the auto-assignment range. The range of the LAN is the
subnet mask range. A node can be assigned to any address in the subnet (which may be outside of the auto-
assignment range given in the dialog), but the addresses for all nodes must be in the subnet.
Gateway: The IP Address of the device that connects two (sub)networks that use different communications
protocols, enabling them to communicate with each other. The value defined here propagates to PROFINET
Controllers and I/O devices throughout the network.
If the gateway is improperly set, devices may be unable to communicate on

the network and might disrupt network communications. Contact your
network administrator to assign values that work with an existing network.
Caution
IO-Controllers: (Read-only.) The number of I/O Controllers configured to reside on the LAN.
IO-Devices: (Read-only.) The number of I/O devices configured to reside on the LAN.
Network Transit Time4 (units of 1 ms): The maximum time (in ms) for a message to propagate between any
two nodes on the LAN. This time depends upon the network architecture and is typically negligible. It can be
significant in networks that have one or more slow segments.
For a media redundancy ring network, the recommended setting this this parameter to at least 5 ms
(parameter value = 5), which accommodates the maximum supported number of ring nodes.
4
Versions of this manual (prior to version N), incorrectly dimensioned this unit in terms of tenths of a millisecond. The units
are in ms.

3.7 Adding a VersaMax PROFINET Scanner to a LAN

To add a VersaMax PNS to a LAN, in the Navigator right-click on the IC695PNC001 module and select Add
IO-Device. The PROFINET Device Catalog appears.
Figure 51: Select PNS from Catalog
In the PROFINET Device Catalog, expand the VersaMax PNS line and choose the module type:
Figure 52: Select PNS Type
Select the PNS type and click OK. The PNS appears in the Navigator window:
Figure 53: PNS Attached to PNC001 in PME Navigator
GFK-2571P July 2018 65

3.7.1 Configuring VersaMax PROFINET Scanner Parameters

After adding a VersaMax PNS to the LAN, its parameters can be configured by either double-clicking on the
Scanner in the Navigator, or right-clicking and selecting Configure from the menu.
Figure 54: Select PNS for Parameter Configuration

3.7.1.1 PROFINET Scanner Parameters (Settings Tab)
Figure 55: PNS Parameters Settings Tab

Inputs Default: Choose whether the RX3i CPU will set inputs from any modules in the PNS module’s remote
node to Off or Hold Last State in the following cases:
• The PROFINET Controller is not operational or has been removed.
• The PROFINET Controller cannot communicate with the scanner due to cable or network configuration
issues.
• The PNS is not able to scan the I/O module in its remote node.
Input Status and Length: The address in reference memory for the 32 bits of status data associated with the
PNS. The address can be assigned to valid %G, %I, %Q, %T or %M memory or Symbolic bits. The default value is
the next available %I address. Refer to the VersaMax PROFINET Scanner Manual, GFK-2721, for definitions of
the PNS input status bits.
Output Status and Length: The address in reference memory for the 32 bits of output control data
associated with the PNS. The address can be assigned to valid %G, %I, %Q, %T or %M memory or Symbolic bits.
The default value is the next available %Q address. Refer to the VersaMax PROFINET Scanner Manual, GFK-
2721, for definitions of the PNS output control bits.
I/O Scan Set: Specifies the I/O scan set to be assigned to the PNS. Scan sets are defined in the CPU’s Scan Sets
tab. The valid range is 1 through 32; the default value is 1.

3.7.1.2 PROFINET Scanner Parameters (Redundancy Tab)

On the Redundancy tab, select whether or not the PNS is redundantly controlled.
Figure 56: PNS Parameters Redundancy Tab
When the PNS supports PROFINET System Redundancy and is configured in an HSB CPU Redundancy system,
the Programmer automatically selects redundant control by setting the Redundancy Mode parameter to HSB
CPU Redundancy.
When the PNS does not support PROFINET System Redundancy, or is not configured in an HSB CPU
Redundancy system, the PNS Programmer automatically selects simplex operation (non-redundant control) by
setting the Redundancy Mode parameter to None.
To configure a redundancy-capable PNS for simplex operation within an HSB CPU Redundancy system, change
the Redundancy Mode parameter on the Redundancy tab from HSB CPU Redundancy to None.
3.7.1.3 PROFINET Scanner Parameters (Media Redundancy Tab)
By default, the PNS is not set up for Media Redundancy. If the system will use Media Redundancy
(see Chapter 6, Redundant Media, for more information), open the Media Redundancy tab and select
Client.
Figure 57: PNS Parameters Media Redundancy Tab
If the PNS will be a Media Redundancy Client, click on Ring Port 1 and Ring Port 2 to choose the module ports
that will be used.
Figure 58: Select PNS Ring Ports Usage
GFK-2571P July 2018 67

3.7.1.4 PROFINET Scanner Parameters (Module Parameters Tab)

The PNS has one module parameter:
Figure 59: PNS Parameters Module Parameters Tab
By default, the PNS module LEDs will blink a fault code if a fatal error occurs. This can be changed to cause the
PNS to restart instead.
3.7.1.5 PROFINET Scanner Parameters (GSDML Tab)
The PNS module’s GSDML Details tab displays the information from its GSDML file.
Figure 60: PNS Parameters GSDML Details Tab
This information cannot be edited.

Double-clicking on the PNS module’s Interface 1 icon in the Navigator displays additional GSDML parameters:
Figure 61: PNS Interface Parameter Details
Double-clicking on the PNS module’s Port 1 and Port 2 icons in the Navigator also displays additional GSDML
parameters for the scanner:
Figure 62: PNS Port Parameter Details
GFK-2571P July 2018 69

3.7.2 Adding VersaMax PROFINET Scanner Power Supplies

The VersaMax PNS has connectors for either one or two power supplies. If necessary, additional power
supplies can also be located between modules in the remote node.
To configure the one or two power supplies that will be installed directly on the PNS module, right-click on the
Slot 0 icon in the Navigator, then select Change Submodule List. A list of VersaMax power supplies appears.
In the Submodule list for slot 0, expand the Power Supply list and select the desired power supply from the list.
Drag the selected power supply to an available slot in the left pane. Slot 0, Subslot 2 is the leftmost power
supply slot. Slot 0, Subslot 3 is the rightmost power supply slot. (To delete a module after moving it, select the
module on the left and press the keyboard Delete key).
Figure 63: Selecting Power Supply for PNS Rack
Click OK to add the selected module(s) to the configuration. The Navigator shows the added power supply or
power supplies under slot 0.
Figure 64: Power Supplies Displayed in PNS Rack
Adding power supplies to the configuration sets up power supply alarms. Alarms will be triggered if the power
supply is configured but not working, or configured in the wrong subslot. These power supplies have no
configurable parameters, but their power supply and GSDML details can be viewed by double-clicking on a
power supply icon or right-clicking and selecting Configure.

3.7.3 Adding VersaMax Modules to a Remote Node

The PNS remote node can contain the module types listed in the VersaMax PROFINET Scanner Manual,
GFK-2721. However, it cannot contain the following expansion modules or communications modules:
Unsupported VersaMax Modules
Asi Network Master Module IC200BEM104
DeviceNet Network Control Module IC200BEM103
Expansion Transmitter Module IC200ETM001
Expansion Receiver Module, Isolated IC200ERM001
Expansion Receiver Module, Non-isolated IC200ERM002
Profibus-DP Network Slave Module IC200BEM002
To add a module to the remote node, right click on the VersaMax PNS icon in the Navigator and select Change
Module List. In the right pane of the Change Module List window, expand the list of VersaMax module types.
Figure 65: Adding VersaMax I/O Modules to Remote Node

Select modules from the list (right pane) and drag them to available slot locations in the remote node (left
pane).
Figure 66: Select VersaMax Module from Available List
To delete a module from the left-side pane, select it and press the keyboard Delete key. When the modules in
the left side pane are correctly situated, click OK to add them to the Configuration.
GFK-2571P July 2018 71

3.7.4 Installing Power Supplies Between Modules

Additional power supplies may be installed between modules, if necessary. Power Supply modules added in
this fashion will service the power requirements of modules located further right in the same rack.
To add a power supply between modules, expand the Power Supply Module node in the Change Module List.
Select the desired power supply from the list. When you drag the power supply to the left pane, additional
rows labeled power appear between the previously listed modules. Drop the power supply into its intended
location.
Figure 67: Adding Power Supplies between Modules in PNS Rack

Click OK to add the module(s) to the Configuration.
Figure 68: VersaMax PNS Rack showing Power Supply Located between I/O Modules

3.7.5 Configuring VersaMax Module Parameters

After adding VersaMax modules to the remote node, the parameters for each must be configured. For all
VersaMax modules, this includes configuring a set of basic parameters (such as: Reference Address, Length,
Scan Set, Carrier, Report Faults). Configuration details for those basic parameters are provided in the
Configuration chapter of the VersaMax PROFINET Scanner Manual, GFK-2721.
3.7.5.1 Configuring Analog Modules Requiring Jumper Settings
The following VersaMax analog modules use jumpers to select their voltage / current operation or output
defaults mode.
IC200ALG230 Analog Input Module, 12-bit Voltage/Current 4 Channels
IC200ALG260 Analog Input Module, 12-bit Voltage/Current 8 Channels
IC200ALG262 Analog Input Module, 15-bit Current Differential 8 Channels
IC200ALG264 Analog Input Module, 15-bit Current 15 Channels
IC200ALG266 Analog Input 15-bit Current 15Ch with enhanced over voltage protection
IC200ALG320 Analog Output Module, 12-bit Current, 4 Channels
IC200ALG321 Analog Output Module, 12-bit Voltage 4 Channels. 0 to +10Vdc Range
IC200ALG322 Analog Output Module, 12-bit Voltage 4 Channels. -10 to +10Vdc Range
IC200ALG325 Analog Output Module, 13-bit Voltage 8 Channels
IC200ALG326 Analog Output Module, 13-bit Current 8 Channels
IC200ALG327 Analog Output Module, 13-bit Voltage 12 Channels
IC200ALG328 Analog Output Module, 13-bit Current 12 Channels
IC200ALG430 Analog Mixed Module, Input Current 4 Channels, Output Current 2 Channels
IC200ALG431 Analog Mixed Module, 0 to +10Vdc Input 4 Channels, Output 0 to +10Vdc 2 Channels
IC200ALG432 Analog Mixed Module, 12-bit -10 to +10Vdc, Input 4 Channels / Output -10 to +10Vdc 2 Channels
All VersaMax Analog modules, except MDD841 and ALG331, support a default Analog value of zero only.
Before their parameters can be configured, these modules require an additional configuration step in Machine
Edition after being added to the PNS remote node.
When one of the above modules is added to the Configuration, the Navigator window shows a Configuration
Mismatch for the module (and for its PNS). This situation needs to be resolved before continuing, as described
in Section 3.7.5.2.
Figure 69 shows a configuration in which two modules have this type of mismatch:
Figure 69: Analog Modules Requiring Jumper-Setting Designation
Double-clicking one of these modules, or right-clicking and selecting Configure displays only the Power
Consumption and GSDML tabs. The Settings tab and other configuration tabs do not appear. To begin
configuring one of these modules, right-click the module in the Navigator and select Change Submodule List
from the menu.
GFK-2571P July 2018 73

3.7.5.2 The Change Submodule List

On the Change Submodule List, select the type of inputs or outputs that will be wired to the module, and drag
the selection to the Content field in the left pane. For example:
Figure 70: Selecting the Sub-Module Configuration with Jumper Settings Declared
Once the Content field has been populated, the Description field indicates how the physical jumpers in the
module should be configured. The +10 Vdc analog inputs selected in Figure 70 do not require the installation of
jumpers on the module. If selected, the other choices for this particular module would require jumpers. It is
important to ensure that the jumper installation matches the configuration for that module in PME. In the
event the jumper settings need to be altered due to changing channel requirements, the module configuration
in PME should be changed to match by retracing the steps outlined in this section.
After choosing the submodule parameters of the module as described above, a subslot appears in the
Navigator, and the module’s Configuration Mismatch is cleared:
Figure 71: Analog Modules Showing Configuration Mismatch Cleared

3.7.5.3 Configuring the Module Parameters
Double-click the subslot (not the module slot) in the Navigator to configure the module parameters. The
remaining configuration steps for these modules is the same as for other VersaMax modules.
For a list of VersaMax Analog module subslot configuration choices and jumper settings, refer to Configuring
Analog Modules that Have Jumpers in the VersaMax PROFINET Scanner Manual, GFK-2721.

3.8 Adding a Third-Party IO-Device to a LAN

To add a third-party IO-Device to a LAN, in the Navigator right-click on the connected IC695PNC001 module
and select Add IO-Device. Select the module in the PROFINET Device Catalog and click Have GSDML:
Figure 72: Selecting Third-Party Modules for Addition to LAN
To be included in the system configuration, any third-party IO-Device requires a GSDML file. The GSDML file for
the device must be present on the computer being used for the configuration.
Figure 73: Finding GSDML File for Third-Party Device
Provide a filename path to the file and click OK. The device is added to the configuration. Machine Edition
extracts necessary parameters from the GSDML file and makes the data available for editing within Machine
Edition.
GFK-2571P July 2018 75

3.8.1 Editing Third-Party IO-Device Parameters

To configure the parameters of a third-party IO-Device, either double-click on the module in the Navigator, or
right-click on the module and select Configure from the menu. Upon opening the IO-Devices configuration, you
will see an IO-Device Access Point tab, a GSDML Details tab, and, possibly, additional parameter tabs (if defined
by the device manufacturer in the associated GSDML file).
3.8.1.1 IO-Device Parameters (IO-Device Access Point Tab)
Use the IO-Device Access Point tab to set up the device’s interface to the RX3i controller:
Figure 74: Third-Party I/O: Use of IO-Device Access Point Tab
Inputs Default: Choose whether the RX3i CPU will set inputs from the remote node to Off, or Hold Last State
in the following cases:
• The PROFINET Controller is not operational or is removed.
• The PROFINET Controller cannot communicate with the device due to cable or network configuration
issues.
• The device is not able to scan the sub-module in its remote node.
I/O Scan Set: The scan set for an IO-Device defaults to scan set 1. Scan sets are defined in the associated PLC
CPU’s Scan Sets tab. The valid range is 1 through 32; the default value is 1.
3.8.1.2 IO-Device Parameters (Media Redundancy Tab)
If the IO-Device supports Media Redundancy (see Chapter 6, Redundant Media, for more information), a Media
Redundancy tab will be present. Open the Media Redundancy tab and select either Client or Manager:
Figure 75: Third-Party I/O: Use of Media Redundancy Tab
If the IO-Device will be a Media Redundancy Client, click on Ring Port 1 and Ring Port 2 to choose the module
ports that will be used.
Figure 76: Third-Party I/O: Select Ring Ports for Media Redundancy Client

If the IO-Device will be a Media Redundancy Manager, edit the Ring Port settings as above. You can also change
the Default Test Interval in the range of 1 to 1000ms and the Test Monitoring Count (2 to 10). For the Media
Redundancy Manager, the Domain Name can be edited by typing over the default name.
Figure 77: Third-Party I/O: Configure Ring Ports for Media Redundancy Manager
3.8.1.3 IO-Device Parameters (Device Parameters Tab)

Additional Device Parameters tabs can be used to select additional device options, as defined by the device
manufacturer. Note: The exact names of the tabs and parameters are derived from manufacturer specific
information contained in the associated GSDML file. For example:
Figure 78: Third-Party I/O: Additional Parameter Settings (Product Dependent)
3.8.1.4 IO-Device Parameters (GSDML Details Tab)

The GSDML Details tab displays the device’s GSDML parameters, which cannot be edited.
GFK-2571P July 2018 77

3.8.2 Configuring Sub-Modules of a Third-Party IO-Device

To configure the sub-modules of a third-party IO-Device, expand it in the Navigator. For example:
Figure 79: Expand Third-Party I/O Device

The device in Figure 79 is a switch. The parameters of its ports can be viewed and edited by either double-
clicking on a port, or selecting a port then right-clicking and selecting Configure from the menu.
For this IO-Device, the port parameters appear for editing (Figure 80).
Figure 80: Editing Port Parameters on Third-Party I/O Device

3.8.2.1 Sub-Module Parameters (GSDML Tab)
The GSDML Details tab displays the device’s GSDML parameters, which cannot be edited.
Figure 81: Display of GSDML for Third-Party I/O Device

3.9 Viewing / Editing IO-Device Properties

In addition to the parameter configuration described on the previous pages, all IO-Devices (PNS modules and
third-party devices) have other configurable properties. These properties are displayed in the Machine Edition
Inspector pane when the device is selected in the Navigator.
In the Inspector, properties that are not grayed-out can be used as is or edited as appropriate.
Figure 82: Inspector View of IO-Device Properties

Device Number: a number automatically assigned to the device in the configuration.
Update Rate: The period between PROFINET cyclic data transfers between an IO-Controller and an IO-Device.
Defaults to 32ms for RX3i and VersaMax PNS modules, and to 128ms for third-party devices. To change the
update period of the PROFINET production cycle for the IO-Device, use the drop-down list to select 1, 2, 4, 8, 16,
32, 64, 128, 256, or 512ms:
Figure 83: Setting of IO-Device Update Rate

Note: Note that shorter update periods place higher processing loads on the associated PROFINET
Controller. Refer to Section 3.1.1.2, PROFINET Controller Loading Limits. A PNC001 module can handle
heavier loads than an equivalent embedded PROFINET Controller.
GFK-2571P July 2018 79

Reference Variable: to be used by the PNIO_DEV_COMM logic blocks. The choice defaults to none. To create a
reference variable for the device, use the drop-down list to select Create. The variable name appears in the
Inspector field:
Figure 84: Assigning Reference Variable to IO-Device
IO LAN: (read-only) identifies the LAN of which the IO-Device is a part.

Device Name: this can be edited within the Inspector, or the default name can be used. Space characters are
not permitted.
Device Description: an optional description can be entered for the IO-Device.
IP Address: IP Address for the IO-Device. Default is assigned the lowest value that is currently available within
the automatic IP Address range defined for the LAN on which the device resides.

3.10 Assigning IO-Device Names

After the PNS and third-party IO-Devices on the LAN have been entered into the configuration, the Discovery
and Configuration Protocol (DCP) tool in Machine Edition must be used to assign a name to each IO-Device.
This step is required before downloading the configuration from the PROFINET Controller. Without this step,
the PROFINET Controller would be unable to connect to the devices and deliver their configuration.
The programmer must be connected to the RX3i controller system and the LAN and its devices must be
installed.
To open the DCP tool, right-click the hardware configuration slot containing the IC695PNC001 PROFINET
Controller and choose Launch Discovery Tool from the menu.
Use the Connection dropdown list to select the computer port being used by the programmer to communicate
with the RX3i system:
Figure 85: Use of Connection Drop-Down List

The choices should match the windows network setting in the computer’s network control panel.
Figure 86: Equivalent Windows Network Settings

In the DCP tool, use the LAN list to select the configured LAN. The results will be validated against the selected
LAN.
Figure 87: Assign LAN
GFK-2571P July 2018 81

Once a LAN is selected, click on Refresh Device List to display a list of actual devices on the LAN. Each device
can be in one of three conditions as indicated by the symbol in the Status column:
indicates that the Device Name, IP Address, Subnet and Gateway of the actual device matches the
configured device of the same Device Name residing on the selected LAN.
indicates that the Device Name of the actual device matches, but the IP Address, Subnet, or Gateway
does not match the configured device of the same Device Name residing on the selected LAN.
indicates that the Device Name of the actual device does not match any configured device residing on
the selected LAN. Either there is no such Device Name configured in the system, or the device with
that Device Name resides on a different LAN.
Figure 88: List of Device Names on LAN with Status Indications
If the Device Name of the device on the network is not correct, select the target device in the list of networked
devices, and click Edit Device. This will open a new dialog that can be used to set various parameters, including
Device Name, directly on the device.
Note: For the PROFINET Controller to successfully deliver configuration to a device, only the Device Name is
required to match the configuration.

3.11 After the Configuration is Stored to the RX3i CPU

The configuration is stored to the RX3i CPU using Machine Edition. For complete instructions, refer to the
PACSystems system documentation. If the configuration is stored to non-volatile memory or is battery-backed,
the CPU maintains configuration data over power cycles.
• The RX3i CPU transfers configuration data to the PROFINET Controller.
• After successfully processing and applying its configuration data, the PROFINET Controller turns on its
CONFIG LED.
• The PROFINET Controller then transfers the configuration for remote IO-Devices over the PROFINET
network.
PROFINET delivers IO-Device configurations when the IO-Controller establishes an Application Relationship
(AR) with the IO-Device. If all Application Relationships (AR)s are lost, the IO-Device (such as a VersaMax PNS)
does not change the configuration of any of its I/O sub-modules. Each sub-module retains the most recent
configuration received since it was last powered up or restarted. If a sub-module has not been configured since
power-up or restart, it remains in its hardware default condition. When the AR(s) are re-established and a
configuration is sent to the IO-Device, and the configuration of a sub-module has changed, the IO-Device
applies the new configuration.
If the PROFINET Controller cannot connect to an IO-Device, the PROFINET Controller logs a Loss of Device fault
in its Local Log table and provides the corresponding information to the RX3i CPU for its fault tables. The
PROFINET Controller periodically attempts to establish communications and configure the IO-Device. When
one of these subsequent connect/configuration attempts is successful, the PROFINET Controller logs an
Addition of Device fault for that IO-Device in its Local Log table and provides the information to the RX3i CPU
for its fault tables.
Note: It may take up to 5–10 seconds for the PROFINET Controller to establish a connection to an IO-Device,
including one that previously existed, but was lost.
• When a VersaMax PNS receives a changed configuration, it temporarily sets all of its outputs to their
defaults. If the configuration has not changed, a VersaMax PNS does not default outputs. Third-party IO-
Devices may operate differently.
• If a PNS is powered up and its modules are at hardware defaults, when it receives a configuration for the
first time, any new defaults that are different from hardware defaults are applied until the first output data
arrives.
If a PNS is powered up after receiving a configuration and the connection is then lost, configuration defaults are
applied when the connection is lost. On a subsequent connection, if the same configuration is sent, outputs
remain at the configuration defaults until the first output data arrives. If a different configuration is sent,
output defaults transition to the new defaults until the first output data arrives.
3.11.1.1 Clearing the RX3i CPU Configuration
If the programmer clears the configuration for an RX3i CPU containing a PROFINET Controller, the PROFINET
Controller clears its configuration (excluding non-volatile parameters, which are retained), closes all opened
PROFINET IO-Device connections, and turns OFF its CONFIG LED.
The RX3i PNS, VersaMax PNS and all third-party IO-Devices react to the clearing of the PROFINET Controller as
a loss of connectivity, and take appropriate action, such as defaulting outputs.
GFK-2571P July 2018 83

Chapter 4 PROFINET System Operation
This chapter describes:
• PROFINET Operation Overview
o PROFINET Communications
o Application Relationships
o Types of PROFINET Communications
o External Switch VLAN Priority Settings
• Operations of the PROFINET Controller in the RX3i and RSTi-EP
o Duplicate Device IP Address Detection
o Duplicate Controller IP Address Detection
o Resolving Duplicate IP Addresses
• I/O Scan Timing
• RX3i and RSTi-EP CPU Operations for PROFINET
o Reference ID Variables for the user Application
o The PNIO_DEV_COMM Function Block
o Reset Smart Module for the PNC001
o DO I/O for Remote I/O Modules
o Scan Set I/O for Remote I/O Modules
o RX3i and RSTi-EP CPU Defaults Inputs
o RX3i and RSTi-EP CPU Defaults Outputs
GFK-2571P July 2018 85

Chapter 4. PROFINET System Operation
4.1 PROFINET Operation Overview

An RX3i or RSTi-EP CPU uses PROFINET communications for data exchange between it (as the PROFINET
Controller) and IO-Devices connected on the same PROFINET network and configured to be under its control.
The PROFINET Controller function may be realized by utilizing the embedded PROFINET Controller option in
RX3i CPL410 LAN2, RX3i CPE400 LAN2, CPE330 LAN2 or RSTi-EP CPE100/CPE115 LAN2. It may also be realized
by installing a rack-mounted IC695PNC001 in the CPU backplane, where permitted.
In all cases, the port used for PROFINET communications is an Ethernet port. While configured for PROFINET,
the same network may also be used for basic Ethernet communications. However, use of a separate Ethernet
LAN and RX3i Ethernet interface is recommended for most applications.
A PROFINET network can include three types of devices:
PROFINET IO- In an RX3i or RSTi-EP system, the CPU operates as an IO-Controller. This may be done via
Controller the embedded PROFINET feature of certain CPUs (refer to Section 1.2.2) or via a rack-
mounted IC695PNC001. It is a controlling device that is associated with one or more
PROFINET IO-Devices.
PROFINET IO- A PROFINET IO-Device is a distributed I/O Device that is coupled to a PROFINET IO-
Device Controller via PROFINET.
PROFINET IO- An IO-Supervisor can be a programming device, a computer, or an HMI device. The
Supervisor PROFINET IO-Supervisor is typically used for commissioning or diagnostics.

4.1.1 PROFINET Communications

Communications on a PACSystems PROFINET network use the standard PROFINET communications described
in this section.
4.1.1.1 Application Relationships
Before an PACSystems PROFINET IO-Controller can exchange data with a PROFINET IO-Device, an Application
Relationship (connection) must be established between the devices. The PACSystems PROFINET IO-Controller
automatically sets up the correct number and types of Application Relationship and Communication
Relationship channels (see below) based on its Proficy Machine Edition configuration. Usually, only one
Application Relationship is established per IO-Device.
Communication Relationships within an Application Relationship
Within each Application Relationship, the PACSystems PROFINET IO-Controller establishes the following types
of Communication Relationships (CRs):
• Record Data CRs – always the first to be established within an Application Relationship. Record Data
Communication Relationships are used for non-real-time transfers of data records such as startup
parameter data, diagnostics data, identification data, and configuration data.
• IO CRs – used for the real-time, cyclic transfer of I/O data
• Alarm CR – used for real-time, acyclic transfer of alarms and events
Figure 89 represents an Application Relationship between a PACSystems controller with a PNC001 module and
an IO-Device. In the example below, the IO-Device consists of a VersaMax PNS with VersaMax I/O modules, but
the same principles apply for all IO-Controllers and IO-Devices.
Figure 89: Application Relationship
GFK-2571P July 2018 87

4.1.1.2 Types of PROFINET Communications

PACSystems PROFINET Controllers use two types of PROFINET communication transfers: real-time and non-
real-time. The illustration below shows real-time communications as solid lines and non-real-time
communications as dashed lines.
Figure 90: Real-Time and Non-Real-Time Data Communications
• Real-Time (RT) communication: PROFINET real-time communication is used for time-sensitive data. A
PROFINET IO-Controller and PROFINET IO-Device use two types of real-time communications to exchange
data: cyclic communication and acyclic communication:
o Real-time Cyclic communication is used to periodically transfer the application’s input and output
data. Cyclic communication occurs each PROFINET IO production cycle.
o Real-time Acyclic communication is used to transfer non-periodic data such as alarms. Acyclic
communication occurs only when needed.
• Non-Real-Time (NRT) communication: PROFINET non-real-time communication is used for less time-
sensitive data such as configuration, parameterization, diagnostics, and identification data.

4.1.1.3 External Switch VLAN Priority Settings

The PROFINET-IO specification indicates the VLAN priorities for each type of Ethernet traffic that originates
from a PROFINET node. VLAN priorities range from 0 to 7, with 7 being the highest.
The PACSystems PROFINET Controller supports just four traffic classes, giving four levels of preference.
Incoming traffic without a VLAN priority is assigned to the lowest priority traffic class. The table below lists the
VLAN priorities, and their corresponding priorities in the PROFINET Controller:
VLAN PROFINET Controller

Ethernet Traffic Description
Priority Priority
7 Highest priority MRP Media Redundancy
RT_CLASS_1 Cyclic PROFINET IO
6 Second-highest priority High Priority
High-Priority PROFINET Alarms
RTA_CLASS_1
Low Priority
5 Third-highest priority Low-Priority PROFINET Alarms
RTA_CLASS_1
4, 3, 2, 1 (reserved) (reserved)
Lowest priority IP Device Discovery and
0
DCP Configuration
If a system includes external switches, these switches must be configured to match the VLAN Priority
groupings listed above for the PROFINET Controller.
GFK-2571P July 2018 89

4.2 Operations of the PROFINET Controller in the

PACSystems System
The PROFINET IO-Controller in the PACSystems controller system performs the following operations:
• Consumes PROFINET IO-Device configuration from the CPU and transfers it to the IO-Devices over
the PROFINET network.
• Consumes input data from each PROFINET IO-Device and makes that data available to the CPU
during the CPU’s input scan.
• Produces the output data that it receives from the CPU during the CPU’s output scan to each
PROFINET IO-Device.
• Receives PROFINET alarms and diagnostics from PROFINET IO-Devices and converts them to a
PACSystems format.
• Maintains a Local Log Table of its own alarms and the diagnostic information it receives. It also
forwards some of the information to the CPU as I/O or Controller Faults.
• Automatically converts between the little-endian data format recognized by the CPU and the big-
endian format used for PROFINET communications.
• Checks for duplicate IP Addresses as described below.
4.2.1 Duplicate PROFINET IO-Device IP Address

The PROFINET IO-Controller will detect an IP Address conflict between a device that it is configured to
communicate with and another device in two situations:
• First, duplicates are detected when the PROFINET IO-Controller is trying to initially establish
communications with the configured PROFINET IO-Device. During the connection sequence, the PROFINET
IO-Controller queries the network to see whether any other node has the same IP Address as the
configured device.
• Second, duplicates are detected whenever a network device announces its presence5 on the network and
the IP Address of that device is identical to that of a PROFINET IO-Device that the PROFINET Controller is
currently communicating with.
In both cases, the PACSystems PROFINET IO-Controller attempts to establish or maintain the connection and
logs a Duplicate IP Address Detected fault for the device. The PROFINET IO-Controller then periodically queries
the network for resolution of the IP Address conflict. If the IP Address conflict is resolved, the PROFINET IO-
Controller logs a Duplicate IP Address Resolved fault for the device.
5
The PROFINET Controller uses the ARP protocol to detect duplicate IP addresses. Devices that issue a gratuitous ARP to
announce their presence on the network are detected.

4.2.2 Duplicate PROFINET IO-Controller IP Address

The PROFINET IO-Controller detects that a network device has the same IP Address as its own
➢ during power-up,
➢ whenever a new hardware configuration is downloaded from the programmer, and
➢ during operation whenever a device with a conflicting IP Address announces its presence6 on the
network.
When a duplicate is detected during power-up, following a reset, or following storage of a new hardware
configuration, the PROFINET IO-Controller:
• logs a Duplicate IP Address Detected fault for itself,
• does not connect to any configured PROFINET IO Devices,
• periodically queries the network for resolution of the IP Address conflict.
When a duplicate IP Address is detected after the PROFINET IO-Controller has established connection to
configured IO-Devices, the PROFINET IO-Controller:
• logs a Duplicate IP Address Detected fault for itself,
• maintains all IO-Device connections
• Note that whenever a second PROFINET Controller with an identical IP Address to the active
PROFINET Controller is connected to the network, the second controller will not succeed in entering
the network.
When the IP conflict is resolved, the PROFINET IO-Controller:
• logs a Duplicate IP Address Resolved fault for itself,
• attempts to re-connect all configured PROFINET IO-Devices,
• logs an Addition of Device fault for each connected PROFINET IO-Device to indicate that device is back
online.
Note: Power cycling a rack that has a PNC001 with the same IP Address as another node on the network will
result in two Duplicate IP Address Detected faults in the I/O Fault Table. This is normal behavior that
occurs because the PROFINET Controller retains IP parameters through a power cycle and attempts to
exist on the network before receiving a new configuration from the CPU. The first fault occurs before
the PNC001 receives the new configuration and the second fault occurs after the PNC001 receives its
new configuration. Both faults result in the PNC001 not attempting to connect to the network.
4.2.3 Resolving Duplicate IP Addresses

Whenever an IP Address conflict exists, IP-based network communication with the device(s) may be disrupted.
The IP Address conflict should be resolved by disconnecting one of the offending devices from the network or
assigning each a unique address. The Duplicate IP Address Detected fault lists the MAC address of the offending
devices in bytes 8 – 13 and 14 – 19 of the Fault Extra Data. The Discovery and Configuration Protocol (DCP) tool
in Proficy Machine Edition may be useful to identify PROFINET devices on the network with conflicting IP
Addresses.
6
The PROFINET Controller uses the ARP protocol to detect duplicate IP addresses. Devices that issue a gratuitous ARP to
announce their presence on the network are detected.
GFK-2571P July 2018 91

4.3 I/O Scanning

In the PACSystems PROFINET network, multiple I/O cycles run asynchronously and independently. Figure 91
illustrates typical cycles in a system with an PACSystems CPU with a PROFINET Controller, and PNS modules
used as the head-end in IO-Devices. Cycles may be different for third-party devices.
Figure 91: Diagram of Multiple Asynchronous I/O Scans
• PROFINET IO-Device Scan: in Figure 91, each VersaMax PNS scans all the modules in its node as
quickly as possible. The PNS stores the input data gathered from each of the input modules in that
node into its internal memory. On each output scan, the PNS writes the output data from its internal
memory to the output modules in its node.
3rd party devices: The conveyance of I/O data between an I/O module and the PROFINET IO network
is device dependent. Third party manufacturer documentation should be referred to for specifics for a
particular device.
• PROFINET IO Production Cycle: each PROFINET Controller in a CPU node and each IO-Device
publishes data from its internal memory onto the network at each scheduled PROFINET production
cycle (note: production cycles between IO-Controllers and IO-Devices are not synchronized, each
publishes at its configured update rate independently). The PROFINET Controller publishes output
data received from the CPU to each IO-Device, and the IO-Device publishes input data from its
memory to the PROFINET Controller.
• PACSystems CPU Sweep: the PACSystems CPU Sweep includes both an input scan and an output
scan. The CPU input scan retrieves the current input data being stored within the PROFINET
Controller. This input data is then available for use by the application logic. After the logic solution, the
CPU output scan writes the outputs to the PROFINET Controller.

4.4 Data Coherency

In a PACSystems PROFINET network, it is important to note that I/O data coherency is at the PROFINET
submodule level. The PROFINET Controller coherently transfers I/O data to and from the CPU on a PROFINET
submodule basis. This means that output data from a single CPU output scan for multiple PROFINET
submodules may not be transferred during the same PROFINET IO production cycle. Conversely, input data
consumed from a single PROFINET IO cycle by the PROFINET Controller may not be consumed during a single
CPU input scan.
GFK-2571P July 2018 93

4.5 Performance Factors

There are many factors that affect the timing of I/O as it flows through the system. Primary factors include:
• CPU Sweep Time
• Configured PROFINET IO Update Rate(s)
• Number of PROFINET IO Devices
• Number of IO modules
• Network latency and loading (for example, switching hardware, additional non-PROFINET network traffic)
• I/O Module Filter Times
When designing a PROFINET IO system, consider and weigh these factors appropriately to achieve an optimal
IO system for the application.

4.6 PROFINET IO Update Rate Configuration

Selecting PROFINET IO update rates is one of the primary means for adjusting performance of the system.
Consider the following when choosing an appropriate value.
• In general, for most applications, there is little benefit to configuring PROFINET IO update rates faster than
half the CPU Sweep time. Scheduling PROFINET IO update rates faster than required by the application
creates unnecessary loading on the network, PROFINET Controller, and PROFINET IO devices.
• Keep in mind that transferring IO over the PROFINET IO network could take up to one complete PROFINET
update cycle time for the transfer to actually occur. Since PROFINET IO production is asynchronous to the
source of the produced data, in the worst case the new production data could miss a PROFINET IO
production cycle, and thus must await the next cycle. Note, this means for an I/O loopback situation where
an application asserts an output and expects to see the output echoed on another input, there are two
PROFINET transfers involved, therefore it may take two PROFINET IO production cycles (one for each data
transfer).
• It is possible that the PACSystems CPU, through application logic actions, can update output data for a
Remote IO Module faster than the usual I/O update rate of that remote I/O module. The application logic
must be careful not to update output data faster than the scanning of the Remote IO Module (which is a
function of both the PROFINET IO Update Rate and IO-Device Scan). Otherwise, output data from the CPU
may not transfer to the Remote IO Module before being overwritten by new output data from the
application logic.
GFK-2571P July 2018 95

4.7 PACSystems CPU Operations for PROFINET

This section describes several PACSystems CPU functions as related to their operation when used with a
PROFINET network.
In addition, PACSystems CPUs with version 7.0 or later firmware and Proficy Machine Edition version 7.0 or
later provide special tools for use in systems with PROFINET networks based on the PROFINET Controller:
• Reference ID Variables (RIVs)
• PNIO_DEV_COMM function block
4.7.1 Reference ID Variables for the PACSystems Application

RIVs are available to the PACSystems application logic to provide a simple symbolic reference to an entity. The
following RIV types are defined for use with PROFINET Controllers and IO-Devices.
RIVs are assigned in Proficy Machine Edition by editing the Properties for a PROFINET Controller or IO-Device in
the hardware configuration.
4.7.1.1 Reference ID Variable Data Types
Data Type Associated With
PNIO_CONTROLLER_REF PACSystems PROFINET Controller
PNIO_DEVICE_REF PROFINET IO-Device
PNIO_CONTROLLER_REF Variable
Each PACSystems PROFINET Controller can have a PNIO_CONTROLLER_REF variable assigned to it.
When assigned, it is linked to the PROFINET Controller and its value cannot be changed. If a linked
PNIO_CONTROLLER_REF variable is present, the application logic and hardware configuration are coupled. The
name of the PNIO_CONTROLLER_REF linked variable corresponds to the controller’s Device Name used in the
hardware configuration to identify the module on the PROFINET network. Whenever the
PNIO_CONTROLLER_REF variable is renamed, Proficy Machine Edition will make sure all uses of that variable in
logic convert to the new variable name.
Unlinked PNIO_CONTROLLER_REF variables can be passed to the IN and Q parameters of the MOVE_DATA
function block. Linked PNIO_CONTROLLER_REF variables can only be passed to the IN parameter of the
MOVE_DATA function block.
PNIO_DEVICE_REF Variable
An RIV of type PNIO_DEVICE_REF uniquely identifies a PROFINET IO-Device. It is an unsigned integer in the
range of 1 – 255.
Each PROFINET IO-Device in an PACSystems hardware configuration can have a PNIO_DEVICE_REF variable
assigned to it. When assigned, it is linked to a PROFINET IO-Device. When a linked PNIO_DEVICE_REF is
present, the logic and hardware configuration are coupled. The name of the PNIO_DEVICE_REF linked variable
corresponds to a combination of the LAN ID and the Device Name used to identify the IO-Device on that LAN.
Whenever the PNIO_DEVICE_REF variable is renamed, Proficy Machine Edition will make sure all uses of that
variable in logic convert to the new variable name.
Unlinked PNIO_DEVICE_REF variables can be passed to the IN and Q parameters of the MOVE_DATA function
block. Linked PNIO_DEVICE_REF variables can only be passed to the IN parameter of the MOVE_DATA function
block.

4.7.2 PNIO_DEV_COMM Function Block

The PNIO_DEV_COMM function block monitors communications between a specified PROFINET Controller and
a specified IO-Device.
Figure 92: PNIO_DEV_COMM Function Block
PNIO_DEV_COMM can be used by the application logic to take a corrective action or turn on an indicator if a
specific device fails. It might also be used by a custom HMI to show which PROFINET IO-Device connections are
currently established.
It is recommended that the All Devices Connected status bit be checked first to determine whether all devices
belonging to the PROFINET Controller are functioning. If this bit is 0, indicating that one or more devices is not
OK, the PNIO_DEV_COMM function block can then be used to determine which specific devices are not
communicating. For details on this status bit, refer to Status Reporting in Chapter 5, Diagnostics.
4.7.2.1 Parameters and Outputs of PNIO_DEV_COMM
PNIO_DEV_COMM returns a Boolean indication of whether or not a given PROFINET Controller is currently
communicating with a specified IO-Device. The PROFINET Controller is identified by the IOController input
parameter, which is a PNIO_CONTROLLER_REF data type. The IO-Device is identified by the IODevice input
parameter, which is a PNIO_DEVICE_REF data type.
PNIO_DEV_COMM has two Boolean outputs (in addition to ENO) labeled OK and Primary.
OK is set ON/true if the PROFINET Controller is successfully communicating with the IO-Device; otherwise
it is OFF/false.
Primary is set ON/true if the IO-Device is currently being actively controlled by the PROFINET Controller. In
a Hot Standby CPU redundancy application, only one PROFINET Controller is actively controlling an IO-
Device at any given time. For details, refer to the PACSystems Hot Standby CPU Redundancy User’s
Manual, GFK-2308.
The application logic must identify the PROFINET Controller and the IO-Device in a symbolic manner, passing
appropriate Reference ID Variables (see Figure 93) to the corresponding input parameters.
GFK-2571P July 2018 97

Example
In the sample logic (Figure 93), the RIV iolan_controller01_L3 is assigned to a PROFINET Controller and the RIV
iolan_controller01_L3 is assigned to an IO-Device.
If the iolan_controller01_L3 PROFINET Controller is communicating with the versamax_pns01_L3 IO-Device, the
Bool variable L3_PNC01_PNS01_Status is set on. In a simplex (non-redundant) system the value of the Primary
output is the same as that of the OK output. In a Hot Standby CPU Redundancy system, the Primary output
sets the L3_PNC01_Primary variable on when the iolan_controller01_L3 Controller is actively controlling the
versamax_pns01_L3 IO-Device.
Figure 93: PNIO_DEV_COMM Example
4.7.3 Reset Smart Module for the PROFINET Controller

Service Request 24, Reset Smart Module7, can be used to reset a PNC001 module in the PACSystems RX3i CPU
rack. The result is the same as extracting the PNC001 module from the rack then re-inserting it.
When the RX3i CPU encounters the Reset Smart Module service request in the application logic, it issues a
reset command to the specified module (in this case, a PNC001). The PNC001 terminates all connections to
PROFINET IO-Devices. When the PNC001 powers up and re-establishes communications with the CPU, the
CPU sends the appropriate configuration to the PNC001, and the PNC001 re-establishes connections with all
its configured PROFINET IO Devices.
Note: The Reset Smart Module request cannot be used to reset smart modules located in remote nodes.
4.7.4 DO I/O for Remote IO Modules

In addition to the normal I/O updates that occur during the PACSystems CPU’s scan, the application program in
the CPU can use the DO I/O function to access the I/O data associated with Remote IO Modules on the
PROFINET network during the logic portion of the CPU sweep. The DO I/O function can obtain or update the
most recent I/O data that is being consumed from or published to the Remote IO Module by the PROFINET IO
Controller. The DO I/O function can also be used to obtain data associated with the PROFINET Controller itself.
It is important to remember that the I/O data being read or written by the DO I/O function is data currently
being stored by the PROFINET Controller within its memory. Executing a DO I/O function from the CPU does
not cause additional data to be produced or consumed on the PROFINET NETWORK. Updates of the actual
Remote IO Module I/O data occur during the configured PROFINET cyclic scanning schedule. The DO I/O
function provides the benefit of immediately updating I/O data at the PROFINET Controller, as opposed to
waiting for the next normal I/O scan. The DO I/O function can also be used to obtain the latest input status
from the PROFINET Controller (see Chapter 5, Diagnostics).
7
This Service Request is not supported by embedded PROFINET Controllers.

4.7.5 Scan Set I/O for Remote I/O Modules

The Scan Set I/O function of the PACSystems CPU requests the scanning of remote modules that are members
of a configured scan set. The Scan Set I/O function operates like a DO I/O function, with the added ability to
identify and group the modules to be scanned. Modules are grouped according to their configured scan sets. As
with the DO I/O function, the Scan Set I/O function updates/consumes data stored in the local PROFINET
Controller; it does not directly update IO-Devices in remote nodes.
4.7.6 PACSystems CPU Defaults - Inputs

The PACSystems CPU defaults input data from remote I/O modules under the following conditions:
• the remote module or PROFINET Controller has not yet come online following a download of hardware
configuration
• the remote module or PROFINET Controller has not yet come online following a power cycle
• the remote module signals its input data is no longer valid (e.g. due to local module fault)
• the remote module is extracted from the backplane
• the remote module loses power or otherwise fails
• the PROFINET Controller loses power or otherwise fails
• the PROFINET network connection (Application Relationship) associated with the input data is lost.
The PACSystems CPU defaults the input values of an input module based on the input default state configured
for the I/O Device. Inputs may be configured to either Hold Last State or Force Off (zero).
If a PROFINET Controller loses connections to an I/O device, the following actions occur:
1. The CPU defaults the input values of all input modules assigned to it within the IO-Device.
2. The PROFINET Controller logs a Loss of Device fault in its Local Log and in the CPU’s I/O Fault Table.
3. The I/O point fault contacts for the I/O references and variables associated with the IO-Device are set to
the faulted state (if point faults are enabled on the CPU).
4.7.7 PACSystems CPU Defaults - Outputs

Outputs default when the CPU is no longer providing the data (e.g. when CPU has I/O disabled). For I/O
modules which control their own output defaults based on their configuration, the output behavior is
determined by that configuration setting. For I/O modules which do not have such a configuration setting, the
output default behavior is fixed (typically 0). Refer to the specification for each I/O module type to determine
behavior.
GFK-2571P July 2018 99

Chapter 5 Diagnostics
• Power-up and Reset
o Module Restart
o Problems during Power-up and Reset
o Transitioning to Firmware Update Mode
• Special LED Blink Patterns
o Special LED Patterns - Module Identification
o Special LED Patterns – Microprocessor Overtemperature
• Fatal Error Reporting
• Status Reporting
• Fault Contacts and Fault Locating References
• PROFINET I/O Alarms
• The PROFINET Controller’s Local Log Table
o Local Log Table-Only Faults
o Viewing and Clearing the Local Log Table
• PROFINET Controller Faults in the PACSystems Fault Tables
o Clearing the PACSystems Fault Tables
o Faults Reported to the Controller Fault Table
o Faults Reported to the I/O Fault Table
GFK-2571P July 2018 101

Chapter 5. Diagnostics
5.1 Power-up and Reset (PNC001 Module)

During power-up and reset, the PNC001 module runs diagnostics and initializes its hardware components.
When the necessary hardware components have been initialized and tested, the PNC001 transitions to either
normal operation or firmware update mode.
As the PNC001 module transitions to normal operation, it adds a startup entry that provides a reason for the
restart in its Local Log table. This entry is normal.
5.1.1 Module Restart

The PNC001 restarts if it receives a Reset signal from the PACSystems RX3i CPU, if the Restart Pushbutton is
pressed, if the restart or default command is issued from the Command Line Interface (refer to the PROFINET
Controller Command Line Interface Manual, GFK-2572), or if the hardware watchdog timer expires. More details
on each type of restart are given below.
When the PNC001 is restarted, it retains any entries in its Local Log table and its non-volatile configuration
parameters. Any debug data in non-volatile storage can be viewed from the Command Line Interface using the
log or show log commands.
5.1.1.1 Restart Triggered by Reset Signal from the PACSystems CPU
The PACSystems RX3i CPU resets/restarts a resident PNC001 module if:
• The application logic executes SVC_REQ #24, specifying the rack and slot of a PNC001 module.
• The RX3i CPU loses communications with the PNC001.
• The PNC001 requests the RX3i CPU to reset / restart it (for example, as a result of a restart or default
Command Line Interface command execution).
Note: This feature applies to PNC001 modules, but does not apply to CPUs with embedded PROFINET
Controllers.
5.1.1.2 Restart Triggered by Restart Pushbutton
Pressing and releasing the Restart pushbutton on the PNC001 module resets the hardware, turns OFF all LEDs
briefly and initiates the module’s power-up sequence. The Restart pushbutton may also be used to restart the
module if the OK LED is blinking an error code upon hardware or runtime failure, or if the module locks up.
5.1.1.3 Restart Triggered by Restart and Default Command
Issuing a restart or default command from the Command Line Interface causes the PNC001 to restart. Modify-
level privileges are required to issue these commands.
5.1.1.4 Restart Triggered by Hardware Watchdog Timer
The PNC001 maintains a hardware watchdog timer that will restart the module in the event that it is unable to
carry out its normal processing. The PACSystems RX3i CPU is not able to access the PNC001 module’s shared
memory while the PNC001 is restarting.
After the restart, the module’s Local Log table is restored from NVRAM. The PNC001 logs a Watchdog Timer
Expired fault in the RX3i CPU’s IO Fault Table, and a Restart Event in its Local Log table.
5.1.2 Problems During Power-up and Reset

Certain conditions can prevent the module from powering up and becoming operational or entering firmware
update mode:
Problem Indication Action
Hardware failure All LEDs off. Module unresponsive. Return the module to
Invalid bootstrap image Automation & Controls
at GE Energy
Invalid boot image ▪ No LEDs turn on and the module is Connections.
unresponsive, or
▪ The STATUS LED is solid green and is the
only LED that is on.
Power-up diagnostics/hardware LED Fatal Error blink code, as described in this Note the blink code
initializations fail that are chapter. and contact Customer
considered fatal Service.
Non-Fatal diagnostic/hardware The module continues normal power-up, but an Note the fault and
initialization faults entry is added to the Local Log table and the contact Customer
RX3i CPU’s Fault Table (if backplane Service.
communications have been established).
The module does not contain LED Fatal Error blink pattern, as described in Note the blink code
hardware identity information this chapter. and contact Customer
Service.
5.1.3 Transitioning to Firmware Update Mode

The module transitions to firmware update mode for any of the following reasons:
1. WinLoader has commanded the module to enter firmware update mode. This is normal when a firmware
update has been initiated from WinLoader.
2. The PNC001 does not have a valid firmware image at power-up. The PNC001 performs checks to
determine the firmware image is valid and has not been corrupted before it begins execution. If the
validation fails, firmware update mode is activated until a valid image has been stored.
For more information about firmware update mode and using WinLoader, please see Chapter 2, Installation.
GFK-2571P July 2018 103

5.2 Special LED Blink Patterns

In addition to the LED blink patterns that indicate a fatal error, the PNC001’s LEDs can indicate module
location/identification and microprocessor overtemperature conditions, as described below.
Special LED Blink Patterns are not supported by RSTi-EP CPE100/CPE115 embedded PROFINET Controller.
5.2.1 Special LED Pattern - Module Identification

The LEDs on a PNC001 module (PNC001-Ax only) can be commanded to repeatedly turn ON and OFF in a
special sequence, to help locate or identify the module:
• First the LEDs are turned on in the following order: OK, LAN, STATUS, CONFIG, PORT 4, PORT 3, PORT 2,
PORT 1. There is a short delay between turning on each LED.
• The LEDs are then turned off in the same order. There is a short time delay between turning off each LED.
For the -Ax version, the command, blinkId <begin/end> is issued via the Command Line Interface. Issuing the
blinkId begin command starts the identification blink sequencing while the blinkId end stops the identification
blink sequencing. When issued from the Command Line Interface, the last command session that commands
the IDENTIFICATION blink pattern determines its state (either blinking or stopped). Note that the blinkId
command requires Modify-level access to the Command Line Interface.
5.2.2 Special LED Pattern - Microprocessor Overtemperature

If the maximum threshold temperature for the microprocessor is exceeded, the PNC001 goes into power-
saving mode. While the PNC001 is in an overtemperature condition:
• the LEDs on the PNC001-Ax module behave as follows:
PORT 1, PORT 2, and STATUS LEDs flash red for 0.5 seconds (all other LEDs off),
then PORT 3 and PORT 4 LEDs flash red for 0.5 seconds (all other LEDs off).
This pattern repeats.
• the LEDs on the PNC001-Bxxx module behave as follows:
the PORT NUMBER LEDs flash red for 3 seconds and
then all LEDs turn off.
This pattern does not repeat.
The PNC001 stays in power-saving mode until the temperature drops to a safer level. Once a safe temperature
is reached, the PNC001 module restarts. When the PNC001 is restarted, it retains any entries in its Local Log
table and its non-volatile configuration parameters. For the -Ax version, any debug data in non-volatile storage
can be viewed from the Command Line Interface using the log or show log commands.
Note: Under certain ambient operating temperatures, the PNC001 may momentarily display the
overtemperature pattern during power up, while it is calibrating its thermal protection functions. This
indication may be ignored, and no overtemperature entry is added to the Local Log table, the
Controller Fault Table or I/O Fault Table.
5.2.3 Firmware Update

While the PNC001 is in firmware update mode, the OK, LAN, and STATUS LEDs blink green for 0.5 seconds and
then off for 0.5 seconds in unison. During firmware update operation, the ports are disabled, so all of the PORT
NUMBER LEDs are off. The CONFIG and LAN LEDs are also off. The USB LED (-Ax only) operates normally,
displaying the condition of the USB port.
5.2.4 Internal Update

Some changes from a firmware update are applied to the system on the next power up. During this internal
update process, the STATUS and LAN LEDs blink green for 0.5 seconds and then off for 0.5 seconds in unison.
At the completion of the internal update process, the PNC001 restarts and should power up normally.
5.3 Status Reporting

The PNC001 module and any embedded PROFINET Controller both provide 32 bits of status information to a
configured location in the PACSystems CPU’s reference memory.
The status data consists of the Module OK bit, which indicates the health of the module itself, a status bit for
each external port, and a bit that indicates the connection status of the configured devices.
All Status bits are active high. The status location may be configured in %I, %Q, %AI, %AQ, %R, %G, %T, %M or
%W or I/O Variable reference memory in the PACSystems CPU.
Status Bit Definitions
Bit Name Description
1 Module OK Indicates the health of the PROFINET Controller.
1 indicates the PROFINET Controller is functioning properly.
0 indicates the PROFINET Controller is not functioning properly.
2 Port1 Link Up 1 indicates the port is connected to another device and is operating correctly.
3 Port2 Link Up 0 indicates the port is not connected to another device, the port has an error
preventing communications, or the SFP cage is empty or has an incompatible SFP
4 Port3 Link Up8
device.
5 Port4 Link Up8 For CPE100/CPE115, Port1, 2 & 3 Link Up status indicates the LAN2 Port2, 3 & 4 Link
Up status.
6 Reserved Always 0.
7 Port3 SFP OK 8
Indicates the health of the SFP plugged into Port 3.
1 indicates that the SFP matches configuration and is operational.
0 indicates that either the SFP does not match configuration or is not operational.
8 Port4 SFP OK8 Indicates the health of the SFP plugged into Port 4.
1 indicates that the SFP matches configuration and is operational.
0 indicates that either the SFP does not match configuration or is not operational.
9 All Devices 1 indicates all configured devices are connected and communicating over PROFINET.
Connected 9 0 indicates no devices are configured or one or more configured devices have not
established a PROFINET connection.
10 Reserved Always 0.
11 MRP Enabled 0 indicates that MRP is not enabled.
1 indicates that MRP is enabled.
12 MRP Role If MRP is enabled:
0 indicates that the PROFINET Controller is currently an MRP client (MRC).
1 indicates that the PROFINET Controller is currently the MRP Manager (MRM).
If MRP is not enabled, this bit will be set to 0.
13 MRP Ring Status If MRP is enabled and the PROFINET Controller is currently the MRM:
0 indicates that the ring is open (ring broken).
1 indicates that the ring is closed (ring complete).
If MRP is not enabled, or if the PROFINET Controller is an MRC, this bit will be set to 0.
14-32 Reserved Set to 0
8
Applies to PNC001 module only. Bit is set to zero on embedded PROFINET Controllers.
9
Individual device statuses (as reported by the PNIO_DEV_COMM function block) are updated prior to the All Devices
Connected bit. Therefore, it is possible (depending on PNC loading) to see via the PNIO_DEV_COMM function block that
every individual device is connected while the All Devices Connected bit is not yet set. To avoid this inconsistency, it is
recommended that the All Devices Connected bit be checked first, before checking individual device connection status
using the PNIO_DEV_COMM function block. For details, refer to the section entitled PNIO_DEV_COMM Function Block.
GFK-2571P July 2018 105

5.4 I/O Fault Contacts

The PROFINET Controller sets I/O point fault contacts to the faulted state whenever an IO-Device is not
available or there is a problem with the I/O module.
If the control application needs to know whether a set of inputs is available or not, it must refer to the input
point faults. For example, immediately following a power cycle or recent download of hardware configuration,
the PACSystems CPU can go to Run mode before the PROFINET Controller and its configured IO-Devices are
ready to transfer inputs. During this time, the inputs for each IO-Device are defaulted and the corresponding
input point faults remain in the faulted state until both the PROFINET Controller and the IO-Device are ready to
transfer inputs. By inspecting the input point faults, the application can determine when the inputs are ready
to be consumed.
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 Reference 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.
GFK-2571P July 2018 107

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 fataIInfo
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.
Figure 94: Alarm Processing Phases
5.7.1.1 PROFINET Alarm Action

If a PROFINET I/O Alarm occurs, the action is Diagnostic (the action type is not configurable). When a fault in
this group is processed, the CPU sets the following status bits: #ANY_FLT, #IO_FLT, #IO_PRES, and
#PNIO_ALARM (%SA30).
The #PNIO_ALARM status bit is cleared whenever the I/O Fault Table is cleared.
GFK-2571P July 2018 109

5.8 Local Log Table of the PROFINET Controller

Since the embedded PROFINET and PNC001-Bxxx do not support the Command Line Interface (CLI), while the
older PNC001-Ax module does support CLI, the interactions become a little confusing. When reading this
section, keep in mind that CLI is supported by PNC001-Ax only. The Local Log Table is still present and behaves
the same in all respects, except for CLI interactions.
The Local Log table in the PROFINET Controller contains entries indicating events and errors. There can be
three types of entries in the Local Log table:
• Local faults. These are viewable only using the Command Line Interface.
• Controller faults. These are passed to the PACSystems CPU Controller Fault Table, provided the PROFINET
Controller was in communication with the CPU at the time the entry was added to the log.
• I/O faults. These are passed to the PACSystems CPU I/O Fault Table, provided the PROFINET Controller
was in communication with the CPU at the time the entry was added to the log.
The PROFINET Controller maintains these entries in its Local Log table. Entries in the Local Log are preserved
across power-cycles. In the PNC001-Ax module, they may also be cleared using the CLI clear log command.
Clearing the CPU Fault Tables or restarting the PROFINET Controller does NOT clear the Local Log table.
If the Local Log table overflows, new entries overwrite the oldest entries, which are then lost. If that happens,
CLI indicates the number of entries that have been discarded. The count of discarded entries is reset to zero
whenever the Local Log table is cleared (applies to PNC001 module only).
The STATUS LED on the PNC001-Ax module provides an indication that a new fault has been added to the
module’s Local Log since either the last time the module was restarted, or since the last time the log was
cleared. The STATUS LED is ON at power-up, after the Local Log has been cleared, or after executing the clear
statLED command from CLI. When a subsequent fault occurs, the STATUS LED turns OFF to indicate that a new
fault has been logged.
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/
Recommended
Error Description Cause
Correction
Code
2-1 PNC001 restarted. The PNC001 has experienced a restart. If the PNC001 restart is
Possible causes include: due to a hardware
- PNC001 power-cycled watchdog timer
- PNC001 reset button pushed expiration, or internal
- PNC001 command shell command to fatal error, note the Fault
reset board issued Extra Data and contact
customer service.
- 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.
2-2 Time The PNC001 was unable to synchronize its Contact customer service.
synchronization with current time with the PACSystems RX3i
PACSystems RX3i controller.
controller failed.
2-4 Invalid Media PROFINET Controller encountered an error Contact customer service.
Redundancy related to applying Media Redundancy
Configuration configuration parameters.
4-1 Socket close failed PROFINET Controller was unable to close an Contact customer service.
opened OS socket.
5-1 CLI null environment PNC001 encountered a null pointer while Contact customer service.
pointer processing a command via the CLI.
5-3 CLI Ethernet PNC001 encountered an error while Contact customer service.
command failure processing an Ethernet related command.
5-4 CLI PNC specific PNC001 encountered an error while Contact customer service.
command failure processing a PNC001-specific CLI command.
5-5 CLI initialization The Command Line Interface functionality Contact customer service.
failure on the PNC001 failed to initialize correctly.
6-1 Write to nonvolatile The PROFINET Controller failed to write data Contact customer service.
memory failure to non-volatile memory, which could result
from configuration store/clear operations
from the programmer, or Command Line
Interface commands.
GFK-2571P July 2018 111

Group/
Recommended
Error Description Cause
Correction
Code
8-1 Return of The PROFINET Controller has received a None.
Submodule Return of Submodule PROFINET alarm from
PROFINET Alarm a PROFINET device.
received.
8-2 PROFINET The PROFINET Controller received a Attempt reactivation of
Submodule replied negative acknowledgement while submodule, by removing
negatively to Plug attempting to reconfigure a PROFINET the submodule and
configuration. submodule that had been plugged back in to reinserting it into its host
a device. device.
8-3 PROFINET Controller The PROFINET Controller was unable to Contact customer service.
failed delivery of deliver to the PACSystems controller a fault
fault to the that was logged locally on the PROFINET
PACSystems Controller. The fault will appear in the Local
controller. Log of the PROFINET Controller, but will not
appear in the controller Fault Tables.
8-5 Failure occurred The PROFINET Controller experienced a Contact customer service.
while processing failure while processing a new configuration.
configuration. Note: The PACSystems controller that
delivered the configuration to the
PROFINET Controller should also log
its own unique failure fault in the
Controller Fault Table.
8-6 PNIO stack The PROFINET Controller has experienced a This is an informational
asynchronous generic error resulting from interactions fault. No action is
response error with the PROFINET Controller stack. required.
Possible causes include two or more
messages from the controller stack were
not received in the expected order.
9-3 Rejected mail error. The PROFINET Controller received a rejected Contact customer service.
mail message from the CPU.
9-4 Mail processing The PROFINET Controller encountered an None.
error on the error while processing mail received from
PROFINET the PACSystems CPU (e.g. PROFINET
Controller. Controller received rejected mail from CPU).
9-7 PROFINET Alarm The PROFINET Controller has attempted to This is an informational
processing error ACK/NACK a PROFINET Alarm more than fault. No action is
once. required.
10-1 Module service The PROFINET Controller encountered an None.
request processing error trying to process a Service Request
error from the CPU (e.g. a request to list all
PROFINET devices on the network)
5.8.2 Viewing and Clearing the Local Log Table

The only way to view and clear the data in the Local Log table of the PROFINET Controller is via the Command
Line Interface (CLI). As discussed above, CLI may only be used with the PNC001-Ax module.
• Log data can be viewed via the CLI log or show log commands.
• The Local Log table can only be cleared via the CLI clear log command, which requires Modify level access.
Clearing the PACSystems CPU Fault Tables or restarting the PROFINET Controller module does NOT clear
the Local Log table.
If the PROFINET Controller Local Log table overflows, new entries overwrite the oldest entries, which are lost. If
that happens, the CLI log or show log command indicates the number of entries that have been lost. The count
of lost entries is cleared whenever the Local Log table is cleared.
5.8.2.1 PROFINET Controller Local Log Display
Figure 95 shows a typical display using the log command. The Loc column identifies the device associated with
the log entry by its Device Number. Proficy Machine Edition assigns a unique Device Number for each Remote IO
Device. The Device Number 000 identifies the PNC001 module itself.
Figure 95: Local Log Display
GFK-2571P July 2018 113

The command log details provides more information (Figure 96) about all the entries in the Local Log, including
the Device Names of remote devices that have log entries. For each PACSystems RX3i CPU, there is a one-to-
one correspondence between Device Names and Device Numbers.
Figure 96: Log Details Display
The command log details followed by an entry number displays the information for a single entry. Figure 97
shows the information for log entry 2:
Figure 97: Log Details of a Specific Log Entry
GFK-2571P July 2018 115

5.9 PROFINET Controller Faults in the PACSystems Fault

Tables
The PROFINET Controller logs all (Local, Controller, I/O) faults in its Local Log. In addition, it passes Controller
and I/O faults to the PACSystems CPU where they are logged in the corresponding CPU fault Tables (the
Controller Fault Table or the I/O Fault Table).
5.9.1 Clearing the PACSystems Fault Tables

• Clearing one or both of the CPU’s fault tables has no effect on the Local Log table in the PROFINET
Controller. The Local Log in the PROFINET Controller can only be cleared via a CLI command (applies to
PNC001-Ax module only).
• Clearing one or both of the CPU’s fault tables has no effect on the Diagnosis conditions maintained by any
IO-Device.
• When the PACSystems CPU’s fault tables are cleared, PROFINET-related faults are NOT re-reported, even
if the condition that is causing the fault still exists.
5.9.2 Faults Reported to the PACSystems Controller Fault Table

The following PROFINET Controller-related faults are reported in the Controller Fault Table of the PACSystems
CPU, in addition to being listed in the Local Log Table of the PROFINET Controller.
Group-
Error Description Cause Recommended Correction
Code
11-67 Unable to deliver PROFINET Controller has Upgrade the PROFINET Controller to its
configuration to been configured for latest firmware or disable unsupported
module. feature(s) that are not feature(s) configured for the PROFINET
supported by the version Controller. The features supported for each
of PROFINET Controller firmware revision can be found in the RX3i
firmware in use PROFINET Scanner Important Product
Information, GFK-2573. This document may
be found on the support website.
11-81 Valid module A module configured for a The module should operate properly in the
substitution PROFINET device does not presence of this fault. However, to eliminate
detected. exactly match what is the fault, try one or more of the following:
physically present on the ▪ Make sure the module is installed in the
device, but the device correct location and move if necessary
indicates it is a valid (PNC001 only).
substitution. ▪ Update the configuration stored to the
PROFINET Controller to exactly match the
module present.
▪ Replace the module on the device to match
the configuration.
11-82 Module A module configured for a The module will not operate properly,
configuration PROFINET device does not therefore try one or more of the following:
mismatch during match the module that is ▪ Make sure the module is installed in the
configuration. physically present on the correct location and move if necessary
device. (PNC001 only).
▪ Update the configuration stored to the
PROFINET Controller to equal the actual
module present
▪ Replace the module on the device to match
configuration.
Group-
Error Description Cause Recommended Correction
Code
11-83 Module A module has been hot- Either update the configuration stored to the
configuration inserted into a PROFINET PROFINET Controller to match the module
mismatch IO-Device, and the physically present, or replace the module on
detected after physical module detected the IO-Device to match the PME
module hot- does not match the configuration.
insertion. configured module.
11-84 Configured SFP SFP configured for a port The SFP present should operate properly in
mismatch on the PNC001 does not the presence of this fault. However, to
detected. match what is physically eliminate the fault, either update the
present on the PNC001. configuration to match the actual SFP type in
use, or physically replace the SFP in use with
the type of SFP configured.
13-h 10 PNC001 The PNC001 has Contact customer service.
hardware failure. encountered a hardware
related failure.
135-s 11 PNC001 has A critical fatal error has Contact customer service.
encountered a occurred during normal
critical fatal error. PNC001 operation from
which the PNC001 cannot
recover.
140-i 12 PNC001 has A non-critical error has None. This fault is informational.
encountered a occurred on the PNC001.
non-critical error.
10
h – Error code that provides more information about what part of the PNC’s hardware experienced a failure.
11
s – Error code that provides more information about what caused a fatal error on the PNC.
12
i – Error code that provides more information about a non-critical error.
GFK-2571P July 2018 117

5.9.3 Faults Reported to the PACSystems I/O Fault Table

The following PROFINET Controller related faults are passed to the PACSystems CPU, where they are reported
in the I/O Fault Table of the CPU, in addition to being listed in the Local Log Table of the PROFINET Controller.
Group/
Category/ Recommended
Description Cause
Type/ Correction
Descriptor
3-2-0-0 Loss of Device A configured PROFINET If this is unexpected operation, either
device is no longer present re-connect missing PROFINET device
on the network. on the network, or remove the device
from the PROFINET Controller’s
configuration.
Notes:
The network connection issue might
be in the interconnecting network
between the controller and the
device, and not necessarily at the
device itself
In an MRP ring with a large number of
clients, storing a configuration that
causes all clients to reconfigure (for
example, changing the Domain Name)
may generate a large number of
Loss/Addition of Device faults. This is
expected behavior and all devices
should automatically return to
operational.
3-14-0-0 Loss of sub-module A configured PROFINET If the submodule is missing, then
on PROFINET sub-module is no longer replace the missing submodule on the
device. present. device. If the submodule is present,
check for a malfunction on the
submodule (e.g. loss of field power,
hardware failure, etc.).
3-14-2-0 PROFINET Device’s A PROFINET Supervisor has If this is unexpected operation,
sub-module under taken control of a investigate the reason for Supervisor
control of PROFINET device’s sub- taking control. Investigate reason for
PROFINET module, for which the Supervisor taking control.
Supervisor. PROFINET Controller is
currently configured and to
which it is connected.
3-33-0-0 Loss of network A configured network Repair or replace the missing or
interface on interface on the PROFINET malfunctioning network interface on
PROFINET device. device is no longer present. the device.
network interface taken control of a investigate the reason for Supervisor
under control of PROFINET device’s network taking control.
PROFINET interface, for which the
Group/
Description Cause
Type/ Correction
Descriptor
3-35-0-0 Loss of network A configured network port Repair or replace the missing or
port on PROFINET on the PROFINET device is malfunctioning network port on the
device. no longer present. device.
3-35-1-0 Expected SFP is SFP configured for a port on Insert SFP into port of PNC001 to
missing. the PNC001 module is not match configuration stored to the
physically present. PNC001 or remove the SFP from PME
configuration.
network port under taken control of a investigate reason for Supervisor
control of PROFINET device’s network taking control.
PROFINET port, for which the
3-68-1-0 Unsupported SFP An unsupported (non- The installed SFP is not supported,
detected. Ethernet) SFP is physically replace with supported SFP
connected to a PNC001
port.
3-68-2-0 Invalid SFP An invalid (non-functional) The installed SFP is invalid, replace
detected. SFP is physically connected with a supported SFP
to a PNC001 port.
7-3-0-0 Addition of Device. A configured PROFINET None.
device that was previously Note: In an MRP ring with a large
missing has just been re- number of clients, storing a
connected. configuration that causes all clients to
reconfigure (for example, changing
the Domain Name) may generate a
large number of Loss/Addition of
Device faults. This is expected
behavior and all devices should
automatically return to operational.
7-15-0-0 Addition of A configured PROFINET None.
Submodule submodule that was
previously reported lost has
just been added to the
device.
7-15-1-0 Submodule A configured PROFINET None.
released by submodule that was
PROFINET IO previously controlled by a
Supervisor PROFINET IO Supervisor
has just been released.
7-31-1-0 Extra SFP present An SFP port on the PNC001 Either update the PNC001
on the PNC001. module has been configuration to indicate the SFP is
configured to be empty, but present, or physically remove the
an SFP is present. extra SFP from the PNC001 port.
GFK-2571P July 2018 119

Group/
Description Cause
Type/ Correction
Descriptor
network interface. interface that was
previously reported lost has
been added to the device.
network port. port that was previously
reported lost has been
added to the device.
7-36-1-0 Network port A configured PROFINET None.
released by port that was previously
PROFINET IO controlled by a PROFINET
Supervisor. IO Supervisor has been
released.
9-6-10-0 Multiple Media The PROFINET Controller is Update the PROFINET Controller
Redundancy configured as a Media configuration to change its MRP role
Managers have Redundancy Manager and to either Disabled or Client, or remove
been detected on other Media Redundancy all of the other devices on the
the network. Managers are currently network that are also acting as a
present on the network. Media Redundancy Manager.
9-6-11-0 Multiple Media The PROFINET Controller is No action necessary. The network is
Redundancy configured as a Media expected to only have a single Media
Managers are no Redundancy Manager and it Redundancy Manager present.
longer present on had detected that multiple
the network. Media Redundancy
Managers were on the
network, but now those
other managers are no
longer present.
9-6-12-0 The Media The PROFINET MRP The MRP Ethernet ring is broken.
Redundancy network ring is broken. Possible causes include damaged or
Manager has disconnected cable or power loss to a
detected that the node or switch. Locate and repair the
network ring has cause(s).
been broken.
9-6-13-0 The Media The PROFINET MRP No action necessary. This is the
Redundancy network ring is closed/okay. normal, expected state of an MRP
Manager has Ethernet ring.
detected that the
network ring has
been repaired.
9-11-3-1 Invalid MAC PROFINET Controller no Contact customer service.
address detected. longer has a valid MAC
address.
9-11-3-3 Media redundancy The PROFINET Controller Contact customer service.
configuration error. has encountered a problem
attempting to configure
media redundancy
operation.
Group/
Description Cause
Type/ Correction
Descriptor
9-11-3-4 All critical network The PROFINET Controller Reconnect the configured critical
ports are has detected that all the network ports.
disconnected. configured critical network
ports have lost their links
and are no longer
connected.
9-11-5-z13 Internal runtime PROFINET Controller has Contact customer service.
error. encountered an internal
error during its operation.
9-18-1-1 PNC001 module The temperature detected Reduce the temperature of the
exceeded its by the PNC001 module has environment where the PNC001
recommended exceeded its safe operating module is operating.
operating temperature.
temperature.
9-18-1-2 Watchdog Timeout PNC001 application code Contact customer service.
Error restarted due to a
hardware watchdog
timeout.
9-69-0-0 PROFINET The PROFINET Controller No action is required if no PROFINET
Controller has has become heavily loaded system performance is observed. If
become heavily with activity. action is required to run the
loaded. PROFINET Controller is PROFINET Controller at or below the
running at or above the maximum supported load, reduce the
maximum supported load. load on PROFINET Controller, using
I/O updates experienced by one or both of the following methods:
the PLC may be slower than ▪ Increase the configured update
optimal. Refer to Section rate value (i.e. IO received less
3.1.1. frequently) of one or more
PROFINET Devices configured on
the PROFINET Controller.
▪ Reduce the number of PROFINET
Devices configured on the
9-70-0-0 PROFINET Load applied to PROFINET None.
Controller is no Controller has been
longer heavily reduced to or below the
loaded. maximum supported load,
after it was previously
heavily loaded. Refer to
Section 3.1.1.
13
z: Runtime error detail. Inform value of z to customer support.
GFK-2571P July 2018 121

Group/
Description Cause
Type/ Correction
Descriptor
9-71-0-0 Duplicate IP PROFINET Controller has Either remove the device on the
Address detected detected a duplicate IP network that has the duplicate IP
on the network. Address on the network. Address, or assign a new IP Address
The location associated to either the PROFINET Controller or
with the fault will indicate the conflicting device.
whether the duplication is Note: The Fault Extra Data displays
with the PROFINET the MAC addresses of the conflicting
Controller itself, or with a devices in the MAC 1 field (bytes 8–
configured PROFINET 13) and the MAC 2 field (bytes 14–19).
Device. If the PROFINET Controller is one of
the devices with a conflicting IP
Address, MAC 1 will be 0. This data is
stored in Big Endian (most significant
byte in lowest address) format.
Also, if the conflict is between
PROFINET devices on the network,
the DCP Tool can be used to help find
the conflict. Sorting by IP Address
within the tool may make it easier to
identify the duplicates.
9-72-0-0 Duplicate IP PROFINET Controller has None.
Address conflict detected that a previously
resolved. duplicated IP Address
conflict has been resolved.
The location associated
with the fault will indicate
whether the duplication
was with the PROFINET
Controller itself, or with a
configured PROFINET
Device.
28-37-0-0 Unexpected The PROFINET Controller Consult Device manufacturer
PROFINET Alarm has received a PROFINET documentation.
received. alarm that is unexpected. Note: Alarm details are provided in
Possible causes could the Fault Extra Data
include a malformed
PROFINET Alarm packet or
an Alarm for a PROFINET
sub-module that is not
configured.
28-38-0-0 Manufacturer A PROFINET Alarm has Consult Device manufacturer
specific Diagnosis been received indicating documentation.
Appears PROFINET that a manufacturer Note: Alarm details are provided in
Alarm received. specific diagnostic the Fault Extra Data
condition has been
detected on the PROFINET
device.
Group/
Description Cause
Type/ Correction
Descriptor
28-39-0-0 Manufacturer A PROFINET Alarm has None.
specific Diagnosis been received indicating Note: Alarm details are provided in
Disappears that a manufacturer the Fault Extra Data
PROFINET Alarm specific diagnostic
received. condition has been
resolved on the PROFINET
device.
28-40-x14-0 Channel Diagnosis A PROFINET Alarm has Consult Device manufacturer
Appears PROFINET been received indicating documentation.
Alarm received. that a Channel-level Note: Alarm details are provided in
diagnostic condition has the Fault Extra Data.
occurred on the PROFINET
device.
28-41-x14-0 Channel Diagnosis A PROFINET Alarm has None.
Disappears been received indicating Note: Alarm details are provided in
PROFINET Alarm that a Channel-level the Fault Extra Data
received. diagnostic condition has
been resolved on the
PROFINET device.
28-42-x14-y15 Channel Diagnosis A PROFINET Alarm has Consult Device manufacturer
Alarm received that a Channel-level Note: Alarm details are provided in
(Alarm contains diagnostic condition has the Fault Extra Data.
Extended Channel occurred on the PROFINET
data). device.
28-43-x14-y15 Channel Diagnosis A PROFINET Alarm has None.
PROFINET Alarm that a Channel-level the Fault Extra Data.
received (Alarm diagnostic condition has
contains Extended been resolved on the
Channel data). PROFINET device.
28-44-x14-y15 Channel Diagnosis A PROFINET Alarm has Consult Device manufacturer
Alarm received that a Channel-level Note: Alarm details are provided in
(Alarm contains diagnostic condition has the Fault Extra Data.
Qualified Channel occurred on the PROFINET
data). device.
28-45-x14-y15 Channel Diagnosis A PROFINET Alarm has None.
PROFINET Alarm that a Channel-level the Fault Extra Data.
received (Alarm diagnostic condition has
contains Qualified been resolved on the
Channel data). PROFINET device.
14
x: Type value will be equal to the Channel Error Type field of the PROFINET Alarm.
15
y: Description value will be equal to the Extended Channel Error Type field of the PROFINET Alarm.
GFK-2571P July 2018 123

Group/
Description Cause
Type/ Correction
Descriptor
28-46-0-0 Diagnosis Appears A PROFINET Alarm has Consult Device manufacturer
PROFINET Alarm been received indicating documentation.
received (Alarm that a diagnostic condition Note: Alarm details are provided in
contains only has been detected on the the Fault Extra Data.
Maintenance PROFINET device.
status).
28-47-0-0 Diagnosis A PROFINET Alarm has None.
PROFINET Alarm that a diagnostic condition the Fault Extra Data.
received (Alarm has been resolved on the
contains only PROFINET device and
Maintenance maintenance is no longer
status). required.
28-48-0-0 Diagnosis Appears A PROFINET Alarm has Consult Device manufacturer
PROFINET Alarm been received indicating documentation.
received. that a diagnostic condition Note: Alarm details are provided in
has been detected on the the Fault Extra Data.
PROFINET device.
28-49-0-0 Diagnosis A PROFINET Alarm has None.
PROFINET Alarm that a diagnostic condition the Fault Extra Data
received. has been resolved on the
PROFINET device.
28-50-0-0 PROFINET Status A PROFINET Alarm has Consult Device manufacturer
Alarm received. been received indicating a documentation.
status change on the Note: Alarm details are provided in
PROFINET Device. the Fault Extra Data
28-51-0-0 PROFINET Update A PROFINET Alarm has Consult Device manufacturer
Alarm received. been received indicating a documentation.
change to an operating Note: Alarm details are provided in
parameter has been made the Fault Extra Data
by an external device.
28-52-0-0 Port Data Change A PROFINET Alarm has Consult Device manufacturer
PROFINET Alarm been received indicating a documentation.
received (Alarm Port change on the Note: Alarm details are provided in
contains PROFINET device. the Fault Extra Data
manufacturer
specific data).
28-53-x14-0 Port Data Error A PROFINET Alarm has Consult Device manufacturer
Alarm received. that a Port Error has Note: Alarm details are provided in
occurred on the PROFINET the Fault Extra Data
device.
28-54-x14-0 Port Data Error A PROFINET Alarm has None.
PROFINET Alarm that a Port Error condition the Fault Extra Data
received. has been resolved on the
PROFINET device.
Group/
Description Cause
Type/ Correction
Descriptor
28-55-x14-y15 Port Data Error A PROFINET Alarm has Consult Device manufacturer
Alarm received that a Port Error has Note: Alarm details are provided in
(Alarm contains occurred on the PROFINET the Fault Extra Data
Extended Channel device.
Data).
28-56-x14-y15 Port Data Error A PROFINET Alarm has None.
contains Extended PROFINET device.
Channel Data).
28-57-x14-y15 Port Data Error A PROFINET Alarm has Consult Device manufacturer
Alarm received that a Port Error has Note: Alarm details are provided in
(Alarm contains occurred on the PROFINET the Fault Extra Data
Qualified Channel device.
Data).
28-58-x14-y15 Port Data Error A PROFINET Alarm has None.
contains Qualified PROFINET device.
Channel Data).
28-59-0-0 Port Data Change A PROFINET Alarm has Consult Device manufacturer
PROFINET Alarm been received indicating a documentation.
received (Alarm Port change on the Note: Alarm details are provided in
contains only PROFINET device. the Fault Extra Data
Maintenance
status).
28-60-0-0 Network A PROFINET Alarm has Consult Device manufacturer
Component been received indicating documentation.
Problem Alarm that a network component Note: Alarm details are provided in
Received (Alarm has encountered a problem the Fault Extra Data
contains on the PROFINET Device.
manufacturer
specific data).
28-61-x14-0 Network A PROFINET Alarm has Consult Device manufacturer
Problem Appears that a network component Note: Alarm details are provided in
PROFINET Alarm has encountered a problem the Fault Extra Data
received. on the PROFINET Device.
28-62-x14-0 Network A PROFINET Alarm has None.
Component been received indicating Note: Alarm details are provided in
Problem that a network component the Fault Extra Data
Disappears problem has been resolved
PROFINET Alarm on the PROFINET Device.
received.
GFK-2571P July 2018 125

Group/
Description Cause
Type/ Correction
Descriptor
28-63-x14-y15 Network A PROFINET Alarm has Consult Device manufacturer
received (Alarm on the PROFINET Device.
contains Extended
Channel Data).
28-64-x14-y15 Network A PROFINET Alarm has None.
received (Alarm
contains Extended
Channel Data).
28-65-x14-y15 Network A PROFINET Alarm has Consult Device manufacturer
received (Alarm on the PROFINET Device.
contains Qualified
Channel Data).
28-66-x14-y15 Network A PROFINET Alarm has None.
received (Alarm
contains Qualified
Channel Data).
28-67-0-0 Network A PROFINET Alarm has Consult Device manufacturer
Problem Alarm that a network component Note: Alarm details are provided in
Received (Alarm has encountered a problem the Fault Extra Data
contains on the PROFINET Device.
Maintenance
status only).
Chapter 6 Redundant Media
The PACSystems PROFINET Controller supports PROFINET Media Redundancy Protocol (MRP). The PROFINET
Controller can be used as either a Media Redundancy Manager or Media Redundancy Client on a redundant
media ring.
Media Redundancy enables the network to recover from a failure at any single network link or network node.
Because it operates transparently to applications using the network, no changes to the application are needed
to use media redundancy.
• PROFINET Media Redundancy Protocol
• MRP Performance
• Ring Topology with One Controller
• Ring Topology with Multiple Controllers
• Setting Up Media Redundancy Protocol for a PROFINET IO-Controller
• Sequence for Enabling Media Redundancy
• Sequence for Replacing a Media Redundancy Manager
• Procedure for Disabling Media Redundancy
The following table shows which PROFINET Scanners/Devices support MRP.
PROFINET Scanner/Device Acronym PROFINET Media Redundancy
Protocol (MRP)
RX3i CEP Carrier RX3i CEP √
RX3i Genius* Communications Gateway RX3i GCG √
PAC8000 PROFINET Scanner (PNS) Module PAC8000 PNS √
RSTi PROFINET Network Adaptor RSTi PNS
RSTi-EP PROFINET Network Adaptor RSTi-EP PNS √
RX3i PROFINET Scanner (PNS) Module RX3i PNS √
VersaMax PROFINET Scanner (PNS) Module Versamax PNS √
VersaMax IP PROFINET Scanner Module VersaMax/IP PNS √16
VersaPoint PROFINET Scanner VersaPoint PNS √
16
Bumpless operation is only guaranteed at IO Update rates at or above 128 ms
GFK-2571P July 2018 127

Chapter 6. Redundant Media
6.1 PROFINET Media Redundancy Protocol

PROFINET Media Redundancy Protocol (MRP) supports devices configured in a ring topology with a maximum
of 1 Manager and 63 Clients. It is based on the functions of IEC 62439. Media Redundancy Protocol may not be
routed between different IP subnets.
Each device within a Redundant Media network has at least two physical pathways to two other devices on the
network. To connect to the ring, each device requires an integrated switch with at least two external ports
(ring ports) that support Media Redundancy Protocol. Devices that are not MRP-capable can be connected to a
device like an MRP-capable switch in the ring, but they cannot be in the ring themselves. The redundant paths
extend only to the devices on the ring that are MRP-capable and enabled.
One of the devices on the ring must be configured as the Media Redundancy Manager (MRM), and all the other
devices must be configured as Media Redundancy Clients (MRCs).
The Media Redundancy Manager disables one of the segments of the ring so that a loop is not created in the
network. To disable a segment, the Media Redundancy Manager either:
• blocks one of its two Ethernet switch ports used to form the ring when the ring is closed, or
• forwards both switch ports if one of the other ring segments is missing (ring open) and passes messages
through the Media Redundancy Manager to get to devices on the other side of the failed segment.
The PROFINET Controller can be used as either a Media Redundancy Manager or Client. The PNS can be used as
a Media Redundancy Client.
Typically, one PROFINET Controller module in each ring I/O network is configured as the media redundancy
manager. All other nodes in the ring (I/O Devices, network switches, and other PROFINET Controllers) must be
configured as media redundancy clients.
6.1.1 MRP Failover Performance

A network using Media Redundancy Protocol recovers from a ring failure within 80 milliseconds when running
at 100 Mbps full duplex with default values. Actual failover time depends on the device responsiveness to
network disconnection and reconnection, number of devices in the ring, media speed, length of media, and
frequency of sending test frames over the network. Network recovery time is shorter with fewer devices, faster
media speed, and shorter media lengths. If all MRC devices provide LinkUp/LinkDown indications, the network
recovery time will be significantly shorter than 80ms. Third-party devices in the MRP ring may introduce
additional network recovery time.
When MRCs do not provide LinkUp/LinkDown detection, network recovery time also depends upon the test
packet timeout interval, which is the product of the Default Test Interval and the Test Monitoring Count plus 1
that have been set for the Media Redundancy Manager. These parameters determine the frequency for
network integrity checks and the number of failed integrity checks to allow before declaring a ring failure. For
an PACSystems PROFINET Controller acting as Media Redundancy Manager, these parameters are set as part
of the Proficy Machine Edition hardware configuration. (For example, the default test packet timeout interval is
20 ms × (3+1) = 80 ms.)
Each device in the ring must be able to detect the failure or recovery of a connection. When using third-party
devices in a redundant media ring, failover time will be affected by the performance of these devices. For
devices that do not detect the failure or recovery of a connection via LinkUp/LinkDown indication, the shortest
guaranteed failover time will be the test packet timeout interval, as described above.
For bumpless network recovery (without disturbing I/O communications to an I/O Device), the Update Rate for
the I/O Device should be configured to be greater than 1/2 of the network recovery time. This permits the ring
to be disconnected or reconnected without timing out the communication connection between the I/O Device
and its I/O Controller.
1000Base-T SFPs on a PNC001 module can introduce significant network recovery time. For best MRP
performance with a 10/100/1000 Mbps copper Ethernet MPR ring network, configure the RJ45 Ethernet ports
(Ports 1 and 2) as MRP ring ports instead of those SFP ports (Ports 3 and 4) with 1000Base-T SFPs.
Note: The 1000BaseT SFPs qualified for use with the RX3i PNC001 module can only detect a ring break when
running at 1 Gbps at the IEEE 802.3 Clause 40 standard requirement of 750ms. In order to experience
bumpless I/O at a 16ms I/O Update rate with these SFPs at 1 Gbps, the MRM must be configured with
a Test Packet Interval of 10ms and a Test Packet Count of 2.
GFK-2571P July 2018 129

6.1.2 Bumpless Operation with MRP

The PROFINET Controller supports bumpless operation with GE PROFINET I/O Devices if and only if
specific conditions are met. Bumpless operation means that a single break in an MRP ring will not
cause the PROFINET connection to be lost and there is no observed loss and addition of PROFINET
I/O Devices while the ring network recovers.
Without bumpless MRP, when a device is lost, it must be re-acquired by the I/O Controller; a typical
recovery time is on the order of seconds.
There are two ways an MRM detects a break in the ring:
• A message from an MRC that provides LinkUp/LinkDown detection
• Use of a test packet timeout interval
A network using Media Redundancy Protocol recovers from a ring failure within 80 milliseconds
when running at 100/1000 Mbps full duplex with default Media Redundant Manager (MRM) test
packet values. Actual failover time depends on the device responsiveness to network disconnection
and reconnection, number of devices in the ring, media speed, length of media, and frequency of
sending test frames over the network. Network recovery time is shorter with fewer devices, faster
media speed, and shorter media lengths. Third-party devices in the MRP ring may introduce
additional network recovery time. Network recovery time is limited by the ring participant with the
slowest ring failure recovery time. Devices that do not provide LinkUp/LinkDown detection should be
taken into account when calculating network recovery time.
For bumpless network recovery (without disturbing IO communications to an I/O-Device), the I/O
Update Rate for the I/O-Device should be configured to be greater than 1/2 of the network recovery
time. This permits the ring to be disconnected or reconnected without timing out the communication
connection between the I/O Device and its I/O-Controller.
In order to insure correct MRP operation, it is important to connect the correct Ethernet ports of the
PROFINET Controller and devices to the MRP ring. The ports connected to the ring must be the same
ports configured as MRP Ring Ports. Failure to connect the configured ports will prevent the
PROFINET Controller and devices from correctly participating in the MRP ring.
Disclaimer: Pulling a fiber SFP cable out of the SFP cage (as opposed to cutting a fiber cable), can
have unpredictable performance (and may lose devices in a properly configured MRP ring) due to the
fact that the light is still seen by the SFP as the cable is being removed so that data is lost
significantly before the SFP can detect that the connection has been lost.
6.1.3 MRP Operation for I/O Update Rates of 16ms or Greater

The PACSystems RX3i PROFINET IO Controller supports bumpless operation at 16ms with the
requirement that the MRP Manager be configured for an MRP Test Packet Interval and MRP Test
Packet Count that is faster than the fastest IO timeout possible.
For example:
Assume the worst-case scenario when a ring break occurs immediately after the device received a
test packet and immediately before the device was scheduled to receive an I/O packet. In the case of
a 16ms I/O Update Rate, a timeout will occur after three consecutive missed I/O packets, which can
occur in slightly over 32ms. Assuming that the Test Packet Interval is configured for 10ms and the
Test Packet Count is configured for 2, the PROFINET Controller can detect a ring break in just less
than 30ms. This ring recover scenario would look like the following timeline.
Figure 98: Timeline for Successful MRP Ring Repair at 16ms I/O Update Rate
To ensure a successful ring recovery using the Test Packets at a 16ms I/O Update rate or above,
make sure the following statement is true:
Test Packet Interval × (Test Packet Count + 1) < I/O Update Rate × 2
6.1.4 MRP Operation at I/O Update Rates Less Than 16ms

The PACSystems implementation of MRP supports fast LinkUp/LinkDown detection on devices, an
optional part of the MRP standard. This allows an MRC experiencing a network link failure or recovery
to send LinkUp/LinkDown messages to the MRM immediately. The MRM can heal the network
without needing to wait for multiple test-packet timeouts to detect the failure. This feature allows
the network recovery time to be significantly shorter than the test packet timeout interval because
the break is detected immediately.
6.1.5 Minimum I/O Rate When Configured in an MRP Ring
The minimum I/O rate that is possible for bumpless operation depends on the speed and the type of
physical connection being used for the MRP ring ports. PACSystems PROFINET I/O Controllers
support a specified number of PACSystems PROFINET I/O devices running at or above the minimum
I/O Update Rate listed in the table below.
GFK-2571P July 2018 131

6.1.6 Minimum I/O Update Rates for Bumpless Operation in an MRP

Ring Topology
If your application requires the PROFINET IO to operate in a bumpless fashion (i.e., experience no
Loss of Device faults and no defaulting of IO) whenever a break in the ring occurs, then the IO Update
Rates of all the devices in that ring must be no smaller than the Minimum IO Update Rate described
in this table.
When no third-party items participate in the ring:
Minimum I/O Update Additional Media Redundancy

Ring Port Usage I/O-Devices in the Ring
Rate (ms) Manager Requirements
VersaMax PNS and/or RX3i

1 None
CEP
An RX3i PNS (or RX3i GCG)

PNC001 Ports 1 & 2 both 2 None
using Port 1 & Port 2 for ring
operating at 100 Mbps
An RX3i PNS using Port 3 or Set Default Test Interval to
16
Port 4 for the ring 10ms. Set Test Monitoring
An RSTi-EP PNS 32 Count to 2.
CPL410/CPE400/CPE330 VersaMax PNS and/or RX3i

8 None
Embedded PROFINET CEP
(LAN2): Both Ports An RX3i PNS (or RX3i GCG)
operating at 100 Mbps 8 None
using Port 1 & Port 2 for ring
PNC001 Port 1 or Port 2

An RX3i PNS, VersaMax PNS
PNC001 Port 3 or Port 4 and/or RX3i CEP, or RX3i 16
Set Default Test Interval to
operating at any speed GCG
10ms. Set Test Monitoring
CPL410/CPE400/CPE330 Count to 2.
Embedded PROFINET
(LAN2): Either Port An RSTi-EP PNS 32
CPE100/CPE115 Embedded An RX3i PNS, VersaMax PNS
PROFINET (LAN2): and/or RX3i CEP, or RX3i 16
Port 2 & Port 3 operating at GCG
None
100Mbps
An RSTi-EP PNS 32
If any third-party items participate in the ring, the minimum I/O Update Rate is the larger of the following two options,
regardless of which ports are used for the ring:
• The smallest I/O Update Rate selectable within PME that is more than 1/2 of the largest worst-case ring recovery
time among the third-party items. For example, if the manufacturer states that the worst-case ring recovery time is
96ms, the rate needs to be more than 96ms divided by 2, which is 48ms. The next available rate above 48ms is
64ms.
• 16ms I/O Update Rate. When using an I/O Update Rate of 16ms, set the Default Test Interval to 10ms and the Test
Monitoring Count to 2 on the Media Redundancy Manager.
6.1.7 MRP Ring Ethernet Traffic Storm Prevention

The LAN2 Ethernet ports used for the embedded IO-Controller function in CPL410, CPE400, CPE330
and CPE100/CPE115 may be used as an MRP Ring Manager (MRM). Since LAN2 defaults to be an
Ethernet switch, it is required that the physical ring must not be connected until a MRM
configuration has been stored to any Ethernet node on the ring, including to LAN2 on CPL410,
CPE400, CPE330 or CPE100/CPE115.
Failure to have an active MRM configured in an Ethernet ring will result in an Ethernet traffic storm
caused by the ring’s network loop topology. The Ethernet traffic storm will prevent communication
to all Ethernet nodes connected to the ring until the ring is broken or an MRM is configured.
The CPL410, CPE400, CPE330 and CPE100/CPE115 maintains its MRM status after a hardware
configuration clear and until it is subjected to a power cycle. After clearing the hardware
configuration, and before power-cycling a CPU that was configured as an MRM in a ring topology, it is
recommended that either:
a) The ring be physically broken by disconnecting an Ethernet port on any network node in the
ring, or
b) Any other network node in the ring be configured as a MRM.
GFK-2571P July 2018 133

6.1.8 Third-party MRP Manager Use with PROFINET Controller as MRP

Client
When using a third-party MRP Manager, it is recommended to set the MRP Manager Test Monitoring
Interval to 10ms and Test Monitoring Count to 2 and/or connect the PROFINET Controller client
directly to a device that provides fast link down detection.
Failure to follow these recommendations may result in degraded MRP Ring update performance for
bumpless operation, due to the speed at which ring breaks are detected.
Use the tables below as a guide when choosing not to follow the recommendations.
CPE100/CPE115 Embedded PROFINET IO- Minimum Recommended I/O Update Rate

Controller (ms)
Ring Port Connection
Cu Fixed Ports @100Mbps 16
CPL410/CPE400/CPE330 Embedded PROFINET IO- Minimum Recommended I/O Update Rate

Controller Ring Port Connection (ms)
Cu Fixed Ports @1Gbps 17
64
PNC001 Ring Port Connection Minimum Recommended I/O Update Rate

(Port Type or SFP Type) (ms)
Cu Fixed Ports @1Gbps 512
Cu SFP @100Mbps 4
Cu SFP @1Gbps 512
100Base FX SFP (MMF) – 100Mbps 16
100Base LX10 SFP (SMF) – 100Mbps 16
1000Base SX SFP (MMF) - 1Gbps 32
1000Base LX SFP (SMF) - 1Gbps 64
1000Base ZX SFP (SMF) - 1Gbps 64
Disclaimer: Performance numbers for SFPs are with GE branded SFPs, or are supported / tested only
with Avago or Finisar vendors. Other vendors may produce varying performance results.
17
Note that if the port is configured as a Critical Network Port, the data rate is forced to 100Mbps. This results in the
minimum update rate as indicated in the row above. For further details, refer to Critical Network Ports in Section 3.5.2.
6.2 Ring Topology with One Controller

The following diagram illustrates a simple ring topology with one RX3i CPU Node and three I/O Devices on the
same PROFINET network. In Figure 99, the PROFINET Controller module in the RX3i controller is configured to
be the Media Redundancy Manager and the I/O Devices, in this case PNS modules, are configured to be Media
Redundancy Clients.
Figure 99: Ring Topology with One Controller

As a Media Redundancy Manager, the PROFINET Controller detects when the network ring has been broken
and repaired. Each time the PROFINET Controller detects that the ring has been broken or repaired, a fault is
reported in the Local Log table and that condition is passed to the RX3i CPU to be registered in the CPU fault
table. In addition, the PROFINET Controller keeps a count of break/repair detections. In the PNC001-Ax module,
this may be viewed via the CLI show rdnmedia command.
As a Media Redundancy Manager, the PROFINET Controller detects whether another Media Redundancy
Manager is on the same ring. If more than one Media Redundancy Manager is present on the same ring, the
PROFINET Controller logs an entry in its Local Log table and passes the fault to the RX3i CPU fault table. Upon
detecting that there are no longer multiple Media Redundancy Managers on the ring, the PROFINET Controller
logs a fault in the Local Log and passes this to the RX3i CPU to be registered in the CPU fault table. This
indicates that the previously invalid setup has subsequently been resolved.
GFK-2571P July 2018 135

6.3 Ring Topology with Multiple Controllers

Figure 100 shows a more complex network. There is one RX3i CPU node with two PROFINET Controllers, a
second RX3i CPU node with one PROFINET Controller, and five I/O Devices, in this case, PNS modules. The
PROFINET Controllers depicted are PNC001 modules, but could be embedded PROFINET Controllers.
All devices are on the same network ring. One PROFINET Controller is configured as the Media Redundancy
Manager (MRM); the other PROFINET Controllers and all PROFINET Scanners are configured as Media
Redundancy Clients (MRCs).
Figure 100: Ring Topology with Multiple Controllers
6.4 Setting Up Media Redundancy Protocol

Media Redundancy must first be set up in the hardware configuration of all devices on the LAN. Instructions for
configuring Media Redundancy using PROFICY Machine Edition are located in Chapter 3 Configuration.
Only one device on the ring can be configured as the Media Redundancy Manager. All other devices on the ring
must be configured as Media Redundancy Clients.
6.4.1 Media Redundancy Setup for a PROFINET Controller

A PROFINET Controller can be configured as either a Media Redundancy Manager (MRM) or a Media
Redundancy Client (MRC). By default, Media Redundancy is disabled for the PROFINET Controller. To be used, it
must first be enabled and set up in the configuration.
Configuring a Media Redundancy Manager includes specifying a test interval and retry count for ring failure
checking. It also includes specifying which of the ports on the PROFINET Controller are connected to the ring.
The PROFINET Controller stores the current Media Redundancy Protocol configuration settings in non-volatile
storage so it can configure the switch port appropriately at power-up. The PROFINET Controller disables all its
external Ethernet ports until it has retrieved and applied the Media Redundancy Protocol configuration from its
non-volatile storage.
If a configuration containing a PROFINET Controller set up as a Media Redundancy Manager is subsequently
used to generate another configuration, using Generate Secondary Hardware Configuration from the Current
Configuration, for example, the PROFINET Controller configuration in the copy is automatically defaulted to a
Media Redundancy Client.
GFK-2571P July 2018 137

6.5 Sequence for Enabling Media Redundancy

To avoid network loops occurring before the Media Redundancy configuration parameters are stored, the
network must first be set up with the ring broken at one point. Otherwise, packets could continuously cycle on
the network and use up significant network bandwidth. The ring should not be closed until the Media
Redundancy configuration parameters are successfully stored to the Media Redundancy Manager and the
Media Redundancy Manager is operational.
If more than one Media Redundancy Manager is present on the same ring, each PROFINET Controller that is
configured as a Media Redundancy Manager will log a fault in its Local Log and in the RX3i CPU’s I/O Fault
Table. When the RX3i configuration is cleared, the Media Redundancy configuration parameters (Media
Redundancy Manager or Client) are kept until a new setting is stored. If power is lost, the Media Redundancy
configuration settings are preserved.
Note: When configuring a Media Redundancy Manager in an open ring, the module may initially report the
ring to be closed. This indication will immediately be followed by a ring open event. This is expected behavior
defined by the MRP specification.
6.6 Sequence for Replacing a Media Redundancy Manager

If it is necessary to replace the PROFINET Controller that is serving as the Media Redundancy Manager, the
replacement module must be set up as a Media Redundancy Manager before adding it to the ring. Alternatively,
the ring must be opened before powering up the new module and adding it to the network, as described above.
The following procedure can be used to replace a PNC001 module that is operating as Media Redundancy
Manager without disrupting the network.
1. Verify that the ring has no breaks in it, or that the only break involves the Media Redundancy Manager
itself. If the ring is already broken someplace else, the Media Redundancy Manager must remain
operational at all times or connectivity between the remaining devices is not guaranteed.
2. Physically disconnect both of the ring’s network connections from the PNC001 module that is serving as
the Media Redundancy Manager.
3. Remove the disconnected PNC001 module from the RX3i rack.
4. Using the Machine Edition programmer, make sure the configuration encompassing the removed PNC001
module is stored to the RX3i CPU.
5. Insert the replacement PNC001 module into the RX3i rack in the allocated slot.
6. Using the Machine Edition programmer, view the Fault Tables to make sure the PNC001 module is
configured correctly.
7. Physically reconnect both of the ring’s network connections to the replacement PNC001 module.
GFK-2571P July 2018 139

6.7 Procedure for Disabling Media Redundancy

When disabling Media Redundancy, the ring must be physically opened before storing configuration to the
modules. Here is the procedure to successfully disable Media Redundancy on a network.
1. If the ring has no breaks in it, physically disconnect one (and only one) of the ring’s network connections
from the PROFINET Controller that is currently serving as the Media Redundancy Manager.
2. Change the configuration for the device that is the Media Redundancy Manager so that it will no longer
serve as the Media Redundancy Manager. If an RX3i PROFINET Controller is the Media Redundancy
Manager, use Proficy Machine Edition to disable the Media Redundancy role on that PROFINET Controller
and then to download the hardware configuration. (If a third-party I/O controller is the Media Redundancy
Manager, the appropriate third-party configuration tool must be used instead.)
Chapter 7 Network Management
The PROFINET Controller supports the SNMP (Simple Network Management Protocol) and LLDP (Link Layer
Discovery Protocol) standards to facilitate network management.
• SNMP
o Overview of SNMP
o Supported SNMP Features
o SNMP Read Access
o SNMP Write Access
o MIB-II Groups Supported
o MIB-II System Group Values
• LLDP
o Overview of LLDP
o LLDP Operation
o LLDP TLV Structures
GFK-2571P July 2018 141

Chapter 7. Network Management
7.1 SNMP
The built-in SNMP (Simple Network Management Protocol) Server/Agent function on the PROFINET Controller
can be used by a third-party SNMP Client or Network Management Station to access network data.
7.1.1 Overview of SNMP

SNMP is a UDP-based network protocol that facilitates the exchange of management information between
network devices. An SNMP-managed network consists of three key components: managed devices, agents, and
network management systems (NMS).
A managed device is a network node that contains an SNMP agent and that resides on a managed network.
Managed devices exchange management information with NMSs via their local agent.
An agent is a network management software module that resides on a managed device. An agent maintains a
collection of management information that it provides in an SNMP-compatible format upon request to NMSs.
An NMS executes applications that monitor and control managed devices.
The collections of management information maintained by agents and managed devices are generally referred
to as Management Information Bases (MIBs). A MIB is a collection of information organized into a hierarchical
structure where related items are grouped together in “groups.” MIBs are used to organize and standardize the
management information on agents and can be accessed via commands provided within the SNMP protocol.
The SNMP protocol is currently defined by five protocol specifications: SNMPv1, SNMPv2, SNMPv2c, SNMPv2u,
and SNMPv3.
NMSs use four basic classes of SNMP commands to retrieve and alter data on managed devices
• The read (GET) command is used by an NMS to monitor managed devices through examination of the
values of different variables maintained within the managed devices’ MIBs.
• The write (SET) command is used by an NMS to control devices through modification of the values
maintained by the managed devices within their MIBs.
• The trap (TRAP, INFORM) command is used by an NMS to get asynchronous notifications when certain
events occur on managed devices. In SNMP Version 2, traps are not set via the protocol but are defined at
the managed device by local action.
• Traversal operations (GETNEXT and GETBULK) are used by an NMS to determine which variables a
managed device supports and to sequentially gather information from the MIBs.
SNMP is a well-defined protocol; additional information is available in the literature and on the World Wide
Web.
7.1.2 Supported SNMP Features

The PROFINET Controller supports:
• SNMPv1 and SNMPv2c
• MIB-II (see RFC 1213 for details)
• LLDP MIB (see IEEE 802.1AB for details)
• LLDP 802.3 Extension MIB (see IEEE 802.1AB for details)
The PROFINET Controller does not:
• Support SNMPv3.
• Provide asynchronous notifications via SNMP.
• Generate SNMP TRAP or INFORM messages.
7.1.3 SNMP Read Access

SNMP provides standard commands that allow a client to read SNMP data. The PROFINET Controller supports
these commands:
GET
GETNEXT
GETBULK
The SNMP Community strings supported for read access are:
• public18
• pub18
• icmp18
• private18
• priv18
• ge_pnc19
These community strings are fixed and cannot be changed.
7.1.4 SNMP Write Access

SNMP should not be used to change parameters on the PROFINET Controller module.
• For PNC001 firmware version 2.05 and earlier, the SNMP SET command succeeds for the variables in some
MIBs/groups, but fails for the variables in other MIBs/groups. Changes made using SNMP SET change only
the SNMP variable itself, do not affect the PNC001 module operation, and are not saved across a power-
cycle or restart. For example, setting the sysName variable from the System Group does not change the
Device Name of the PNC001 module.
• The SNMP Set command for PNC001 firmware version 2.10 and later is disabled.
18
Requires PNC firmware version 2.05 or later.
19
Requires PNC firmware version 2.10 or later.
GFK-2571P July 2018 143

7.1.5 MIB-II Groups Supported

The PROFINET Controller supports all of the mandatory values in the following groups of the MIB-II
specification:
• System group
• Interfaces group
• IP group
• ICMP group
• TCP group
• UDP group
• Transmission group (802.3 Ethernet subset)
• SNMP group
The EGP group and Address Translation group of MIB-II are not supported.
The meanings of the values in these groups are well defined in the standard literature. However, the contents
of some values are implementation-specific. This section explains contents of values specific to the PROFINET
Controller.
7.1.5.1 Interface Number
Many MIB-II groups use an SNMP interface number to refer to a device port. For the PROFINET Controller
module the interface numbers are:
Physical Port SNMP Interface Number
External Port #1 1
External Port #2 2
External Port #3 3
External Port #4 4
Internal Data Port 5
7.1.5.2 MIB-II Interface Group Values

For the MIB-II Interface Group, the ifDescr value provides a textual description of the corresponding
interface/port. The values returned for that item are the same as the port numbers listed above.
The counters ifInDiscards and ifInUnknownProtocols are always reported as zero.
7.1.6 MIB-II System Group Values

Many of the items provided by the MIB-II System Group are implementation-specific. The values that are
returned for the PROFINET Controller are described in the following table.
Name Value
sysDescr Text description of the device being managed. For example:
GE Intelligent Platforms PROFINET IO-Controller, IC695PNC001
sysObjectID Uniquely identifies the kind of device being managed. The first part of the value
returned (1.3.6.1.4.1.24893) indicates that this is a GE Intelligent Platforms device.
The two numbers after that (1.5) indicate that it is a product made for the Control
Systems Business. The three numbers after that identify (in order):
▪ Family: RX3i = 1
▪ Product: PROFINET Controller = 2
▪ Model: (specific to each Family/Product combination)
For the RX3i PNCr: 1.3.6.1.4.1.24893.1.5.1.2.1
sysContact Nothing (empty string)
sysName The Device Name assigned to the node. If the Device Name hasn’t been assigned yet,
an empty string is returned.
sysLocation Nothing (empty string)
sysServices 79 (0x4F)
This value indicates the PROFINET Controller has Layers 1–4 (physical, datalink,
network and transport) and Layer 7 (application) functionality.
GFK-2571P July 2018 145

7.2 LLDP
The PROFINET Controller implements the Link Layer Discovery Protocol (LLDP). A PROFINET IO-Supervisor or
other network host may use LLDP to discover the PROFINET network.
7.2.1 Overview of LLDP

The Link Layer Discovery Protocol is an IEEE standardized protocol used by network devices to advertise their
identities and capabilities and receive that information from physically adjacent link layer peers.
LLDP data packets are sent by devices from each of their interfaces at fixed intervals. The LLDP packets are
multicast and are not forwarded by network switches.
Each LLDP packet consists of one LLDP Data Unit (LLDPDU). Each LLDPDU is a sequence of Type-Length-Value
(TLV) structures.
7.2.1.1 LLDP Data Unit Contents
Chassis ID TLV structure (mandatory, always first)
Port ID TLV structure (mandatory, always second)
Time to Live TLV structure (mandatory, always third)
Optional Structures (any number of these, in any order)
.
.
.
End of PDU TLV (mandatory, always last)
7.2.2 LLDP Operation

The LLDP agent in the PROFINET Controller multicasts LLDP messages to the network at 5 second intervals, or
when a change occurs in any of the local data that is delivered within the LLDP message. The LLDP messages
are transmitted from each external port that is connected to a network.
7.2.3 LLDP TLVs

The following is a brief description of the RX3i PROFINET Controller LLDP TLVs.
7.2.3.1 Chassis ID TLV
The Chassis ID is always the first TLV in the LLDPDU. Chassis ID identifies the particular device on the network.
PROFINET defines two possible Chassis ID formats; each format has a different Chassis ID subtype. The
PROFINET Controller generally uses the Name of Station (NOS) as the Chassis ID. If for some reason the station
name is changed to the empty string “”, the internal MAC address is used instead.
ID Subtype Meaning Value
7 PNIO Chassis ID Name of Station (character string)
4 MAC Address Internal MAC Address of Ethernet controller
7.2.3.2 Port ID TLV

The Port ID is always the second TLV in the LLDPDU. The Port ID identifies the individual network port on the
device. PROFINET defines the Port ID as a character string.
ID Subtype Meaning Value
7 PNIO Port ID “port-PPP-SSSSS” (length = 14 bytes)
PPP specifies the decimal port number in the range 001 to 004. SSSSS specifies the decimal slot number of the
Controller in the range 00000 to 65535.
7.2.3.3 Time to Live TLV
Time to Live is always the third TLV in the LLDPDU. Time to Live specifies the number of seconds that the
information in this LLDPDU remains valid after delivery on the network. A Time to Live value of 0 instructs the
receiver to immediately invalidate the data in this LLDPDU and is issued when the PROFINET Controller has
changed a parameter that is advertised in its LLDP.
The PROFINET Controller sets the Time to Live value to 20 seconds.
7.2.3.4 End of PDU TLV
The End of PDU TLV is always the last TLV in the LLDPDU. This TLV carries no device information.
7.2.3.5 PROFINET Port Status TLV
The PROFINET Port Status TLV indicates the current PROFINET status of the network port over which this LLDP
message is sent. Since the PROFINET Controller does not support RT Class 2 or RT Class 3, the subfields are set
to off (0x0000).
7.2.3.6 PROFINET MRP Port Status TLV
The PROFINET MRP Port Status indicates the current MRP status of the network port over which this LLDP
message is sent.
This TLV is required when the LLDP sender is an MRP port. It is not present in the LLDP packet issued from a
non-MRP port.
The PROFINET Controller supports the following values:
Subfield Value
MRP Domain ID Contains the MRP domain UUID. Assigned internally by the network node.
Set to 0xFFFFFFFF-FFFF-FFFF-FFFF- FFFFFFFFFFFF.
MRRT Port Status 0x00 = Off / Not Used
GFK-2571P July 2018 147

7.2.3.7 PROFINET Chassis MAC TLV

The PROFINET Chassis MAC indicates the internal MAC address used by the PROFINET stack. This is not the
MAC address of any individual network port.
7.2.3.8 MAC/PHY Config/Status TLV
The MAC/PHY Configuration/Status indicates the supported auto-negotiation capability, the current
negotiated capability, and the Medium Attachment Unit (MAU) type of the network port over which this LLDP
message is sent.
Field Values RX3i PROFINET Controller
Auto- Bit 0: Auto-negotiation supported (1= Yes, 0 = No) 0x03 (Auto-negotiation
negotiation Bit 1: Auto-negotiation status supported and enabled)
Support/Status (1 = Enabled, 0 = Disabled)
Bits 2-7: Reserved
Auto- Note: There are no AutoNegCapability definitions for Copper Ports:
negotiation 100Base FX or LX (HD or FD). A device that supports 0x6C03 = 10/100/1000T HD+FD
Advertised these must advertise “Other”. SFP Ports:
Capability (Depends on SFP type)
0x000C = 1000 LX/SX HD+FD
0x6C03 = 10/100/1000T HD+FD
0x8000 = Other (100 FX, LX)
SC Fiber Ports:
0x8000 = Other (100 FX)
Operational Typical values are: Copper Ports:
MAU Type 0x000B: 10BaseT FD 0x001E = 1000T, FD
0x0010: 100BaseTX FD SFP Ports:
0x0012: 100Base FX FD (Multi-mode fiber) (Depends on SFP type)
0x0018: 1000BaseLX FD (Long wavelength fiber) 0x0012 = 100 FX, LX
0x001A: 1000BaseSX FD (Short wavelength fiber) 0x0018 = 1000 LX, FD
0x001E: 1000BaseT FD (Copper) 0x001A = 1000 SX, FD
0x001E = 1000 T, FD
SC Fiber Ports:
0x0012 = 100 FX, FD
7.2.3.9 Management Address TLV

The Management Address is the address associated with the local LLDP agent that may be used to reach
higher layers within the device to assist with LLDP operations. Typically, this indicates how to reach the LLDP
MIB. The Management Address TLV contains three fields: Management Address, Interface Number, and Object
Identifier (OID).
Management Address
The Management Address indicates the management address of this device. For the RX3i PROFINET Controller,
the management address is the IP Address of the device.
Subtype Meaning Address Value
4 IPv4 address IPv4 address of this device
Interface Number
The Interface Number identifies a specific interface or port at the specified management address. Thus, the
interface number varies with the network port number. The RX3i Controller uses the current network port
number.
Subtype Meaning Address Value
3 System port number Management port number (1-max network ports)
Object Identifier (OID)

The OID specifies a MIB object (typically the LLDP MIB) in ASN.1 format that is reachable at the specified
management address and interface number. A length of zero means that an OID is not provided. The OID value
is internally assigned by, and meaningful only to, the LLDP device.
GFK-2571P July 2018 149

Appendix A PROFINET IO Performance Examples
Note: The configurations and performance numbers shown here are examples; Actual performance timings
will vary depending on your exact configuration and network setup.
This section presents various PROFINET IO systems and their measured I/O performance for a simple Discrete
IO loopback in an RX3i IO-Device and in a VersaMax IO-Device. As these systems are not identical in their
configuration or setup, additional details of each system configuration are provided in the sections below.
The IO Loopback measurements were done by wiring the outputs of a discrete output module directly to the
inputs of a discrete input module, and using Ladder Logic to measure the time difference between setting the
outputs and reading the same data on the corresponding inputs. Proficy Machine Edition was attached to the
RX3i during testing. The average, minimum, and maximum loopback times were captured from a 4-hour
sample period. In addition, since the CPU sweep time is a primary factor in the accuracy and precision of the IO
Loopback times recorded, the average and maximum CPU sweep times for each system are given.
Note: CPU Sweep time variations between systems are not completely a function of varying PROFINET IO. It
was also influenced by variations in logic executed and main rack configurations.
GFK-2571P July 2018 151

Appendix A. PROFINET IO Performance Examples
A-1 Systems with RX3i PNS

A-1.1 RX3i System Performance Summary
RX3i CPU 16-pt. Discrete
Total Amount
Total # of PROFINET Sweep Time I/O Loopback
PROFINET I/0
System Configuration I/O Devices/ (ms) Time (ms)
Modules20 Discrete pts./
Average Average
Analog Chan.
(Max) (Min, Max)
1 ms PROFINET Update Rate
A.2.1 - Multi-Device w/MRP 8/33 x 12-slot racks 176/16 4.1 (6.7) 12 (7, 20)

B.1 - Multi-Device 20/59 x 12-slot racks 656/64 6.0 (7.6) 28 (11, 48)
A-1.2 RX3i System Descriptions

A.1 - Multi-Device with MRP (3i PNS)
This system contained an IC695CPU320, IC695ETM001, and an IC695PNC001 in the main rack. The PNC001
was connected in a Media Redundancy Protocol (MRP) network of eight RX3i PNS modules (IC695PNS001),
each configured for a 1 ms PROFINET update rate. Each PNS contained between one and nine discrete input,
discrete output, analog input, or analog output modules. The I/O Loopback measurement was taken using a
32-point output module (IC693MDL740) owned by one RX3i PNS that was then tied to the 32-point input
module (IC694MDL660) in the same device. The input module (IC693MDL660) was set to have a 0.5 ms input
filter time.
B.1 - Multi-Device
was connected in a network bus configuration to 20 RX3i PNS modules (IC695PNS001), each configured for a
16 ms PROFINET update rate. Each PNS contained at least two discrete input, discrete output, analog input, or
analog output modules. The I/O Loopback measurement was taken using a 32-point output module
(IC694MDL754) owned by one RX3i PNS, that was then tied to the 32-point input module (IC694MDL660)
owned by a different RX3i PNS. The input module (IC694MDL660) was set to have a 0.5 ms input filter time.
20
Number of modules includes I/O modules only; does not include head-ends or power-supplies.
A-2 Systems with VersaMax PNS

A-2.1 VersaMax System Performance Summary
RX3i CPU
Total # Total Amount 16 pt. Discrete I/O
Sweep Time
System PROFINET I/O PROFINET I/O Loopback Time (ms)
(ms)
Configuration Devices/ Discrete pts./ Average
Modules20 Average
Analog Chan. (Min, Max)
(Max)
192/0
A.1 – Single Device 1/4 3.2 (5.8) 8 (5, 13)
824/0
A.2 – Multi-Device 8/14 4.0 (6.4) 7 (4, 12)
A.2.1 – Multi-Device
8/14 824/0 4.0 (6.6) 7 (4, 12)
w/MRP
A.3 – Multi-PNC001
32/41 2808/85 7.2 (9.6) 14 (6, 17)
Multi-Device
B.1 – Multi-Device 20/29 1928/0 5.2 (8.2) 22 (5, 42)
B.1.1 – Multi-Device
20/29 1928/0 5.2 (7.7) 23 (5, 43)
w/MRP
B.2 – Max Device 64/89 5176/445 12.3 (15.4) 36 (11, 60)
GFK-2571P July 2018 153

A-2.2 VersaMax System Descriptions

A. – 1ms PROFINET Update Rate Systems
A.1 – Single Device
This system contained an IC695CPU315, IC695ETM001, and an IC695PNC001 in the main RX3i rack. The
PNC001 was connected to a single VersaMax PNS (IC200PNS001) configured for a 1 ms PROFINET update rate.
The PNS contained four mixed discrete 16 point in/out modules (IC200MDD844). Each I/O module had its
outputs tied to the inputs of an adjoining I/O module, and each input module was configured with a 1 ms Input
DC Filter time. The I/O Loopback measurement was taken using one of the IC200MDD844 modules.
A.2 – Multi-Device
This system contained an IC695CPU315, IC695ETM001, and an IC695PNC001 in the main RX3i rack. The
PNC001 was connected in a network bus configuration to eight different VersaMax PNS modules
(IC200PNS001), each configured for a 1ms PROFINET update rate. Each PNS contained at least one discrete
input or output module. The I/O Loopback measurement was taken using a 16-point output module
(IC200MDL741) owned by one VersaMax PNS, that was then tied to the 16-point input module (IC200MDL640)
owned by a different VersaMax PNS. The input module (IC200MDL640) was configured for a 0 ms Input DC
Filter time.
A.2.1 - Multi-Device with MRP
This system is identical to the A.2 – Multi-Device configuration, except that Media Redundancy Protocol (MRP)
was in use. To exercise MRP, the network was set up in a ring configuration and the PNC001 was configured as
an MRP Manager with a configured Default Test Interval of 20ms.
A.3 - Multi-PNC001 Multi-Device
This system contained an IC695CPU315, two IC695ETM001’s, an IC694MDL732, an IC694MDL645, and four
IC695PNC001 modules in the main rack. Each PNC001 module was connected in a network bus configuration
to eight VersaMax PNS modules (IC200PNC001), each configured for a 1ms PROFINET update rate. Each PNS
contained at least one discrete input, discrete output, analog input, or analog output module. The I/O Loopback
measurement was taken using a 16-point output module (IC200MDL741) owned by one VersaMax PNS, that
was then tied to the 16-point input module (IC200MDL640) owned by a different VersaMax PNS. The input
module (IC200MDL640) was configured for a 1 ms Input DC Filter time.
B. – 16ms PROFINET Update Rate Systems

B.1 – Multi-Device
module was connected in a network bus configuration to 20 VersaMax PNS modules (IC200PNS001), each
configured for a 16ms PROFINET update rate. Each PNS contained at least 1 discrete input, discrete output,
analog input, or analog output module. The I/O Loopback measurement was taken using a 16-point output
module (IC200MDL741) owned by one VersaMax PNS, that was then tied to the 16-point input module
(IC200MDL640) owned by a different VersaMax PNS. The input module (IC200MDL640) was configured for a 0
ms Input DC Filter time.
B.1.1 – Multi-Device with MRP
This system is identical to the B.1 – Multi-Device configuration, except that Media Redundancy Protocol (MRP)
was in use. To exercise MRP, the network was set up in a ring configuration and the PNC001 module was
configured as an MRP Manager with a configured Default Test Interval of 20ms.
B.2 – Sixty-four IO-Device
module was connected in a network bus configuration to 64 VersaMax PNS modules (IC200PNS001), each
configured for a 16ms PROFINET update rate. Each PNS contained at least one discrete input, discrete output,
analog input, or analog output module. The I/O Loopback measurement was taken using a 16-point output
module (IC200MDL741) owned by one VersaMax PNS, that was then tied to the 16-point input module
(IC200MDL640) owned by a different VersaMax PNS. The input module (IC200MDL640) was configured for a 1
ms Input DC Filter time.
GFK-2571P July 2018 155

A-3 Systems with RSTi-EP EPSCPE100/CPE115

A-3.1 RSTi-EP CPE100/CPE115 Embedded PROFINET Controller System
Performance Summary
4-pt.
Total Analog
RSTi-EP 8-pt.
Amount I/O
Total # of CPU Discrete I/O
PROFINET Loopbac
PROFINET I/O Sweep Loopback
System Configuration I/0 k Time
Devices/ Time (ms) Time (ms)
Discrete (ms)
Modules21 Average Average
pts./ Average
(Max) (Min, Max)
Analog Chan. (Min,
Max)
A-3.2.1 – Single Device 1/10 8/44 2.7(7.17) 25(11,41) 24(11,40)
A-3.2.2 – Single Device Max-IO 1/64 188/148 6.9 (13.8) 36 (17, 56) 33(11, 48)
A-3.2.3 – Max-Device 8/96 428/225 11.4 (18.7) 48 (20, 69) 40(18, 57)
A-3.2.4 – 4-Device with
4/70 348/173 16.8(26.7) 48(15, 77) 39(12, 61)
Ethernet Protocols
21
Number of modules includes I/O modules only; does not include head-ends or power-supplies.
A-3.2 RSTi-EP System Descriptions

A. – 16ms PROFINET Update Rate Systems
A-3.2.1 – Single Device
This system contained an RSTi-EP Standalone Controller with embedded PROFINET EPSCPE100/CPE115 and
IO Scan in Normal Sweep mode. The embedded Ethernet is connected to PME. The embedded PROFINET
Controller CPE100/CPE115 was connected to a single RSTi-EP PNS (EPXPNS001) configured for a 16 ms
PROFINET update rate. The PNS contained 10 I/O modules with combinations of discrete 4 point in/out
modules & analog 4/6 channel in/out modules. Each I/O module had its outputs tied to the inputs of an
adjoining I/O module. The total data Bytes size is 122. The I/O Loopback measurement was taken using EP-
2214 (DO4) & EP-1214 (DI4) discrete modules and EP-3124 (AI4 V/I 12BITS) & EP-4264 (AO4 V/I DIAG) analog
modules.
A-3.2.2 – Single Device Max-IO
Controller CPE100/CPE115 was connected to a single RSTi-EP PNS (EPXPNS001) configured for a 16 ms
PROFINET update rate. The PNS contained 64 I/O modules with various combinations of discrete 4/8/16 point
in/out modules & analog 4/8 channel in/out modules. Each I/O module had its outputs tied to the inputs of an
adjoining I/O module. The total data Bytes size is 713. The I/O Loopback measurement was taken using EP-
2218 (DO8) & EP-1218 (DI8 2-wire) discrete modules and EP-3124 (AI4 V/I 12BITS) & EP-4264 (AO4 V/I DIAG)
analog modules.
A-3.2.3 – Max-Device
Controller CPE100/CPE115 was connected in a network bus configuration to eight different PNS modules (4 -
EPXPNS001, 1 - RX3i CEP001, 1 - RX3i PNS001, and 2 - VersaMax PNS001), each configured for a 16ms
PROFINET update rate. All the devices contained 96 I/O modules with various combinations of discrete 4/8/16
point in/out modules & analog 4/8 channel in/out modules. Each I/O module had its outputs tied to the inputs
of an adjoining I/O module. The total data Bytes size is 1262. The I/O Loopback measurement was taken on
device EPXPNS001 using EP-2218 (DO8) & EP-1218 (DI8 2-wire) discrete modules and EP-3124 (AI4 V/I 12BITS)
& EP-4264 (AO4 V/I DIAG) analog modules.
A-3.2.4 – 4-Device with Ethernet Protocols
IO Scan in Normal Sweep mode. The embedded Ethernet LAN1 port was configured with 2 Modbus Client
channels with 200 data Bytes, 2 Modbus Server channels with 150 data Bytes, 2 SRTP Client channels with 256
data Bytes, 2 SRTP Server channels with 50 data Bytes, 2 EGD Producers with 800 data Bytes at 100ms
production rate each, 2 EGD Consumers, and connected to PME. The embedded PROFINET Controller LAN2
port was connected in a network bus configuration to four different PNS modules (EPXPNS001, RX3i CEP001,
RX3i PNS001, and VersaMax PNS001), each configured for a 16ms PROFINET update rate. All the devices
contained 70 I/O modules with various combinations of discrete 4/8/16 point in/out modules & analog 4/8
channel in/out modules. Each I/O module had its outputs tied to the inputs of an adjoining I/O module. The
total PROFINET data Bytes size is 831. The I/O Loopback measurement was taken on device EPXPNS001 using
EP-2218 (DO8) & EP-1218 (DI8 2-wire) discrete modules and EP-3124 (AI4 V/I 12BITS) & EP-4264 (AO4 V/I
DIAG) analog modules.
GFK-2571P July 2018 157

GE Automation & Controls Additional Resources
Information Centers For more information, please
Headquarters: visit our web site:
1-800-433-2682 or 1-434-978-5100 www.geautomation.com
Global regional phone numbers
are available on our web site
www.geautomation.com
Copyright © 2011-2018 General Electric GFK-2571P

Company. All Rights Reserved
*Trademark of General Electric Company.
All other brands or names are property of their
respective holders.

Pacsystems Rx3I & Rsti-Ep Profinet Io-Controller User Manual

Uploaded by

Copyright:

Available Formats

Pacsystems Rx3I & Rsti-Ep Profinet Io-Controller User Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Pacsystems Rx3I & Rsti-Ep Profinet Io-Controller User Manual

Uploaded by

Copyright:

Available Formats

GE

Automation & Controls

RX3i & RSTi-EP PROFINET IO-Controller User

RX3i & RSTi-EP

For Public Disclosure

Warnings, Cautions, and Notes as Used in this Publication GFL-002

Warning notices are used in this publication to emphasize that hazardous

Caution notices are used where equipment might be damaged if care is

* indicates a trademark of General Electric Company and/or its subsidiaries.

©Copyright 2011-2018 General Electric Company.

For Public Disclosure

Europe, Middle East, & Africa

Table of Contents ............................................................................................................................................ i

Table of Figures .............................................................................................................................................. vi

Chapter 1 Introduction ......................................................................................................................... 1

1.1 Revisions in this Manual ........................................................................................................... 2

1.2 PROFINET Controller Description ......................................................................................... 4

1.3 PNC001 Module Specifications ............................................................................................... 6

1.4 Operating Range for Surrounding Air Temperature ......................................................... 9

1.5 PNC001 Module Controls and Indicators ...........................................................................10

1.6 PROFINET Networks for PACSystems ...............................................................................14

GFK-2571P July 2018 i

Chapter 2 Installation ......................................................................................................................... 31

2.1 Pre-Installation Check ............................................................................................................ 32

2.2 Installation in Hazardous Areas .......................................................................................... 33

2.3 Removing the Backplane Knockout .................................................................................... 34

2.4 Module Installation ................................................................................................................. 35

2.5 Module Removal ...................................................................................................................... 35

2.6 Hot Insertion and Removal ................................................................................................... 36

2.7 Ethernet Port Connections ................................................................................................... 37

2.8 PNC001 LED Behavior ............................................................................................................. 43

2.9 Installing the USB Port Driver .............................................................................................. 46

2.10 Firmware Updates................................................................................................................... 47

Chapter 3 Configuration ..................................................................................................................... 49

3.1 Configuration Overview ........................................................................................................ 50

3.2 Configuration Tools ................................................................................................................ 52

3.3 Configuring an RX3i PROFINET Controller ........................................................................ 53

3.4 Configuring PROFINET System Redundancy .................................................................... 55

3.5 Exploring PROFINET Networks ............................................................................................ 56

ii PACSystems* RX3i & RSTi-EP PROFINET IO-Controller User Manual GFK-2571P

3.5.2 Configuring PROFINET Controller Parameters ............................................................................................. 58

3.6 Configuring PROFINET LANs .................................................................................................62

3.7 Adding a VersaMax PROFINET Scanner to a LAN.............................................................65

3.8 Adding a Third-Party IO-Device to a LAN ..........................................................................75

3.9 Viewing / Editing IO-Device Properties ..............................................................................79

3.10 Assigning IO-Device Names...................................................................................................81

3.11 After the Configuration is Stored to the RX3i CPU .........................................................83

Chapter 4 PROFINET System Operation .........................................................................................85

4.1 PROFINET Operation Overview ...........................................................................................86

4.2 Operations of the PROFINET Controller in the PACSystems System ........................90

4.3 I/O Scanning ..............................................................................................................................92

4.4 Data Coherency ........................................................................................................................93

4.5 Performance Factors ..............................................................................................................94

4.6 PROFINET IO Update Rate Configuration ..........................................................................95

4.7 PACSystems CPU Operations for PROFINET ....................................................................96

GFK-2571P July 2018 iii

Chapter 5 Diagnostics ....................................................................................................................... 101

5.1 Power-up and Reset (PNC001 Module) ............................................................................ 102

5.2 Special LED Blink Patterns .................................................................................................. 104