Building Automation Knowledge Base

Issue Questions regarding specifications of Central I/O Inputs and Outputs Product Line EcoStruxure Building Operation Environment SmartStruxure I/O Modules: AO-8, AO-8-H AO-V-8, AO-V-8-H DI-16 DO-FA-12, DO-FA-12-H DO-FC-8, DO-FC-8-H RTD-DI-16 UI-8-AO-4, UI-8-AO-4-H, UI-8/AO-4-2, UI-8/AO-4-H-2 UI-8-AO-V-4, UI-8-AO-V-4-H, I/O UI-8/AO-V-4-2, UI-8/AO-V-4-H-2 UI-8-DO-FC-4, UI-8-DO-FC-4-H, UI-8/DO-FC-4-2, UI-8/DO-FC-4-H-2 UI-16 Cause Different I/O modules have varying electrical specifications Resolution Universal Input Specifications Universal inputs can be configured as voltage, current, thermistor, resistance, digital or supervised inputs.   Voltage Input Specifications: Range: 0 to 10 VDC Resolution: 12-bit (UI-8 v2: 16-bit) Accuracy: ±(0.7mV + 0.2% of reading) Current Input Specifications: Range: 0 to 20 mA Resolution: 12-bit (UI-8 v2: 16-bit) Accuracy: ±(0.03 mA + 0.4% of reading) Resistance Input Specifications: 10 Ohm to 10 kOhm 10 kOhm to 60 kOhm Thermistor Input Specifications: Range: -50 to 150° C (-58 to 302° F) Supported Types: 10k Type I (Continuum) 10k Type II (I/NET) 10k Type III (Satchwell) 10k Type IV (FD) 1.8k (Xenta) 10k Linearized (Satchwell DRT) 10k Type V (FD w/ 11k shunt) 1k (Balco) 20k (Honeywell) 2.2k (Johnson Controls) Digital Output Specifications Form C Relay: Terminals: Common (C), Normally Open (NO), Normally Closed (NC) Minimum Pulse Width: 100 ms Isolation: 1500 VAC (coil to contact) Cycle Life: ≥100,000 cycles Contact Rating: 250 VAC, 30 VDC, 3 A Form A Relay: Terminals: Common (C), Normally Open (NO) Minimum Pulse Width: 100 ms Isolation: 1500 VAC Cycle Life: ≥100,000 cycles Contact Rating: 250 VAC, 30 VDC, 2 A LED Indicators: Polarity: Reflects actual output state (ON = active, OFF = inactive) Color: Green Analog Output Specifications Analog outputs can be configured as voltage or current. Voltage Output: Range: 0 to 10 VDC Resolution: 50 mV Accuracy: ±100 mV Terminals: Voltage (V), Return Minimum Load: Source 2 mA, Sink -1 mA Current Output: Range: 0 to 20 mA Resolution: 0.1 mA Accuracy: ±0.2 mA Terminals: Current (I), Return Max Load: ≤650 Ohms Supervised Input Specifications Supervised inputs detect sabotage via resistor monitoring. Detected Conditions: Open circuit, short circuit, contact open/closed Circuit: 5V, 1 or 2 resistors Configurations: Series only, parallel only, series + switch Resistor Range: 1k to 10k Ohms (must be equal values) Note: Resistor value must be defined in the system. RTD Input Specifications RTD-DI-16 specifications are extensive. Refer to the official datasheet: RTD-DI-16 Specification Sheet  

Issue You need to replace a faulty Xenta 301 controller. However, the existing unit is running System Version 1, and the network comprises approximately 12 Xenta controllers on a Menta-only network using the .nwc and .ndb configuration tools. Product Line TAC Vista Environment TAC Xenta 300 Cause New Xenta 301 controllers are shipped with System Version 3 by default. System Versions 1 and 3 are incompatible on the same network. Resolution To ensure compatibility, downgrade the new Xenta 301 controller to System Version 1.17 before installation. Steps to Downgrade and Replace: Download TAC Xenta 300 system program version 1.17 Use the Download Wizard as usual. Important: When downgrading from Version 3 to Version 1, do NOT retain the old application in the Download Wizard. Select "Clear Application" during the process. Manually Download the Menta Application and Network Configuration Use a serial cable to perform the manual download. Apply the appropriate TAC Menta versions for your network setup. Additional Notes Mixing different system versions on the same network can lead to unpredictable behavior and communication issues. Always verify the version compatibility before deploying new hardware.

