Building Automation Knowledge Base

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 StruxureWare Building Operation Extended trend logs have an incorrect unit associated with the measured value. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.3.x Cause It is possible to create extended trend logs by selecting multiple trend logs and using the right click option to create extended trend logs. The software incorrectly associates all of the created trend logs with the first trend log object's associated unit even if the other trend logs in the selection use different units. Resolution The cause of the problem is resolved in a forthcoming release (1.4.0) however if the system is in the state currently additional steps must be taken. The method to resolve this problem depends on the need to maintain the existing extended trend log data or not. 1. Accept loss of data Delete the extended trend logs that have incorrect units and create each extended trend log individually and avoid multiple selections. 2. Avoid loss of data Export the trend logs in StruxureWare Workstation. Modify the export file and edit the unit value for the Extended trend log The unit will need to be validated with another export that contains an object of the correct unit type. Example of Units % - 0x200001 F - 0x280003 no unit - 0x10001 inH20 - 0x230005 ppm - 0x200002 kW - 0x3210001 Import the modified file and when it detects a naming conflict allow it to rename the Trend log with a "2" notification. Stop the data collection on the original trend logs and once the retention levels of the new trend logs meets your site requirements delete the old trend logs with the incorrect data. Please be aware this issue could impact meter reports from WebReports detailed in Energy Reports not working in 1.3 and earlier

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 Upgrading from older Continuum version using parallel dongle. Product Line Andover Continuum Environment CyberStation Cause The old style hardware key cannot be attached to newer machine that do not have a parallel port. Resolution It is not necessary to have a hardware key plugged into Continuum workstation pc when the c2v file is created.   If you are able to read the key information and/or identify the serial number for the existing key, contact the EcoBuilding upgrade department at Upgrades.Continuum@schneider-electric.com and provide them with the serial number of the hardware key and a c2v file that was generated on the Continuum workstation. If you are unable to read the key information or identify the S/N from the old dongle, contact the EcoBuilding upgrade department at Upgrades.Continuum@schneider-electric.com. It may become necessary to sent the hardware key to the EcoBuilding Upgrade Dept to so that they can extract the serial number and key information themselves.   See also Software Licensing for Continuum 2.0 and StruxureWare Solution.

Issue When deploying Automation Server or Enterprise Server from Workstation for Projects under PCS, it will fail. The error shown in the Progress view window is "The live server is not empty." Product Line EcoStruxure Building Operation Environment SmartStruxure Project Configuration Server Workstation for Projects Enterprise Server (ES) Automation Server (AS) Cause A project can only be deployed to a server when the server has an empty database and not has been part of a multi-server system. A server is considered empty when it does not contain any user-created objects, such as programs and graphics. Resolution The server database can be emptied in different ways depending on if it is an Automation Server or an Enterprise Server: Reinstall the Enterprise Server. Upgrade the Automation Server with a new database. For more detail about how to deploy AS or ES, refer to Offline Engineering with Project Configuration Server (PCS).

