LonMaker® Integration Tool Turbo Editions
ReadMe File
Release 3.22, June 2008

Copyright © 1998 – 2008 Echelon Corporation
All Rights Reserved

1      Introduction

This file contains important information not included in the LonMaker User's Guide and help files.  Additional information and updates, including critical updates, may be available at www.echelon.com/downloads.  See Echelon’s Knowledge Base at www.echelon.com/support for answers to frequently asked questions.

WARNINGS:

2      Contents

1        Introduction. 1

2        Contents. 1

3        Release Identification. 2

4        Problems Fixed in LonMaker 3.22. 2

5        Problems Fixed in LonMaker 3.21. 4

6        Problems Fixed in LonMaker 3.2 SR-A.. 5

7        Known Problems and Workarounds. 6

7.1        Start-up. 6

7.2        OpenLDV Network Driver 7

7.3        Visio. 8

7.4        LonMaker Design Manager 8

7.5        LonMaker 8

7.6        Device Templates. 8

7.7        Recovery. 9

7.8        LonMaker Browser 9

7.9        Multi-byte Characters. 9

8        Documentation Updates. 9

 

3      Release Identification

This ReadMe file applies to the LonMaker Integration Tool Turbo Editions with Service Pack 2 (SP2) applied.  You can verify that you have this release by starting the LonMaker software, clicking the LonMaker icon in the top-left corner of the LonMaker Design Manager, and then clicking About Echelon LonMaker.  The About Echelon LonMaker Design Manager dialog appears.  This dialog displays the version number of your LonMaker software.  For LonMaker Turbo with SP2, the version number is 3.22.xx, where xx is the build number of the software.  LonMaker 3.22 fixes the problems listed in the next section.

4      Problems Fixed in LonMaker 3.22

The following table summarizes problems fixed in LonMaker 3.22, which also includes all fixes from earlier Service Packs.  The EPR column lists Echelon internal problem tracking numbers.  

EPR

Description

N/A

LonMaker Turbo Edition now supports the Windows Vista Operating System.

45359

In some instances, some text on the Design Manager dialog would be truncated, obscuring some fields or buttons.

45871

If a dynamic functional block (FB) was created from an FB type which inherited NVs from a standard FB, LonMaker would not automatically create the inherited NVs.

45888

In some instances, if an NV was created or renamed with more than 16 characters, LonMaker would truncate the NV name and/or report that the drawing was out of sync.

46790

If the same NV name from the two or more FBs on the same device were bound to the same connection, LonMaker would not update the drawing correctly if one of those connections was removed.

46922

In some cases, exporting a network to XML would fail with an LNS #38 error (“An application device object is required”).

46943

In some cases, if a device was copied along with its FBs and reference connections, LonMaker would not update the drawing correctly with the new connections.

47540

In some cases, when a device template was uploaded from a device, the name assigned to the new template was not correct.

47629

In some cases, creating a shape for a remote NSD would fail with LNS error #6 (“Object not found”).

47630

In some cases, an attempt to replace an NSD would fail with LNS error #140 (“Not allowed for permanent device”)

47647

Occasionally, when a device was created and commissioned in the same operation, LonMaker would clear the Neuron ID property assigned to the device.

47726

LonMaker was not correctly setting the polling interval for monitored connections.

47858

LonMaker was preventing FB shapes from being resized, even when auto-sizing was disabled.

48219

If a dynamic FB was removed from a device by an application other than LonMaker, an exception was reported when an attempt was made to resynchronize the drawing.

48252

If an FB was moved into a new subsystem, LonMaker would delete the FB from the old subsystem, but not re-create it in the new subsystem.

48323

In some cases, the LonMaker Browser would not properly display CP values in the LonMaker Browser Details and Table dialogs.

48681

In some cases, an attempt to add a dynamic NV to a static FB would fail.

 

5      Problems Fixed in LonMaker 3.21

The following table summarizes problems fixed in LonMaker 3.21, which also includes all fixes from LonMaker 3.2 SR-A.  The EPR column lists Echelon internal problem tracking numbers.  

EPR

Description

42397

The LonMaker tool truncated the right side of some dialog boxes on some versions of Windows.

42357

The LonMaker Browser did not correctly display the values of enumerated values if they were derived from another SNVT, SCPT, UNVT, or UCPT.

42364

The LonMaker Browser edit field did not update the value of an NV or CP when ENTER key was pressed.

42404, 44133

LonMaker did not update the XIF and APB fields in the device shape when they were upgraded.

42406

The LonMaker tool did not properly update the drawing if another application added a root-level subsystem.

42407

The LonMaker tool did not properly update the drawing when a root subsystem was moved to another subsystem.

42512

The LonMaker tool did not save changes to default options that were modified within the Design Manager.

42597

Making a copy of a NodeBuilder® device shape would fail in some cases.

42761

In some cases, when a master shape contained both a functional block and a hub connector, the LonMaker tool would incorrectly update the drawing.

42776

In some cases, there were performance problems when copying a subsystem with a large number of fan-in connections.

42777

In some cases, the LonMaker tool would create multiple reference connector shapes for the same hub NV.

