Echelon i.LON® SmartServer 2.0 Service Pack 1 ReadMe
Release 4.04, August
2010
Copyright © 1998 –
2010 Echelon® Corporation
All Rights Reserved
This document describes i.LON SmartServer 2.0 Service Pack 1 (SP1). See Upgrading to Release 4.04 for instructions on installing SP1 and verifying that it has been installed, and Changes in Release 4.04 for details on what is fixed in this release.
Additional information and updates, including service packs and critical updates, may be available at www.echelon.com/ilon. 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.
To provide full functionality, the SmartServer 2.0 SP1 configuration software must be used with Microsoft Internet Explorer 7 or newer, or Mozilla Firefox 3.0 or newer. If you are using SmartServer 2.0 SP1 with an LNS® Server or the LonMaker® Integration Tool, you must be using the latest Echelon LNS Turbo and LonMaker service packs and updates. The latest LNS and LonMaker service packs and updates at the time of the SmartServer 2.0 SP1 release are included with the LNS Server included with the SmartServer LNS Server Editions, are included on the SmartServer 2.0 SP1 DVD and DVD image, and are also available from www.echelon.com/downloads.
6 Known Problems and Workarounds
6.1 Intermediate SSL Certificates not Supported
6.2 Commissioning Devices with Changeable-Type NVs
6.3 Missing Connections in LonMaker
6.4 Persistent Synchronization Error Message
6.5 Misleading Alarm Notifier Error Message
This document applies to SmartServer 2.0 with Service Pack 1 software (Release 4.04). To verify that you have this release on your computer, follow one of the following procedures:
· For 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 i.LON SmartServer 2.0 Software. If the Version column is not displayed, right click the list header, select More, and then select Version to add the Version column. The version number of SmartServer 2.0 Software with SP1 is 4.04.088.
· For Windows XP, open Add or Remove Programs in Windows Control Panel, and then click Echelon i.LON SmartServer 2.0 Software. Click the Click Here for Support Information link. The version number of SmartServer 2.0 Software with SP1 is 4.04.088.
To verify that you have the SmartServer 2.0 SP1 loaded on your SmartServer, check the Firmware Version property in the Setup ‑ System Info Web page as described in the i.LON SmartServer 2.0 User’s Guide in Chapter 3, Viewing System Information and Performance, or by typing show in the Windows console. If you have the SmartServer 2.0 or SmartServer 2.0 Update 1 firmware on your SmartServer 2.0, the firmware version number will be 4.04.088.
The following table summarizes the i.LON 100 e3 plus and SmartServer release history:
|
Number |
Date |
|
|
i.LON 100 e3 plus |
3.03 |
April 2008 |
|
i.LON 100 e3 plus SP1 |
3.04 |
December 2009 |
|
i.LON SmartServer |
4.00.136 |
January 2008 |
|
i.LON SmartServer SR1 |
4.01.012 |
March 2008 |
|
i.LON SmartServer SR2 and SP2 |
4.02.055 |
October 2008 |
|
i.LON SmartServer 2.0 |
4.03.123 |
October 2009 |
|
i.LON SmartServer 2.0 Update 1 |
4.03.123 |
January 2010 |
|
i.LON SmartServer 2.0 SP 1 |
4.04.088 |
August 2010 |
You can upgrade a SmartServer 2.0 Release 4.03 to Release 4.04 by installing SmartServer 2.0 SP1. SmartServer 2.0 SP1 is available as a free download at www.echelon.com/ilon. To upgrade a Release 4.03 installation to Release 4.04, follow these steps:
1. Mount the image as a virtual DVD using virtual DVD software such as CloneDrive or MagicDisc. If the SmartServer 2.0 SP1 setup application does not launch immediately, open the setup.exe file on the root directory of the Echelon i.LON SmartServer 2.0 SP1 DVD. The SmartServer 2.0 Service Pack 1 setup application main menu appears.
2. Click Install Products. The Install Products dialog appears.
3. Click Echelon i.LON SmartServer 2.0 Software SP1. The Echelon i.LON SmartServer 2.0 Software SP1 installer appears.
4. Follow the steps of the installation wizard. The installation will automatically upgrade the existing Echelon i.LON SmartServer 2.0 Software installation on your computer to Echelon i.LON SmartServer 2.0 SP1 Software.
5. Click the Echelon i.LON SmartServer 2.0 button in the taskbar to return to the i.LON SmartServer 2.0 installer, click Echelon i.LON SmartServer 2.0 Enterprise Services SP1 in the Install Products dialog, and then follow the on‑screen instructions. See Chapter 1 of the Echelon Enterprise Services 2.0 User’s Guide for more information on installing the EES 2.0 software.
6. Upgrade your SmartServer 2.0 firmware as described in the Echelon Enterprise Services 2.0 User’s Guide Chapter 2, Upgrading the SmartServer Firmware.
7. Follow the steps of the installation wizard. The installation will automatically upgrade the existing Echelon SmartServer 2.0 Enterprise Services Release 4.03 installation on your computer to Echelon SmartServer 2.0 Enterprise Services Release 4.04.
You can now create secure Web connections that use SSL encryption. See 7.1 Secure Web Binding 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 7.2 Battery Status 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)
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 Custom Datapoint Selector in the ReadMe document for i.LON Vision for documentation. (53258)
The following table summarizes problems fixed in this release. The EPR column lists Echelon internal problem tracking numbers.
|
EPR |
Description |
|
54793 |
If you added a data point that is a bound in a Web connection to an Alarm Generator, the Web connection stops functioning. |
|
54931
|
In an 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. |
|
54934 |
Commissioning a device in standalone mode dida not disable self‑installation. |
|
54935 |
Synchronization did not match external data points created in LNS with existing data points on the SmartServer that have the same name but are marked as deleted. |
|
54975 |
The Alarm Generator did not properly maintain the alarm condition for a data point when an analog comparison function was used. |
|
54980 |
Rebooting the SmartServer sometimes caused the Modbus driver to fail. |
|
55106 |
The following problems sometimes occured if the computer time was set to a local timezone 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. |
|
55107 |
In some cases you could not set the SmartServer system time. |
|
55175 |
The Data Logger SOAP Read Response message sometimes omitted some data log entries. |
|
55187 |
The scope of user‑defined network variable types (UNVTs) was sometimes incorrect. |
|
55201 |
In some cases the Data Logger leaked memory when reading data. |
|
55202 |
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. |
|
55912 |
In some cases, the Scheduler did not import an exception from the calendar when the UCPTindex property was not specified correctly. |
|
55915 |
In some cases a network monitor would cause the SmartServer to reboot. |
|
55918 |
A Modbus template sometimes caused a .NET application to fail. |
|
56386 |
Invalid time zone offsets in the system time sometimes caused the SmartServer to fail. |
|
56441 |
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. |
|
56445 |
Devices created and installed automatically from device templates sometimes did not have correct data point values initially. |
|
56549 |
The SmartServer Web interface sometimes failed with Firefox 3.6. |
|
56702 |
The SmartServer console application did not notify the user if the WebParams.dat file was missing. |
|
56714 |
You could not programmatically write data point values in raw hex format. |
|
56875 |
The Data Logger did not return correct UTF8 alias names in response to a data logger read function. |
|
56958 |
Auto-selected Smart Network Management settings caused current .APB and .XIF files to be overwritten. |
|
56984 |
You had to clear your browser’s cache after manually uploading .zip files to the SmartServer to update its image. |
|
57039 |
The Alarm Notifier’s nviAnEnable data point did not enable or disable the notification and data point update functions. |
|
57051 |
SMTP messages were sent using small (74 byte) packets, which caused overhead in network traffic. |
|
57092 |
Cinterion modems had incorrect AT commands. |
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.
You cannot use an intermediate SSL certificate to secure your SmartServer via HTTPS/SSL. Workaround: Create a self‑signed SSL certificate or obtain a direct‑signed SSL certificate. (54561)
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)
If you add a connection to or from a dynamic network variable from the SmartServer tree, the connection may not appear in a LonMaker drawing. Workaround: Use the LonMaker command to resynchronize the drawing to the LNS database. The connection is created correctly in the LNS database, and when you synchronize the connection will be added to the drawing. (57282)
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 Generator, a “No application response for '#8000010128000000[4].UFPTalarmNotifier" error message is displayed in the Web interface. Workaround: Configure an Alarm Generator, and then re-open these Web pages. (57045)
This section describes updates to the documentation.
When adding a remote SmartServer as described in Adding a Remote SmartServer to the LAN in the SmartServer User’s Guide, or when adding a Web connection as described in Adding a WebBinder Target Server to the LAN in the SmartServer User’s Guide, the box where you enter the HTTP port number has a new checkbox next to it that is labeled “SSL”. Select the SSL checkbox to create a secure Web connection. Enter the port number to use for the SOAP interface. By default, port 443 is used for SSL, but you can change to a different port if required for your installation. (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. You can use the battery status data point or indicator to determine when the internal SmartServer battery can no longer reliably maintain system time during a power outage. The default name for the datapoint is Net/VirtCh/iLON System/VirtFb/BatteryLevel. (57395)
Add the following paragraph to step 2 of the Configuring the Pulse Counter Application section in Chapter 9 of the i.LON SmartServer 2.0 User’s Guide:
The values stored in the nvoPcValue and nvoPCValueDif data points are sent when the time interval specified in step 3 expires or the value of the nviPcTrigger data point changes from off to on. (56568)
When discussing transferring files to a SmartServer, the documentation should recommend either using the new AdminServer component deployment feature or using an FTP client that provides reliable file transfers and that reports file transfer errors. Example reliable FTP clients that report errors include Core FPT, WS FTP Pro, and Cute FTP. Internet Explorer and Filezilla do not report errors and should not be used to transfer SmartServer image files or SmartServer apps. See the Echelon Enterprise Service ReadMe document for documentation of the new component deployment feature. (56847)
Echelon, LON, LonWorks, i.LON, LNS, and LonMaker are registered trademarks of Echelon Corporation in the U.S. and other countries.