i.LON® 100 e3 and e3 plus Internet Server ReadMe File
Release e3 Service Pack 4, February 2010

Copyright © 2002 – 2010 Echelon Corporation
All Rights Reserved

1       Introduction

This file describes i.LON 100 e3 and e3 plus with Service Pack 4 (version 3.04.014).  You can create this version by applying i.LON 100 e3 Service Pack 4 (SP4) to an existing i.LON 100 e3 or i.LON 100 e3 plus, or to an i.LON SmartServer or SmartServer 2.0 that has been downgraded to the e3 plus image.  This service pack is delivered as a self-extracting executable file and requires a previous installation of the i.LON 100 e3 or e3 plus software to be present on your computer.  You can install i.LON 100 e3 Service Pack 4 over any existing i.LON 100 e3 (V3.0) installation, such as e3, e3 SP1, e3 SR1, e3 SP2, e3 SR2, e3 SP3, e3 SR3, or e3 plus installation, or to any SmartServer installation that has been downgraded to an e3 plus.  This service pack will not upgrade a Release 1 (V1.00) or Release e2 (V1.10) installation.  

To simplify upgrading an existing i.LON 100 server, use the Upgrade utility provided in the i.LON 100 Configuration Utility Plug-In to upgrade the i.LON 100 server.  The upgrade utility downloads only the needed firmware files, and avoids overwriting the IP and LonWorks® network configuration.

The i.LON 100 Internet Server Configuration Utility Plug-In and Web pages must be used with the latest Microsoft Internet Explorer and Echelon LNS® and LonMaker® service packs.   If you are using LNS 3 (not LNS Turbo or LNS FX), you must install LNS 3 Service Pack 8 Update 1(V3.08.05) or newer.  If you are using LonMaker 3.1 (not LonMaker Turbo or LonMaker FX), you must install LonMaker 3.1 Service Pack 3 Update 1 (V3.13.10) or newer.  LNS 3 Service Pack 8 Update 1 is installed automatically if needed.  LNS and LonMaker service packs are also available from www.echelon.com/downloads.  

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 i.LON product.  See Echelon’s Knowledge Base at www.echelon.com/support for answers to frequently asked questions.

2       Contents

1        Introduction  1

2        Contents  1

3        i.LON 100 Release History  2

4        Identifying your i.LON 100 Release  2

5        Installing the Service Pack  3

6        Installing the Bootrom   4

7        Downgrading an i.LON SmartServer 5

8        Removing Release 3.04  5

9        Release 3.04 Fixed Problems  5

10     Fixed Problems from Previous Service Packs and Updates  6

11     Known Problems and Workarounds  10

12     Documentation Updates  11

13     Software License Agreement 11

3        i.LON 100 Release History

Software (limited distribution releases shown in italics)

Release

Date

i.LON 100 Internet Server Release 1

1.00.52

November 2002

i.LON 100 Internet Server Service Pack 1 (V1.01)

1.01.01

April 2003

i.LON 100 Internet Server Service Pack 2 (V1.02 SP1)

1.02.06

December 2003

i.LON 100 Internet Server Service Release 2 (V1.02.06)

1.02.06

January 2004

i.LON 100 Internet Server Service Pack 2 Update 1 (V1.02 U1)

1.02.07

January 2005

 

 

 

i.LON 100 e2 Internet Server

1.10.90

September 2004

i.LON 100 e2 Internet Server Update 1 (V1.10 U1)

1.10.94

January 2005

i.LON 100 e2 Internet Server Service Pack 1 (V1.10 SP1)

1.11.15

March 2005

i.LON 100 e2 Internet Server Service Pack 1 Update 1 (V1.11 U1)

1.11.20

September 2005

i.LON 100 e2 Internet Server Service Pack 1 Update 2 (V1.11 U2)

1.11.20

October 2005

 

 

 

i.LON 100 e3 Internet Server

3.00.61

September 2005

i.LON 100 e3 Internet Server Service Pack 1 (V3.00 SP1)

3.01.09

December 2005

i.LON 100 e3 Internet Server Service Release 1 (V3.01.09)

3.01.09

December 2005

i.LON 100 e3 Internet Server Service Pack 1 Update 1 (V3.01 U1)

3.01.12

February 2006

i.LON 100 e3 Internet Server Service Pack 2 (V3.00 SP2)

3.02.07

April 2006

i.LON 100 e3 Internet Server Service Release 2

3.02.07

April 2006

i.LON 100 e3 Internet Server Service Pack 2 Update 1 (V3.02 U1)

i.LON 100 e3 Internet Server Service Pack 2 Update 2 (V3.02 U2)

