Building Automation Knowledge Base

Issue Migrating from LonMaker to NL220 Environment LonMaker NL220 Cause Changing LNS management tools. Resolution If both Lon Maker and NL220 reside on the PC: Migrating from LonMaker (or other LNS management tool) to NL220, all that is required is the LNS database.  NL220 will recognize the LNS Databases which have already been created in LonMaker. Open the database in NL220. There is no need to recommission online devices, so no credits need to be re-purchased.   If the LNS must be transferred onto a PC that only has NL220 installed: Take a copy of the Folder located in the directory Lm/Db/[name of project]/files Place this folder in C:\NLPrj\[name of project]\files Create a new Project in NL220 Name the project Select 'open an existing database' Browse to the Project path (C:\NLPrj\ ) Select OK. NOTE: Migrating from NL220 (or other LNS management tool) back to LonMaker is a little less seamless because LonMaker utilizes proprietary Visio drawings for viewing the network, and these are not native to the LNS database.  Viewing the network may be difficult with the automatically generated Visio drawings.

Issue Changes to public variables (PVR, PVI, PVB) in a Menta file on a live system are accepted by the database, but it seems that the actual controller is ignoring these changes, or not seeing them. Environment Vista Workstation More commonly a Vista Classic Network, though it does apply to LNS Cause In the upper left-hand corner of the Workstation, there is a drop-down menu to select either Engineering or Operating mode.  Engineering mode is used most often in a Vista Classic Network while adding or configuring new controllers.  While in engineering mode, changes can be made to database values, but these changes will not be propagated down into the controllers. Resolution Change back to Operating mode.

Issue Under user admin in a Xenta server you can change the content of the 3 frames that the user sees when logging in. If the user have changed the default frames for the root user in a Xenta server so that the tree navigation is not available you can't navigate back to user admin to reset the frames. Environment TAC Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause User have changed the frames so that the menu tree is no longer available Resolution Log on to the Xenta server with the root account. Type in https://xx.xx.xx.xx/wm/useradmin/ in the IE address field. This takes you directly to the useradmin page. Click on the root user. Under Frame Settings click on Use Default for the Menu frame.

Issue Error message: Insufficient object database authority to start the TAC Vista Server, when starting the TAC Vista Server. Environment Windows 7, Vista Server Cause TAC Vista Server thought the log in user does not have the full rights to view the TAC Vista Database. Resolution Before doing anything, please make sure you are logged in as an administrator.  Close Vista Server, then follow the steps below Go to TAC Vista Server Setup (Start/All Programs/Schneider Electric/TAC Vista Sever 5.1.X/Server Setup). Select "Authority" tab and click on the "Grant Access" button. You should get a success message. Start the Server again, you should not get the error message again. If it still doesn't work do the following:  Right click on the database folder. Unmark the "read only" check box. Click apply. Select  "Change this folder, subfolders and files".  

Issue Is the ICI editor and associated BIN files still available. Environment I/Net Seven all revisions. 7797 ICI all firmware revisions connecting to a third party device.  Cause It is not clearly defined in the documentation the location of the ICI Editor and associate BIN files. Resolution The ICI Editor is part of the I/NET install CD, the application is found under the folder name ICI-CD.  The associated BIN files for these devices are also located on the I/NET CD under the folder name SUPPORT\BINS.

Issue After transferring an LNS database from NL220 or LonMaker into TAC Vista Workstation, all controllers are green (online) in Workstation. However, clicking on some programmable controllers results in an error message that states: "The blueprint is corrupted." Environment TAC Vista Workstation Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause The TAC Xenta group name was too long or contained spaces. (More than 20 characters)   Resolution Change the Xenta Group name to be less than 20 characters without any spaces.

Issue The xDriver profile selected does not exist, or the xDriver connection broker is not currently running. Environment LNS NL220 LonMaker Vista Cause Make sure that the profile you are using exists, and that the xDriver connection broker service has been started if you encounter this error. Resolution For more information on the xDriver connection broker, see the OpenLDV Programmer’s Guide, xDriver Supplement. http://downloads.echelon.com/support/documentation/manuals/devtools/078-0275-01C.pdf

Issue You attempted to create an object with a name that is already being used by an object of that type. Environment LNS NL220 LonMaker Vista Cause For example, the name assigned to all LonMarkObject objects must be unique. Therefore, if you use the Add method to create a LonMarkObject and specify a name that is already being used by another LonMarkObject, this exception will be thrown Resolution Name LonMarkObject as something unique.

