Building Automation Knowledge Base

Issue Where is the I/NET Host Tool located? Environment All versions of I/NET Cause Unable to get the Host Tool to download for a system that has a valid CD and Key. Resolution The Host Tool is located on the original CD or could be downloaded from The Exchange Download Center . If it is not there then follow these steps if a CD with the required version is available: Place the CD into the PC and open up Windows Explorer Browse the CD and  go into the Support Folder Open up the Host Tool folder and in there is a Host Tool file Download it on the PC and execute it to install the Host Tool.

Issue Is IPv6 supported with I/Net and SE Vista Controllers? Environment NPR2000 Xenta 527-NPR, 527, 731, 913 Cause IPv6 with I/NET and Vista Controllers Resolution  I/NET and Vista Controllers DO NOT support IPv6

Issue Average space temperature on TAC Xenta 120 devices. Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Xenta 121-FC TAC Xenta 121-HP Cause TAC Xenta 121 is able to average space temperatures from multiple sensors. For example, it could average two room units, or one room unit and one Lon sensor. It is possible to average up to three different Lon sensors. Resolution Bind a valid temperature SNVT value to the input nviSpaceTemp. The TAC Xenta 120 device will calculate the average between the bound input and the physical sensor.

Issue When accessing the Webstation/Screenmate website a 404 Page not found error message is returned. Environment Windows Server 2003 Vista 5.x.x Cause The ASP.NET technology is currently prohibited on the Web Server. Resolution Open the Windows Control Panel Click the Administrative Tools Click Internet Information Services (IIS) Manager Expand the local computer Click Web Service Extensions Ensure that ASP.NET v 1.1.4322, ASP.NET v 2.0.50727, and ASP.NET v 4.0.30319 are allowed (Possible that only version 2.0.50727 is listed) Version 4.0.30319 is required for Vista versions 5.1.5 or higher.

Issue User account with read rights have admin access to all Xenta web pages webserver access thru Vista Environment Vista Xenta   Cause When the default settings are used, all users in TAC Vista Workstation have full access to all pages in Xenta Server regardless of their rights in Vista. This is due to the fact that the Vista Workstation user uses the root account to access Xenta Server. The root account always has full permissions to objects in Xenta Server. Resolution Enable Enhanced Xenta Server web access Under Vista server right click on $system object and choose properties (Need to have admin rights) Enable "Enhanced Xenta Server web access" Click ok and log in the user that should only have read rights.

Issue Values are not updating in a specific TGML graphic in webstation. Red x on all values in a TGML graphic, other graphics working fine. Crossed out values in TGML graphic. String value (text) with " in the text not displaying Product Line TAC Vista Environment TAC Vista 5.1.6 TAC Webstation 5.1.6 Cause If there is a string value (text value) in the graphic with the a double quote quotation mark (") in the text, all signals stop updating on that graphic. Resolution Make sure there are no " in any string on the graphic.

Issue When editing a Xenta Server from Vista, an old version of the XBuilder project will open and you will be asked to convert it. Environment TAC Vista TAC Xbuilder Cause Under some circumstances, after upgrading a Xbuilder project the old xbp file will still remain in the project folder. When one does Edit in Vista Workstation the XB project is unpacked in a Windows user temp folder. After that XB searches for *.xbp files and take the first one found to open. If you for example have converted a 5.1.5 project to 5.1.6, there may be both a .xbp515 file and a xbp516 file. It is  the old one (.xbp515) that will be opened, since it's alphabetically first.   Update: In v5.1.7 and later, Xbuilder will always open the latest version of the project. Note that it will go for the latest file extension (xbpXXX) and not by the date of the files. Resolution Find the zip fie associated with the Xbuilder project, for example C9F20001.zip located in the db\$thisfil, and extract it to a temporary folder. Once extracted delete or rename the old xbp file (project.xbp515 in the example above). Zip the folder that has all the previous project version removed back to db\$thisfil folder using the same name, overwriting the old one.   Update: In v5.1.7 and later, Xbuilder will always open the latest version of the project. Note that it will go for the latest file extension (xbpXXX) and not by the date of the files.

