Building Automation Knowledge Base

Issue When using I/A MNL800 controllers in Vista classic network (without using LNS database), an issue will happen when commissioning and downloading the controller: Local Network Management Failure, Info: nci_Location. The xif file has been updated to the newest version of the WPT program. Environment WPT version higher than 5.7.2 Vista 5.1.6 Cause The possible cause is that the WPT version is too high for Vista classic network to integrate. Resolution Firstly it isn't recommended to use I/A LonWorks controllers in Vista system. And there is no specific compatible matrix for Vista and WPT. Currently the proved version of WPT that can be used with Vista 5.1.6 is 5.7.2. The version higher than this will has this issue. So the only solution is to use the xif file generated by WPT 5.7.2 in Vista classic network.

Issue Start TAC Vista Comm. Log Product Line TAC Vista Environment TAC Vista Server Cause Sometimes to solve a problem we need to record the communication to and from TAC Vista. Resolution Start the TAC Vista server Open workstation and close all graphics, charts, etc., that are not needed to reduce traffic and make the log easier to read. Log in to TAC Vista Server. Go to Log > Comm. Log Set Physical layer to active Click Ok  The log will be created in the $log folder in the TAC Vista db.

Issue Naming a point in Menta results in a pop up error Warning Syntax error Product Line TAC Vista Environment Menta Cause Special characters are not permitted in the names of Menta signals. Resolution Remove all of the following characters from the Menta signal name: space . period, ? question mark - dash (hyphen) !, @, #, $, %, ^, &, *, (, ) \ backslash denotes the Menta module name separated from the Menta signal name. One is permitted, the second will cause a syntax error The best rule to go by is to use nothing but alphanumeric characters and (_) underscores in Menta naming conventions.

Issue Get "Type error: cannot call method "toFixed" of null" error message when opening a TGML graphic, upgraded to Vista 5.1.7   A TGML script has stopped working after upgrading to Vista 5.1.7 Environment TAC Vista Workstation 5.1.7 TGML editor 5.1.7 219 Cause Javascript method toFixed can only be used with numerical values. The TGML engine in TGML 5.1.7 is stricter than the older versions, so an upgraded script may have worked in previous versions. Resolution An example when using convertCustom element. Original script: function convert(value) { value = value.toFixed(2); return value; } should be: function convert(value) { value = Number(value).toFixed(2); return value; }  

Issue Get "Value does not fall within expected range" error message when trying to view values from a Vista node in webstation. Environment Vista 5.1.X Webstation 5.1.X Vista in network (master with at least 1 slave) Cause This is a COM error caused by a difference in regional settings on the Vista servers. E.g. 100 000.00 may be retrieved as 100,000.00 if other settings are used on another server. This will cause a mismatch. Resolution Ensure that the settings for digit grouping and decimal symbol are the same on all Vista servers. Click on Start\Control Panel\Regional and language options. Select Customize and check the settings on the Numbers tab. Compare these settings with the other Vista servers.