i.LON 100 e3 Internet Server Service Pack 2 Update 3 (V3.02 U3

i.LON 100 e3 Internet Server Service Pack 2 Update 4 (V3.02 U4)

i.LON 100 e3 Internet Server Service Pack 2 Update 5 (V3.02 U5)

3.02.07**

3.02.07**

3.02.07**

3.02.20

3.02.21

June 2006

December 2006

December 2006

February 2007

August 2007

i.LON 100 e3 Internet Server Service Pack 3 (V3.03 SP3)

3.03

April 2008

i.LON 100 e3 Internet Server Service Release 3

3.03

April 2008

i.LON 100 e3 Internet Server Service Pack 4 (V3.04 SP4)

3.04

February 2010

 ** Note: These releases include version 3.02.09 of the i.LON 100 Configuration Plug-in.           

4       Identifying your i.LON 100 Release

This ReadMe document applies to i.LON 100 e3 and e3 plus Release 3.04.  You can determine whether or not you have the Release 3.04 firmware installed on an i.LON 100 server, as well as any updates to that release that may be installed.  To determine the firmware version running on your i.LON 100 server, follow these steps:

1.     If you have copied any updated firmware files to your i.LON 100 server, reboot it before checking the version number.  See the final step of Installing the Service Pack for information on how to reboot an i.LON 100 server.  You can tell the i.LON 100 has been rebooted when the green Power/Wink LED on the i.LON 100 server stops blinking and stays on.

2.     Enter your i.LON 100 server’s address in Internet Explorer (7.0 or newer). 

3.     Click the Login button.

4.     Enter your user name and password when prompted.  By default this is ilon and ilon, but you may have changed them.

5.     The first digit of the version number displayed at the bottom of the first page will be 3 if you have an i.LON 100 e3 server, and you should apply this service pack if you have any version starting with 3.00, 3.01, 3.02, or 3.03.  If the version number starts with 1.00, 1.01, 1.02, 1.10, 2, or 4 you have an i.LON 100 server that cannot be directly updated with i.LON 100 e3 Service Pack 4.

If you have an i.LON SmartServer (4.00, 4.01, or 4.02) or i.LON SmartServer 2.0 (4.03 or higher) and you wish to downgrade that system to run the e3 software, see Downgrading an i.LON SmartServer.

Note:

This release supplies an updated bootrom.  If you have an older version of the bootrom you can install this updated bootrom to update the flash disk driver for improved reliability and diagnostics.  See Installing the Bootrom  for instructions on how to install the bootrom update.  Do not install this updated bootrom if your bootrom is newer than Release 3.04.

5       Installing the Service Pack

You can install the i.LON 100 e3 Service Pack 4 over an existing i.LON 100 e3, e3 SP1, e3 SR1, e3 SP2, e3 SR2, e3 SP3, or e3 SR3 installation.  This service pack will not upgrade a Release 1 (V1.00), i.LON 100 e2 (V1.10), SmartServer (V4.00, V4.01, or V4.02), or SmartServer 2.0 (V4.03) installation. 

To install i.LON 100 e3 Service Pack 4, follow these steps:

1.     Check www.echelon.com/ilon for the latest i.LON service pack and updates.  See the installation instructions included with the service pack or update for more information.

2.     Verify that you have the i.LON 100 e3 software installed on your computer.  This update will not work with other i.LON 100 server releases, and will cause them to quit functioning if applied.  If you are downgrading a later release of the i.LON server, see Downgrading an i.LON SmartServer.

3.     Use an FTP client such as Internet Explorer to backup a copy of all files on your i.LON 100 to another computer, or use the Backup option in the i.LON 100 Configuration Plug-In.

4.     Download iLON100_e3SP4.exe file from Echelon’s Web site to any directory on your computer.

5.     Browse to and run the iLON100_e3SP4.exe file.

6.     Insert the original i.LON 100 e3 (V3.00) CD-ROM in the CD-ROM drive of your computer if prompted.  The service pack installation may not complete correctly if the original e3 installation media is inaccessible.

7.     Complete the installation on your computer.  In most cases, you can accept all defaults.  The installation software creates a V3.04 images directory in your i.LON 100 e3 installation directory. 

8.     Update the i.LON 100 firmware.  You can do this in two ways:

·       Start the i.LON 100 Configuration Utility Plug-In.  The procedure varies depending on which LonWorks installation tool you are using.  For example, if you are using the LonMaker Integration Tool, you can right-click an i.LON 100 e3 device or functional block shape, click Configure on the shortcut menu, and then enter the IP address of your i.LON 100 server.

Click the Tools menu, and then click Update to update the i.LON 100 firmware.  The upgrade utility downloads only the changed files to the i.LON 100 server, which is sometimes an advantage for modem users.

·       Use an FTP client such as Internet Explorer to copy the updated firmware files from your <LonWorks directory>\iLON100\Images\iLON100 3.03 directory to the /root/ directory on your i.LON 100 server.  If you are using the Internet Explorer FTP client, the “/root” portion of this path is hidden.  The <LonWorks directory> is c:\LonWorks by default.  See the i.LON 100 e3 documentation for the correct procedure before doing this upgrade—in general you will not want to overwrite all of the files in the root, config, and ltConfig directories in order to avoid losing your IP and LonWorks network configuration.

9.     If you have any existing designs with Pulse Counter functional blocks, delete any connections to the pulse counter outputs prior to upgrading the Pulse Counter functional blocks.  Restore the type of the output network variable after an upgrade and recreate the connections.

10.  Reboot your i.LON 100 server from the Setup > Reboot Web page.  To access the Web page, enter your i.LON 100 e3 server’s address in Internet Explorer (7.0 or newer).  Click the Service button and enter the user name and password when prompted.  By default these are ilon and ilon, but you may have changed them.  Click Setup and then click Reboot.  In the Reboot Web page, click the Reboot button to reboot your i.LON 100 server.

Alternatively, you can enter the reboot command in the Console application, or you can cycle the power to your i.LON 100 server.

11.  To update the bootrom, use an FTP client to copy the bootrom.upd file from the <LonWorks directory>\iLON100\Images\BootROM 3.04 directory on your computer to the i.LON 100 root directory.  Next, type update bootrom at the i.LON 100 console from a terminal application connected to the console port or a Telnet connection. After the update is complete the i.LON 100 server will reboot.

12.  Start Internet Explorer and clear the browser cache (Tools > Internet Options > Delete Files).

13.  Test that you can login to the i.LON 100 server.

6       Installing the Bootrom

You can install a new e3 bootrom image in your i.LON 100 server if your i.LON 100 server currently has a bootrom older than V3.04.  The bootrom image loads the i.LON firmware from the i.LON 100 server flash disk when the i.LON 100 server powers-up or is rebooted.  You can install the e3 Service Pack 4 bootrom image on an i.LON 100 1, e2, or original e3 (hardware revision 2) to take advantage of the improved SP4 flash disk driver.  The updated bootrom is already installed on i.LON 100 e3 plus servers and i.LON SmartServers.  To install the e3 Service Pack 4 bootrom update, follow these steps:

1.     Using an FTP client, copy the Service Pack 4 bootrom.upd file from the <LonWorksDirectory>\iLon100\images\BootROM folder on your computer to the i.LON 100 root folder.

2.     Connect a serial cable between your computer and the i.LON 100 console port.

3.     Start a terminal emulator such as Windows HyperTerminal and open the console application on the i.LON server.  If you are using Windows 7 or Windows Vista, HyperTerminal is not included.  You can use a third-party terminal emulator such as PuTTY.  Set the serial interface settings to 9600 bps, 8 bits, no parity, 1 stop bit, and no flow control. See the i.LON 100 Hardware Guide for more information on the console interface.

4.     Enter the update bootrom command in the console application.  If you renamed the bootrom file to something different than the default (bootrom.upd), specify the actual file name as an additional parameter.

5.     If you are installing the bootrom on an i.LON 100 1, e2, or original e3, when the bootrom update has been completed, your i.LON 100 is automatically rebooted.  If you are installing the bootrom on an i.LON 100 e3 plus or SmartServer, the i.LON server will not automatically reboot.  In this case, manually reboot the i.LON server.  When the console reads “Press the ‘!’ key to stop auto-boot”, press ‘!’.  The i.LON server will stop in the bootrom console.  The flash disk may fail to mount properly, and may display errors. This is expected, and is not a problem.

6.     If you are not installing the bootrom on an i.LON 100 e2, format the flash disk with the format console command.  The i.LON 100 server will automatically reboot and again stop in the bootrom console, but this time the flash disk should be mounted successfully.

7       Downgrading an i.LON SmartServer

You can downgrade an i.LON SmartServer or i.LON SmartServer 2.0 to run the i.LON 100 e3 firmware.  To downgrade an i.LON SmartServer or i.LON SmartServer 2.0, follow these steps:

1.     If you do not already have a computer with the i.LON 100 e3 software installed, install the i.LON 100 e3 software from the i.LON 100 e3 CD. 

2.     If you have not already installed i.LON 100 e3 SP4 on your computer, download and install i.LON 100 e3 SP4 from www.echelon.com/downloads as described in Installing the Service Pack.

3.     Format the flash disk with the format console command.

4.     Using an FTP client, copy the i.LON 100 e3 firmware to the i.LON SmartServer or SmartServer 2.0.

5.     Restore factory defaults with the factorydefault console command. This will cause the i.LON server to reboot.

6.     When the reboot is complete, the i.LON server will be running the e3 firmware.

7.     Configure the i.LON server as you would a new i.LON 100 e3 plus server.

8       Removing Release 3.04

You can remove Release 3.04 from your computer using the standard Windows Add or Remove Programs control panel application. To remove Release 3.04 from an i.LON 100 server, use an FTP client to remove Release 3.04 and re-load the i.LON 100 server with a different release.

9       Release 3.04 Fixed Problems

This section describes the problems fixed and other changes in Release 3.04.  Numbers in parentheses at the end of the descriptions are Echelon's internal problem tracking IDs.

1.     The Setup – Time Web page does not display the timezone if you load a new firmware image, even if one has previously been defined on the e3 server. (49646)

2.     The Version 13.00 LonMark resource files are not included. (50473)

3.     If you add to a data logger a data point that uses a RAW_HEX value and has the Use Send On Delta property enabled and set to 1, a *FATAL* Exception vector #2 in task \\"dataServer\"\"" may occur.  (50876)

4.     The RS-485 interface may cause the e3 server to reboot if the Data+ and Data- lines are not connected correctly.  (51414)

5.     Setting the Max Age (Lifetime) property of a data point to 0 seconds does not cause the data server to poll the data point. (52051)

6.     IP forwarding and ICMP timestamps are not disabled, which may expose the e3 server to potential security breaches. (54148)

7.     The real-time clock cannot be synchronized when no SNTP time server is defined or both primary and secondary SNTP time servers fail. (54188).

8.     Synchronization to the real-time clock may fail if you switch to a backup SNTP time server that subsequently fails.  (54611)

9.     If you open and close multiple Telnet sessions on the e3 server, a *FATAL* Exception vector #2 in task \\"telnetInact\"\"" may occur. (54679)

10.  Daylight saving time (DST) is not calculated correctly for southern hemisphere.  (54693)

11.  The e3 server can be rebooted via Telnet without login credentials being entered. (54983)

12.  When the i.LON 100 server is reloading modules, a *FATAL* Exception vector #2 in task "Builder::worker" may occur. (55010)

13.  If you try to create a one-time exception in the New One-Time Scheduler Exception dialog on the same date as an existing one‑time exception in a different scheduler, a JavaScript exception occurs. (55940)

14.  i.LON Vision fails if it is installed on a computer that has both Adobe Contribute CS3 and CS4 installed on it. (56310)

15.  When you open the Configure – Event Scheduler - Exception Schedules Web page, it either requires approximately two minutes to become enabled or it fails. (56312)

16.  You cannot install the e3 software in a directory other than the C:\LonWorks folder.  (54914)

10  Fixed Problems from Previous Service Packs and Updates

This service pack and service release includes fixes from all previous e3 service packs and updates. These include the fixes for the problems listed in this section.  Names in brackets identify the service pack and update—where applicable—where the fix or change first appeared.

1.     [SP3U3] When a UCPTalarmStatus data point is changed, the change is not written correctly to the log. (48738)

2.     [SP3U3] Substitutions in alarm text work in an e-mail message but not in the alarm summary view. (48715)

3.     [SP3U3] An Alarm Notifier sometimes sends an alarm e-mail message with the data point value in place of the preset name. (46054)

4.     [SP3U3] An Alarm Notifier sometimes sends an alarm e-mail twice when a data point goes offline. (45517)

5.     [SP3U3] A scroll bar was missing in the Alarm Notifier configuration Web page. (40074)

6.     [SP3U3] A Calendar ignores an exception when the exception follows an exception that occurred in the past. (48719)

7.     [SP3U3] A Scheduler sometimes ignores the effective period on startup. (48615)

8.     [SP3U3] An exception occurs if you add an exception outside the effective period in a Scheduler. (48703)

9.     [SP3U3] A Data Logger status data point reports incorrect status after clearing the log. (48717)

10.  [SP3U3] A Type Translator with no delay does not calculate all values when the output of Rule[n] is the input of Rule[n+1]. (48788)

11.  [SP3U3] A Type Translator output is always OC_OCCUPIED whenever the SNVT_lev_disc_TO_SNVT_occupancy type translator rule is used. (48718)

12.  [SP3U3] A Type Translator cannot break up a structured network variable with a format modifier (such as #US or #SI). (48716)

13.  [SP3U3] A data server SOAP interface sometimes reports the offline state for data points updated by a Type Translator which splits a structured network variable. (48664)

14.  [SP3U3] If a Type Translator receives an update on its input with the same value as the previous one, the output NV is not propagated on the LonWorks network. (45743)

15.  [SP3U3] A minimum poll interval for an i.LON Vision Web page can now be specified in the Start.htm file of the user directory with the top.poll_interval parameter.(45908)

16.  [SP3U3] The i.LON Vision software did not work with Adobe Contribute 4. (42762)

17.  [SP3U3] LonTalk applications are not started if the i.LON server does not get an IP address from the DHCP server at startup. (48763)

18.  [SP3U3] Pulse dialing does not work with a modem. (48705)

19.  [SP3U3] The timeout for a wireless M-Bus data request is too short. (48700)

20.  [SP3U3] M-Bus IDs were sometimes overwritten with zero values. (45892)

21.  [SP3U3] The ManId, VersionId and MediumId fields are not set correctly on the M-Bus configuration page when changing the M-Bus address. (45979)

22.  [SP3U3] A very large Modbus data point can cause a crash. (48679)

23.  [SP3U3] The Modbus driver wrote a zero value to a data point when a Modbus error is received. (45160)

24.  [SP3U3] Daylight savings time updates were required. (48612, 48425, 48739, 48210)

25.  [SP3U3] SMTP authentication sometimes fails. (48227)

26.  [SP3U3] The default gateway was not set correctly if a DHCP server cannot be contacted. (48172)

27.  [SP3U3] The .local domain could not be used. (46835)

28.  [SP3U3] Acknowledged data points going from the i.LON server to devices that go offline stay offline even with heartbeats to devices that come back online. (46600)

29.  [SP3U3] The bootrom did not respond correctly to routed IP traffic. (46093)

30.  [SP3U3] Login sometimes failed. (45916)

31.  [SP3U3] The LonTalk stack sometimes deadlocks when more than 50 inbound group connections exist to the i.LON server. (44367)

32.  [SP3U3] The minimum send time was not honored for Web connections. (43492)

33.  [SP3U3] The namespace in a SOAP request was not recognized correcting if it was not specified in first attribute. (42992)

34.  [SP3U3] The installer did not work correctly with Microsoft Windows Vista. (48004)

35.  [SP3U3] The LNS Turbo Service Pack 2 prompted for the installation CD. (42924)

36.  [SP2U5] A computer with Microsoft Update KB936021 could not access the i.LON 100 Web pages using IE6 or IE7 the second time this access was attempted.  (45916)

37.  [SP2U4] Infrequently, single i.LON 100 vision objects were not updated. (42892)

38.  [SP2U4] NVCs were not listed for compare data points when used on the AFB block. (43141)

39.  [SP2U4] GPRS external modems could experience "PDP Loss of Context" unless the i.LON 100 server periodically pinged a fixed IP address specified by the telecommunications infrastructure provider.  A verification application has been added to the Connection Manager.  This application must be manually configured by editing the startup script (/config/Startup.scr). Specifically, the command 'fnCM_SetPersistentConnectionChecker' must be called immediately after the line “fnStartModule “iLon100Main”. The line that must be added to Startup.scr immediately after the fnStartModule “iLon100Main” line is as follows: (43132)

fnCM_SetPersistentConnectionChecker <Host>, <Verification Interval>, <Retries>, <Retry Interval>, <Service>

<Host>: Hostname or IP address of the server

<Verification Interval>: The interval after the i.LON 100 verifies the connection (Default 1 hour)

<Retries>: The i.LON 100 retries the verification if it fails (Default: 10)

<Retry Interval>: The time between the retries (Default: 1 minute)

<Service>:  -1: use PING (ICMP) only; 0: (default) use PING and HTTP (Port 80); 80: Use HTTP only

40.  [SP2U4] The e3 software needed a software watchdog timer which logs a timeout imminent message to eventlog.txt and to the new watchdoglog*.txt files at the point in time when the hardware watchdog timer is about to expire and reboot a locked-up system. (43115)

41.  [SP2U4] When you choose Delete When Expired in the advanced section of a Scheduler exception, the Scheduler did not delete the exception correctly after the date had expired, but the Calendar did. (43099)

42.  [SP2U4] The MODBUS (J-Bus) driver needed to support the full address range for devices 1-255, not just 1-127. (43090)

43.  [SP2U4] The e3 iLonSystem and bootrom.upd needed an update to support flexible memory configurations. (42928, 43130)

44.  [SP2U4] Daylight Savings Time start and stop dates needed to be changed in March 2007.  See http://support.microsoft.com/kb/928388. (42816)

45.  [SP2U4] The user could not add new MBUS points after a reboot when the index was not given. (42620)

46.  [SP2U4] The i.LON 100 needed to assign the size of changeable type NVs at boot time; otherwise, devices such as the pulse counter could stop functioning on a reboot. (42024)

47.  [SP2U4] The M-Bus driver could deliver the wrong data length due to an occasional error in the data processing algorithm. (41902)

48.  [SP2U4] The Modbus configuration Web page showed the wrong size for coils (32 bits, instead of 1 bit). (41729)

49.  [SP2U4] In Alarm Notifier e-mails, the e-mail source address could be missing, even though it had been explicitly added. (41268)

50.  [SP2U4] The e2 SOAP namespace (V1.10) SOAP header format was different when running on an e3 than when running on an e2. (41020)

51.  [SP2U4] Under certain circumstances the index of a new M-Bus device was not correctly calculated and adding a new device would fail. (40838)

52.  [SP2U4] In the Modbus driver it was impossible to use a 7 bit data length in RS-232C mode. (40789)

53.  [SP2U4] An improved i.LON 100 Vision tutorial has been made available in Chapter 13 of http://www.echelon.com/Support/documentation/manuals/cis/078-0310-01B.pdf. (43131)

54.  [SP2U4] It was impossible to get i.LON 100 Vision to work with Adobe Contribute 4. (42762)

55.  [SP2U3] The pulse counter input could cause random crashes anywhere in the system. The problem became worse when the pulse input frequency was increased. (42922)

56.  [SP2U2] In the configuration plug-in, an i.LON 100 which used a password-protected WSDL file could not be accessed. (42915)

57.  [SP2U1] In the plug-in, under calendar, certain exception details could not be selected and only three of the six options were available.  (41032)

58.  [SP2U1] In the configuration plug-in, only the default Web port numbers could be entered, although the documentation stated otherwise.  (41450)

59.  [SP2] Data could become lost or corrupted in the flash disk. (40805, 40538, 40332)

60.  [SP2] Under heavy bi-directional LonTalk traffic, uplink messages could be delayed by 3 seconds or more. (40358)

61.  [SP2] In certain circumstances the Alarm Notifier cleared acknowledged alarms if an SNTP server was configured. (40471)

62.  [SP2] The Microsoft SOAP toolkit has been updated to V3.0 in order to avoid warnings that occurred when running the latest Windows Updates. (40463)

63.  [SP2] LonMaker 3.13 Update 2 could not be installed on computers that did not have an Internet connection. (40418)

64.  [SP2] The Astronomical Position Sensor (APS) generated imprecise values for the elevation angle, especially at small angles or certain days of the month. (40544)

65.  [SP2] The Event Scheduler could update a snvt_tod_event data point without a scheduled entry at 12:00, if SNTP was active and the time was changed. (40473)

66.  [SP1 U1] Ill-behaved Web clients could cause the Web server to lockup or terminate. (40063 and 40062)

67.  [SP1 U1] SOAP Applications that worked on an e2 i.LON 100 no longer worked on an e3 i.LON 100 due to a missing tag error.  (39792)

68.  [SP1 U1] Under extreme conditions the flash disk structure could become corrupted. (40011)

69.  [SP1 U1] The Analog Function Block configuration for UCPTthreshold could be corrupted after rebooting.  (39751)

70.  [SP1 U1] The Event Scheduler Web page could intermittently fail to show all events as the user clicked on various elements and dates on the page. (40042)

71.  [SP1 U1] Unable to Configure Event Scheduler calendar exception to specify the Every Fifth Day of the Year option. (39888)

72.  [SP1 U1] Alarm Summary Web page shows passive alarms after reboot although Clear and Ack Required flag is not set. (40073)

73.  [SP1 U1] Alarm Summary doesn't show current alarm status. (40095)

74.  [SP1] Installer doesn't work with Contribute 3.11. (39089)

75.  [SP1] Web pages fail to start properly if a sidebar page is created manually. (39301)

76.  [SP1] ResetPrio object has inconsistent behavior. (39238)

77.  [SP1] User should be able to reset DP prio by click to the green hand icon. (38911)

78.  [SP1] Green hand is not removed after resetting priority if an alarm generator uses the respective data point. (38938)

79.  [SP1] A top-level menu bar item without sub items cannot be followed by one with sub items. (38556)

80.  [SP1] An attempt to add a layer from Contribute causes a "value.trim is not a function" JavaScript error. (39176)

81.  [SP1] Modbus timeouts are not detected (or not handled) in the Web pages. (38565)

82.  [SP1] No root item in the Navigation tree. (38623)

83.  [SP1] FTP abort (ABOR) command handled improperly. (39257)

84.  [SP1] Passive FTP from a Contribute client fails. (38929)

85.  [SP1] Run time error and misbehavior when switching between menu items. (38558)

86.  [SP1] The message box is not cleared after "Please wait, connecting to Web service". (38557)

87.  [SP1] Modbus cannot select RS232 port. (39193)

88.  [SP1] Modbus data point format type setting problems in the Format Description field. (38494)

89.  [SP1] Modbus data points are online even if the Modbus device is not connected. (38522)

90.  [SP1] Modbus device address 0 is illegal and should be avoided. (38896)

91.  [SP1] Modbus DP data point with the wrong length is created from the Web page. (39041 and 38479)

92.  [SP1] Modbus points can be orphaned in the data server. (38477)

93.  [SP1] Siemens MC75 EDGE Modem and MultiTech Modem are not supported. (39071, 39102, 39072, 39211)

94.  [SP1] Alarm Generator can't handle Constants after using M-Bus points. (39262)

95.  [SP1] Alarm Generator throws exception when switching instances and the tree wasn't built yet. (39263)

96.  [SP1] Alarm Notifier e-mail header has extra spaces which get rejected by virus scanner software. (38812)

97.  [SP1] Calendar date exception is not shown correctly. (38525)

98.  [SP1] Calendar exception creation can make the Web page hang. (38526)

99.  [SP1] Configuration Plug-In: Can't set the Type Translator Case Rule Multiplier value to 1, it gets reset to zero after Apply. (38631)

100.         [SP1] Data Point view page: Focus jumps if navigating with TAB key. (39122)

101.         [SP1] i.LON 100 Web configuration fails to view an event if the event time is after 17:00. (39172)

102.         [SP1] LonScanner appears to be disabled on the Security Web page, but it is enabled. (39203)

103.         [SP1] Can't add multiple M-Bus data points without clicking refresh. (38521)

104.         [SP1] Problem switching instances in service pages when navigating over standard menu. (39251)

105.         [SP1] Pulse Counter: Plug-In uses wrong length when changing the Output type, causing a LNS Turbo DS #200 error. (38559)

106.         [SP1] SMTP client generates wrong SMTP header. (38446)

107.         [SP1] The Web pages should allow self defined root domains like .myrootdomain. (38777)

108.         [SP1] Web Binder port change causes error on the iLON 100 Web page. (39129)

109.         [SP1] Web page ""instColl"" is undefined, causing a hang. (39249)

110.         [SP1] When deleting IP-852 service from the Web, the local port on the i.LON 100 server is reset to 1629. (38418)

111.         [SP1] When linking to a Service Page and clicking back immediately, the Standard page will not be loaded. (38622)

11  Known Problems and Workarounds

Following are known problems and workarounds for the i.LON e3 software.  Please report any additional problems to support@echelon.com.  Numbers in parentheses at the end of the descriptions are Echelon's internal problem tracking IDs.

1.     You may not be able to open the i.LON help files on a computer that is running Windows 7 or Windows Vista.  This is due to missing help file support in Windows 7 and Windows Vista.  Workaround: Open the  help file.  If you see a dialog that says “Why can’t I get Help from this program”, follow the instructions in the dialog to get WinHlp32.exe from Microsoft.

2.     If you attempt to repair an i.LON installation on a computer that is running Windows Vista that is a member of a domain, the repair will fail with the default Vista installation policy settings.  Workaround: To repair an i.LON SmartServer installation, the Windows AllowLockdownMedia policy must be set to 1.  To set this policy, following registry value should be added/set to the HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer system registry key: AllowLockdownMedia REG_DWORD 1.

12  Documentation Updates

Following are updates to the i.LON e3 documentation.

1.     Chapter 13 of the i.LON 100 e3 User’s Guide describes how to create e3 custom Web pages with the original i.LON Vision tool and Macromedia Contribute, which are both no longer supported. Workaround: See Chapter 12 of the i.LON SmartServer User’s Guide (078-0345-01D) for more information on creating custom e3 Web pages with i.LON Vision 1.0 and Adobe Contribute CS4, which are included in Release 3.04.  This manual is archived on the Echelon Web site at www.echelon.com/docs.  This manual was written prior to the release of Adobe Contribute CS4 and therefore refers to the CS3 release of Contribute throughout Chapter 12.

2.     Section 13.3.4 of the i.LON 100 e3 Programmer's Reference describes how to accept a Web connection from an i.LON 100 e3 Server.  In step 11 of this section, the example of the SOAP path in the SOAP Path box in the New Server Dialog does not include a leading ‘/’.   This results in the application returning an HTTP error 400.  Workaround: When adding a Web service to the i.LON 100 e3 Server, include a leading ‘/’ character in the SOAP path of the Web service in the SOAP Path box in the New Server Dialog.

3.     EMH EIZ-GDWL-739B M-Bus devices do not work with secondary addresses.  Workaround:  Use primary addressing for EMH EIZ-GDWL-739B M-Bus devices.

13  Software License Agreement

NOTICE

This is a legal agreement between you (“You” “Your”) and Echelon Corporation (“Echelon”). YOU MUST READ AND AGREE TO THE TERMS OF THIS SOFTWARE LICENSE AGREEMENT BEFORE ANY SOFTWARE CAN BE DOWNLOADED OR INSTALLED OR USED. BY CLICKING ON THE “ACCEPT” BUTTON OF THIS SOFTWARE LICENSE AGREEMENT, OR DOWNLOADING SOFTWARE, OR INSTALLING SOFTWARE, OR USING SOFTWARE, YOU ARE AGREEING TO BE BOUND BY THE TERMS AND CONDITIONS OF THIS SOFTWARE LICENSE AGREEMENT. IF YOU DO NOT AGREE WITH THE TERMS AND CONDITIONS OF THIS SOFTWARE LICENSE AGREEMENT, THEN YOU SHOULD EXIT THIS PAGE AND NOT DOWNLOAD OR INSTALL OR USE ANY SOFTWARE. BY DOING SO YOU FOREGO ANY IMPLIED OR STATED RIGHTS TO DOWNLOAD OR INSTALL OR USE SOFTWARE AND YOU MAY RETURN IT TO THE PLACE YOU OBTAINED IT FOR A FULL REFUND (IF APPLICABLE).

i.LON® 100 Software License Agreement

Echelon grants You a non-exclusive, non-transferable license to use the Licensed Software and accompanying documentation and any updates or upgrades thereto provided by Echelon according to the terms set forth below. As used herein:

If the Licensed Software is being provided to You as an update or upgrade to software which You have previously licensed, then You agree to destroy all copies of the prior release of this software within thirty (30) days after installing the Licensed Software; provided, however, that You may retain one (1) copy of the prior release for backup, archival and support purposes.

LICENSE

You may:

(a) use the i.LON Utilities internally to create IP-852 Channels, each with a minimum of one (1)  i.LON Server, and to Monitor, Control, and Configure i.LON Servers;

(b) copy the i.LON Utilities as reasonably necessary for such permitted internal use and for backup or archival purposes consistent with Your archive procedures, provided that You reproduce, unaltered, all proprietary notices on or in such copies;

(c) make one (1) copy of the i.LON System Image for the purpose of loading it into an i.LON Server in order to replace or update the i.LON System Image on the i.LON Server and one (1) copy for backup or archival purposes consistent with Your archive procedures, provided that You reproduce, unaltered, all proprietary notices on or in such copies; and

(d) transfer Your rights under this Agreement to an end user of the Licensed Software; provided that (i) You require the transferee to execute both copies of the Software License Transfer Agreement included with the Licensed Software, and (ii) You retain one (1) signed original thereof and furnish Echelon with a copy of same upon request. This right of transfer is exercisable on a one-time-only basis, and Your transferee shall have no right whatsoever to further transfer any rights to the Licensed Software.

You may not:

(a) use the Licensed Software for purposes other than the purposes set forth above;

(b) copy the Licensed Software, or any part thereof, except as expressly permitted above, or copy the accompanying documentation;

(c) modify, translate, reverse engineer, decompile, disassemble or otherwise attempt (i) to defeat, avoid, bypass, remove, deactivate, or otherwise circumvent any software protection mechanisms in the Licensed Software, including without limitation any such mechanism used to restrict or control the functionality of the Licensed Software, or (ii) to derive the source code or the underlying ideas, algorithms, structure or organization from the software from the Licensed Software (except to the extent that such activities may not be prohibited under applicable law), or

(d) distribute, rent, transfer or grant any rights in the Licensed Software or modifications thereof or accompanying documentation in any form to any person without the prior written consent of Echelon.

This license is not a sale. The Licensed Software may contain or be derived from materials provided to Echelon under license from a third party supplier. Title and copyrights to the Licensed Software, accompanying documentation and any copy made by You remain with Echelon or its suppliers. Unauthorized copying of the Licensed Software or the accompanying documentation, or failure to comply with the above restrictions, will result in automatic termination of this license and will make available to Echelon and its suppliers other legal remedies. You agree to indemnify, to the fullest extent permitted by law, Echelon and its suppliers (“Indemnitees”), for any third party infringement claims that may arise as a result of Your use of any Licensed Software in violation of the license granted in this provision.

You may make appropriate and truthful reference to Echelon and Echelon products and technology in Your company and product literature; provided that You properly attribute Echelon's trademarks. No license is granted, express or implied, under any Echelon trademarks, trade names or service marks.

TERMINATION

This license will continue until terminated. Unauthorized copying of the Licensed Software or failure to comply with the above restrictions will result in automatic termination of this Agreement and will make available to Echelon other legal remedies. This license will also automatically terminate if You go into liquidation, suffer or make any winding up petition, make an arrangement with Your creditors, or suffer or file any similar action in any jurisdiction in consequence of debt. Upon termination of this license for any reason You will destroy all copies of the Licensed Software. Any use of the Licensed Software after termination is unlawful.

TRADEMARKS

You may make appropriate and truthful reference to Echelon, Echelon products and technology in Your company and product literature; provided that You properly attribute Echelon’s trademarks and do not use the name of Echelon or any Echelon trademark in Your name or product name. No license is granted, express or implied, under any Echelon trademarks, trade names, trade dress or service marks.

LIMITED WARRANTY AND DISCLAIMER

Echelon warrants that, for a period of ninety (90) days from the date of delivery or transmission to You, the Licensed Software under normal use will perform substantially in accordance with the Licensed Software specifications contained in the documentation accompanying the Licensed Software. Echelon's entire liability and Your exclusive remedy under this warranty will be, at Echelon's option, to use reasonable commercial efforts to attempt to correct or work around errors, to replace the Licensed Software with functionally equivalent Licensed Software, or to terminate this Agreement. EXCEPT FOR THE ABOVE EXPRESS LIMITED WARRANTIES, ECHELON AND ITS SUPPLIERS MAKE AND YOU RECEIVE NO WARRANTIES OR CONDITIONS, EXPRESS, IMPLIED, STATUTORY OR IN ANY COMMUNICATION WITH YOU, AND ECHELON AND ITS SUPPLIERS SPECIFICALLY DISCLAIM ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT AND THEIR EQUIVALENTS. Echelon does not warrant that the operation of the Licensed Software will be uninterrupted or error free or that the Licensed Software will meet Your specific requirements.

SOME STATES OR OTHER JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSIONS MAY NOT APPLY TO YOU. YOU MAY ALSO HAVE OTHER RIGHTS THAT VARY FROM STATE TO STATE AND JURISDICTION TO JURISDICTION.

LIMITATION OF LIABILITY

IN NO EVENT WILL ECHELON OR ITS SUPPLIERS BE LIABLE FOR LOSS OF DATA, LOST PROFITS, COST OF PROCUREMENT OF SUBSTITUTE GOODS, TECHNOLOGY OR SERVICES OR OTHER SPECIAL, INCIDENTAL, PUNITIVE, CONSEQUENTIAL OR INDIRECT DAMAGES ARISING FROM THE USE OF THE LICENSED SOFTWARE OR ACCOMPANYING DOCUMENTATION, HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY (INCLUDING NEGLIGENCE). THIS LIMITATION WILL APPLY EVEN IF ECHELON OR AN AUTHORIZED DISTRIBUTOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES AND NOTWITHSTANDING THE FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY PROVIDED HEREIN. IN NO EVENT SHALL ECHELON'S OR ITS SUPPLIERS' LIABILITY EXCEED THE AMOUNTS PAID FOR THE LICENSED SOFTWARE. ALL LIABILITY UNDER THIS AGREEMENT IS CUMULATIVE AND NOT PER INCIDENT AND BENEFIT ECHELON’S THIRD PARTY SUPPLIERS. YOU ACKNOWLEDGE THAT THE AMOUNTS PAID BY YOU FOR THE LICENSED SOFTWARE REFLECT THIS REASONABLE ALLOCATION OF RISK.

SOME STATES OR OTHER JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATIONS AND EXCLUSIONS MAY NOT APPLY TO YOU.

SAFE OPERATION

YOU ASSUME RESPONSIBILITY FOR, AND HEREBY AGREE TO USE YOUR BEST EFFORTS IN, ROUTING, MONITORING, CONTROLLING LONWORKS DEVICES TO PROVIDE FOR SAFE OPERATION THEREOF, INCLUDING, BUT NOT LIMITED TO, COMPLIANCE OR QUALIFICATION WITH RESPECT TO ALL SAFETY LAWS, REGULATIONS AND AGENCY APPROVALS, AS APPLICABLE. THE NEURON CHIP, 709.1 PROTOCOL, NEURON CHIP FIRMWARE, i.LON SERVER, AND THE LICENSED SOFTWARE ARE NOT DESIGNED OR INTENDED FOR USE AS COMPONENTS IN EQUIPMENT INTENDED FOR SURGICAL IMPLANT INTO THE BODY, OR OTHER APPLICATIONS INTENDED TO SUPPORT OR SUSTAIN LIFE, FOR USE IN FLIGHT CONTROL OR ENGINE CONTROL EQUIPMENT WITHIN AN AIRCRAFT, OR FOR ANY OTHER APPLICATION IN WHICH THE FAILURE OF THE NEURON CHIP, LONTALK PROTOCOL, NEURON CHIP FIRMWARE, i.LON SERVER OR THE LICENSED SOFTWARE COULD CREATE A SITUATION IN WHICH PERSONAL INJURY OR DEATH MAY OCCUR, AND YOU SHALL HAVE NO RIGHTS HEREUNDER FOR ANY SUCH APPLICATIONS.

COMPLIANCE WITH EXPORT CONTROL LAWS

You agree to comply with all applicable export and re-export control laws and regulations, including the Export Administration Regulations ("EAR") maintained by the United States Department of Commerce. Specifically, You covenant that You shall not—directly or indirectly—sell, export, re-export, transfer, divert, or otherwise dispose of any software, source code, or technology (including products derived from or based on such technology) received from Echelon under this Agreement to any country (or national thereof) subject to antiterrorism controls or U.S. embargo, or to any other person, entity, or destination prohibited by the laws or regulations of the United States, without obtaining prior authorization from the competent government authorities as required by those laws and regulations. You agree to indemnify, to the fullest extent permitted by law, Echelon from and against any fines or penalties that may arise as a result of Your breach of this provision. This export control clause shall survive termination or cancellation of this Agreement.

LANGUAGE

The parties hereto confirm that it is their wish that this Agreement, as well as other documents relating hereto, have been and shall be written in the English language only.

Les parties aux présentes confirment leur volonté que cette convention de même que tous les documents y compris tout avis qui s'y rattache, soient rédigés en langue anglaise.

GENERAL

This Agreement shall not be governed by the 1980 U.N. Convention on Contracts for the International Sale of Goods; rather, this Agreement shall be governed by the laws of the State of California, including its Uniform Commercial Code, without reference to conflicts of laws principles. This Agreement is the entire agreement between us and supersedes any other communications or advertising with respect to the Licensed Software and accompanying documentation. If any provision of this Agreement is held invalid or unenforceable, such provision shall be revised to the extent necessary to cure the invalidity or unenforceability, and the remainder of the Agreement shall continue in full force and effect. If You are acquiring the Licensed Software on behalf of any part of the U.S. Government, the following provisions apply. The Licensed Software and accompanying documentation were developed at private expense and are deemed to be "commercial computer software" and "commercial computer software documentation", respectively, pursuant to DFAR Section 227.7202 and FAR 12.212(b), as applicable. Any use, modification, reproduction, release, performance, display or disclosure of the Licensed Software and/or the accompanying documentation by the U.S. Government or any of its agencies shall be governed solely by the terms of this Agreement and shall be prohibited except to the extent expressly permitted by the terms of this Agreement. Any technical data provided that is not covered by the above provisions is deemed to be "technical data/commercial items” pursuant to DFAR Section 227.7015(a). Any use, modification, reproduction, release, performance, display or disclosure of such technical data shall be governed by the terms of DFAR Section 227.7015(b). You agree not to export the Licensed Software in violation of the laws and regulations of the United States or any other nation. Echelon’s direct and indirect licensors of software incorporated into the Licensed Software are third party beneficiaries of this Agreement and this Agreement is made expressly for the benefit of, and is enforceable by, Echelon and such licensors.

Echelon, LON, LonTalk, LonWorks, i.LON, and Neuron are registered trademarks of Echelon Corporation in the U.S. and other countries. SmartShapes is a U.S. registered trademark of Microsoft Corporation.