The standard for building services
LonWorks® technology is a standardised communication protocol which is well-established in building and industrial automation systems. Properties such as the decentralised intelligence, modular design, requirement-based interfaces and the capability to adjust to existing infrastructures makes LonWorks® an interesting option for the transfer of data in the field layer and for backbone systems.
The individual network participants, the so-called nodes, are able to exchange event-controlled data among themselves.
LonWorks® forms the platform for manufacturer independent communication in multi-service building automation systems.
More information about LON FTT10 you find unter the following link.
Typical applications of a LonWorks® infrastructure
- Heating, ventilation and climate control
- Light control
- Shading control
- Energy management, etc.
LonWorks® is available as a communications option for practically all PCD systems. PCD classic controllers are connected to the Saia PG5® COSinus operating system via IP 852 (Ethernet). LON FTT10 is also possible using a communication module, whereby each module supports max. 254 network variables. The PG5 contains a suitable LON resource configurator for configuring the LON nodes and an FBox library for commissioning, testing, transmitting and receiving network variables.
A LON options module is always required for using the LON-over IP (IP 852). A PCD7.R58x is used for memory slots M1 or M2 for PCD3.M5/M6-, PCD2.M5-, PCD1.M2- and PCD1.M0 controllers. The PCD3.R58x module is available for I/O slots.
A “LON communication module” is also required to connect the LON FTT10. This module provides PCD controllers with a LonWorks® interface but without a router function. PCD1.M2 controllers require the PCD2.F2400 module and PCD3 controllers (see supported PCD3 devices in the table belwo) the PCD3.F240 module.
External LON FTT10- / IP gateways are also required to connect FTT10 devices directly to the management system or other LON IP 852 devices, for example. In place of a router, the application program can also copy network variables on IP 852 via PCD resources from any system.
PG5 LON Configurator and FBox Library
The FBox library can be used for communication control of LON IP (PCD7.R58x) and LON FTT10 (PCD3/2.F240x) modules. The Help describes the functionality of the different FBox modules. Please note that you'll still use the PG5 LON over IP or Lon FTT10 Configurator to create LonWorks node configurations. For detailed information about the work flow, please check out the Saia Lon Manual 26-883.
System Catalogue : LonWorks Networks
|Extract||PP26-215_B0262||System Catalogue : LonWorks Networks|
LonWorks for PCD COSinus
|Manual||26-883||LonWorks for PCD COSinus|
Room Controller with LON PCD7.L611
|Manual||26-876||Room Controller with LON PCD7.L611|
LonWorks® Networks with Saia PCD
|Manual||26-767||LonWorks® Networks with Saia PCD|
Single Room Controller with LON PCD7.L610
|Manual||26-873||Single Room Controller with LON PCD7.L610|
Single room controllers based on LON
|Technical Info||PP26-341||Single room controllers based on LON|
LonIp firmware used in production
|Firmware||1.24.69/1.26.31/1.28.16||LonIp firmware used in production|
LonIp FW and coresponding PCD FW for PCD1.M2xx0, PCD2.M4x60, PCD2.M5xx0, PCD3.Mxxx0, PCD3.Mxx60
Do use at least the PG5 firmware downloader version 2.1.311 or newer (included in PG5 patch 2.1.311 or newer) to prevent the loading of the FW 1.24.xx or 1.26.xx or newer to a not compatible PCD.
|LonIP FW 1.24.69 / 1.26.31 / 1.28.16||.zip||15.41 MB||Download|
The actual COSinus FW 1.20.xx or higher for the PCD is available from the COSinus firmware page
Good to know
|More information about LON FTT10 you find unter the following link.|
Communication / LON (FTT10)
LON Work: how many variables SNVT can be used on a PCD/PCS ? (FAQ #101296)
It is depending of the PCD/PCS used, the rest of the programme and of the memory available:
PCD2.M170/M150 until1000, advised 500 -700
PCD1,PCS1 advised maximum 400-600
When Extended Memory isn't used (not advised du to the speed) we can used normally 50 - 150 SNVT.
Can I run BACnet and LON on the same PCD at the same time? (FAQ #101216)
In the system catalogue there is a schematic of a PCD connected to a BACnet/IP network which could lead to a missinterpretation. Although BACnet is supported by a PCD3 or a PCD2.M5xx0 and LON on IP will be suppored in future, it won't be possible to run both stacks on the same PCD at the same time.
Why is it not possible to run BACnet and LON at the same time?
This limitation is caused by the rather high usage of ressources (performance and memory) from both these firmware extensions. While there is no problem to run one of these firmware extensions, the currently available PCD systems do not support both firmware extensions at the same time.
It is intended to provide a solution for BACnet and LON on the same PCD but this requires a new PCD system in future.
Why is this schematics printed in the System catalogue?
The aim of this schematic is to show that both protocols are supported, but not to indicate that both protocols can be used at the same time. If the PCD is running the LON stack, the other communication could e.g. be Ether-S-Bus.
How can I realize a gateway from BACnet to LON with PCD systems?
The currently only solution is the realisation with two systems, which could e.g. be connected with Ether-S-Bus.
Why it’s not possible to make the binding with the LonMaker to a PCS1? (FAQ #101132)
If a PCS1 does use at the same time a serial communication with > 9’600 baud and the user wants to make a binding with the LonMaker then it’s possible that the binding will not succeed and on the LonMaker there is an error message:
“The device is application less or is not associated with a program record”
To solve the problem and to be able to make the binding either you have to switch off the serial communication or to use a baudrate <= 9'600 baud.
The reason of the problem is, that the PCS1 has not enough CPU power to perform simultaneously a Lon binding and a serial communication with > 9'600 baud.
How to configure a LON interface on a PCD1 / PCD2? (FAQ #101075)
The PCD must be equipped with a PCD7.F8xx module and RAM is to be mounted on the memory socket, with the "memory use" set to RAM (the binding does not work with a Flash).
The RAM Text and RAM DB have to be set to the following range:
- PCD1: 2000-2499, 2500-2599
- PCD2: 4000-4499, 4500-4999
If 1 Mbit RAM is used the user memory should soon be too small, it is recommended to use 4 Mbit RAM.
For a PCD1 we recommend to use maximal 400-600 SNVT.
For other PCD the theoretical limit is 4095 SNVT.
How to save the binding in a Flash?
Follow these steps:
¨ Bind the network using RAM on all PCD
¨ Execute an upload dBx and rebuild (all)
¨ Replace the RAM with flash on all PCD at wish
¨ Download the program again, this goes now in flash
PG5 2.0 / LON on IP
With PG5 2.1.100, why do I get the error "LONIP FAIL 1007" (FAQ #101831)
After compiling and download of a LON IP project with PG5 220.127.116.11, the error LONIP FAILED 1007 is shown in the history of the PCD and the PCD goes to halt.
This problem is due to a bug in the LONIP configurator of PG5 2.1.100.
With PG5 18.104.22.168 this problem was not yet present.
Install the patch 1 for PG5 2.1 that can be downloaded from the Support homepage in the section Software / PG5 2.1 Suite.