Allen-bradley controllers via ethernet/ip i/o, E using allen-bradley, Controllers via ethernet/ip i/o – Delta RMC151 User Manual
Page 573: Using allen-bradley controllers via ethernet/ip
6 Communication
Reading DWORDs from the RMC
All items in the RMC have F-file addresses. Allen-Bradley defines F file data as 32-floating
point values. All the RMC registers have F-file addresses, even if they are DWORDs or
DINTs. For example, the Status Bits and Error Bits in the RMC are DWORDS. To read
these values, read them using their F addresses as given in the RMC. Then, in the PLC,
use the COP instruction (RSLogix5000), or CPW instruction (RSlogix500) to copy the data
to a register or tag of the correct data type, for example, an N register, L register, or
DINT tag. The COP instruction preserves all the bits correctly, and the resulting values
will be correct.
If the PLC must write a DINT or DWORD in the RMC, use a similar method.
6.11.2. Using Allen-Bradley Controllers via
EtherNet/IP I/O
Several Allen-Bradley controllers support EtherNet/IP I/O communication. This topic describes
how to configure and use the Allen-Bradley ControlLogix and CompactLogix PLCs to
communicate with the RMC via EtherNet/IP I/O. If you are looking for details on using the
MSG block command, see the Using Allen-Bradley Controllers via Message Block topic.
The download section of Delta's website contains RSLogix programs that are already set up to
communicate with an RMC via EtherNet/IP I/O. These programs can be used as a starting
point for your application.
Determine I/O Data Locations in the RMC
EtherNet/IP I/O transfers data back and forth between the RMC and PLC at the Requested
Packet Interval (RPI). The user must specify which data items in the RMC should be sent
and received. Typically, this is data in the Indirect Data Map.
Set up the Indirect Data map so that one part contains all the data coming from the PLC
(Incoming Data), and another part contains all the data going to the PLC (Outgoing
Data). Make sure the Incoming and Outgoing Data areas in the Indirect Data Map do not
overlap.
The Outgoing Data typically includes RMC status items that the PLC always needs to keep
track of, such as actual positions and status bits.
The Incoming Data consists of items that the PLC needs to write to in the RMC. This is
typically variables and possibly command registers.
Note:
The Incoming and Outgoing Data locations need not be the Indirect Data Map. However, the
Indirect Data Map is usually the best choice. Other options are the Variable Table and the
command area.
Setting Up the RMC for EtherNet/IP I/O
Do the following in the RMC:
1. Set the RMC's IP Address
Set up the RMC's IP Address as for any Ethernet connection. See Setting Up the RMC
Ethernet for details.
2. Set Up the Indirect Data Map
Beginning at item 0 in the Indirect Data Map, choose the items for the Outgoing Cyclic
I/O Data.
At some location in the Indirect Data Map after the Outgoing Cyclic I/O Data area,
choose the items for the Incoming Cyclic I/O Data, that is, the items that will be sent
to the RMC from the PLC. If you are using another location for your Incoming Data,
deltamotion.com
553