LonWorks Network Design

Download Report

Transcript LonWorks Network Design

LONWORKS Network
Design
Overview
1-2
Welcome!
1-3
Course Objectives
• Identify network architectures
• Select and install network infrastructure
components
• Select and install network devices
• Program the network by configuring
devices and connecting network
variables
• Commission devices
• Test and verify network devices and
channels
• Optimize network and device
performance
• Document the network design
• Maintain the network
Identify
Architectures
Select Network
Components
PLAN THE NETWORK
Install Physical
Network
Program
Network
Commission
Network
IMPLEMENT THE NETWORK
Test and Verify
Network
Optimize
Network
TEST AND OPTIMIZE
Document
Network
Maintain
Network
DOCUMENT AND MAINTAIN
LONWORKS
Technology Overview
2-2
Objectives
Review the following LONWORKS Technology concepts:
 Control Networks
 LONWORKS Benefits
 LONMARK International
 LONWORKS Terminology
 LonTalk Protocol
 Basic LONWORKS Components
 Device Interface Components
 LONWORKS Network Services (LNS®)
2-3
Control Networks
1st Generation
1st Generation
Master/Slave




Centralized Architecture
• Centrally located processor
• No integrated intelligence
• Single point of failure


A single master control device or
panel makes the control decisions
Master controller continuously polls
input devices for values and directs
output devices to play values
Single point of failure
Difficult to expand
Costly to install – more wiring
needed to connect sensors and
actuators
Proprietary programming model
2-4
Control Networks
2nd Generation
2nd Generation
Decentralized Master/Slave



Networked PLCs
• Distributed intelligence
• Centrally located processor
• Single point of failure reduced



Added network programable logic
controllers (PLCs) between central
processor and devices
Single master control device makes
the control decisions
Master controller continuously polls
PLCs for values and directs output
devices to play values
Greatly reduced wiring requirement
Reduced point of failure
Proprietary programming model
2-5
Control Networks
3rd Generation
3rd Generation
Can remove
after installation
complete
Peer-to-Peer



Monitoring and
control can be
added at any point

Decentralized Automation

• Distributed intelligence
• Intelligent nodes/devices
• No central processor needed
• Single point of failure eliminated
• Reduced wiring requirement
Distributed control intelligence
within all control devices
No single point of failure
Easy to expand and add more
devices
Less costly wiring installation

No home I/O wiring runs
Event driven

Devices publish control
information to the network
2-6
The Origins of
LONWORKS Technology
• Local Operating Network
• Echelon founded in 1988 by AC
‘Mike’ Markula
 CEO of Apple Computer
• First Neuron Chip shipped in 1991
• Echelon is a global company
 250+ employees
 Nasdaq listed ELON
 100+ products
• LonTalk is an implementation of
an open protocol international
standard
 ISO/IEC 14908-1


ANSI/CEA 709.1B
EN14908-1
2-7
Benefits of the
LONWORKS Platform
• Robust, reliable, proven everyday device
networking protocol on a single
inexpensive microchip
• Distributed control with reduced single
point of failure
• Manufacturers of smart everyday devices
can get to market quickly
• End users no longer locked into single
supplier
• Integrators can choose best of breed devices
• LonTalk ISO/IEC 14908-1 protocol is
media independent
• LONWORKS tools operate on multiple
computer platforms
• Multi-industry standards group ensure
interoperability – LONMARK International
• Overall result –




Lower costs
Decreased complexity
Flexibility for changes
and expansion
More options
Open Systems
2-8
• To ensure an open interoperable system is delivered


All application-specific controllers should be LONMARK
certified
Network architecture should follow the LONMARK Open
Systems Architecture definition.
• Benefits







