Building Automation Knowledge Base

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 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 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 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 Graphics or Webpages not working in a Xenta 701 or 721.  They can be built and configured in XBuilder, but then when logging into the web interface, they do not appear in the menu. Environment Xenta 701, Xenta 721 Cause The Xenta 701 and Xenta 721 only have "Service Web" capabilities. Service Web means it is not possible to have any end-user web content, such as graphics, trend viewers, alarm viewers or value pages. To get access to end-user information, connect the Service Web controllers to TAC Vista and retrieve the full range of information. The Xenta 711 and Xenta 731 have the necessary support for "Custom Web." Custom Web means that the web interface is totally configurable in TAC XBuilder, the Xenta server configuration tool; navigation and all features for creating a full end-user web are available.   Modbus MicroNet I/NET WEB I/O Modules Support Xenta 280/300/401 Xenta 701       Service 10   Xenta 711       Custom 10 X Xenta 721       Service 20 X Xenta 731 X X X Custom 20 X Resolution If custom web is needed at the Xenta Server then a Xenta 711 or 731 needs to be installed instead of the 701 or 711. Another option would be to put Vista on top of the Xenta Server and build graphics at the HMI level.

Issue During the boot sequence of a Xenta Server the message "Unmap block xxx at remount" occurs. Environment Xenta 511 Xenta 527 Xenta 555 Xenta 701 Xenta 711 Xenta 721 Xenta 731 Xenta 913 Cause Sections of the flash drive are being declared bad and are being removed from the accessible drive map. This can be a natural pruning process of bad sections due to drive damage or that section exceeding the maximum number of writes. The amount of lost space is: # of pages * 2 bytes All hardware 2 Xenta Servers have 16mb flash drives, so it takes a large number of pages to be lost before significant space is lost and will impact performance of the unit. Resolution If the number of pages is low and is not increasing then the unit should function normally without any additional action. If the number of pages is exceeding 50000 or increasing rapidly, then have the Xenta Server repaired or replaced depending on its age.

Issue Various error when trying to login, cant open graphics Environment Vista webstation Cause Java errors i.e. When opening graphic error "Error: Click for detail" or Dynamic mode not functioning. Resolution Dynamic picture not working are most likely caused by wrong Java version. Vista 5.1.4 uses Java 1.6-17 but installing this version afterwards might causes other problem like "Error: Click for detail (various java code errors). This can be resolved by reinstalling the webserver again or check for the following. IIS use the wrong version of .NET. - Go to administrator tool and choose Internet information services. - Choose Web sites then Default Web Site - Right click on Webstation and choose properties - Go to the ASP.NET tab and make sure the version specified are 2.0.... Address used  HTTP://IP/defaultpage.aspx when it should be using HTTP://IP/webstation/defaultpage.aspx - Go to same path as above but instead of right clicking the Webstation right click on the tree above "Default Web Site" and choose properties. - Go to the tab Home directory and check local path it should be directed to wwwroot (see attached) Then write in the address HTTP://IP/webstation/ (might work if you try directly) There have always been problem in which order you install programs, it has been noticed that sometimes java needs to be installed before webstation since webstation tries to reach components in java that do not exist else. So a try would also be to reinstall webstation now when the new Java version are already installed.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue How to restore and view a Log backup without overwriting current database How to view backed-up events without overwriting current database How to restore a SQL database  without overwriting current database Environment TAC Vista 4.3 and higher running a typical (not custom) SQL. Cause The event and logs will be backed up as a SQL backup file. This means that restoring a backup on the same PC that it was made on replaces the SQL database.    Resolution To view old data, restore the log database backup file on a different PC that has the same TAC Vista database on it. Create a copy of the TAC Vista database (or make a backup) Copy / restore the database to a computer that is running the same version of TAC Vista Go to the Server application and log in Go to File > Restore Log Database Browse in the backup file, the path should be filled in automatically

