i.LON® 100 e2 Internet Server ReadMe File
Release 1.11, March 2005

Copyright © 1998 – 2005 Echelon Corporation
All Rights Reserved

1         Introduction

This file describes i.LON 100 e2 Release 1.11, which is created by applying i.LON 100 e2 Service Pack 1 (“SP1”) to an i.LON 100 e2 installation, and is included on the i.LON 100 e2 Service Release 1 (“SR1”) CD.  Release 1.11 provides important updates to the i.LON 100 e2 firmware and Configuration Utility, and includes the fixes contained in i.LON 100 e2 Update 1.  The service pack is delivered as a self-extracting executable file of approximately 20 megabytes, whereas the service release is delivered on a CD.  The service release installation has no prerequisites, whereas the installation of the service pack requires a previous installation of i.LON 100 e2 to be present (with or without e2 Update 1 installed).  The installation of either the service release or service pack results in identical executable files and firmware being installed for use on the computer and i.LON 100 server.

Update and upgrade notifications will be sent to registered users, so be sure to register your software.

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 software must be used with the latest Microsoft Internet Explorer and Echelon LNS® and LonMaker® service packs.  At a minimum, you must install both LNS 3 Service Pack 8 Update 1 and LonMaker 3.1 Service Pack 3 Update 1, both of which are included on the i.LON 100 CD and installed automatically if needed.  LNS and LonMaker service packs are also available from Echelon’s Download Center at www.echelon.com/downloads.  Microsoft Internet Explorer 6 (IE6) is also included on the i.LON 100 CD-ROM.

Additional information and updates, including critical updates, may be available on the i.LON 100 Internet Server Web page at www.echelon.com/ilon.  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. 3

4      Identifying your i.LON 100 Release. 3

5      Installing i.LON 100 e2 Service Pack 1. 4

6      Installing i.LON 100 e2 Service Release 1. 6

7      Release 1.11 Changes. 7

7.1       Alarm Generator 7

7.2       Alarm Notifier 8

7.3       Analog Function Block. 8

7.4       Data Logger 8

7.5       Data Server 8

7.6       Event Scheduler 8

7.7       Pulse Counter 9

7.8       Type Translator Errors. 9

7.9       Backup and Upgrade Utility. 9

7.10     Configuration Plug-in. 9

7.11     Formats and Units. 10

7.12     Modem.. 10

7.13     TrendGraph Example. 10

7.14     Web Pages. 10

8      Known Problems and Workarounds. 11

8.1       i.LON 100 Configuration Plug-in & Utilities. 11

8.2       i.LON 100 Internet Server Firmware. 12

8.3       i.LON 100 Web Pages. 13

8.4       Upgrading from Prior Releases. 13

8.5       Examples. 14

9      Software License Agreement 14

 

3         i.LON 100 Release History

Release

Date

i.LON 100 Internet Server Release 1 (V1.00.52)

November 2002

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

April 2003

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

December 2003

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

January 2004

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

January 2005

 

 

i.LON 100 e2 Internet Server (V1.10.90)

September 2004

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

January 2005

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

March 2005

 

4         Identifying your i.LON 100 Release

You can determine whether or not you have the i.LON 100 e2 firmware installed on an i.LON 100 server, and you can determine whether or not you already have Service Pack 1 software installed on your i.LON 100 server.  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 the Installation instructions below for instructions on how to reboot an i.LON 100 server.
  2. If you have rebooted the i.LON 100 server, wait for the reboot to be completed.  You can tell when the i.LON 100 has completed initialization when the green Power/Wink LED on the i.LON 100 server stops blinking and stays on solidly.
  3. Enter your i.LON 100 e2 server’s address in Internet Explorer (6.0 or newer). 
  4. Click the Login button.
  5. Enter your user name and password when prompted.  By default this is ilon/ilon, but you may have changed that. 
  6. The version number displayed at the bottom of the first page should be 1.10.90 if you have an i.LON e2 without Update installed, or 1.10.94 if you have applied Update 1.  If the version is 1.00.52, you have a Release 1 i.LON 100 Internet Server that cannot be updated with Service Pack 1 (but can be updated with the i.LON 100 e2 SR1 CD).