Ability to chose between multiple vendors
Affordable and economical service and system expansion
Sub-system and device-level expansion at any time
Full choice of service providers
Facilitate interoperability with other vendors / systems
Plethora of choices
Flexible, expandable automation
2-9
LONMARK International
Making Plug-and-Play A Reality
• LonMark International is a global membership
organization created to promote and advance the
business of efficient and effective integration of open,
multi-vendor control systems utilizing ISO/IEC
14908-1 and related standards.
2-10
Who is LONMARK International?
• Manufacturers, distributors, engineers, system
integrators and end-users
• California based non-profit corporation.
• Over 500 members worldwide
• Over 750 certified interoperable products
• Over 70 approved functional profiles
• Oversees open systems professional certification
The word LONMARK itself is a trade association symbol
LONMARK - A Virtual
Who’s Who in Control Networking
Look for the
LONMARK Label
2-12
• Ensures that products will interoperate in the
most efficient and economical way possible in an
open, integrated control system
• Includes the number designating the latest
version of the LONMARK Interoperability
Guidelines as shown here.
• Certifies product conformance following
technical guidelines and standards developed by
industry specific task groups





SFP - standard functional profiles
SNVT - standard network variable types
SCPT - standard configuration property types
Provides a resource of device information
Controllers, actuators and application-specific
devices can be LONMARK Certified
A-3
•
•
•
•
•
•
•
•
•
•
•
•
LON Speak
LONWORKS
LonTalk
LNS
LONMARK
LonMaker
LonPoints
Network Integrator
Neuron Chip
Device/Node
i.LON
Domain/Subnet/Node
Client/Server
•
•
•
•
•
•
•
•
•
•
•
•
Channel
Network Variable
Binding
Configuration Property
Functional Profile
Functional Block
Plug-In
External Interface File (XIF)
SFPT or SFP
SNVT
UNVT
SCPT and UCPT
2-13
LONWORKS – Distributed
Control Intelligence
• Puts the control intelligence inside the
• Flat LonWorks architectures
device where the control happens
allow devices to communicate
with each other without passing
• Each device may subdivide multiple
data through central controller
control functionality into objects called
functional blocks
 Could be I/O, controller, system wide
functions or a combination
• Any device can communicate with any
other device using standard data types
• Can create large, powerful and flexible
networks across LANs and WANs
• Reduces installation costs compared to
Master/Slave systems
SetTime
Time
Day
DST
A1
A2
Digital
Realtime Clock
Analog
A_Out
Digital_Out
Function Block
Analog
Digital
Binary In
Control
Data_In
Digital
Analog
Translator
Digital
D1
D2
D3
D4
Auto_Man
Man_Value
CV
SP_Out
Auto_Man_Out
Mode
Enable
PID Controller
0-10V Out
Data_Out
Counter
PV
SP
Feedback
Mode
Enable
2-20mA In
Feedback
Mode
Enable
Digital_Out
Mode_Out
Binary Output
Encoder
Time
Day
Event_Out
DebugEnable
DebugNext
Event Scheduler
2-14
LONWORKS
Network Program
• The network image is a collection of
configured devices and their associated
connections (aka network variable
bindings)
• A network management tool is initially
required to configure device behavior and
define the network variable connections
 When the tool is finished it can go
away!
• LONWORKS uses an event driven control
process
Analog
Function Block
0-20mA In
Digital_Out
Digital
A2
A1
A_Out
Analog
Feedback
Mode
Enable
0-10V Out
A1
A2
Analog
Digital
2-20mA In
A_Out
Digital_Out
D1
D2
D3
D4
Function Block
Digital
Control
Binary In
Digital_Out
Mode_Out
Encoder
Digital
Analog
Counter
Analog
PV
SP
0-10V In
Auto_Man
Man_Value
CV
SP_Out
Auto_Man_Out
Analog
Feedback
Mode
Enable
4-20mA Out
Mode
Enable
PID Controller
SetTime
Time
Day
DST
Realtime Clock
Time
Day
Event_Out
DebugEnable
DebugNext
Event Scheduler
Data_In
Data_Out
Translator
Digital
Feedback
Mode
Enable
Binary Output
LonTalk Protocol
2-14
• Communications protocol - language
of LONWORKS
• Open and published standard
available to anyone

