1 - Product Overview. Rockwell Automation Guardmaster 440R-ENETR
Advertisement
Advertisement
Chapter
1
Product Overview
About the Interface
The Guardmaster EtherNet/IP network interface is catalog number
440R-ENETR (referred to as ‘ENETR interface’ throughout this manual). The
ENETR interface provides connectivity to EtherNet/IP networks from the
Guardmaster safety relays (GSR).
This user manual describes the Series B version of the ENETR interface, which was released in mid-year 2018.
Two significant differences between the Series A and B interface include:
• Webpage was discontinued to meet Internet security requirements.
• A faster optical bus was added to accommodate the DG relay and
GuardLink® designs.
The ENETR interface communicates to the GSR safety relays over two optical buses that are on the side of the housing. EtherNet/IP connectivity is provided through two RJ45 connectors for 2-port pass-through support of daisy chain or ring, and the existing star and tree network topologies.
shows the key features of the ENETR interface and the locations of the two optical buses. Opto bus 3 communicates with the DG safety relay. Opto bus 2 communicates with the DI, DIS, EM, EMD, GLP, GLT, and SI safety relays.
Power Up a System
Each time the interface is powered up, the adapter compares the number of I/O modules present on its backplane to the chassis size value from nonvolatile memory. The adapter does not allow I/O connections until the number of I/O modules present equals the chassis size value minus one for the adapter itself.
On powerup, the interface assigns an address to every Guardmaster safety relay
(up to six) in the backplane. The addressing starts from left to right with the
Guardmaster safety relay to the immediate right of the interface taking the first address of 1.
Rockwell Automation Publication 440R-UM009C-EN-P - July 2019 7
Chapter 1 Product Overview
RIUP Situations
You must observe the following rules for Guardmaster safety relay system construction and the removal and reinsertion of safety relays.
• Actual Guardmaster safety relay identification (such as, electronic keying) is done when connection establishment requests are received from the controller or controllers. The interface does not allow any I/O connections until the number and type of Guardmaster safety relays match the configuration in the connection request.
• A Guardmaster safety relay that is removed under power disrupts communication of the other Guardmaster safety relays in the system.
Connections to all safety relays are disallowed until power to the entire system, including the interface, is cycled to initiate readdressing the system.
• If safety relays of different types are removed and returned to the wrong locations, attempts to connect to these safety relays fails during verification of the electronic ID (providing that keying has not been disabled).
• If safety relays of the same type are removed and returned to the wrong locations, they accept connections from the controller or controllers once they pass their electronic keying check.
What the Interface Does
The interface performs the following primary tasks:
• Real-time input data (also known as implicit messaging) - the interface serves as a bridge between Guardmaster safety relays and the network
L
7
X
E
N
B
T
EtherNet/IP Network
E
T
E
N
R
Guardmaster
Safety
Relays
E
N
B
T
ControlLogix
I/O
Other
Network
Devices
• Support of messaging data for programming information (also known as
Explicit Messaging)
8 Rockwell Automation Publication 440R-UM009C-EN-P - July 2019
Interface Features
Product Overview Chapter 1
Features of the interface include:
• Use of EtherNet/IP messages encapsulated within standard TCP/UDP/
IP protocol
• Common application layer with ControlNet and DeviceNet networks
• Interfacing via Category 5 rated twisted-pair cable
• Half/full duplex 10 Mbit or 100 Mbit operation
• DIN Rail mounting for 440R-ENETR interface
• Communication from Guardmaster safety relays on the same DIN rail
(mounted immediately to the right of the interface) as the ENETR interface to controllers on the EtherNet/IP network
IMPORTANT Each safety relay must be mounted to the right of the interface within
5 mm [0.2 in.] of the next safety relay.
• Communication supported by RSLinx software
• IP address that is assigned via standard BOOTP or DHCP tools
• Configuration via RSLogix 5000 software
• No network scheduling required
• No routing tables required
• Support of connections from multiple controllers simultaneously
You must use RSLogix 5000 software to configure these features. For more details on configuration, see
Figure 1 - Key Features of the 440R-ENETR Interface
4
5
2
3
1
6
7
8
2
3
Item Description
1 35 mm (1.38 in.) DIN rail mounting
4
Optical communications bus (OLink) 2.0
Optical communications bus (OLink) 3.0
Removable terminal block
6
7
Item Description
5 Status Indicators
8
EtherNet/IP address rotary switches
Two Ethernet network RJ45 connectors
22.5 mm (0.89 in.) wide housing
Rockwell Automation Publication 440R-UM009C-EN-P - July 2019 9
Chapter 1 Product Overview
Hardware/Software
Compatibility
The interface and the applications that are described in this manual are compatible with the following firmware revisions and software releases.
Contact your Rockwell Automation sales office or Allen-Bradley distributor if you need software or firmware updates to use this equipment.
Product Firmware Revision/ Software Release
440R-ENETR interface
1756-ENBT
Logix controller
RSLogix 5000 software
RSLinx software
GSR DI (Catalog number 440R-D22R2)
GSR DIS (Catalog number 440R-D22S2)
GSR EM (Catalog number 440R-EM4R3)
GSR EMD (Catalog number 440R-EM4R2D)
GSR GLP (Catalog number 440R-GL2S1P)
GSR GLT (Catalog number 440R-GL2S2T)
1.xx or later
2.3 or later
19 or later
19 or later
2.52 or later
2 or later
2 or later
2 or later
2 or later
2 or later
2 or later
Use of the Common
Industrial Protocol (CIP)
The adapter uses the Common Industrial Protocol (CIP). CIP is the application layer protocol that is specified for EtherNet/IP, the Ethernet Industrial Protocol, and for ControlNet and DeviceNet networks. It is a message-based protocol that implements a relative path to send a message from the producing device in a system to the consuming devices.
The producing device contains the path information that steers the message along the proper route to reach its consumers. Since the producing device holds this information, other devices along the path simply pass this information; they do not store it.
This configuration has the following significant benefits:
• You do not need to configure routing tables in the bridging modules, which greatly simplify maintenance and module replacement.
• You maintain full control over the route that each message takes, which enables you to select alternative paths for the same end device.
10 Rockwell Automation Publication 440R-UM009C-EN-P - July 2019
Product Overview Chapter 1
Understand the Producer/
Consumer Model
The CIP producer and consumer networking model replaces the old source and destination (master and slave) model. The producer and consumer model reduces network traffic and increases speed of transmission. In traditional I/O systems, controllers poll input modules to obtain their input status. In the CIP system, a controller does not poll input modules. Instead, they produce (multicast or unicast) their data either upon a change of state (COS) or periodically.
Multicast is the default mode for version 17 Logix and earlier controllers and unicast is the default for version 18 with multicast as a selectable option.
The frequency of update depends upon the options that are chosen during configuration and where on the network the input module resides. The input module, therefore, is a producer of input data, and the controller is a consumer of the data.
The controller also produces data for other controllers to consume. The produced and consumed data is accessible by multiple controllers and other devices over the EtherNet/IP network. This data exchange conforms to the producer and consumer model.
Specify the
Support of Data
Connections
Requested
Packet Interval (RPI)
The Requested Packet Interval or RPI is the update rate that is specified for a particular piece of data on the network. The RPI can be specified for the interface and includes all Guardmaster safety relays in the system.
When you add an interface to the I/O configuration of a controller, you must enter the RPI as a parameter. This value specifies how often to produce the data for that device. For example, if you specify an RPI of 50 ms, it means that every
50 ms the device should send its data to the controller and the controller should send the consumed (output) data to the device.
Use RPIs only for devices that exchange data. For example, a ControlLogix®
EtherNet/IP bridge in the same chassis as the controller does not require an RPI, because it is not a data-producing member of the system. Its use is only as a bridge to remote racks.
TheGuardmaster EtherNet/IP Network Interface supports data connections.
A data connection to the interface is a grouping of data from one or more
Guardmaster safety relays into one block of data that is sent over one connection at the same data rate.
See the EtherNet/IP Design Considerations Reference Manual, publication ENET-RM002 for more information on connections.
Rockwell Automation Publication 440R-UM009C-EN-P - July 2019 11
Chapter 1 Product Overview
Notes:
12 Rockwell Automation Publication 440R-UM009C-EN-P - July 2019

Public link updated
The public link to your chat has been updated.
Advertisement