Issue Could not initialize the LonTalk stack. Environment LNS NL220 LonMaker Vista Cause Could not initialize the LonTalk stack. Resolution First, close the LonMaker tool, then test your network interface using the LonWorks Plug 'n Play utility found in the Windows Control Panel. Once there, press the "Diagnostics" button and then press the "Test" button. If you get a "Failed" message similar to the following: ------------------------------------------------------------------------------ LonWorks® PCC10/PCLTA10/PCLTA20 Device Driver Version: 2.01 Card Type: PCLTA-20 / LMPA Driver Status:           Number of Free LTA Output Buffers-            Non-Priority: 0, Priority: 0           Loaded Image Size: 16384           Interrupt Count: 17333 ------ Network Interface Node Status ------ ** Failed ** ------------------------------------------------------------------------------ Then go back to the main LonWorks Plug 'n Play dialog and change your NI Application to something other than what is currently selected. Click on the "apply" button and do the test again. Don't forget to change it back to its original NI Application. Remember that the LonMaker tool can work with either the "NSI" or "VNI" NI Application images, although "VNI" is preferred due to higher performance. You may also want to try to "reset" and "restart" your network interface card and driver from the "Diagnostics" window. Once you stop getting the "Failed" message and see the network interface statistics, you should be able to open the network from the LonMaker tool. The following is an example of a successful "Test" result. Some of the counts may not be zero, but that should not be a problem unless it increases rapidly as you test again and again. If that happens, it can be due (most of the time) to one of three problems: wiring connections, excessive noise, or excessive traffic on the network. ------------------------------------------------------------------------------ LonWorks® PCC10/PCLTA10/PCLTA20 Device Driver Version: 2.01 Card Type: PCLTA-20 / LMPA Driver Status:           Loaded Image Size: 57344           Interrupt Count: 20345 ------ Network Interface Node Status ------ CRC Errors:                  [00000] TX Timeouts:                 [00000] Lost (APP) Messages:         [00000] Missed (NET) Messages:       [00000] Most recent error:           0 Reset Cause:                 External ------------------------------------------------------------------------------  

Issue The LonMaker tool has the incorrect NSI or "VNI" NI application images Environment LNS NL220 LonMaker Vista Cause The LonMaker tool only works with NSI or "VNI" NI application images, i.e., PCL10VNI or NSIPCLTA. Resolution Unable to change the state of the network interface. i.LON 100 or SmartServer: There are two types of RNIs, "Other" and "LonScanner". For LonMaker (or a LNS application), you must use the "Other" RNI. For LonScanner, you must use the "LonScanner" RNI. Check the interface setting in the LonWorks Interface Applet which is available in the Windows Control Panel. Select the RNI tab and double click the RNI you are using. If the interface setting is set incorrectly, change it to the correct one and press the Apply button. PCC-10 or PCLTAs: The LonMaker tool works with NSI or "VNI" NI application images, i.e., PCL10VNI or NSIPCLTA. To eliminate this error message, open the LonWorks Plug 'n Play utility from the Control Panel and check your NI Application. If it is "PCC10L7", it needs to be changed to PCL10VNI or NSIPCLTA. Hit Apply to change the image, then go ahead and open the network again.

Issue The network interface has already been opened with a different network driver.  Environment LNS LonMaker Vista Cause This error will be generated if you open a network that is already opened using a different network interface, LNS type, or database directory. Resolution Access the network properly.

Issue The Data Server failed to initialize properly. Environment LNS NL220 Vista Cause This exception could be thrown if your application specifies an invalid name or index number when retrieving an object from the LNS database. This error can occur when trying to monitor a variable with the DataServer of LNS 3.08.  Resolution It is a corrupted database error. The best thing to do is to come back to a previous backup of your database

Issue How to create a LNS database in NL220 and then bring it to Vista Workstation online Product Line TAC Vista Environment NL220 Cause In order to have a healthy LNS database, it is very important to create this database with proper steps in NL220. Resolution Preparation: Configure the Infrastructure Device Set up Vista Database path   Creating LNS Db in NL220 NL220: Add infrastructure device, nodes, etc. System plug-in: Assign Neuron ID (Optional), Menta file Back to NL220: SNVT binding   Bring LNS Db to Vista Db System plug-in: Network settings, Update TAC Network, create group bindings, add I/O modules, update the TAC Network again, check TAC Network, Update Vista Database   Bring Vista Db online NL220: Commission the Infrastructure Device System plug-in: Verify network settings, assign Neuron ID if needed, update TAC network and Vista database, download application and parameters Back to NL220: Commission and downloading all nodes besides I/O modules. Back to system plug-in: Change infrastructure setting, commence communication

Issue A Continuum database setup for IE. version 1.81 will only support Continuum software version 1.81. Environment Continuum all versions Cause Attempting to use different versions of the Continuum software on a Continuum database Resolution Using Continuum software version IE. 1.9 would not be able to access a database setup for ie... older Continuum version 1.81. This is true for all versions of Continuum. The Continuum software and database must be of the same version.

