Echelon SmartServer 2.2 SR5/SP5 ReadMe

Release 4.09.018, December 2, 2016

Copyright © 1998 – 2016 Echelon® Corporation
All Rights Reserved

1     Introduction

This document describes SmartServer 2.2 SR5/SP5.  You can apply SmartServer 2.2 SR5/SP5 to update previous SmartServer 2.2, SmartServer 2.1, and SmartServer 2.0 installations to the SmartServer 2.2 SR5/SP5 software.  See Installing SmartServer 2.2 SR5/SP5 for instructions on installing the update and verifying that it has been installed.

Additional information and updates, including updates to this document and other SmartServer documentation, service packs, and critical software updates, may be available at  The latest documentation, service packs, and updates may not be included with your SmartServer.  See Echelon’s Knowledge Base at for answers to frequently asked questions.

SmartServer 2.2 SR5/SP5 is compatible with 64-bit and 32-bit versions of Windows 10, Windows 8.1, Windows 8, and Windows 7, and is also compatible with 32-bit versions of Windows XP.  To provide full functionality, the SmartServer software must be used with Microsoft Internet Explorer 8 or newer, Google Chrome 46 or newer, Mozilla Firefox 41 or newer, or iOS 9 Safari or newer.  If you are using a SmartServer with an LNS® Server, OpenLNS Server, IzoT® Net Server, the LonMaker® Integration Tool, the OpenLNS Commissioning Tool, or the IzoT Commissioning Tool, you must be using the latest releases of each.

2      Contents

1        Introduction. 1

2        Contents. 1

3        Release Identification. 2

4        Installing SmartServer 2.2 SR5/SP5. 4

5        Improvements. 5

5.1         Improvements in SmartServer 2.2 SR5/SP5. 5

5.2         Improvements in SmartServer 2.2 SR4/SP4. 5

5.3         Improvements in SmartServer 2.2 SP3. 6

5.4         Improvements in SmartServer 2.2 SR1/SP1. 7

5.5         Improvements in SmartServer 2.2 Update1. 8

5.6         Improvements in SmartServer 2.0 SP4 / SmartServer 2.2. 8

5.7         Improvements in SmartServer 2.0 SP3. 10

5.8         Improvements in SmartServer 2.0 SR2/SP2. 11

5.9         Improvements in SmartServer 2.0 SP1. 11

6        Fixes. 12

6.1         Fixes in SmartServer 2.2 SR5/SP5. 12

6.2         Fixes in SmartServer 2.2 SR4/SP4. 13

6.3         Fixes in SmartServer 2.2 SP3. 14

6.4         Fixes in SmartServer 2.2 SP2. 15

6.5         Fixes in SmartServer 2.2 SR1/SP1. 15

6.6         Fixes in SmartServer 2.1 SR1. 16

6.7         Fixes in SmartServer 2.0 SP4 / SmartServer 2.2. 16

6.8         Fixes in SmartServer 2.0 SP3. 17

6.9         Fixes in SmartServer 2.0 SR2/SP2. 19

6.10       Fixes in SmartServer 2.0 SP1. 21

6.11       Fixes in SmartServer 2.0. 23

7        Known Problems and Workarounds. 24

7.1         Slow Commissioning for Street Light Networks. 24

7.2         Incorrect Offline Reports for Street Light Networks. 25

7.3         6-Byte Authentication Keys Fail with the CRD 3000. 25

7.4         Commissioning Devices with Changeable-Type NVs. 25

7.5         Persistent Synchronization Error Message. 25

7.6         Misleading Alarm Notifier Error Message. 25

7.7         Analog Functional Block (AFB) Reset Error 26

7.8         Disabled Security Web Page Cannot Be Enabled. 26

7.9         Cellular Carrier Network Incompatibility. 26

7.10       Using a Duplicate IP Address Range for Different Interfaces. 26

7.11       Misconfigured Heartbeats on Local NVs. 26

7.12       LON Connection Failure with Uncommissioned iLON App. 27

7.13       Web Server Security & Parameters Help Menu Fails on Windows 7. 27


3      Release Identification

This document applies to SmartServer 2.2 SR5/SP5 (Release 4.09.018).  To determine which release of the SmartServer software you have installed on your computer, follow one of the following procedures:

·        For Windows 10, type Apps & Features in the Search box, press Enter to open Apps & Features, and then click Echelon SmartServer 2.2 SR5/SP5 Software.  If the Version column is not displayed, right click the list header, select More, and then select Version to add the Version column.

·        For Windows 8.1, Windows 8, and Windows 7, click the Start button, type Programs and Features in the Search box, press Enter to open Programs and Features, and then click Echelon SmartServer 2.2 SR5/SP5 Software.  If the Version column is not displayed, right click the list header, select More, and then select Version to add the Version column. 

·        For Windows XP, open Add or Remove Programs in Windows Control Panel, and then click Echelon SmartServer 2.2 SR5/SP5 Software.  Click the Click Here for Support Information link.

To determine which release of the SmartServer firmware you have installed on your SmartServer, see the Firmware Version property in the Setup ‑ System Info Web page as described in the SmartServer 2.2 User’s Guide in Chapter 3, Configuring and Managing the SmartServer, in the subsection Viewing System Information and Performance, or by typing show in a SmartServer console window. 

The following table summarizes the SmartServer and i.LON 100 e3 plus release history, with SmartServer 2.2 SR5/SP5 in bold:




i.LON 100 e3 plus


April 2008

i.LON 100 e3 plus SP1


December 2009



January 2008

SmartServer SR1


March 2008

SmartServer SR2 and SP2


October 2008

SmartServer 2.0


October 2009

SmartServer 2.0 Update 1


January 2010

SmartServer 2.0 SP1


August 2010

SmartServer 2.0 SR2 and SP2


February 2011

SmartServer 2.0 SR2 and SP2 Update 1


July 2011

SmartServer 2.0 SP3


May 2013