ISO/IEC 14908-1 (ANSI/CEA 709.1)
• Designed for control applications not data applications
• Includes all 7 layers of the ISO Open
Systems Interconnection Reference
Model
• Implemented on all LONWORKS
devices through Neuron Chip or
equivalent processor
• Media independent
7
Application
Neuron C Program
6
Presentation
Network Variables
5
Session
Network Management
4
Transport
Message Service
3
Network
Addressing and
Routing
2
Data Link
Media Access
1
Physical
Physical Connection
Physical Media
LonTalk Standards
2-15
• ISO/IEC 14908-1

Open Data Communication in
Building Automation, Controls and
Building Management
• ANSI/CEA-709.1-B

Control Network Protocol
Specification
• EN 14908-1:2005

Open Data Communication in
Building Automation, Controls and
Building Management
• GB/Z 20177.1-2006

Application
Neuron C Program
6
Presentation
Network Variables
5
Session
Network Management
4
Transport
Message Service
3
Network
Addressing and
Routing
2
Data Link
Media Access
1
Physical
Physical Connection
Control Network LonWorks
Technology Specification
• IEEE 1473

7
Standard for Communications
Protocol Aboard Trains
Physical Media
ISO/IEC 14908 and
Related Control Standards
2-16
International
Organization for
Standardization
International
Electrotechnical
Commission
ISO/IEC 14908 Open Data Communication in
Building Automation, Controls and Building
Management – Control Network Protocol
• ISO/IEC 14908-1
Part 1: Protocol Stack



ANSI/CEA-709.1-B-2000
EN 14908-1:2005
GB/Z 20177.1-2006
• ISO/IEC 14908-2
Part 2: Twisted Pair
Communication



ANSI/CEA-709.3
EN 14908-2
GB/Z 20177.3
• ISO/IEC 14908-3
Part 3: Power Line
Channel Specification



ANSI/CEA-709.2
EN 14908-3
GB/Z 20177.2
• ISO/IEC 14908-4
Part 4: IP Communication



ANSI/CEA-852
EN 14908-4
GB/Z 20177.4
LONWORKS
Network Elements
2-17
• Channel

Device
Network Tool
Media that devices
communicate over
• Device


Actuator, sensor, controller
or combination
LONMARK Certified or
compliant
• Network Tool



Network management tool
Human machine interface
(HMI)
Protocol analysis
Channel
2-18
Network Integration/
Management Tools
• Install devices on a network and enable them to
become active participants in the network by
 Assigning logical network addresses
 Binding network variable connections
 Configuring devices
 Commissioning devices
• Required for non-self installed networks
Also referred to
as Network
Integration Tools
2-19
Network Variables
• The dynamic data sent or
received by network devices
• Create the logical interface to the
network
• Signal-type independent –
temperature, pressure, volume,
flow, etc.
• SNVTs are standard network
variable types as defined by
LONMARK
 Known and documented
structure, size, range, resolution
and scaling for each field.
• UNVTs (user network variable
types) are manufacturer defined
Open Loop Sensor
Object Type #1
nvoValue
SNVT_temp
nvoRawHWData
SNVT_count
nviPresetFb
SNVT_preset
nc17 - Location Label
nc31 - Gain
nc26 - Offset
nc20 - Max Range
nc23 - Min Range
...
nvoPreset
SNVT_preset
Mandatory
Network
Variables
Optional
Network
Variables
Optional
Configuration
Properties
Configuration Properties
2-20
• Define device’s operating or
application behavior such as
setpoint, high limits, throttle.
• SCPTs are standard
configuration property types
defined by LONMARK