Notes:

 

5         Installing i.LON 100 e2 Service Pack 1

You can install the i.LON 100 e2 Service Pack 1 over an existing i.LON 100 e2 installation.
To install i.LON 100 e2 Service Pack 1, follow these steps:

  1. You must install Service Pack 1 on a computer that already has Release 1 i.LON 100 e2 (V1.10) installed, with or without Update 1.   This service pack will not work with a Release 1 i.LON 100 (V1.00).
  2. 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.
  3. Download the iLON100e2_SP1.exe file from Echelon’s Web site to any directory on your computer.
  4. Click the Windows Start menu, click Run, and browse to the directory where you downloaded iLON100e2_ SP1.exe.
  5. Double-click iLON100e2_ SP1.exe.
  6. Insert the original i.LON 100 e2 (V1.10) CD-ROM in the CD-ROM drive of your PC when prompted. The service pack installation will not complete correctly if the original e2 installation media is inaccessible.
  7. Complete the installation on you computer.  In most cases, you can accept all defaults.  The i.LON 100 software on your computer will be updated to Release 1.11, and an additional V1.11 Images directory will be created.
  8. 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 device or functional block shape, click Configure on the shortcut menu, and then enter the IP address of your i.LON 100 server. 
  9. 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 an advantage for modem users.
  10. Instead of the previous two steps, you can use an FTP client such as Internet Explorer to copy the updated firmware files from your <LonWorks directory>\iLON100\Images\iLON100 1.11 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 e2 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.
  11. If you previously updated the /root/Webparams.dat file. merge your changes into the new Release 1.11 Webparams.dat file.  The Release 1.11 Webparams.dat file now has the following contents before your customization:


iLonSecurity 1.3 100

GlobalMemoryBytes:16384

RequestMemoryBytes:16384

TaskStackBytes:204800

NumTasks:5

TaskPriority:240

MaxSymbols:100

MaxUrlSize:1024

(Users)

all:i.LON:i.LON

(Locations)

everywhere:*.*.*.*

(Realms)

