Openlns object hierarchy – Echelon OpenLNS User Manual

Page 41

Advertising
background image

OpenLNS Programmer's Reference

4

a Subsystem. Different Subsystems can contain devices with the same name, however.

For example, a building may consist of a Subsystem object for each room, with each room

Subsystem including AppDevice

object

s called VAV and Thermostat.

The NetworkServiceDevice class provides a logical representation of the OpenLNS Server

and its NSI. The network service device, in turn, contains a NetworkInterface object.

This network interface determines the driver name to be associated with the system, if

any. Many additional object classes are provided to OpenLNS applications through the

Object Server.

OpenLNS Object Hierarchy

System

TemplateLibrary

Interface

Channel

NetworkServiceDevice

ComponentApp

Extension

NetworkInterface

DeviceTemplate

Subnet

Subsystem

Subsystem

AppDevice

ConnectDescTemplate

NetworkInterface

AppDevice

ObjectServer

Channel

NetworkInterface

AppDevice

Extension

Extension

NetworkServiceDevice

Subnet

Connections

MessageTag

NetworkVariable

Interface

Alias

DeviceTemplate

ComponentApp

Extension

Interface

NetworkVariable

ConfigProperty

MessageTag

ConfigProperty

LonMarkObject

NetworkVariable

LonMarkAlarm

ObjectStatus (2)

Network (3)

Application

Interface

AppDevice (MyVNI)

NvMonitorPoint

NvMonitorOptions (2)

FormatSpec

MsgMonitorOptions (2)

LdrfLanguage

Router

Channel

Subnet

RouterSide (2)

Extension

Subsystem

DetailInfo

Extension

UpgradeStatus

UpgradeInfo

NvMonitorOptions

MsgMonitorOptions

FormatSpec

DataPoint

A parenthetical number next to an object or collection
indicates that the parent object references multiple
copies of that object or collection.

FormatSpec

DataPoint

Extension

DetailInfo

Subsystem

TestInfo

Error

Extension

RecoveryStatus

ComponentApp

PingIntervals

ServiceStatus

ConfigProperty

Account

FileTransfer

MsgMonitorPoint

MonitorSet

DataValue*

SourceAddress*

FormatSpec (2)

*Object is not referenced directly by any other object, but is
created by events and methods. The DataValue and
SourceAddress objects are created by network variable and
monitor point update events, respectively. The
DatabaseValidationReport,
DatabaseValidationErrorSummary,
andDatabaseValidationErrorInstance objects are created
when you call the Validate() method.

NetworkResources

FormatLocale

TestInfo

TypeSpec

DatabaseValidationReport*

DatabaseValidationErrorSummary*

DatabaseValidationErrorInstance*

MonitorSet

DataPoint

DataPoint

ActivationLicense

KEY:

Object Only

Object &

Collection

TypeSpec


Advertising