Building Automation Knowledge Base

Issue Animations, gifs, updating values, hover overs or mouse event scripts work in Workstation but do not work in Webstation. Product Line TAC Vista Environment Vista Webstation TGML graphics   Dynamic values       Cause Various reasons can cause TGML graphics to not function the same in TAC Vista Webstation as in Workstation. Typical reasons can be: Using "Static TGML viewer" vs. "Dynamic TGML viewer". Under Static view, all animations are prohibited. Using unsupported script functions can cause animation to not work in Webstation. Sizes and the number of animated .GIF images used on a single TGML graphic page. Resolution Check if the Webstation is running under Dynamics view. Go to Start->All Programs->Schneider Electric->TAC Vista Web Applications -> Vista Web Setting. (For Vista 5.1.3 or prior, go to Start->All Programs->TAC->TAC Vista Web Applications -> Vista Web Setting instead.) Click on "Graphics/TGML Views" in the left panel. Make sure the TGML View is either “AutoDetect” or “Dynamics” in the right panel.  If it is “Static”, click on the drop down manual and choose a different display viewer.   Check if using any unsupported Java script. Please reference Vista Webstation unsupported TGML functions for more information.   If a TGML graphic page contains many animated GIF images, it can cause the animation on that graphic page to run slow, discontinuously, or not run at all.  The amount of animated GIF images that can be put on one single TGML graphic page various case by case. Therefore, the best way to test it is deleting all animated GIF images and add them back on one by one.

Issue The reason for TAC dummy nodes and the logic behind the number of dummy nodes created. Product Line TAC Vista Environment Vista NL220 LonMaker TAC Vista System Plug-In Cause TAC dummy nodes are added to Xenta groups automatically in the LNS network. The dummies are made after group bindings have been created. Resolution The TAC dummy nodes are created when group bindings are made. For more information about group bindings see Verifying Xenta Group Bindings in an LNS system. Vista requires that the TAC Group and the TAC Xenta group differ in the number of devices. If you only have one Xenta group in your system, TAC Vista System Plug-In will create a dummy device and use its tag_0 (also first row of the address table) in the group binding for the TAC Group. This will allow Vista to differentiate between the TAC and Xenta groups. Notice that in both LonMaker and NL220, this dummy node that is created to represent a second Xenta group appears to be located in the same Xenta Group as the rest of the controllers. This is fine, the system plug-in is not going to create a new group to put it in, just realize why the dummy node is there. Modules do not count in the group bindings therefore the example below only has three devices in Xenta group 1.   Xenta Groups must consist of at least three Xenta devices. If you only have two Xentas in a Xenta group, TAC Vista System Plug-In will also use a dummy device, since a binding between just two devices is not considered a group binding. To create a group binding, a third device is needed. Consequently, you will need two dummy devices if you only have one Xenta in your Xenta group. Thus, if just one Xenta device exists in a single Xenta group, three dummy devices will be needed: one to separate the TAC group binding from the Xenta group binding and two more to form a Xenta group.

Issue Error messages appear in graphics that have worked in previous versions. Environment TAC Vista TGML graphics editor/ workstation graphics 5.1.8 and newer Cause There are a number of changes made in TGML in version 5.1.8, but one of the changes in the way we handle scripts being run when in a graphic when a link is invoked may cause errors.  Resolution One of the commonly used menu-components invokes a link via a script within a script. Previously the scripts remained in the cache memory and all running functions were completed, but in 5.1.8 the cache is emptied as soon as a new graphic is invoked. In this case evt.stopPropagation() should be used to terminate any scripts that could potentially run after invoking a link, for example when using nested scripts. A fix has been posted on the Graphics Exchange that addresses this issue. This is not an official Schneider Electric fix and Schneider Electric takes no responsibility for issues arising from it's use (Go to Community Post).

