Building Automation Knowledge Base

  Issue TAC Xenta devices suddenly indicate that they Needs commissioning. Product Line EcoStruxure Building Operation. Environment • Building Operation Workstation • Xenta 401 • Xenta 301 • Xenta 281 Cause The flag "Needs commissioning" is suddenly set.     Resolution If the property "Needs commissioning" is set, something has changed in the settings. This could be Subnet/Node address in the Domain table, or a change in any LonWorks binding, that caused a change in the Selector, Address, and or Alias tables.   The property Needs commissioning may also be set after a TAC Vista upgrade (conversion) or similar situations.  

Issue EP series information not available in documentation Product Line Field Devices Environment EP Series Pressure Sensor Cause Required information for planning installation. Resolution The EP 3x series consumes maximum 20mA input power as determined in loop powered mode (4-20mA).  When in three-wire voltage output mode, up to 2 mA of additional current may be drawn from the load. Further information is available on the Schneider Electric Exchange - EP Series Pressure Sensors.

Issue With the same time interval as the trend log, the traffic on the LonWorks network increases for a short period. This can be seen by a spike in the LPA log when viewing the bandwidth. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Lonworks Cause The LonWorks traffic increases with the same time interval as the trend log. Resolution To ensure we could log values in the trend log from a LonWorks device, a subscription is set up about 30 seconds before the value should be logged. After the value is logged, the subscription is removed until the next log interval. A good solution to flatten a spike caused by this issue is to stagger the times of the LonWorks trend logs. This will ensure the subscription for all the logs do not happen at the same time.

Issue Unable to configure the OA (outside Air) Damper control of SE8000 to work as desired for free cooling and CO2 (Ventilation) Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 Cause The damper control on the SE8000 is restricted to the minimum position under the following conditions: Econo.config parameter is set to off The CO2 value is 0 or lower than Min CO2 Parameter (adjustable) The OA (Outside Air) is warmer than Changeover SP (adjustable) The SA (Supply Air) temperature is colder than Supply air SP (adjustable) The parameter Mech. Cooling is set to OFF Resolution

  Issue TAC Xenta I/O modules working as LonWorks device, indicates offline, flashes fast after power restore. Product Line TAC Vista, EcoStruxure Building Operation Environment XENTA421A XENTA451A Cause When the TAC Xenta I/O modules are used as Lonworks devices, this is indicated by the LED that flash once every tenth second. After a power failure, the device will indicate offline by 5 flashes per second.   The device will indicate offline until it gets an update to any nvi or nci variable. Resolution As soon as the device gets an update on any nvi or nci, it will again start to flash once every tenth second. This means, that if you only read variables from the device, that is, only uses its inputs, it may indicate offline until the next time the configuration is changed.   A workaround for this issue could be to just use a dummy output, that is updated regularly.  

Issue When trying to browse for Areas to assign to the Area Inside Door and Area Outside Door fields in Door records, not all Areas are shown or available to be selected. Product Line EcoStruxure Security Expert Environment Security Expert Cause The Programming Mode selector is set to "Local" which is the default value. This will only show objects that are already attached to the controller this record resides in.   Programming Mode Resolution Change the Programming Mode to "Global" which will now show all Area records, including those unassigned or assigned to other controllers.   Programming Mode Global

Issue Replacements for Schneider Electric SmartX MF41 Damper Actuator Product Line Field Devices Environment SmartX MF41 Cause Replacement of SmartX MF41 Damper Actuators within the Schneider-Electric range Resolution Outgoing Actuator Model         Replacement Model (Part Number)        MF41-6083-G00                         MD10B-24 (875 1015 000)      MF41-6083-G02                         MD10B-24 (875 1015 000) + Aux Switch (914 1061 000)      MF41-6153-G00                         MD20B-24 (875 1025 000)      MF41-6153-G02                         MD20B-24 (875 1025 000) + Aux Switch (914 1061 000)

