LONWORKS Network Design

LONWORKS Network Design
Overview

Welcome! 1-2

Course Objectives 1-3 PLAN THE NETWORK Identify Architectures 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 Be sure to find out if there are any special concerns or issues to cover for this audience. The design process in terms of order of operation will vary as a function of the installation scenario – This is a common order that we will follow in this course. We will refer back to the flow chart at the beginning of most chapters. Select Network Components IMPLEMENT THE NETWORK Install Physical Network Program Network Commission Network TEST AND OPTIMIZE Test and Verify Network Optimize Network DOCUMENT AND MAINTAIN Document Network Maintain Network

LONWORKS Technology Overview

Objectives 2-2 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®) In this section, get students to talk about what they know about the basics of LonWorks technology. They should already be familiar with the basics of LonWorks networks and should remember some of the terminology. Take the opportunity in this section to make the learning interactive. Ask lots of questions so YOU (the instructor) can learn what the students know and don’t know.

Control Networks 1st Generation
2-3 1st Generation Master/Slave 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 LonWorks is said to be a third generation control system Polling increases network traffic Centralized Architecture Centrally located processor No integrated intelligence Single point of failure

Control Networks 2nd Generation
2-4 2nd Generation Decentralized Master/Slave 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 Centralized control reduced single point failure but did not eliminate it Compared to centralized architecture Networked PLCs Distributed intelligence Centrally located processor Single point of failure reduced

Control Networks 3rd Generation
2-5 3rd Generation Peer-to-Peer 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 Event driven – if an event happens it goes on to the network, does not need to poll. Can remove after installation complete 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

The Origins of LONWORKS Technology
2-6 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 ANSI/CEA 709.1B EN LonWorks refers to “technology” While explaining Apple’s networking “roadmap” (early days of computer networks) to new CEO John Scully, Mike realized there was a hole in the plan –control of devices over network.

Benefits of the LONWORKS Platform
2-7 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 protocol is media independent LONWORKS tools operate on multiple computer platforms Multi-industry standards group ensure interoperability – LONMARK International Flexibility for changes and expansion, very easy to add & interchange devices Can be used for almost any type of control/ operation of any type of equipment Overall result – Lower costs Decreased complexity Flexibility for changes and expansion More options

Open Systems To ensure an open interoperable system is delivered
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 VAV, T-Stat are applications

LONMARK International Making Plug-and-Play A Reality
2-9 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 and related standards.

Who is LONMARK International?
2-10 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 refers to trade association symbol Membership open to any manufacturer, distributor, engineer, system integrator, or end-user interested in the development, specification, and use of open, interoperable products utilizing ANSI/CEA and related standards

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 SFP – LonMark site has this data on their site

LON Speak LONWORKS LonTalk LNS LONMARK LonMaker LonPoints
Channel – communication media Network Variable – NV application specific data shared among devices and tools Binding- network variable connection Configuration property – defines device/object/NV behavior Functional Profile – A definition created by LonMark to describe how the combination of network variables and configuration properties support device function. Functional Block – An instance of a functional profile present on a device. Plug-in – application that provides a graphical user friendly way to configure devices XIF – A text file listing functional blocks, network variables and configuration properties to be used in designing a network without having physical devices present. SFPT/SFP – standard functional profile template defined by LonMark SNVT – standard network variable type defined by LonMark UNVT – user network variable type defined by manufacturer SCPT – standard config property type defined by LonMark A-3 Use simple one sentence descriptions. Details on following slides. LonWorks – generic term to describe the technology, overall encompassing system. LonTalk – communication protocol, the language. LNS – Lonworks Network Services – network operating system, database tools LonMark – interoperability organization, organization that certifies devices LonMaker – network management tool design/install/manage, network integration tool LonPoints – Echelon’s intelligent devices, no longer sold Network Integrator – contractor that delivers complete control solution to end user, he who creates the system Neuron Chip– 3 microprocessors on one chip that implements the LonTalk protocol, they do all the work Node – intelligent device, anyhting with a neuron chip, speaks on LonWork network i.LON –Echelon’s family of internet enabled LonWorks devices that provide routing, interface, web services, data logging, scheduling, and alarming functionality. IP product Domain/Subnet/Node – device’s logical address (city/street/address) Client/Server – allows multiple users running LNS tools such as LonMaker on separate computers to access the LNS server simultaneously, how LNS is allowed to communicate. Channel – what you talk over Network Variable – output of a device Binding – making a connection Configuration Property – making adjustments, doing set points Functional Profile – definition of a device, the network variables, configuration properties, defaults, and power-up behaviors Functional Block – instance of a profile Plug-In - manufacturer created profiles XIF – definition of everything that makes up a device, file tells network-management tools how to communicate and recognize a device SFP – Standard Functional Profile SNVT – Standard Network Variable Type UNVT – User Network Variable Type (manufacturer, provides resource of device information) SCPT – Standard Configuration Property Type UCPT – User Configuration Property Type 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

