UM353-1
Function Blocks
March 2003
3-35
COIL INPUTS 16 CHAN - ETHERNET
COIL INPUTS
CIE_
16-CHAN ETHERNET
C0
Output
C0
CF
Output
CF
IP A D
d
RES
s
(H)
....
nnn.nnn.nnn.nn n
(192.168.0.0)
QS
Output
QS
Ethernet Network
START
ing
C
oi
L
(H)
.. 0000 - 65535
(null)
NO. OF C
oi
L
s
(H)
................ 1 - 16
(1)
MB A D
d
RES
s
(H)
.............. 1 - 255
(1)
P
A
R E S
S
I
D
T A R
F
Y
L
C
L
N O
O
T
A D R E S
B
M
D A T A
T
P
DATA
TYP
e
(H)
............
Coil/InPut
(Coil)
C
U
p
D
ate
RATE
(H)
.............. P2P/Ct
(P2P)
E
T
A
R
D
U
3.2.25 CIE_- Coil Inputs - Ethernet (V3.0)
CIE_ function blocks are available when the
optional Ethernet communication board
installed in the controller. It enables the controller
to obtain Coil data from other stations over the
Ethernet network.
Up to 32 CIE_ blocks are available. Blocks are
assigned in sequence, controller wide, with each
use. Up to 16 Coils can be obtained from a
Modbus device. Each Coil is assigned to block
outputs C0 – CF.
The IP ADRES parameter is used to configure the
IP address of the source Modbus device. The
MB ADRES parameter allows a Modbus address
to be configured. When connecting to other
Siemens MOORE controllers, the Modbus
address is set to 1. In some cases, other Modbus
devices may use a different address or when
going through a Modbus TCP/IP gateway a Modbus network may have multiple devices, each having a unique
address.
The START CL parameter identifies the location of the first Coil. Subsequent Coils, up to 16, can be obtained by
setting the NO OF CL parameter to a value greater than 1. The DATA TYP parameter enables reading of Coils
(Modbus Function Code 01) or Inputs (Modbus Function Code 02). Both are treated the same but the Coil type is
the most common usage. The UD RATE parameter configures the rate at which the block will request data. The
P2P setting will update the data at the rate set by the P2P RATE parameter in the ETHERNET block. The Ct
setting will update the data at the cycle time of the controller.
Output QS indicates the quality of the received data and will go high (1) when the data is bad. This is normally
associated with failure to receive data due to a communication failure or a misconfiguration of the source.
8
Requires Ethernet communications board firmware version 2.0 or later
StockCheck.com
Summary of Contents for Moore 353
Page 2: ...S t o c k C h e c k c o m ...
Page 14: ...Contents UM353 1 xii March 2003 S t o c k C h e c k c o m ...
Page 24: ...Introduction UM353 1 March 2003 1 10 S t o c k C h e c k c o m ...
Page 152: ...LonWorks Communications UM353 1 March 2003 5 4 S t o c k C h e c k c o m ...
Page 164: ...Network Communications UM353 1 6 12 March 2003 S t o c k C h e c k c o m ...
Page 246: ...Operation UM353 1 March 2003 9 8 S t o c k C h e c k c o m ...
Page 254: ...Controller and System Test UM353 1 March 2003 10 8 S t o c k C h e c k c o m ...
Page 282: ...Circuit Description UM353 1 March 2003 13 4 S t o c k C h e c k c o m ...
Page 298: ...Model Designation and Specifications UM353 1 March 2003 14 16 S t o c k C h e c k c o m ...
Page 302: ...Abbreviations And Acronyms UM353 1 15 2 March 2003 S t o c k C h e c k c o m ...
Page 304: ...Warranty UM353 1 W 2 March 2003 S t o c k C h e c k c o m ...