Professional Documents
Culture Documents
Lonworks - A Documentation
Lonworks - A Documentation
ABSTRACT
provides a platform for building industrial, transportation, home automation and public
utility control networks to communicate with each other. Built on the Local Operating
Network, it uses the LonTalk protocol, in order to have a peer to peer communication
applications for over nine years, and was a LONWORKS Independent Developer for
over six years. As the result of this extensive background in applying LONWORKS
technology solutions to problems in the real world, products and services from IEC can
The nodes on a LON may be thought of as objects that respond to various inputs
and produce desired outputs. Linking the inputs and outputs of network objects enables
the network to perform applications. While the function of any particular node may be
quite simple, the interaction among nodes enables a local operating network to perform
complex tasks. A benefit of local operating networks is that a small number of common
node types may be configured to perform a broad spectrum of different functions
depending how they are linked in a network.
2. OPEN SYSTEMS:
Each component part of a control system plays a role. Hardware is used to
measure real-time values and cause control actions and software is utilized to
manipulate system hardware for the purpose of monitoring and controlling system
functions. The physical devices that are commonly found in an HVAC control system
include:
Develop and edit control logic: Typically used with programmable controllers,
this software is used to develop control applications that can be downloaded into
programmable controllers.
System architecture is the term used to describe the overall network structure of
a control system. In many instances, a primary LAN, using a standard protocol such as
TCP/IP, provides connectivity for operator interfaces to remotely access control system
data. A router and/or area controller acts as a bridge between the primary LAN and the
fieldbus on which DDC controllers exist.
In control systems, gateways are often used to connect systems from different
manufacturers—they act as an interface between proprietary control systems, allowing
equipment using different proprietary protocols, communication speeds, and/or data
formatting to exchange data.
A host bridge combines the functions of a user interface with those of a gateway
to provide a high-end workstation that communicates with multiple vendors' proprietary
control system equipment. In this architecture, software drivers replace separate
gateways. The workstation is typically capable of displaying real-time data, allowing
control commands and setpoint changes, and handles alarms and error messages, but
detailed editing of control logic still requires knowledge and use of underlying
proprietary software.
From the vendor's perspective, a move towards the production of hardware and
software products that support open systems carries major risk:
LONWORKS OVERVIEW:
LonWorks is the name given to the collective technology developed by the
Echelon Corporation for implementing control system networks. The root term, LON, is
an acronym for local operating network, which refers to an intelligent control network
that facilitates communications between devices or nodes that communicate with one
another over a variety of transmission media using a common, message-based control
protocol. Echelon's design endeavors to provide an off-the-shelf method for
manufacturers to build devices that can coexist and operate as peers on a flat,
interoperable control network.
3.3 LONMARK:
If a device is designed to use the LonWorks technology, depending on the
implementation, it may or may not interoperate with other LonWorks devices. Simply
using the LonWorks technology does not guarantee interoperability. The LonMark
certification is granted through the LonMark Association, which is a large, relatively
independent organization of manufacturers, suppliers, and end users from around the
world.
The organization develops technical product specifications and guidelines that
promote interoperability among participating equipment manufacturers. Participation of
this nature promotes interconnection and intercommunication with other products.
LonMark refers to the mark signifying that a product has met LonMark guidelines that
allow it to interoperate with other LonMark devices on a LON.
4. LONWORKS ARCHITECTURE:
5.1 Elements Overview
The LonWorks technology includes all of the elements required to design,
develop, and deploy control system networks. These include:
• The Neuron Chip
• LonTalk protocol
• LonWorks communications transceivers and network interface
• Network management tools
In addition to the Neuron chip, LonWorks devices require a transport system that they
can use for communications. As part of the LonWorks technology, Echelon has defined
and provides much of the infrastructure needed to implement these networks.
5.1.1 The Neuron Chip
The central component of an Echelon node is the Neuron chip. Each Neuron chip
contains three 8-bit, in-line CPUs, on-board memory, eleven general-purpose I/O pins,
and a complete interoperable implementation of the LonTalk protocol. In fact, on
Neuron-based nodes, the Neuron chip alone does the vast majority of the work performed
by the node. Except for the power supply, I/O devices, and some of the transceiver
functions, all work performed by the node is done by the Neuron chip.
As shown in Figure 5-1, the Neuron chip performs several different duties at
once. It is a processor, a device controller, a memory chip, and it has built-in EEPROM
that contains network configuration and addressing information, a unique permanently
programmed 48-bit serial number, and optional user-written application code. There are
two models of the Neuron chip available from Echelon: the 3120 and the 3150. Both
models provide three processors (two dedicated to communications and another dedicated
to applications processing), I/O device controllers that support connection to applications
hardware, timing and counting hardware, and a transceiver interface. Both chips include
on-board memory. The 3120 includes RAM (1K) and ROM (10K), where the 3150
includes 2K of RAM (no ROM) and an external memory interface for more complex
applications processing.
The address table defines the network addresses to which a node can send
messages and network variables. It also defines the group(s) to which the node belongs.
For each address table entry, the first byte contains the type of address table entry
including group, subnet/node, broadcast, turn-around, or not in use.
• Group addressing is used for multi-casting, when a network variable or message
tag is used in a connection that has more than two members.
• A subnet/node address is used when a message is to be sent to only one other
node.
• Broadcast addressing is not typically used, but it is supported by the protocol to
allow explicit messaging.
5.1.1.6 Network Variable Tables
Network variables have three associated tables: the network variable
configuration table, the network variable alias table, and the network variable fixed table.
• Network Variable Configuration Table: Defines the configurable attributes of
the network variables in the node. The table is located in EEPROM so that it can
be modified and it becomes part of the network image written to the node during
installation.
• Network Variable Alias Table: Defines the configuration attributes of the alias
network variables in the node. This table is also located in EEPROM,
immediately following the network variable configuration table.
• Network Variable Fixed Table: Defines the compile-time attributes of the
network variables in the node. The table may be located in ROM and it is part of
the application image written at the time the device is downloaded.
5.1.2 Hosted Nodes
In addition to Neuron-based nodes, where the application layer (OSI layer seven)
runs in the Neuron chip, control devices can also use a separate dedicated microprocessor
to run the layer seven applications. Nodes that off-load the application layer to a separate
host processor are referred to as hosted nodes.
Three different communications interface modules are available:
Microprocessor Interface Program (MIP): This module supports custom network
interfaces.
The Network Services Server (NSS) engine: This module is used in the LNS
architecture to process network services, maintain the network database, and enable and
coordinate multiple points of (PC) access.
Network Services Interface (NSI): This module is used in the LNS architecture to
provide connectivity to the LonWorks network from multiple clients.
5.1.3 Transceivers, Media, and Network Topology
In addition to the Neuron chip, LonWorks devices require one of several
transceiver modules for communications. These devices are manufactured by Echelon
and they provide connectivity for virtually every transmission media including twisted
pair, power line, RF, infrared, coaxial cable, and fiber.
Probably the most versatile and popular transceiver is the FTT-10 Free Topology
transceiver, which supports twisted pair, unshielded, polarity-insensitive, peer-to-peer
communications at 78 Kbps. Examples of FTT-10 network topologies are illustrated in
Figure 5-3 and Figure 5-4.
A network segment in a free topology network is any part of the network in
which each conductor is electrically continuous. Each of the four diagrams above is a
segment. Some application may require two or more segments.
5.1.3.1 FTT-10 Topology
As illustrated in Figure 4-3 and Figure 4-4, there are two broad categories of
wiring topologies supported by FTT-10: the Free Topology approach and the Doubly
Terminated approach.
• The Free Topology approach allows any number of tees, stars, loops, or bus
combinations in a wiring segment.
• The Doubly Terminated approach, although it supports greater wiring lengths, is
significantly more restrictive in terms of wiring topology.
A single wiring segment supports up to 64 nodes (FTT-10 transceivers), but a channel
can span multiple segments that employ physical layer repeaters to expand both the
number of nodes and the length of the control network. Depending on the application and
expected network performance (in terms of response time), the maximum number of
nodes supported by a LonWorks network is 32,385.
5. LONTALK PROTOCOL
LonTalk is Echelon's open-architecture communications protocol that defines the
rules for communicating on a LonWorks network. The protocol follows the OSI
reference model developed by the International Standard Organization (ISO) and it uses
all seven layers of that model, as shown in Table 5-1.
6.1 Logical Addressing:
Since each Neuron ID is unique, it could be used as an address. But, such an
addressing scheme would support only one-to-one transactions (meaning no groups). To
simplify routing, the LonTalk protocol defines a hierarchical form of address to logically
address each node. In the process known as network management, software is used to
associate the node's unique 48-bit Neuron ID to a logical domain, subnet, and node
number.
The components of a logical address include:
• Domain—Nodes must be on the same domain to communicate, but if different
network applications exist on the same transmission medium, different domain
identifiers can be used to keep the applications separate.
• Subnet— The second level of addressing is the subnet. A subnet is a logical
grouping of up to 127 nodes from one or more channels. Each domain can have
up to 255 subnets.
• Node Address—Each node must have a unique node number on a subnet. Up to
127 nodes can exist on a subnet.
The transmission medium (channel) does not affect the way a node is logically
addressed. Domains can contain several channels as can subnets and groups.
6.1.1 Routing Messages
A router or bridge is a special purpose node that contains two Neuron chips and
transceivers, each connected to a separate channel.
• A physical layer repeater is the simplest form of a router, merely forwarding all
packets it receives. Using a repeater, a subnet can exist across multiple channels.
• A bridge forwards messages for a given domain ID. Using a bridge, a subnet can
exist across multiple channels.
• A learning router monitors network traffic and learns the topology at the
domain/subnet level and it uses that knowledge to selectively route packets
between channels.
6.2 Communications Services
The LonTalk protocol offers four basic types of message service. The first two,
acknowledged and request/response, are end-to-end acknowledged and the other two,
repeated and unacknowledged, are unacknowledged. In addition to the LonTalk message
service options, the protocol offers a priority mechanism to improve response time for
critical messaging and authentication for security. System design should employ the most
effective use of network efficiency, response time, security, and reliability, but, generally
speaking, the LonTalk protocol defaults to that which provides the greatest level of safety
and verification for all network communications.
1. Acknowledged Service: The most reliable message service is acknowledged.
With this service, messages are sent to a node or a group of nodes, and individual
acknowledgements are expected from each receiving node.
2. Request/Response Service: The request/response service is as reliable as the
acknowledge service, in fact, it is the same as the acknowledged service, except a
response is sent rather than an acknowledgement.
3. Repeated Service: Also referred to as the unacknowledged/repeated service, this
service sends a message to a node or a group of nodes multiple times (n times at
intervals of m milliseconds) and expects no response.
4. Unacknowledged Service: The least reliable message service is
unacknowledged. With this service, the message is sent one time and no response
is expected. A timer, called the free buffer wait timer, is used to determine how
long the node waits for a free message buffer prior to sending its message.
6.3 Collision Detection:
All networking protocols use a media access control algorithm to allow devices to
determine when they can safely send a packet of data. These algorithms are designed to
reduce the number of collisions that occur when two or more nodes on the network
attempt to send data at the same time. Packets that collide cannot be successfully
delivered, which results in a delay in response time.
The LonTalk protocol implements a unique collision avoidance algorithm that
allows an overloaded channel to carry close to its maximum capacity, rather than have its
performance degrade due to excessive collisions. This is of particular importance when
the medium being used lends itself to collisions (for example, twisted pair). In such a
case, the LonTalk protocol:
• Optionally cancels transmission of a packet as soon as a collision is detected, and
• Waits a random period of time before attempting to retransmit.
6.4 Timers
There are several timers used with the LonWorks messaging service. Typically,
these timers are automatically configured by a network management tool. Also known as
layer 4 timers, these include:
• Free Buffer Wait Timer
• Transaction Timer
• Group and Non-Group Receive Timers
• Repeat Timer
7. INTEROPERABILITY
8.1 Network Variables
Echelon defines a network variable as a data item that a particular device
application program expects to get from other devices on a network (an input network
variable) or expects to make available to other devices on a network (an output network
variable). Network variables can be any single data item, or they can be data structures.
Examples of network variables may include temperature, switch positions (binary), or
actuator position (analog). An example of a network variable that uses data structures is
SNVT_temp_setpt—this one variable contains 6 setpoints.
8. RECENT APPLICATIONS
a. Buses in Italy Stop for LonWorks Networks
Brescia Trasporti SpA, the public transportation company for the Italian city of
Brescia, decided to improve its monitoring system to allow the immediate exchange of
data between buses, electronic bus stops, and a control center.
To monitor the bus network within the city of Bresica, Italy, Microlab Sistemi
srl implemented a flexible and expandable integrated solution based on Echelon’s
LonWorks technology. This new system consists of a meshed network, which connects
56 electronic bus stops. Each electronic bus stop is connected via existing twisted-pair
cable to central control center. Furthermore, each bus stop contains a special LonWorks
based CPU, integrated with a Neuron 150 chip and FTT-10 transciever.
Problem-free Expansion
Connection between the various electronic bus stops has been obtained by using
existing twisted-pair cable. However, Microlab Sistemi needed to offer a future-proof
solution that would facilitate easy system expansion at a later date. In a city center it is
extremely difficult, if not impossible, to obtain excavation permission. Thus, installing
further twisted-pair cables would not be an option, as this would necessitate road works.
Key Benefits
In additional, many end user organizations require the LonWorks platform, including
the US Army Corps of Engineers and the New York CIty Public Schools District.
10. CONCLUSION
In Summary….
The simple way of installation and operation, the standardized by the Lonmark
organization network variables (SNVT's) the device templates, the wide choice of
communication channels and transceivers and the information which is freely spread for
the Lon technology make Lonworks the most interoperable protocol at the BMS sector
today. The Lon networks are sponsored as open networks and probably this is the best
way to describe the protocol itself.
All the big BMS manufactures such as Siemens, Johnson controls, TAC and
Honeywell have turned to Lonworks technology, a fact that ensure the future of
Lonworks as the interopable protocol of the BMS industry. Very close to the
development of lonworks we can relate the TCP/IP protocol which gave the opportunity
to all the computers in a network to communicate directly nomatter what operating
system or hardware they use. TCP/IP which was first brought to the computer market a
few years ago today has dominated the computer world and especially the internet which