Echelon SmartServer 2.2 SP2 ReadMe
Release 4.07.003, March
2015
Copyright © 1998 –
2015 Echelon® Corporation
All Rights Reserved
This document describes SmartServer 2.2 SP2. You can apply SmartServer 2.2 SP2 to update previous SmartServer 2.2, SmartServer 2.1, and SmartServer 2.0 installations to the SmartServer 2.2 SP2 software. See Installing SmartServer 2.2 for instructions on installing the update and verifying that it has been installed.
Additional information and updates, including service packs and critical updates, may be available at www.echelon.com/smartserver. The latest service packs and updates may not be included with your SmartServer. See Echelon’s Knowledge Base at www.echelon.com/support for answers to frequently asked questions.
SmartServer 2.2 SP2 is compatible with 64-bit and 32-bit versions of Windows 8 and Windows 7, and is also compatible with 32-bit versions of Windows Vista and Windows XP. To provide full functionality, the SmartServer software must be used with Microsoft Internet Explorer 8 or newer, Mozilla Firefox 9 or newer, Chrome 16 or newer, or iOS 5.1 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.
4 Installing SmartServer 2.2 SP2
5.1 Changes in SmartServer 2.2 SP2
5.1.2 Support for RF Meshing Analysis
5.2 Changes in SmartServer 2.2 SR1/SP1
5.2.2 Multiple Web Targets on the same Host IP Address
5.2.3 Support for Secure (SSL/TLS) SMTP Connections
5.2.4 NodeBuilder Resource Editor Update
5.2.6 Support for Large Network Variables
5.2.7 Improved Communication Interruption Recovery
5.2.9 SMTP Greetings Enhancements
5.3 Changes in SmartServer 2.2 Update1
5.4 Changes in SmartServer 2.0 SP4 / SmartServer 2.2
5.4.3 Improved Device Image Download Time
5.4.4 SSL Support for LNS Proxy
5.4.5 LonWorks Connections in Standalone Mode
5.4.6 Increased Device and Data Point Limits in Standalone Mode
5.4.7 Maintenance Network Management Mode
5.4.10 OpenLNS Server and OpenLNS Commissioning Tool Support
5.4.11 Version 14 Standard Resource File Set
5.4.12 Improved Web Page Performance
5.4.15 Additional Language Support
5.5 Changes in SmartServer 2.0 SP3
5.5.3 Web Browser Compatibility
5.5.4 Standard Resource File Set
5.6 Changes in SmartServer 2.0 SR2/SP2
5.6.1 Cinterion MC75 and MC63i Series Modem Support
5.6.3 Enhanced Authentication Security
5.6.4 Internet Explorer 9 Support
5.7 Changes in SmartServer 2.0 SP1
5.7.4 Chinese, Japanese, and Korean Language Support
5.7.7 Custom Datapoint Selector
6 Known Problems and Workarounds
6.2 Slow Commissioning for Street Light Networks
6.3 Incorrect Offline Reports for Street Light Networks
6.4 6-Byte Authentication Keys Fail with the CRD 3000
6.5 Commissioning Devices with Changeable-Type NVs
6.6 Persistent Synchronization Error Message
6.7 Misleading Alarm Notifier Error Message
6.8 Analog Functional Block (AFB) Reset Error
6.9 Disabled Security Web Page Cannot Be Enabled
6.10 Cellular Carrier Network Incompatibility
6.11 Releasing Neuron ID Strands Devices
6.12 Using a Double Quote (“) Character in a Unit String
6.13 Using a Duplicate IP Address Range for Different Interfaces
6.14 Misconfigured Heartbeats on Local NVs
6.15 Internal Turnaround LON Connection Failure in PL Repeating Mode
6.16 LON Connection Failure with Uncommissioned iLON App
6.17 i.LON 100 Plug-in Launch Failure
This document applies to SmartServer 2.2 SP2 (Release 4.07.003). To determine which release of the SmartServer software you have installed on your computer, follow one of the following procedures:
· For Windows 8, Windows 7, and Windows Vista, click the Start button, type Programs and Features in the Search box, press Enter to open Programs and Features, and then click Echelon SmartServer [Release] 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 [Release] 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 SP2 in bold:
Number |
Date |
|
i.LON 100 e3 plus |
3.03 |
April 2008 |
i.LON 100 e3 plus SP1 |
3.04 |
December 2009 |
SmartServer |
4.00.136 |
January 2008 |
SmartServer SR1 |
4.01.012 |
March 2008 |
SmartServer SR2 and SP2 |
4.02.055 |
October 2008 |
SmartServer 2.0 |
4.03.123 |
October 2009 |
SmartServer 2.0 Update 1 |
4.03.123 |
January 2010 |
SmartServer 2.0 SP1 |
4.04.088 |
August 2010 |
SmartServer 2.0 SR2 and SP 2 |
4.04.119 |
February 2011 |
SmartServer 2.0 SR2 and SP2 Update 1 |
4.04.119 |
July 2011 |
SmartServer 2.0 SP3 |
4.4.131 |
May 2013 |
SmartServer 2.1 Firmware (streetlight system use only) |
4.05.094 |
October 2010 |
SmartServer 2.1 Firmware SR1 (streetlight system use only) |
4.05.140 |
November 2012 |
SmartServer 2.0 SP4 / SmartServer 2.2 |
4.06.048 |
October 2013 |
SmartServer 2.0 SP4 / SmartServer 2.2 Update 1 |
4.06.048 |
December 2013 |
SmartServer 2.2 SR1/SP1 |
4.06.057 |
September 2014 |
SmartServer 2.2 SP2 |
4.07.003 |
March 2015 |
You can install the SmartServer 2.2 SP2 software from a SmartServer 2.2 SP2 download image, or update any prior release of SmartServer 2.2 or SmartServer 2.0 to SmartServer 2.2 SP2 by installing SmartServer 2.2 SP2. Prior releases are SmartServer 2.2, SmartServer 2.2 Update 1, SmartServer 2.0 with no service packs, SmartServer 2.0 SP1, SmartServer 2.0 SR2/SP2, SmartServer 2.0 SP3, SmartServer 2.2, and SmartServer SR1/SP1.
SmartServer 2.2 SP2 is available as a free download at www.echelon.com/smartserver. The service pack can only be installed on a computer with a prior release of the SmartServer 2.2, SmartServer 2.1, or SmartServer 2.0 software. 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 SP2 software will not run on hardware releases prior to the i.LON 100 e3 Plus due to the smaller memories of the prior releases.
To install the SmartServer 2.2 SP2 software, follow these steps:
1. Download the SmartServer 2.2 SP2 file from the Echelon website, and then 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 SP2 setup application will start automatically.
2. The Echelon SmartServer 2.2 SP2 setup application main menu appears.
3. Click Install Products. The Install Products dialog appears.
4. Click Echelon SmartServer 2.2 SP2 Software. The Echelon SmartServer 2.2 SP2 Software installer appears.
5. Follow the steps of the installation wizard. If you have an existing installation of the SmartServer 2.2 or SmartServer 2.0 software, the installation will automatically update it to SmartServer 2.2 SP2. 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 SR1 firmware. See Upgrading the SmartServer Firmware in Chapter 2, Using the i.LON AdminServer of the Echelon Enterprise Services 2.0 User’s Guide for details on how to update the firmware.
The Echelon Izot Lighting Segment Controller (SmartServer) connects with the IzoT CRD 4000 border router to provide seamless interface to the wireless networks of IzoT CPD 4000 RF-OLCs.
The Echelon Izot Lighting Segment Controller (SmartServer) provides a Web page for displaying RF device properties for easy RF meshing analysis. (ILE-7746 & ILWP-3188)
The Scheduler now allows an exception name longer than 25 bytes. (68993, 69294)
Multiple Web-connection destinations can now be selected for the same host IP address. (70314)
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)
The NodeBuilder Resource Editor has been updated to version 4.02.09. This version provides compatibility with NodeBuilder FX and IzoT NodeBuilder. (ILE-70461)
The following resource files have been updated:
· LonMark standard resource file set version 14.01—this is the current beta release
· 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)
You can now create dynamic data points containing up to 228 bytes. (ILE-7727)
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)
SmartServer’s hostname restrictions now comply with RFC 1123. The hostname length can be up to 64 characters, with alphanumeric and hyphen (‘-‘) characters accepted. A fully-qualified domain name (FQDN) can be entered. 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)
The SMTP client can now send HELO/EHLO greetings using FQDN, plain hostname, or IP literals. (ILE-7721, ILE-7738, ILWP-3163)
OpenSSL chained/intermediate certificates are now supported. Weak ciphers (less than 128-bits) are now disabled. (ILE-7728, ILE-7729)
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)
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)
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)
For improving device image download time, a new LCA_MAINTENANCE mode has been added to the UCPTmgmtMode in the LON_Netowrk_Cfg to suppress sending of heartbeats and poll requests to the network. (57447, 57823, 67967)
SmartServer is now able to contact and synchronize with the LNS Proxy in EES through SSL. (68134, 68625)
Create peer-to-peer connections in standalone networks with repeating for rapid response to external events.
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.
Rapidly commission networks by disabling data point heartbeats and polling messages.
Optimize the performance of power line repeating channels by disabling the periodic verification of repeating paths.
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.
Integrate the SmartServer in networks managed with an OpenLNS Server. Use the SmartServer with networks managed with the OpenLNS Commissioning Tool (OpenLNS CT).
The standard resource file set has been updated to Version 14.
Performance of built-in and custom Web pages has been improved.
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.
View SmartServer 2.2 built-in and custom Web pages using Chrome and Safari in addition to previously supported browsers (Internet Explorer and Firefox).
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).
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)
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)
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)
The standard resource file set has been updated to Release 13.10. (63449)
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)
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)
You can now enable or disable the SNMP service from a built-in Web page. (62147)
Support has been added for the Cinterion MC75 and MC63i series modems. (59478)
The retry count can now be specified for M-Bus devices. (59476, 59477)
The hashing algorithm used to verify passwords has been enhanced to use standard SHA-512 hashing. (57978)
Support has been added for viewing and updating SmartServer Web pages using Internet Explorer 9. (59564)
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)
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)
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)
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)
New data types have been added to support Modbus timing parameters. (57165)
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)
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)
The following table summarizes problems fixed in the SmartServer 2.2, 2.1, and 2.0 releases and service packs. The EPR column lists Echelon internal problem tracking numbers. The release or service pack that first included the fix is listed in parentheses.
This section describes known problems and their workarounds for this release. Numbers in parentheses at the end of the descriptions are Echelon's internal problem tracking IDs.
The SmartServer can fail to update a data point output that is configured with a heartbeat interval (maximum send time) if the same SmartServer output data point is also monitored from a Web page with a maximum age (specified by UCPTmaxAge) that is less than the heartbeat interval. This occurs because the SmartServer incorrectly clears the heartbeat timer when the data point is refreshed internally after the maximum age interval expires. If the output is bound to a device that implements a failure mode when an update is not received within the expected maximum receive heartbeat interval (typically 3x the output heartbeat interval), the failure mode can be incorrectly triggered as a result of the missed heartbeat updates.
Workaround: When monitoring an output datapoint configured with a heartbeat interval from a custom Web page or one of the built-in Web pages, if you specify a maximum age always specify a maximum age longer than the heartbeat interval. This applies per data point, and also applies to the global maximum age setting that you can set in the SmartServer configuration pages.
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:
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)
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)
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)
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)
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)
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)
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)
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)
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)
If you add a device to the network in Standalone network management mode and attempt to commission the device with the wrong Neuron ID, the operation will fail as expected. If you then use the Release Neuron ID' command, and use the correct Neuron ID, the Web UI will create a new device instance in the SmartServer, leaving the first attempted device in the list of devices. These orphans may persist across resets. On a SmartServer defined interval the SmartServer will continue to attempt commissioning these devices. Workaround: Use the Replace command. (69187)
If you use a single double quote in the units field of a resource file format, the double quote will be treated as a special symbol and will not be displayed within the formatted text. Workaround: To use the double quote (") character in a unit string, you must escape it with another double quote. For example, to use a single double quote character to represent inches, enter two double quotes (""). If you do not escape the double quote, the Data Logger: View Web page may not display the data point value. (67450)
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 192.168.1.0 to 192.168.1.255 for a local IP address if you are using the SmartServer's default IPv4 address (192.1.168.222). (61637)
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)
Configuring an internal turnaround LON connection such as a connection from a scheduler to an alarm generator in PL repeating mode does not work. Workaround: Always use SmartServer Web connections for connections between internal SmartServer functional blocks. (69353)
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)
When you attempt to open the i.LON 100 configuration plug-in, the following message may be displayed: "Unable to communicate with the iLON 100. Please verify the IP address and network connection. Application: Dataserver NVL List." Workaround: Install the Microsoft MSXML4 SP3 plug-in as described in the following procedure:
http://www.microsoft.com/en-us/download/details.aspx?id=15697. (69286)
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 Web site at www.echelon.com. All rights reserved.
Other trademarks belong to their respective holders.