Issue What does it mean on an MNL-800 if both the top green LED (Transmit) and the Amber LED (Receive) are on continuously? Product Line TAC IA Series Environment MNL-50 MNL-100 MNL-200 MNL-800 MNL-V1R MNL-V2R MNL-V3R Cause LEDs indicate LON traffic on the trunk Resolution For an explanation of the Transmit (Green LED) and Receive (Red LED) see F-26724, MNL-800 Installation Instructions, Table 1 LED Indications: LED Operation Status Green ON Normally ON indicating controller is powered and not actively transmitting data on the LON. Flashes OFF Flashes OFF while actively transmitting data on the LON. Amber OFF Normally OFF unless actively receiving data from the LON. Flashes ON Flashes ON while actively receiving data from the LON. Red OFF  (Neuron - normal communications) indicates the Neuron is operating properly allowing normal communications to and from the HVAC application. OFF  (Neuron - Offline) Neuron responds to network management messages only. In this state, communication to and from the HVAC application is not possible. To correct, place the Neuron online by downloading an application using WP Tech or configure using a third party management tool. Blinking The service LED blinks at 0.5 Hz rate (1 second ON, 1 second OFF) to indicate that the Neuron is unconfigured (i.e. communications parameters not loaded). Corrective action: Configure the Neuron by downloading an application using the Work Place Technician's Tool or configure the neuron using a third party management tool. ON Indicates Neuron is not operating properly. Replace controller.  Heartbeat (Green LED) Blinking (Normal Operation) The heartbeat LED blinks at 0.5 second ON, 0.5 second OFF to indicate controller is operating properly. Wink Mode Wink mode provides a visual means for identifying the controller using WP Tech or third party management tool. During wink, the heartbeat LED blinks as follows: With revision 1.x firmware: 2 seconds ON, 0.5 seconds OFF; cycles five times for a total of 12.5 seconds of wink time. With revision 2.x (or later) firmware: 3 seconds ON, 1 second OFF; cycles three times for a total of 12 seconds wink time. Diagnostic Blink (RAM/ROM Failure) The heartbeat LED repeats a pattern of 2 quick flashes followed by pause. To correct, turn power OFF then ON. Replace controller if necessary. Diagnostic Blink (ROM Failure) The heartbeat LED repeats a pattern of three quick flashes followed by a pause. To correct, turn power OFF then ON. Replace controller if necessary. Diagnostic Blink  (RAM Failure) The heartbeat LED repeats a pattern of four quick flashes followed by a pause. To correct, turn power OFF then ON. Replace controller if necessary. OFF Indicates controller is not operating properly. Check power. Replace controller if necessary.      If the amber LED is blinking fast enough, it appears to be ON continuously, so it is receiving data at a high frequency. The other MNL devices on the same LON should all be behaving the same way, indicating a lot of LON traffic. Confirm with a LON protocol analyzer. If excessive LON communications traffic is suspected, see How can LON communications be throttled in MNL-800 controllers? for a method of throttling LON traffic.

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 Satchwell “AL..S” series Spring Return Linear Actuator requires replacement Product Line Field Devices Environment Satchwell “AL..S” series Spring Return Linear Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body. Actuator type :- AL..S series. Cause Obsolescence of Satchwell AL..S series Spring Return Linear Actuator. Resolution Replace Satchwell AL..S series Spring Return Linear Actuator with S-E M700 Spring Return Linear Actuator and Linkage Kit : AL..S = M700 + L7SV (880-0126-000) Linkage Kit. N.B. M700 is available with two different spring return actions M700 - SRSU (880-0430-000) = Spring Return Spring Up          ( M700 - SRSU will CLOSE a Satchwell Valve.) M700 - SRSD (880-0440-000) = Spring Return Spring Down     ( M700 - SRSD will OPEN a Satchwell Valve.) Should the Satchwell AL..S series Actuator include a wired Auxiliary Switch then the following S-E M700 Actuator specifications which include 2 independent 24 volt 4 amp AC-1 rated SPDT Auxiliary End Point Switches should be considered as appropriate: M700 - S2 - SRSU (880-0431-000) M700 - S2 - SRSD (880-0441-000) Alternatively Auxiliary Switch Pack S2 (880-0104-000) - Two independent 24 volt 4 amp AC-1 rated SPDT Auxiliary End Point Switches may be purchased separately permitting local installation.  Particular care should be taken when selecting a TAC Forta M700 Spring Return Actuator to replace an existing Satchwell ALMS, ALXS or ALES Spring Return Actuator.  Please refer to Replacement of Satchwell "AL..S" series Spring Return Linear Actuator by S-E M700 Spring Return Linear Actuator due to obsolescence.(Actuator Wiring). Please check the latest catalog for current equipment.

Issue A 7791 is used specifically for what? Product Line TAC INET Environment I/NET Site Cause A 7791 is used on security/access control installations. Resolution It is the interface for Door Processing Units (DPUs). (TCON209, 1-20) TCON Number and Title Cross Reference (with links) is TCON information. Explain and define I/NET Ethernet, C-LAN, and Sub-LAN communication is a chart to explain further.

Issue The card reader beeps continually when connected to the door controller with the Sounder cable connected. Product Line TAC INET Environment I/NET Cause There may be several causes for this situation: The door which this reader belongs to isn't configured. The polarity setting of the reader beeper isn't correct. This reader port is damaged due to certain cause. Resolution The following steps need to be followed: For cause 1, configure the door and reader in Door parameter. For cause 2, click "Sounder" button in the Door parameter window and change the "Polarity" setting correctly. Usually change from "High" to "Low". For cause 3, send the door controller to repair. For how to set up a beeper in I/NET, refer to How to use the Beeper of the Card Reader in I/NET.

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 Many alarms showing up during site commissioning for controllers that were not configured properly. Some duplicate id's and controller offline alarms for controllers that are no longer online and the alarms can't be removed. Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server SmartStruxure 1.3 Cause Alarms are orphaned in the database and are not removed once the duplicate id issue is resolved. Resolution The first thing to do is to attempt deleting the PersistedData.dat file (Purge Alarm from SmartStruxure Building Operation Database) and restarting the AS. If the orphaned alarms are still showing up then the next option is to completely clear the AS. Backup the AS, configuration only. Clear the AS and commission. Once it comes back up, restore the configuration.