Issue Even though Windows Server 2008 R2 is exclusively a 64-bit operating system, 32-bit applications are supported by enabling the WoW64 optional feature. NOTE: These are general instructions for utilizing the WoW64 function. Not all Schneider Software will be able to run in an emulated environment. If uncertain, please check with Product Support Services to ensure proper installation. Product Line Andover Continuum, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC INET, TAC Vista Environment Windows Server 2008 R2 WoW64 feature. All 64bit OS Cause If the WoW64 feature is not enabled and you try to run a 32-bit application, the application will fail to execute. WoW64 option in in undesired state. Resolution If the WoW64 feature is not enabled and you try to run a 32-bit application, the application will fail to execute. The WoW64 execution layer is an optional component that is installed by default on R2 releases. You can save resources by removing the feature if you are not going to be running 32-bit applications on your Server Core install. Install the WoW64 Execution Layer using the following command: dism /online /enable-feature /featurename:ServerCore-WOW64 If your solution has a .NET 32-bit dependency, then also invoke the following sequence: dism /online /enable-feature /featurename:NetFx2-ServerCore dism /online /enable-feature /featurename:NetFx2-ServerCore-WOW64 Note: In Windows Server 2008 R2 RC1, WoW64 is enabled by default. If you don't want WoW64 enabled, just disable the feature as follows:  dism /online /disable-feature /featurename:ServerCore-WOW64

Issue Is a Menta License required in order to program  the Menta in a Xenta 711? Environment 711 Vista Menta licensing Cause Licensing is unlocked from the factory for "711 Menta." Resolution No License is necessary.

Issue How to create a local String Variable in a Xenta 731. Data Type String is not allowed in this node. When trying to set data type to string. Environment TAC Xbuilder Cause The datatype string can only be used for SNVT str_asc and signals connected to SNVTs of this type. Resolution To get a String signal you have to use snvt_str_asc.

Issue Generating a Xbuilder project results in the error message "The size of the generated project is xxxx KB, which exceeds the maximum size 8192 KB". Environment Xbuilder 5.x.x Cause The generated project size exceeds the maximum limit due to the following reasons: The project contents made up of graphic pages, inserted networks (LON, I/NET, etc), large images (BMP, GIF, etc), or imported files in the UserTargetImage directory cause the project to exceed the limit. The option "Send Project backup file to target device" is checked and this causes pushes the project size over the limit. Resolution Generate the Xbuilder project to see how far above the limit the project currently is. Open the Project\Settings and uncheck the "Send Project backup file to target device" and regenerate the project to see the difference in file size. If the size difference is significant then check for large files in the project directory that should not be sent to the device such as project or device documentation files such as PDFs. Remove these files from the Xbuilder project directory and generate the project again.  Search the Xbuilder project directory for the largest size files such as graphic pages and try to find way to reduce the size by converting background image formats that will result in smaller file sizes. Example convert BMP file to PNG or JPG format.

Issue Xenta 913 will not communicate with the Bacnet device. Wireshark does not show any packets between 913 and Bacnet device Environment Xenta 913 Cause The Xenta 913 has been installed on a TCP/IP network with a switch between the Xenta 913 and Bacnet device. Resolution A basic switch does not pass broadcast messages that a Xenta 913 uses to talk to Bacnet device. The solution to this issue is to replace the switch with a Hub or use a managed switch. If a managed switch is used it will need to be configured to pass broadcast messages from the Xenta 913 to the Bacnet device.

Issue The Values column in the Vista Workstation Object View shows a blank field against a SNVT Switch (or any other structured SNVT) Environment TAC Vista Workstation Cause The TAC Vista Workstation Object View displays a single row for each public variable in a selected folder or device and a single Values column.  For a structured SNVT such as a Switch this means that there is no space to display all the SNVT member values.  Vista solves this problem by not displaying any of the SNVT members. Resolution Open a Status Watch pane in Workstation. Drag the structured SNVT from the Object View on to the Status Watch. In the Property column, select the Property you want to view (in the case of a SNVT Switch either 'Value' or 'State'). N.B.  Vista will not allow you to enter the same SNVT twice in the Status Watch, so you cannot view both members simultaneously.   Alternatively,  display the SNVT on a graphic.  The binding selection dialog allows you to choose which Property of the SNVT to display.  There is no problem with displaying as many properties of the same SNVT as you wish on a graphic.