/user/Echelon/*:all:everywhere

/forms/Echelon/*:all:everywhere

(Aliases)

  1. 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.
  2. Reboot your i.LON 100 server from the Setup>Reboot Web page.  To access the Web page, enter your i.LON 100 e2 server’s address in Internet Explorer (6.0 or newer).  Click the Login button and enter the user name and password when prompted.  By default this is ilon/ilon, but you may have changed that. 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 simply cycle the power to your i.LON 100 server.

 

6         Installing i.LON 100 e2 Service Release 1

You can install Release 1.11 from an i.LON 100 e2 Service Release 1 CD.
To install an i.LON 100 e2 Service Release 1 CD, follow these steps:

  1. If you are upgrading an existing i.LON 100 e2 server, use an FTP client such as Internet Explorer to backup a copy of all files on your i.LON 100 server to another computer, or use the Backup option in the i.LON 100 Configuration Plug-in.
  2. Insert the i.LON 100 e2 SR1 CD and the installation program should start automatically (sometimes there is a pause after initial startup to install the Microsoft SOAP toolkit). If the installation program does not start automatically when the CD is inserted, run the setup.exe at the root of the CD.  In most cases, you can accept all defaults.
  3. 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 an advantage for modem users.
  4. Instead of the previous two steps, you can use an FTP client such as Internet Explorer to copy the updated firmware files from the <LonWorks directory>\iLON100\Images\iLON100 1.11 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 e2 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.
  5. If you previously updated the /root/Webparams.dat file. merge your changes into the new Release 1.11 Webparams.dat file.  The Release 1.11 Webparams.dat file now has the following contents before your customization:

iLonSecurity 1.3 100

GlobalMemoryBytes:16384

RequestMemoryBytes:16384

TaskStackBytes:204800

NumTasks:5

TaskPriority:240

MaxSymbols:100

MaxUrlSize:1024

(Users)

all:ilon:ilon

(Locations)

everywhere:*.*.*.*

(Realms)

/user/Echelon/*:all:everywhere

/forms/Echelon/*:all:everywhere

(Aliases)

  1. 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.
  2. Reboot your i.LON 100 server from the Setup>Reboot Web page. To access this Web page, enter your i.LON 100 e2 server’s address in Internet Explorer (6.0 or newer).  Click the Login button and enter the user name and password when prompted.  By default this is ilon/ilon, but you may have changed that. 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 simply cycle the power to your i.LON 100 server.

To remove Release 1.11, follow these steps:

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

 

7         Release 1.11 Changes

This section describes the problems fixed and other changes in Release 1.11 that were not include in the original i.LON 100 e2 release (Release 1.1).  Numbers in parentheses at the end of the change descriptions are Echelon's internal problem tracking IDs.  IDs followed by “U1” indicate fixes or changes that were also in i.LON 100 e2 Update 1.

7.1        Alarm Generator

The Alarm Set Delay property of the Alarm Generator specifies the amount of time that an alarm condition must be satisfied before an alarm will be raised.  The i.LON 100 e2 firmware did not restart this timer if the value of the Input point drops out of an alarm condition and then enters the alarm condition again.  The result was that some alarms were raised even though the Alarm Set Delay had not been properly satisfied.  (34764: U1)

The alarm set time was not retriggered when the alarm condition became false.  (34764)

The high limit, low limit, and deadband values were sometimes all set to zero in the plug-in when operating in the US English locale.  (35275)

7.2        Alarm Notifier

The i.LON 100 sometimes failed when sending an email message.  (35437)

The alarm notifier sent email messages with the wrong version number:  (35508)

The Send Email When Alarm Condition Clears setting did not work if the alarm enable cleared while an alarm was active. (34779)

7.3        Analog Function Block

The analog function block generated incorrect values on start-up.  (35385)

7.4        Data Logger

CSV data log files contained blank lines between data lines after clearing a log that was less than 100% full.  (34850)

7.5        Data Server

When the user tried to set a data point's format description to a fully qualified name (i.e. #progid[mode].type), but forgot to include the required "." separating the mode value and the type name, the Data Server crashed.  (35804)

The data server did not return values correctly for data points whose priority was set below 255 and lifetime was set greater than 0.  (35360)

SNVT_tod_event definitions were missing. (35025)

A SOAP data point read request would fail when reading a field of a structure if the field was also a structure.  (35455)

7.6        Event Scheduler

The event scheduler did not update an output if its new value was equal to its current value.  (34878: U1)

If two consecutive events with the same value were defined in an Event Scheduler, the i.LON 100 e2 firmware only executed the first of these events.  This could cause a problem if one of the scheduled data points had been set to another value after the first event, and the Event Scheduler was expected to override this data point and set it back to the scheduled value.  (35032: U1)

When an operator placed a scheduled data point in an override state such that its priority was higher than that of the schedule, the i.LON 100 e2 Event Scheduler still reset the priority of the data point at midnight (12:00AM or 00:00).  The result was that the Event Scheduler could write a new value to this data point even though the operator intended to keep this point in an override state and block the output of the schedule.  (35044: U1)

7.7        Pulse Counter

Binding between a pulse counter and an external network variable did not work.  For example, if the user attempted to bind a 4-byte SNVT_elec_kwh_l NV on an external device to an i.LON SNVT_elec_kwh_l pulse counter output, when the pulse counter updated the NV, the bound NV on the external device was unchanged.  (35751)

Incorrect pulse counter values were logged when the log delta time was set to a longer time interval than the polling time.  (35225)

The default output type for the pulse counter has been changed to a double-float type.  (35661)

7.8        Type Translator Errors

The i.LON 100 Configuration Plug-In sometimes did not show the correct data types for a type translator.  (35006)

 

A value of .001 could not be used as multiplier or constant in a type translator rule.  (35234)

7.9        Backup and Upgrade Utility

Pulse Counter metering values were not restored after an upgrade from Release 1 to e2.  (35811)

Default values were incorrectly changed by an upgrade. (35224)

Active FTP has been added as the default option for the plug-in backup and upgrade functions since the previous passive FTP sometimes caused problems with firewalls.  The user can now select either type of FTP.  (35717)

Under conditions where over 500 files were being backed up, the i.LON 100 could exhaust its network buffers and signal an error to the plug-in backup utility.  The backup utility would indicate to the user that a single file did not get backed up, where in reality all of the remaining files were not backed up.  The i.LON 100 server now correctly indicates the nature of any errors to the user and has twice as many buffers in the operating system. (35687 and 35715)

The upgrade utility now requires less free memory on the i.LON 100 server.  (35900)

After an i.LON 100 upgrade via the plug-in, Web pages were accessible without a password.  The Release 1.11 includes a new /root/Webparams.dat file.  See the installation instructions for information of merging your changes with the new file. (34901)

After an i.LON 100 upgrade via the plug-in, the old preset names were deleted and replaced by new, incorrect preset names.  (34905)

7.10    Configuration Plug-in

The plug-in could not be used to create NVEs based on UNVTs not defined in the i.LON 100 resource file.

The plug-in could not be used to add an NVE point that used SNVT_press_p in with a US format.  (34784)

The user could not create dynamic network variables that were created using a configuration network variable as the template.  (35256)

7.11    Formats and Units

When changing output data type of a pulse counter to US units, the plug-in left the format of the input in SI units.  For example, if the output data type of a pulse counter was set to cubic feet (SNVT_vol) with US units, the input data point format was set to SI instead of US.  The result was that if the user set a new start amount the calculation of the output value was wrong.  (35845)

The SNVT_power_f#US format was not defined correctly—BTU was used instead of kW.  (35802)

The i.LON Configuration Plug-in sometimes displayed the wrong units for US formats when configuring a pulse counter.  (35799)

The plug-in did not show data point presets for some types. (35616 and 35271)

The plug-in sometimes incorrectly displayed invalid values for SNVT_temp_f data points.  (35439)

The wrong units were used for SNVT_elec_kwh_l differential values.  (35226)

7.12    Modem

After changing the username and password for dial-in access in the Setup>Modem Web page, dialing in with the new username and password, and then rebooting the i.LON 100 server, the password was incorrectly set equal to the new username.  (35205: U1)

7.13    TrendGraph Example

The TrendGraph example did not work.  (35370)

7.14    Web Pages

The Web binder validation page reported a firmware version mismatch due to Internet Explorer security settings.  This problem was caused by an error in the script which discovers the SOAP version of the i.LON 100s involved in a Web connection.  These issues have been fixed in Release 1.11, and the help page for the Web binder has been updated to describe in more detail how to modify the browser security preferences.  (34852)

The Rebuild Test button on the Verify Web page did not work.  (34747)

 

8         Known Problems and Workarounds

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

8.1      i.LON 100 Configuration Plug-in & Utilities

When installing the i.LON 100 software, the installation program may pause for 2–5 minutes while a large amount of hard disk activity is observed.  This can especially occur if you are running an antivirus service or have a very large Windows registry.  It is caused by an issue with the installation of the Microsoft SOAP toolkit.  Workaround: Turn off any antivirus services while installing the i.LON 100 software.  (26393)

LNS Application developers writing applications to handle RNI uplink connections from the i.LON100 should program their LNS application to process uplink request messages, and provide suitable responses to the LonWorks network, in a timely fashion (e.g. less than 30 seconds).  This becomes particularly critical when using an i.LON 100 Internet Server and the uplink is delivered over PPP, and the PPP profile (connection) is exclusively set up for your i.LON 100 Internet Server.  Other i.LON 100 applications will not be able to use the PPP link until the LNS application terminates the xDriver.  During this time, i.LON 100 Web bindings and alarm notifications which are configured to use a different PPP profile (connection) will fail.  Workaround: Follow the guidelines above or use a single ppp profile (i.e. an Internet service provider).  (33198 and 32153)

 

The i.LON 100 e2 i.LON Web Server Security and Parameters utility is not compatible with Release 1 i.LON 100 servers. Workaround: Use the i.LON Web Server Security and Parameters utility included with the Release i.LON 100 server to create or modify a WebParams.dat file for a Release 1 i.LON 100 server. (34697)

 

If you change the LonTalk® channel priority of the i.LON 100, the i.LON 100 will be unable to communicate over the LonTalk channel for approximately 5 minutes.  The priority does get set correctly, but there is a long delay after the change.  Workaround: Wait for the i.LON 100 to respond or reboot the i.LON 100 after changing its LonTalk channel priority value. (34663)

 

In rare cases, it is possible for the NVL_nviDateEvent data point to be assigned an incorrect format.  The symptom of this error is that the plug-in will report an error stating that the i.LON 100 Configuration Software was unable to update the type of the NVL_nviDateEvent data point when you attempt to resynchronize using the plug-in.  Workaround: If you see this error, cancel the update to the i.LON 100 device, go to the Data Server\Data Point Presets page and change the format to UNVT_dateEvent, and then click Apply. (34567)

 

The backup utility automatically backs up subdirectories of selected top-level directories.  If the user selects both a top-level directory and its subdirectories, the subdirectories are backed up twice.  Workaround: Do not select subdirectories of selected directories when selecting directories to be backed up.  You can further reduce the size of the backup file by not selecting the Modules directory, since the Modules directory is already backed up in the Images directory installed by the i.LON 100 software, and is also on the i.LON 100 CD.  (35542)

 

The backup utility does NOT backup the files in the root directory of the i.LON 100, such as the Webparams.dat file. Workaround: Manually back up any modified root-level files such as the Webparams.dat file.

 

The default behavior of the plug-in has been changed to not delete the applications added via the Web user interface instead of the plug-in.  This change only applies to new installations and existing installations that have not yet been synchronized.  Workaround: Change the option for existing applications.

 

If you are modifying the i.LON 100 XML configuration files on a computer (not recommended) and transferring them to the i.LON 100 via FTP, and you use the plug-in, the XML file cache may become stale and not contain your updated files.  Workaround: Set the option in the plug-in to disable local caching of the XML configuration files on the computer. The cache is dependent upon the LastUpdateTime value in the XML file to know whether it needs to update its cache. If you defeat this by using FTP, then there is no way for the plug-in to keep the cache current.  (35046)

8.2      i.LON 100 Internet Server Firmware

When upgrading an i.LON 100 from Release 1 to the e2 release (Release 1.1), all data logs and alarm logs are deleted the first time the i.LON 100 reboots. Workaround: Backup all data logs and alarm logs using FTP before starting the upgrade process. (34537)

The Alarm Generator does not convert offset values correctly when upgrading from V1.00 to V1.10.  Workaround: Reset the offsets manually after the upgrade.  (34166)

The Alarm Notifier consumes all i.LON 100 system RAM memory if all 40 function blocks are defined, each with 50K summary logs.  Workaround: Use fewer alarm generators and smaller summary logs.  (27760)

The Data Logger cannot log reserved characters such as 0x0D (CR) and 0x0A (LF) to a data log in CSV format.  These characters may appear in SNVT_str_asc network variables.  Workaround: Do not log reserved characters.  (35148)

The Event Scheduler recalculates and writes out current values for each of its data points when it is reconfigured, the i.LON 100 server is rebooted, or the system time is changed.  Workaround: To force a value for an Event Scheduler output, set a high priority for the desired value.

Changing the start amount of a Pulse Counter will overwrite the reported metering value.  Workaround: Backup the metering value before changing or upgrading the Pulse Counter configuration.  (35891)

Upgrading a Pulse Counter will fail if the Pulse Counter output is bound.  This is because the default type of the output changed.  Workaround: Delete any connections to the Pulse Counter output prior to upgrading the functional block.  Restore the type of the output network variable after an upgrade and recreate any connections. (35661)

The Type Translator does not correctly process rules containing hex values.  Workaround: If a data point or data point field to be used with a Type Translator uses hex formatting, change the format to use decimal formatting, and then specify all values as decimal.  For example, a SNVT_alarm data point will have the following format by default: text("%x %x %x %x %x %x %d %m %m %d <%x %x %x %x>  %d/%d/%d/%d:%d:%d:%d <%x %x %x %x>",location[0], location[1], location[2], location[3],location[4], location[5], object_id, alarm_type,priority_level, index_to_SNVT, value[0], value[1],value[2], value[3], year, month, day, hour, minute,second, millisecond, alarm_limit[0], alarm_limit[1],alarm_limit[2], alarm_limit[3]);.  To use one of the value[] or alarm_limit[] fields in a Type Translator rule, create and apply a new format that specifies decimal formatting for the value[] and alarm_limit[] fields as follows: text("%x %x %x %x %x %x %d %m %m %d <%d %d %d %d>  %d/%d/%d/%d:%d:%d:%d <%d %d %d %d>",location[0], location[1], location[2], location[3],location[4], location[5], object_id, alarm_type,priority_level, index_to_SNVT, value[0], value[1],value[2], value[3], year, month, day, hour, minute,second, millisecond, alarm_limit[0], alarm_limit[1],alarm_limit[2], alarm_limit[3]);. (34688)

If RNI session establishment fails while using LNS 3.08 Update 1 or earlier, a misleading success message can appear on the i.LON 100 console.  Typically such a session establishment fails when authentication keys are mismatched between your computer and the i.LON 100 server.  Workaround: Upgrade to LNS 3.2.  (32407)

The i.LON 100 server now uses the standard comma (“,”) to separate data fields instead of a semicolon (“;”) in CSV (text format) alarm logs and data logs.  Third-party programs that expect the Release 1 semicolon will not function correctly. Workaround: Modify the program to look for commas instead of semicolons. (34537)

The %va data point value in an email is always in SI units if the type of the input point is SNVT_alarm, even if US units are specified. (35268)

8.3      i.LON 100 Web Pages

Pop-up advertisement blocker programs can prevent proper operation of the i.LON 100 Web pages.  Workaround: Turn off pop-up blocking for your i.LON 100’s IP address.  It is also a good idea to make each i.LON 100’s IP address a “Trusted Site” in IE6 to prevent problems with downloading and running the i.LON 100 ActiveX controls.  (30326)

8.4      Upgrading from Prior Releases

Custom type translator files that worked for the Release 1 i.LON 100 server won't necessarily work with an i.LON 100 e2 server due to the new enforcement of fully qualified format names for UCPTFormatDescription references to UNVT type files. Although the Release 1 programmer's guide also discussed fully qualified format names for UNVT types, the firmware did not enforce them.  For example, with a Release 1  i.LON 100 server, you could simply list the format file name for a type and nothing else was required.  For example, the following format worked in Release 1:.<UCPTformatDescription>UNVT_ac_data</UCPTformatDescription>.  However, this format will cause an error to be written to the event log with an i.LON 100 e2 server.  Workaround: When using an i.LON 100 e2 server, fully qualify the type by including a prefix that references the program ID and scope of the type file.  For example, the previous example should be written as follows: <UCPTformatDescription>#80004a0000000000[3].UNVT_ac_data</UCPTformatDescription>.  (35007)

8.5      Examples

Microsoft Office 2003 is not supported for the TrendGraph example.  Workaround: Use Office 2000 or do not use the TrendGraph example.  (35370)

 

9         Software License Agreement

NOTICE

This is a legal agreement between you 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 1000 Internet Server, i.LON 600 LonWorks/IP Server, i.LON 100 Internet Server  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 LonWorks/IP Channels and to Configure i.LON Internet Servers to serve web pages;

(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 the i.LON System Image for the purpose of loading it into an i.LON Internet Server in order to replace or update the i.LON System Image on the i.LON Internet 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.

You may not:

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

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

(c) modify, translate, reverse engineer, de-compile, 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 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.

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 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, LonTalk PROTOCOL, Neuron CHIP FIRMWARE, i.LON INTERNET 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 INTERNET 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.

CISCO SYSTEMS SUPPORT

The Cisco Systems, Inc. ("Cisco Systems") software contained in the i.LON 1000 Internet Server has been integrated or pre-installed as part of the Licensed Software. The functionality of the Cisco Systems software as integrated in the Licensed Software may differ from a non-Cisco Systems product and any issues concerning the functionality or performance of the Echelon i.LON 1000 Internet Server and the integrated Cisco Systems software should be directed to Echelon Corporation and not to Cisco Systems.

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. Cisco NetWorks is a registered trademark of Cisco Systems.