SmartServer 2.1 Firmware (streetlight system use only)


October 2010

SmartServer 2.1 Firmware SR1 (streetlight system use only)


November 2012

SmartServer 2.0 SP4 / SmartServer 2.2


October 2013

SmartServer 2.0 SP4 / SmartServer 2.2 Update 1


December 2013

SmartServer 2.2 SR1/SP1


September 2014

SmartServer 2.2 SP2


March 2015

SmartServer 2.2 SP3


November 2015

SmartServer 2.2 SR4/SP4


March 2016

SmartServer 2.2 SR5/SP5


December 2016

4      Installing SmartServer 2.2 SR5/SP5

You can update any prior release of SmartServer 2.2, SmartServer 2.1, or SmartServer 2.0 to SmartServer 2.2 SR5/SP5 by installing SmartServer 2.2 SR5/SP5 DVD or SmartServer 2.2 SR5/SP5 download image.  Prior releases are SmartServer 2.2 SR4/SP4, SmartServer 2.2 SP3, SmartServer 2.2 SP2, SmartServer 2.2 SR1/SP1, SmartServer 2.2 Update 1, SmartServer 2.2, SmartServer 2.1 SR1, SmartServer 2.1, SmartServer 2.0 SP3, SmartServer 2.0 SR2/SP2, SmartServer 2.0 SP1, and SmartServer 2.0. 

SmartServer 2.2 SR5/SP5 is available on a DVD or as a free download at To install the service pack you must have a prior release of the SmartServer 2.2, SmartServer 2.1, or SmartServer 2.0 software installed on your computer.  To upgrade the i.LON 100 e3 Plus or SmartServer 1.0 software, you can purchase a license for the SmartServer 2.2 Software and the software will be provided to you as a software download.  The SmartServer 2.2 SR5/SP5 software will not run on hardware releases prior to the i.LON 100 e3 Plus due to the smaller memories of the prior hardware releases.

To install the SmartServer 2.2 SR5/SP5 software, follow these steps:

1.      If you are installing the SmartServer 2.2 SR5/SP5 software from a SmartServer 2.2 SR5/SP5 DVD, insert the DVD into your DVD drive.  If your computer does not have a DVD drive, insert the Echelon SmartServer 2.2 SR5/SP5 DVD on a network accessible computer that has a DVD drive and copy the files on the DVD to a shared network drive.  If the SmartServer 2.2 SR5/SP5 setup application does not start immediately, open the setup.exe file on the root directory of the Echelon SmartServer 2.2 SR5/SP5 DVD.

If you are installing SmartServer
2.2 SR5/SP5 from a file that you downloaded from the Echelon website, double-click the downloaded file in Windows Explorer to extract all the files.  Click OK when all the files are extracted.  The SmartServer 2.2 SR5/SP5 setup application will start automatically.

2.      The Echelon SmartServer 2.2 SR5/SP5 setup application main menu appears.

3.       Click Install Products.  The Install Products dialog appears.

4.       Click Echelon SmartServer 2.2 SR5/SP5 Software The Echelon SmartServer 2.2 SR5/SP5 Software installer appears.

5.      Follow the steps of the installation wizard.  If you have an existing installation of the SmartServer 2.2, SmartServer 2.1, or SmartServer 2.0 software, the installation will automatically update it to SmartServer 2.2 SR5/SP5.  See Chapter 2 of the SmartServer 2.2 User’s Guide for follow-along information on installing the SmartServer 2.2 software.

6.      Update the firmware in your SmartServers to the SmartServer 2.2 SR5/SP5 firmware.  See Upgrading the SmartServer Firmware in Chapter 2, Using the i.LON AdminServer of the Echelon Enterprise Services 2.2 User’s Guide for details on how to update the firmware.

5      Improvements

5.1    Improvements in SmartServer 2.2 SR5/SP5

5.1.1     Support for Echelon Plug-n-play Provisioned Networking

The SmartServer software now supports Plug-n-play Provisioned Networking (PPN) for Echelon’s PL Outdoor Lighting Controllers implementing LonMark Smart Luminaire Controller (35.14) profile. (ILE-7801)

5.1.2     Support for Echelon LonTalk Device Discovery with Filtering based on Location Index

The SmartServer software now supports LonTalk device discovery with filtering based on location index to improve scalability and maximum network sizein power line networks.  (ILE-7941)

5.1.3     Support for Firmware Download to Series 6000 Processors

The SmartServer software now supports downloading firmware to Series 6000 devices including devices based on the Echelon FT 6050 Smart Transceiver.  (ILE-7900)

5.2    Improvements in SmartServer 2.2 SR4/SP4

5.2.1     Support for Echelon Outdoor Lighting System (OLS) Framework

The PL versions of the SmartServer software now contain the Outdoor Light System (OLS) framework for outdoor lighting applications. (ILE-7910, 7942, 7946, 7950)

5.2.2     Updated Support for CPD 3000

Echelon CPD 3000 Outdoor Lighting Controller version 2.1.16 firmware is included. (ILC-2832)

5.2.3     Logging & Global Settings

The SmartServer software now logs all login and logout activities into /root/loginLog.txt file.  As the currently active loginLog.txt file grows larger than 5KB, the log content will be moved into loginLog1.txt. (ILE-70771)

Global settings are now always persistent across opening and closing of Global Setting windows.  Cookies have been replaced with local storage.  (ILWP-3287)

5.2.4     Meter Pulse Counter Edge Detection

The SmartServer software now allows users to select rising, falling, or both-edges for meter pulse or edge counting. (ILE-7944)

5.2.5     Modbus Configuration Web-UI Enhancement

The SmartServer Web interface now supports viewing and editing the Modbus register start address in hexadecimal number format. In addition, the user interface for configuring the start and stop address for bit or byte data field has been improved. (ILWP-62825 & ILWP-3288)

5.2.6     Updated LonMark Resource File Set & Editor

