IzoT® Resource Editor ReadMe First
Release 4.40, December 2015

Copyright © 1998 – 2015 Echelon Corporation
All Rights Reserved

1      Introduction

This document describes IzoT Resource Editor Release 4.40.  This document contains important information not included in the IzoT Resource Editor User's Guide or the Resource Editor help file.  Additional information and updates, including critical updates, may be available from Echelon at www.echelon.com/downloads or from LonMark® International at www.lonmark.org.

2      Contents

1        Introduction. 1

2        Contents. 1

3        New Features. 1

4        Requirements. 2

5        Repairing an IzoT Resource Editor Installation. 2

6        Known Problems and Workarounds. 3

6.1        Resource Editor 3

7        Compatibility. 6

3      New Features

Release 4.40 of the IzoT Resource Editor includes the following new features:

·        Version 15.00 Standard LonMark Resource File Set— see the Version 15.00 LonMark Resource Files ReadMe First document for a description of the new profiles and types added in Version 15.00.

·        Version 2.41 LonMark Resource File API—the LonMark Resource File API provides programmatic access to the LonMark resource files installed on the same computer.  Version 2.41 or newer of the LonMark Resource File API is required for the Version 15.00 Standard LonMark Resource File Set.  See Compatibility for a description of how to create a version of the Standard LonMark Resource File Set that is compatible with prior versions of the LonMark Resource File API.

4      Requirements

The following are minimum hardware and software requirements for the computer running the IzoT Resource Editor:

·        Microsoft® Windows.  Windows 10 (64-bit and 32-bit), Windows 8.1 (64-bit and 32-bit), Windows 8 (64-bit and 32-bit), Windows 7 (64-bit and 32-bit), or Windows XP with SP3 (32-bit).     

·        An Intel® Pentium® or compatible processor meeting the minimum Windows requirements for the selected version of Windows. 

·        10 megabytes (MB) free hard disk space, plus the minimum Windows requirements for the selected version of Windows. 

·        512 MB RAM minimum. 

Note:  For Windows 10, Windows 8, and Windows 7, Echelon’s testing for the IzoT Resource Editor was performed on computers that have a minimum of 2 GB of RAM. 

·        1024x768 or higher‑resolution display with at least 256 colors.

·        Mouse or compatible pointing device. 

5      Repairing an IzoT Resource Editor Installation

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 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.

4.      Click Click Here for Support Information.

5.      Click the Repair button.

6.      Repeat steps 1 – 5 for each program to be repaired in the Add or Remove Programs program list.

The programs that you may need to repair in the Add or Remove Programs program list include the following:

1.      Echelon IzoT Resource Editor

2.      LonMark Resource Files 15.00

6      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.

6.1    Resource Editor

You may see a “file corrupted” error if you attempt to create or edit functional profiles in a resource file set in a Windows offline folder (for example, folders on a computer other than the computer running the Resource Editor, which you have identified as an offline folder to Windows).  You may also see a Windows “blue screen” when you shut down Windows after editing a resource file set in an offline folder.  Workaround: Do not create or edit resource files in offline folders.  You can copy resource file sets to and from offline folders, but do all editing in local folders, or in remote online folders.  (22113)

The Resource Editor sometimes displays the incorrect string index for a language string.  When you add a new network variable or configuration property member to a functional profile and the type of the new member is defined in a different resource file set than the profile, creating a new text string or comment for that profile member may cause the resource editor to display an incorrect index for this new text.  Workaround: You can ignore the incorrect display; the correct index is stored in the resource file.  (22091)

If you change a type that is referenced by other types, the override values and display formats of the referring types may become invalid.  Workaround: Verify the override values and display formats for any referring types when you change a type definition.  (28148)

You cannot host reports created by the Resource Report Generator on multiple domains.  Workaround: If you wish to host resource reports on a Web server, make sure to host all reported resources, and the Templates folder, on the same domain.  (27921, 27904)

The resource editor attempts to detect gaps between adjacent bitfields.  A gap between two adjacent bitfields b1 and b2, with width w1 and w2 and offset o1 and o2, exists if (o1+w1 != o2) and (o1+w1+w2 <= 8). 

Example 1:

typedef struct {

   unsigned b1 : 1;   // offset 0

   unsigned b2 : 1;   // offset 3

} example1;

The resource editor detects a gap of 2 bits between b1 and b2.  It will produce a related warning, and the user can have the gap being tolerated or being closed (o2 will be changed to make the gap disappear).

Example 2:

In some circumstances, the Resource Editor might incorrectly detect gaps between bitfields when there aren't any, or where those gaps exist but cannot be closed.  This might be the case when an aggregate type (struct, union) includes another aggregate, where the inner aggregate's last member is a bitfield and the first (outer) member following the inner aggregate also is a bitfield.

typedef struct {

   struct {

      unsigned b1 : 1;   // offset 0

   } x;

   unsigned b2 : 1;      // offset 3;

} example2;

An aggregate forms a fixed compound, and bitfields within and outside that aggregate cannot share the same byte.  The same also applies to aggregates that are organized as arrays and end with a bitfield member; these, too, cannot share the same byte for storage.  Workaround: When the resource editor incorrectly determines such a gap, make sure to respond to the message indicating you do not wish the gap to be closed by the resource editor.  If you have requested the gap to be closed already, then you should review and re-adjust the offset values of adjacent bitfields in the type.  (28376)

The Resource Editor may omit the display of unnamed bitfields when displaying the “C structure definition” view of the type.  For example, the definition view of SNVT_file_req does not show an unnamed bitfield of 4 bits within the gp structure, between the retry and tx_timer bitfields.  Workaround: You can view the bitfield sizes and offsets of each field separately and verify that they are correct.  (44728)