Issue When setting up the TH90x series thermostats there are communication limitations.  Unable to pull multiple registers.  Some registers are only in Celsius, regardless of the display setting. Product Line EcoStruxure Building Operation, Field Devices Environment SpaceLogic TH903 Series Thermostat SpaceLogic TH907 Series Thermostat Cause The TH903/TH907 does not support multiple/block register reads in Modbus.    The following parameters will show their value in Celsius only via Modbus communication regardless of whether the display is showing values in Celsius or Fahrenheit:   All SpaceLogic Series TH9xx thermostats Register 30 - Function Code 3/6 - Room Temperature (from the remote Modbus Controller) Register 1 - Function Code 4 - Actual Room Temperature 7 Day Programming Versions of TH900: Register 26 - Function Code 3/6 - 7 Day program schedule, heat set-point Register 27 - Function Code 3/6 - 7 Day program schedule, cool set-point Register 30 is used by the customer to override the current temperature. This register expects a value to be written to it every 15 seconds. If no values are written to it every 15 seconds, then it will populate with our internal temperature sensor value. Resolution Registers must be read one at a time rather than in groups. When using Modbus write the set-point values in Celsius. 

Issue Replacements for Satchwell AY series actuators Product Line Field Devices Environment AY Actuator Cause Obsolescence of AY series actuators from Satchwell Options range Resolution The following pop top actuators can be used to replace the AY actuator series:   AY1201                                              AG13U230 AY1251                                              AG23U230 AY1301                                              AG13A230 AY1351                                              AG23A230   For further Knowledge Base information - Types of TAC Erie Pop Top valves and actuators available from Schneider Electric in the UK.

Issue Getting error message when selecting Character set file for the TAC  Xenta Operator Panel (OP).     Product Line EcoStruxure Building Operation, TAC Vista, Xenta OP Environment TAC Xenta OP EcoStruxure Building Operation Microsoft Windows 10 Cause Microsoft Windows 10 does no longer allows the software to change files in all directories. Resolution Manually open up the directory C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 3.2\WorkStation\CharSet.lib Select the Charset you want to use, depending on the language, and copy the file. Remove the extension, so that the file is named Charset, without any extension. Manually open up the directory C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\WorkStation\Function Block Editor Paste the copied file here.

Issue How to upgrade an Automation Server if Port 80 is closed and the Automation Server is placed behind a NAT router. Getting error message when upgrading: Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Cause The problem is that the certificate are generated with the IP address off the Automation Server, and not the NAT Router IP. Resolution The Device Administrator has the option to add SAN's (Subject Alternative Name) and not just the address of the server. So add both the LAN and the WAN addresses in the SAN field when you generate the certificate and transfer to the server.

Issue When doing an "import Trend Logs" in TAC Vista Conversion Tool only HTTPs works and not HTTP. When using HTTP the error message below is shown: "Log on to Building Operation server failed because Failed to access the server, a network error occurred" Product Line EcoStruxure Building Operation Environment TAC Vista Conversion Tool version 3.1.1 Cause This is an issue fixed in TAC Vista Conversion Tool version 3.2. The issue is that the "Import Trend Logs" tab looks at the HTTP/HTTPS settings of the "Convert Database" tab instead of its own. Resolution Use TAC Vista Conversion Tool version 3.2 when available. Workaround: Set the HTTP/HTTPS settings on the first tab(Convert Database) even if "Import of trend logs" is done.