LONWORKS – Distributed Control Intelligence
2-13 Puts the control intelligence inside the device where the control happens Each device may subdivide multiple 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 Flat LonWorks architectures allow devices to communicate with each other without passing data through central controller Flat LonWorks architectures devices can communicate with each other without passing data through central controller

LONWORKS Network Program
2-14 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 The network in the drawing is without function. Don’t try to understand what it does.

Addressing and Routing
LonTalk Protocol 2-14 Communications protocol - language of LONWORKS Open and published standard available to anyone ISO/IEC (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 Physical Connection Media Access Addressing and Routing Message Service Network Management Network Variables Neuron C Program 1 2 4 5 6 7 3 Physical Data Link Transport Session Presentation Application Network Physical Media Physical Electrical Interconnect twisted pair, power line, radio frequency, coax, fiber optic Link Media Access and Framing CRC Error checking, Collision Avoidance, Data Encoding Network Destination Addressing Addressing Routers Transport End-to-end Reliability Acknowledged & unacknowledged Session Remote Actions Authentication, Network Interface and Management Presentation Data Interpretation Network varaibles Application Application Compatibility SNVT

Addressing and Routing
LonTalk Standards 2-15 ISO/IEC Open Data Communication in Building Automation, Controls and Building Management ANSI/CEA B Control Network Protocol Specification EN :2005 GB/Z Control Network LonWorks Technology Specification IEEE 1473 Standard for Communications Protocol Aboard Trains Physical Connection Media Access Addressing and Routing Message Service Network Management Network Variables Neuron C Program 1 2 4 5 6 7 3 Physical Data Link Transport Session Presentation Application Network Physical Media

ISO/IEC 14908 and Related Control Standards
2-16 International Electrotechnical Commission International Organization for Standardization ISO/IEC Open Data Communication in Building Automation, Controls and Building Management – Control Network Protocol Because "International Organization for Standardization" would have different acronyms in different languages ("IOS" in English, "OIN" in French for Organisation internationale de normalisation), its founders decided to give it also a short, all-purpose name. They chose "ISO", derived from the Greek isos, meaning "equal". Whatever the country, whatever the language, the short form of the organization's name is always ISO. provides peer to peer and master/slave control strategies ,125kbit/s between multiple nodes all information necessary for power line communication Internet protocol communication ISO/IEC Part 1: Protocol Stack ANSI/CEA B-2000 EN :2005 GB/Z ISO/IEC Part 2: Twisted Pair Communication ANSI/CEA-709.3 EN GB/Z ISO/IEC Part 3: Power Line Channel Specification ANSI/CEA-709.2 EN GB/Z ISO/IEC Part 4: IP Communication ANSI/CEA-852 EN GB/Z

LONWORKS Network Elements
2-17 Channel Network Tool Device Channel 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 Note that controllers, actuators, and applications specific devices can be LonMark Certified

Network Integration/ Management Tools
2-18 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 LM Exam Common network management tasks - binding, commissioning, and device configuration Required for non-self installed networks A primary goal of all integration tools – assign logical addresses Provide device with applications, logical addresses and links to device variables Also referred to as Network Integration Tools

Network Variables LM Exam
2-19 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 LM Exam NVs create the logical interface of the node to the network SNVT includes size, range, resolution and scaling for each field Note that the SNVT types given here just randomly chosen examples. SNVTs provide a convenient way to exchange data between two or more points. We will use network variables throughout this course to accomplish a distributed network control algorithm.

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 UCPTs (user configuration property types) are manufacturer defined

Functional Blocks 2-21 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 LonMark Functional profiles describe in detail the application-layer interface—including the network variables, configuration properties, defaults, and power-up behaviors—required on LonMark devices for specific, commonly used control functions.

LONMARK Standard Functional Profiles - SFP
2-22 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 LM Exam Functional profile defines minimum NV and CP requirements Certified device must contain one or more LonMark profiles Required to become LM certified under 3.4 or later – primary function using one or more LM profiles Mandatory NVs and CPs for specific functions aid interoperability Device’s primary function must be based on SFP to be certified Every profile has at least one NV or CP Data types and network direction of mandatory input and output NVs Ensure interoperability

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

Demonstration: LONWORKS Resources
LONMARK Web site SNVT/SCPT master list Interoperability guidelines Functional profiles Case study examples

LNS® – LONWORKS Network Services
2-25 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 LM Exam LNS – LonWorks Network Services Provides unified functions to a Windows program Echelon Corporation's LNS provides directory, installation, management, monitoring, and control services required for open LonWorks networks. LNS is a platform that allows multiple LNS applications to interoperate on the same personal computer (PC) or on multiple PCs on the same network. See also LonWorks Network Services.

Local Client Application(s) Remote Client Application(s)
LNS Server 2-26 Provides network services Network installation and configuration Network maintenance and repair System monitoring and control 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 Runs on PC and provides database and unified functions for accessing LW network LNS is a client-server operating system with a single LNS Server that supports many interoperating client applications. The LNS Server can run as a standalone application on a PC attached to the network, or it can run on the same PC as the Network Management tool. Clients on other PCs (called remote clients) can log into the LNS Server to access the shared LNS database. Network Management tools use the client-server capabilities of LNS to allow multiple Network Management tools running on different PCs to simultaneously access the same LNS Server. This capability allows multiple users to work at the same time on a single network. Local Client Application(s) LNS Tool LNS Plug-In Remote Client Application(s) LNS Tool LNS Plug-In Remote Access LNS Server Utility LNS Server Database LONWORKS Network

Local Client Application(s) Remote Client Application(s)
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. 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. Local Client Application(s) LNS Tool LNS Plug-In Remote Client Application(s) LNS Tool LNS Plug-In Remote Access LNS Server Utility LNS Server Database LONWORKS Network

Summary and Review Network variable Configuration properties
2-28 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 Network variable Configuration properties LNS LonWorks Network Services 7 (seven) SFP – Standard Functional Profile Standard Network Variable Type, Standard Configuration Property Type

Selecting Network Architectures and Topologies

Objectives Describe the steps for creating a network design
3-2 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 PLAN THE NETWORK Identify Architectures 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 Select Network Components IMPLEMENT THE NETWORK Install Physical Network Program Commission Network TEST AND OPTIMIZE Test and Verify Network Optimize Network DOCUMENT AND MAINTAIN Document Network Maintain Network

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?

Job Aid – Network Design Plan Worksheet
3-5 Begin to design your network with the Network Design Plan Worksheet Note that when looking at the worksheet on the following page, many of the items that are not clear yet will become clear later In the course NSI Network Services Interface TP/FT Free topology/twisted pair PCC-10 formerly PCMCIA pc card PCLTA-10 ½ size ISA card SLTA-10 RS232 port

Installation Options Interoperable Self-Installation (ISI) Lowest cost
3-6 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

Network Architectures
3-7 Network Architectures

Simple Device Network 3-8 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 manage-ment tool is required to perform network maintenance tasks such as adds, moves and changes NM Tool Portable Network Management Tool

Local Client Applications
3-9 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 NSI LNS App(s) LNS Server Local Client SNTP server may be required if IP-852 channel is internet LNS App(s) Config Server LNS Server Local IP Client IP-852 Network i.LON IP-852 NIC

Remote Lightweight Client Applications
3-10 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 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. LM Exam Lightweight client needs IP connection to LNS Does not have its own data server LNS App(s) Remote Lightweight Client LNS Server NSI NIC IP Network Server

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. LM Exam Fullweight clients use its own LonWorks interface and bus connection Client PC has LNS client and data server NSI LNS App(s) Full Client LNS Server Server TP/XF-1250 High Speed Backbone Router NIC LNS App(s) Full Client Config Server LNS Server NIC Server IP-852 Network i.LON IP-852

Telephone Connections to the Network
3-12 Modem SLTA-10 PSTN NM Tool NSI HMI Tool 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 NM Tool NSI Modem PSTN HMI Tool i.LON 100 with Modem Option i.LON 100 can also provide remote IP connectivity with optional internal modem Supports connection to an external GSM or GPRS modem

Simple Web Browser Based Client
3-16 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 IP Network NIC Web Server i.LON SmartServer

Internet/Intranet IP Backbone
3-17 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 i.LONs IP-852 i.LON Devices in London Devices in Lisbon Devices in Beijing Devices in Hong Kong Devices in New York Intranet 3 (IP) Intranet 1 Intranet 2 (IP) NIC Internet SNTP Server 12:10:15 Web Browser LM Exam Significant advantage of IP-852 – use existing of IP infrastructure

Monitoring/Control and Network Management
3-18 Network management/maintenance tasks are routed through the LNS server add/remove devices and routers change channels bind NVs 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, and controlling tasks as well as network management tasks are routed through the LNS Server LM Exam (note entire monitoring paragraph) Monitoring - The ability to display real-time data about a network Web based – UI that allows browser to access Web server allows data to be displayed to an Internet browser in HTML format. Note that while database is not required for monitoring and control, server needs to be present for LonMaker LNS Server Monitoring and Control Management and Maintenance Monitoring - The ability to display real-time data about a network

LONWORKS Network Design

Similar presentations

Presentation on theme: "LONWORKS Network Design"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

LONWORKS Network Design

Similar presentations

Presentation on theme: "LONWORKS Network Design"— Presentation transcript:

Similar presentations

About project

Feedback