GE PACSystems RX3i - 1.3 PNC001 Module Specifications

Chapter 3. Communication Requirements
10 PACSystems PROFINET IO Devices Secure Deployment Guide GFK-2904D
3.3 PROFINET
This section describes the communication paths needed to support common operations on a PROFINET
network.
Installing an I/O Device
Commissioning, adding, or replacing an I/O device requires that the device be assigned a unique name to use
on the PROFINET network. Doing this requires supporting the following communication path.
Protocol
Proficy Machine Edition
I/O Device
PROFINET DCP
Client
Server
Supporting this path will allow Proficy Machine Edition to directly discover all of the PROFINET I/O devices that
are connected to the same subnet as the computer. (Note that this protocol is not routable.) Proficy Machine
Edition implements the Client functionality directly from the computer network adapter, so I/O devices must
be local to the computer’s network adapter. It can then be used to (re-)assign a unique name to the I/O device
being installed.
Note: This protocol can also be used to make other modifications to the I/O device, such as
assigning a new IP address or resetting it to factory defaults. However, those functions
are not generally required when Installing an I/O device.
Network Discovery and Device Identification
Proficy Machine Edition can also request information about the devices on a PROFINET network from a
PACSystems Controller, and then retrieve additional identification information about each device. This request
is sent to the PACSystems Controller using the Service Request protocol (described elsewhere) embedded
within the SRTP or SNP protocols. The PACSystems Controller satisfies those requests using the following
communication paths.
Protocol
Local I/O Controller
Remote I/O Controllers and I/O Devices
DCE/RPC
Client
Server
PROFINET DCP
Client
Server
Note: No mechanism is provided through this communication path for assigning a name to a
new I/O device.