The SmartServer software now installs LonMark Resource File Set version 15.00.15 and Echelon IzoT Resource Editor version 4.40.08. (ILC-2841)

5.3    Improvements in SmartServer 2.2 SP3

5.3.1     Windows 10 Support

The SmartServer software can now be installed on 64-bit and 32-bit versions of Microsoft Windows 10.

5.3.2     New Default SmartServer Installation Path

The default SmartServer installation path is now under C:\program files (x86)\lonworks on 64-bit versions of Microsoft Windows and C:\program files\lonworks on 32-bit versions of Microsoft Windows. (ILC-2810, ILC-2814)

5.3.3     OpenSSL Update

The SmartServer OpenSSL library has been updated to version 1.0.2a to address a Man-in-the-Middle vulnerability, to disable weak (< 128-bit) ciphers, and to add support for chained/intermediate and 2048-bit client certificates. (ILE-7728, 7729, 7810 & 62794)

5.3.4     Support for Plug-N-Play Provisioned Network (PPN)

Added support for detecting (via the SOAP LON_Network_Command_Invoke method) whether or not PPN is supported on a given SmartServer. (ILE-7841)

5.3.5     System Health Configuration Changes

Added support for a system health configuration change to take effect without requiring a reboot of the SmartServer. (ILE-49254)

5.3.6     Dynamic Data Point Direction

Added a user interface to specify the input/output direction when creating a dynamic network variable. (ILWP-3167)

5.3.7     Display/Edit Modbus Data Point Register Address in Hexadecimal

Added an option for a user to view, set, or edit a Modbus register start address in hex with a new Hexadecimal option in the Global Settings dialog. (ILWP-62825)

5.3.8     Simplified Deleting Multiple Devices with Network Connections

Simplified the user interface for deleting multiple devices with network connections. (ILE-7899)

5.3.9     Adobe SVG Viewer Product Installation

The Adobe SVG Viewer product installation option has been removed from the SmartServer 2.2 Product Installation menu. (ILC-2823)

5.4    Improvements in SmartServer 2.2 SR1/SP1

5.4.1     Scheduler Updates

The Scheduler now allows an exception name longer than 25 bytes.  (68993, 69294)

5.4.2     Multiple Web Targets on the same Host IP Address

Multiple Web-connection destinations can now be selected for the same host IP address.  (70314)

5.4.3     Support for Secure (SSL/TLS) SMTP Connections

New STARTTLS (port 587) or SSL/TLS (port 465) security options have been added for SMTP connections.  This provides support for mail servers that require SSL or TLS encryption.  (ILE-56715, ILE-7721)

5.4.4     NodeBuilder Resource Editor Update

The NodeBuilder Resource Editor has been updated to version 4.02.09.  This version provides compatibility with NodeBuilder FX and IzoT NodeBuilder.  (ILE-70461)

5.4.5     Resource File Updates

The following resource files have been updated:

·        LonMark standard resource file set version 14.01

·        Echelon’s CPD 3514 PL OLC  resource file set version 2.0.13

·        Echelon Lighting resource file set version 1.22 files  (ILE-7716, ILE-7737 & ILE-7749)

5.4.6     Support for Large Network Variables

You can now create dynamic data points containing up to 225 bytes.  (ILE-7727)

5.4.7     Improved Communication Interruption Recovery

In Standalone Network Management mode, the SmartServer is more robust in handling commissioning interruptions due to power cycles or changes in the PL proxy agent.  (ILE-7719, ILE-7730, ILE-7731)

5.4.8     Hostname Enhancements

SmartServer’s hostname restrictions now comply with RFC 1123.  The hostname length can be up to 64 characters, with alphanumeric and hyphen (‘-‘) characters accepted.  You can enter a fully-qualified domain name (FQDN).  To use a hostname that was not accepted in the previous release, you must first upgrade the bootrom to version 4.06.057, which is included with this release, or newer.  (ILE-7722, ILE-7736, ILWP-3170, ILWP-3163)

5.4.9     SMTP Greetings Enhancements

The SMTP client can now send HELO/EHLO greetings using FQDN, plain hostname, or IP literals.  (ILE-7721, ILE-7738, ILWP-3163)

5.4.10  OpenSSL Enhancements

OpenSSL chained/intermediate certificates are now supported.  Weak ciphers (less than 128-bits) are now disabled.  (ILE-7728, ILE-7729)

5.5    Improvements in SmartServer 2.2 Update1

5.5.1     IE 11 Compatibility

Support for IE 11 has been added.  SmartServer 2.2 SR1 has been tested with Internet Explorer 8, 9, 10, and 11; Firefox 9, 10, and 11; Chrome 16, 17, and 18; and iOS 5.1 Safari.  (69951, 70306)

5.6    Improvements in SmartServer 2.0 SP4 / SmartServer 2.2

5.6.1     Device Discovery

Scan command for device discovery on repeating channels can now be done for unconfigured devices (NST_UNCONFIGURED) and previously commissioned or preconfigured devices (NST_SELECTED).  In addition, the Scan command can also be used to limit the number of discovered devices per agent and to start predictive device discovery.  (67948, 67951)

5.6.2     Device Authentication

An optional AuthenticationKey property has been added to the LON device property page to provide security during device commissioning.  This optional key is used when a device is added or replaced through the SNM. (67949, 67950)

5.6.3     Improved Device Image Download Time

For improving device image download time, a new LCA_MAINTENANCE mode has been added to the UCPTmgmtMode CP in LON_Network_Cfg to suppress sending of heartbeats and poll requests to the network. (57447, 57823, 67967)

5.6.4     SSL Support for LNS Proxy

SmartServer is now able to contact and synchronize with the LNS Proxy in EES through SSL. (68134, 68625)

5.6.5     LonWorks Connections in Standalone Mode

Create peer-to-peer connections in standalone networks with repeating for rapid response to external events.

5.6.6     Increased Device and Data Point Limits in Standalone Mode

