Echelon IzoT BACnet Developes - Manual (Page 25)

Functional Block Array
A set of identical functional blocks. A functional block array is useful if your device contains two or
more identical switches, lights, dials, controllers, or other I/O devices that will each have an identical
external interface. In addition, a functional block array saves code space and reduces the number of
when-tasks in your code.
Functional Profile
A template for a functional block that enables equipment specifiers to select the functionality they need
for a system. Each functional profile defines mandatory and optional network variable and
configuration property members along with their intended usage. A number of generic standard
functional profiles are available for generic devices such as simple sensor and actuators. Many
industry-specific standard functional profiles are available for industry-specific applications.
Industry-specific standard profiles are developed through a review and approval process, including a
cross-functional review to ensure the profile will interoperate within an individual subsystem and also
provide interoperability with other subsystems in the network.
User-defined functional profiles can be created if no appropriate standard profiles are available.
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.
Interoperable Self-Installation (ISI) Protocol
The standard protocol for performing self-installation in LONWORKS networks. ISI is an
application-layer protocol that lets you install and connect devices without using a separate network
management tool. It is typically used in home networks, and may be used in any network with less
than 200 devices with simple connection and configuration requirements.
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.
OpenLNS
A network operating system that provides services for interoperable L ON W ORKS installation,
maintenance, monitoring, and control tools such as the OpenLNS 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. OpenLNS client applications, 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 for OpenLNS client applications to access the L ON W ORKS network.
3. The OpenLNS Server, which manages the network and maintains a database containing the
network configuration.
OpenLNS Network Database
Each L ON W ORKS network has its own OpenLNS network database (also referred to as the network
database) that is managed and maintained by an OpenLNS Server. The network database 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.
Using BACnet and LONWORKS with the FT 6000 EVK 25