Building Automation Knowledge Base

Issue What is the part number for a Vista 5 Engineering Dongle? Product Line TAC Vista Environment Vista 5 Cause There are several part numbers on iPortal for Vista 5 licenses, end-user dongles, engineering dongles, etc.  It may not be very clear which is the right part to order to obtain an in-house engineering license/dongle.   Resolution On Schneider Electric iPortal website (https://iportal2.schneider-electric.com/😞 Part Number: 000885000 Part Name: 1YEAR VISTA INHOUSE Part Short Description: Vista In-house Subscription for internal personnel only. Includes in-house dongle, which allows Vista 5.X software to run without any license file. Part Long Description: Vista 5 Vista In-house: 1 year in-house subscription* for Schneider Electric's and partners' internal personnel only. Includes the in-house dongle, which allows Vista 5.X software to run without any license file *Currently the subscription is unlimited, though the description indicates it is only valid for 1 year.

Issue Xenta 913 is communicating to BACnet MSTP device fine (shows online status), but no data will show up on values page.  All of the data will be zeros.  XBuilder does not give you an error or warning of this problem. Environment Xenta 913, Xenta 731, Xenta 511:B XBuilder Cause When using BACnet or Modbus in the 913/731/511:B you can not name the Modbus or BACnet port the same name as any of the devices below it. For example, if you name your BACnet MSTP port "RTU" and then name the slave device "RTU" the device will show an online status, but you will not see any information on a values page. All of the data will be zeros.  By default, XBuilder attempts to prohibit this from happening by adding a numeric to the end of a new device.  So by default the device name would be "RTU 1" and you would have had to rename it to "RTU." Resolution Name the slave device below the BACnet or Modbus port something different than the port itself. 

Issue The current manager ID does not correspond to a known manager. This is an internal error and should be reported to customer support. Environment LNS LonMaker Vista NL220 Cause Power failure on the computer while adding controllers to an existing drawing.  Could not open the drawing after this. Resolution Restore the most recent backup where this controller did not exist. Open the drawing with network unattached Then go network attached Then go onnet. Launch System Plug-in to delete and create new group bindings. Save the file. Open drawing again Register the System Plug-in

Issue  An attempt was made to add an object that already exists. Environment LNS LonMaker Vista NL220 Cause An attempt was made to add an object that already exists. Resolution Something has become corrupted in the database.  Resynchronize the drawing to ensure that an item is not just missing from the page and needs to be deleted.  If this doesn’t work, restore the most recent backup where the error was not occurring.

Issue The requested service cannot be provided in the current management mode.  Environment NL220 ZBuilder Xenta 121 Cause Attempts to download a ZBuilder configuration to a Xenta 121 on a network that is not "attached."  This is the incorrect management mode to perform a download. Resolution Make sure the network status is onnet and attached.

Issue A record from a binary external interface file or binary application image file was received out of sequence.  Environment LNS LonMaker Vista NL220 Cause A record from a binary external interface file or binary application image file was received out of sequence.  Resolution If you encounter the error, the XFB or APB file may be corrupted

Issue A checksum error occurred while transferring the binary external interface or binary application image file to the LNS.  Environment LNS LonMaker Vista NL220 Cause A checksum error occurred while transferring the binary external interface or binary application image file to the LNS.  Resolution If you encounter the error, the XFB or APB file may be corrupted.

Issue Invalid session handle or a session error.  Make sure that sessions are begun and ended in pairs, and are always part of an explicit transaction. Environment LNS LonMaker Vista NL220 Cause If two LNS clients attempt to perform a device application download at the same time, one of the clients will receive the NS #36 SRSTS_SESSION_ERROR (Invalid session handle or a session error) exception. Resolution Retry the device application download at a later time.

Issue An operation requiring a Neuron ID was attempted on a device with no Neuron ID.  Subsystem; NS #37 Environment LNS LonMaker Vista NL220 Cause For example, if you invoke the Wink method on a device whose Neuron ID has not been set in the LNS database, this exception will be thrown.  In some other cases, this exception may be thrown if a device’s Neuron Id has been set in the LNS database, but the device has not been commissioned.  For example, if you read the SelfDocumentation property of a device before that device has been commissioned, this exception will be thrown, regardless of whether or not the device’s Neuron ID is set. Resolution Make sure the Neuron ID has been set and the device is commissioned.

Issue Requested operation can't proceed because a database import or export is currently in progress. Environment LNS LonMaker Vista NL220 Cause Requested operation can't proceed because a database import or export is currently in progress. Resolution Wait for the import or export to complete.

Issue These errors are internal to Echelon LonMaker and require the assistance of Echelon Technical Support. Environment LNS LonMaker Vista NL220 LonSupport@Echelon.com 1-800-258-4LON or 1-800-258-4566 Cause NS #9 lcaErrNsBadClient NS #11 lcaErrNsNoClient NS #14 lcaErrNsClientBlocked NS #16 lcaErrNsNotImplemented NS #18 lcaErrNsServiceFailure NS #20 lcaErrNsPrematureRelease NS #21 lcaErrNsRootBus NS #22 lcaErrNsRootDoesNotExist NS #23 lcaErrNsNoFreeRootTransactions NS #30 lcaErrNsEventFailure NS #32 lcaErrNsSubscriptionDblimit NS #34 lcaErrNsSegmentation NS #41 lcaErrNsDbError NS #42 lcaErrNsOutOfJournal NS #46 lcaErrNsNetworkHasInstalledNodes NS #49 lcaErrNsIntegrityError NS #55 lcaErrNsProgramDblimit NS #57 lcaErrNsNvmtDbLimit NS #61 lcaErrNsMsgError NS #62 lcaErrNsCancelError NS #71 lcaErrNsTimerRange NS #83 lcaErrNsObjectLocked NS #84 lcaErrNsInvalidContext NS #85 lcaErrNsServerNotFound NS #109 lcaErrNsStaleFileHandle NS #115 lcaErrNsManagerNotAllowed NS #126 lcaErrNsUnimplementedCategory NS #127 lcaErrNsUnimplementedProperty NS #128 lcaErrNsDisallowedInMipMode NS #129 lcaErrNsDisallowedInTxHandler NS #130 lcaErrNsNssNotInitialized NS #146 lcaErrNsInvalidErrorContext NS #151 lcaErrNsBatchOptionNotImplemented NS #152 lcaErrNsBatchNoResult NS #172 lcaErrNsEngineNotInitialized NS #189 lcaErrNs16BitUserErrorCode NS #190 lcaErrNs16BitWarningCode NS #191 lcaErrNs16BitErrorCode NS #289 lcaErrNsEngineIsSuspended NS #290 lcaErrNsNotSupportedFromRemoteClient NS #4031 lcaErrNsUpdateFuncError NI #24 lcaErrNiObsolete NI #27 lcaErrNiUnimplemented LNS #5 lcaErrUninitializedDb LNS #35 lcaErrGeneric LNS #36 lcaErrDbServer LNS #39 lcaErrWrongWriteDataSize LNS #40 lcaErrInvalidFormat LNS #54 lcaErrCantCopyLNSDirectory LNS #70 lcaErrCantRecoverReadOnlyFile LNS #71 lcaErrStringIsEmpty LNS #73 lcaErrInvalidProgramType LNS #97 lcaErrInvalidRmcObject LNS #98 lcaErrInvalidRmcServer LNS #99 lcaErrInvalidRmcClient LNS #101 lcaErrInvalidRmcMethod LNS #123 lcaErrInvalidPropChangeEvent LNS #133 lcaErrInternalErrBadExceptionCode LNS #134 lcaErrInternalErrBadHresultExceptionCode LNS #135 lcaErrInternalErrBadVNIDataServer LNS #136 lcaErrInternalErrBadNsdHandle LNS #137 lcaErrInternalErrStartTransaction DS #365 lcaErrLnsDsUnexpected DS #366 lcaErrLnsDsFailed Resolution These are internal errors and should be reported to Echelon's customer support. Contact Echelon at 1-800-258-4LON (258-4566) or LonSupport@Echelon.com.

Issue How can I tell what device the alarm is coming from in the b0warlog.log file? The  b0warlog.log or "Warning Log" file does not reference individual devices therefore is difficult to see where the alarm happened. Environment Vista Alarms Cause A lot of  warnings are due to a mismatch in the Vista database and a device on the field. For instance, if you have a Xenta Server alarm that doesn't exist in the Vista database. Resolution You could see if the Xenta/Xenta Server is marked in Vista, look for the asterisk (*), to give you a clue where it came from.   An alternative way to do it is to use testclt program: Start testclt.exe from the root directory of you Vista installation. Login Go to File-Dbg Write alrproc Click Add Choose the Time radio button Click Poke Click Close Wait for the warning to happen in the b0warlog.log Open b0dbglog.logfile in notepad and search for "your error" Just above the line found you should see which alarm object that sent the alarm Example: (Searching for Error:81) Tue Nov 23 13:26:02 2010 :alrproc  >> ProcessAlarmEvent EventId:TGML_test-731-Lon-XG-Xenta401-$NETMON.offline EventType:1 Pri:9 Txt:Xenta group offline Tue Nov 23 13:26:02 2010 :alrproc  >> ValidateDataSpec Id:TGML_test-731-Lon-XG-Xenta401-$NETMON ObjType:EE_MESS Tue Nov 23 13:26:02 2010 :alrproc  >> Processed Error:81  

Issue Error: NS#64 lcaErrNsNotInstalled Environment LNS LonMaker Vista NL220 Cause An operation on a node was requested that requires the node to be configured, but the node is not configured. When you encounter this error, make sure that the device in question has been configured. Resolution Some operation on a device was requested and that operation requires the node to have been installed, but the device has not been added yet. Add the device.

Issue The network subnet limit (currently 255) has been reached. Environment LNS LonMaker Vista NL220 Cause The network subnet limit (currently 255) has been reached. Resolution Run the LNS Database Recovery Wizard: If you are recovering through a PCC-10, PCLTA-10 or PCLTA-20, use the LonWorks Plug 'n Play Control Panel to select the NSI NI Application. Otherwise, error "NS #138 (Local interface is in the wrong state (unconfigured)" is reported, then "NS #67 system is not open)", then "LNS #55". Finally, the LNS Database Recovery Wizard only gives you the option to cancel the recovery.  

Issue An attempt was made to add, commission, move, or replace a device that is on the wrong channel.  A device is considered to be on the wrong channel when a configured, learning, or non-permanent bridge class router exists between the device and the channel on which it is to be place.  When you encounter this error, place the device or router on the correct channel, or define the device or router without a channel and have LNS determine the channel automatically. Environment LNS LonMaker Vista NL220 Cause This usually occurs when the device is defined on the wrong channel.  Resolution Moving the device in the LonMaker drawing to the correct channel will usually clear the error.  Also check to make sure that the Network Interface is on the correct channel.  Sometimes the incorrect channel is just relative to the Network Interface. Look to see if your Network Interface is on the same channel that you are physically connected to.  Move your Network Interface to the correct channel and attempt to commission again If devices have moved recently, it may be necessary to change the routers to Repeater mode.  As a general rule of thumb, it is always best to leave routers in Repeater mode until the conclusion of the commissioning process – just in case some devices need to be moved.  After everything is commissioned and online, then switch the router (or each port of the router) to Configured mode.

Issue An attempt was made to create a connection between nodes on different channels, but no routers were available to complete a logical path between the channels. Environment LNS LonMaker Vista NL220 Cause This error can occur when attempting to remove or move a router which has connections across it, or a router which connects an NSI to either the LNS or another NSI Resolution Lon Maker will not allow the disconnection of a router if the logical path to the device is broken. To combat this you must be creative by adding temporary routers, moving the devices to the new temporary channel, which will create a new path to the devices. the old Routers can then be removed/replaced and the devices can now be returned. Delete any temporary routers/channels.

Issue When accessing an SNP network with SE Vista values are not displayed. Environment UK Cause SE Vista does not support 0 as a LAN number Resolution Edit the XBuilder exported file to change the LAN number from 0 to 1. The XMLM file can be opened with Windows notepad.exe Change " To"

Issue A value could not be found for the specified configuration parameter. Environment LonMaker NL220 Vista LNS Cause This exception will be thrown if you use the GetDataPoint method to create a data point with the lcaDataSourceOptionsDatabaseOnly (2) option set, and then attempt to read the value of the data point, but the value does not exist in the LNS database. Resolution You need to make sure to add your resources to the resource catalog BEFORE importing the XIF to LNS. Once the XIF is imported, adding the resources later will not make them appear. You will need to delete the device template (LonMaker|DeviceTemplates|Delete).  Run ldrfcat and add the directory with your resources in it (usually in \LonWorks\Types\User\MfgName\...) Refresh the catalog and re-import the XIF.

Issue There is a resource problem in the API or application. Environment LonMaker NL220 Vista LNS ZBuilder Cause This may be a compatibility issue observed when launching ZBuilder from LonMaker.  Resolution Zbuilder may work many times after LonMaker is started, but eventually produce this error.  Once the error was produced, it would reoccur every successive attempt.  To launch Zbuilder successfully, LonMaker had to be restarted.  When checking versions, it was discovered that there was ZBuilder 5.0.3 installed and ZBuilder part of the 5.1.0 ToolPack installed.

Issue Host resource allocation problem. Subsystem NS,  #123 lcaErrNsHostResourceProblem.  There is a resource problem in the API or application. Environment LonMaker NL220 LNS Cause NS #123 is a generic LNS resource allocation error (could be memory). This error has been encountered while attempting to re-bind a few SNVTs that had been lost.  When attempting to re-bind, the following error message appeared: 'NS #123: Host resource allocation problem.'    This error has been encountered while attempting to service pin a replaced Xenta programmable.  After a failed download, the service pin resulted in the following error message: 'NS #123: Host resource allocation problem.'    Resolution If there is another LNS application (e.g. LNS DDE Server) running in the background, you may want to shut down other LNS applications and try again.  In some cases, restoring a backup resolved the issue.