Program id, Remote client, Remote device – Echelon IzoT BACnet Developes User Manual
Page 29: Remote network interface (rni), Resource file, Selfinstalled network
Priority Array
BACnet Outputs are never directly written to (*). A write is achieved by writing to the Present Value
with a priority of 1 to 16. (With priority 1 being the highest). If the write happens to be the highest
priority in the array of writes, then this value is transferred to the Present Value. If it is not the highest
priority write, then the present value remains set whatever value is at the highest priority in the array.
(*) subject to Out-Of-Service below
Program ID
A unique, 16-hex digit ID that uniquely identifies the device application.
Relinquish Default
To ‘cancel’ a write operation at a given priority, a NUL value is written to the Present Value at the
appropriate priority. This has the effect of “relinquishing” (canceling) the value in the Priority Array.
Lower priority values at this point may be transferred to the Present Value. If no suitable values remain
in the Priority Array, then the Relinquish Default value is transferred. In the FT 6050 BACnet Stack
implementation, this Relinquish Default is any external Lon input to the Network Variable. See the
BACnet White Paper for more details on this.
Remote Client
An LNS application that communicates with the LNS Server (running on a separate computer) over a
LonWorks channel (an IP-852 or TP/XF-1250 channel) or over an LNS/IP interface. The NodeBuilder
tool cannot be run on a remote client, but the LonMaker tool and other LNS client software can.
Remote Device
A device that sends SNVT_lux and/or SNVT_temp_p output network variables updates to an Echelon
Series 6000 EVB running the NcMultiSensorExample application (the local device). The temperature
and light level values are displayed in the Remote Info Mode panel on the LCD of the local device. A
remote device may be another Echelon Series 6000 EVB running the NcMultiSensorExample
application.
Remote Network Interface (RNI)
A network interface that enables you to connect an LNS or OpenLDV-based application to a
L
ON
W
ORKS
network via a TCP/IP connection. RNIs include the i.LON SmartServer, i.LON 100 e3
plus Internet Server, and i.LON 600 L
ON
W
ORKS
-IP Server.
Resource File
A file included with a L
ON
W
ORKS
device that defines the components of the device interface to be
used by integration and development tools. Defined components include network variable types,
configuration property types, and functional profiles implemented by the device application. Resource
files hold definitions of standard and user-defined resources, including network variable and
configuration property types, functional profiles, enumerations, and formatting rules to display
network variable and configuration properties in a readable form. Resource files are used during
device development, installation and management. Standard resource files are distributed by
L
ON
M
ARK
International. User-defined resource files are created and managed during device
development.
Self-Installed Network
A network that has network addresses and connections created without the use of a network
management tool. In a self-installed network, each device contains code (the Neuron C ISI library,
which implements the ISI protocol) that replaces parts of the network management server’s
functionality, resulting in a network that no longer requires a special tool or server to establish network
communication or to change the configuration of the network.
Using BACnet and LONWORKS with the FT 6000 EVK
29