Watlow EZ-ZONE RUI/Gateway - Manual (Page 36)

Watlow EZ-ZONE ® RUI/Gateway • 33 • Chapter 5 Networking with a Gateway
using CIP can be accomplished via explicit and or im-
plicit communications. Explicit communications usu-
ally requires the use of a message instruction within
the Programmable Logic Controller (PLC) but there
are other ways to do this as well. Implicit communica-
tions is also commonly referred to as polled communi-
cations. When using implicit communications there is
an I/O assembly that would be read or written to; the
default assemblies are embedded into the firmware
of the controller and are different for each. Watlow
refers to these assemblies as the T to O (Target to
Originator) and the O to T (Originator to Target) as-
semblies where the Target is always the EZ-ZONE
controller and the Originator is the PLC or Master
on the network. The O to T assembly is made up of
20 (32 bit) members that are user configurable where
the T to O assembly consists of 21 (32 bit) members.
The first member of the T to O assembly is called the
Device Status, it is unique to the RUI/GTW and can-
not be changed. Bits 16 - 31 of this 32 bit word rep-
resents the communications status of the EZ-ZONE
controllers on the Standard Bus side of the RUI/GTW
when enabled. Once a Zone is enabled, valid commu-
nications will be represented with the bit set to a "1",
if set to "0", the RUI/GTW is not communicating with
the zone. Bit 16 represents Zone 1 where bit 31 rep-
resents Zone 16. The 20 members that follow Device
Status are user configurable. The Appendix of this
user manual contains the assemblies for each of the
EZ-ZONE controllers. ( See Appendix: CIP Implicit As-
semblies by product).
To change any given member of either assembly
simply write the new class, instance and attribute to
the member location of choice. As an example, if it
were desired to change the 14 th member of the O to
T assembly of an EZ-ZONE PM Integrated controller
(PM1) from the default parameter (Heat Proportional
Band) to Limit Clear Request (see Operations Page,
Limit Menu) write the value of 0x70, 0x01 and 0x01
(Class, Instance and Attribute respectively ) to 0x77,
0x01 and 0x0E. Once executed, writing a value of zero
to this member will reset a limit assuming the condi-
tion that caused it is no longer present.
Note:
When changing the implicit assembly of any given
controller through the RUI/GTW ensure that the
CIP Instance Offset is added to the documented
instance for any given parameter as well as the as-
sembly instance. As an example, if it were desired
to do the above operation on PM3 the value to write
would now be 0x70, 0x 09 and 0x01 (Class, Instance
and Attribute respectively ) to 0x77, 0x 09 and 0x0E.
Notice that the CIP Offset was added to each.
Using DeviceNet™
Communications To/From Third Party Device:
When using the DeviceNet protocol, there are two
methods used in communicating, implicitly and ex-
plicitly. Once the gateway instance is enabled there
are two prompts that relate directly to these forms of
communication.
Use the graphic below in reference to the descrip-
tions that follow.
[`ost]
CIP Offset, used exclusively with explicit
messaging where it defines a specific gateway
instance (EZ_ZONE PM or RM controller) to
receive a message originating from the net-
work Master. The CIP offset is unique to each
gateway instance and is added to the pub-
lished instance of any given parameter.
As an example, when programming the explicit mes-
sage ensure that the class, instance and attribute are
defined. To read the first instance of the Process Vari-
able in PM2 (see graphic on next page) use the follow-
TM
RUI/Gateway Setup Prompts
[gtW] 1 = PM1
[gtW] 4 = PM4
TM
Gateway
Watlow Standard Bus
(Daisy chain EIA-485)
EZ-ZONE ® Controllers
1 - 16 maximum
CIP Offset
13-16
CIP Offset
9-12
CIP Offset
5-8
CIP Offset
1-4
[oSt] = 0 - 255
(CIP Offset)
DeviceNet TM
[Ao;nb] = 0 - 20
CIP Output Assembly Size
[Ai;nb] = 0 - 20
CIP Input Assembly Size
[gtW] = 1 – 16
(Gateway Instance)
[Du;En] = Yes or No
(Enable gateway instance)
[Du;st] = [On] or [off]
(Device Status)
[Com] Instance 1
Standard Bus Address
[Ad;S] = 1-8
Start Node to Scan
[St;2n] = 1-24
End Zone to Scan
[nU;2n] = 1-24
DeviceNet TM Node Address
[ad;d] = [0-63]
[Com] Instance 2
Network Baud Rate
[baud] = [125], [250], or
[500] Kb
DeviceNet TM Quick Connect
[FC;e] = [yes] or [no]
Units
[`C_f] = [``f] or [``C]