Issue When a TGML graphic is opened from Webstation and the user right clicks on a value in the graphic to open properties, it can take up to 20 seconds before the properties dialog is displayed. During the 20 seconds the working area is just grey. Product Line EcoStruxure Building Operation Environment Building Operation Webstation 2.0.4 and earlier versions Cause This problem only occurs when the signals in the graphic resides in a TAC Xenta; The problem has not been observed with Modbus or BACnet signals, and is only present in Webstation, not in Workstation. Resolution This issue is fixed in EBO 3.0. There is also a hotfix for version 2.0.4. It is labelled 2.0.4.5801. Contact you local technical support organisation if you need the hotfix.

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 for assistance. Issue How to combine multiple Continuum DBs into one DB Product Line Andover Continuum Environment Continuum Cyberstation Cause Multiple Continuum site databases need to be combined into a single site database Resolution Guideline for combining Multiple sites to one Database Executing this procedure requires a technician who thoroughly understands Continuum and how it works with SQL Server. This procedure does not encompass BACnet controllers. There is a multitude of decisions related to efficiencies and site preferences that are not documented here. The following procedure is intended for use as a guideline for combining multiple databases. This work must be done offline on a development database and validated on a test bench before Note:Before proceeding with this procedure you must do the following. Backup the Continuum database in SQL. Backup all the files and folder structure under New Graphic Files. Note that these files may be on the SQL Server or elsewhere on a mapped drive. Back all Cyberstation Profiles. Steps 1 – 11 must be done before any of the site exports are done. Preparation All sites must have the same revision software and CX firmware. NO EXCEPTIONS! Make sure that all the Alarm Enrollments and Event Notifications have unique names between all sites as these will wind up together in a single database. Make sure that all the Graphics in the Root directory have unique names between all sites. Make sure each Schedules in the Root directory has a unique name across all sites. Make sure each Custom ListViews in the Root directory has a unique name across all sites. Make sure each Groups in the Root directory has a unique name across all sites. Make sure each Reports in the Root directory has a unique name across all sites. Once steps 1-5 are completed, export each class in the root individually. Import files from step 6 into the new site The Local Site name on all the sites that will be combined must be named LocalSite. All workstations must have unique names and ACC IDs between the sites. All CX, ACX and BCX controllers must have unique names and ACC IDs between the sites. Note: The safest way to do steps 9 & 10 is to create a new controller in offline mode with the changed ID, then drag and drop copy from the original controller to the new controller. Panels, reports, and programs then must be edited to bind to the new controller. Another way to merge the panel, reports, and programs that are in the root is to copy all the panels, programs, and reports to their corresponding controller then export the controller. Doing this will keep all the bindings linked. Then once the controller is imported into the merged database they can be copied back up to the root. All Commports on all controllers and workstations must be named Comm1, Comm2, etc… Each site must have the default “ACC” user and password. All graphic files (.pin) under the New Graphic Files folder must have unique names between the sites. Merging the databases Install a standard multi-user Continuum system being sure to size the database big enough to accept all the other databases combined into one database.  After a clean installation is done, shut down the new workstation and the SQL server. Copy the empty database files to an area where they won’t get corrupted. Do a complete site export from each of the sites that will be combined. Back up all the Graphic files (.Pin) files from the site so that they can be transferred to the new server. Copy all the backed up Graphic files (.Pin) from each site onto a New Graphics Files folder in the location of choice. Note these files can reside on the SQL server or elsewhere on a mapped drive. Import each of the site text exports from the old systems into the new system. After each import check to make sure that each import went cleanly. Check all the Graphics, Programs, Alarm Enrollments, and Event Notifications to make sure that all the links were made during the import process.

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 for assistance. Issue A full backup immediately fails on the Automation Server.  Performing a configuration-only backup completes successfully. Product Line EcoStruxure Building Operation Environment Building Operation 3.x - first detected Building Operation Automation Server  Building Operation Automation Server Premium (AS-P) Building Automation Server AS-B Cause A directory under the DB folder, called tc [TypeCache], within the database of the Automation Server, had grown close to 1 GB in size.  The combination of this with the large TrendDb caused the backup failure with the following message seen in the trace log:    nsp.csc.bar.BarBackupOperation BarBackupOperation Execute failed with: Internal Server Error: Insufficient_Space_For_Backup (0x80008) in module Bar_Manager(51). "/<servername>": Insufficient space for backup, XXXXXXXXX bytes estimated for new backup but only XXXXX available   This tc directory contains types fetched from other servers that are used in runtime. These are loaded either from the local database or the tc directory. If a type for another server is not found in the tc directory when accessed, it will first be fetched from that server.   There may be other reasons for the backup failure, presenting this Insufficient_Space_For_Backup message in the trace.log. Clearing this Type Cache does not adversely affect the controller and can be cleared as the first step to see if this will allow the full backup to occur.    The issue has only been seen in Building Operation 3.x, if the issue is presented in a later revision or you continue to have failures, then contact your local support and reference this article.     Resolution To clear the Type Cache contents, follow these steps: Navigate to the RuntimeDBManager object under /System/Modules/RuntimeDBManager/ Right-click on the TypeCache object. Select Type Cache Clear All Attempt a full backup of the server again.  If failures continue to concur, then contact your local support