Issue Import/Export in TAC Vista Workstation does not work. Nothing happens when trying to start the import/export. Environment TAC Vista Cause The $DatabaseExport and $DatabaseImport objects in the Vista database has been removed, probably during an upgrade. Resolution In the instructions below, we assume that TAC Vista is installed in the default location. Replace the version number (5.1.6) with the actual version you have installed, and the Vista Server name (VistaServer) with the actual name of your Vista Server. This procedure requires that TAC Vista Server is running as an application, and not as a service. 1. Make sure TAC Vista Server is stopped -- First we need to change a file to allow creation of these objects -- 2. Browse to C:\Program Files\Schneider Electric\TAC Vista 5.1.6\$cfg 3. Find a file named "objtmpl.cfg", make a copy, just in case. 4. Edit the file with notepad and find the strings FI_EXPORT and FI_IMPORT. 5. Remove AB on each of the two lines, (stands for abstract object), save and close. 6. Browse to the TAC Vista database folder, and open the folder $thisdb. 7. Change the name of the file TacVista.cfg, to TacVistaOld.cfg 8. Start TAC Vista Server. -- Now we need to create the missing objects -- 9. Open the testclient (testclt.exe) located in the folder C:\Program Files\Schneider Electric\TAC Vista 5.1.6 10. In the menu, click "Session-->Log in" 11. In the menu, click "Services-->Create" 12. In the ID field, write "VistaServer-DatabaseExport" and in the type field write "FI_EXPORT" 13. Click "Create". 14. In the ID field, write "VistaServer-DatabaseImport" and in the type field write "FI_IMPORT" 15. Click "Create". -- Now we have to change the name of the created objects to $DatabaseExport and $DatabaseImport -- 16. In the menu, click "Services-->Access" 17. In "Enter ID:" write "VistaServer-DatabaseExport.$name" 18. Click "Request" 19. Write "$DatabaseExport" in the "New Value" field, and click "Poke". 20. In "Enter ID:" write "VistaServer-DatabaseImport.$name" 21. Click "Request" 22. Write "$DatabaseImport" in the "New Value" field, and click "Poke". 23. Reenter AB on each of the two lines in "objtmpl.cfg" previously edited in step 4, save and close.  

Issue There are a number of TGML link or binding objects with the name ??128 in a folder in Vista workstation. They cannot be deleted. An error message "Could not delete the object. Attempt to delete an abstract object" appears. Product Line TAC Vista Environment TAC Vista Workstation 5.1.X Cause Sub-objects from a TGML graphic have not been removed from the database when the graphic has been deleted. This may be an indication that the database is corrupt. The error from Vista is "nonexisting object in request/advise/poke". Resolution It may be possible to delete the folder that the objects are in and thereby remove the sub-objects. Otherwise a backup of the Vista database (from a time before the objects appeared) will need to be restored.

Issue Vista hangs when navigating between TGML graphics. The screen dims, Vista workstation stops responding and an error message is displayed. In the event viewer the following event description is displayed: Description: Application: TACVistaExplorer.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException Stack:    at java.lang.String.instancehelper_length(System.String)    at SE.Graphics.DOM.TGML.TgmlTextShape.setAttribute(System.String, System.String)    at SE.Graphics.DOM.TGML.TgmlBind.internalSetAttribute(System.String, System.String)    at SE.Graphics.DOM.TGML.TgmlBind.executeBind(System.Object, System.String, System.String, Int32)    at SE.Graphics.GraphicsServices.Dynamics.BindUpdater.executeBinds(SE.Graphics.GraphicsServices.GraphicsDocument)    at SE.Graphics.GraphicsServices.GraphicsDocument.UpdateBinds()    at SE.Graphics.Viewer.Windows.GDIPlus.GraphicsViewerControl.UpdateDynamics()    at TAC.Graphics.Windows.Vista.VistaGraphicsViewerControl.UpdateView()    at .CODEChildTgmlGraphics.UpdateView(CODEChildTgmlGraphics*)    at ._WinMainCRTStartup()   Environment Vista Workstation 5.1.6 TGML graphics Cause Workstation crashes when the TGML graphic updates it's content. It's suspected that at the same time as the TGML graphic is updating it's content, the graphic is changed, which means that it's not there anymore to receive the updates. Resolution Change the registry key HKEY_LOCAL_MACHINE\SOFTWARE\TAC\TAC Vista Workstation\5.1.X\MaxTGMLFPS  (max TGML frames per second) to 0.

Issue The Xenta 121-FC/HP controller will not build a terminal load when in unoccupied night setup mode. Environment ZBuilder 5.1.6 Xenta 121-FC Xenta 121-HP Cause The “Cooling interlocked to fan” setting prevents the unit from building cooling terminal load in unoccupied mode. Resolution This issue will be corrected in a future upgrade but for now this is a work around. Open ZBuilder Go to the Configuration tab > Control > Fan > Interlock Uncheck the box called “Cooling interlocked to fan”. Click Apply at the bottom of the window to update the settings in the controller.  

