Technical Resources

• Overview

• Guides & Specifications

• Resource Files

• White Papers

• Manufacturer IDs

• Technical Corner / FAQs

• Terminology

• Standards

  Related Information

Device Certification - LonMark conformance instructions.

Design Guidelines - Technical information for developing open interoperable LonMark products.

Technical Corner - Provides answers to commonly asked technical questions.

LonMark Members who manufacture products used in Open Systems

Terminology (R - S)

The descriptions and terminology contained within this document are made in the context of use with LonWorks® networks and products.




Random access memory, which has read-write capabilities. This type of memory is volatile implying it loses contents on power loss.

Remote Client

The name of the PC running the network management  tool when it is not the LNS® Server.

Remote Full Client

A network management tool communicating with LNS server through a LonWorks or LonWorks IP channel. When OnNet, a remote full client can monitor and control the network without routing the requests through the LNS Server. It can also make configuration changes. There are a number of ways a remote full client can be connected to the LNS Server; the simplest is by connecting directly to a LonWorks network using an LNS network interface.

Remote Lightweight Client

A network management tool communicating with LNS server through an IP channel. The combination is called an LNS/IP channel. When OnNet, a remote lightweight client can monitor and control the network. It canNOT make configuration changes.

Remote Operation

Describes using the network management tool on a PC other than the LNS Server.


Resets the device by sending the Reset network management command to the device to stop execution, terminate all incoming and outgoing messages, set all temporary settings to their initial values, and start the application again using the original conditions. If the device was offline, it will be put online.


Read-only (non-volatile) memory. This type of memory maintains its contents after a power loss.


Multiple channels can be connected using routers. Routers are used to manage network message traffic, extend the physical size of a channel (both length and number of devices attached), and to connect channels that use different media (transceiver types) together. Unlike other devices, routers are always attached to two channels. LonWorks /IP routers may be used to connect LonWorks networks to the Internet or IP networks. See also LonWorks Router.

SCPT (see Standard Configuration Property Type)

Segment (see Channel Segment)


It associates a network variable in an FB with the connection, thus determining which network variable is the intended recipient of the update. The following restrictions apply to selector values:
1.   Network variables within a selection can only share one selector.
2.   Multiple input network variables on a node cannot share a selector.
3.   Each network variable can only have one selector.
4.   An alias, required to resolve selector conflicts, uses a selector.


A mechanism that a device can use to provide descriptive information.  Self-documentation can be provided for the device's program and network variables.  A provider of user-defined services and events may also support self-documentation for itself, its services, events, objects, and properties.  When possible, the NSS makes self-documentation information available to the host application through properties.


A mechanism that a device can use to document the types of network variables it contains (identified by SNVT ID). When available, the NSS and the network management tool automatically import this information to determine a device's external interface.


Any component that is used to determine the condition or value of a physical system variable, or to accept commands from a human operator.

Shared Media

A shared media system is one where multiple, independently managed networks share one (or more) physical channels. For example, in a building, if multiple systems use the power wiring of the building as a channel, they are shared media systems. Systems using shared media must follow pre-established rules to ensure that they don't interfere with one another during system configuration or repair. See also Private Media.

SLTA (Serial LonTalk Adapter)

A serial NSI interface with built-in twisted pair transceiver that connects to any host with an EIA-232 (formerly RS232) port.  It can also connect to the host remotely using a Hayes compatible modem.  For example, Echelon Corporation's "SLTA-10" is for use with a remote application or for portable hosts that do not contain a Type II PC slot or USB slot.

A network interface that provides an EIA-232 (formally RS-232) interface to connect a host processor to a LonWorks network.

SNVT (see Standard Network Variable Type)


A code used to identify the type of SNVT used by a network variable. A value of 0 indicates that the variable is not a SNVT. Also sometimes called a SNVT index.

SOAP (once known as: Simple Object Access Protocol)

SOAP is a simple XML based protocol to let applications exchange information over HTTP. It provides a way to communicate between applications running on different operating systems, with different technologies and programming languages.

Source Address

The logical node address of the transmitting node, contained in every packet transmitted over a LonWorks network.

Standard Configuration Property Type (SCPT)

A method of storing application configuration data using files that are read and written using the LonWorks File Transfer Protocol (LW-FTP); via direct memory-read/write of the file data (DM-R/W); or through config network variables using typical network-management tools. SCPTs are defined by LonMark International to ensure that LonMark devices can be configured without a proprietary configuration tool. There are hundreds of them defined by LonMark.

Standard Network Variable Type (SNVT)

SNVTs facilitate interoperability by providing a well-defined interface for communication between devices made by different manufacturers. See the Echelon or LonMark website for a current list and documentation.


Stencils are used to simplify finding and reusing shapes. Stencils contain shapes that may be reused in the drawings. The shapes contained on a stencil are called master shapes.

A logical collection containing up to 127 devices within a domain.  Up to 255 subnets can be defined within a single domain.  All devices in a subnet must be on the same segment.  Subnets cannot cross non-permanent type routers.

Subnet/Node ID

The logical address assigned to a device after it has been commissioned. In a network with one subnet, the LNS Network Interface is assigned a Subnet/Node ID of 1/127, whereas all other devices Subnet/Node IDs begin with an address of 1/1 and increase sequentially to 1/2, 1/3, etc. the network management tool automatically assigns these values.

The subnet portion of the ID is used to route packets. Packets will only be exposed to other channels (subnets) as required, i.e. the source channel, the destination channel and all channels between the source and destination. The node ID portion of the address is used to identify a device on a subnet.

The address is hardware independent. When a device is replaced, the new device will use the same Subnet/Node ID. A device’s Subnet/Node ID and Neuron ID can be found in the Identifiers tab of the device’s properties. See also Neuron ID.


Subsystems contain devices, routers, and functional blocks. Subsystems allow the placement of devices, routers, and functional blocks onto separate folders for organizational purposes.

Subsystems may also be placed in other subsystems, allowing the creation of a subsystem hierarchy for large networks. For example, a network may consist of HVAC, lighting, security, and operator subsystems. These may be further divided into subsystems for each floor, and each floor divided into subsystems for each room.


A subsystem with its own network variable interface. Supernodes may be used to organize groups of devices into logical units and to hide complex subsystem details, exposing only the desired network variables. This reduces errors and decreases the time required for network engineering and commissioning. A supernode’s network variable interface may contain any network variable on any device found within the supernode or its nested subsystems.


© 2007-2019 LonMark International. Terms of Use | Privacy Policy (“Cookie”) cookie settings: view/edit