42828

Making a connection descriptor change to a large connection (> 25 targets) would fail with an NS #1 error.

43043

Viewing the details of a structure NV in the LonMaker Browser would cause the browser to crash.

43044

The LonMaker Browser would sometimes show CPs using the Localized format, even when the non-localized format was explicitly requested.

43093

The drawing was not properly updated if you used a functional block master shape to create a functional block, and the shape contained shapes for NVs that do not exist on the device.

43107

In some cases, the option to upload the XIF from the device was disabled when creating a new device.

43143

LonMaker installation would hang on Windows Vista.

43644

If a device master shape specified the requiresVFB option as 0, the LonMaker tool would not display the last defined functional block.

43710

Configuration network variables (CPs implemented as NVs) were not being set to their default values when a new device was created.

43758

Performing an application image download and a replace at the same time would fail under certain conditions.

44139

In some cases, when a subsystem was moved on a remote client, the update to the drawing would fail on other clients.

44256

If a Visio page name was modified, the LonMaker tool would report an error and not update the database.  This problem was also not corrected by resync

44257

In some cases, the LonMaker tool would not properly create connections that were copied along with a supernode.

44279

If you copied a functional block and related reference connections in the same operation, and the functional block creation failed and the LonMaker tool would delete the original connector shapes from the drawing.

44358

When a NodeBuilder device was de-commissioned and then was re-commissioned and an application image load was performed, LonMaker would not use the correct XIF and NXE path.

6      Problems Fixed in LonMaker 3.2 SR-A

The following table summarizes problems fixed in LonMaker 3.2 SR-A.  Service Release A installed the same version of the LonMaker software as the original LonMaker Turbo Editions, and also included a separate installer for OpenLDV 3.3C as described in OpenLDV Network Driver.  The EPR column lists Echelon internal problem tracking numbers.                                                                                     

EPR

Description

42290

The LonMaker installer did not accept serial numbers from copies of the LonMaker tool included with the NodeBuilder Development Tool.

43028

Some of the datasheets on the LonMaker CD were out-of-date.

N/A

Added the OpenLDV 3.3C installer to the LonMaker CD.

 

7      Known Problems and Workarounds

Following are known problems and workarounds for the LonMaker software.  Please report any additional problems to support@echelon.com.

7.1    Start-up

The Visio macro security settings sometimes become corrupted.  When this happens, Visio may start without the LonMaker software when you attempt to start the LonMaker tool.  Workaround: To restore the link to the LonMaker software, follow these steps:

  1. Open the Windows Start menu, point to Program Folders, and then click Microsoft Visio.  Visio starts.  If you see the LonMaker menu, skip the rest of this procedure.
  2. Open the Tools menu, point to Options, and then click Security.
  3. If any of the check boxes under Macro Security are not selected, select them, click OK, and then exit and restart the LonMaker tool.  If you restart the LonMaker tool and you see the LonMaker menu, skip the rest of this procedure.
  4. Open the Tools menu, point to Options, point to Advanced, and then click File Paths.
  5. Write down the LonMaker path shown in the Add-ons box, and then delete it.  By default, the LonMaker path is C:\LonWorks\LonMaker\Visio.  The path may be followed by a semicolon if there are any additional paths in the list.
  6. Exit and restart Visio.
  7. Open the Tools menu, point to Options, point to Advanced, and then click File Paths.
  8. Enter the LonMaker path you wrote down in step 5 in the Add-ons box.  Include the semicolon if there are additional paths after the LonMaker path.
  9. Exit Visio and then start the LonMaker tool. (39839)

If you open a LonMaker drawing created with an earlier version of the LonMaker tool, Visio may display a message starting with the following text: “Macros in this document are disabled because the security level is high…”  If you click OK, the drawing opens, but most of the LonMaker functionality is disabled.  Workaround: To enable the LonMaker software to work with a drawing created with an earlier version of the LonMaker tool, use the following steps to decrease Visio's macro security.

  1. Open the Tools menu.
  2. Click Options, select the Security tab, and then click Macro Security.  A dialog appears allowing you to select Low, Medium, High, or Very High security.
  3. Select Low or Medium security.  If you select Low security, you will be able to open the drawing without a prompt.  If you select Medium security, you will be prompted to enable macros for unsigned network drawings or network drawings signed by companies that have not been added to the trusted signatures list.  

Visio's security level is persistent.  When you change Visio's security level, it will be the security level for Visio every time it is started until you change it again.   Alternatively, you can apply your own company's digital signature to any LonMaker drawings to disable macro warnings for those drawings.  For detailed instruction on how to do this, see the following page on Microsoft's Web site (you may need to concatenate this URL, 40186):

msdn.microsoft.com/library/default.asp?url=/library/en-us/odeopg/html/deovrusingdigitalcertificatestoproducetrustedsolutions.asp

There have been a few cases of the LonMaker Design Manager failing to start correctly on a computer running Windows 2000.  Workaround: Contact Echelon support for a workaround. (39363)

