Building Automation Knowledge Base

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.

Issue Expanding a system with a 7798B and unable to connect to other controllers. Product Line TAC INET Environment All versions of I/NET Cause There is no expansion card to connect the LAN Controllers together. Resolution The 7798B requires a CLX Expansion Card to be plugged into the slot to allow it to communicate to other controllers. The part number for this is LAN EXPANSION OPTION FOR RS-485, CLX. See Additional information on CLX LAN Expansion Option for RS-485 for more information on the CLX part. Take the device off the wall, unplug all wires including power. Insert the CLX card into the slot on board, be careful not bend any pins while doing this. Connect the wires again in their respective terminal with the LAN wire connecting to the CLX card, Sublan to those devices and power. Put the device back on the wall, set up accordingly and it should be communicating to the controllers now.

Issue Should we upgrade to the latest revision for the SCU 1284 If we do not upgrade the SCU will I/NET work properly. Product Line TAC I/NET Environment I/NET Seven Security Control Unit (SCU) 1200 series firmware 3.2x 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. Resolution I/NET Seven is backward compatible with all previous hardware firmware revisions of the SCU. The recommendation is to 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. If you have any additional concerns then please contact Product Support. The following table lists the release firmware revisions and associated fixes and new features: Rev Date DCN Changes 3.21 05/06 5593 Add support for SCU tamper to the SCU1200 and SCU1280 3.22 01/07 5610 Start adding intrusion alarm support to SCUs Add issue level support to SCU1284 Fix defect where deleting last tenant from DPU causes incorrect schedules Add door code 3.23 08/07 5627 Fix defect where changing a door to "unselect" did not prevent access through door 3.24 10/07 5631 Expand individual count from 24,000 to 32,000 per tenant 3.25 07/08 5657 Implement various changes to intrusion alarm system that were identified during EN50131 certification 3.26 01/10 5677 Fix corrupt reader LED due to OP5 monitoring board Fixes to SCU1284 expansion board for IAS power monitoring 3.27 07/11 5717 Make AMT show person who commanded PIN functions 3.28 12/12 5739 Fix for bad card read on reader number 4 with internal AO at bit offset 04 3.29 08/13 5745 Fix so that a change of date from one month to the next will work correctly when using special days 3.30 10/14   Support for 130-bit Wiegand card New event named “Key reassignment” 3.31 12/14 5754 Support for 86-bit Wiegand card For DPU range of controllers refer to I/NET Door Processing Unit (DPU) 7910A / 7920A EPROM Feature matrix.

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 trying to log into SBO Workstation receive the following error: Invalid returned data from license server system. (Error code: -12) Product Line EcoStruxure Building Operation Environment Workstation Enterprise Server Cause This error has been caused when a Workstation license is present but no Enterprise Server license is present. Resolution An Enterprise Server license must be purchased and added. Please see EcoStruxure Building Operation License types for license options and part numbers.

Issue Alarms or Events are not being received as soon as they occur and there is a large delay before they are written to the Database. Product Line Andover Continuum Environment Continuum Cause Review the controller error log. If there are 6c0e errors, this indicates the comms buffer is filling up (see Controller error log: error transmitting (LAN_ERR_TRANSMIT_ERROR)). Another indicator is in the ACCTRace logs. Check if Alarms are being logged in the Database when the WS thread is receiving them. The time in the ACCtrace may be logged as the TimeOfLog. Investigate the programming to see if it is polling data from a BACnet controller constantly. There may be no delay in poll requests which can overload the controllers comms buffers. This will in turn delay some Alarms from being delivered to the Workstation to be displayed and logged in the Database. Resolution Fix programming so there are wait lines between each poll. Also see Controller error log: error transmitting (LAN_ERR_TRANSMIT_ERROR).

Issue How to upgrade from Continuum v1.4 Product Line Andover Continuum Environment Continuum Cyberstation Cause What are the steps in upgrading from Continuum 1.4 Resolution For a smaller site it may be quicker and more reliable to install the current Cyberstation version, then upload from the controller, this has the advantage of ensuring you have a clean database. The alarms, workstations etc, would needs to be rebuilt from scratch. If the current database is clean (Passing continuum analyzer is NOT proof of a clean database, only a helpful initial step) and it is decided to upgrade the existing database from 1.4, you will first need to upgrade to v1.5x, then follow Upgrading Continuum from 1.5x to Continuum 1.9x. The overall process can be a little complex as various operating systems need to be available/installed. See the Continuum Compatibility Matrix for details for the PC and Controller firmware requirements Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation See the Continuum installation guides for the PC hardware requirements The v1.4 graphics could be .pan or .pin files. The .pan would need to be re-drawn as .pin files, in order to be compatible Run Continuum Analyzer before/after each upgrade, also run Continuum to ensure it runs correctly.

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 there are dual NICs on the computer, you will get host number conflicting error. The IP address causes this conflict is just the local IP address. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET prior to Version 2.44a Win 7 or higher OS Cause When there are two NICs on the computer, I/NET needs to know which NIC is used for communication. I/NET support for dual Network Interface Cards (NIC) can be used for dual NIC configuration for I/NET. But under Win 7 and higher OS, wireless NIC can't be recognized in I/NET, which makes it impossible to choose wireless NIC to be used for I/NET. In the I/NET configuration, it just shows 0.0.0.0. Resolution I/NET will fix this issue in the new release. For I/NET prior to version 2.44a, there are two workarounds for this issue currently: Refer to I/NET support for dual Network Interface Cards (NIC) to choose onboard NIC to be used for I/NET communication. Disable onboard NIC or just disconnect it from the network. Then you will see the option for choose NIC for I/NET communication will be grayed out. That will force I/NET to communicate with wireless NIC. Remember to reboot I/NET I/O server after this to make it take effect.