Issue Considerations to make when using the economizer function in a Xenta 121. Environment Xenta 121-FC Xenta 121-HP Vista Workstation ZBuilder LonMaker NL220 Cause The economizer / outside air damper function of the Xenta 121 requires that certain considerations be made in order for it to work properly. This includes the wiring and display of a mixed air temperature sensor. Resolution Some things to consider when using the economizer in Xenta 121: The Xenta 121 application requires that a mixed air temperature sensor be used when the economizer mode is set up. This is to keep the application from bringing in too much cold air and freezing a coil. It is not possible to bypass this requirement in the software, but installing a ~1.8K ohm resistor in place of the mixed air temperature sensor will fulfill this requirement. The control method for the economizer can either be selected as Space temperature controlling against cooling setpoint or Mixed air controlling against setpoint value. Even if the space temperature method is selected the application still requires a mixed air temp sensor for safety lockout purposes. By default, the mixed air temperature is not displayed on the front end even if it is being used by the economizer. In order to display the mixed air temperature, navigate to the SNVT menu while on the Configuration tab of ZBuilder. Check the box at the bottom that says nvoGenericTemp. When the cursor is hovered over the text a tool tip pops up and indicates that this is used for displaying the mixed air temp. Next, select the I/O Setup tab and the Mixed Air Temperature point will appear and can now be dragged to the desired point assignment.