Install up to 300 devices and use up to 2000 data points in a standalone network.  The limits may be lower depending on the number of data points and custom apps.

5.6.7     Maintenance Network Management Mode

Rapidly commission networks by disabling data point heartbeats and polling messages.

5.6.8     Static Repeating Mode.

Optimize the performance of power line repeating channels by disabling the periodic verification of repeating paths.

5.6.9     Enhanced XMPP Client

Use real-time bi-directional communication between SmartServers and enterprise applications located behind firewalls.  The SmartServer’s built-in XMPP client now supports connections where the IP address changes because of lease timeouts, and it is now compatible with Openfire.

5.6.10  OpenLNS Server and OpenLNS Commissioning Tool Support

Integrate the SmartServer in networks managed with an OpenLNS Server.  Use the SmartServer with networks managed with the OpenLNS Commissioning Tool (OpenLNS CT).

5.6.11  Version 14 Standard Resource File Set

The standard resource file set has been updated to Version 14.

5.6.12  Improved Web Page Performance

Performance of built-in and custom Web pages has been improved.

5.6.13  64-Bit Windows Support

SmartServer 2.2 is compatible with 64-bit versions of Windows 8 and Windows 7, in addition to the previously supported 32-bit versions of Windows 8, Windows 7, Windows Vista, and Windows XP.

5.6.14  Cross Browser Support

View SmartServer 2.2 built-in and custom Web pages using Chrome and Safari in addition to previously supported browsers (Internet Explorer and Firefox).

5.6.15  Additional Language Support

View SmartServer 2.2 built-in and custom Web pages in Chinese, Korean, and Japanese in addition to previously supported languages (English, French, and German).

5.7    Improvements in SmartServer 2.0 SP3

5.7.1     Device Capacity

The device capacity has been increased to 300 from 200.  The limit may be lower depending on the number of data points and custom apps. (63507, 63376, 62947, 63373, 64192)

5.7.2     Web User Interface

Web page performance for built-in and custom Web pages has been improved. (62793, 63669)

Displaying and updating data points has been improved. (50499, 63356, 63444)

5.7.3     Web Browser Compatibility

A Web page timing issue with Firefox 6.0.2 has been fixed. (62965)

Scrolling has been improved with Chrome. (65356)

Data log viewing has been improved and crashes have been addressed in Internet Explorer 9. (59850, 59983)

The message to download the Adobe SVG viewer has been changed. (64332)

5.7.4     Standard Resource File Set

The standard resource file set has been updated to Release 13.10. (63449)

5.7.5     Modbus Driver

A tracing option has been added for the Modbus driver.  The Modbus driver displays bus activity in the console when trace level 2 is selected.  (63519)

5.7.6     XMPP Service

You can now set SASL, SLL, BOSH, and XMPP ping interval options from the Web user interface and via SOAP. (67598)

You can now start and stop the XMPP message service. (67656)

5.7.7     SNMP Service

You can now enable or disable the SNMP service from a built-in Web page. (62147)

5.8    Improvements in SmartServer 2.0 SR2/SP2

5.8.1     Cinterion MC75 and MC63i Series Modem Support

Support has been added for the Cinterion MC75 and MC63i series modems. (59478)

5.8.2     M-Bus Enhancements

The retry count can now be specified for M-Bus devices. (59476, 59477)

5.8.3     Enhanced Authentication Security

The hashing algorithm used to verify passwords has been enhanced to use standard SHA-512 hashing. (57978)

5.8.4     Internet Explorer 9 Support

Support has been added for viewing and updating SmartServer Web pages using Internet Explorer 9. (59564)

5.9    Improvements in SmartServer 2.0 SP1

5.9.1     Secure Web Binding

You can now create secure Web connections that use SSL encryption.  See Chapter 4 of the SmartServer 2.2 User’s Guide for documentation.  (57043)

5.9.2     Battery Status

A new battery status indicator has been added to the System Information Web page, and a battery status data point has been added that you can use to trigger an alarm when the battery is low.  See Chapter 3, Viewing System Information and Performance in the SmartServer 2.2 User’s Guide for documentation.  (57395)

5.9.3     Rapid Deployment

The EES 2.0 AdminServer no longer stores the standard SmartServer firmware files in the template when you create an i.LON template.  This significantly reduces the time required to create and deploy i.LON templates.  See Rapid SmartServer Deployment in the ReadMe document for the Echelon Enterprise Services for documentation.

The EES 2.0 AdminServer can now be used to create and deploy components to up to 100 SmartServers at a time.  A component is any collection of files that you want to deploy to one or more SmartServers from an AdminServer.  For example, a component may consist of an FPM app, resource files, XIF files, and custom Web pages that you want to deploy to one or many SmartServers.  See Rapid Component Deployment in the ReadMe document for the Echelon Enterprise Services for documentation. (57345)

5.9.4     Chinese, Japanese, and Korean Language Support

Built-in Web pages are now available in Chinese, Japanese, and Korean language versions, in addition to the previous English, French, and German versions. (57186)

5.9.5     New Data Types

New data types have been added to support Modbus timing parameters. (57165)

5.9.6     Release 4.04 Update

The EES 2.0 AdminServer can now update a Release 4.03 SmartServer 2.0 to Release 4.04 (SmartServer 2.0 with SP1). (56858)

5.9.7     Custom Datapoint Selector

The i.LON Vision 2.0 datapoint selector has been enhanced for custom Javascript objects.  See Chapter 5 of the i.LON Vision 2.2 User’s Guide for i.LON Vision for documentation.  (53258)

6      Fixes

The following section summarizes the issues fixed in the SmartServer 2.2, 2.1, and 2.0 releases and service packs.  The Issue column lists Echelon internal issue tracking numbers.

6.1    Fixes in SmartServer 2.2 SR5/SP5




Fixed Modbus databpoint aggregation failure (when the message size exceed 240 byte bytes) to allow handling the maximum Modbus message of 246 bytes.


