(1) LNS 3 Service Pack 5 Now Available! Download Service Pack 5 to get the latest reliability, compatibility, and performance updates for LNS 3. Download today from Echelons web site at http://www.echelon.com/toolbox/updates.asp. Echelon highly recommends the use of this Service Pack. The entire ReadMe for the Service Pack is included here: ================================================================== LNS(tm) for Windows(r) 3.0 Service Pack 5 (SP5) Read Me File Updated December 21, 2001 Copyright (c) 2001 Echelon Corporation. All Rights Reserved. ================================================================== CONTENTS ======== 1. Overview 2. Installation Instructions 3. LNS 3.0, LNS 3.01, LNS 3.02, LNS 3.03 And LNS 3.04 Issues Fixed in LNS 3.05 3.1 Empty CP value file causes XIF import to fail 3.2 Various LNS component crashes 3.3 Duplicate dynamic network variables 3.4 Problem setting large Extension values with Lightweight client 3.5 Problem adding a polled output network variable to a monitor set 3.6 LNS DDE Server crash when running formatting tool 3.7 Domain broadcast application messages always sent acknowledged 3.8 Various File Transfer Protocol (FTP) issues 3.9 NS #5 or NS #38 when performing a device upgrade 3.10 Incorrect property returned on remote client 3.11 Unable to access resource files 3.12 LonMark standard resource files upgraded to version 11 4. LNS 3.0, LNS 3.01, LNS 3.02 And LNS 3.03 Issues Fixed in LNS 3.04 4.1 Problem managing devices without SNVT self-identification information 4.2 Problem managing devices with Binding Constraints mismatch 4.3 NV-based CP changed position in LonMarkObject.ConfigProperties collection 4.4 Problem with NetworkVariables.GetItemByIndex() on remote clients 4.5 Fatal error from VC++ Runtime Library after some program upgrades 5. LNS 3.0, LNS 3.01 And LNS 3.02 Issues Fixed in LNS 3.03 5.1 AppDevice.Upgrade() method problems 5.2 Credit incorrectly charged on device application upgrade 5.3 LNS applications on LonWorks/IP channels cant use MD5 authentication 5.4 CP forward-reference causes import or upload error 5.5 NSD upgrade causes host dynamic NVs to disappear 5.6 Memory leak in LcaLdrfLanguages.GetItem() 5.7 Cant monitor up to published point limit 5.8 Single point monitoring startup does not report error on comm error 5.9 Heap error when monitoring on dual processor PC 5.10 Re-enabling monitor point does not re-enable error reporting 5.11 Load() after NeuronID property change used original Neuron ID 5.12 Current value not always reported after re-enabling monitor point 6. LNS 3.0 And LNS 3.01 Issues Fixed in LNS 3.02 (and included in LNS 3.03) 6.1 Cant import an XIF with LonMark device-level CPs 6.2 Node self-documentation string limit smaller than LonMark limit 6.3 Device Interface Upgrade() causes unbound NetworkVariable direction change 6.4 Various dynamic network variables issues 6.5 Interface object AddNVFromString() returns an invalid object on a Lightweight client 6.6 NS#67 after obtaining 65,536 references to the System object 7. LNS 3.0 Issues Fixed in LNS 3.01 (and included in LNS 3.03) 7.1 Issues with Windows Millennium (Windows Me) 7.2 ALL Subsystem path incorrect 7.3 NS# 8 error on System.Open() 7.4 LNS 2 compatibility issue with lcaAliasForUnicast connection option 7.5 Application exits after opening third network database 7.6 Events stop working 7.7 Database conversion problem with target alias connection members 7.8 Router.GetBufferConf() returned error 7.9 Setting MsgMonitorPoint.DefaultOptions 7.10 MonitorSet object default property 7.11 LNS IP Configuration Utility name change 7.12 Exit hang when using LonWorks/IP channels 7.13 De-serialization error