Building Automation Knowledge Base

Issue Which signal types can be connected to a UI on a Xenta I/O Modules? Product Line TAC Vista Environment Xenta 451A/452A, 421A/422A Cause UI is short for universal input, which means that these inputs are compatible with many different input types. Resolution Supported input signal types are: Thermistor: 1.8 KΩ at 25 °C or 10KΩ at 25 °C; Voltage: 0 to 10VDC; Current: 0 to 20mA; Digital Input. Refer to the following link about 1.8KΩ and 10KΩ thermistor compatibility: 1.8k Thermistor compatibility with Xenta controllers 10k Thermistor compatibility with Xenta controllers

Issue Is there a way to translate Cyberstation to a language other than English and use different SQL collation sequences and code page? Product Line Andover Continuum Environment Continuum Cyberstation Cause Standard Cyberstation installation installs the SQL using Code Page 850 1.x Strict compatibility. Resolution The link below is to the Language Translation support guides. These provide detail on how to translate the Continuum Cyberstation user interface to a different language. It also details in Chapter 3 how to use a different SQL sort order. This would allow the use of different character sets for use in personal names Language Translation Support Guide V1.81 Language Translation Support Guide V1.94 Also, there is an additional Continuum Language Support document available in MSWord format Here. For Arabic specifically, additional MSWord Document Here.  There are freelancers that can be of assistance to help with your site. Upwork is a site with potentially low-cost translators. NOTE - No testing has been done with Continuum v2.0 due to a lack of demand for translation See Andover Continuum v2.0 Language Translation

Issue Want to be able to run the SE7200 in floor heating and chilled beam simultaneously. Environment SE7200 Cause running simultaneous applications. Resolution Unfortunately the SE7200 will only handle 1 main application per controller due to its limited I/O.

Issue Error when installing SQL 2005 Express on a machine that had previously had MSDE installed Product Line TAC INET Environment SQL 2005 Express Cause  MSXML 6.0 SP2 is causing the installation to fail Resolution Download the program linked below Remove SQL 2005 from the system Run the application to remove MSXML 6.0 from the system Re-install SQL2005 Express MicrosoftFixit50568.msi.zip For alternative solutions see SQL Express install fails on MSXML 6 and Failed to create or configure database on SQL Server! ([17] SQL Server does not exist or access denied.).

Issue How long can the power to AS be interrupted Product Line EcoStruxure Building Operation Environment PS Power Supply Automation Server Cause Question regarding the AS and the power supply module. If the power is interrupted from the 24VAC power supply for say, 100 milliseconds, will the power to the AS be interrupted? There is a cold cap in the PS, and how long does it maintain power supplied to the AS? What about the RTC?   Resolution The power to the AS will be interrupted if there is a 100mS main power fail. The AS will then save the server cache. When the power returns the AS will make a restart that will take approx. 2 minutes. The AS Power supply fully complies with the IEC 61000-4-11 standard and can withstand voltage dips, with a 20mS dip and a 0% residual voltage.  The Power-fail process: When the AS loses power the super-cap keeps the AS alive for 15 seconds. 10 seconds of it dedicated to power-fail process to flush all the data that that are currently in the RAM to the SD card(That data can be anything with any value they have before power-fail). When power comes back that data is retained and are stored in appropriate place on the SD card. Real-Time-Clock(RTC) is maintained when the AS loses power by a dedicated capacitor which backs up the RTC chip for a minimum of 30 days in the absence of power since there is no battery in the AS.    

Issue SP-C-WEB Recommended Limits Product Line Security Expert Environment Security Expert SP-C-WEB Cause The SP-C-WEB limitations are mentioned in briefly in the SmartX Controller SP-C-WEB presentation but detailed information on this is not available in the current SP-C-WEB documentation.  Resolution Schneider Electric's recommended limits for the SP-C-WEB:Number of Areas: 32 Number of Doors: 32 Number of Aperio Doors: 0 Number of Sallis Doors: 0 Number of Allegion Doors: 0 Number of Credential Readers: 0 Number of Cameras: 2 Number of Elevators: 0 Number of Floors: 0 Number of Inputs: 512 Number of Keypads: 32 Number of Outputs: 512 Number of Input Expanders: 32 Number of Output Expanders: 32 Number of Reader Expanders: 32 Number of Analog Expanders: 32 Number of Users: 10000 Number of Areas: 32 Number of Doors: 32 Number of Aperio Doors: 0 Number of Sallis Doors: 0 Number of Allegion Doors: 0 Number of Credential Readers: 0 Number of Cameras: 2 Number of Elevators: 0 Number of Floors: 0 Number of Inputs: 512 Number of Keypads: 32 Number of Outputs: 512 Number of Input Expanders: 32 Number of Output Expanders: 32 Number of Reader Expanders: 32 Number of Analog Expanders: 32 Number of Users: 10000

