Echelon IzoT NodeBuilder - Manual (Page 280)

NodeBuilder Device Template
An XML file with a .NbDt extension that specifies the information required for the IzoT NodeBuilder
tool to build the device application. The NodeBuilder device template includes a list of Neuron C
source code files and the hardware template name
NodeBuilder Hardware Template
A file with a .NbHwt extension that defines the hardware configuration for a target device. It specifies
hardware attributes including platform, transceiver type, Neuron Chip or Smart Transceiver model,
clock speed, system image, and memory configuration. Several hardware templates are included with
the IzoT NodeBuilder tool. You can use these or create your own. Third-party development platform
suppliers may include NodeBuilder hardware templates for their platforms
NodeBuilder Project
A NodeBuilder project collects all the information about a set of devices that you are developing.
NodeBuilder Project Manager
The NodeBuilder Project Manager provides an integrated view of an entire NodeBuilder project and
provides the tools for defining and building a NodeBuilder device.
Non-const Device-specific Configuration Property
A configuration property that can be changed by the device application, an LNS network tool such as
the LonMaker tool, or another tool not based on LNS. For example, a thermostat may include a user
interface that allows the user to change the setpoint.
OffNet
A management mode in which network configuration changes are stored in the network database, but
not propagated to the devices on the network. To send the changes to the devices, you place the IzoT
Commissioning tool OnNet. If the IzoT Commissioning tool is OffNet and attached to the network,
you can still perform read operations on the network.
OnNet
A management mode in which network configuration changes are propagated immediately to the
devices on the network.
OpenLNS
A network operating system that provides services for interoperable L ON W ORKS installation,
maintenance, monitoring, and control tools such as the IzoT Commissioning tool. Using the services
provided by the OpenLNS client/server architecture, tools from multiple vendors can work together to
install, maintain, monitor, and control L
ON W ORKS networks. The OpenLNS architecture consists of
the following elements:
1. The OpenLNS Client application program, which can be used to develop, monitor and control
L ON W ORKS networks.
2. The OpenLNS 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 .
Optional Network Variable/Configuration Property
A network variable/configuration property that may be implemented by the functional block, as
specified by the functional profile that the functional block is instantiating.
266 Appendix C: Glossary