When you mark a resource as deleted, the Resource Editor requests confirmation.  It is possible to refuse that confirmation (click No to indicate the resource is not to be deleted), and it is possible to set the Don’t Show this Again checkbox at the same time.  If you do this, the resource editor will no longer allow a resource to be deleted (as it memorizes the previous answer to the confirmation query).  Workaround: Close and re-open the resource editor if you are using the standalone Resource Editor.  (28603)

No warning is shown when a language string resource is marked as deleted.  Workaround: To undelete a language string resource that has been accidentally marked as deleted, but has not yet been purged, set the Show Deleted Items checkbox in the Resource Editor options and remove the tilde character (“~”) from the string.  To undelete a string that you have accidentally deleted and purged, edit the language file in the Resource Editor and edit the "Purged Record~" placeholder that will be shown in place of the purged string, entering the lost content of the purged string.  (28605)

When editing a standard enumeration, the TAB key moves the focus to read-only fields such as the minimum or maximum value fields.  Workaround: Press TAB until the focus has reached the desired field or command, or click the desired field or command with the mouse pointer.  (28621)

The resource editor shows the full location and base name of the currently selected resource file set in a small informational pane above the resource hierarchy.  For example, this pane displays c:\LonWorks\Types\Standard, when the standard resource file set is selected and installed in the default location.  Sometimes, this text display changes color.  Workaround: Ignore the color change.  Obtain the name and location of the currently selected resource file set from the resource hierarchy, if needed.  (28266)

When editing a functional profile that includes member configuration properties that refer to unavailable configuration property types, you cannot directly remove these member configuration properties from the profile.  A configuration property type might become unavailable when purging the type after adding it to the profile, or by removing the related resource files from the resource catalog.  Workaround: To remove such a configuration property member for the profile, edit the profile, select the property, set its reference to any arbitrary but valid configuration property type, and then remove the property from the profile.  Alternatively, correct the symptom by (re-) adding the related resource file to the resource catalog or by re-defining the configuration property type as needed.  (28817)

If you cut or copy an entire resource file set, and then paste it to a folder that already contains another resource file set, the paste operation will sometimes fail. An error message will be shown, reporting the failure.  Workaround: Always paste to an empty folder when pasting an entire resource file set.  (28894)

When an aggregate network variable or configuration property type contains members that refer to another network variable type, details of that referred type are shown when the structure or union member is selected.  These details include the size of the referred-to network variable type in bytes.  The reported size might show an outdated value if the referred-to type has been edited within the same Resource Editor session.  Workaround: The size is shown for information only—you can safely ignore the outdated value.  To see the correct size, exit and restart the Resource Editor.  (30205)

The Resource Report Generator reports the size of some types incorrectly.  If the type references another type in the resource files, and the referenced type changes size after the referencing type is created, the reported size for the referencing type will be incorrect.  Workaround:  Delete and re-create the referencing type.  (49366)

The Resource Report Generator cannot resolve configuration property “applies to” information when the CP applies to an inherited network variable member.  Workaround: Ignore the Resource Report Generator output for CPs defined in an inheriting profile that applies to an inherited NV.  (43658)

Release 4.0 of the Resource Editor adds support for invalid value overrides.  Resource files created with invalid value override entries can be read by older LonMark Resource File API runtimes, but they should not be written to by older LonMark Resource File API runtimes due to potential file corruption.  Workaround: If you are developing resource files with Release 4.0 or newer of the Resource Editor, be sure that all members of the development team are updated to at least the 4.0 version of the Resource Editor.  (52729)

The Resource Editor allows C language keywords to be used for enumeration member names, but the resulting include files will not compile.  Workaround: Don’t use C language keywords for enumeration member names.  (55103)

7      Compatibility

Release 4.0 and higher of the Resource Editor generates enhanced resource files, which are not compatible with tools or devices based on any version of the LonMark Resource File API prior to version 2.4.  This includes all LNS® 3.08 and 3.27 tools not running on the same computer with the IzoT Resource Editor, IzoT NodeBuilder, NodeBuilder FX, NodeBuilder FX SR1, or NodeBuilder Resource Editor 4.02 software, or embedded software running on an i.LON 100 or i.LON 1000 Internet Server Release 1.  Workaround: To read the resource files on Windows clients, upgrade the LonMark Resource File API to version 2.41 or newer by either installing the IzoT Resource Editor software, installing an upgrade to the application that includes the version 2.4 API, or downloading and installing the LonMark Resource Files 15.00 (or higher) software, which includes the 2.41 API or higher, from www.lonmark.org.  To read the resource files on non Windows clients, or on Windows clients that have not been upgraded to the 2.41 API, you can first convert the resource files to an older format using the IzoT Resource Converter Utility.  To start the Resource Converter Utility, open your Windows Start menu, point to Programs > Echelon IzoT NodeBuilder Software, and then click Resource Converter Utility.  The Resource Editor User’s Guide describes how to use the utility, describes the changes in each format version of the resource files, and describes the required version of the Resource File API for each format version.


Echelon, LON, LonWorks, IzoT, LonMaker, LonManager, LonTalk, Neuron, 3120, 3150, LNS, OpenLNS, ShortStack, and the Echelon logo are trademarks of Echelon Corporation that may be registered in the United States and other countries.

LonMark and the LonMark Logo are registered trademarks of LonMark International in the U.S. and other jurisdictions.  Other brand and product names are trademarks or registered trademarks of their respective holders.