Issue Users need a way to identify all Forced Variables without manually inspecting each point. The goal is to have a summary view—not via Reports Server—but directly accessible on the Automation Server (AS) or Enterprise Server (ES). Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There is no built-in summary page in versions 1.4.1 and older that lists all Forced Variables. This makes it time-consuming to locate which points are currently forced. Resolution You can locate Forced Variables using the system tree in the Workstation. Navigate to: ES/Servers/AS/System/Modules/RuntimeDBManager/VariableManager/Variables Ensure the isForced column is enabled to view which variables are forced. Additional Notes: This method provides a quick overview without needing to open each individual point. It is especially useful for troubleshooting and auditing system behavior.

Issue What does it mean when a TAC controller is said to have a Universal Input? Product Line TAC Vista Environment Xenta Programmable Controllers Xenta I/O modules Cause The term “Universal” is commonly interpreted to mean compatibility with all types of inputs. However, this definition does not accurately apply to TAC Xenta controllers. Resolution In the context of TAC Xenta controllers, the term “Universal Input” refers to compatibility with multiple types of input signals, but not necessarily all types.   Key clarification: It is essential for project planners and system designers to consult the specific device’s datasheet to understand the exact definition of “Universal” as it applies to the particular TAC Xenta model in use. This ensures proper configuration and avoids misinterpretation during system design and implementation.

Issue After the "Windows is shutting down" message, Windows displays a non-specific memory error: lmadmin.exe - Application Error The instruction at "0x00000000" referenced memory at "0x000000". The memory could not be read. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause This issue is caused by Flexera Software, the licensing software used within Building Operation. Flexera does not support Windows XP, which leads to this error during system shutdown. This is a known limitation and will not be addressed in future updates. Resolution There are no known operational impacts associated with this error. It only occurs during shutdown of a Windows XP machine. Upgrading the operating system to a supported version will eliminate this error. Additional Notes This issue is cosmetic and does not affect system performance or licensing functionality. Users are encouraged to migrate away from Windows XP due to broader security and compatibility concerns.

Issue How can the firmware version of Security Expert Smart Card Readers be determined. Product Line EcoStruxure Security Expert Environment Security Expert Smart Card Readers Cause It is not possible to easily identify the firmware which a reader has been shipped with. Serial Numbers are not sequential and cannot be used as general guide. Resolution There are two supported methods to determine the firmware version of a Security Expert Smart Card Reader: 1. Via Product Support If you need to identify the original firmware version shipped with a reader: Raise a case with Schneider Electric Product Support. Include the reader’s serial number in your request. Product Support will contact Manufacturing to obtain confirmation of the firmware version originally installed on the reader. 2. Via Controller Web Interface (Requires Reader Expander Firmware 1.12.605 or later, Security Expert Controller Firmware 2.08.1498 or later, SP-C-WEB Firmware 4.00.2261 or later) From firmware version 1.12.605 and above, the Security Expert Controller’s web interface displays the serial numbers and firmware versions of connected card readers via RS-485 or OSDP. Steps to View Firmware Version: Log in to the Controller Web Interface. Navigate to Application Software. Open the Module dropdown to view connected readers. Important Notes: Wiegand-connected readers are not displayed in the web interface. If the Reader Expander address has changed, a power cycle is required for the readers to reappear in the interface.  

  Issue Understanding the size of individual tables within the Security Expert databases is essential for effective database management. This insight helps optimize system performance and supports archiving strategies. Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert Microsoft SQL Server Cause Managing SQL database size is critical to maintaining system performance. Identifying which tables consume the most space provides actionable data for optimization and archiving. Resolution To determine table sizes in the Security Expert and Security Expert Events databases, follow these steps using SQL Server Management Studio (SSMS): Open SSMS Right-click on the relevant database (e.g., Security Expert or Security Expert Events). Navigate to: Reports > Standard Reports > Disk Usage by Table Review the report to identify tables with the largest data footprint. Examples: Security Expert DB Security Expert Events DB Exporting the Report You can print or export the report for documentation or analysis: Print Export to Excel, PDF or Word Right-click on the data results and select Export Note: The “Disk Usage by Table” report is available in SQL Server 2008 and later.

Issue Fail to setup reverse proxy for SAML SSO. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation Cause EBO doesn't support reverse proxy configuration for SSO. Resolution The current version of EBO (7.0) does not support reverse proxy for SSO. An enhancement idea has been submitted to the Idea Forum. Please click the thumbs-up icon to help increase its visibility to product management.   Idea forum: SAML reverse proxy support  