Issue How and when does a Xenta 102-AX resynchronize its damper floating output control? Environment Xenta 102-AX v2.17 and up Cause Documented reasons for a damper and floating output resynchronization on a Xenta 102-AX controller Resolution There are 5 events that cause a Xenta 102-AX to resynchronize its floating control logic for the damper and other outputs. These reasons are: At controller reset. (This could be a power cycle or reset command via TAC Vista/LNS) If the damper motor position command has been inside its "active zone" (5% - 95%) for an accumulated time of 24 hours, AND the motor position then goes to 0% or 100% (Note that the outputs and damper are timed and reset independent of each other) Indication of error in flow detection. This is if nvoFlowControlPt = 0 but nvoMotorPositn > 0 for 1 minute or more If nviEmergCmd is set to any of the following modes: EMERG_PRESSURIZE EMERG_DEPRESSURIZE EMERG_PURGE EMERG_SHUTDOWN and then goes back to EMERG_NORMAL A controller reset via Lonmaker or NL220 will also cause a resynchronization of the damper and the other floating outputs. This is necessary if the stroke time (throttling range) or stroke direction is changed in the middle of a damper operation

Issue When directly connected to a Xenta programmable controller through a serial cable, and observing live Menta, it is possible to override inputs and outputs.  This override is the same override attribute that can be set from the OP and from the Workstation. Environment Menta Xenta programmable Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause Overriding points while simultaneously witnessing live updates of all program values is an effective troubleshooting technique. Resolution Directly connect live to a Xenta Programmable Download the correct Menta file to the hard drive of a laptop. Right click on the controller in Workstation and select Edit. File > Save As ... to the hard drive. The Menta file must exactly match what currently is downloaded into the controller or else it won't connect. Connect to the RS-232 port on the face of the Xenta programmable. Open the Menta file. Options > Simulate Click the Online button in the top left corner. Select "Connect" from the menu. View I/O and override Options > I/O Configuration This brings up a list of all inputs and outputs in the controller.  The last column says "Not overridden" for any point not currently overridden.  If it is, it will show the override value.  Choose a point and click the Override button at the bottom. Check the box to override and enter the desired value.  Click OK. The point is now in override. NOTE: This override attribute is the same override that is available through the OP and through Vista Workstation.  Points can be put into override and taken out of override from any of these 3 locations and it will dynamically update any other concurrent users.

Issue In TAC Menta, under Device Specification, it is not possible to  define the actual System Version or Hardware version of your TAC Xenta device. Environment TAC Menta Version 5.1.5 TAC Xenta 280/300/401 Version 3.80, 3.84 Cause When a new System Program for TAC Xenta devices is released, TAC Menta is not always updated with the latest TAC Xenta version number. Resolution Until the correct TAC Xenta System Version number are available in the TAC Menta, you could use the closest lower version number.

Issue Changes made in TAC vista workstation are not saved in TAC Menta. Change of alarm texts made in TAC Vista workstation are not saved in TAC Menta Change of value of a PVR block made in TAC Vista workstation is not saved in TAC Vista. Environment TAC Vista 5.1 Cause In TAC Vista workstation it is possible to type in texts in the description field that are longer then TAC Menta allows. If you do this no changes made to that signal (block) done from TAC Vista workstation will be saved in the TAC Menta file Resolution Edit the Description for the block so that it is 41 characters of less.

Issue When transferring a value from an analog value to a multistate using object transfer, negative values are inverted. Environment Vista Object Transfers Cause A problem in the Vista software. Resolution This value with need to be converted in Menta first, then connected to the object transfer. The steps to convert the value in Menta are: Select the TAC Xenta device in Vista. Right-click the device and select "Edit". Add an AI block and connect it to a ConversionAA operator. Connect the ConversionAA operator to a DELI block. Edit the DELI block - give the variable a name (Identifier) and make sure the "Public" checkbox is ticked. Save and close the Menta application. Commission and download the updated Mental application. Connect the new variable created in step 5 to the "Object Transfer" object.