Echelon IzoT NodeBuilder User Manual
Page 276
i.LON IP-852 Router
An i.LON IP-852 router forwards ISO/IEC 14908-2 packets enveloped in ISO/IEC 14908-4 packets
over an IP-852 channel. i.LON IP-852 routers include the i.LON SmartServer with IP-852 routing,
i.LON 100 e3 Internet Server with IP-852 routing, and the i.LON 600 L
ON
W
ORKS
-IP Server.
I/O Object
An instantiation of an I/O model. An I/O objects consists of a specific I/O model, and its pin
assignment, modifiers, and name.
IP-852 Channel
Also known as an ANSI/CEA-852 L
ON
W
ORKS
/IP channel, an IP-852 channel carries ISO/IEC
14908-2 packets enveloped in ISO/IEC 14908-4 packets. An IP-852 channel is a L
ON
W
ORKS
channel
that uses a shared IP network to connect IP-852 devices and is defined by a group of IP addresses.
These IP addresses form virtual wires that connect IP-852 devices so they can communicate with each
other. IP-852 devices include the LNS Server computers, LonMaker computers, and
i
.LON IP-852
routers. An IP-852 channel enables a remote full client to connect directly to a L
ON
W
ORKS
network
and perform monitoring and control tasks.
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 IzoT Commissioning 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.
IzoT Commissioning Tool
An OpenLNS network tool that uses Visio as its graphical user interface. The IzoT Commissioning
tool is used to design, commission, maintain, and document distributed control networks comprised of
both L
ON
M
ARK
and other L
ON
W
ORKS
devices.
262
Appendix C: Glossary