TAC AB, 1999-08-18
0-004-7516-1 (GB), 8:3 (10)
TAC Xenta 102 Handbook
Communication
8.4
Not accepted values
All nvo’s are limited to their accepted values, and all nvi’s detect
whether the incoming value from the network is within the
accepted limits. If the value is not accepted, the controller
activates bit 13 in the variable for alarm handling, nvoAlarm-
Status. For an nvi, the controller uses the off value, which is
also counted as an accepted value.
8.5
The node object
The variables in the node object (figure 8.1) are separated into
three categories:
•
Mandatory (M)
•
Optional (O)
•
Configuration properties (C)
The category “Mandatory” contains all compulsory variables
*
,
“Optional” contains selectable variables, and ”Configuration
properties” contains the configuration parameters.
Note! The network variables’ indeces are not the same as the
figure in “nv” in the figure.
8.5.1 The node object’s inputs (nvi)
Index Variable
Hb*
1
SNVT
Accepted values
Default
Description
(Service type)
value
(self doc. string)
48
nviRequest
No
SNVT_obj_request 0=RQ_NORMAL
RQ_NUL
Object request
2=RQ_UPDATE_STATUS (Confirmed) @0|1
5=RQ_REPORT_MASK
50
nviFileReq
No
SNVT_file_req
see “SNVT Master List”
FR_NUL
File request
(Confirmed) @0|5
nv1
nv2
nv6
nviRequest
SNVT_obj_request
nvoStatus
SNVT_obj_status
nvoFileStat
SNVT_file_status
nciInstallType
SNVT_config_src
Configuration Properties
Mandatory
Network
Variables
Optional
Network
Variables
0 - Node Object
Object Type: 0
nv5
nviFileReq
SNVT_file_req
Figure 8.1 The node object
According to LonMark
standardised function
profile for VAV
controllers.
*
*
1
Hb=Heartbeat