Known and documented
structure, format, range, etc.
SCPT Master List available
on www.lonmark.org
• UCPTs (user configuration
property types) are
manufacturer defined
Open Loop Sensor
Object Type #1
nvoValue
SNVT_temp
nvoRawHWData
SNVT_count
nviPresetFb
SNVT_preset
nc17 - Location Label
nc31 - Gain
nc26 - Offset
nc20 - Max Range
nc23 - Min Range
...
nvoPreset
SNVT_preset
Mandatory
Network
Variables
Optional
Network
Variables
Optional
Configuration
Properties
2-21
Functional Blocks
• Defines a single function within a
device – sensor, actuator or controller
• Devices can include multiple
functional blocks
• Include network variables (NV) and
configuration properties (CP)
• Standard Functional Profiles (SFP)
are templates defined by LONMARK
which describe the application-layer
interface
• User-defined functional profiles
(UFP) represent manufacturer
specific control functions
Analog
Discharge Air Temp
Analog
PV
SP
Enable
CV
Analog
Feedback
Mode
Enable
PID- 1
HotWaterValve
Discharge Air Setpoint
schOut1
schOut2
Scheduler
nviAgEnable
nviAgLatchEnbl
nviAgInput
nviAgCompare
nvoAgAlarmFlag
nvoAgAlarm
Temperature Alarm
nviAnEnable
nviAnWeekday
nviAnWeekend
nviAnAlarm
Alarm Notifier
Analog
Room Temp
Analog
nviApplicMode
nviFanOnAuto
nviOccCmd
nviSetpoint
nviSpaceTemp
nviTime
nvoCoolOutput
nvoEffectSetpt
nvoHeatOutput
nvoSetpoint
nvoSpaceTemp
nvoUnitStatus
SetPoint Adjust
Honeywell T7300
Digital
Occupancy Sensor
nvoAnAlmFlag
DischargeTem
Occupancy
RoomSetPt
RoomTemp
Data Logger
RoomTemp
DischAirTemp
DischAirSetP
HotWaterValv
Occupancy
RoomSetPt
Web Server
2-22
LONMARK Standard
Functional Profiles - SFP
• Describe in detail the application-layer
interface required on interoperable
LONMARK devices for specific,
commonly used control functions
• Ensure interoperability by defining
 Mandatory and optional SNVTs
 Mandatory and optional SCPTs
 Default and power-up behaviors
• A device’s primary function
must be based on SFP if it is to be
certified to the LONMARK
Interoperability Guidelines.
• To be LONMARK certified, a device
must contain one or more SFP
• Every SFP must include at least one
network variable or configuration
property
Open Loop Sensor
Object Type #1
nvoValue
SNVT_temp
nvoRawHWData
SNVT_count
nviPresetFb
SNVT_preset
nc17 - Location Label
nc31 - Gain
nc26 - Offset
nc20 - Max Range
nc23 - Min Range
...
nvoPreset
SNVT_preset
Mandatory
Network
Variables
Optional
Network
Variables
Optional
Configuration
Properties
Device Interface Elements
2-23
• Device Interface Elements




Functional Blocks
Network Variables
Configuration Properties
Hardware characteristics
• Device External Interface
File (.XIF)


Created by device
manufacturer
Spawned from the device
application program
Open Loop Sensor
Object Type #1
nvoValue
SNVT_temp
nvoRawHWData
SNVT_count
nviPresetFb
SNVT_preset
nc17 - Location Label
nc31 - Gain
nc26 - Offset
nc20 - Max Range
nc23 - Min Range
...
nvoPreset
SNVT_preset
Mandatory
Network
Variables
Optional
Network
Variables
Optional
Configuration
Properties
Demonstration:
LONWORKS Resources
• LONMARK Web site

SNVT/SCPT master list

Interoperability guidelines

Functional profiles

Case study examples
2-25
LNS® – LONWORKS
Network Services
• Network management
platform
• Foundation for open and
interoperable networks
• Provides unified functions directory, installation,
management, monitoring and
control services to a Windows
program
• Client/server architectures
• Supports open configuration
tools from multiple vendors
• Multiple personnel can
simultaneously access network
and application management
services and data from any
number of client tools
• Provides access to any point of
network information from any
point on the network
• LNS based tools include
resource files
LNS Server
2-26
• Provides network services
LNS Plug-In
LNS Plug-In
Local Client Application(s)
LONWORKS Network
LNS Plug-In
LNS Tool
LNS Server
LNS Plug-In
Database
Remote
Access
LNS Tool
Remote Client Application(s)
LNS Server
Utility