Fixed a gzipped data log file corruption when SmartServer tried to recreate a gzipped log file after renaming one or more datapoints followed by either a change in data log configuration or rebooting of the SmartServer. In both cases, the data log file will be checked for deleted (or renamed) data points and the data log file will be recreated with deleted/renamed data point entries removed.


Fixed the SmartServer “Unknown” powerline repeating setting (after firmware upgrade) to one of the three allowable modes: Repeating Off, Repeating On (with Automatic Discovery and Optimization of Proxy Chains) or Repeating On (with Static Proxy Chain).


Updated the SmartServer ILON100_FTT_V40 & ILON100_PLC_V40 dynamic interface templates to support adding of dynamic NVs over 31 bytes in length & fix incorrect static NV count.


Fixed a repeating proxy history mechanism lock up problem that caused a nascent device to incorrectly get an LDV_DEVICE_ERR(4) message, go into a temporary unknown state and eventually come back into an up state. 


Added data logger support in handling double quote character/symbol ("- which is the US symbol for length unit in inches) as a unit override string in data point by automatically preceding another double quote character as an escape character.


Fixed/reduced memory footprint by 7 MB of RAM space for non-M-Bus and most M-Bus applications that do not need multi-telegram feature.  The resource file needed to support M-Bus multi-telegram feature (introduced in SmartServer 2.2 SR1/SP1 – revision 4.06.057) contains M-Bus DP definitions for 65 to 200 value elements and requiring additional 7 MB of RAM space.  Since non-M-Bus and most M-Bus applications do not need the extended M-Bus DP formats, starting with SmartServer 2.2 SP5 (revision 4.09) the default is the original M-Bus resource file that requires 7 MB less RAM space. When the M-Bus driver detects application usage of an extended M-Bus DP format, it automatically replaces the default M-Bus resource file with the extended M-Bus resource file that uses an additional 7 MB of RAM space. 


Improved the way SmartServer does nascent device checking: If a device is down but the SmartServer is still able to communicate with it using its Neuron ID addressing then it is assumed to be in nascent state if any of the following is true:

a.       Device is unconfigured.

b.      Domain index 0 has the invalid bit set

c.       Domain index 0 has the wrong domain ID, subnet or node.


Fixed a LonTalk stack issue where NV update messages sent from an external device were dropped.

6.2    Fixes in SmartServer 2.2 SR4/SP4



ILC-69286 & ILC-63974

Fixed iLON configuration plug-in failure due to missing MSXML4 library.


Fixed an issue that cause peer-to-peer periodic heartbeat from SmartServer to a device to stall due to MaxAge while in Data Points View page.


Improved LON binding algorithm to reduce too many network management messages (no need to query & only send the used binding entries).


Fixed the V40 dynamic interface to limit the instantiation of the hardware function blocks (such as DI/DO/PC/RTC) to the actual physical device count. For example, 2 DI, 2 DO, 2 PC and 1 RTC.

ILE-7939 & ILE-7894

Fixed a memory leak issue when a scheduled alarm sent an email with SSL/TLS.  This issue affects SMTP, Web Binder and XMPP/gloox clients when configured using SSL/TLS.


Fixed an issue that causes SOAP response for a request using a different unit format (i.e. °C) than the defined format for the data point (i.e. °F) to return the defined format (°F) instead of the requested format (°C), even though the actual scalar value get scaled/converted properly to the requested format (in Celcius).


Fixed an issue that caused the SmartServer to calculate the wrong daylight saving start and stop time for some regions.


Fixed an issue that caused a Public Exception schedule not showing up under Calendar after duplicating Scheduler function block.


Fixed an issue under Internet Explorer 11 that caused the context menu in the right pane of SmartServer Web-UI to stay/remain after switching to a different function block.


Fixed an issue that caused the SmartServer to reboot when deleting a device that still has a LON binding.


Fixed an issue that leaves orphaned/stranded devices in the SmartServer when performing ‘Release Neuron ID’ command after a failed commissioning attempt.

6.3    Fixes in SmartServer 2.2 SP3




Fixed an issue with changing the direction of a dynamic data point after the data point has been created.


Fixed an issue that caused the SmartServer IP-852 router to fail due to an invalid Session ID when interoperating with the Gesytec Easylon Router.


Fixed an issue that caused the SOAP DataServer Read command to return Item-Data (containing status E_Fault: DataServer busy) instead of Dp-Data when a data point is (hard) offline.


Fixed a memory leak of 3KB per XMPP call in the XMPP client.


Updated the V40 dynamic interface XIF file to fix a broken reference to the Node Object’s nviTimeSet network variable.


Fixed an issue that caused the SmartServer to report an Exception Vector #1: “<CO-01E1024> - missing ‘Domain’ element” error when setting LON_Network_Cfg via SOAP.


Fixed an issue that caused the SmartServer Scheduler to incorrectly report data point status at midnight.


Fixed an issue that reported an unitialized value (typically 0) in response to a SOAP request for a configuration network variable value with UCPTmaxAge set when the request was sent after a reboot. Persistent values for internal device configuration network variable data points are now persistent across reboots.


Fixed an issue that caused a LON turnaround (internal) connection to fail on a power-line repeating network.


Fixed an issue that caused the SmartServer to hang and cause SOAP timeouts after repeatedly opening and closing the Global Settings dialog three or more times.


6.4    Fixes in SmartServer 2.2 SP2




SmartServer is constantly rebooting (Null pointer exception) while reading from a corrupted CP file (may be caused by power interruptions during device commissioning).

6.5    Fixes in SmartServer 2.2 SR1/SP1



70110, 70125

Daylight Savings Time was sometimes handled incorrectly when deleting a one time exception.

69515, 70112

The timezone name display was sometimes blank in Chinese Windows 7.


The timezone was not updated correctly when changing from one country to another country with the same timezone.


Watchdog exceptions occurred on shut down after commissioning from the Streetlight.Vision-Design application.


A 404 error was sometimes displayed in Firefox and Chrome browsers when selecting English on non-English versions of Windows.

ILE-7719, 7730, 7731

Power interruptions while commissioning is in progress can result in incomplete network management tasks - devices may end up in incomplete configuration and in the Soft Offline state or devices may get commissioned twice.



Reading or clearing a corrupted gzip-compressed datalog sometimes resulted in the SmartServer getting into 100% CPU utilization.

6.6    Fixes in SmartServer 2.1 SR1




An extra TAB or click was sometimes required to enter a preset value for a data point.

6.7    Fixes in SmartServer 2.0 SP4 / SmartServer 2.2



65540, 67430

SmartServer sometimes crashed or stalled when making multiple LON connections using the LonMaker Integration Tool.


The real time clock was not working after updating the SmartServer image from Release 4.04.119.


The Pulse Counter sometimes jumped between two values while polling.


The XMPP Server failed to connect when using the hostname instead of IP address.


Configuring Openfire without BOSH resulted in a failure to connect with the server.


Adding a Real Time Clock or Alarm Generator in the LNS tree with a non-default name results in a “The base name cannot be found” error message, but everything continues to work.


XMPP updates sometimes have a long delay after the first update.


A memory leak occurred while sending Web connection updates via XMPP.


A duplicate XMPP server was not detected.


An error occurred on Chinese Windows while trying to insert a Data Point Value by Alias Name or Data Point Preset by Alias Name in the Configure Email Web page.


Selecting “Show Message with Identical Program ID only” in the LON Device Identification dialog resulted in all service pin messages being filtered.


Adding a new CP to an existing functional block will causeed the SmartServer user interface to hang.


Leading space non printable characters were lost or removed when updating a SNVT_string_ascii Data Point Value of type.

6.8    Fixes in SmartServer 2.0 SP3



52902, 63354

Modbus messaging sometimes failed if there were many Modbus data points.

57385, 63252

Adding an XMPP message service without any credentials or with an empty configuration caused unexpected reboots.

59606, 60541

There was a memory leak during SOAP message processing.


A Calendar did not work without reference to nvoDateEvent.


Adding a Modbus data point sometimes failed.


Discovering and commissioning a new device in standalone mode sometimes caused the SmartServer to crash.


The data server did not properly handle an NV length change of a changeable type NV.

62533, 64191

LON device commissioning failed if the device template had an incorrect subnet.


Deploying a template in LNS mode often resulted in Error 25 Device In Use.


The data point references to the nviEnable, nviClear, nvoLevelAlarm, and nvoStatus data points were missing after adding 1000 data points for logging.


Time zone and daylight savings settings for some regions were incorrect.


A watchdog reset would sometimes cause multiple reboots.

63268, 63706

It was not possible to create a RAW_HEX data point with a length of more than one byte.

63374, 64193

The timeout was too short when starting many apps.


A Data Logger continued to log during reboot when it was disabled.


Menus were sometimes invisible after converting i.LON 100 e3 Web pages.


Setting the time zone sometimes failed.


Deleting and creating apps sometimes caused the data server to fail.


The Pulse Counter output value sometimes incorrectly decreased.


The system information message service could not be accessed when the XMPP message service was enabled.


The XMPP message service did not reconnect with the XMPP server after a dynamic IP address change.

67357, 67560

The Alarm Generator and Alarm Notifier did not observe set/clear delays.


The SmartServer sometimes crashed when creating many Web connections.


The time to next state field of a SNVT_TOD_event output from a Scheduler was not updated correctly.


Two consecutive single quotes could not be used in a SOAP request.


An empty password could not be specified when configuring the XMPP message service.


Some LON devices were not commissioned after deploying a template with EES.


Sockets were not correctly released after changing the XMPP message service.


Radio buttons for NVL data points were sometimes disabled after converting an i.LON 100 e3 Web page.



The XMPP service did not correctly handle non-default BOSH server paths.

6.9    Fixes in SmartServer 2.0 SR2/SP2




Deleting a virtual functional block sometimes corrupted references from other functional blocks to datapoints referenced by the virtual functional block.


When using LNS network management mode with the LonMaker Integration Tool, if you used the SmartServer navigation pane or an LNS plug-in to create a connection to a dynamic NV on the SmartServer, the connection sometimes did not appear on the LonMaker drawing.


The Device Overview Web page sometimes did not display devices discovered by subsequent scans.


The Scheduler SOAP Read Response message sometimes did not include events created at midnight.


A Web Binding Target service could not be added to an LNS Proxy host device in the SmartServer Web interface.


Creating an Exception Schedule in the Scheduler sometimes caused the SmartServer to reboot.


The M-Bus driver failed when the SmartServer was rebooted.


Web connections with file attachments failed with some Web servers for files larger than 4 Kbytes.


The Apps for the SmartServer’s static functional blocks (Digital Input, Digital Output, Pulse Counter, and Real-Time Clock) failed when the SmartServer’s internal i.LON App device was deleted and then re-created.


Offline Modbus devices sometimes caused a memory leak.


Fields of structured data types within arrays could not be formatted correctly.


The Edit Value dialog in the Data Point: View Web page could not be used to update the fields of structured data types within arrays.


The Setup – Security Web page could not be opened sometimes.


In some cases the Data Logger and Alarm Notifier View Web pages consumed a lot of the SmartServer’s CPU and made many operations seem non-responsive.


The warning message displayed when there were too many entries to be displayed in the Data Logger and Alarm Notifier View Web pages was confusing.


The slider button in the Data Logger and Alarm Notifier View Web pages was hard to use when viewing short intervals within a long-term log.


The SmartServer sometimes queued too many SOAP requests causing excessive SmartServer CPU usage.


No error was displayed when the SmartServer did not have enough RAM for the deletion of data and alarm log entries.


Modifying the Smart Network Management commands in the Setup - LON Device Web page immediately after instantiating a device external interface (XIF) file caused duplicate devices to be created.


The Data Logger did not record data point string values containing the embedded ‘>’ and ‘<’ characters.


Opening the Configure – Data Point Web page for some data points caused the SmartServer Web interface to fail.


The Alarm Notifier could fail and cause the SmartServer to reboot.


The Real Time Clock SOAP Set Request message expired if received before time change and processed thereafter.


The Data Logger: View Web page displayed only one value once the Web page’s cache overflowed.


The Data Logger SOAP Read Response message does not include data from compressed (.gz) log files.


The SVG trend graphs in the Data Logger and Alarm Notifier View Web pages did not function with Microsoft Internet Explorer 9.


The Data Logger: View Web page did not display all data points for a given Data Logger if that logger was recording multiple data points.


The Data Logger SOAP Read Response message did not return data in the frequency specified by the poll rate.


The Data Logger log files included multiple entries for the same update.


The SmartServer would sometimes permanently fail to start the SmartServer applications if a power sag occurred during the boot process.


Dynamic data points required for apps were sometimes deleted after a reboot.


Devices based on an FT 5000 Smart Transceiver and any devices running Neuron firmware version 19 could not be commissioned by a SmartServer running in standalone mode.

6.10Fixes in SmartServer 2.0 SP1





In an OpenLNS or LNS managed network, if you created external functional blocks and data points on the SmartServer without first creating the parent external device, the external functional blocks and data points would not be synchronized.


Commissioning a device in standalone mode did not disable self‑installation.


Synchronization did not match external data points created in and OpenLNS or LNS Server with existing data points on the SmartServer that have the same name but are marked as deleted.


The Alarm Generator did not properly maintain the alarm condition for a data point when an analog comparison function was used.


Rebooting the SmartServer sometimes caused the Modbus driver to fail.


The following problems sometimes occurred if the computer time was set to a local time zone that has a negative offset from UTC:  SmartServer Web pages may slow down or even fail; you could not create external network variables; and a warning message appeared in the SmartServer Web pages every day in January after a specific time.


In some cases you could not set the SmartServer system time.


The Data Logger SOAP Read Response message sometimes omitted some data log entries.


The scope of user‑defined network variable types (UNVTs) was sometimes incorrect.


In some cases the Data Logger leaked memory when reading data.


The Edit dialog in the Scheduler application did not always display the correct schedule name after you modified the daily schedules in the Edit Daily Schedules dialog.


In some cases, the Scheduler did not import an exception from the calendar when the UCPTindex property was not specified correctly.


In some cases a network monitor would cause the SmartServer to reboot.


A Modbus template sometimes caused a .NET application to fail.


Invalid time zone offsets in the system time sometimes caused the SmartServer to fail.


The SmartServer had to be rebooted to calculate the current number of internal FPM devices correctly because the SmartServer did not include deleted internal FPM devices in the current count of available devices.  The SmartServer only allows nine internal FPM devices to be created.


Devices created and installed automatically from device templates sometimes did not have correct data point values initially.


The SmartServer Web interface sometimes failed with Firefox 3.6.


The SmartServer console application did not notify the user if the WebParams.dat file was missing.


You could not programmatically write data point values in raw hex format.


Modbus writes within a short interval were not aggregated.


The Data Logger did not return correct UTF8 alias names in response to a data logger read function.


Some operations were very slow in IE8.


Auto-selected Smart Network Management settings caused current .APB and .XIF files to be overwritten.


You had to clear your browser’s cache after manually uploading .zip files to the SmartServer to update its image.


The Alarm Notifier’s nviAnEnable data point did not enable or disable the notification and data point update functions.


SMTP messages were sent using small (74 byte) packets, which caused extra overhead in network traffic.


Cinterion modems had incorrect AT commands.


NV indexes were sometimes not updated correctly after the program ID for a device changed.


The Alarm Notifier: Summary Web page stopped polling if you navigated away from it.

6.11Fixes in SmartServer 2.0




Time sometimes drifted multiple seconds per day.


C# SOAP client reported an "underlying connection was closed" error.


The Alarm Notifier: Summary Web page displayed obsolete active alarm entries after comments were changed.


Reloading an app rebooted the SmartServer if more than one app was being developed.


Calculation of daylight savings time (DST) did not work in the southern hemisphere.


You could not write configuration properties when the SmartServer was using OpenLNS and LNS management mode and the OpenLNS or LNS Server was not attached to the network.


A resource conflict between an external modem and the Modbus driver was reported, even if no modem was selected.


The RS‑485 interface sometimes caused the SmartServer to reboot when Data+ and Data‑ lines were not connected correctly.


Disabled SNTP synchronization was not re‑enabled after communication with the SNTP server was restored.


Real‑time clock synchronization sometimes failed after switching to the backup SNTP server if the backup SNTP server also failed as well.


Writes to Modbus multi-write coil registers sometimes failed.


In OpenLNS and LNS management mode, synchronization of a router sometimes caused an endless loop if the channel of the far side was not defined in the LNS Server.

7      Known Problems and Workarounds

This section describes known problems and their workarounds for this release.  Numbers in parentheses at the end of the descriptions are Echelon's internal issue tracking IDs.


7.1    Slow Commissioning for Street Light Networks

When commissioning a street light network, improper configuration can cause excessively long commissioning times due to the large number of devices sharing the available power line bandwidth.

Workaround:  Do not use the default method for adding a device to the SmartServer using the device interface (XIF) file.  In this case, the SmartServer automatically defines a 600 second polling interval for each data point defined by the XIF file.  Thus, as you add devices and commission those, the total network traffic load increases because of this data point polling.  The polling traffic then competes with the traffic associated with device commissioning, so that commissioning each device can take a long time to complete.

Use device templates instead of defining devices with the XIF file.  Create a device template that defines the polling and heartbeat rates for each data point associated with a device type.  See Chapter 4 of the SmartServer User’s Guide for more information about creating and using device templates.

To add devices to the SmartServer using a device template rather than a XIF file:

  1. Add and commission a single device of each type (luminaire and Street Light Bridge module) using the device’s XIF file. 
  2. Create a device template for each device type that you added in step 1.  Ensure that you have exactly one device template for each device type.
  3. Edit the device template to set configuration and driver properties for each device to set polling interval and heartbeat values for all data points to 0. 
  4. Use the device template for each device type to add and commission all subsequent devices within the street lighting network. 
  5. Wait for all devices to complete the commissioning process.
  6. Edit the added devices, as needed, to set polling intervals and heartbeat values for appropriate data points.  Typically, you set polling rates for input data points to 0, and only poll output data points at a rate that is compatible with the logging requirements for the output data points. 

    If a luminaire provides a complex data type that collects information about the current operating state of the device, polling the feedback data point might prove redundant, and should therefore have a polling rate of 0.  In some cases, data points are used for real time monitoring, and are only polled when the device is brought into focus by a system management tool. 

You can also add functionality to your streetlight management system that sets polling and heartbeat rates after the device commissioning process is complete.  When the system is ready for operation, the streetlight management system can set the polling and heartbeats to values that are appropriate for the available channel bandwidth.

(57520, 57708)

7.2    Incorrect Offline Reports for Street Light Networks

When monitoring a street light network with active multi-hop repeating, online devices may be reported as offline due to delayed responses caused by the repeating chains.  Workaround: If you see unexpected offline reports in street light networks, increase the offline delay for LonWorks devices to accommodate the delayed responses.  To set the offline delay for devices, right-click the LonWorks channel in the SmartServer navigation pane and then click Properties on the shortcut menu. (58275)

7.3    6-Byte Authentication Keys Fail with the CRD 3000

A 6-byte authentication key will fail when used with the Echelon CRD 3000 Power Line/RF Bridge.  Workaround: Always specify a 12-byte authentication key for networks that use the CRD 3000.  (57993)

7.4    Commissioning Devices with Changeable-Type NVs

You cannot commission a device in the LNS tree that has a bound output network variable with a changeable type that was changed with the SCPTnvType configuration property.  Workaround:  Commission the device with the LonMaker tool or other LNS application.  (54584) 

7.5    Persistent Synchronization Error Message

The “Cannot synchronize with LNS" error massage is displayed in the Web interface approximately 20 minutes after the condition has been resolved.  Workaround:  Manually clear the system log to delete the error message.  (54772) 

7.6    Misleading Alarm Notifier Error Message

If you open the Alarm History or Alarm Summary Web pages before configuring an Alarm Notifier, a “No application response for '#8000010128000000[4].UFPTalarmNotifier" error message is displayed in the Web interface.  Workaround:  Configure an Alarm Notifier, and then re-open these Web pages.  (57045) 

7.7    Analog Functional Block (AFB) Reset Error

The AFB output is not updated after the poll on reset delay interval is over if any of the input data points get an update during the interval.  Workaround: Specify a poll on reset delay of 0 for the AFB. (54503)

7.8    Disabled Security Web Page Cannot Be Enabled

Once you disable the SmartServer Security Web page, you cannot re-enable it.  Workaround: Use the console interface to change security settings after you disable the Security Web page. (54668)

7.9    Cellular Carrier Network Incompatibility

Some cellular carriers such as Deutsche Telekom are converting their networks to use IP interfaces to carry Circuit Switch Data (CSD).  The IP interfaces have longer latencies than previous CSD interfaces, and as a result up to 8 seconds of latency can be added during modem initialization.  This increased time can result in modem initialization failures.  Workaround: Select a modem that is compatible with your carrier’s network. (63533)

7.10Using a Duplicate IP Address Range for Different Interfaces

Communications may fail if you assign a duplicate address for the Ethernet IP address and the PPP IP, or if you assign addresses within the same subnet address range.  Workaround:  Assign local IP addresses outside the range of the SmartServer's Ethernet IP connection.  For example, do not use to for a local IP address if you are using the SmartServer's default IPv4 address (  (61637) 

7.11Misconfigured Heartbeats on Local NVs

If you misconfigure heartbeats for a dynamic output NV on the SmartServer, updates to the output may not occur when you expect them.  Workaround: Use the following guidelines for adding a dynamic output NV to a functional block in the SmartServer:

1.      After adding the functional block and a dynamic output NV with a heartbeat time defined, commission and set the iLON app online.  Heartbeats will not work if the iLON application is not commissioned and online. 

2.      The default SmartServer behavior for creating a dynamic NV is to create an Input NV.  If you are creating an output NV, you must select the Output NV option before you click Submit.

3.      Before you create a connection, select the type of connection.  If you do not specify the connection type, the SmartServer will select the connection type automatically.  The automatic selection may not be correct for your use case.  The connection type that works for most uses cases is Repeated LON Connection.

4.      Initialize the Output NV with a valid value to kick off the heartbeats. (69067) 

7.12LON Connection Failure with Uncommissioned iLON App

If you attempt to create a LON connection to an external device when the iLON App is not yet commissioned will silently fail.  Workaround: Always commission the iLON App before making any LON connections. (69411)

7.13Web Server Security & Parameters Help Menu Fails on Windows 7

On Windows 7, the help page of the SmartServer 2.2 Web Server Security and Parameters application fails to come up.  Workaround: Download WinHlp32.exe from Microsoft Corporation website. The winhlp32.exe is different for different OS. For example, download winhlp32.exe for Windows 7 and Windows 8.1 respectively from the following links:   (ILC-2846)





Echelon, LON, the Echelon logo, LonWorks, NodeBuilder, LonTalk, LonPoint, Neuron, 3120, 3150, LNS, i.LON, IzoT, LonLink, LonResponse, LonSupport, OpenLDV, LonScanner, and LonBridge are trademarks of Echelon Corporation that may be registered in the United States and other countries.  For a complete list of registered trademarks see the Echelon website at  All Rights Reserved.


Other trademarks belong to their respective holders.