LonScanner™ FX Protocol Analyzer ReadMe
Release 4.0, April 2010
Copyright
© 2004 – 2010 Echelon Corporation
All Rights Reserved
This file contains important information not included in the LonScanner User's Guide and help files. Additional information and updates, including critical updates, may be available from Echelon’s Downloads Web page at www.echelon.com/downloads. See Echelon’s Knowledge Base at www.echelon.com/support for answers to frequently asked questions.
To be eligible for replacement activations, register your LonScanner software at www.echelon.com/register.
5 Repairing Software Installations
6 Changes in LonScanner FX (4.00)
6.1 NodeBuilder FX and Mini FX Compatibility
6.2 Windows 7 and Vista Compatibility
Hardware and software requirements for computers running the LonScanner FX Protocol Analyzer are listed below:
· 32-bit versions of Microsoft® Windows® 7, Windows Vista®, Windows XP, or Windows Server 2008. Echelon recommends that you install the latest service pack available from Microsoft for your version of Windows.
· Intel® Pentium® III 800MHz processor or faster, that meets 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.
· 128 MB RAM minimum.
Note: For Windows 7 and Windows Vista, Echelon’s testing for the LonScanner FX Protocol Analyzer 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.
· LonWorks® network interface as described in the LonScanner FX User’s Guide.
This document applies to the LonScanner FX Protocol Analyzer. You can verify that you have this release by starting the LonScanner software, opening the Help menu, and then clicking About LonScanner. The About LonScanner dialog appears. This dialog displays the version number of your LonScanner software. For LonScanner FX, the version number is 4.00.xx, where xx is the build number of the software.
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.
4. Click Click Here for Support Information.
5. Click the Repair button.
6. Repeat 3 – 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 LonScanner FX Protocol Analyzer
2. Echelon OpenLDV 3.4
3. LonMark Resource Files 13.00
The following changes are included in LonScanner FX. The version number for this release is 4.00.bb, where “bb” is the final build number. Numbers in parentheses at the end of the problem descriptions are Echelon's internal problem tracking IDs.
LonScanner 3 installation breaks the NodeBuilder FX and Mini FX tools, and would require installation repair. (52244)
Clicking on menu items in Windows 7 and Windows Vista caused LonScanner to lock up. (52083)
Setting LonScanner timestamp default to “relative to anchor” caused an invalid starting timestamp after the LonScanner tool was stopped and restarted. (37017)
Timestamps could be wrong when used with an i.LON SmartServer or i.LON 100, and relative clock adjustments occurred. (49105)
The response to a Query Status message was sometimes not decoded correctly. (41622, 45492)
The Update Domain message was decoded incorrectly. (42703)
NV alias updates were decoded incorrectly. (44172)
Wink messages were sometimes decoded incorrectly. (47323)
Several LonScanner crashes were fixed. (42980, 43500, 49910, 52517, 43118)
The LonScanner FX tool has the following known problems. Numbers in parentheses at the end of the descriptions are Echelon's internal problem tracking IDs.
The LonScanner tool may quit functioning if you install the LonMaker 3.1 Integration Tool, LNS® 3 Application Developer’s Kit, or any other products that install the LNS 3 runtime after installing the LonScanner FX software. Workaround: This problem does not occur with LNS Turbo (Release 3.2) or later. If you install an LNS 3 product after installing the LonScanner FX software, follow the instructions displayed the next time you run the LonScanner FX tool. The instructions will tell you to open the Windows Control Panel and use Add/Remove Programs to repair the OpenLDV installation. (36597)
If you attempt to save a names file that already exists and is read-only, any changes to the names file are not saved, and there is no warning message. Workaround: Use Windows Explorer to clear the Read-only attribute for the file. Local names files have an .lsn extension. (36805)
The LonScanner software may not display U10 and U20 USB network interface attachment or detachment events in the LonScanner status bar when an LNS Turbo runtime is installed. Workaround: If you have an LNS Turbo runtime and use a U10 or U20 network interface, open LonWorks Interfaces in the Windows Control Panel and click the USB tab to see USB interface status. (36422)
The LonScanner software may not detect the transceiver type of a PCC-10, PCLTA-20, or PCLTA-21 network interface when an LNS Turbo runtime is installed. Workaround: If you have an LNS Turbo runtime and use a PCC-10, PCLTA-20, or PCLTA-21 network interface, open the Statistics menu, click Channel Parameters, and then select your channel type. (36506)
If you are using the LonMaker 3.1 Integration Tool or other tool based on an LNS 3 runtime, and you have UNVTs defined in scope 4, 5, or 6 resource files, the scope of the resource file is not automatically set in the LNS database. Workaround: This problem does not occur with LNS Turbo (Release 3.2) or later. Before importing LNS names with LNS 3, set the scope for any scope 4, 5, or 6 functional blocks using a device plug-in, a custom device shape, or manually using the LNS Object Browser or other tool. If you are using the LonMaker 3.1 Integration Tool, see Setting User Functional Block Scopes and Types in the LonMaker User’s Guide. If you are using another tool, see the documentation for that tool. The LNS Turbo runtime automatically sets the scope for user types.
If you install the LonScanner software on an LNS 3 runtime and then uninstall the OpenLDV software, the LNS runtime will quit functioning. Workaround: This problem does not occur with LNS Turbo (Release 3.2) or later. If your LNS 3 runtime stops functional after uninstalling OpenLDV, re-install the LonScanner FX software, OpenLDV, the LNS runtime, or a tool using an LNS runtime such as the LonMaker 3.1 Integration Tool.
During installation, the LonScanner setup program may not update the progress bar for a period of about 15 seconds. Workaround: Do not cancel or kill the setup program if it appears to stop functioning for periods of up to one minute.
If you are using a circular log file and you attempt to access a log entry that is no longer available, you will see a warning dialog. Workaround: This behavior is normal because the log entry is no longer in the log file. If this dialog pops up often, increase the log file size so that data entries are not overwritten as often.
The log sequence number always starts from 0, so when entries are being deleted from a full circular log, all log numbers are shifted such that the top entry always starts from 0. Workaround: This behavior is normal, but you can prevent it by displaying the arrival sequence number format in the packet log instead of the log sequence number. The arrival sequence number for a packet never changes, whereas the log sequence number may change with circular log files.
When LonMaker Turbo SR2 (3.22) is installed over LonScanner FX, launching LonScanner will display a “CrypKey -102 error” message. Workaround: Install LNS Turbo Service Pack 6 (or higher) to update the LonMaker product. (55169)