Issue Get alarm the "Filename too long for backup" in TAC Vista Workstation. What is wrong? Environment TAC Vista 4.2.5 Cause The too long filename is from one of the debug logs in the $log folder in Vistas database. Resolution Make sure no debug log is started, open the Vista server, Log-Comm. Log, nothing should be active or marked. Delete or copy to another folder the logs in the $log folder.

Issue Fail to install Java 1.5 or greater on the OP1500 Error "low on virtual memory" and "error code 1722" during install Environment OP1500 Cause The OP1500 comes in two versions, with 0.5 GB and 1 GB memory. Java v1.5 or greater requires the 1 GB version. To determine which version you have refer to the Schneider Electric label on the side of the OP1500: SE part number of the 0.5 GB version: MPC ST52 NDJ00T SE part number of the 1 GB version: MPC ST52 NDJ10T If you do have the 1 GB version, it may be an install shield error (described here ) Resolution If you have the older OP 1500 with 0.5 GB I it may still be possible to order a 1 GB memory card upgraded with Java version 1.5 from Schneider Electric Sales/Order. If you have the 1 GB version, you can try download the offline installation package, available here.

Issue All the alarms in Vista come to alarm receiver which are not wanted. For example, the system alarms are not wanted to be received by Alarm Receiver. Environment Vista Cause The possible cause is that the alarm control is not defined in Menta or Workstation. Resolution For Menta alarm blocks that do not have an alarm control object assigned to them or Menta alarm blocks that references a non-existing alarm control object in TAC Vista, the alarms are sent to the default alarm control object, $Alr_Cntrl. Define the specific alarm control in Menta or Workstation. Then only specific alarms will come to alarm receiver. Refer to the Chapter 18 of the TAC Vista Technical Manual.

Issue When disconnecting the IP cable to a 911 which  act as a RSPD the RPUs goes offline, when connecting it again the RPUs stay offline.   Environment Vista 5.1.6 Xenta 911 as RSPD, PLB and RPU 6751 Cause The PLB object in the Vista database have somehow become corrupt. Resolution When creating new PLB objects and move the RPUs to that new object it works like it should.

Issue In an old TAC Menta file, STATE members of SNVT_Switch inputs and outputs are assigned to DI/DO blocks. When editing existing SNVT_Switch I/O blocks, or adding a new one, it is not possible to select the STATE member from the drop-down list because the list is empty. Environment TAC Menta version 4.20 or higher Cause An application made in a version of Menta earlier than 4.20 would have had the STATE member of a SNVT-Switch declared as a digital input/output. From TAC Menta version 4.20, both the STATE and VALUE members of the SNVT_Switch are declared as analog input/output. Resolution Applications made with earlier versions of TAC Menta can still be downloaded with the latest TAC Menta version and will work correctly, provided you do not open the DI/DO block containing the SNVT_Switch member STATE and then exit the block dialog with the OK button. If this occurs: Delete this DI/DO block Recreate the SNVT_Switch STATE using a AI/AO block instead See TPI C-89-1-F5 for full details of this issue

Issue After installing Vista successfully, Vista Server starts, but an error message occurs when starting Vista Workstation: Application Error: The application failed to initialize properly (0xc000007b). Click on OK to terminate the application. Environment Vista Workstation Windows XP Professional (tested with) Cause Some other software or driver installed on the computer caused Microsoft .NET Framework error. Resolution Download an IExpress setup file named dotnetfx from Microsoft website and install the file. Restart the computer and reinstall TAC Vista Server and Workstation, the issue should be solved.

Issue What options exists for redundancy and hot swap support for TAC Vista Server front end. Environment Vista 5.x.x Cause There is no direct support for redundancy in a Vista system. The software is designed to only allow a single Vista Server to receive alarms and trends from a field bus. If multiple Vista Servers are trying to access the same system the reliability of the data will be compromised. To use any true redundancy of fail safe conditions 3rd party solutions must be designed. Resolution Without 3rd party tools Ensure that the SQL database is on a full version of SQL server on another computer. Use standard SQL tools to provide reliability and data integrity of the SQL database. Make regular backups and provide a process to restore these backups on a duplicate computer when a problem is encountered. Only one of the two Vista Servers should be running at one time. With 3rd party tools Use software/hardware packages that provide duplicate equipment for fail safe and high availability environments. One such option is Marathon HA & FTsolution (http://www.marathontechnologies.com/index.html)