Issue Sites using Report Server need to upgrade to EcoStruxure Building Operation (EBO) 2022 or higher, where WebReports/Report Server is no longer supported. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Report Server Building Operation Timescale Database Cause WebReports/Report Server is not supported in EBO 2022 (version 4.0) or higher. Resolution To address this, Schneider Electric provides a Data Migration Assistant (DMA) tool that: Reads data from WebReports 3.x Writes data to External Log Storage Download the DMA Tool External Log Storage Overview Stores historical data from EcoStruxure BMS Storage capacity is limited only by your hardware Historical data is displayed in WorkStation and WebStation (event and trend views) Any server can be configured to write data to TimescaleDB   Any server in the system can be configured to write historical data to the TimescaleDB database. Licensing Requirements External Log Storage requires a license Refer to: Software and Features that Require Licenses Part Number Summary and Hardware Software Matrix Hardware & Software Requirements Ensure compatibility with: TimescaleDB PostgreSQL Recommended specs for large systems (e.g., 100 BMS servers): High-performance SSD Minimum 64 GB RAM Additional CPU capacity Refer to: IT System Planning Guide Merging Log Data External Log Storage reduces extended trend logs on BMS servers You can merge extended trend logs into source logs in External Log Storage See: Merging of Trend Log Data Enhanced Reporting (XLSX Templates) EBO servers (v3.2 or higher) support native reporting with: Text and XLSX formats Advanced XLSX features: formulas, conditional formatting, charts, sparklines Historical data pulled from External Log Storage (PostgreSQL/TimescaleDB) Refer to: Examples for Native EBO Notification Reports

Issue How are BACnet controllers established as being Online / Offline? Product Line EcoStruxure Building Operation Environment BACnet Cause BACnet controllers may appear offline in the system, even though they can still be communicated with. This raises questions about how their online/offline status is determined. Resolution The online/offline status of BACnet devices is managed by the BACnet device manager plugin, which processes BACnet I-Am messages to maintain a device table.   The following rules and mechanisms are used to determine the status of BACnet controllers: Device Discovery and Initial Probing When a new device is discovered, an entry is added to the device table. The system probes the new entry up to four times at 5-second intervals. If the device does not respond within this time, it is declared offline. Offline Detection via MSTP Driver Building Operation uses the MSTP dev driver to monitor token passing. If three consecutive tokens are missed, the device is marked as offline. Probing Offline Devices Once a device is offline, the system sends a Who-Is message every 60 seconds. Offline devices are probed indefinitely at 60-second intervals until they respond. Online devices are never probed. Status Transition A device is considered online once it responds to a request. If it fails to respond, its status is updated to offline, and probing resumes.

Issue How to get data from Rayleigh Instruments RI-78-80-C kWh power meters Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Automation Server (ASP/ASB) Modbus RTU Interface Cause The RI-78-80-C meter provides a single 48-bit Modbus RTU word representing energy in kWh. This word spans three 16-bit registers (registers 0, 1, and 2). The meter: Only responds to a valid 48-bit read Does not return exceptions for invalid or partial register reads Resolution To successfully read the 48-bit value: Step-by-Step Instructions Create a Modbus Group Set an appropriate polling interval. Add Registers Add three 16-bit unsigned registers to the group: ModReg0 (Register 0) ModReg1 (Register 1) ModReg2 (Register 2) Create an Analog Value Example name: kWReading Script Program Use the following calculation: kWReading = ((256 * 256 * ModReg0) + (256 * ModReg1) + ModReg2) / 100 ​ This formula accounts for the fact that each register only uses half of its 16-bit range (values from 0 to 255). The register values represent 1/100 of a kWh, so a scaling factor of /100 is applied. Bind Points Bind the Modbus registers and analog value to the script program. Example Calculation If: ModReg0 = 3 ModReg1 = 167 ModReg2 = 59 Then: kWReading = ((3 × 256 × 256) + (167 × 256) + 59) / 100 = 239419 / 100 = 2394.19 kWh ​   Additional Notes The device may appear online in EcoStruxure even if it’s not responding correctly. This is because the online poll interval mechanism expects a response from a 16-bit register. Since the RI-78-80-C doesn’t respond to invalid reads, it may falsely appear online. To avoid this, set the online poll interval mechanism to “Inhibit”. Compatibility Warning: This device may not function correctly in v2.0 and v3.0 due to changes in offline detection. This issue is resolved in v3.1. Resources Example Modbus Objects and Script RI-78-80-C Exports.zip Numeric Output kWReading   Line Calc1 kWReading = ((256*256*ModReg0) + (256*ModReg1) + ModReg2)/100

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices.   Issue The panel displays an Address 1 has a wiring trouble condition. This is accompanied by a General Trouble alert. Product Line ESMI Fire Detection. Environment FFSULH2007. Cause The system is showing a wiring trouble condition at Address 1. To view more details, press the “More Details” button on the panel. This issue originates from the Input Module (FFSULH2007). Resolution The Input Monitor Module provides contact monitoring circuits for equipment that uses a dry contact signal. Typical Connection Diagram The diagram below shows a typical connection of the input module with the monitored equipment. The circuit is monitored for wiring faults using an End-of-Line (EOL) resistor, which should be installed at the last point of the circuit. Note: The EOL resistor is supplied inside the module box. Troubleshooting Steps If the EOL resistor is removed or discarded, or if the wiring is broken, the module will detect a loss of resistance and generate a wiring trouble alert. The installer must ensure: The EOL resistor is properly connected at the last point of the equipment. Any broken wires are repaired or rejoined. Once the wiring and resistor are correctly installed, the trouble condition will automatically clear.

