i.LON® 100 Internet Server ReadMe File
Release 1.0, Service Pack 2, December 2003
Copyright © 1998-2003 Echelon
Corporation
All Rights Reserved
This file contains important information not included in the i.LON 100 Internet Server User's Guide or the i.LON 100 Internet Server help file concerning Release 1.0, Service Pack 2 (SP2). Additional information and updates, including critical updates, may be available from the i.LON 100 Internet Server Web page at www.echelon.com/products/internet/ilon100.htm.
Update and upgrade notifications will be sent to registered users, so be sure to register your software.
i.LON 100 V1.0 Service Pack 1 was an interim service pack that was never officially released. It is not necessary to install Service Pack 1 before installing Service Pack 2.
It is strongly recommended that the i.LON 100 Internet Server configuration software be used with the latest LNS and LonMaker service packs. LNS and LonMaker service packs are available from Echelon’s Download Center at www.echelon.com/downloads. At a minimum, you must install LNS 3 Service Pack 8, Update 1 and LonMaker 3.1 Service Pack 3, Update1.
4 Problems Fixed In Service Pack 2
4.3 Novell ARP broadcast packets may disrupt the Ethernet connection.
4.4 SOAP-based data log upload speed increased for large CSV Text logs.
4.5 Loss of default gateway interrupts i.LON 100 Internet Server communication.
4.6 Denial-Of-Service (DOS) attack susceptibility improved.
4.7 New Telnet functionality added for remote console access.
4.8 i.LON 100 Internet Server failed to connect using some older modem models (NO CARRIER).
4.9 Daylight Savings Time (DST) was enabled in all time zones.
4.11 The default value of UCPTlifeTime for all data points was previously set to 1.
4.14 Constant (NVC) data points could not be displayed in a Web page.
5 Documentation Errata for Release 1.0 i.LON 100 Internet Server User’s Guide
5.1 Address Table and Network Variable Limits
5.2 Output Network Variables Must Have Defaults for Heartbeats to Function
5.3 Telnet support is included in Release 1.0 Service Pack 2.
6 Known Problems and Workarounds
6.1.2 Type mismatch error while adding dynamic NV
6.1.3 Cannot communicate with device NS#26
6.1.4 Cannot test the i.LON 100 device
6.1.5 Error while replacing a device
6.1.7 The LonMaker tool places i.LON 100 device in the hard-offline state
6.2 i.LON 100 Configuration Plug-in & Utilities.
6.2.1 Configuration plug-in cannot apply changes
6.2.2 Plug-in does not show all functional blocks or subsystems
6.2.3 Cannot enter tenths of seconds for maxSendTime, minSendTime, maxRcvTime
6.2.4 LNS Error #40 reported when applying changes
6.2.5 Error entering long location strings
6.2.6 Error updating alarm generator
6.2.7 Multiple scheduler events for the same time do not trigger
6.2.8 WebParams utility allows out of range values
6.3 i.LON 100 Internet Server Firmware
6.3.1 RNI connection can fail if not using LNS 3 Service Pack 8, Update 1
6.3.2 Cannot restore factory defaults
6.3.3 MinSendTime never expires
6.3.4 Must reboot to get new NV default to take effect
6.3.5 i.LON 100 out-of-memory condition
6.3.6 User names are limited to 18 characters
6.3.7 Cannot change LonTalk® address
6.3.8 Alarm limits are not properly reported in emails
6.3.9 Data point format displays as RAW HEX
6.3.10 Cannot create more than 255 calendar exceptions
6.3.11 Cannot share NVE output data point
6.4.1 JavaScript error while trying to abort data log load
6.4.2 MD5 “Text secret phrase” does not adhere after submit is pressed
6.4.3 Security web page displays non-zero value for MD5 key
6.4.4 Dreamweaver FTP transfer fails
7 i.LON 100 Internet Server Software License Agreement
You can only install i.LON 100 Internet Server V1.0 Service Pack 2 on a computer that already has i.LON 100 Internet Server V1.0 or V1.0 plus Service Pack 1 installed.
To install Service Pack 2, follow these steps:
When removing i.LON 100 Internet Server V1.0 SP2, the installer will remove the i.LON 100 SP2 images but it will not roll back the version of Configuration Software to the previous version. To remove Service Pack 2 and restore V1.0, follow these steps:
To continue to use i.LON 100 Internet Server V1.0 Software without Service Pack 2, remove the Echelon i.LON 100 Software and reinstall the Echelon i.LON 100 V1.0 software from your i.LON 100 Internet Server V1.0 Software CD-ROM (December 2002).
This behavior has been changed. The Connection Manager now makes three attempts and then waits 5 minutes before attempting to send email again thus allowing incoming connections.
Problem #1: A bug in the i.LON 100 Internet Server plug-in that prevented the creation of more than 100 NVE points has been repaired.
Problem #2: An independent bug in the i.LON 100 Internet Server firmware limiting the number of NVEs has been repaired.
Novell Netware broadcast ARP requests were improperly interpreted by the i.LON 100 Internet Server’s TCP/IP stack, causing a deadlock which prevented the i.LON 100 Internet Server’s Ethernet connection from functioning. No communication (HTTP, ICMP, FTP, etc.) was possible when the deadlock occurred. SP2 resolves this problem in the TCP/IP stack.
Data log upload speeds using SOAP are now up to 10 times faster for large CSV Text logs. This increase was achieved by caching a list of log entries so that they can be accessed rapidly.
An unsuccessful incoming telephone connection could cause the i.LON 100 Internet Server to lose its default gateway. This prevented communication to any device beyond the local subnet. This bug has been repaired in SP2.
Under specific conditions on a high speed link it was possible to cause an Ethernet transmit buffer overflow condition by flooding the i.LON 100 Internet Server with malformed IP packets. This overflow condition is fixed in SP2.
SP2 adds the ability to use Telnet to remotely access the i.LON 100 Internet Server’s console application. Telnet is disabled by default on the security setup web page because it could potentially create a security vulnerability. It is recommended that Telnet be disabled unless specifically required. The username and password for Telnet access is the same as the username and password used for FTP.
This problem was fixed by adding delays between the modem AT commands.
The problem was fixed by only allowing the enabling of DST in the specific time zones where it is used.
The display problem has been fixed in SP2 by revising the MSSOAP.CAB file that resides on the i.LON 100 Internet Server’s flash disk.
The default in the DataServer is now set to 0 for all data point types when a new list of data points is created. Setting UCPTlifeTime to a value other than 0 causes NVE points to be actively polled for each SOAP / WEB request or any request from one of the i.LON 100 Internet Server’s built-in applications. If UCPTlifeTime is set to 0, the i.LON 100 Internet Server will not poll NVEs on each SOAP request. Instead, NVEs will be polled as defined in each NVE’s poll interval; SOAP requests will be served immediately using the cached value of the NVE as of its most recent poll.
The SMTP HELO command now includes the sender’s domain name. This modification was made in the i.LON 100 Internet Server’s config.sys file by adding <SMTPLogin>domain_name</SMTPLogin>.
Only the needed NVE’s are updated in SP2.
NVC’s may now be displayed in a web page using the <ilonweb> HTML tag.
The i.LON 100 Internet Server has the following limits on its address table entries and network variables:
· Maximum number of address table entries: 4096
· Maximum number of aliases: 1024
· Maximum number of data points: 800
If an output network variable on an i.LON 100 Internet Server functional block does not have a default value, it will not send a heartbeat until it a value is set. See Creating Data Point Presets in Chapter 4 of the i.LON 100 internet Server User’s Guide for more information on setting default values.
Version 1.0 SP2 of the i.LON 100 firmware supports Telnet access to the Console Application (see Appendix A of the i.LON 100 Internet Server User’s Guide). By default, Telnet access is disabled. You can enable Telnet access in one of the following ways:
· Perform a security access reset and open the i.LON 100 Security Web Page (see Chapter 3 of the i.LON 100 Internet Server User’s Guide for more information), and then set the Enable Telnet option on this page and click Submit.
· Access the console application through the serial port and enter the following command at the console prompt: enable telnet
Once Telnet is enabled, you will be able to access the i.LON 100 using any Telnet client (such as the command line Telnet client program present on a computer running Microsoftâ Windows). To begin a Telnet session, type: telnet <IP address or host name>
You will be prompted for a username and password. Use the FTP Username and FTP Password set on the Security Web Page.
If you right-click an i.LON 100 Web Server functional block and then click Configure on the shortcut menu, the LonMaker Browser starts instead of the i.LON 100 Configuration Plug-in.
Workaround: To configure data points on an i.LON 100 Web Server functional block, right-click the i.LON 100 device shape and then click Configure on the shortcut menu instead of right-clicking a Web Server functional block shape.
If you add a network variable (NV) shape to an i.LON 100 functional block, and then delete it and add an NV shape with the same name to the same functional block with a different type the i.LON 100 server will not properly assign the NV type.
Workaround: Start the i.LON 100 Configuration Plug-in. Wait for the i.LON 100 configuration data to load, and then click Resync.
You may receive a "Cannot communicate with device (NS, #26)" error message from LonMaker tool after reopening an existing network and re-commissioning the i.LON 100 device.
Workaround for PCLTA Network Interface: Use a Fast Network Interface on the host PC. Select this using the PCLTA control panel applet (Start>Settings>Control Panel>LonWorks Plug and Play). Change NI Application from NSIPCLTA to PCL10VNI and then click Apply.
Workaround for xDriver/RNI Network Interface: Reduce browsing and polling. Retry the connection.
The LonMaker tool may lose communication with the i.LON 100 server while executing the Test device management command while also browsing hundreds of data points per second in the LonMaker Browser.
Workaround: Close the LonMaker Browser or reduce the number of network variables being monitored.
When replacing an i.LON 100 device, the LonMaker tool may report a communication failure when reading or writing to network variables on the device.
Workaround: After copying the XML files in the /root/config/Software/ directory from the old i.LON 100 server to the new one, commission the new device using the LonMaker tool before trying to read or write to network variables.
You may not be able to start the i.LON 100 Configuration Plug-in when you are monitoring many network variables in the LonMaker Browser.
Workaround: Close the LonMaker Browser or reduce the number of network variables being monitored.
Under rare circumstances it is possible to inadvertently place the i.LON 100 device in the hard-offline state while making changes with the LonMaker tool. This could affect operations such as commissioning, adding functional blocks, or creating dynamic network variables. This has only been seen to occur under heavy monitoring conditions.
Workaround: Turn off all monitoring in the LonMaker tool and in any other LNS applications such as the LonMaker Browser, wait at least one minute, and then try the operation again or re-commission the i.LON 100 device. Waiting a minute should allow LNS to free up any buffers that may have been allocated to monitoring, but it could be necessary to wait even longer.
If you change the type of an NVL data point
and apply the changes, the i.LON
100 configuration plug-in may state that the change cannot be applied because
the data point is currently bound. This error may be reported if the data
point is bound, is being monitored by the LonMaker tool, or is defined as a
point in an LNS monitor set.
Workaround: Remove the point from any connections and monitor sets, and
quit monitoring the point in the LonMaker drawing or the LonMaker Browser.
After adding or removing subsystems or functional blocks using the LonMaker tool, the Functional Blocks list on the Data Point\External Points page of the i.LON 100 plug-in may not reflect the changes.
Workaround: Exit and re-start the i.LON 100 Configuration Plug-in.
The fields for the maxSendTime, minSendTime, and maxRcvTime in the Data Points properties page of the i.LON 100 plug-in accept values in one tenth of second granularity; however, the i.LON 100 firmware ignores any fractional portion of these values.
Workaround: Enter only the number of whole seconds desired for these values.
If you enter an out-of-range value for the Start Amount on one of the i.LON 100 Pulse Counter functional blocks, the error is not reported until you apply the change. When changes are applied the plug-in will report "Invalid format (Subsystem: LNS, #40)." The error text will also indicate the Pulse Counter functional block in which the problem was detected.
Workaround: Select Abort when the error is reported, then return to the configuration page for the Pulse Counter functional block, and adjust the specified Start Amount (or Output Data Type Value). The limits for the Start Amount are the same as what is displayed in the selected Output Data Type Value.
If you enter a data point Location value greater than 127 characters long in the i.LON 100 Configuration Plug-in, the plug-in may report that the value is too long and require that a shorter value be entered. If you then enter a valid location value, the new value is not stored, and the location string is reset to its original value.
Workaround: After the error is reported, press the ESC key to cancel the changes to the Location field, and then double-click the field again and enter the correct value.
The i.LON 100 Configuration Plug-in allows the entry of a location string with 22 characters; however, when you save the change, the following error may be reported: "An error occurred while updating 'Alarm Generator'. error format UCPTalarm2Description." The name of the Alarm Generator functional block that caused the error will also be reported.
Workaround: Select Abort or Ignore from the error dialog, edit the Alarm Generator location string to have 21 or fewer characters, and then re-apply the changes.
In some cases, it is possible to enter multiple scheduler events (on the i.LON 100 plug-in Schedule Details page) with the same start time. The i.LON 100 Configuration Plug-in will report the problem, but will not require that it be corrected. In this case, the i.LON 100 firmware will only execute the last event entry for a given time.
Workaround: Assign unique times to all Scheduler events.
The i.LON 100 Web Server Parameters utility, used to create a webparams.dat file, allows more than 5 web tasks to be specified, which could cause all available memory on the i.LON 100 to be used by web tasks. It also allows web task stack sizes smaller than 200KB, which could cause HTTP requests to fail.
Recommendation: Allow no more than 5 web tasks in the webparams.dat file. Specify no less than 200KB stack size for each task.
Please note: this problem is fixed when you use LNS 3 Service Pack 8, Update 1
If you temporarily lose TCP connectivity to the i.LON 100 server from the LonMaker tool or any other LNS application, the RNI connection may fail and the LonMaker tool or LNS application may become non-responsive. You can lose TCP connectivity due to problems within the IP network, a power cycle of the i.LON 100 server, or other reasons.
Workaround: Allow the i.LON 100 server to complete its boot sequence, close the LonMaker drawing, and then re-open the drawing selecting the i.LON 100 RNI as the network interface. Depending on the computer, operating system, and circumstance of the failure, you may have to manually kill all LNS processes in the Windows Task Manager or possibly even reboot the computer.
If the i.LON 100 flash disk is very close to being full and you try to restore factory defaults, the operation may fail and leave the system in an inconsistent state. Disk errors may be reported in the event log when the i.LON 100 server is rebooted.
Workaround: Delete some files to free up several MB of disk space and try restoring factory defaults again. If this does not succeed, you may need to format the disk using the format console command, and then reload all the i.LON 100 files using FTP.
If the minSendTime of an NVE is greater than the poll rate, the minSendTime will never expire.
Workaround: Set the minSendTime to a value less than the poll rate, set the poll rate to 0 when using the minSendTime, or do not use minSendTime at all.
If you set or change the default value of a new NV, the current value of the data point may not be updated until you reboot the i.LON 100 server. For example, if you add a new dynamic NV, start the i.LON 100 configuration plug-in, and set the default value of the new NV, the UCPTdefOutput property of the NVL is set correctly but the UCPTvalue property is not updated.
Workaround: Reboot the i.LON 100 server.
The i.LON 100 server can become non-responsive or crash due to an out-of-memory condition. Out-of-memory conditions can happen due to a variety of circumstances but generally relate to having too many tasks running simultaneously. For example, this may be caused by too many large SOAP requests or too many threads allocated to the Web server process. This is similar to the out-of-memory condition on a computer when more applications are started than the operating system can handle. Although the i.LON 100 server attempts to provide feedback whenever possible, an out-of-memory message is not always displayed in the Web page, event log, or console. It is impossible for the i.LON 100 software to always predict an out-of-memory condition without placing undue restrictions on the user.
Workaround: Follow the recommendations in the i.LON 100 User's Guide and Programmer's Reference to maximize free memory. This involves limiting the number of data points in the network and (for SOAP programmers) limiting the size of SOAP requests and responses.
Alarm summary logs can also use a lot of memory, so you should strictly limit their maximum size, especially if you are using many alarm notifiers. If alarm summary logs are filling up because alarm conditions are toggling back and forth, you can prevent that by configuring a deadband value in the Alarm Generator criteria options, or you can clear the Clear Required and Acknowledgement Required checkboxes in the Alarm Notifier data point options to cause the alarm to automatically clear itself. You can also free up memory by reducing the number of alarm notifiers.
The i.LON 100 Web server doesn't accept user names longer then 18 characters and passwords longer then 17 characters.
Workaround: Enter user names of 18 characters or less and passwords of 17 characters or less.
You cannot change the i.LON 100 LonTalk address from the i.LON 100 configuration Web page when the i.LON 100 device state is hard-offline.
Workaround: Ensure the i.LON 100 device is online before changing its LonTalk address. Recommission the i.LON 100 if necessary.
The i.LON 100 email substitution does not properly allow an alarm limit to be reported within the text body of an email sent as a result of an alarm condition.
Workaround: None. Do not specify an alarm limit substitution (%lm).
Node Object.NVL_nviDateEvent, Node Object.NVL_nvoDeviceAlarm, and Calendar.NVL_nvoEcDateEvent, may be displayed as raw bytes of data in a Web page or via SOAP response.
Workaround: For NVL_nviDateEvent and NVL_nvoDeviceAlarm add a Node Object shape to the LonMaker drawing before clicking Resync in the i.LON 100 Configuration Plug-in. Likewise, for NVL_nvoEcDateEvent, add a Calendar shape to the LonMaker drawing before clicking re-sync.
If you attempt to define a Calendar via SOAP with more than 255 exceptions, the i.LON 100 server may crash.
Workaround: Do not use the EventCalendarSet SOAP function to define a Calendar with more than 255 exceptions.
When using an NVE style data point as an output in both a Scheduler and another application, updates to the data point from the other application that are suppressed (due to the Scheduler priority) while the Scheduler is active will not be propagated when the Scheduler becomes inactive.
Workaround: Use an NVL data point instead of an NVE data point, or do not share NVE data points in the Scheduler with other applications.
Alternatively, set the poll rate for the NVE point to zero in the i.LON 100 configuration plug-in Data Points properties page. If the point is used in the Data Logger, set the poll rate for the point to zero as well on the Data Logger page in the plug-in.
If you attempt to stop loading the View Data Logs Web page or any of the View Alarm Web pages, you may see a JavaScript runtime error in Internet Explorer.
Workaround: Click the Reload button in Internet Explorer, and then wait for the page to load completely. The load is not complete if you see either of the following messages: "Gathering log information" or "Please wait, reading log."
The Text Secret Phrase field for the MD5 authentication key is not persistent on the i.LON 100 configuration Web page, unlike the same field in the LonWorks® Interfaces control panel on the computer. When you enter the phrase in the Web page and then click the Submit button, the Web page will be refreshed with the resulting numeric key (created from the text phrase), and the text phrase is no longer displayed.
Workaround: Refer to the LonWorks Interfaces control panel applet if you need to reenter the original text phrase.
If the i.LON 100 MD5 authentication key is non-zero, and you change the key in the LNS computer's LonWorks Interfaces control panel to be all zeros, and you then make a connection to the i.LON 100 server using that interface (which will remotely update the key on the i.LON 100 server), the key value in the i.LON 100 Security Web page will display a non-zero value.
Workaround: The two keys are equivalent, and the non-zero key (which is based on one of the Neuron IDs assigned to the i.LON 100 server) is the one that is actually used to authenticate the connection. An all-zero key is simply an alias for that non-zero key, which will be unique for each i.LON 100 server.
Dreamweaver/MX fails when trying to save files to the i.LON 100 server using its built-in FTP client.
Workaround: Use a different FTP client such as Internet Explorer 6 or newer to transfer files to the i.LON 100 server.
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 Internet Server 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:
· “Licensed Software” means the i.LON Utilities and i.LON System Image.
· “i.LON Utilities” means the i.LON Internet Server computer software utilities listed in the UTILITIES.TXT file, and associated media, printed materials, and online or electronic documentation, including without limitation any and all executable files, add-ons, stencils, templates, SmartShapes(r) symbols, filters, tutorials, help files, web pages and other files, that accompany such software or are in the accompanying documentation;
· “i.LON Server” means the i.LON 1000™ Internet Server or the i.LON 100™ Internet Server, as the case may be;
· “i.LON System Image” means the i.LON Internet Server firmware preloaded on the device or listed in the SYSTEM.TXT file, and associated media, printed materials, and online or electronic documentation, including without limitation any and all executable files, tutorials, help files, web pages and other files, that accompany such software or are in the accompanying documentation.
· “LonWorks/IP Channel” means a collection of i.LON Internet Servers that can directly exchange LonTalk packets with each other without the need of a LonTalk router. A LonWorks/IP Channel is specified by the list of unicast IP addresses, exactly one for each i.LON Internet Server.
·
“Configure” means to provide a
valid LonTalk Domain, Subnet, and Node address, as well as valid Group, Network
Variable Selector, and Message Tag values, and device state information as
defined by the LonTalk Protocol to the i.LON Internet
Server.
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:
use the i.LON Utilities internally to create LonWorks/IP Channels and to Configure i.LON Internet Servers to serve web pages;
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;
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:
use the Licensed Software for purposes other than the purposes set forth above;
copy the Licensed Software except as expressly permitted above, or copy the accompanying documentation;
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
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 LON WORKS 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 reexport 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, reexport, 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 1000 ™ Internet Server, i.LON 100 ™ Internet Server and Neuron are U.S. registered trademarks or trademarks of Echelon Corporation. SmartShapes is a U.S. registered trademark of Visio Corporation. Cisco NetWorks is a registered trademark of Cisco Systems.