LNS Tool

Network installation and
configuration
Network maintenance and repair
System monitoring and control
LNS Tool

• Maintains network database of
project data stored in
standardized format
• Enables and coordinates
multiple points of access to its
services and data
• Must be present on the network
whenever management
operations are performed
LNS Clients
2-27
• Client - LNS applications, capable
of running locally or remotely.
• A single network can
simultaneously be accessed by
several local and remote
applications.
LNS Plug-In
LNS Plug-In
LNS Tool
LNS Tool
Local Client Application(s)
• Local client application - one
that is running on the same
PC as the LNS Server and
database.
• Remote client application one that is running on a PC
that does not contain the
LNS database or run the
LNS Server.
LONWORKS Network
LNS Plug-In
LNS Tool
LNS Tool
LNS Server
Remote
Access
LNS Plug-In
Database
LNS Server
Utility
Remote Client Application(s)
2-28
1.
2.
3.
4.
5.
6.
Summary and Review
What creates the logical interface to a LONWORKS network?
network variable
What defines a device’s operating or application behavior ?
configuration properties
What provides unified functions - directory, installation, management,
monitoring and control services to a Windows program?
LNS – LONWORKS Network Services
How many layers of the ISO standard for networking does the LonTalk
protocol include?
7 (seven)
What must a device’s primary function be based on if it is to be certified
to the LONMARK Interoperability Guidelines?
SFP - Standard Functional Profile
What does SNVT stand for? SCPT?
Standard Network Variable Type, Standard Configuration Properties
Selecting Network
Architectures and
Topologies
3-2
Objectives
• Describe the steps for creating a network design
• Choose an appropriate network architecture
• Explain the difference between monitoring and control
functions vs. network management tasks
• Identify possible network topologies
• Select design and installation strategies
• Choose a network design tool
Network Design Process
3-3
• LONWORKS networks are
design/build networks
• Engineered networks are built to
fit any application, architecture,
and customer need
• Success requires planning




Using the right parts
Logical design sequence
Safe installation process
Network sustainability
Identify
Architectures
Select Network
Components
PLAN THE NETWORK
Install Physical
Network
Program
Network
Commission
Network
IMPLEMENT THE NETWORK
Test and Verify
Network
Optimize
Network
TEST AND OPTIMIZE
Document
Network
Maintain
Network
DOCUMENT AND MAINTAIN
Planning the Network Design
3-4
• Project information

Who is the customer?
• Control requirements

What does the customer
require?
• Network architecture



What topologies are
possible?
How will network tools
access the network?
How will end users access
network information?
• How will the network
design be created?

Who will create the
design? Where?
• How will the network
program be implemented?

Commissioning, testing,
verification?
• How will the network be
maintained?

Adds, moves, changes,
backups, replacements?
3-5
Job Aid – Network
Design Plan Worksheet
• Begin to design your
network with the Network
Design Plan Worksheet
3-6
Installation Options
• Interoperable Self-Installation (ISI)
 Lowest cost
 Suitable for simple networks
with simple configuration and connections
• Standard installation tool using an i.LON SmartServer
 Simplest solution for small networks
 Suitable for simple networks
with simple configuration and no connections
• Standard installation tool such as LonMaker
 Lowest development cost
 Best flexibility and network documentation
• Custom installation tool
 Most customized solution
 Highest development cost
3-7
Network
Architectures
3-8
Simple Device Network
• Devices communicate with
each other directly, no head end
or master controller required.
• Network management tool is
not required after devices have
been commissioned
• A portable network management tool is required to perform
network maintenance tasks
such as adds, moves and
changes
NM Tool
Portable Network
Management Tool
3-9
Local Client Applications
• LNS database resides on same
computer as the network tool
• LNS network management tools and
Human Machine Interfaces (HMIs)
communicate with devices via network
services interface (NSI) hardware/
software



Local NSI interface over Twisted Pair,
Power Line, RF
Local IP client over IP-852
 i.LON router connects IP channel
