Echelon NodeBuilder FX - Manual (Page 284)

270 Appendix C: Glossary
IP-852 Network Interface
Formally called VNI, an IP-852 network interface enables IP-852 devices such as LNS Server
computers, LonMaker computers, and i.LON IP-852 routers to be attached to IP-852 channels. An
IP-852 network interface requires that the L
ON W ORKS -IP Configuration Server be configured before
trying to communicate with remote devices or remote computers.
Implementation-specific NVs/CPs
Network variables and configuration properties that are not defined in the functional profiles used by
their parent functional blocks. Implementation-specific network variables and configuration properties
(those implemented as configuration network variables [CPNVs]) appear in Virtual functional blocks
instead of their parent functional blocks when you are using the LonMaker tool or other network tool.
Note: If you use implementation-specific network variables in your device interface, your device will
not comply with interoperability guidelines version 3.4 (or better) and therefore cannot be certified by
L
ON M ARK . A better alternative for adding members to a functional profile is to create a user-defined
functional profile template (UFPT) that inherits from an existing standard functional profile template
(SFPT), and then add new mandatory or optional member network variables to the UFPT. This
method results in a new functional profile that you can easily reuse in new devices. See the
NodeBuilder Resource Editor User’s Guide for more information on creating UFPTs.
Interoperable Self-installation (ISI) Protocol
The standard protocol for performing self-installation in L ON W ORKS networks. ISI is an
application-layer protocol that lets you install and connect devices without using a separate network
management tool.
ISI Mode
An installation scenario in which the ISI protocol is used (instead of the LonMaker tool or other
network tool) to install devices and create network variables connections.
LNS
A network operating system that provides services for interoperable L ON W ORKS installation,
maintenance, monitoring, and control tools such as the LonMaker tool. Using the services provided by
the LNS client/server architecture, tools from multiple vendors can work together to install, maintain,
monitor, and control L
ON W ORKS networks. The LNS architecture consists of the following elements:
1. The LNS Client application program, which can be used to develop, monitor and control
L ON W ORKS networks.
2. The LNS Object Server ActiveX Control, which is a language-independent programming interface
to access the L ON W ORKS network.
3. The Network Services Server (NSS), which maintains an image of the network.
4. The Data Server, which provides services for monitoring and control.
5. The Network Services Interface (NSI), which is the physical interface to the network .
LNS Device Template
A device template automatically generated by the NodeBuilder tool when you build a device
application. The LNS device template defines the external interface to the device, and it is used by the
LonMaker tool and other LNS network tools to configure and bind the device
LNS Network Database
Each L ON W ORKS network has its own LNS network database (also referred to as the network
database), which includes the network and device configuration data for that network. The network
database also contains extension records, which are user-defined records for storing application data.