QuickServer Gateway (LonWorks)
QuickServer is a high performance, fully configurable, cost-effective Building and Industrial Automation gateway for integrators to easily interface devices to networks in commercial buildings and industrial plants.
System integrators worldwide have benefitted from the value of the powerful line of interoperability gateways offered by FieldServer. Now, QuickServer adds to that value by running the same robust FieldServer protocol conversion software on a highly cost-effective platform backed by the experience, engineering expertise and proven technical support that integrators have come to expect from FieldServer.
QuickServer is available in two series:
The FS-QS-1X11 Series is preloaded with two BAS drivers (one RS485 serial port, one LonWorks Port, and one Ethernet port) drivers from a choice of at least 150 Protocols. There is a basic QuickServer that can handle up to 250 points and an enhanced QuickServer that can handle 500 points.
The FS-QS-1X21 Series is preloaded with two BAS drivers (one RS232 serial port, one LonWorks Port, and one Ethernet port) drivers from a choice of at least 150 Protocols. There is a basic QuickServer that can handle up to 250 points and an enhanced QuickServer that can handle 500 points.
Each QuickServer includes browser-based tools to make it easy to set-up QuickServer and perform diagnostics including determination of status, network settings, node information, map descriptors and more. The USB flash drive also includes the Discovery utility to determine what FieldServers are on a network.
The Modbus TCP Driver allows the FieldServer to transfer data to and from devices over Ethernet using Modbus TCP Protocol. The Modbus TCP driver uses port 502. This port is not configurable. The driver was developed for Modbus Application Protocol Specification V1.1a" from Modbus-IDA. The specification can be found at www.modbus.org. The FieldServer can emulate both a Client and a Server simultaneously on the same ethernet port.
The information that follows describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer.
There are various register mapping models being followed by various vendors. To cover all these models FieldServer uses the following three Models
- Modicon_5digit – Use this format where addresses are defined in 0xxxx, 1xxxx, 3xxxx or 4xxxx format. A maximum of 9999 registers can be mapped of each type. This is FieldServer driver’s default format.
- ADU –Application Data Unit address. Use this format where addresses of each type are defined in the range 1-65536
- PDU –Protocol Data unit address. Use this format where addresses of each type are defined in the range 0-65535.
The key difference between ADU and PDU is for example if Address_Type is ADU and address is 1, the driver will poll for register 0. If Address_Type is PDU, the driver will poll for address 1.
Note 1: If vendor document shows addresses in extended Modicon (i.e. 6 digit) format like 4xxxxx then consider these addresses as xxxxx (omit the first digit) and use either ADU or PDU
Note 2: The purpose of providing 3 different ways of addressing the Modbus registers is to allow the user to choose the addressing system most compatible with the address list being used. At the protocol level, the same protocol specification is used for all three with the exception of the limited address range for Modicon_5digit.
The LonWorks driver allows the FieldServer to transfer data to and from devices using LonWorks protocol over the TP-FT/10 channel amongst others. The LonWorks FieldServers can emulate either a Server or Client.
The FS-B30, QuickServer, and SlotServer Series FieldServers have a built-in LonWorks Interface and a Fieldbus connection is available on the FieldServer.
The FS-B30 and the SlotServer can handle up to 4096 Network Variables which can be of the Standard Network Variable Types (SNVT) and/or User-defined Network Variable Types (UNVT), and the QuickServer can handle 250 Network Variables (or a limit of 500 for the enhanced model).
QuickServer Gateway (LonWorks)
- Operating Temperature: -40 to 75â„ƒ (-40 to 167°F)
- Relative Humidity: 5-90% RH non-condensing
9-30V DC or 12-24V AC
(RS-422 = 15-30V DC or 12-24V AC)
(M-Bus = 12-24V DC)
Current draw: @ 12V
- FS-QS-1010, FS-QS-12X0: 240 mA
- FS-QS-1011, FS-QS-12X1: 250 mA
- Slave: 550 mA @ 12V
- Master (1 Slave): 580 mA @ 12V
- Master (64 Slave): 980 mA @ 12V
- Dimensions (WxDxH): 4.5x2.9x1.6 in. (11.5x7.4x4.1cm
- Weight: 0.4 lbs (0.2 Kg)
- Input voltage: 24 V DC nominal: 10-30V DC
- Capacity: 250 points FS-QS-10X1. (500 points FS-QS-12X1)
- Table, Wall or DIN rail mount
- Baud: 4800, 9600, 19200, 38400, 57600, 115200
- Start Bit: 7, 8
- Stop Bit: 1, 2
- Parity: Even, Odd, None
LonMark Certification on the QuickServer FS-QS-1XX1-XXXX
- SPID: 80:00:95:46:00:84:04:01
- Profiles: 0000 - Node object (1), 0001 - Open Loop Sensor Object (5), 0003 - Open Loop Actuator Object (5)
- Ethernet: 1, 2
- Parity: 10/100 BaseT
- TUV Approved: to UL 916, EN 60950-1, EN 50491-3 and CSA C22.2 standards
- BTL Mark:
- LonMark Certified: (FS-QS-1011 and FS-QS-12X1)
- RoHS Compliant
- GOST-R Certified
- CE and FCC
FST - Lonworks Approvals
The following FieldServer Platforms are LonMark Certified:
The FieldServer provides the capability of defining multiple functional blocks, but only a single LonMark object. The user can create multiple functional blocks or a LonMark object by filling out the Node SelfDocumentation String and the respective Network Variable Self-documentation String fields in the FieldServer configuration file.
Standards & Certification
LonWorks became and ANSI standard in 1999, and subsequently became a widely adopted global standard. The standard is supported and maintained by LonMark International. Standards include:
LonMark International is responsible for certification, education, and promotion of interoperability standards for the benefit of manufacturers, integrators, and end users. LonMark International has developed extensive product certification standards and tests to provide the integrator and user with confidence that products from multiple manufacturers can work together.
Sierra Monitors FieldServer has more LonMark Certified gateways for integrators and OEMs that carry the LonMark logo than any other gateway manufacturer. For more information about our LonMark Certified products, visit the LonMark International Product Certification Directory.
Certified Products are listed here:
https://www.lonmark.org/products/search check for updates
|FS-B2011 Serial/Ethernet/LonWorks® Gateway||Sierra Monitor Corporation||3.4||TP/FT-10|
|FS-B3510 Serial/Ethernet/LonWorks® Multiport Gateway||Sierra Monitor Corporation||3.4||TP/FT-10|
|FS-B4011 Serial/Ethernet/LonWorks® 10-port Gateway||Sierra Monitor Corporation||3.4||TP/FT-10|
|ProtoCarrier/ProtoCessor FPC-CD2 Daughter Card Gateway for OEMs||Sierra Monitor Corporation||3.4||TP/FT-10|
|ProtoCessor FPC-F04 Embedded Gateway Module for OEMs||Sierra Monitor Corporation||3.4||TP/FT-10|
|ProtoNode LER External Protocol Gateway for OEMs||Sierra Monitor Corporation||3.4||TP/FT-10|
|QuickServer FS-QS-1XY1 Gateway for LonWorks®||Sierra Monitor Corporation||3.4||TP/FT-10|
|Liebert SiteLink-12 LonWorks® Adapter||Sierra Monitor Corporation||3.3||TP/FT-10|
|SlotServer LonWorks® Open Interface||Sierra Monitor Corporation||3.3||TP/FT-10|
|FS-B2011-01 Water Temp Sensor||Sierra Monitor Corporation||3.2||TP/FT-10|
|Cleaver Brooks Adapter for LonWorks®||Sierra Monitor Corporation||3.3||TP/FT-10|
|Discharge Air Controller||Manufacturer||Version||Transceiver|
|FieldServer Data Aire DAP Adapter for LonWorks®||Sierra Monitor Corporation||3.3||TP/FT-10|
|FieldServer Caterpillar EMCP II Adapter||Sierra Monitor Corporation||3.3||TP/FT-10|
|FieldServer Kohler 550 Adapter||Sierra Monitor Corporation||3.3||TP/FT-10|
Modbus - MK10 and 32 Bits Numbers
Scaling in Modbus
Modbus does not provide a method for transporting large or Floating Point numbers or a mechanism for scaling analog values. A 16 bit word can only contain values in the range 0-65535. Only whole numbers are permitted. To work around this many server device manufacturers use multipliers and document them in their manuals. For example, to report a temperature of 58.5 the device reports a value of 585, and makes a note in the manual that the master should scale by 10. This scaling is achieved by adopting a convention between the client and the server.
What about large numbers > 65535
Modbus does not provide a mechanism but 3 important schemes are widely used.
Long Integers – Two consecutive 16 bit words are interpreted as a 32 bit long integer.
MK10 values – Two consecutive words are used. The 1st reports the number of units and the 2nd reports the number of 10,000’s.
Floating Point Numbers – Two consecutive words are used and a scheme. These schemes are conventions and not all servers or clients support them.
The protocol does not identify these big numbers. Only the vendor docs do.
What we mean by this is – if you look at the byte stream in a Modbus message there is no way of telling whether you are looking at two consecutive 16 bit words, or two consecutive words that should be interpreted as floating point, long or MK10 formats. Because of this you always have to look to the vendor docs.
Modbus - Reading Vendor Modbus Maps
Reading Vendor Modbus Maps
If you are reading the documentation for sensor blocks, valves, and other devices, you must keep in mind that some vendors may document their hardware in different ways.
According to the Modbus standard, addresses are simply integers from 0 to 65,535 with the different address ranges being referred to as coils, holding registers, etc. However, some vendors will document their hardware using numerical prefixes which are not actually part of the Modbus address. This originated from some models of PLCs which used the Modbus communications protocol, and which also used numerical prefixes in their internal data table. This is similar to using “I”, “Q”, “V”, etc. as address prefixes in IEC type PLCs.
However, it is important to remember that these numerical prefixes are documentation methods and are not part of what the Modbus protocol itself sends as part of the messages. A difference in documentation methods does not affect the compatibility of the protocol itself.
These prefixes are they mentioned anywhere in the Modbus standard, but the following shows how they are typically used in documentation based on this older convention:
- 0xxxx – Coils.
- 1xxxx – Discrete inputs.
- 3xxxx – Input registers.
- 4xxxx – Holding registers.
Note that there is no 2xxxx address prefix.
In addition to numerical prefixes, some documentation will refer to protocol addresses (addresses start at 0), while other documentation will refer to data model addresses (addresses start at 1). That is, the first holding register may be 0 or 1 (or 40000 versus 40001 using prefixes). However, this has no bearing on what gets sent over the wire as a Modbus message. For a Modbus protocol message, the lowest address is always “0”, not “1”.
Modbus - Protocol Specifications
Modbus - Flavors of Modbus
Flavors of Modbus
Active Master-passive Slave
Supported by FieldServers, QuickServers, CAS gateways
Similar to ModbusRTU but for each byte in an RTU message, there are 2 bytes in an ASCII message. The 2 bytes are the humand readable form of the single hex byte.
Eg RTU byte = 0x03 (Hex). ASCII bytes = ‘0’ and ‘3’ ie 0x30 and 0x33
Active Master-passive Slave
Supported by FieldServers, QuickServers
Modbus had the limitation of a max of 9999 items of each type. Ie only 9999 holding registers. However the protocol message allows 65k items to be addressed. JBUS allows all 65k items to be read/written. Other than that it is identical to RTU
Active Master-passive Slave
Supported by FieldServers, QuickServers, CAS gateways
Uses TCP/IP connection based Ethernet communications
Encapsulates RTU messages and adds a header.
A single slave can respond to multiple masters
Many slaves ignore the NodeID field in the message.
Supported by FieldServers, QuickServers, CAS gateways
Proprietary coax networking layer
Supported by FieldServers, CAS gateways
Lonworks - LonWorks Protocol
A set of services is offered by the LonWorks Protocol that enables all devices in the network to transmit and receive messages to and from other devices via their application program— requiring no acquaintances with network topology or the other devices’ names, addresses, or functions. Besides, LonWorks Protocol can be made to deliver authentic, high priority messages within delimited transaction times. Moreover Network management services allow remote network management tool’s interaction with devices over the network; making them capable to reconfigure network addresses and parameters, download application programs, report network problems and Start/stop/reset device application programs. Consequently it’s relatively easy to employ LonWorks network over any medium, including power line, twisted pair, radio frequency (RF), infrared (IR), coaxial cable, and fiber optics.
Lonworks is another communications protocol useful in building automation applications. The protocol was developed by the Echelon Corporation in the late 1990s. Lonworks originally transformed from Echelon’s earlier “Lontalk”, and was submitted to the American National Standards Institute (ANSI) for acceptance. Lonworks was designed on a low bandwidth platform for networking devices through powerlines, fiber optics, and other media.
The entire Lonworks package consists of the following components by the Echelon Corporation:
- Lonworks – communications protocol (ANSI/EIA 709.1, and others).
- Echelon’s “Neuron” chip (Three 8-bit inline processor). Two are used by Lonworks, and one as a general application processor.
- Twisted-pair and/or powerline transceivers to transmit Lonworks protocol.
- LNS Network Operating System is the required software.
- Internet connectivity through Standard Network Variable Types (SNVTs) or with LonMark profiles.
- LonMaker allows interoperability among devices.
Lonworks has various advantages and disadvantages. The advantages include:
- Less architecture at the device level.
- Numerous developers of Lonworks products in the market.
- Lonworks devices are close to “plug & play” ability, but still far from achieving interconnectivity in today’s computers using Microsoft Windows.
The disadvantages of Lonworks are presented in the following list:
- Less architecture causes controlled devices and variables to be connected to a separate control device. Most designers do not recommend this type of architecture because network interruptions could eventually produce system failures.
- The protocol is proprietary, and not truly open to the public. Only actual members, mostly manufacturers are included in standard development(s).
- Extensions within Lonworks are allowable only through the LonMark Consortium.
- Hardware specific, and requires the Neuron chip for network movement of the protocol.
Lonworks - LonWorks Applications
Amongst the extensive range of LonWorks technology applications the vital nine are listed below:
- Semiconductor manufacturing
- Lighting control systems
- Energy management systems
- Heating/ventilation/air-conditioning systems
- Security systems
- Home automation
- Consumer appliance controls
- Public street lighting, monitoring, and control
- Gas station control
Lonworks - Building Control Networks
A P2P (peer to peer) architecture is undoubtedly the preeminent way to build control networks. Being exclusive of a single master control, P2P-based control network confers high reliability and high performance to its users. Unlike other control networks, in P2P architectures, there is absolutely free and open communication between network devices which automatically puts a stop to the system collapses that could occur whenever the master stops working.
Lonworks - Neuron
A processor identified as Neuron chip embracing three 8- bit inline processors designed by Echelon is well optimized for control network devices. Out of three processors: two are committed for the communications protocol and one is a general-purpose applications processor. Standardization of the variables used to illustrate physical things to LonWorks is maintained by LonMark International and each standard is known as Standard Network Variable Types (SNVTs). LNS Network Operating System is a mandatory software component of open control systems which ensures an open environment for extending, maintaining, and managing LonWorks based system
Lonworks - Introduction
LonWorks is not just a protocol or physical layer for communication but an exclusively designed networking technology platform to install, maintain, monitor and sense various automation and control applications. Essentially LonWorks was established for a range of automation functions within buildings such as lighting and HVAC. Invented by Echelon Corporation, the fundamental communications platform, twisted pair signaling technology, power line signaling technology, and IP tunneling method constitutes a global standard documented ISO/IEC 14908.
Lonworks - Software - XIFdump
Another useful utility is XIFDUMP. It is a report generator (DOS), and it allows you to generate reports (text file) from a XIF files.
Lonworks - Software - NodeUtil
What happens if you need to learn about a Lonworks network and it devices but you haven’t been provided with the database or if you don’t have LonMaker?
NodeUtil is a Lonworks utility that can be used to explore Lonworks networks and devices without having LonMaker. All you need is a device such as an Echelon U10/U20 USB Network Interface.
Using NodeUtil you can discover devices , learn about the Domains, SubNets, NodeID’s. You can also upload the XIF file from specific nodes.
More Nodeutil Downloads available: HERE
Lonworks - Software - Lonmaker
LonMaker is a Windows GUI based network/device management tool for Echelon LonWorks. It can be used for initial network setup and functioning as a management console on a completed network.
Lonworks - Why are Lonworks communications so good
The communications between all Lonworks devices is done by means of a proprietry chip (The Neuron chip) made according to one design by one company according to one standard which it wrote on its own. It’s obvious that there are so many less aspects of the data communications process that can go wrong when there is a single entity involved. When a device vendor implements a Lonworks System Interface he simply has to implement the application layer of the data communication process. For almost all other protocols the device vendor must implement the physical layer, data link layer, the Network Layer, The transport Layer, The Session Layer, the Presentation Layer and the Application Layer. You can see how many more areas of risk there are.
When Echelon released the standard, their license terms required anyone who implements it to implement the full standard. The fact that other vendors can’t cherry pick features and services means that even when implemented by other vendors you still have the same strong chance of success.
Lonworks - Jargon Watch
Lonworks – a wide ranging term generally applied to describe the whole technology developed by Echelon. It is used frequently and ambiguously.
LonTalk – A registred trademark belonging to Echelon. They use it as the name of the protocol used for data communications in a Lonworks system. Ie. It is the brandname protocol. Echelon released this protocol so it could be adopted as a standard – ANSI-approved standard EIA/CEA-709.1-A-1999 – SO/IEC Standard 14908 or European standard EN14908.
Lonworks - How to - Commissioning and Binding
How to Commission and Bind using Lonmaker. CAS can configure Lonworks gateways so Commissioning and Binding can be avoided. Call our Tech Sipport for more info.