Echelon SmartServer 2.0 SR2 and SP2 ReadMe
Release 4.04.119, February
2011
Copyright © 1998 –
2011 Echelon® Corporation
All Rights Reserved
This document describes SmartServer 2.0 Service Release 2 (SR2) and Service Pack 2 (SP2). SmartServer 2.0 SR2 is shipped with SmartServer 2.0 Energy Managers, and you can apply SmartServer 2.0 SP2 to update previous SmartServer 2.0 installations to the same version of the SmartServer software that is included with SmartServer 2.0 SR2. See Upgrading to SmartServer 2.0 SR2 or SP2 instructions on installing the update and verifying that it has been installed, and Fixes 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/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.
To provide full functionality, the SmartServer software must be used with Microsoft Internet Explorer 8 or newer, or Mozilla Firefox 3.0 or newer. If you are using a SmartServer 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 are available from www.echelon.com/downloads.
4 Upgrading to SmartServer 2.0 SR2 or SP2
5.1 Changes in Release SmartServer 2.0 SR2/SP2
5.1.1 Cinterion MC75 and MC63i Series Modem Support
5.1.3 Enhanced Authentication Security
5.1.4 Internet Explorer 9 Support
5.2 Changes in Release SmartServer 2.0 SP1
5.2.4 Chinese, Japanese, and Korean Language Support
5.2.7 Custom Datapoint Selector
6 Known Problems and Workarounds
6.1 Slow Commissioning for Street Light Networks
6.2 Incorrect Offline Reports for Street Light Networks
6.3 6-Byte Authentication Keys Fail with the SLB
6.4 Intermediate SSL Certificates not Supported
6.5 Persistent Synchronization Error Message
6.6 Misleading Alarm Notifier Error Message
6.7 Analog Functional Block (AFB) Reset Error
6.8 Disabled Security Web Page Cannot Be Enabled
7.3 Data Logger Input Data Point
7.4 Compressed Data Log File Format
This document applies to SmartServer 2.0 with Service Release 2 or Service Pack 2 software (Release 4.04.119). 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 [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 i.LON 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.0 User’s Guide in Chapter 3, 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:
|
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 SP2 |
4.04.119 |
February 2011 |
|
SmartServer 2.1 (streetlight system use only) |
4.05.094 |
October 2010 |
You can upgrade an i.LON 100 e3 plus or any prior release of the SmartServer to SmartServer 2.0 SR2 by installing the SmartServer 2.0 SR2 software from a SmartServer 2.0 SR2 DVD, or from a download provided by Echelon Corporation. You can update a prior version of the SmartServer 2.0 software to SR2 by downloading and installing SmartServer 2.0 SP2. SmartServer 2.0 SP2 is available as a free download at www.echelon.com/smartserver but can only be installed on a computer with a prior release of the 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.0 Software and the software will be provided to you as a software download. To upgrade to SmartServer 2.0 SR2 or SP2, follow these steps:
1. If you are installing SmartServer 2.0 SR2 from a SmartServer 2.0 SR2 DVD, insert the DVD into your DVD drive. If your computer does not have a DVD drive, insert the Echelon SmartServer 2.0 SR2 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.0 SR2 setup application does not start immediately, open the setup.exe file on the root directory of the Echelon SmartServer 2.0 SR2 DVD.
If you are installing SmartServer 2.0 SR2 or SP2 from a file that you downloaded from the Echelon website, extract all the files from the download file to a C:\SmartServer directory using a zip utility, and then open the setup.exe file in the SmartServer directory.
WARNING: On some computers, the setup application will not start if you extract the files to your user directory. Workaround: Extract the files to a C:\SmartServer directory, and then run the setup application. (58181)
2. The Echelon i.LON SmartServer 2.0 SR2 setup application main menu appears.
3. Click Install Products. The Install Products dialog appears.
4. Click Echelon i.LON SmartServer 2.0 Software SR2. The Echelon i.LON SmartServer 2.0 SR2 Software installer appears.
5. Follow the steps of the installation wizard. The installation will automatically upgrade the existing SmartServer software installation on your computer to Echelon i.LON SmartServer 2.0 SR2 Software. See Chapter 1 of the SmartServer 2.0 User’s Guide for more information on installing the SmartServer 2.0 software.
6. Click the Echelon i.LON SmartServer 2.0 SR2 button in the taskbar to return to the SmartServer 2.0 SR2 installer, click Echelon i.LON SmartServer 2.0 SR2 Enterprise Services in the Install Products dialog, and then follow the steps of the installation wizard. The installation will automatically upgrade the existing Echelon Enterprise Services (EES) installation on your computer to Echelon i.LON SmartServer 2.0 Enterprise Services SR2. See Chapter 1 of the Echelon Enterprise Services 2.0 User’s Guide for more information on installing the EES 2.0 software.
7. Update the bootrom to the SmartServer 2.0 SR2 version located in your LonWorks iLon100\images\BootROM 4.04 directory as described in Updating the Bootrom in Appendix B of the SmartServer 2.0 User’s Guide.
8. Upgrade to the SmartServer 2.0 SR2 firmware as described in Upgrading the SmartServer Firmware in Chapter 2 of the Echelon Enterprise Services 2.0 User’s Guide.
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 the Internet Explorer 9 Release Candidate. (59564)
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)
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 Custom Datapoint Selector in the ReadMe document for i.LON Vision for documentation. (53258)
The following table summarizes problems fixed in the SmartServer 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.
|
EPR |
Description |
|
33820 |
Time sometimes drifted multiple seconds per day. (2.0) |
|
43248 |
C# SOAP client reported an "underlying connection was closed" error. (2.0) |
|
50425 |
The Alarm Notifier: Summary Web page displayed obsolete active alarm entries after comments were changed. (2.0) |
|
50759 |
Reloading an app rebooted the SmartServer if more than one app was being developed. (2.0) |
|
50803 |
Calculation of daylight savings time (DST) did not work in the southern hemisphere. (2.0) |
|
50906 |
You could not write configuration properties when the SmartServer was using LNS management mode and the LNS Server was not attached to the network. (2.0) |
|
50962 |
A resource conflict between an external modem and the Modbus driver was reported, even if no modem was selected. (2.0) |
|
51380 |
The RS‑485 interface sometimes caused the SmartServer to reboot when Data+ and Data‑ lines were not connected correctly. (2.0) |
|
51516 |
Disabled SNTP synchronization was not re‑enabled after communication with the SNTP server was restored. (2.0) |
|
52392 |
Real‑time clock synchronization sometimes failed after switching to the backup SNTP server if the backup SNTP server also failed as well. (2.0) |
|
52794 |
Writes to Modbus multi-write coil registers sometimes failed. (2.0) |
|
53330 |
In 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. (2.0) |
|
54781 |
Scale labels with decimal values on the x-axis of the Data Point: View Web page trend graph were not rounded and displayed correctly. (2.0 SR2/SP2) |
|
54793 |
If you added a data point that is a bound in a Web connection to an Alarm Generator, the Web connection stopped functioning. (2.0 SP1) |
|
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. (2.0 SP1) |
|
54934 |
Commissioning a device in standalone mode did not disable self‑installation. (2.0 SP1) |
|
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. (2.0 SP1) |
|
54975 |
The Alarm Generator did not properly maintain the alarm condition for a data point when an analog comparison function was used. (2.0 SP1) |
|
54980 |
Rebooting the SmartServer sometimes caused the Modbus driver to fail. (2.0 SP1) |
|
55106 |
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. (2.0 SP1) |
|
55107 |
In some cases you could not set the SmartServer system time. (2.0 SP1) |
|
55175 |
The Data Logger SOAP Read Response message sometimes omitted some data log entries. (2.0 SP1) |
|
55187 |
The scope of user‑defined network variable types (UNVTs) was sometimes incorrect. (2.0 SP1) |
|
55201 |
In some cases the Data Logger leaked memory when reading data. (2.0 SP1) |
|
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. (2.0 SP1) |
|
55912 |
In some cases, the Scheduler did not import an exception from the calendar when the UCPTindex property was not specified correctly. (2.0 SP1) |
|
55915 |
In some cases a network monitor would cause the SmartServer to reboot. (2.0 SP1) |
|
55918 |
A Modbus template sometimes caused a .NET application to fail. (2.0 SP1) |
|
56386 |
Invalid time zone offsets in the system time sometimes caused the SmartServer to fail. (2.0 SP1) |
|
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. (2.0 SP1) |
|
56445 |
Devices created and installed automatically from device templates sometimes did not have correct data point values initially. (2.0 SP1) |
|
56549 |
The SmartServer Web interface sometimes failed with Firefox 3.6. (2.0 SP1) |
|
56702 |
The SmartServer console application did not notify the user if the WebParams.dat file was missing. (2.0 SP1) |
|
56714 |
You could not programmatically write data point values in raw hex format. (2.0 SP1) |
|
56844 |
Modbus writes within a short interval were not aggregated. (2.0 SP1) |
|
56875 |
The Data Logger did not return correct UTF8 alias names in response to a data logger read function. (2.0 SP1) |
|
56944 |
Some operations were very slow in IE8. (2.0 SP1) |
|
56958 |
Auto-selected Smart Network Management settings caused current .APB and .XIF files to be overwritten. (2.0 SP1) |
|
56984 |
You had to clear your browser’s cache after manually uploading .zip files to the SmartServer to update its image. (2.0 SP1) |
|
57039 |
The Alarm Notifier’s nviAnEnable data point did not enable or disable the notification and data point update functions. (2.0 SP1) |
|
57051 |
SMTP messages were sent using small (74 byte) packets, which caused extra overhead in network traffic. (2.0 SP1) |
|
57092 |
Cinterion modems had incorrect AT commands. (2.0 SP1) |
|
57101 |
NV indexes were sometimes not updated correctly after the program ID for a device changed. (2.0 SP1) |
|
57161 |
Deleting a virtual functional block sometimes corrupted references from other functional blocks to datapoints referenced by the virtual functional block. (2.0 SR2/SP2) |
|
57332 |
The Device Overview Web page sometimes did not display devices discovered by subsequent scans. (2.0 SR2/SP2) |
|
57282 |
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. (2.0 SR2/SP2) |
|
57526 |
An unnecessary index number was sometimes added to a data point name after the name was changed. (2.0 SP1) |
|
57726 |
The Scheduler SOAP Read Response message sometimes did not include events created at midnight. (2.0 SR2/SP2) |
|
57856 |
A Web Binding Target service could not be added to an LNS Proxy host device in the SmartServer Web interface. (2.0 SR2/SP2) |
|
57937 |
Creating an Exception Schedule in the Scheduler sometimes caused the SmartServer to reboot. (2.0 SR2/SP2) |
|
57971 |
The M-Bus driver failed when the SmartServer was rebooted. (2.0 SR2/SP2) |
|
58279 |
Web connections with file attachments failed with some Web servers for files larger than 4 Kbytes. (2.0 SR2/SP2) |
|
58329 |
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. (2.0 SR2/SP2) |
|
58345 |
Offline Modbus devices sometimes caused a memory leak. (2.0 SR2/SP2) |
|
58441 |
Fields of structured data types within arrays could not be formatted correctly. (2.0 SR2/SP2) |
|
58442 |
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. (2.0 SR2/SP2) |
|
58601 |
The Setup – Security Web page could not be opened sometimes. (2.0 SR2/SP2) |
|
58737 |
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. (2.0 SR2/SP2) |
|
58863 |
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. (2.0 SR2/SP2) |
|
58864 |
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. (2.0 SR2/SP2) |
|
58931 |
The SmartServer sometimes queued too many SOAP requests causing excessive SmartServer CPU usage. (2.0 SR2/SP2) |
|
58945 |
No error was displayed when the SmartServer did not have enough RAM for the deletion of data and alarm log entries. (2.0 SR2/SP2) |
|
58969 |
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. (2.0 SR2/SP2) |
|
58989 |
The Data Logger did not record data point string values containing the embedded ‘>’ and ‘<’ characters. (2.0 SR2/SP2) |
|
59012 |
The Alarm Notifier: Summary Web page stopped polling if you navigated away from it. (2.0 SP1) |
|
59013 |
Opening the Configure – Data Point Web page for some data points caused the SmartServer Web interface to fail. (2.0 SR2/SP2) |
|
59021 |
The Alarm Notifier could fail and cause the SmartServer to reboot. (2.0 SR2/SP2) |
|
59024 |
The Real Time Clock SOAP Set Request message expired if received before time change and processed thereafter. (2.0 SR2/SP2) |
|
59048 |
The Data Logger: View Web page displayed only one value once the Web page’s cache overflowed. (2.0 SR2/SP2) |
|
59072 |
The Data Logger SOAP Read Response message does not include data from compressed (.gz) log files. (2.0 SR2/SP2) |
|
59075 |
The SVG trend graphs in the Data Logger and Alarm Notifier View Web pages did not function with Microsoft Internet Explorer 9. |
|
59083 |
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. (2.0 SR2/SP2) |
|
59111 |
The Data Logger SOAP Read Response message did not return data in the frequency specified by the poll rate. (2.0 SR2/SP2) |
|
59117 |
The Data Logger log files included multiple entries for the same update. (2.0 SR2/SP2) |
|
59533 |
The SmartServer would sometimes permanently fail to start the SmartServer applications if a power sag occurred during the boot process. (2.0 SR2/SP2) |
|
59596 |
Dynamic data points required for apps were sometimes deleted after a reboot. (2.0 SR2/SP2) |
|
59613 |
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. (2.0 SR2/SP2) |
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.
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’s 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 2.0 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)
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 Street Light Bridge (SLB). Workaround: Always specify a 12-byte authentication key for networks that use the Echelon Street Light Bridge. (57993)
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) 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)
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)
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)
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 2.0 User’s Guide, or when adding a Web connection as described in Adding a WebBinder Target Server to the LAN in the SmartServer 2.0 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)
In the Selecting and Configuring Data Points section in Chapter 8 of the SmartServer 2.0 User’s Guide, change the “You can set this property to On Change so that the data point is logged only when its value changes” statement to “You can set this property to On Change so that the data point is logged only when its value or its state changes”.
In the Selecting and Configuring a Log File section in Chapter 8 of the SmartServer 2.0 User’s Guide, the following information needs to be added to the second bullet in step 2 regarding compressed data log files (the CSV ‑ zipped format [.csv .gz extension]):
Removing a data point from a compressed data log or deleting a specific interval within a compressed data log will decompress the log file. If the SmartServer does not have enough memory to store a decompressed log file in RAM, it will not allow the action that would cause the log file to be decompressed, and it will report an error in the system logger. Always ensure that there is enough free space in the SmartServer RAM to decompress the log file when removing data points or portions of a compressed data log. Following are estimates of the RAM required to decompress a log file:
· CSV/text. Approximately 2 times the size of the log file.
· CSV ‑ zipped. Approximately 10–20 times the size of the log file.
· Binary. Approximately 20–30 times the size of the log file.
Generally, log files should be no larger than 1 MB.
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)
The description of the Suppress Event Recovery option in the SmartServer 2.0 User’s Guide is incorrect. Following is the corrected description:
If the Suppress Event Recovery check box is set the Scheduler maintains the existing data point value until the next scheduled event when the SmartServer is rebooted, the system time is changed, or a data point’s priority is reset at the end of a one-time exception. This enables the SmartServer to maintain the current value stored in the data point if the data point has been overridden by another application. You can clear the Suppress Event Recovery check box so that when the SmartServer is rebooted, the system time is changed, or a data point’s priority is reset at the end of a one-time exception, the Scheduler will attempt to restore the values and priorities of the selected input points by searching for the most recent past event and executing it. Ultimately, the Scheduler exclusively determines the value of each selected input point (as long as it has the highest priority assigned to the data point). (57661)
The following information supplements the SmartServer documentation concerning transferring files to a SmartServer: To transfer files to the SmartServer, you can use either the new AdminServer component deployment feature or use an FTP client that provides reliable file transfers and that reports file transfer errors. Example reliable FTP clients that report errors include Core FTP, 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)
The text description of terminals 9, 10, 11, and 12 on page 14 of the SmartServer 2.0 Hardware Guide is incorrect, reversing the positive and negative terminals. The table on page 15 and the marking on the SmartServer hardware is correct. (54022)
Echelon, LON, LonWorks, i.LON, LNS, and LonMaker are registered trademarks of Echelon Corporation in the U.S. and other countries.