Issue Xenta Server Log Error contains the error line: Generic OS: Too Many Semaphores. 5326 02-Dec-2011 12:47:33 AM fatal  undef  httpdd           1      Generic OS: Too many semaphores.   (Error#:8202) Environment Xenta Server System Error Log Xenta 701, 711, 721, 731 Cause An Application in Xenta 700 consumes too many internal semaphores which cause a fatal error resulting in repeated coldstarts. Resolution Corrected in release 5.1.0 and documented on page 6 of TPA-MALR-08-0009.00. Upgrade to Vista version >5.1.0.

Issue Instructions for finding the version of LonMaker and LNS Server on a machine. Environment Echelon LonMaker Cause Knowing the version of LonMaker and LNS are necessary for many troubleshooting techniques. Support representatives may ask you to have this information available in order to assist you better. Resolution Please follow these steps to find the version of LonMaker and LNS server on the machine: Open LonMaker, then pick and completely open a network. Choose the LonMaker menu in the menu bar, then about LonMaker: This is the about LonMaker window that should be shown. As you can see in this screen capture, LonMaker 3.1 is being run with the LNS server version 3.27.

Issue When doing Xenta server to Xenta server communication, via other projects network, a good troubleshooting technique is to determine if the two Xenta servers are truly communicating to one other over TCP-IP. This is possible via the online status of the imported Xenta server in the project tree. Environment Xenta 511, 527, 555, 701, 711, 721, 731, and 913 Cause Two Xenta servers are set up to communicate to one another, but they are not passing data properly. Troubleshooting step number one should be to determine if the two Xenta servers are online to each other on the TCP-IP Resolution To  check the online / offline status of a Xenta server follow these steps: Login to the web browser of the Xenta server that that is configured to receive data. Navigate to the project tree similar to the image below. 3.  Within the project tree, browse down to the Xenta servers and check the online status as shown here:

Issue Cannot select LNS Database in Explorer after Browsing to the desired database. Can click on the LNS Database but it doesn't do anything. Correct way to add LNS Network to an XBuilder Project. Environment XBuilder Xenta Server LNS Network Cause Selecting an LNS network to add to an XBuilder project requires dragging and dropping the LNS network object rather than just clicking it Resolution In the Network pane of XBuilder expand the Xenta 5XX / 7XX / 9XX device to locate the LON port object. Right click the LON port object and select Insert Network from LNS... to open the TAC LNS Explorer. Drag the TAC LNS Explorer window to make the LON port object in the Network pane of XBuilder visible. In the TAC LNS Explorer select the File menu and select Open > Local LNS Networks. (This is assuming that the LNS network is on the local computer.) Identify the desired LNS network and click and drag it from the TAC LNS Explorer to the LON port object in the Network pane of XBuilder. The LNS network will then populate below the LON port object.

Issue Updating a application specific controller with a later firmware version Environment NL220 Cause Enhancements in firmware version need to be implemented into existing controllers of older firmware versions Resolution Here are the steps to download a new APB or NXE file in NL220. Locate the controller you wish to update in NL220. Right mouse click and select "Copy configuration values to memory" Right click on the same controller and select  "Download Program" Browse to the new APB or NXE file you want to download Once the download is complete you can paste the configuration back into the controller. Right click on the controller again and select "Paste configuration value(s) from memory" The controller is now updated with the new application.

Issue This issue has symptoms as below: Blank page, No ID code or number displayed in login webpage and can not login to Xenta Server. Can not access Xenta Server via webpage. The following blank page is displayed: Login page is displayed, but project name and ID code or ID number are not: Environment Windows Server Environment TAC Vista 5.1.X Xenta Server Ver 5.1.X Cause Windows Server "Internet Options" Security Settings are not set properly. Resolution Need add the Xenta Server IP address into "Trusted Sites" in "Internet Options>>Security>>Trusted Sites". If didn't add the IP address into "Trusted Sites", blank page would display; If just "http://%Xenta Server IP address%" is added into the "Trusted Sites", would get login webpage which didn't include project name and ID code in the login page; Need remove "http://%Xenta Server IP address%" from "Trusted Sites", and add "https://%Xenta Server IP address%" into "Trusted Sites" list;   Then could get correct login webpage,  

Issue Is it possible to remove the folder tree and alarm pane from webstation? Environment Vista webstation 5.1.X Cause Certain users have access to graphics and nothing else. It would therefore be better to be able to maximize the graphic resolution and not see the other panes. Resolution The folder View and Alarm View can be removed by editing the DefaultPage.aspx file. The DefaultPage.aspx file can be found in the folder C:\Inetpub\wwwroot\TACVistaWeb51X.

Issue Vista does not allow the user to edit standard graphics. Attempting to edit a standard object will result in the following error: Environment TAC Vista OGC Graphics Cause Vista does not allow the user to edit a standard graphic file within the vista database. A standard graphic is more of a shortcut to the master graphic in the root directory of TAC Vista Resolution Only make edits to the master graphic within the root directory of TAC Vista. This change will automatically be changed to all standard graphics associated to it.

Issue After making changes to Xenta 121 in ZBuilder and clicking OK or Apply an error is returned that says: Error writing to device - Errors occurred while writing to the device. Database and device may not be synchronized. Please download values from database and restart device manually Environment Xenta 121-FC,  Xenta 121-HP Vista Workstation ZBuilder Cause This error can occur if Vista is unable to connect to the Xenta 121 controller. Resolution Ensure that the Xenta 121 controller is powered on and that there is a reliable connection to the controller. To verify that the controller is talking to Vista either right click on the controller in Vista and select properties then click on the Neuron Status tab and check that the state is Configured, online. Alternatively, this can be checked in LonMaker by right clicking the device and selecting Properties and then clicking the Attributes tab. The State should say Configured, Online.

Issue Is it possible to create a switch, in TGML, which has a popup dialog to confirm the action taken (Yes/No)? Environment TGML editor 5.1.X Vista workstation 5.1.X Webstation 5.1.X Cause A customer wishes to confirm changes before applying them, to avoid setting variables by mistake. Resolution In the components library in TGML editor, there is a check box component which has a confirm function. Drag & drop the component onto the workspace and study the code. This can be used as a basis for a switch component.