Building Automation Knowledge Base

Issue This error will be generated if you attempt to load a new application image into a device with the Load method, and the system image (firmware version) used by the device is incompatible with the new application image.  Some devices support the LoadEx method, which will upgrade the system image to a compatible version when this error occurs.  Environment LonMaker NL220 Vista LNS Cause The device contains an incompatible firmware version. You have a mismatch between the old firmware and new firmware. The old firmware was built (linked) to an older version of the system firmware (Echelon's OS) that's either in the Neuron chip (3120 type) or external flash (3150 type). Resolution The solution is to either: Rebuild your application image (the one you're trying to download) and select the older system image version in the project properties. Update the system (and application) image by reprogramming the flash. That's only possible for a 3150 based product.   Xenta 102-AX upgrade to 2.1.6 caused this error and didn’t allow the new firmware to download.  This particular Xenta 102-AX had previously been loaded incorrectly and rendered applicationless.  This is why it is very important to always know what you are doing prior to loading a new firmware.

Issue Returned when an attempt is made to set the MgmtMode property to lcaMgmtModePropagateConfigUpdates (0) without selecting a network interface. Environment LonMaker NL220 Vista LNS Cause After restoring an NL220 backup file and opening the project using the "Default" network interface, you may receive NS #135. Trying to re-open the network and manually chose the correct network interface, instead of "Default", the same the same error occurs.  Resolution Open the smart channel window and then click on the IP channel, Attached, and Test All.  This resolves the offline network interface. In the NL main window, chose Tools, Attached to Network, and the network status should return to ONNET.   If the Attached and Test All buttons are grayed out then try rebooting the server and connecting the NL220 database again. This may be due to all NIC ports being locked out by another program like Vista.

Issue LNS license access failure.  Environment Cause A variety of conditions may cause this error.  Some relate directly to internal licensing components.  For example, the license DLLs may not have installed properly, the files that identify the license, nsseng.exe for the LNS Server for example.  Certain conditions on the PC operating the license may also cause this error.  For example, if the PCs file system is corrupted or low on space, or if the license files have been manually deleted, tampered with in any way, or moved by some disk-defragmentation utilities, this error will occur. You can resolve these situations by ordering a replacement license key.  If the PC clock is set back to a time before the creation of the license or before the last time credits were purchased, this error will occur. In some cases, this can be resolved by rebooting the PC.  Otherwise, it may be necessary to order a replacement key. The error may occur if the license has been transferred out of the PC, manually terminated, or if there are zero maximum credits.  In this case, you need to purchase additional credits for the license. Resolution Open a DOS command prompt window (Start > Run > cmd) Type "checklic nsseng.exe" and press Enter Take a screenshot Open LNS License Wizard (Start > Programs > Echelon LNS Utilities > LNS Server License Wizard) Take a screenshot Send Echelon both screenshots in order to define the problem and determine how to advise you to fix it.

Issue LNS license time limit has expired. Environment LonMaker NL220 Vista LNS Cause This error will occur if you are using a trial license and the number of days allocated to the license has expired, or if you are using a trial license and set the PC clock back. Resolution For more information on licensing, see Chapter 13 of the LNS Programmers Guide. All the LNS deficit credits have been used. You have to recredit LNS.

Issue Error: Subsystem NS, #149 lcaErrNsConflictWithCurrentNetwork This error will be generated if you open a network that is already opened using a different network interface, LNS type, or database directory. Environment LonMaker NL220 Vista LNS Cause After restoring a LonMaker database, or upgrading a LonMaker system, each LNS database has to be opened before the Vista server is started or you get this error. Same as with LonMaker, if you start the NL220 stand alone, and then start Vista, the LNS server will not be conflicted.  If switching between LonWorks Interface types (example:  RNI to PCLTA) you may receive this error when trying to open the LonMaker drawing.   Cannot run LNS Database Validation Tool with the database open (Start > Programs > Echelon LNS Utilities > LNS Database Validation Tool 3.2). Resolution Shut down the Vista Server. If Vista Server is set to run as a service (Control Panel > Administrative Tools > Services > TACOS) manually stop the service. Open each LNS database network attached and onnet.  Restart the server. If this error occurred from switching LonWorks Interface types, rebooting the PC should clear the error.

Issue Monitor point cannot be found. Environment Echelon LonMaker NL220 Vista LNS Cause When trying to resynchronize, you may get this error. Resolution  A monitor point is a member of a monitor set.  They are created when you right click on a SNVT in the LonMaker drawing and choose “Monitor.”  If a monitor point can no longer be found, then it can be cleaned out of the monitor set to eliminate this error. Navigate to LonMaker > Network Service Devices.  Click on the NSD Name for your network, which highlights the Monitor Sets button.  Click it. Expand the view to find Echelon LonMaker Monitor Sets.  These are the monitor points created manually by monitoring a point in the drawing.  They are optional and unnecessary.  Right click on Echelon LonMaker Monitor Sets and select Delete. Select "Done".  Select "Done".  LonMaker > Resynchronize.  Try it again.  This time check Sync drawing to database (fix-up drawing).  Also, check Sync monitor sets between drawing and database. It should resynchronize successfully now.  In the future instead of right clicking on a SNVT binding and selecting monitor value, use get value.  This will momentarily show you the LON value without creating monitor sets, which can later cause this error.

Issue No routers exist to complete logical path needed for monitoring and control. Environment LonMaker NL220 Vista LNS Cause When initially creating a multi-port router, the internal L-IP FT-1250 channel was designated as an existing FT-10 channel.  The drawing was built and then couldn’t be commissioned due to the physical topology not matching the drawing. Resolution With no logical path for the controllers and you attempt to move them to another channel, you must first  correctly define the router in the Visio drawing.

Issue Neuron model version mismatch.  Environment LonMaker NL220 Vista LNS Cause This error will be generated if you attempt to use the Load method to load an application image into a device that is incompatible with the devices system image.  Resolution In this case, you need to upgrade the devices system image.  Some devices support the LoadEx method, which automatically upgrades the system image before loading the application image if there are compatibility problems.

Issue New system image cannot be written Environment LonMaker NL220 Vista LNS Cause This error will be generated if you invoke the LoadEx method on a device, but the system image cannot be written, probably because it is not stored in flash memory.  Resolution The old system image will remain intact if this error is thrown.  However, the device will remain applicationless.  You should load a new application image into the device with the Load or LoadEx methods in this case.

Issue New system image memory fails during upgrade. Environment LonMaker NL220 Vista LNS Cause This error will be generated if there is a failure to write the new system image the device after the LoadEx method has been invoked. These failures usually occur because the device does not have flash memory in the required location to hold the new image during the download process. Resolution The old system image will remain intact if this error is thrown.  However, the device will remain applicationless.  You should load a new application image into the device with the Load or LoadEx methods in this case.

Issue New system image failed to upgrade. Environment LonMaker NL220 Vista LNS Cause This error will be generated when you invoke the LoadEx method on a device, and the new system image is successfully transferred to the device, but the switch from an old system image to a new system image fails.  Resolution  If you encounter this error, try invoking the LoadEx method again, or loading the previous system image back into the device.

Issue The application timed out starting the LNS engine process (NssEng.Exe).  Environment LonMaker NL220 Vista LNS Cause This could be an indication that LNS is not installed properly.  Resolution If you encounter this error, you should try the following steps in order. Restart the "Echelon LNS Server" service Rebooting the PC Re-installing LNS

Issue The specified LonMarkObject is not dynamic. Environment LonMaker NL220 Vista LNS Cause This exception may be thrown if you attempt to assign a network variable to a static LonMarkObject with the AssignNetworkVariable method, unassign a network variable from a static LonMarkObject with the UnassignNetworkVariable method, or delete a static LonMarkObject with the Remove method. Resolution You can determine if a LonMarkObject is dynamic or not by reading its IsDynamic property.

Issue The specified network variable is not dynamic. Environment LonMaker NL220 Vista LNS Cause This exception may be thrown if you attempt to assign a static network variable to a LonMarkObject with the AssignNetworkVariable method, unassign a static network variable from a LonMarkObject with the UnassignNetworkVariable method, or delete a static network variable with the Remove method. Resolution You can determine if a network variable is dynamic or not by reading its IsDynamic property.

Issue The specified LonMarkObject is in use, and at least one of its member network variables is bound. Environment LonMaker NL220 Vista LNS Cause This error may be thrown if you use the Remove or RemoveByIndex methods to delete a LonMarkObject with the lcaLonMarkObjectRemoveNVs (1) option set as the removalFlags element, and that LonMarkObject contains bound network variables. Resolution The bound network variables must be disconnected before the LonMarkObject can be deleted. You can disconnect the network variables by specifying the lcaLonMarkObjectRemoveAndDisconnectNVs (3) option as the removalFlags element when you call the Remove or RemoveByIndex methods

Issue The link between the parent and the child record was unexpected. Environment LonMaker NL220 Vista LNS Cause This error usually indicates that the LNS database has been corrupted. Resolution If you encounter this error, you should use the Validate method to run a database validation, and consider switching to a backup database.

Issue The database updates were successful, but one or more nodes were not updated because the node(s) rejected the update, for example due to an authentication failure.  A device encountered an operational or messaging error while its configuration was being updated. Environment LonMaker NL220 Vista LNS Cause This usually means that there is a configuration mismatch between the node and the LNS database.  The LNS will continue to try to update the nodes in the background if the UpdateInterval property of the System object is set to a non-zero value, and you can force a retry with the RetryUpdates method. This seems to have two origins – either in the LNS tool which commissioning or creating group bindings, etc., or in the System Plug-in while trying to download a programmable controller.  It has been observed when creating group bindings when most of the controllers were offline in an onnet connected network. It has been observed while creating and downloading a network in NL220.  All of the correct steps of creating a node, importing a Menta file, updating the network, and downloading were followed.  During a download, an error occurs: “A device encountered an operational or messaging error while its configuration was being updated” (Subsystem: NS, #4031).  After which an additional dummy device was created and inherited the neuron ID of the controller originally being downloaded. It has been observed on an engineering PC using a NIC USB running under Windows Vista which had been reverted to Windows XP.   Commissioning a router in a brand new NL220 Smart Channel results in this error.  Resolution This error occurs because LonMaker/LNS does not receive the device's response in a timely manner during the commissioning process. A new property (AppDevice::Delay) was introduced in LNS Turbo to resolve this issue. This Delay value will be added to any delays calculated by LNS based on the network topology. When this property contains the default value of 0, LNS will not calculate an extra delay for the device. For earlier versions of LNS, the workaround is to increase the channel delay.  Please note that this solution will affect all devices on that channel. Also note that the AppDevice::Delay property is not exposed in the LonMaker Turbo Edition. To modify this property, you must use another LNS application, such as the LNS Object Browser (lnsobjectbrowser.exe located in your LonWorks\bin folder). You can keep track of which devices are up to date using commissioning events, and by reading the CommissionStatus property of each AppDevice object.  If you are receiving persistent update failures on a device, you should re-commission the device with the Commission method. In some cases, switching to a PC using an Echelon LTA cleared the problem. It has been observed that in NL220, an incorrect Device Template was assigned to the Controller during the commission process. The workaround was found by deleting the controller, updating Vista, and then deleting the offending template (in this case Lonm401 assigned to a Xenta 282). The controller then was able to be added with the correct Template. In another case, the controller had to be decommissioned, the controller had to be deleted (including the IO modules if they exist), the TAC network tree inside the system plug-in was deleted, and then the Vista database was updated. A new controller was then added to the page and the commissioning process was started over. All bindings are lost in this process. 

Issue The database updates were successful, but the configuration properties on one or more devices could not be updated as a result of invalid configuration property definitions.  The LNS will continue to try to update the nodes in the background if the UpdateInterval property of the System object is set to a non-zero value, and you can force a retry with the RetryUpdates method. Environment LonMaker NL220 Vista LNS Cause You can keep track of which devices are up to date using commissioning events, and by reading the CommissionStatus property of each AppDevice object.  If you are receiving persistent update failures on a device, you should re-commission the device with the Commission method. This error can occur while running LNS TE with NL220. This error is likely due to the device implementation. It could occur if the CP definitions were incorrect for example or if the device implements changeable-type NVs and the type change was rejected by the device. Resolution The best is to get a protocol analyser log of the CP download. 

Issue When launching NLCredits Generator, you get the following error : THE OBJECT WAS NOT FOUND. (SUBSYSTEM: LNS, #6)  An object has been requested by name or index that could not be found in the databases.  Typically, this would be a request from a LNS collection object with a bad name or index. Environment NL220 Vista LNS Cause An object has been requested by name or index that could not be found in the databases.  Typically, this would be a request from a LNS collection object with a bad name or index. It should be noted that this error can also occur in some implicit assignments. For example, if the network interface to be used has not been explicitly assigned to the appropriate property, LNS will continue using the network interface previously assigned to the ActiveRemoteNI or NetworkInterface property, respectively. In such a scenario, this exception could occur even though no explicit assignment has been made, indicating that an implicit assignment maps to an unavailable object. A monitor set may be created while offnet (System.MgmtMode is set to lcaOffNet); however, a monitor set cannot be opened while offnet. Furthermore, attempts to query the MonitorSet.IsOpen property will get the error "The object is not found (Subsystem: LNS, #6)" when offnet Resolution Launch NL220 and check if there is a project with a name only composed by alphanumerical characters (for instance, something like 82807E44116C482). Delete the project if you find it. Go to C:\NLPrj and manually delete the directory of the project you've deleted in NL220.

Issue An unexpected error occurred. Environment LonMaker Vista LNS Cause An unexpected error occurred. Resolution Please contact Echelon technical support on LonSupport@Echelon.com