Issue How many Modbus TCP Clients can be connected to Vista via an Xenta 913? Product Information TAC Vista Environment Vista 5.1.X Xenta 913 5.1.X or later Xenta 511 5.1.5 or later Xenta 701 5.1.5 or later Xenta 711 5.1.5 or later Xenta 721 5.1.5 or later Xenta 731 5.1.5 or later Cause When planning a system it's important to know how many devices are required. Resolution A maximum of 40 Modbus TCP clients are supported when communicating via a Xenta 913, Xenta 511 or Xenta 700. Each TCP Client may have up to 100 Modbus devices (see page 4 in the datasheet).  

Issue Values of Units change when viewing English OS from Metric OS Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Site Cause Changes in Unit Value English OS example of Pressure Unit of Bar: Metric of same exact unit from a Metric OS: Resolution This behavior of different Units being displayed on OS systems with metric units. In the State the English units for measurement are on the OS and StruxureWare Building Operation. The issue described is Functions as Design in StruxureWare Building Operation. Not just IO, but all the functions are like this. The localization follows the regional settings of the PC’s operating system, out of the control of users. To change your PC's measurement System, complete the following steps: Open the Control Panel on your PC and browse to "Region and Language" In the Region and Language editor, click on the "Additional Settings" button found at the bottom of the "Formats" tab. Change the measurement system to the desired system                                                                  Click OK to close all Windows Restart all applications for changes to take effect.

Issue Various controller install guides suggest fitment of an optional varistor for surge/spike protection, what components should be used? Product Line Andover Continuum Environment Surge and transient protection Metal Oxide Varistors (MOV) Part Number Line voltage protection, power line protection, mains spike protection. Noise, EMC resilience. Cause Install guides specify 39V, 130V or 250V varistors but what component part numbers should be used? Resolution For controllers with a 24VAC power feed, these are specified as a 39V Varistor, a suitable component would be: V39ZA1 This is also equivalent to Part # 01-2020-095 as listed in some install guides. For controllers fed from a 115VAC power feed, these are specified as a 130V Varistor, a suitable component would be: V130LA20A For controllers fed from a 230VAC power feed, these are specified as a 250V Varistor, a suitable component would be: V250LA40A Littelfuse Varistor ZA Datasheet PDF showing the full specification for each varistors is attached.

Issue How to enable Continuum site for use with Endura DVRs and cameras. Product Line Andover Continuum, Pelco Environment Continuum V1.91 and above Pelco Endura DVR See the Video Compatibility matrix for supported Pelco Endura products on the various Continuum versions, Cause Want to enable Continuum for use with Endura but unsure which security keys support the addition of the option and what the option provides. Resolution Why is this option required? The Endura -E option for Continuum security keys is required to be able to: Configure VideoServer objects in Continuum to use Endura DVRs. Use VideoAdministrator and VideoMonitor to configure and view Endura cameras. It is not required to be able to configure and view cameras from DigitalSentry DVR's or to view Endura cameras using VideoLayout objects that have already been configured. Which Workstations can have the option added? SU and LAN Cyberstation security keys can be enabled with the Endura -E option. This option cannot be added to the WEBC key for WebClient Servers. If configuring Endura cameras is required, a Cyberstation with the -E option must be used. WebClient browser users are able to use the VideoLayout to view DigitalSentry and Endura cameras. The Endura option is only available through the upgrade process through Repairs. There is no part number to specify to enable Endura at the time of ordering the security key. Once you have the serial number of the key, contact Repairs below. Email:  upgrades.continuum@schneider-electric.com How to tell if the option is enabled? If the system is operating normally (not in Demo Mode), open up a Video Server object. If the key is video enabled it should look like this: If it is not enabled, the Pelco Endura option is not available:

Issue After configuration, Suprema readers are showing as offline in the Security Expert client. There are Security Expert Download Service events logged in the windows application event log. Cannot load DLL - LoadLibrary() Failed. Cannot load DLL event mesage Product Line EcoStruxure Security Expert Environment Security Expert Suprema biometric readers Cause Required DLL SecurityExpertSV2.ThirdParty.dll is missing from the installation folder. Some versions of Security Expert installer will not install this required DLL and the file need to be manually added. Resolution Check the Security Expert install folder, typically C:\Program Files (x86)\Schneider Electric\Security Expert, to confirm if the file SecurityExpertSV2.ThirdParty.dll is present. SecurityExpertSV2.ThirdParty.dll   If the file is not in the installation folder then it can be sourced from the integration guide ZIP package. AN 264 Security Expert - Suprema Biometric - Integration Guide contains the three DLL's required for the integration. Install the file by copying it into the installation folder, then restart all of the Security Expert services or restart the Security Expert server.