Issue TCP/IP Network Settings required for an I/NET Seven Installation.  If the incorrect network speed is used, communication with the NPR-2000 and the Xenta 527 will fail. Environment TCP/IP Network I/NET Seven NPR-2000, Xenta 527 Cause I/NET works on 10 Mb/Second (also known as 10-half).  The NPR-2000s and the Xenta 527 will only function on 10-half. Resolution I/NET requires Microsoft's TCP/IP protocol. While I/NET Seven can coexist with another vendors networking software, (Novell or Banyan, for example) it will not use any other version of TCP/IP. You can add Microsoft's TCP/IP in the Network options of the Control Panel. Most modern Ethernet Switch gear should be set to "Auto Negotiate" for 10/100mb speed required by a device, but speed is an important factor for proper communication.  I/NET can only run on a 10 Mb/Second network. Old style NetPlus Routers(NPR-2000), Xenta  527 NPR, and Xenta 527 Web require 10 Mb/Second.  See TCON 300 (from the Technical Reference Manual included on the I/NET installation CD) for further details.  TCON 300 has all of this information on pages 1-9; 1-33 & 1-34 Because this is not an individual PC configuration, assistance from the building IT staff will likely be required.  

Issue Xenta Server is marked with an asterisk and says "Needs to be Commissioned" Environment Vista Workstation Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause The files in the Xenta Server do not match the Xbuilder project stored in the Vista Database. Resolution Right-click on the Xenta Server in Vista Workstation and select Edit.  This will open XBuilder. In Xbuilder, click "Send to Target" to download the files to the Xenta Server.

Issue An error is received on Continuum startup on videoLaunch Method 'There is an installation configuration problem, and this application is unavailable...constructor error' not found. Environment Windows XP SP3 Windows Server 2003 Continuum 1.91 Webclient 1.91 Cause Some PCs come with .net 3.5 pre-installed. If Continuum 1.91 is installed the installation will complete, but then the method, constructor error is received. The compatibility matrix indicates that we require .net 3.5 SP1.  Resolution Install .net 3.5 SP1 and attempt to start Continuum. If the same error pops up then do the following: Remove continuum from Windows Add/Remove programs from Windows Control Panel Reboot the PC Install 3.5 SP1 by running donetfx35.exe (This is on the service release CD in the NetFramewrok3.5 folder) It contains SP1. Reinstall Continuum This error could also occur if 1.90 is being used and .net 3.5 SP1 is installed

Issue Nodes not showing up under subsystem view in System plug-in with NL220. However, in NL220 under subsystem tree, everything shows up fine. Environment NL220, system plug-in Cause This can occur if the default root subsystem "Locations" was deleted. The "Locations" root subsystem must be linked to the geography of the site. Therefore, deleting it may cause the lost of the link. You can change the "Locations" root subsystem’s name to something else. However, we do not suggest deleting and adding a root subsystem back. Resolution Before doing anything, please make a back up of your LNS database. Create a new root subsystem. (Right click on the Project object and select the option “New root subsystem”). When asked for the name, type "Locations". Copy all nodes under all subsystems and paste them into the "Locations" root subsystem you just created. Delete all the subsystems outside of the “Locations” root subsystem. Go to "Edit" tab, choose "define location subsystems" Select "Locations" root subsystem. Click on "location subsystem" button on the right. Click on "Yes" Refresh the tree. Go to the System Plug-in, you should be able to view all nodes under subsystem view. Now, you can go back to NL220 and change the root subsystem name to anything you want.

Issue An error is received, comm port is not enabled when trying to apply the 2nd generation xdriver file to comm2 on a BCX. Environment Continuum 1.9x BCX4040 Xdriver Cause Typically comm2 is set to mstp. Trying to apply the Xdriver file to the comm port thinks it already has the port applied and renders the error. Resolution Pull the battery connection Power off the controller which sets the port to autoset Power up the controller Set comm2 to xdriver and apply the file and no error is received -If this still doesn't work then update the firmware, it may resolve the issue If this does not resolve the issue try Clearing Database Backup from the controllers webpage and reload.

Issue Change of font color isn't kept when viewing graphics page. Environment TAC I/Net Seven by Schneider Electric Cause Font colors not remembered when selected, for example on an AI point, simple temperature value, the font at the bottom of the screen is changed to any of the colors available. I/NET reverts back to black. Resolution Located on the I/Net Seven 2.31 cd, there is a folder named: Patch-B Graphics Paste Inside this folder is a file named: INET Rev 231Graphic Patch with size.zip  Take this file, unzip, and with INET closed, and the I/O Server shut down, copy into your I/Net Seven folder on the C:\Program Files\INET Seven This overwrites a variety of files, dll etc.