Issue Analog Producer value located in an RP-C controller cannot command light object(BACnet type: crs-lighting-output) or blind object(BACnet type: crs-blind-output) located in another RP-C's CRS expansion module. Analog Producer Value, Status flags: Fault and Reliability: communication-failure.     Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) 24 V Building Operation Room Controller (RPC) 230 V Cause Light and Blind objects support only two priorities (1 - Force, 2 - Normal). An error will be returned by the RP if the Priority in the Write request from the Producer Value is outside this range, ex. Priority 16. Resolution In the Analog Producer Value, set the default priority for writing to 2 (normal) or 1 (Force), as shown in below screenshot:  

Issue Unable to Access Access Expert after converting from V2 to V3 Product Line EcoStruxure Access Expert Environment Access Expert Hosted software V3 Cause Used the same Password as V2 Resolution When a site is converted from V2 to V3, Feenics sends out an email with a new username and password that can only be used within AX Version 3.   *Note* These new credentials cannot be used in V2. Once the conversion to V3 occurs, the V2 instance will be retired and you will only be able to use the V3 AX client to access your instance.

Issue After a PIN Duress Event at a door, the Duress Trouble Input stays "ON" and is unable to reset or restore the trouble input until a Valid Access Event occurs at the door. Product Line EcoStruxure Security Expert Environment Security Expert Controller Cause Attempting to restore Duress Trouble Input remotely after an accidental PIN Duress Entry by Card Users Resolution This is the intended design and function of the PIN Duress Trouble Input. It is considered an extremely-high priority issue and must be restored by a specific physical action. Remotely restoring (via Keypad in another location) would defeat the purpose of the PIN Duress Trouble Input. This is intentional to prevent a real duress event from going unnoticed.

Issue What is Life Reporting? Product Line EcoStruxure Security Expert Environment Security Expert Schindler Elevator HLI Integration Cause What function does the Life Reporting feature in a Schindler Elevator HLI Integration perform Resolution Life Reporting is a feature in the Security Expert Schindler Elevator HLI Integration. The life reporting interface is how Access Events from the Schindler system are reported back to Security Expert via TCP port. When enabled, you can receive "floor unlocked" events. Multiple loggers can be configured for the life reporting interface using the same IP address. Up to 32 loggers can be configured for the life reporting interface. You can also use Schneider Electric card readers for elevator access control alongside the Schindler system. For more details including prerequisites and configuration, please read AN - 196 - Security Expert Schindler HLI Integration    NOTE: Security Expert Software v 4.1.180 or higher is required. SX Controller Firmware v 2.08.919 or higher is required. One Security Expert Schindler Elevator High Level Interface License (SX-ELV-HLI-SC) per controller is required.

Issue Can Enterprise Servers inherit licenses from a parent Enterprise Central? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause Need to know if Enterprise Central Licenses can be inherited by an Enterprise Server, and then, in turn by Automation Servers. Resolution An Enterprise Server cannot inherit its licenses from a parent Enterprise Central. Licenses can only be inherited from an Enterprise Server by the attached automation servers. Refer to WebHelp article Inherited Licenses and Knowledge Base article SmartX Server License Inheritance in EBO 3.x.