Issue Receive error stating that a Menta "File object is locked by another application" when trying to open it for editing. Product Line TAC Vista Environment TAC Vista Menta Cause There are several potential causes of this error: The Menta (.mta) file is already open locally or on a remote machine. The current user does not have the appropriate authority to edit the file. Menta crashes while editing a file opened directly from the Server. Each subsequent attempt to launch the Menta editor from Workstation will result in this error. When a "standard" Menta file is being used and the user attempts to edit the Menta file locally. For more information about this scenario, please see "Read-only because object refers to a standard file" when editing Menta from Workstation. Resolution The following resolutions correspond to the causes listed above: If an instance of Menta already has the file open, whether on the local computer or on a remotely connected computer, then it must be closed before trying to open and edit that particular Menta file again. If the current Vista user has only "User" privileges or is otherwise limited from editing Menta then a user with the appropriate authority should log in to open the Menta file for editing. Shut down then restart Vista Server and Workstation if the error was caused by Menta crashing. See the link in Cause D above.

Issue The connection to the MQTT broker is not working and the MQTT client in the ES is offline following an upgrade from EBO 2022 to EBO 2023. The following error message can be seen in the ES trace.log: nsp.csc.mqtt.MqttNetwork Connection failed: TCP/TLS connect failure  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central MQTT integration Cause The reason for the connection issue is that the client certificate that is used is (self-signed) signed using SHA1. Since OpenSSL 3.0 this is forbidden at the default security level (which EBO is using) due to it having less then 80 security bits. See text in picture below taken from https://www.openssl.org/docs/man3.0/man3/SSL_CTX_set_security_level.html The default level is 1 and that is the setting EBO is using. Resolution Change the client certificate to one not using signing signature MD5 or SHA1. The certificate signature can be checked using the following OpenSSL command: openssl x509 -in cert.pem -noout -text Below is an example of how to use OpenSSL to check the certificate signing signature on the client certificate:

Issue Getting the connection error below when using Microsoft SQL server as External Log Storage for EBO. Error: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] SSL Security error [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] ConnectionOpen (SECDoClientHandshake()). [Microsoft][ODBC Driver Manage     Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES) Building Operation Enterprise Central (EC)   Cause When EBO connects to the Microsoft SQL server it uses the ODBC installed on the computer. It will use the ODBC version which comes with the OS and not the newest one installed on the computer. In this case that was too old to work with the Microsoft SQL server Resolution It is possible to specify what ODBC version EBO should use. First check what ODBC version is installed on the computer. Enter ODBC in the search bar on the computer Open ODBC Data sources and select the Drivers tab. Open EBO and navigate to the properties /External Log Storage/Microsoft SQL Server in the system tree. In the Database name field it is possible to specify which ODBC version EBO should use, see picture below

Issue Problem with Override control of BACnet Binary Output (BO) on IA Series BACnet Unitary, VAV and Zone controllers with firmware version 1.420 or earlier. When a BO override is released the value will not reflect the correct null state and may appear to still be in the previous state. After relinquishing the priority from the point, the actual Priority status shows up correctly as "Null". However, this is not reflected in the Building Operation Workstation "Watch" window. (Click on image below for larger view) Product Line TAC IA Series, EcoStruxure Building Operation Environment StruxureWare Building Operation 1.2 Automation Server BACnet Interface with MNB 1000 with MNB 300, MNB-Vx, or MNB-70. Cause When requesting the complete "Priority Array" for an output object, the values returned match their actual values, i.e. 0, 1 or "null". When requesting individual "priority array indexes" index numbers that are "null" will incorrectly return a 0 or a 1. Resolution MNB series V1.424 firmware for the VAV, Unitary, and Zone controllers resolves this issue. When an individual "priority array index" is requested, the priority input value of 0, 1, or “null” is returned. The issue only applies to the MNB-V1, MNB-V2, MNB-70, and MNB-300. The MNB-1000 does not have the "Priority Array" problem. The MNB series V1.424 firmware files are placed in the WorkPlace Tech firmware folder during the installation of WorkPlace Tech 5.8.2.

Issue Has the AC256 Xdriver been qualified or modified to work on any second generation controllers (NC2, bCX)? Product Line Andover Continuum Environment bCx9640 CX9680 Xdriver AC256 LA-1 Cause With the obsolescence of the NetC (CX99xx), will the AC256 Xdriver be updated to work with NC2 and/or bCX controllers? Resolution There are no plans to upgrade the AC256 Xdriver for the NC2 and/or bCX. One option, if a site only has AC256 IOU boards, is to use the NC2 and the LA-1 LBus Adapter module or the NC2 with built in LBus support (on comm4 or comm1 with an RS232-to-RS422 converter) to communicate over the LBus with Plain English programming in the NC2. Note: If you configure the controller for Lbus (using the LA-1 or directly to comm1 or comm4) you cannot use Continuum IO modules on that controller. For further information on X Driver compatibility and how to request new drivers/ upgrades, please see Will Continuum communicate with a third party system?

