UM353-1
Function Blocks
March 2003
3-39
3.2.31 DID_ - Digital Input lev_Discrete
DID_ function blocks convert 16 on/off signals received from
a single or multiple nodes on the LonWorks network into 16
block outputs for use by other function blocks within the
controller. A maximum of 6 DID blocks can be used, up to the
limit of nodes allowed on the Lon network or the memory
limit of the controller. Each use of the block will be assigned a
unique station wide ID (e.g. DID02). Input connections are
established by ‘binding’ each output variable of type
SNVT_lev_disc (SNVT #22) in the remote node devices to
each network variable in the DID function block. These
blocks will be available when the LonWorks option board is
installed in a 352P, 353, or 354N controller.
The 0 NV NUM parameter enables the number that the station
has assigned to input 0. All subsequent network variables are
assigned consecutively.
Each function block output has a mode associated with it. The
mode can be either NORMAL or FORCED. When using a
PC capable of sending LIL or Modbus commands, the mode
can be changed and the forced state can be assigned a high (1)
or low (0) value. The values accessible over the network are
the two switch inputs (N and F) and the position of the SPDT
switch illustrated in the block diagram. A mode of ‘0’ is
Normal and ‘1’ is Forced.
Each function block output also has a quality status associated
with it. This status will go high (1) when the block
determines it has lost communication with the Lon node. If
any of the individual quality outputs are high the Quality
Status block output will also be high.
DIGITAL INPUT LEV_DISCRETE
O0
O
utput 0
DIGITAL INPUT
DID_
QS
Q
uality
S
tatus
(16 channel)
LEV_DISCRETE
LonWorks
Remote I/O Bus
nv*
SNVT _ lev_disc
nviDIDnn_0
N
N U M
V
0
N
etwork
V
ariable
NUM
ber (nv *) (R) ....... 1 to 2000 (*)
nv*
nviDIDnn_1
nv*
nviDIDnn_2
nv*
nviDIDnn_3
nv*
nviDIDnn_4
nv*
nviDIDnn_5
nv*
nviDIDnn_6
nv*
nviDIDnn_7
Q0
Q
uality 0
0
1
2
3
4
5
6
7
0
SNVT _ lev_disc
SNVT _ lev_disc
SNVT _ lev_disc
SNVT _ lev_disc
SNVT _ lev_disc
SNVT _ lev_disc
SNVT _ lev_disc
(Channel 0)
(Channel F)
OF
O
utput F
QF
Q
uality F
nv*
SNVT _ lev_disc
nviDIDnn_8
nv*
nviDIDnn_9
nv*
nviDIDnn_A
nv*
nviDIDnn_B
nv*
nviDIDnn_C
nv*
nviDIDnn_D
nv*
nvDIDnn_E
nv*
nviDIDnn_F
8
9
A
B
C
D
E
F
SNVT _ lev_disc
SNVT _ lev_disc
SNVT _ lev_disc
SNVT _ lev_disc
SNVT _ lev_disc
SNVT _ lev_disc
SNVT _ lev_disc
BLOCK DIAGRAM
QS
Quality Test
node r1
nv x1 SNVT_
LonWorks
option board
node u
Remote
I/O Bus
Station
nv x1 binding
node u, nv *0
O0
nv *0 SNVT_
nv x2 SNVT_
nv x2 binding
node u, nv *1
Channel 0
F
0
N
F
Q0
SNVT_
Channel F
QF
node r2
nv x1 SNVT_
nv x1 binding
node u, nv *E
nv x2 SNVT_
nv x2 binding
node u, nv *F
nv *0
N
F
F
F
LonWorks Remote Devices
X03133S0
OF
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 ...