to LONWORKS channel
 Config Server must be running on a
PC connected to IP-852 channel
Local IP client over telephone network
 Uses PPP (point-to-point protocol)
 Requires RNI
 Poor performance
LNS App(s)
LNS Server
NSI
Local Client
SNTP server may be
required if IP-852
channel is internet
IP-852
Network
LNS App(s)
Config Server
LNS Server
NIC
Local IP Client
i.LON
IP-852
3-10
Remote Lightweight
Client Applications
• Communicate with LNS Server via
IP network (not to be confused with
IP-852 channel.)
• Doesn’t have data server so can only
communicate with devices on
physical network through the
LONWORKS interface of the server
LNS App(s)
NIC
IP Network
Remote
Lightweight
Client
• Network management,
monitoring and controlling
tasks are all routed through
the LNS Server.
• Potential bottleneck in the
LNS Server if multiple
remote lightweight clients
monitoring and controlling
multiple data points
simultaneously.
LNS Server
NIC
Server
NSI
Remote Fullweight
Client Applications
3-11
• Communicate with the LNS Server PC
through any LONWORKS channel,
typically IP-852 or TP/XF-1250.
• Has data server so can communicate
directly with devices through its own
network interface (any LONWORKS
channel including IP-852).
• Network management tasks are
routed through the LNS Server.
• Monitoring and controlling tasks
are sent directly to the network.
LNS App(s)
NSI
LNS App(s)
Config Server
LNS Server
NIC
IP-852
Network
Full Client
TP/XF-1250
High Speed
Backbone
LNS Server
NIC
Server
i.LON
IP-852
Full Client
NSI
Server
Router
3-12
Telephone Connections
to the Network
HMI Tool
NM Tool
PSTN
Modem
NM Tool
NSI
SLTA-10
• SLTA (Serial LonTalk Adapter)
with modem locally installed at
network
• Modems allow the RS-232 line to
be extended through the public
switched telephone network
• LinkManager software required
by LNS application
HMI Tool
NM Tool
• i.LON 100 can also provide
remote IP connectivity with
optional internal modem
• Supports connection to an
external GSM or GPRS modem
NM Tool
PSTN
NSI
Modem
i.LON 100 with
Modem Option
3-16
Simple Web
Browser Based Client
• i.LON 100 or SmartServer web-based
client performs monitoring and control
tasks.
• Advanced web server features provide
XML, JavaScript, DHTML and SOAP
interfaces to enterprise systems.
• Customizable and simple to develop
with a easy to use HMI that can
represent or write network variable
values in graphical or text formats.
• i.LON 100 may not perform network
management tasks without access to
LNS server.
• SmartServer may perform network
management tasks in Standalone mode.
Web Browser
NIC
IP Network
i.LON
SmartServer
Web
Server
3-17
Internet/Intranet
IP Backbone
• Internet to LONWORKS
(i.LON devices) can be used to
create one network by
connecting remote locations
over IP-852 channels
• LNS Server is not required
for routing packets
• Up to 256 IP-852 devices per
channel
• IP-852 can use existing IP
infrastructure
Devices in London
Web Browser
i.LONs
IP-852
NIC
Devices in Lisbon
Intranet 1
(IP) i.LON
IP-852
Internet
Devices in New York
Intranet 2 (IP)
SNTP Server
Intranet 3
(IP)
12:10:15
Devices in Beijing
NIC
i.LONs
IP-852
Devices in Hong Kong
3-18
Monitoring/Control and
Network Management
• Network management/maintenance tasks are
routed through the LNS server
 add/remove devices and routers
Management
 change channels
and
 bind NVs
Maintenance
 adjust CPs
• Monitoring and Control applications are sent
directly to the network
 get updates (monitor network variables)
 send updates (write to network variables)
• On a remote lightweight client, monitoring,
LNS Server
and controlling tasks as well as network
management tasks are routed through the
LNS Server
Monitoring - The ability to display
real-time data about a network
Monitoring
and
Control