Issue The MPM controller does not adjust the clock automatically when Daylight Saving Time (DST) period occurs. Product Line EcoStruxure Building Expert Environment SmartStruxureLite Multi-Purpose Manage Cause DST settings in the MPM are configured for North America. Canada and United States: Daylight saving time begins on the second Sunday of March and ends on the first Sunday of November Europe: Daylight saving time begins on the last Sunday of March and ends on the last Sunday of October Resolution In Firmware 2.15, DST properties can be configured in the Controller Configuration Object (CFG1) and/or configuration page. DST start and end configuration on month, week, weekday, hour and offset can be set. If using a firmware version older than 2.15, a script can be used to correct the issue. The script can be found here: Daylight_Saving_Time_DSC.lua

Issue How to use bit masking to decode on/off states from a Modbus analogue registers e.g. Holding or Input registers. Where each bit is required to be read individually to indicate the status of a coil. Product Line Satchwell Sigma Software Environment Sigma IC Modbus and IC3 Modbus controllers Cause Configuration technique to read 16-bit Modbus registers for on/off states. Resolution Each modbus holding or input register is 16 bits, where each bit can be on or off i.e. 0 or 1. For example the Sigma analogue input value of 901 represents the state of a number of coils where each bit indicates the on or off.  Hence, this translates to the 16-bit binary value  0000001110000101  where 1 = on and 0 = off Create a Sigma analogue input object to read the Modbus value. Click here for the  Sigma Modbus 4.06 release Note Create a programmable object for each of the required bits (max of 16 for each register) to be read as below.  (Highlight, copy and paste into each programmable object). For Example starting with the Least Significant Bit (LSB) and where point 0|222 is the Modbus value created, the programmable objects are; Bit 1 (LSB) 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 1 ) 30 IF YINT = 1 THEN RETURN TRUE "Bit 1 = on" 40 RETURN FALSE "Bit 1 = off" Bit 2 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 2 ) 30 IF YINT = 2 THEN RETURN TRUE "Bit 2 = on" 40 RETURN FALSE "Bit 2 = off" Bit 3 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 4 ) 30 IF YINT = 4 THEN RETURN TRUE "Bit 3 = on" 40 RETURN FALSE "Bit 3 = off" Bit 4 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 8 ) 30 IF YINT = 8 THEN RETURN TRUE "Bit 4 = on" 40 RETURN FALSE "Bit 4 = off" Bit 5 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 16 ) 30 IF YINT = 16 THEN RETURN TRUE "Bit 5 = on" 40 RETURN FALSE "Bit 5 = off" Bit 6 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 32 ) 30 IF YINT = 32 THEN RETURN TRUE "Bit 6 = on" 40 RETURN FALSE "Bit 6 = off" Bit 7 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 64 ) 30 IF YINT = 64 THEN RETURN TRUE "Bit 7 = on" 40 RETURN FALSE "Bit 7 = off" Bit 8 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 128 ) 30 IF YINT = 128 THEN RETURN TRUE "Bit 8 = on" 40 RETURN FALSE "Bit 8 = off" Bit 9 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 256 ) 30 IF YINT = 256 THEN RETURN TRUE "Bit 9 = on" 40 RETURN FALSE "Bit 9 = off" Bit 10 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 512 ) 30 IF YINT = 512 THEN RETURN TRUE "Bit 10 = on" 40 RETURN FALSE "Bit 10 = off" Bit 11 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 1024 ) 30 IF YINT = 1024 THEN RETURN TRUE "Bit 5 = on" 40 RETURN FALSE "Bit 6 = off" Bit 12 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 2048 ) 30 IF YINT = 2048 THEN RETURN TRUE "Bit 12 = on" 40 RETURN FALSE "Bit 12 = off" Bit 13 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 4096 ) 30 IF YINT = 4096 THEN RETURN TRUE "Bit 13 = on" 40 RETURN FALSE "Bit 13 = off" Bit 14 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 8292 ) 30 IF YINT = 8292 THEN RETURN TRUE "Bit 14 = on" 40 RETURN FALSE "Bit 14 = off" Bit 15 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 16384 ) 30 IF YINT = 16384 THEN RETURN TRUE "Bit 15 = on" 40 RETURN FALSE "Bit 15 = off" Bit 16 (MSB) 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 32768 ) 30 IF YINT = 32768 THEN RETURN TRUE "Bit 16 = on" 40 RETURN FALSE "Bit 16 = off"

