=============================================== LonMaker(tm) Integration Tool Readme File Release 3.12, October 2002 =============================================== Copyright (c) 1998-2002 Echelon Corporation. All Rights Reserved. This file contains important information not included in the LonMaker User's Guide or the LonMaker help file. Additional information and updates, including critical updates, may be available on the LonMaker Home Page at www.echelon.com/lonmaker. Update and upgrade notifications will be sent to registered users, so be sure to register your software. This file covers LonMaker 3.12, which is created by applying LonMaker 3.1 Service Pack 2 to LonMaker 3.1. Service Pack 2 may be applied to any LonMaker 3.1 installation, with or without LonMaker 3.1 Service Pack 1. Service Pack 2 incorporates all changes from Service Pack 1 and adds additional changes as described in this document. ************************* WARNING ************************* WARNING: The LonMaker help file installed by the LonMaker setup program may generate a "Cannot find or load the file Inetwh32.dll" error, followed by a "An error exists in the Help file" message, when you open it and is missing a few updates to the introduction and a few topics in the Contents pane. WORKAROUND: Copy the lonmaker.hlp and lonmaker.cnt files from the LonMaker CD to your LonMaker program folder (c:\LonWorks\LonMaker by default). Set the option to display hidden files in Windows Explorer and delete the lonmaker.gid and lonmaker.ftg files in your LonMaker program folder. *********************************************************** CONTENTS ======== 1. Release History 2. Installing Release 3.1 Service Pack 2 3. Service Pack Fixes 3.1 Changes and Problems Fixed in Service Pack 2 (Release 3.12) 3.1.1 Dynamic Network Variable Changes 3.1.2 LonMaker Template Digital Signature Expired 3.1.3 Shapes Not Restored During Resynchronization 3.1.4 SCPTnvType Processing 3.2 Problems Fixed in Service Pack 1 (Release 3.11) 3.2.1 Upgrading Devices Failed With Message Tag Connections 3.2.2 Controls Not Visible in Japanese Windows 3.2.3 Error When Deleting a Connection 3.2.4 Error While Merging Two LonMaker Networks 3.2.5 Moving Functional Blocks With Many Connections 4. Known Problems and Workarounds 4.1 LonMaker Credits 4.2 Adobe PostScript Driver 4.3 Regional Settings 4.4 Installation 4.5 Drivers and Network Interfaces 4.6 Windows 98 4.7 Windows Shutdown 4.8 Performance 4.9 Remote Clients 4.10 Configuration Properties 4.11 Connection Monitoring 4.12 Connections 4.13 Device Upgrade 4.14 LNS Server 4.15 LNS Text Box Control 4.16 LonMaker Browser 4.17 LonMaker Design Manager 4.18 LonMaker License Transfer Utility 4.19 LonMaker Shapes 4.20 LonMaker Startup 4.21 Merging Networks 4.22 Resource Files 4.23 Visio Limitations 4.24 Compatibility with Other Applications 4.24.1 LonMaker 3 4.24.2 LonMaker 1 and LonMaker 2 4.24.3 Other LNS Applications 4.24.4 NodeBuilder 1.5 4.24.5 Disk Defragmenters 4.24.6 Mijenix ZipMagic 5. Documentation Changes 5.1 Windows XP Support 5.2 LonMaker Help File 5.3 Data Formatting 5.4 Resource File Documentation 1. RELEASE HISTORY =================== Following is a summary of the LonMaker 3.1 and Service Pack release dates: LonMaker 3.1: December 2001 Service Pack 1 (LonMaker 3.11): June 2002 Service Pack 2 (LonMaker 3.12): August 2002 2. INSTALLING RELEASE 3.1 SERVICE PACK 2 ========================================= Service pack 2 can only be installed over LonMaker 3.1 (with or without Service Pack 1). To apply LonMaker 3.1 Service Pack 2 to any LonMaker releases prior to Release 3.1, you must first install a LonMaker 3.1 upgrade. You can install Release 3.1 over an existing LonMaker 2 or 3 installation, or you can install it as a new installation. If you have purchased LonMaker credits for Release 2 or 3, you should install Release 3.1 over your existing installation. The LonMaker 3.1 installation includes a complete LNS 3.04 runtime with LNS 3 Server, and new/updated drivers. The LNS 3.04 runtime includes LNS 3 Service Pack 4. To install Service Pack 2 over LonMaker 3.1, follow these steps: 1. If you are running Windows NT, Windows 2000, or Windows XP, log on with Administrator privilege. 2. Download the LMW312.exe file to any directory. 3. Shut down all LonWorks(r) applications that are running. 4. If the LNS Server application or any other LNS application is currently running as a Windows NT, Windows 2000, or Windows XP Service, stop the service. 5. Run LMW312.exe. If there are any errors detected during the execution of LMW312.EXE, the errors will be listed in the file PATCH.ERR in the LonWorks folder. WARNING: Do not set any options to search your path or subdirectories. Setting these options may cause the service pack update to fail. 6. Download and install the latest LNS 3 service pack. At the time of the release of this service pack, the latest LNS 3 service pack was LNS 3 Service Pack 7. You can download the latest LNS 3 service pack from www.echelon.com/lns. Follow the instructions provided with the LNS service pack to install it. 7. Re-start the LonWorks applications. 3. SERVICE PACK FIXES ====================== 3.1 Changes and Problems Fixed in Service Pack 2 (Release 3.12) ---------------------------------------------------------------- The following changes have been made and problems have been fixed in Release 3.12. 3.1.1 Dynamic Network Variable Changes --------------------------------------- To improve compatibility with devices with dynamic network variables, the LonMaker tool now uses different rules to assign names to new dynamic network variables. Following is a summary of the new rules. The term FBNV represents a network variable that is a member of a function block (as oppossed to a device NV, which is a network variable that is not a member of a functional block). o Dynamic FBNV names are limited to 12 characters, including any integer suffix which must be added to make the name unique within the functional block. o User cannot assign a dynamic FBNV name containing a suffix of "_" where is a three digit decimal number, unless the number is the same as the functional block index (in this latter case, this suffix does not count in the 12 character limit). o If the name specified by the user for a dynamic FBNV does not contain a "_" suffix where "" is equal to the functional block index, the LonMaker software will append such a suffix to the programmatic name of the FBNV. o When the user creates a dynamic FBNV by dropping a master shape or copying an existing functional block shape, the LonMaker tool will automatically truncate the FBNV name, if required, to meet the 12-character limitation. o If the user drags a master shape containing any functional blocks with dynamic network variables to a drawing, and the creation of any of the dynamic FBNVs fails, the functional block containing the failed dynamic FBNV will not be added, and all subsequent shapes in the master shape will not be processed, including any connections. o When renaming a dynamic FBNV, if the update to the FBNVs programmatic name fails for any reason, the name change will not be allowed. The format of the programmatic name of a dynamic FBNV is as follows: nnnnnu_iii where: nnnnn is 1 or more characters specified as the name of the FBNV; u is 0 or more decimal digits required to make the name unique within the functional block; iii is a 3-digit decimal number which equals the functional block index. Handling of dynamic device NVs has not changed, with the following exception: the names of dynamic device NVs cannot have a suffix of "_", where is a 3-digit decimal number. As was the case before, the following rules apply to dynamic device NVs: o When a dynamic device NV is created, the name specified must be valid for the programmatic name for the NV on the device. That is, the name is limited to no more than 16 characters, only alphanumeric characters may be used, and the first character must be a letter. In addition, the name must be unique if required by the device. If the name is not valid, the dynamic device NV will not be created. o When a dynamic device NV is renamed, the LonMaker tool will attempt to update the name of the NV on the device. If the update fails for any reason, the LonMaker tool will report the failure, leaving the name of the NV on the device unchanged, but will update the name locally. Creating connections, copying functional blocks, deleting functional blocks, and resynchronization sometimes failed with functional blocks -- other than the virtual functional block -- that contained dynamic network variables. If you delete a functional block that contains dynamic network variables, you will now be prompted to specify whether or not to also delete the dynamic network variables. 3.1.2 LonMaker Template Digital Signature Expired -------------------------------------------------- Opening a drawing created with LonMaker 3.1 results in a Security Warning message. This message is benign and can be safely ignored as long as you click Enable Macros for LonMaker drawings. Service Pack 2 includes a new LonMaker template with a digital signature that will not expire. This will eliminate the Security Warning message for new LonMaker drawings, but will not eliminate it for existing LonMaker drawings. To eliminate the warning message for existing drawings, do one of the following: 1. Decrease Visio's macro security by opening the Tools menu, pointing to Macros, and then selecting Security. A dialog opens allowing you to select Low, Medium, or High security. Select Low security to eliminate the Security Warning message (this option is equivalent to the setting in Visio 2000). 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. If you select High security, macros will automatically be disabled -- and the LonMaker tool will no longer function -- for unsigned network drawings. 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. 2. 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: msdn.microsoft.com/library/default.asp?url=/library/en-us/odeopg/html/deovrusingdigitalcertificatestoproducetrustedsolutions.asp 3.1.3 Shapes Not Restored During Resynchronization --------------------------------------------------- A shape that referred to another shape that was on a different page was sometimes incorrectly deleted during a resynchronization. This problem primarily occurred with message tag connections. 3.1.4 SCPTnvType Processing ---------------------------- The LonMaker tool sometimes set the wrong scaling factors when changing a network variable type using a SCPTnvType configuration property. The LonMaker tool now sets the scaling factors based on the values in the resource file. 3.2 Problems Fixed in Service Pack 1 (Release 3.11) ---------------------------------------------------- The following problems have been fixed in Release 3.11. 3.2.1 Upgrading Devices Failed With Message Tag Connections ------------------------------------------------------------ Replacing a device with a new device with an upgraded application would fail if the device was a member of any message tag connections. 3.2.2 Controls Not Visible in Japanese Windows ----------------------------------------------- Some controls were shifted past the edge of the visible window in the Japanese version of Windows. This is due to a wide fixed-width font being the default font on Japanese Windows. WORKAROUND: A new LonMakerTweakUI utility is installed by LonMaker 3.1 Service Pack 1. This utility can be used with any supported version of Windows to change the font, font size, and dialog width factor (a multiplier for the standard dialog width) for the LonMaker tool. To use this utility, run the LonMakerTweakUI application in the LonMaker folder (this is c:\LonWorks\LonMaker by default). Select a proportional font, font width, and dialog width factor that results in dialogs with all controls visible. These settings are stored in the registry, so the utility only has to be run once per computer. For the Japanese version of Windows, the following settings will work: Font: Font Width: Dialog Width Factor: 1.15 3.2.3 Error When Deleting a Connection --------------------------------------- Dragging a Connection shape to the drawing, then viewing its properties and deleting the shape from the Properties dialog caused an unexpected error to be reported. 3.2.4 Error While Merging Two LonMaker Networks ------------------------------------------------ Merging two LonMaker networks would sometimes result in "Missing text" error messages. 3.2.5 Moving Functional Blocks With Many Connections ----------------------------------------------------- Moving a functional block with many connections to a new subsystem used to take a very long time. The time required to move a functional block with many connections has been significantly reduced. 4. KNOWN PROBLEMS AND WORKAROUNDS ================================== 4.1 LonMaker Credits -------------------- When you are ordering LonMaker credits, you will generate a PC key that you use on your order form to request an application key. Until you receive your application key, do not delete any devices that are commissioned, decommission any devices, or merge networks. These actions invalidate your PC key and require the generation of a new key. You may add new devices, commission devices, or delete devices that are not currently commissioned. The LNS setup application called by the LonMaker setup application installs the LNS Server License Upgrade Utility. This utility allows you to order LNS device credits for the LNS Server. The LonMaker tool does not use LNS device credits, it only uses LonMaker credits. WORKAROUND: Always follow the procedure described in the LonMaker User's Guide or help file for ordering LonMaker credits. Do not use the LNS Server License Upgrade Utility. 4.2 Adobe PostScript Driver --------------------------- Your computer may crash or hang when adding a large number of shapes to a drawing if you are using the Adobe PostScript printer driver version 4.1, originally installed by Windows 9x, Windows NT, and Windows 2000. This problem is due to a memory leak in the PostScript driver, which causes all other applications and menus to stop operating. A typical symptom may be an error in GDI.exe. WORKAROUND: Upgrade the Adobe PostScript printer drivers to AdobePS 4.4.1 for Windows 95/98, AdobePS 5.1.2 for Windows NT 4.0, PScript 5 for Windows 2000. Updated drivers are available in the PostScript directory on the LonMaker CD. Updated drivers are also available from Adobe at www.adobe.com/support/downloads/pdrvwin.htm. This update is not required if you do not have any printers defined. Following is additional help for installation of the printer driver: Visio uses the PostScript driver installed for your default printer. The driver for your default printer must be the updated version. To set your default printer, open the Windows Start menu, point to Settings, then select Control Panel. The Windows Control Panel opens. Select Printers, right-click the desired printer and select Set As Default. The Adobe installation defaults to the most recently created printer. During the installation, you may select the desired printer from a list. To install the updated driver for additional printers, run the installation once for each printer. When installing the new Postscript driver for a networked printer, Adobe creates a new printer. If the printer was defined previously by the user or by any application other than the Adobe installation program, a duplicate printer name will be created. Once the printer is defined by the Adobe installation and the drivers are installed, trying to define the same printer through the Adobe installation will result in an error of duplicate printer name. The PostScript installation requests that you select your printer model from a list; if you are using a networked printer, select the Generic PostScript Printer in the list and click the Next button to continue the installation. If you are using a local printer, select your printer manufacturer and model. See the ReadMe file included with the PostScript driver update for additional information. A copy of this ReadMe file is available in the PostScript directory on the LonMaker CD. 4.3 Regional Settings --------------------- When using a Windows Regional Setting that does not use a '.' as the decimal symbol, the LonMaker tool may report unexpected errors when creating a new object or network. For example, the following error may be displayed: "Unable to set cell 'Width' value(Guard(TEXTWIDTH(TheText)*1.5)). Unknown error (0x86db0ce6")." This occurs when one of the libraries loaded by Visio sets its locale to the current regional settings. Known cases that cause this error to occur include some Hewlett-Packard printer drivers. WORKAROUND: Follow the steps in the Adobe PostScript Driver section above and make that printer your default printer. If that does not solve the problem, define a generic text printer to a text file and make that your default printer. If that still does not solve the problem, change your regional settings to use a '.' as the decimal symbol. 4.4 Installation ----------------- Installation may fail if there are any 16-bit applications running at the same time. WORKAROUND: Close all applications while installing the LonMaker tool. This is especially important for 16-bit applications. Installation may be very slow initializing if Microsoft Outlook 98 is running and connected to the Exchange Server. WORKAROUND: Close all applications while installing the LonMaker tool. This is especially important for Outlook 98. If you have Visio Standard installed on your computer, the VBA scripting language that is required by the LonMaker tool will not get installed when you install Visio 2002 from the LonMaker CD. WORKAROUND: Uninstall Visio Standard before installing Visio 2002. If you want to continue using Visio Standard, you can reinstall it, but you must select a different directory for Visio Standard than the one you selected for Visio 2002. 4.5 Drivers and Network Interfaces ----------------------------------- For optimum performance when attached to LonWorks networks, you should always use an LNS Fast Network Interface (also known as a VNI). The drivers included with LonMaker 3.1 for Echelon's PCC-10, PCLTA-10, and PCLTA-20 cards all include upgraded firmware for an LNS Fast Network Interface. THESE UPGRADED DRIVERS ARE NOT LOADED BY DEFAULT. In addition, the driver for these cards does not initialize until you open the control panel application for the driver. To select the LNS Fast Network Interface and initialize the driver, follow these steps: 1. Open the Windows Start menu, point to Settings, then choose Control Panel. 2. Open the LonWorks Plug 'n Play control panel application. 3. Under NI Application, select the application name with "VNI" in the name. 4. Click Apply to apply the changes. 5. Click the Diagnostics button to open the Diagnostics dialog. 6. Click the Test button to test the network interface. 7. Click OK to close the Diagnostics dialog. 8. Click OK to close the control panel application. If you open the Network Properties dialog, change the network interface from an LNS Legacy Network Interface (also called NSI) to an LNS Fast Network Interface (also called VNI), or vice versa, and at the same time change from OffNet to OnNet, the LonMaker tool will report an NS #171 error (NSS upgrade required). WORKAROUND: Change the network interface first and then click OK. Re-enter the Network Properties dialog and then change from OffNet to OnNet. 4.6 Windows 98 --------------- If you originally installed the LonMaker tool under Windows 95, then upgrade to Windows 98 and choose to perform the optional FAT32 file system conversion as part of the upgrade, you may lose your LonMaker and LNS license files. If you perform the optional FAT32 file system conversion before you install the LonMaker tool, this is not a problem. Similarly, if you install the LonMaker tool and then perform the Windows 98 upgrade but do not perform the optional FAT32 file system conversion, there is not a problem. WORKAROUND: If you have previously installed the LonMaker tool and need to perform the optional FAT32 file system conversion, first transfer the LonMaker and LNS license files to another computer with the LonMaker and LNS License Transfer Utilities. When the Windows 98 upgrade and FAT32 file system conversion has been completed, transfer the product licenses back again using the same utilities. 4.7 Windows Shutdown --------------------- You may see an application not responding error if you have any pre-launch plug-ins running when you shutdown Windows. The LonMaker Browser and LonPoint plug-in are both pre-launch plug-ins which means that they have a component that is running whenever the LonMaker tool is running, even if you have not started the plug-in. Other plug-ins may identify themselves as pre-launch plug-ins. WORKAROUND: You can ignore the Windows error and allow Windows to terminate the LonMaker software. Any changes that you have made are saved before this error message is displayed, so you will not lose any updates. You can prevent the error from occurring by exiting the LonMaker tool and any other LNS applications before shutting down Windows. 4.8 Performance ---------------- Visio uses your computer's default printer to format the text in the drawing. If your default printer is a network printer that is not accessible, this will cause significant delays when refreshing the display. WORKAROUND: Make sure your default printer is accessible from your computer or defined to be local to your computer (in which case, it is not necessary that it be attached). If your drawing has an expired digital signature, you may encounter a long delay when you open the drawing as Visio attempts to validate your signature. WORKAROUND: You can either delete the digital signature or add a new valid one. Contact LonSupport for details. 4.9 Remote Clients ------------------- Commissioning may fail when multiple lightweight remote clients are commissioning devices at the same time. WORKAROUND: Use remote full clients when you have multiple remote clients. 4.10 Configuration Properties ------------------------------ If you select the Upload Values From Device or Set Device Template Defaults From Device checkboxes from the Resync CPs command on a device that is offline, that device will be left in the online state after the operation is completed. WORKAROUND: Use the Manage dialog to return the device to the offline state. 4.11 Connection Monitoring --------------------------- The following message may be displayed when you enable connection monitoring: "Can't find standard type file". WORKAROUND: Open the Windows Start menu, point to Programs, point to Echelon LNS Utilities, then select the LNS Resource File Catalog Manager utility. The catalog manager starts and prompts you for a directory. Enter the pathname for your LonWorks Types folder (c:\lonworks\types by default), click the Refresh Now button, then exit from the catalog manager. Connection monitoring may fail if either side of the connection terminates at a functional block that does not use Network Variable shapes. WORKAROUND: Add Network Variable shapes to the functional block by dropping a Network Variable shape on the functional block, or convert the connection to use references. 4.12 Connections ----------------- You cannot change the properties (such as service type) of a connection if two or more connections share an output network variable as targets of the connection and the connections do not use the same connection description. WORKAROUND: Follow these steps: 1. Select the common connection description under New Connections. 2. For each connection, right-click the hub network variable, then select Assign from the shortcut menu. 3. Right-click any of the connections and select Properties from the shortcut menu. 4. Change the service type to the desired service type then click OK. The LonMaker tool updates all connections that use the connection description to use the new service type. If you attempt to apply a connection description that causes a connection error, such as applying a connection description with the priority attribute set to a connection that does not support it, an error message will be displayed such as: "The priority attribute was not specified as configurable. (Subsystem: NS Connections, #11)." Subsequent attempts to add any connection with the default connection description will result in the same error message. WORKAROUND: Exit and re-enter the LonMaker tool. Then add the connection. Alternatively, explicitly select a valid connection description other than the default. It may take a very long time to add a connection to a reference if the reference already includes many connections. WORKAROUND: Create a new reference for additional connections. Each reference should contain no more than 200 connections, where each connection is displayed as one line in the Connection list in the Connection Properties dialog. 4.13 Device Upgrade ------------------- When upgrading a device that previously did not have any network variables or functional blocks to a device template that does have network variables or functional blocks, the LonMaker tool does not correctly reflect the upgraded device’s template. WORKAROUND: Delete the device and add it again. You may see data server errors if you are a monitoring a device using the LonMaker Browser, and at the same time upgrade the same device with a new application that has different network variables. WORKAROUND: Always close any monitoring applications such as the LonMaker Browser when upgrading devices being monitored with the browser or other monitoring application. If this error occurs, exit and restart all LNS applications, including the LonMaker tool. You will see an error if you replace a commissioned device, and specify that the new device uses a device template that is created by uploading the interface definition from the new device. WORKAROUND: Open the LonMaker menu and then click Network Properties. On the LonMaker Options tab select Device in Options Category. Clear Remove Unreferenced Device Templates. Create a new device and device template, uploading the device template from the device, and then delete the device. Replace the original device using the newly created device template. 4.14 LNS Server ---------------- When you start the LNS Server application, the LNS Server by default starts listening at IP port 2540 if IP networking is available on that computer. Any IP-enabled LNS client can then access your LNS Server if they are aware of your LNS Server IP address and IP port. WORKAROUND: To restrict access by remote LNS applications to specific IP addresses or IP address ranges, set up IP access permissions as described in the Network Properties: Remote IP Access Permission topic in the LonMaker help file. If you run multiple LNS Servers on the same computer, they cannot use the same LNS network interface, open the same networks, or use the same ports. WORKAROUND: Use a single LNS Server to open multiple networks on a single LNS network interface and to listen on the same IP port. To use multiple LNS Servers, select a different network or networks in each server. You can run more than one LNS Server on a computer as long as each is serving a different network and is connected to its network on a dedicated LNS network interface or shared LNS fast network interface. In addition, if the LNS Server is to serve remote lightweight clients in addition to remote full clients, each server must be assigned to a different IP port. In order to assign a different IP port for the LNS Server, follow these steps: 1. Open the Windows Start menu and select Run. 2. Browse to the LonWorks bin directory (c:\LonWorks\bin by default) and select the lcaserv application (this is the LNS Server). 3. Specify the "/PORT=" flag, substituting your port number. 4. Click OK to start the LNS Server. A lightweight remote client running on a LNS/IP channel is disconnected from the LNS Server if the IP connection is broken. Unlike a full remote client running on a LonWorks or LonWorks/IP channel, a remote lightweight client running on an LNS/IP channel cannot monitor and control the LonWorks network if the connection to the LNS Server is lost, because both the connection to the LNS Server and the data monitoring and control are through the LNS/IP connection. On some computer, if an established IP connection is idle for some time, the computer enters a power save mode that causes IP disconnection. The LNS Server treats this as it would any other disconnection, and the LNS/IP-remote application will need to re-establish the connection with the LNS Server by exiting and restarting the application. WORKAROUND: To avoid going into power save mode unintentionally on an LNS/IP-remote computer, disable the power saver mode on the computer. If you launch the LNS Server from the Design Manager multiple times, you get a separate instance each time. WORKAROUND: If you want a single LNS Server, for example to share an LNS fast network interface between multiple networks, open the first LNS Server from the LonMaker Design Manager, then open the additional networks from within the LNS Server. 4.15 LNS Text Box Control -------------------------- On Windows 2000, if your drawing contains an LNS Text Box Control or other ActiveX control, the following message may be displayed when you save your drawing or exit Visio: "Visio internal error #3400, Action 1004: Save." WORKAROUND: To save your drawing, open the File menu, point to LonMaker Documents, then select Save All LonMaker Documents. Or, to save your drawing and exit, select Save and Close All LonMaker Documents. When deleting a subsystem that contains an LNS Text Box Control or other ActiveX control, you may receive an "Unable to create cell" or other "Unknown error" error from Visio and your drawing will be closed. WORKAROUND: First delete any controls, then save your drawing. Then you can delete the subsystem. The LNS Text Box Control can be inserted using Visio's Insert Object menu, but does not work correctly when inserted from this menu. WORKAROUND: To add an LNS Text Box Control to your drawing, drag the LNS Text Box Control shape from the LonMaker Basic Shapes stencil to your LonMaker drawing. 4.16 LonMaker Browser ---------------------- If the LonMaker Browser is monitoring a device at the same time you add or remove a network variable on the device, and then you rebuild and reload the device, the browser may start reporting a Data Server #200 error on one or more of the network variables on the device. WORKAROUND: Exit and restart all LNS applications including the LonMaker tool, LonMaker Browser, and the NodeBuilder Development Tool. The LonMaker Browser does not save changes made to some browser options when you exit if you are running as a remote lightweight client. The following settings are affected: Retries, ServiceType, Priority, Report By Exception, and Poll Interval. WORKAROUND: Either change the settings from the browser running on the same computer as the LNS Server, or change the settings each time you run the browser. The LonMaker Browser reports an Object Not Found error messages when a browser file is opened and any of the subsystem or device names saved in the file have changed. WORKAROUND: Create new browser files after changing subsystem or device names. 4.17 LonMaker Design Manager ----------------------------- If you specify a network name with trailing spaces the LonMaker tool will report an LNS #6 error (object not found), and report an unexpected error. WORKAROUND: Do not specify trailing spaces in your network name. The LonMaker Design Manager cannot create or open a network if Visio is installed on a path with a space in the folder name (such as c:\program files) and you have another folder at the same level with the same name up to the first space (such as c:\program). WORKAROUND: Perform the following steps: 1. Rename or remove the folder with the matching name (e.g. c:\program). 2. Open a DOS window, go to the Visio folder (e.g. c:\program files\Visio), and enter the following commands: visio32 /u visio32 /r 3. Exit from Visio. 4. You may now create or open a network from the LonMaker Design Manager. You may get a "Error in loading DLL" message the first time you attempt this. If you do, exit Visio and create or open your network again. 4.18 LonMaker License Transfer Utility --------------------------------------- The LonMaker License Transfer Utility does not transfer the LNS Server license. WORKAROUND: If you are transferring the LonMaker software to another computer, and you need the LNS Server on the new computer, run the LNS Server License Transfer Utility after running the LonMaker License Transfer Utility. The LNS Server License Transfer Utility is located in the Echelon LNS Utilities program folder on the Windows Start menu. The procedures for using this utility are similar to the LonMaker License Transfer Utility. 4.19 LonMaker Shapes --------------------- The shape's text displaying the name of a Functional Block, Network Variable, or Message Tag may wrap-around if you copy a LonMaker drawing from another computer. WORKAROUND: Open the File menu and select Page Setup. The Page Setup dialog opens. Click Setup. The Print Setup dialog opens. Click Printer. The Print Selection dialog opens. Reselect your current printer or select a new printer. Click OK for the three open dialogs. 4.20 LonMaker Startup ---------------------- The LonMaker tool will sometimes fail to start when it is opened by a different user than the user who originally installed the software. This occurs because Visio does not always correctly copy all user-specific options to a new user's registry settings. WORKAROUND: Open the Tools menu and then click Options. Select the File Paths tab. If you do not see a "\LonMaker" entry in Add-ons, add one. is your LonWorks directory (this is c:\LonWorks by default). If there are other entries, separate the new entry from them with a semicolon (';'). If you do see a "\LonMaker" entry in Add-ons, add and then remove a space in Add-ons to force Visio to rebuild its cache. After either change, exit and restart both the LonMaker tool and Visio. 4.21 Merging Networks --------------------- You may lose connection attributes if you merge a LonMaker network into another LonMaker network if the first LonMaker network was itself the result of a merge. WORKAROUND: Always merge LonMaker networks into a single master LonMaker network. 4.22 Resource Files ------------------- If the LonMaker tool, the LonMaker Browser, or any other LNS application is monitoring a device, and you then add new user resources to the resource catalog, and you then load a new application to the device that references the new resources, you may see Data Server errors due to the new resources not being available in the data server cache. WORKAROUND: Exit and restart all LNS applications including the LonMaker tool, LonMaker Browser, and the NodeBuilder Development Tool. 4.23 Visio Limitations ----------------------- You cannot save a LonMaker drawing as an AutoCAD drawing if the Visio Add-On path is not set correctly. WORKAROUND: Open the Tools menu, select Options, point to File Paths, select Add Ons, and enter the Solutions folder (C:\Program Files\Visio\Solutions by default). 4.24 Compatibility with Other Applications ------------------------------------------- 4.24.1 LonMaker 3 ------------------ A LonMaker 3 network can be opened with LonMaker 3.1. A LonMaker 3.1 network can be opened with LonMaker 3 as long as you do not use any of the new LonMaker 3.1 features, including adding dynamic network variables to functional blocks other than the Node Object functional block. A LonMaker 3.1 remote client can use an LNS Server from a LonMaker 3 installation. You can mix LonMaker 3 and LonMaker 3.1 clients on the same network as long as you do not use any of the new LonMaker 3.1 features including dynamic network variables on functional blocks other than the Node Object functional block. You should ensure that your LNS Server and all LNS clients, including all LonMaker clients, always have the most current LNS service packs applied. LonMaker 3.1 includes LNS 3 with Service Pack 4. Check www.echelon.com/lns for the availability of newer service packs. 4.24.2 LonMaker 1 or LonMaker 2 -------------------------------- A LonMaker network created with or modified by LonMaker 3.1 cannot be opened locally or remotely on a computer running LonMaker 1 or LonMaker 2. WORKAROUND: Upgrade your computer to LonMaker 3.1. A LonMaker network design running the LNS Server included with LonMaker 1 or LonMaker 2 or any other tool based on LNS 1 or LNS 2 cannot be accessed by a remote client computer running LonMaker 3.1. WORKAROUND: Upgrade the LNS Server to an LNS 3 Server by licensing another copy of LonMaker 3.1. If you open a very large LonMaker 1 drawing, Visio may hang and the LonMaker Network Wizard is never shown. WORKAROUND: Contact Echelon LonSupport. They can help you convert your drawing to LonMaker 3.1. 4.24.3 Other LNS Applications ------------------------------ The LonMaker Browser will display the format as "Raw" in the Change Format dialog and the Details dialog if another LNS application changes the format for a network variable and does not explicitly set the program ID and scope for the format. However, the data will be formatted correctly unless you open the Details dialog, at which point the data will be formatted as Raw data (hex value). WORKAROUND: Change the LNS application to explicitly specify the program ID and scope as part of the format, or use the LonMaker Browser to assign the format. LNS applications and plug-ins may report a Host Resource Allocation error and fail to start when too many LNS applications, including plug-ins, are open. WORKAROUND: Close one or more of the open LNS applications or plug-ins to free Windows resources. When starting an LNS plug-in on a virtual functional block, LonMaker 3.1 identifies the object to the plug-in as a LonMarkObject. In LonMaker 2, LonMaker identified it as an AppDevice. This may change the behavior of the plug-in if it expected the LonMaker 2 interface. WORKAROUND: Start the plug- in from the Device shape instead of the Functional Block shape. When performing operations from the LonMaker tool running as a remote full client that affect both the client's network interface as well as other devices or routers, the LNS Server may generate events that are not received by remote clients. For example, the commission status of Network Service Device shapes in a LonMaker drawing may not be updated to reflect their current state when you add a new Network Service Device shape. WORKAROUND: To work around the problem for Network Service Device shapes within LonMaker drawings, open the Properties dialog for each Network Service Device shape, then click OK. The device style updates if required. Other workarounds are dependent on the LNS clients. 4.24.4 NodeBuilder 1.5 ----------------------- If you have both the NodeBuilder 1.5 Development Tool and the LonMaker tool installed, and then you uninstall the LonMaker tool, the NodeBuilder 1.5 will no longer work (reporting a floating point error). WORKAROUND: Re-install the NodeBuilder 1.5 tool after uninstalling the LonMaker tool. 4.24.5 Disk Defragmenters -------------------------- Certain third-party disk defragmenters such as Norton SpeedDisk can CAUSE YOUR LONMAKER LICENSE FILE AND ALL LICENSE CREDITS TO BE DELETED. Once this happens, the LonMaker tool cannot be used until new LonMaker credits are obtained from Echelon (you can get replacement credits at no charge as described in the LonMaker User's Guide if this happens). This occurs because the defragmenter relocates files, even if they are marked as system files. Disk defragmenters built into Windows XP, Windows 2000, Windows Me, and Windows 98 do not break the license. WORKAROUND: Prior to defragmenting your disk using the Norton Speed Disk utility or other third-party disk defragmenters, configure it not to move files with the following extensions: *.ENT, *.KEY, and *.RST. How this is done is dependent upon the disk defragmenter that you are using. If the disk defragmentation is not configurable, either use the disk defragmentation built into Windows, or use third-party disk defragmentation software that is configurable. If you lose credits because of a third party defragmenter, order free replacement credits as described in the LonMaker User's Guide. Be sure to send in the entire order form whenever you order LonMaker Credits. 4.24.6 Mijenix ZipMagic ------------------------ The LonMaker tool cannot restore a network from a backup file if ZipMagic (or a similar product) is installed and enabled on the computer. If you use ZipMagic, the contents of a Zip file may automatically be expanded to appear to be a Windows folder and the LonMaker tool is not able to access the Zip file. WORKAROUND: Disable ZipMagic before using the LonMaker restore feature, or add the LonMaker tool to the ZipMagic application exclusion list. For example, if you are using ZipMagic 98, to add the LonMaker tool to the ZipMagic application exclusion list, open the ZipMagic properties, click the Applications icon, select the "These applications see Zip files as files (not as folders)" checkbox, click the Add button, click the Browse button, browse to the LonWorks LonMaker folder, click lonmaker.exe, click Open, click Add, click Done, then click OK. This will disable ZipMagic's automatic expansion feature for the LonMaker tool, while allowing it to continue to work in other applications. 5. DOCUMENTATION CHANGES ========================= 5.1 Windows XP Support ----------------------- The LonMaker User's Guide and CD cover do not list Windows XP as a supported operating system. It is now a supported operating system, and is also one of the two recommended operating systems (the other is Windows 2000). 5.2 LonMaker Help File ----------------------- The LonMaker help file installed by the LonMaker setup program may generate a "Cannot find or load the file Inetwh32.dll" error, followed by a "An error exists in the Help file" message, when you open it and is missing a few updates to the introduction and a few topics in the Contents pane. WORKAROUND: Copy the lonmaker.hlp and lonmaker.cnt files from the LonMaker CD to your LonMaker program folder (c:\LonWorks\LonMaker by default). Set the option to display hidden files in Windows Explorer and delete the lonmaker.gid and lonmaker.ftg files in your LonMaker program folder. 5.3 Data Formatting -------------------- The following change is not documented in the on-line help: LonMaker 3.1 uses an improved method of performing localized formatting of data over LonMaker 1 and 2. This improved method is provided by LNS 3, and is shared by all LNS 3 tools. Previously, the LonMaker tool included two sets of format files that provided instructions on how to format each standard network variable type (SNVT) and standard network configuration property type (SCPT). Both sets of files included two sets of formatting instructions, one for US units such as Fahrenheit, the other for SI units such as Celsius. The difference between the two files was that one set identified the US units as default; the other set identified SI units as default. The user selected between these two format files at the time of installation of the LonMaker software. The improvement in LNS 3 is to use a single set of format files, and to now choose the default based on the Windows regional settings of the computer where the data is formatted (the data is formatted on the LonMaker computer for local and remote full clients; the data is formatted on the LNS Server computer for remote lightweight clients). To determine the measurement system used on your computer, open the Windows Control Panel and double-click Regional Settings. Select the Number tab in the Regional Settings Properties dialog. LNS 3 uses the value of the Measurement System item, which will be either "U.S." or "Metric". 5.4 Resource File Documentation -------------------------------- Updated documentation is available for the SNVT and SCPT definitions included with the LonMaker 3.1 tool. To get the updated documentation, download the latest resource file update from http://www.lonmark.org/products/snvtfile.htm and install it as described in the ReadMe.htm file for the update.