Issue What are the new features that are available in the 3.xx firmware version of the DPU. Should we upgrade to the latest EPROM revision for the DPU 7910A / 7920A If we do not upgrade the EPROM will I/NET work properly. 7910 / 7920 DPU Transactions not showing up in AMT - including Disabled / Deny Entry Sel / Deny Entry Schd (Schedule) 7910 / 7920 DPU Door Editor changes not downloaded to controller. Editor changes revert back to None. Product Line TAC INET Environment I/NET Seven DPU 7910A / 7920A 2.23 and above. Cause The recommendation is to always upgrade to the latest revision. In some cases this is not always possible. Please review the information below to determine if these features and fixes are required for your installation. Note: The implications are that if you choose to leave the EPROMs at the earlier revision, and you enable the new features which are a "Global" setting (for example User defined PIN) then the DPUs with the unsupported firmware will not accept these changes even though you have defined this at the Host. If you require these features then you MUST upgrade the DPU which require these features and / or fixes. Resolution I/NET Seven is backward compatible with all previous hardware firmware revisions of the DPU. The recommendation is too always upgrade to the latest revision to enable all of I/NET's features and fixes included in these revisions. In some cases this is not always possible. Please review the information below to determine if these features and fixes are required for your installation. Note: The implications are that if you choose to leave the EPROMs at the earlier revision, and you enable the new features which are a "Global" setting (for example User defined PIN) then the DPUs with the unsupported firmware will not accept these changes even though you have defined this at the Host. If you require these features then you MUST upgrade the DPU which require these features and / or fixes. If you have any additional concerns then please contact Product Support. Below are the New Features introduced in firmware revision 3.00: This release contains changes to support a real time clock and the ability to report messages with seconds. The DPU now supports generating an alarm for a card read of a card that has been disabled. The DPU now supports the use of User defined PIN numbers. The DPU now supports soft and graced APB. The DPU has been modified to handle the new user defined Duress scheme. The DPU now has the capability of generating a Reader Tamper Alarm by configuring a two bit DA at bit offset 4 for door 1 and 5 for door 2. Click Here to review the changes for EPROM firmware revisions 2.23 through to 3.04 for both the DPU 7910A and DPU 7920A. For SCU range of controllers refer to I/NET Security Control Unit (SCU) firmware releases. 

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 Unable to enable or disable Enhanced Alarm Logging or Enhanced Alarm Delivery flags in Database Initialization. The Enhanced Alarm Logging flag goes back to what it was set to before making the change and the Enhanced Alarm Delivery flag is greyed out and uneditable. Product Line Andover Continuum Environment Continuum Database Initialization Cause The owner of the ContinuumDB is set to something other than the default andover97. In this specific case it was set to SA. The SA user was unable to write these changes to the database hence why the settings kept reverting back. To compound the issue it was found that an andover97 user had been created under the Security folder in the ContinuumDB, this then blocked attempts to change the owner to the correct andover97 user. Resolution Backup the ContinuumDB before making any changes. See Move / Backup / Restore a database on a Single User SQL2005 Express system. Attempt to change the db owner with the below query using the sp_changedbowner stored procedure. Select "New Query" and copy the query text shown below. Run the query. USE [ContinuumDB] GO sp_changedbowner 'andover97' GO If this produces an error "The proposed new database owner is already a user or aliased in the database" then see Unable to change the ContinuumDB database owner using the stored procedure sp_changedbowner for instructions on how to drop the incorrect user so we can use the correct one. After successfully dropping the user from the ContinuumDB, re-run the query in step 2 above to change the database owner to andover97.   After successfully setting andover97 to the database owner you should now be able to toggle the Enhanced Alarm Logging and Enhanced Alarm Delivery options in Database Initialization. If you want these enabled; toggle them both off, update the database, toggle them both on, update the database again. This will ensure they have been enabled properly. Note: The definitive check to see if the Enhanced Alarm logging and Enhanced alarm delivery are both enabled is by checking the dbo.ACCDBVersion table in the SQL database using SQL Server Management Studio (or Express). New Alarm Logging and New Alarm Delivery should both be set to 1.

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 Video integrations with Cyberstation want to bring in Pelco based alarms Product Line Andover Continuum, Pelco Environment Pelco DVR/SRV and encoders Continuum Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause Pelco devices have alarm abilities, but not all can be brought into Continuum Resolution Offline and motion alarms can be brought into Continuum. Any other Pelco hardware related alarms (i.e. dry contact or alarm inputs) cannot be brought into Continuum. See Video Monitor is not popping up video on alarm for troubleshooting motion or offline alarms.

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 Continuum runs very slowly. Taking up to two minutes to first startup. Generally opening up Continuum Explorer and any other objects are seen to be slower than normal as well. Product Line Andover Continuum Environment Continuum v1.94 and above Cause There was no Security Key connected and Continuum was running in Demo mode.  This symptom can also be caused by a missing or corrupt driver for the Security key, see Re-install of Continuum system and security key is not being recognized for details on re-installing the Security Key driver. Resolution Install valid Security Key and restart Continuum. Note: Want to know what features are supported in Demo mode? See How do we run Continuum in Demo mode and what features are available?

Issue Require manuals, datasheets, install guides or sales information for Field Devices. Product Line Field Devices Environment European Field Devices, U.S. Field Devices IPortal, USiportal, Extranet Datasheets, Specification, manual, sources of information Cause Where to obtain field device data? Resolution Field Device information for your part of the world can be accessed from the Exchange Extranet: Field Devices. When you logon to the site it will allow access to products available for your location. U.S. Products can also be easily found using the search in iPortal. Catalog information can be obtained via the following Valve, Actuator, Sensor, Field Device, Peripheral, HVAC Control Devices Datasheets and Catalogues, Selection Tool. Note: The Extranet links above are for Schneider Electric personnel or approved partners, if you do not have a logon account please contact your local Schneider Electric office for information. For pricing information please contact you local Order Entry or sales contact.