Issue Installing and Configuring Email Service Accounts in Niagara G3 Environment Niagara G3 Cause The need for a quick reference guide Resolution The following document can be found at Niagara-Central.com as well.

Issue How to configure a LON router in Niagara R2. Environment Niagara R2 LON Cause Troubleshooting Resolution Review / download documentation here.

Issue Schlage step by step configuration. Environment Windows Xp, 7,  2008, 2008R2 Continuum 1.94 Cause Single Door set Up examples. Resolution Schlage Door setup examples attached.   Download here

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 How to setup automatic table truncation on Single-User SQL Express systems. Product Line Andover Continuum Environment Continuum Cyberstation Single-User SQL Express SQL Server 2005 Cause Only the ExtendedLog table is automatically truncated on an Single-User SQL Express Continuum system. The other tables that can fill up quickly and need to be truncated regularly are not catered for (accessevent, activityevent, alarmevent, and errorevent). Resolution IMPORTANT: Make sure to perform a full SQL Database backup before attempting to make any changes to the database. (See Move / Backup / Restore a database on a Single User SQL2005 Express system for details on how to backup your database and, if not already installed, where to get Management Studio from) Use the attached file SQLExpress to add table truncations.zip, to configure your Single-User SQL Express system to automatically truncate these tables when it does the ExtendedLog truncation. After downloading the file, follow the steps below. There are three files in the archive, these need to be copied to your Continuum folder on your Single-User system running SQLExpress as the database engine. LogTruncate.SQL This file is the SQL script that performs the truncation of the four tables (accessevent, activityevent, alarmevent, and errorevent) to the number of days you specify - I have selected 90 days as my default but you can change this to whatever you require for each table. CS_LogTruncate_OneOff.bat This batch file will run the LogTruncate.sql script once when manually executed. You will need to change the server name "PC3" to whatever your PC's name actually is on your system. CS_Hrly - with LogTruncat.bat This is the batch file that will be renamed and replace the existing "CS_Hrly.bat" file currently located in your Continuum folder. This is the same as your current file except it has added the LogTruncate.sql script so that this will now be executed every hour along with the rest. Backup "CS_Hrly.bat" file in Continuum folder by renaming the file to something like "CS_Hrly ORIGINAL.bat". Rename "CS_Hrly - with LogTruncat.bat" to "CS_Hrly.bat", copy into (overtop the existing file if you haven't renamed it) the Continuum folder, and change the server name "PC3" to your PC's name. This should now execute this table truncation script along with the other database maintenance scripts every hour.

Issue Documentation for the Huba 692 differential pressure sensor is not available on the Extranet or other Schneider Electric web sites. Environment Part no 6552050000, Huba 692 Differential pressure sensor Cause This is a Class 3 product that is sold by Schneider Electric, but documentation is provided by the manufacturer. Resolution Data sheet is available here, or on the manufacturer web site: http://www.hubacontrol.com/en/products/

Issue Webstation static graphic viewer no longer works in Chrome, FireFox or on smart phones. The "Loading..." image never goes away. Environment Webstation Cause The file "xmlHttpImageLoader.js" located in "C:\inetpub\wwwroot\TACVistaWeb519\Modules\Graphics\ImageLoader" (519 being the version of TAC Vista installed) uses the name "status" for a variable in the script. This variable name is a reserved word. The name is actually not a reserved JavaScript word, but a reserved Windows word: http://www.w3schools.com/js/js_reserved.asp Resolution As only Internet Explorer is supported, this is not going to be fixed. There is however a workaround that will enable viewing graphics in static mode. 1. Rename the file C:\inetpub\wwwroot\TACVistaWeb519\Modules\Graphics\ImageLoader\xmlHttpImageLoader.js 2. Paste this corrected file to the same location