TAC AB, 1999-08-18
0-004-7516-1 (GB), 8:1 (10)
TAC Xenta 102 Handbook
Communication
8
Communication
8.1
General
The controller consists of two LonMark objects: the node object
(section 8.5) and the controller object (section 8.6). These objects
are monitored by means of the network variables nviRequest and
nvoStatus.
The network variable nciLocation is used when configuring the
basic parameters (section 4.1) to give a detailed description of
the actual place where the controller is fitted. The variable
receives an arbitrary string of signs and dividers as long as the
string is no longer than 30 signs. You can program a certain
location label, e.g.
TAMF.main.floor3.room343/RC40
A LNS based network management tool uses nciLocation when
a data base should be recreated. The monitoring of an already
installed network is made by the LNS tool reading nciLocation,
and then using the information to give the node a sub-system
name and a unit name. The string should therefore consist of a
name and a search path for the sub-system, followed by a slash
and the unit name, i.e.
system.sub-system[.sub-system...]/unit name
8.2
Default settings and power on
For all network variables the following default settings are
valid:
•
Number of sent messages per time unit: NONE
•
Service type: NOT CONFIRMED if not stated otherwise
•
Access check: NO, possible to configure: YES.
•
Polled: NO for all nvo and nci, YES for all nvi
(commissioning)
•
Synchronized: NO
•
Change/update only when the controller is not enabled on
the network; flags = NO
•
Restart of TAC Xenta 102 after a change; flags = YES
