Echelon OpenLNS Commissioning Tool - Manual (Page 24)

8 Introduction
actuator has mandatory SNVT_switch input and output network variables, optional
SNVT_elapsed_tm and SNVT_elec_kwh output network variables, and a number of optional
configuration properties. The following diagram illustrates the components of the standard light
actuator functional profile:
When a functional block is created from a functional profile, the application designer can determine
which of the optional configuration properties and network variables to implement.
Standard Network Variable and Configuration Property Types
Every network variable and configuration property has a type, which determines the content and
structure of the data. To enable devices from different manufacturers to interoperate, the following
standard types are defined:
• Standard Network Variable Types (SNVTs, pronounced snivits). SNVTs contain many common
operational data types. For example, SNVT_temp_p is a network variable type for network
variables containing temperature as a fixed-point number.
• Standard Configuration Property Types (SCPTs, pronounced skipits). SCPTs contain many
common configuration data types. For example, SCPT_location is a configuration property type for
configuration properties containing the device location as a text string.
See types.lonmark.org for a list and description of all SNVTs and SCPTs.
User-defined Standard Network Variable and Configuration Property Types
Applications may use manufacturer-defined non-standard types—user network variable types
(UNVTs) and user configuration property types (UCPTs)—which are defined in user resource files.
Device manufacturers may provide additional resource files that define these types. See the
NodeBuilder Resource Editor User’s Guide for additional information on creating or using these files.
Subsystems
Devices, routers, and functional blocks are contained in subsystems. With OpenLNS CT, each
subsystem corresponds to one page within an OpenLNS CT drawing. Subsystems allow you to place
devices, routers, and functional blocks onto separate pages for organizational purposes. You may also
nest subsystems in other subsystems, allowing you to create a subsystem hierarchy for large networks.
For example, a network may consist of HVAC, lighting, security, and operator subsystems. These may