If you are using the LonMaker Trial Edition, it may fail to start if you change the time on your computer.  Workaround: If you moved the time forward, reboot your computer.  If you moved the time backward, contact Echelon support. (28224)

7.2    OpenLDV Network Driver

Multiple warning messages may be displayed when running OpenLDV on Vista.  Workaround: Download and install OpenLDV 3.4 (or newer) from the Network Interfaces category at www.echelon.com/downloads.  (43753, 43755, 43754, 43772, 46103)

In some cases, the LonMaker Turbo Edition installation may cause PCLTA-10, PCLTA-20, and PCC-10 card device driver entries to disappear after reboot.  Workaround: If you are using a PCLTA-10, PCLTA-20, or PCC-10 card, after you have installed the LonMaker Turbo Edition software, download and install OpenLDV 3.4 (or newer) from the Network Interfaces category at www.echelon.com/downloads. (42583)

The LonMaker Turbo Edition installation will delete the PCC10L7 image used with PCLTA-10, PCLTA-20, and PCC-10 cards.  This image is not used with the LonMaker tool, but may be required for some third-party applications.  Workaround: If you need the PCC10L7 image, after you have installed the LonMaker Turbo Edition software, install OpenLDV 3.4 (or newer) from the Network Interfaces category at www.echelon.com/downlaods. (42584)

If you are using a RoHS-compliant PCLTA-20/SMX network interface card, the OpenLDV driver installed by the LonMaker Turbo Edition software installer will not recognize the card.  Workaround: After you have installed the LonMaker Turbo Edition software, install OpenLDV 3.4 (or newer) from the Network Interfaces category at www.echelon.com/downloads. (42396)

7.3    Visio

When you open a LonMaker document, more than one instance of the document may open in Visio, or additional documents may be opened at the same time.  Workaround: To prevent opening the extra drawing or drawings, follow these steps:

1.   On the LonMaker menu, click Synchronization/Resynchronize.

2.   Select Reset Visio Workspaces.

3.   Click Next.

4.   Select either Only the Current Drawing to update the workspace for the current drawing only, or All Drawing Files in the Network to update the workspace for all drawing files. (40066)

7.4    LonMaker Design Manager

Occasionally, if you attempt to reselect the LonMaker Design Manager window after opening a LonMaker network, you may see a Server Busy dialog box with Switch To and Retry buttons. Workaround: Click the Retry button. (39851)

If you press the ENTER key on the LonMaker Default Options tab, the displayed options will disappear. Workaround: Either re-select the category or switch to another tab and then reselect the LonMaker Default Options tab. (41369)

If you use the LonMaker tool from a different user account than you used to install the LonMaker software you may encounter an error the first time you attempt to open or create a network.  The error will state “Cannot start LonMaker.  If you have run Visio directly, please instead run LonMaker Design Manager…”.  Workaround: Exit Visio, exit and restart the LonMaker Design Manager, and then re-open (or re-create) the network.  If the problem persists, reset the Visio workspaces as described in section 7.4. (23900)

When running under the Windows Vista Operating System, the system menu cannot be accessed by right-clicking in the title bar. Workaround: Left or right-click on the icon in the left corner of the title bar. (48981)

7.5       LonMaker

If you move a reference connection in one instance of LonMaker, other instances of LonMaker will not be updated with the new location of the reference shape. Workaround: Replicate the drawing update in all instances of LonMaker, or use the auto-alignment feature.

7.6       Device Templates

If you set the Self-doc Consistency option for a device template to the Identical on All Devices setting, you may receive an NS #59 error when setting the option, or you may receive the same error when you set this option and try to commission more than one device with identical self-documentation information.  Workaround: If you see this error, do not set the Self-doc Consistency option to Identical on All Devices—select one of the other settings. (41664)

7.7       Recovery

If you recover a network, some of the devices in the top-level subsystem may be recovered to a subsystem named “Subsystem 5”, which will not be the top-level subsystem.  Workaround: If you see this error, move the devices and functional blocks to the top-level subsystem as described in Changing the Subsystem for a LonMaker Shape in the LonMaker User’s Guide. (41815)

7.8       LonMaker Browser

If you have the LonMaker help file open at the same time that the LonMaker Browser is active, and then you close the LonMaker Browser, the LonMaker help file also closes. Workaround: Do not close the LonMaker Browser if you wish to continue using the LonMaker help file, or re-open the LonMaker help window after closing the LonMaker Browser. (39570)

7.9       Multi-byte Characters

The LonMaker tool and some plug-ins may fail if devices, functional blocks, or network variables have multi-byte character names.  Workaround: If you see this error, try changing the name in the LonMaker drawing and then restarting the plug-in.  If that does not correct the problem, do not use a multi-byte character name. (41701)

8      Documentation Updates

The LonMaker User’s Guide incorrectly states that Visio Service Pack 2 is included on the LonMaker CD.  The correct reference is LonMaker Service Pack 3.

The LonMaker User’s Guide incorrectly states that the maximum number of subnet IDs is 127.  The correct number is 255. (43625)

When using multiple LonMaker clients for the same network, if a connection reference shape is moved on one client, the reference shape is not moved on the other clients. (44162)