Function Blocks
UM353-1
March
2003
3-44
3.2.36 DIS_ - Digital Input _ State
DIS_ function blocks, in firmware 1.30 and higher, convert a 16-
bit word received from a single node on the LonWorks network
into 16 block outputs for interconnection to other function blocks
within the controller. A maximum of 6 DIS 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. DIS02). Input connections are
established by ‘binding’ the output variable of type SNVT_state
(SNVT #83) in the remote node to the network variable in the DIS
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 viewing the number that the
station has assigned to input 0.
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.
The function block also has a quality status output associated with
it. This status will go high (1) when the block determines it has lost communication with the Lon node.
BLOCK DIAGRAM
QS
Quality Test
LON node r1
nv x1 SNVT_
LON
LON network
option board
Station
node u
nv x1 binding
node u, nv *0
O0
.
nv _
SNVT_
F
0
N
F
OF
.
F
F
N
F
DIGITAL INPUT _ STATE
O0
O
utput 0
DIGITAL INPUT
DISnn
QS
Q
uality
S
tatus
STATE
LONWorks
Network
nv*
SNVT _ state
nviDSnn0
N
N U M
V
view
N
etwork
V
ariable
NUM
ber (nv *) .... 1 to 2000 (*)
0
O1
O
utput 1
O2
O
utput 2
O3
O
utput 3
O4
O
utput 4
O5
O
utput 5
O6
O
utput 6
O7
O
utput 7
O8
O
utput 8
O9
O
utput 9
OA
O
utput A
OB
O
utput B
OC
O
utput C
O
utput D
OE
O
utput E
OF
O
utput F
OD
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 ...