Issue The Vista administrator user account (system manager) is created; however, that account does not have administrator rights such as add/edit/delete any user, cannot change time schedules, graphics, etc. Product Line TAC Vista Environment TAC Vista Workstation 5 Cause When adding a system manager account in Vista, that account also needs to be added into the administrator group ($Administrators). If the system manager account is not listed under the administrator group, it will not be able to behave as the administrator. Resolution Maker sure the user account is set as a “System manager” Log into Workstation as an administrator and click on the root project folder in the left panel, right click on the user account in the right panel, and then select property. Under “General/Authority level”, it should say “System manager”. If not, change to “System manager”.                             NOTE: If the textbox is grayed out, it means the current logged in account does not have the permission to make changes to that user account. Please read Cannot edit or delete a user account in TAC Workstation to add the control rights. If this articele fails also, please go to step 2.   Click on the root project folder in the left panel, and right click on the “$Administrators” in the right panel, then select “Properties”. Under “Users”, all administrators should be listed here. Make sure the desired user account name is listed. If not, use “Add” function to add the user account. If the text box is grayed out, log in as one of the system manager account listed under “Users” to process this step.                  NOTE: If all system managers listed under “Users” are no longer available. Please contact product support to unlock the database.

Issue Unless the correct format is used when defining a dongle as locking property in https://schneider-electric.flexnetoperations.com web site when activating license, the license will not work. Product Line TAC Vista Environment Vista 5.x Cause Defining a dongle as locking property in schneider-electric.flexnetoperations.com web site when activating license. Resolution It is important that the format is entered in the following format: TAC_HL_ID=1234567890. If the "TAC_HL_ID=" part is not entered, it will not work, and you will need to rehost the licenses again, this time using the correct format as stated above. Complete instructions can be found in Rehosting a Vista 5 License on the FlexNet License Server.

