Watlow RUIGTW
Watlow RUIGTW
Watlow RUIGTW
2.2.4 Once connected, navigate to the Communications Menu and then to the
Communications 2 parameter. Once there enter the required network IP and
Subnet address while also enabling EtherNet/IP (green highlight).
2.2.5 In order for the RUI/GTW to work in concert with the PLC it is important that
the assembly sizes match in both configurations. Navigate to the “Local Remote
Gateway” and expand the folder structure by clicking on the plus symbol.
Note: The input assembly within the PLC will always be set to n+1 where n = the
size of the combined (all EZ-ZONE devices) input assemblies (see step
2.3.4).
2.2.6 Click on the local remote gateway (gateway instance) that will pass data through
the RUI/GTW to the Master device and configure as shown below. The gateway
instance is an EZ-ZONE device with an address that ranges from 1 to 16.
2.2.7 If explicit messaging will be used alone, the minimum assembly size requirement
(from the PLC perspective) is 1 input and 1 output. Again, the assembly size
must be the same in the PLC and the RUI/GTW. In the previous step, the graphic
shows the assemblies set to twenty. This was done now for implicit communica-
tion examples that will follow later in this document.
2.3 PLC Configuration, Step-by-Step
2.3.1 Open RSLogix5000 software and add an additional I/O module. Follow the steps
below to accomplish this task.
2.3.2 Navigate to the I/O Configuration folder structure. If not already expanded, do so
now by clicking the plus sign next to it.
2.3.3 Right click the Ethernet port to add a new module. To narrow the search select
the “Communications” category for available modules, select a “Generic Ethernet
Module” and then click OK.
2.3.4 Define the RUI/GTW properties. Fields that must be completed include:
Name: Given name becomes controller tags to be used in program.
Comm Format: Defines how data is to be treated within PLC.
Note: All EZ-ZONE assembly members are 32-bits in
length. If the Comm Format is set to something
other than DINT, ensure the size changes in a
corresponding fashion. As an example, if 20 (32-bit)
members are in use, the appropriate Comm Formats
would be:
DINT (32-bit): *Inputs = 21, Outputs = 20
INT (16-bit): *Inputs = 42, Outputs = 40
SINT (8-bit): *Inputs = 84, Outputs = 80
* The input assemblies within EZ-ZONE modules have a
dedicated Status member that is always present. The
PLC input assembly size will always be n+1 where n =
the size of the combined (all modules) input assembly.
IP Address: Network RUI/GTW module Ethernet address.
Assembly Instance
Input (101): Defines number of members to be included in the Input
Implicit Assembly (as seen in EZ-ZONE Configurator
software “CIP Implicit Assembly Output Member
Quantity” from EZ-ZONE devices).
Output (100): Defines number of members to be included in the Output
Implicit Assembly (as seen in EZ-ZONE Configurator
software “CIP Implicit Assembly Input Member Quantity
from master devices).
Configuration(128): Enter zero.
- Destination Element
The tag shown above (PM_Ain) must be created by the user and represents
the location in which the analog input value will be found when the message
instruction is executed.
2.4.3 When all fields in the graphic above are filled in, click the Communications tab to
identify the path to the PM1. Click the Browse button and select the
ENet_RUIGTW that was configured in step 2.3.4. Lastly, click the OK button to
finish the message instruction configuration.
2.4.4 Looking at the graphic in step 2.4.1 when the contact identified as “Read_Ain1”
comes on, the message instruction will be executed and the analog input will be
read from the PM1 and then stored in the PLC tag called “PM_Ain”.
Note: If there is more than one PM control on the Standard Bus network (as
shown in the graphic below) and there is a desire to read analog input 1
explicitly from each, the CIP Instance Offset prompt must be used. CIP
instance offset is used exclusively with explicit messages; it’s unique to
each gateway instance (EZ-ZONE device), never overlapping, and defines
the control on the network as well as the parameter instance within the
control. Using the CIP instance offset (entered in decimal format) allows
for a message originating from the Master (Originator) to make its way to
the appropriate Slave (Target).
Note: If it is desired to use all 20 members of the assemblies for each control the
CIP offset must be set to at least what is shown above (or larger).
2.4.5 To read analog input 1 from the PM control at zone address 3 add the CIP Offset
(in this case 40) to the desired instance. The PLC message instruction
configuration would change as shown in the graphic below.
Note: All numbers in the graphic above that are preceded by 0x are in
hexadecimal format; numbers without the prefix of 0x are in decimal
format.
To change the 3rd Assembly Member at zone address 3 from what is shown above
to Control Mode loop 2, first find the appropriate CIP address in the PM User’s
Guide (shown below).
The Source Element was created as a 3 dimensional array using the SINT data
type because the Class, Instance and Attribute objects are 8-bits in length.
Notice in the graphic above and below that the instance for the 3rd assembly
location as well as the parameter to be written have the listed offset (40) added to
each.
3.1.1 In step 2.2.6 above, the Implicit Assembly (input and output) was configured for
20 members. With the RUI/GTW configuration complete, it is time to look closer
at the PLC side.
3.1.2 In step 2.3.2 above, the PLC was configured to include a Generic Ethernet
module. The module parameters, specifically, the assembly sizes were configured
at this time to be the same as the RUI/GTW.
3.1.3 Prior to making any changes to the current PLC configuration let’s look closer at
what is currently there. Recall that when a generic Ethernet module was added
to the PLC I/O structure (step 2.3.4) it was also given a name (ENet_RUIGTW)
and that name became a controller tag. While being connected to the PLC on-line
and with the PLC in the run mode the input tag (ENet_RUIGTW:I) clearly shows
that it is dynamically receiving raw data from the Slave (see the screenshot
below).
3.2.2 Once created, a controller tag should be created using the User Defined Data
Type as its data type. Below, a controller tag was created by the name of
PM8_t_to_O where the data type (green highlight) is the User Defined Data Type
created in the previous step.
The example above was based on the default PM T to O assembly. This assembly
configuration will typically be uniquely modified by each user.
3.2.3 Enter the rung of logic shown below to read the Target data into the PLC tag
created above.
Notice that the source of the copy instruction has the same name as the name
given to the RUI/GTW back in step 2.3.4. Recall that when the module was added
that there were entries for the input, output and configuration assemblies. The
input assembly was defined as having 21 members as was the destination tag.
Therefore, the length is defined as 21. Once the contact (Read_Input_Assembly)
is enabled the source data will be copied to the destination as can be seen below.
Now that the data formats correspond to each parameter (assembly member)
data type we see values that are more in alignment with expectations. This
illustrates why a user would want to ensure that the incoming data type
corresponds with the user defined data type in the PLC.
Again, looking at the graphic above, notice the first member referred to as
“Device Status”. This member is sourced from the RUI/GTW Ethernet card.
Regardless of how many PM controls are connected to the RUI/GTW there is only
one assembly member referred to as the Device Status. Counting the bits from
right to left, bit 12 is shown as being set to a “1”. This bit represents the
RUI/GTW being present in the PLC I/O structure and corresponds directly to the
RUI/GTW Standard Bus Address. Valid Standard Bus addresses for an RUI
range from 1- 8. If an Ethernet card is installed (RUI/GTW) valid addresses
range from 1- 4. As can be seen in the table below when the RUI/GTW is set to
Standard Bus address 1, bit 12 of the device status word will be set. When the
address is set to 2, bit 13 of the device status word would be set, etc…(see table
below).
Bits 16 through 31 of the device status word represent gateway instances (EZ-
ZONE controls on Standard Bus). Once the gateway instance is enabled, as long
as there is successful communications to the RUI/GTW the corresponding bit/s
will be set to a one. Above, bits 16 - 19 (PM Standard Bus addresses 1 - 4) are set
to a “1” because each of those four controls were enabled and they are
communicating successfully with the RUI/GTW.
Note: The other bits (20 through 31) being “0” could represent a module problem
or may simply mean that those instances have not been enabled.
3.2.4 To write data out to the Target, perform the same steps in the creation of the O
to T assembly; as can be seen below (partial assembly shown), the User Defined
Data Type is created based on the PM default. Keep in mind that this assembly
represents the output from the PLC or Originator which will be sent to the
Target or EZ-ZONE controller. The program within the PLC would write values
to these tags and they would then be sent out to the Target at the rate of the
setting for the RPI (see step 2.3.6).
3.2.6 Enter the rung of logic shown below to write data from the Originator to the
Target.
Notice that the source of the copy instruction is now the controller tag created
above where the destination is the same name given to the RUI/GTW back in
step 2.3.4. In this case, the output assembly was defined as having 20 members
as was the destination tag, therefore, the length is defined as 20. Once the
contact (Write_Output_Assembly) is enabled the source data will be sent to the
destination as can be seen below.