ISI Library ReadMe
Release 4.0, October 2009

Copyright © 2005 – 2009 Echelon Corporation
All Rights Reserved

1      Overview

This document contains important information for the ISI library that is not included in the ISI library documentation.

For the latest information about updates to the ISI library and examples, see the ISI Web page at www.echelon.com/isi.

2      Contents

1        Overview.. 1

2        Contents. 1

3        Requirements. 2

3.1         PC Hardware Requirements. 2

3.2         PC Software Requirements. 2

4        Documentation. 2

5        Repairing Software Installations. 2

6        Changes in Release 4.00. 3

7        Changes in Release 3.02A.. 3

8        Changes in Release 3.02. 3

9        Changes in Release 3.01. 3

10     Changes in Release 3.00. 4

11     Known Problems. 4

11.1       Polling ISI Network Variables. 4

11.2       Selector Monitoring in the ISI Packet Monitor 4

 

3      Requirements

3.1    PC Hardware Requirements

The following are minimum requirements:

3.2    PC Software Requirements

The following are minimum requirements:

4      Documentation

The ISI Programmer’s Guide describes how you can use Interoperable Self-Installation (ISI) to create networks of control devices that interoperate, without requiring the use of an installation tool.  This guide also describes how to use the ISI Library to develop devices that can be used in both self-installed as well as managed networks.

The ISI Protocol Specification describes the ISI protocol used by the ISI library.

Both of these documents are available after installing the ISI library or Mini EVK, and are available online at www.echelon.com/isi.

5      Repairing Software Installations

This software product is installed using Microsoft Windows Installer technology.  Some components of this product were also present in earlier installations of Echelon products that did not follow the Windows Installer installation rules.  As a result, installing some older Echelon products after installing this product may revert some files to obsolete versions.  Workaround: If you experience unexpected software behavior changes as a result of another software installation, you can repair this product installation through the following procedure:

  1. Open the Windows Control Panel.
  2. Double-click Add or Remove Programs.
  3. Click program to be repaired in the program list.  This product name is the Echelon Interoperable Self-Installation Developer’s Kit.
  4. Click Click Here for Support Information.
  5. Click the Repair button.

6      Changes in Release 4.00

This release of the ISI libraries supports the Echelon ShortStack FX, NodeBuilder FX, and Mini FX development tools.

This release also corrects a problem with Echelon PL 3170 Smart Transceiver support that could result in incorrect ISI initialization and timing parameters when using ISI on this chip.  The problems sometimes caused the Neuron firmware to log divide-by-zero errors.  (54075)

7      Changes in Release 3.02A

The IsiPl3170.lib library, supporting ISI development with the Echelon PL 3170 Smart Transceiver, was mistakenly shipped as an empty library in the 3.02 release, resulting in link errors when it was used.  The 3.02A release inserts the correct version of this library from ISI 3.01 with the rest of the contents of 3.02.

You can determine whether you have ISI 3.02A instead of ISI 3.02 by the following method:

  1. Open the Windows Control panel.
  2. Click on Add or Remove Programs.
  3. Select Echelon Interoperable Self-Installation Developer’s Kit on the list of programs.
  4. Click on Click here for support information for the ISI entry.
  5. The version number shown in the support information dialog will be 3.02.08 for ISI 3.02A.  It will be 3.02.07 for ISI 3.02.

8      Changes in Release 3.02

This release adds support for the Echelon ShortStack 2.1 release and ISI-enabled Micro Servers.

9      Changes in Release 3.01

This release adds support for the Echelon PL 3170 Smart Transceiver.  The PL 3170 Smart Transceiver provides most of the ISI library contents in ROM, leaving more room in EEPROM for application code.  The ISI Programmer’s Guide and the ISI Protocol Specification have been updated to describe ISI device development with the PL 3170 Smart Transceiver.  NodeBuilder FX, Mini FX, or NodeBuilder 3.14 (NodeBuilder 3.1 with Service Pack 4) is required to develop applications for the PL 3170 Smart Transceiver.

10  Changes in Release 3.00

The ISI 3 changes are described in the ISI Programmer’s Guide and the ISI Protocol Specification for Release 3.  This section describes additional information about the changes in this release.

The ISI Packet Monitor Application is a new tool included with the ISI 3 Developer’s Kit.  You can use this tool to monitor and analyze ISI messages. The ISI Packet Monitor application requires Echelon OpenLDV 2.1 or newer, and the Microsoft .NET Framework 1.1 Redistributable.  If you currently do not have .NET Framework version 1.1 installed, you can download it from www.microsoft.com/downloads.  If you do not currently have OpenLDV 2.1 or newer, you can download it from www.echelon.com/openldv. (41808)

ISI 3 fixes a problem where replacement selectors were sometimes calculated incorrectly by the ISI 1 and 2 engines. (40512)

11  Known Problems

The ISI Library has the following known problems.  Numbers in parentheses at the end of the descriptions are Echelon's internal problem tracking IDs.

11.1 Polling ISI Network Variables

By default, ISI connections use open groups (groups without a specified size) which are incompatible with polling.  Workaround: Do not poll input NVs that are members of ISI connections. (48760)

11.2 Selector Monitoring in the ISI Packet Monitor

The RegisterConnection() method, which handles CSMI messages, identifies connections through the complete connection header, which includes the connection identifier (CID) and the base selector for the reported set.  If the connection (or a subset of it) moves to a new selector range, the ISI Packet Monitor will continue monitoring the now non-existent old connection, and also create a new record for the new connection.  Workaround: Ignore the extra connection, or close and restart the ISI Packet Monitor.   (53390)