Issue If there are already TAC Xenta 104-A devices commissioned in an LNS database, then it may not be possible to add TAC Xenta 104-A controllers of different system versions into the same database. Nor is it possible to do a replace. Certain firmware versions of the 104-A controller are not compatible with one another. Trying to add a different system version to an existing database will produce an interface does not match error. For more information on this error, see The new program interface does not match the previously defined program interface. (Subsystem: NS, #59). Product Line TAC Vista Environment NL220 LonMaker Vista Cause The incompatibility between different system versions of the TAC Xenta 104-A controller is due to a change that was made in the size of the SNVT declaration area residing in the device memory. The change in device memory occurred between version 1.10 and 1.20. For the same Program ID, LNS requires this size to be the same as previously commissioned devices. Resolution The first action that should be taken is to update the LNS network to the most recent version. It has been confirmed that newer LNS versions have addressed this issue so that no further action is required. With newer LNS software, different version types of the TAC Xenta 104-A may be added to the same database.  If upgrading the LNS software is not an option, the firmware in the controllers can be upgraded as a work around to correct the issue. In order for a TAC Xenta 104-A controller with version 1.10 to reside in the same database as version 1.20, the 1.20 controller must be upgraded to version 1.20A. In similar fashion, version 1.21 must be upgraded to version 1.21A to coincide with version 1.10. To add a 104-A controller with version 1.21 to a database with version 1.20 already on it, no further action need be taken. Version 1.20 and 1.21 are compatible. It is important to reference the compatibility matrix found below. Changing the firmware to an "A" version will then make the controller incompatible with versions 1.20 and 1.21. Also note that it is not possible to upgrade from system version 1.10 to 1.20/1.21 due to the memory configuration. The modified "A" versions will not be loaded into the controllers from the factory. These NXE/APB files will only be available on the Buildings Business Extranet. To download the NXE/APB file for v1.20A or v1.21A, go to The Exchange Download Center. Perform a search for TAC Xenta 104-A Firmware. The 1.20A version will be labeled "TAC Xenta 104-A Version 1.20 (78 Kb)" and the 1.21A version will be labeled "TAC Xenta 104-A Version 1.21A (45 Kb)".

Issue Necessary Accounts for DCOM and Firewall Security Settings. Product Line TAC Vista Environment TAC Vista Webstation TAC Vista Remote Workstation DCOM Configuration Cause DCOM Parameters must be set to allow for remote connectivity to the Vista Server. Resolution You will notice in the "Security Settings for MS Windows XP SP2 and MS Windows Server 2003 SP1" instructions that several changes are needed for the accounts "ANONYMOUS LOGON" and "Everyone". If these accounts do not exist, they must be created and set to allow local launch and remote activation permissions. See also Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET for an automatic DCOM utility.

Issue Error message "Invalid Object Name" Error message "Failed to transfer application file to TAC Vista"   Product Line TAC Vista Environment LonMaker NL220 Menta TAC Vista System Plug-In Cause Error message "Invalid Object Name" appears when browsing in a Menta file in TAC Vista. Add it via the System Plug-in results in an error saying "Failed to transfer application file to TAC Vista"  Resolution This could have different causes. There could be a signal name that is to long (longer than 20 characters). The problem can also be that there is an ALARM that have an alarm controller object defined that are using a $ (other than the default $Alr_Cntrl). TAC Vista will try to add the object and you are not allowed to add objects with $ in them. For more help see "Update Vista database failed" Error in Vista System Plug-In.

Issue When adding points to your OPC Client from a Schneider Electric Vista OPC Server that contains points from Xenta Servers error "The item definition does not conform to the server syntax". Product Line TAC Vista Environment Vista 5.x Vista OPC Server 1.6.x Xenta Server 511-B, 731, 527, 913 Cause There are certain characters that are invalid in an OPC Server environment which are allowed in the Vista Server database. Invalid names include I/NET, RS232/485 A, and TCP/IP. Resolution Create a folder in the Vista database and create shortcuts for the points that are suffering this problem. This avoids any invalid characters, but grants full functionality for the data in question. For more OPC Server issues please see Vista OPC Server Installation and Known Issues.

Issue When a specific application request exceeds the standard capability of I/NET it is sometimes possible to use XBuilder to expand possible applications. Product Line TAC INET, TAC Vista Environment I/NET XBuilder I/NET Host Tool Cause When a specific application request exceeds the standard capability of I/NET it is sometimes possible to use XBuilder to expand possible applications. Resolution This is a sample access control application to demonstrate the possibility. Minimum requirements for this are :Xenta 527 Web Server. If you wish to use Menta Programming, use a Xenta 731 or Xenta 913. Application: Customer Requests an Audible Buzzer be triggered when a door is forced open, but not shut off until the alarm has been acknowledged. Create a DO point to controller your buzzer/light/alarm indicator (buzzer DO) Create an internal AO point to function as a translator (logic AO) Add a Calc to the buzzer DO: ~(P0=C0) where P0 is the logic AO and C0 is 80 Perform a Station save In XBuilder, create a project for the 527 Web Server Insert or re-insert the I/NET network Add a connection object Drag the Flags attribute of the Doors DO point to the "from" part of the connection object Drag the Value attribute of the logic AO point to the "to part of the connection object Generate the Project and Send to Target. The response time of the buzzer coming on or going off is dependent on the Scan interval of the buzzer DO.  The reason it works is that the flag attribute of the Door point will equal exactly 80 if you have an alarm flag and the point is still in alarm (the alarm has a value of 64 and unack has a value of 16 totaling 80. See Decoding the I/NET signal "flags" attribute for more information). The door point will stay in alarm until it is acknowledged so this will stay at 80 until someone acknowledges the alarm, or puts the point in Manual/Test.  The Buzzer will not activate if the point is in Manual or Test The above solution will trigger off any alarm specified from the door editor (Door Open To Long, Door Forced, Bad Card read, etc).  Turn off the other possible alarms, or create an addition internal point labeled Door Forced.  The Door DO point can trigger an event sequence based on Forced door to control the additional point. If you do this the calc will need to be modified to ~((P0=C0)|(P0=C1)|(P0=C2))  C0=16 C1-64 C2=80. This will allow for the buzzer to be on until the point has been acknowledged and return to normal

Issue Commission and Download command from Vista Workstation on a controller/network beneath a Xenta 911 communication port results in "Error: Failed to connect to TAC Xenta 911 - Invalid User/Password" Product Line TAC Vista Environment Vista Classic Network Communication Port - Xenta 911 Xenta 511/911 Cause Vista port properties has User name and Password stored.  If the user name or password are changed in the controller, these changes must be made to the Vista server settings as well. Resolution Obtain the most current user name and password for the Xenta hardware device If the password is not known and cannot be obtained, a temporary password can be assigned.  Please see Receive a temporary session password for a Xenta 5/7/9xx if the password has been lost. Right-click on the Xenta 911 communication port and select Properties Enter the new user name and password under TCP/IP settings Attempt the Commission and Download command again.

Issue Where can I obtain the technical information, manuals, guides or other documents on Continuum? (or other product lines) Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Continuum Cause Manuals and documentation can be used for training or self-help troubleshooting for Continuum. (or other product lines) Resolution Review the course notes The notes and document gathered during training can be very useful and a great source of information. Technical Documentation is available on the EcoBuilding Download site at: https://ecobuilding.schneider-electric.com/ For technical data/PDFs installed with Continuum, Go to Start > All Programs > Continuum > Documentation The discs and downloaded zip files that are used to install Continuum also include technical PDFs. Some of these are installed when Continuum is installed. (CONTINUUM) Most of the online help is context based, thus if you click help within a InfinityNumeric, then InfinityNumeric help is given. This help file can also be searched in the normal way. It is an excellent source of information. (CONTINUUM) Bookmark this Knowledge Base:  https://community.se.com/t5/Knowledge-Base/tkb-p/knowledge-base_public New articles are added daily and should be used as a first stop for self help. The Exchange Community site has a community space just for Continuum, SmartStuxure, Sigma, Vista etc.  for posing questions, sharing solutions, https://community.se.com/ (CONTINUUM) The Continuum catalogue also provides a good overview of the product range Some documentation is freely accessible, see https://www.schneider-electric.com/en/work/products/building-automation-and-control.jsp If an end user has problems on site, they should first contact Schneider Electric local support or service department (In the UK contact Support Bureau 0870 606 2800, cs.bureau@uk.schneider-electric.com) SmartStruxure For Building Operation help can be found online at: http://help.sbo.schneider-electric.com/home/index.castle?locale=en-US&productversion=1.8   CONTINUUM ONLY Always ensure the site fits within the Continuum Compatibility Matrix, this includes:  For PC requirements see the relevant Installation Instructions included with the Continuum Software Controller firmware (Continuum, BACnet, Infinet), use the most up to date available (of the correct version) Workstation operating systems, service packs and .NET framework versions SQL versions See Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation for other system data The Continuum.chm file found in the Continuum directory include the "online help" It is usually worth ensuring the latest Continuum service pack is applied to ALL workstations on site (Cyberstation and WebClient) Click Here

Issue The STR-250 will not respond to any input and the display is incorrect, typically flashing random characters or 00. During this behavior the Xenta 102-AX will remain offline and unresponsive, no longer controlling room temperature. Product Line TAC Vista Environment Xenta 102-AX STR-250 Cause A firmware error has been identified in the TAC Xenta 102-AX (and 102-AX-U8) version 2.14, when they are used together with STR-250, the LCD version of STAT. A certain sequence of key strokes will cause the Xenta 102-AX to lock up. A firmware upgrade is available. Until that has been downloaded a power cycle will in most cases recover the controller. See the full TPA-MALR-10-0004.00. Resolution The 102-AX Firmware error is fixed in version 2.16 and later. Instructions on how to properly upgrade the 102-AX are located here: Upgrading a Xenta 102-AX to version 2.16 or later

Issue During Vista Installation, receive error message “SQL server service cannot be started” or "Failed to start SQL Server service!". Product Line TAC Vista Environment TAC Vista 5.X.X (Tested on Windows XP SP3 with SQL server 2005 EXPRESS) Cause This issue typically happens after uninstall an earlier version of Vista, and then install a newer version of Vista with the built in SQL server (SQL server 2005 express). Sometimes the SQL server registry key is remained on the computer during the uninstall process. When new installation happens, Vista thinks there is an existing SQL sever; however a failure will occur when try to start the SQL Server service. Resolution It is recommended to use the installation file to uninstall TAC Vista 5.X.X. Follow How to uninstall and completely remove TAC Vista 5 to make sure all files and folders are removed.   Check if SQL Server Service still exists: Right click on “My Computer” and choose “Manage”. Chose “Services and Applications" -> "Services". Check if “SQL Server (TACVISTA)” is listed, if yes, go to next step. Otherwise, restart the computer then run the installation again, issue should be solved now.    Go to “start->Run->regedit” to open “Registry Editor”.   Go to “HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/”. Find “MSSQL$TACVISTA” and “MSSQLServerADHelper”. Then delete both registry folders.   Repeat step 4 for “CurrentControlSet001” and “CurrentControlSet003” under “HKEY_LOCAL_MACHINE/SYSTEM/.   Restart computer and run the installation again. Issue should be solved now.

Issue The B0cfglog.txt file located in the Vista database $log folder and Alarms in Vista are getting the error: Physical unit "Unit Name" on node "Node Name" is a duplicate by uid=### with "Unit Name" on node "Node Name" Product Line TAC Vista Environment Noded Vista Server Master / Slave Vista Cause Conflicting UID in a Master/Slave node network. Master Vista Server or Master. In a Vista network/system containing several Vista Servers, one of the Vista Servers is the Master Vista Server, managing and communicating system-specific information and global settings throughout the Vista network/system. Slave Vista Server or Slave. The Slave Vista Servers in a Vista system receive system-specific information and global settings from the Master in the Vista network/system. If once standalone servers are all added to one Master network, the Master assigns a unique ID to each slave. Normally when a UID gets duplicated the master tells the servers correct the duplication. Sometimes this automated fix cannot occur because the duplication prevents the proper communication. In this case, the slaves need to re-establish communication with each other and be restarted. Resolution Delete the slaved node Update Vista to reflect the node is removed Adding the node back Restart Vista Server The UID should be resolved and the error should not be present.  If the error still comes up please try the following steps: Make current backups of all Vista Databases Close the slave server Open the mater server When asked, "Do you want to change identities on this node?" select Yes Close the master server and reopen both the mater and the salve server and the error should be gone Instructions on how to add the Vista Slave node onto the master can be found in Creating TAC Vista multi-server network. For this to work, the slaves need to be able to see each other as well. If you do not want the slaves to see each other, add them while balancing the load on the network. They can later be removed when the problem is not occurring anymore. 

Issue "No license available" message appears some while after having logged in to Webstation. Product Line TAC Vista Environment Vista 5.1.6 Windows 2008 Server Internet Information Services (IIS) IIS 7.0 or higher Cause This is most likely due to a corrupt IIS installation. Resolution Reinstall IIS Reinstall Webstation The steps for this are outlined in Problems installing Vista Webstation 5.1.5 or newer.

Issue If a Xenta I/O module has experienced a hardware failure it may be necessary to replace it with a new controller. Product Line TAC Vista Environment Xenta I/O Modules Xenta 411, 421, 422, 422A, 452, 452A, 471, 491 Cause Hardware failure of a Xenta I/O module requires it to be replaced. Resolution Physically replace the I/O module The next steps depend on whether the I/O module is part of an LNS system or a Vista Classic Network. LNS System Right click on the I/O module in the LNS management tool (LonMaker or NL220) Select Replace Service pin or manually enter the new neuron ID Open Vista System Plug-in Update the TAC Network Update the Vista database Download the base programmable controller Vista Classic Network Go to How to set the neuron ID of an I/O Module in a Vista classic network for instructions on setting the neuron ID for the new I/O module. Service pin or manually enter the new neuron ID Download the base programmable controller

Issue Xenta server trend logs are mixed up or missing when logged to SQL. For example log a from Xenta server 1 is logged under log a in Xenta server 2. This causes duplicates for some logs and missing logs for others. Product Line TAC Vista Environment Vista 5.1.X Xenta server 5.1.X with trendlogs that are retrieved by Vista and logged to SQL. Cause When creating the Xenta servers, copy/paste has been used in Vista. Using copy/paste causes certain references to be created incorrectly. Resolution !If you have already encountered the behaviour described contact Product Support! Otherwise read on... The correct way to engineer Xenta servers in Vista when the XBuilder project is to be reused. Right-click on the server object in Vista and select New->Xenta Server X5\7\9xx Right-click the newly created Xenta server and select Edit In the XBuilder project that opens, configure and download your project to the Xenta server. Close the XBuilder and save the changes to the current project when prompted. Refresh Vista and ensure that everything is online and correct in the Xenta server. To reuse this project in another Xenta server Right-click the Xenta server in Vista and select Edit. Make the appropriate changes to the project e.g. change the IP address. You can now either save the project as a template or choose Save as from the file menu. Rename the file and save it. After saving, select the menu item Vista Database->Save As and navigate to the Vista server object in the dialogue that opens. Right-click in the dialogue window and select New->Xenta Server X5\7\9xx. Choose an appropriate name and then click on Select. Go to Vista workstation and update the server object. The new Xenta server should now appear. Now it has been created it can be edited further and then downloaded to via XBuilder.   Note: If the trend log values are mixed up also in the Xenta Server itself (i.e. in a trend log page) it may be a different issue, see Trend log values from M-bus meters under a Xenta Server are mixed up.

Issue When the need arises to change object paths in OGC graphics the Vista reference changer does not work. Product Line TAC Vista Environment Vista 5.x.x Cause For unknown reasons the reference changer does not seem to work well on all OGC databases. Resolution The first thing to try is to edit the OGC after an attempt has been made with the reference changer. If the links have been updated saving the OGC back to the Vista database can sometimes work. If this did not work you can use the reference changer in the OGC editor. Graphics binding were broken after a Vista upgrade to 4.5 from an earlier version is a link on that process.

Issue Site License is not working after upgrading to Vista 5.1.4 or newer. Product Line TAC Vista Environment Vista License Cause The path to the License Server (lmgrd.exe) and License File (Licensename.lic) is incorrect because the default Vista installation folder changed from TAC in 5.1.3 and older to Schneider Electric 5.1.4 and newer. Resolution Stop and close TAC Vista Server, Workstation, etc. Open the LMTOOLS utility from the Start menu: All Programs/Schneider Electric/TAC Tools 5.x.x/LMTOOLS Under "Config Services Tab", ensure the path to licenses file is correct ,C:/Program Files/Schneider Electric/License. Under "Start/Stop/Reread" tab, check "Force Server Shutdown" box. In order click, "Stop Server", "Start Server", "Reread License File". You should receive a message stating the Reread License File Completed. Start any TAC application other than Vista Server (for example: TAC Menta). You will be prompted to "Specify the License Server System" or "Specify the License File". Select "Specify the License Server System" and enter the computer name. Alternatively, If the License Server resides on the local machine, you may type "localhost" as the computer name. If the above is unsuccessful, follow the full steps in the resolution of TAC Vista 5.0 to 5.1.7 license does not work after installation which will also correct the path name to Schneider Electric.