Issue Service Pack 2 provides the following correction: MicroNet VisiSat import file replaces all non-ASCII chars with replacement character( Defect 31467). Fix applied so that the characters are converted correctly.  Fix applied so that points with alarms and trends results in the import file being generated. Product Line Satchwell MicroNet Environment VisiSat 2.1 Build 196 201 Cause Correction of raised defects. Resolution This Service Pack should only be added to VisiSat 2.1.196 or 2.1.200 if service pack 1 has been installed. Note: When installed, the VisiSat 2.1.96 or 200 installation (200 if service pack 1 has been installed), the build number increases to 2.1.201. (due to one of the files in 'Program Files'). VisiSat will still show as Build 2.1.196 in Control Panel - Programs - Programs and Features - Uninstall or change program. Installing VisiSat Service Pack 2 =============================== Shutdown VisiSat and the VisiSat-Server. Run "VisiSat 2.1.196 Service Pack 2.exe". Extract to VisiSat installation root drive. (or extract to another location and move the Satchwell folder, created when extracted to the root of the C: drive). To the question 'Would you like to replace the exiting file', select 'Yes to All' Restart VisiSat. Download VisiSat 2.1 Build 196 Service Pack 2. See VisiSat version 2.1 Build 196 service pack 1 where information on VisiSat 2.1 Build 196 Service Pack 1 can be found and the service pack downloaded.

Issue Which actuators are suitable for VG311F? Environment VG311F Venta Forta M700 MG900SR M800 M1500 MV15B M3000 Cause Which actuator to choose for MV15B Resolution The following actuators are, depending on application requirements, suitable for use with the VG311F valve: M700, MG900SR, M800, M1500, MV15B, M3000 For more information on the valve / actuator selection, please see the valve data sheet here. For more details on each actuators, please see their data sheets respectively. They are available for download from the Extranet or public website.

Issue Unsure what options are available in the Lua smtp.send() function. Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager (MPM) Cause The Lua smtp.send() function is not fully documented. Resolution The syntax of the smtp.send() function is: smtp.send { from = string, rcpt = string or string-table, source = LTN12 source, [server = string,] [user = string,] [password = string,] [port = number,] [domain = string] }   From above you can see that the "from", "rcpt" and "source" fields are required. Whilst "server", "user", "password", "port" and "domain" fields are optional. Example Lua code is: --============================================================================== -- SSL email notification script example --============================================================================== -- Define the input you want to monitor below var("temperature", "ME.AI1") -- Room Temperature limit = 78 -- define the threshold now = scl.sysclock() if (temperature > limit) then -- When temperature is above threshold     if (sent == nil) -- Check if e-mail was already sent     and ((last == nil) or (now - last > 15 * 60)) then -- Maximum every 15 minutes         sent = true -- Only send e-mail once         last = now -- Keep track of last time     result, reason = smtp.send {     user = "alerts@server.com",  -- Enter your existing SMTP username     password = "test1234",  -- Enter your existing SMTP password     from = "alerts@company.com",  -- Enter your existing Source address     rcpt = {             "user1@company.com",  -- First recipient             "user2@company.com",  -- Second recipient             "user3@company.com"  -- Third recipient             },     source = smtp.message( {     headers = {     from = "alerts@company.com",  -- Displayed source address     to = "technicians@company.com",  -- Displayed recipients     subject = "Temperature Alert"  -- E-mail title                 },     body = "Current temperature is: " .. temperature .. " (above " .. limit .. ")" .. " [" .. os.date() .. "]"}),     server = "server.com" – enter your SMTP server                 }     if result ~= 1 then         print(os.date(), "E-mail was NOT sent:", reason)     else         print(os.date(), "E-mail was successfully sent.")     end end     else     sent = nil -- Re-enable alerting on condition end   --[[ Disclaimer: We hope that this script example and associated information (the "information") is valuable to you. Your use of this information, however, is at your sole risk. All information is provided "as -is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Schneider Electric.. Further, Schneider Electric. shall not be liable for any damages you may sustain by using/installing/modifying this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages. --]]  

Issue Netcontroller 2 offline with CPU LED and Ethernet LED's on solid. This occurred after electrician installed new equipment in the same cabinet. Environment Netcontroller 2 Continuum Cause Controller database has become corrupt. Resolution Clear controller RAM and Flash and reload controller. In this instance, the Controller did not seem to respond to pressing the "reset IP" button for 30s. Removing power and battery connections for a minute and then reconnection power cleared the memory. Able to see device online and reload from the Workstation after this.