Building Automation Knowledge Base

Issue Windows update KB4519976 causes all Xenta servers to go offline in TAC Vista every few minutes. Product Line TAC Vista Environment TAC Vista Server Microsoft Windows 7 or Microsoft Windows 2008 Server Xenta 500 Xenta 700 Xenta 900 Cause After the Windows update, KB4519976 is installed, the SSL handshake behavior is changed. This affects TAC Vista and its communication with the TAC Xenta server. Resolution There are two workarounds available at the moment. Solution 1: Uninstall Windows update KB4519976 Solution 2: Turn off SSL for the communication between TAC Vista and the TAC Xenta server using the registry setting shown below. This means that only the login will be encrypted when TAC Vista is communicating with the TAC Xenta servers. Run the utility TacosTweak.exe, located in the program folder where TAC Vista is installed. Set "Only use SSL for login to TAC Xenta Servers(5xx/7xx)" to 1 to run the communication between TAC Vista and TAC Xenta servers without SSL. Restart the TAC Vista server for the changes to take effect.

Issue The specifications and setup details of the EH series humidity sensors. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, TAC IA Series, TAC INET, TAC Vista Environment Humidity Sensor Cause The EH Series Room, Duct and Outside humidity sensors are a universal Relative Humidity transmitter that can be powered with either a +15 to 36 Vdc or 24 Vac supply voltage. The EH series sensors are designed with a field selectable 4-20 mA, 0-5 Vdc, or 0-10 Vdc output signal that is equivalent to 0 to 100% RH. The EH Series is used in building automation system, humidity chambers, and OEM applications and is compatible with Vista, Continuum, I/Net, I/A, and SmartStruxure systems. Resolution EH Series Humidity Sensors Click the below links to look at the documentation for these sensors including the dip switch settings. EH Series Humidity Sensor Data Sheet EH Series Humidity Sensor Installation and Operation Instructions Old EH Series Humidity Model For information on the older style of dip switches (models with two separate sets of dip switches), see the document below. Old EH Series Humidity Sensor Installation and Operation Instructions

Issue Schindler have recently released version 1.3.370.1 of their Schindler PORT elevator system software. Product Line Security Expert Environment Security Expert SP-C Schindler PORT elevator system version 1.3.370.1 Cause Schindler have released an updated version of their Schindler PORT elevator system version 1.3.370.1 Resolution The SDK for Schindler PORT elevator system version 1.3.370.1 has no major changes when compared to the existing tested and supported version 1.3.369.1. So while it is 'likely' that this latter version will operate correctly, at this present time it is an untested and unqualified version for this integration. Please see AN 196 Security Expert - Schindler HLI - Integration Guide for more details of the integration.

Issue There is a compatibility issue between Revision 2 MNL controllers and S-Link sensors. This incompatibility is noticed when a later production S-Link sensor is connected to an older Revision 2 controller. When the sensor is connected to the controller, 88.8 appears on the sensor’s display window along with all of the other LCD icons. The display never recovers from this mode, which makes the sensor non-functional. Product Line TAC IA Series Environment MN-Sx sensors MNL-10Rx1 and MNL-20Rx1, where x denotes profile type (F, H, R) MNL-V1RV1, MNL-V2RV1, MNL-V3RV1 Cause New MN-Sx production S-Link sensor firmware is not compatible with older Revision 2 MNL controllers. Resolution Newer model S-Link sensors have been released to address this issue. The new part numbers are MN-S1-2, MN-S2-2, MN-S3-2, MN-S4-2, and MN-S5-2. The MN-Sx-2 model line was designed and verified to work with older Revision 2 controllers.  Reference TPA-RKFD-09-0028-00 for more details. Please note that the new MN-Sx-2 S-Link sensors are only for use with older Revision 2 controllers.

Issue SBO WebStation has stopped loading with an ERR_SSL_VERSION_OR_CIPHER_MISMATCH error (Chrome & Edge Browsers)   or an SSL_ERROR_UNSUPPORTED_VERSION (Firefox browser)   Product Line EcoStruxure Building Operation Environment Building Operation WebStation Chromium release 91 and above Firefox version 78 and above Cause Chrome and Edge browsers In Chromium release 91 an alert was shown on the browser regarding the security of unsecured connections. In Chromium 98 support for TLS 1.0 and 1.1 was removed.   Firefox Browser Starting in Firefox version 78, the minimum TLS version allowed by default is TLS 1.2. The error page may also include a button, Enable TLS 1.0 and 1.1 that will allow you to override the minimum TLS requirement. Note: Mozilla plans to remove this option and permanently disable TLS 1.0 and 1.1 in a future version of Firefox. Resolution Modern browsers don't allow SSL versions lower than TLS 1.2 [1] [2]   The site can temporarily use a HTTP rather than HTTPS connection to bypass this issue, however, this is not advisable on a permanent basis for Cyber Security reasons.   Using an older browser like Internet Explorer can also be used as a workaround since this is no longer being updated and won't have the latest Cyber Security policies.   Ideally, the site will need to upgrade to SBO 1.9 or above to allow TLS1.2 support.   [1] https://chromeenterprise.google/policies/?policy=SSLVersionMin [2] https://support.mozilla.org/en-US/kb/secure-connection-failed-firefox-did-not-connect

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 Data not passing from Enterprise Server to Reports Server after upgrading to 1.6 Reports folder does not appear on new 1.6 Reports installations Logon failed at attempt no. XX User account has been temporarily disabled. Contact your administrator. Product Line EcoStruxure Building Operation Environment Building Operation WebReports 1.6 and above Cause New features require additional configuration to allow Reports to function. Specifically, the Reports installation requires that the SystemReportsService user account be enabled before installation.  If this is not done, the steps below must be taken.   For Issue #3: If the user account used to access WebReports is changed through WorkStation, WebReports is still using the previous account password to access the Enterprise Server, this will lock the user account out and if used to log in to WorkStation will indicate that the account is disabled To verify that this is what is causing the lockout, open the Report Agent log StruxureWareReportingAgentLog and check for Logon Failed at attempt xx Reason: User account temporarily disabled.... error is shown. The default path for this log file is: C:\Program Files (x86)\Schneider Electric (StruxureWare)EcoStruxure\Building Operation Resolution During the installation of WebReports, you will see the popup message below. In order for the installation to work correctly, the SystemReportsService account must be changed to enabled before clicking OK. Ensure that SystemReportsService user account is enabled in the Enterprise Server before you proceed with the installation process further. To correct this error after installation: If running stop the Repot Agent Service and wait 1 minute before proceeding Log into Workstation using the admin account Modify the user "SystemReportsService" (or user account used) that is part of the Local domain Check/Change the property "Disabled" is set to "False Change/verify the password Close WorkStation On the Report Server open the program "Building Operation WebReports Administrator" Enter the newly created password for the SystemReportsService (or account used) Click Apply - a successful update should be reported. Click Save Close Building Operation WebReports Administrator Restart the Reporting Agent Service. Verify logins now work. For additional Authentication issues please see the online help topic: Authentication Failed (se.com)

Issue What port is used for the I/A Series G3/N4 LON and Serial tunnel clients and can it be changed? Product Line TAC IA Series Environment I/A Series G3/N4 Enterprise Server I/A Series G3 ENC I/A Series Jace 8000 Cause Requires port change due to routing or firewall conditions. Resolution By default, the G3/N4 Tunnel Service utilizes TCP port 9973. The port used for tunneling can be configured by modifying the Server Port within the tunnel service properties. Example: Configuring the Lon tunnel server In the palette sidebar, open the lontunnel palette. Open the ENC/JACE station and expand its Services folder. If no TunnelService exists, paste one from the palette into the Services folder. If a TunnelService does exist, go to the next step. Note: Only one TunnelService is needed in a station's services, and it can hold multiple tunnel components (both LonTunnel and (serialTunnel). The TunnelService in the lontunnel module is identical to the TunnelService in the (serial) tunnel module. From the palette, paste a LonTunnel under the station's TunnelService The station should now have a TunnelService and a child LonTunnel component. Configure the properties and modify the TunnelService server port if required. Note: If the ENC/JACE has multiple LON ports (and corresponding LonNetworks), the same number of LonTunnel components can be copied under the TunnelService. Each LonTunnel component can then be associated with a particular LonNetwork (by its LONn device name). For any station user that needs to Lon tunnel, make sure the user has admin write permissions for the LonTunnel(s). Example: Configuring the serial tunnel server In the palette sidebar, open the tunnel palette. Open the ENC/JACE station and expand its Services folder. If no TunnelService exists, paste one from the palette into the Services folder. If a TunnelService does exist, go to the next step. Note: Only one TunnelService is needed in a station's services, and it can hold multiple tunnel components (both LonTunnel and (serialTunnel). The TunnelService in the lontunnel module is identical to the TunnelService in the (serial) tunnel module. From the palette, paste a SerialTunnel under the station's TunnelService. The station should now have a TunnelService and a child SerialTunnel component. In the SerialTunnel's property sheet, expand the "Serial Port Config container." Enter the COMn "Port Name" used by the target driver network, and specify other parameters as defined in the network's configuration. If the ENC/JACE has multiple serial-type driver networks (and corresponding COM ports), the same number of SerialTunnel components can be copied under the TunnelService. Each SerialTunnel component can be associated with a particular network (by its COMn port name) and set the other parameters accordingly. For any station user that needs to the serial tunnel, make sure the user has admin write permissions for the SerialTunnel(s).

Issue Platform connection using TLS fails. Standard HTTP connection of port 3011 successful. Product Line TAC IA Series. Environment I/A Series Enterprise Server Cause TLS platform connection fails immediately and throws an exception in Workbench. Note that the Niagara Daemon is running and a non-TLS HTTP connection is successful. No station is currently running on the PC. All stations are stopped.   Example exception- SEVERE [08:45:58 02-Sep-20 CDT][wb.shell] Error connecting to platform daemon at localhost: GET /platformInfo javax.baja.naming.UnresolvedException: platformssl: Resolution A possible cause is a zero-byte file size bog file in the Daemon Home 'stations' folder. Check all of the station folders in Daemon Home, searching for any bog file that is zero bytes in size. Look for 'Config.bog.lock' files as one could be orphaned when a station running in the Niagara daemon were to stop unexpectedly, such as the system reboots suddenly or the PC is powered down. Remove all files that are zero bytes in size. Remove any 'Config.bog.lock' files. Test the TLS connection for a successful connection.

Issue How to create an offline alarm if the AS-P or RP-C loses the connection to a Zigbee sensor (SED-MTH-G-5045, SED-WDC-G-5045, and SED-WLS-G-5045) connected to AS-P or RP-C. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Room Controller (RP-C) Greenpower sensors SED-CO2-G-5045 and SED-TRH-G-5045 non-Greenpower sensors SED-MTH-G-5045, SED-WDC-G-5045, SED-WLS-G-5045 Cause The Zigbee device will communicate the measured data with a time interval, if EBO doesn't hear the data it should mark the device as offline and generate an offline alarm Resolution In general, the RP-C or AS-P will listen for communication from the Zigbee device and if it doesn’t hear any communication for a certain time period, the Offline timeout (which can be specified in the properties for the Zigbee device in EBO) will set the device offline and an offline alarm will be displayed in the alarm list. How often the Zigbee device will communicate the measured data depends on the Zigbee device. It is possible to see and configure how often it should send the data in EBO but depending on the device it can be found in different places in EBO. For the Greenpower sensors SED-CO2-G-5045 and SED-TRH-G-5045 it is found here: The default value can be found in the specification sheet for the sensor. And for the non-Greenpower sensors SED-MTH-G-5045, SED-WDC-G-5045, SED-WLS-G-5045 It can be found here:   It is possible to change the interval for how often the sensor will send the data but this may cause the battery in the sensor to drain faster. It is recommended that the Offline timeout is set to more than twice the heartbeat interval from the sensor so that it will not be set as offline if only one message from the sensor is missed by the RP-C or AS-P.

Issue What is Alarm decoration in EBO (EcoStruxure Building Operation) and how is it set up? Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause Alarm decoration is used when you wish to change the alarm configuration or appearance in the alarm list for a specific alarm or a group of alarms if it meets certain conditions specified when setting up the alarm decoration. If any alarm in the system meets the conditions specified when setting up the alarm decoration the alarm will be displayed in the alarm list as specified in the alarm decoration rule. Examples of alarm specifications that can be changed by an alarm decoration rule are: Alarm text message Alarm priority Auto hide Background color Resolution See the video below: The video will show how to: Create an Alarm decoration Set up an Alarm decoration filter with the conditions: -Alarm text: *offline* -Priority: 20 Set up Alarm decoration presentation with the specifications: -Priority: 300 -Auto hide: Yes After the Alarm decoration is set up any alarm in the system where "offline" is part of the alarm text and having priority 20 will be auto hidden and given the priority 300.  

Issue Niagara Runtime Environment (NRE) fails Console output when starting Workbench Product Line TAC IA Series Environment I/A Series N4 Workbench Cause An issue has occurred in the security of the user home for the installation of Niagara N4 Resolution If the Workbench fails to launch. Open the Console for the build you are trying to use by following the illustrated path and clicking the console.exe If the Console output is as shown under "Issue" above, follow the path shown below. Complete the instructions in the illustration below. Open the Workbench as you normally would.

Issue While editing graphics, the editor may "freeze" if you open the script window for a script object. This is because the window was last opened on a screen that is now not connected Product Line EcoStruxure Building Operation Environment EBO Graphics Editor Cause The position of the script window is saved along with other settings in a file on the PC. When the window was last opened on an external monitor, the window is displayed in the same position afterwards, ie. outside the area visible when the monitor is not connected. Resolution Make sure the editor is closed and edit the file. Path:% LOCALAPPDATA% \ Schneider_Electric_Buildi \ SE.Graphics.Editor.exe_Url_ [guid] \ [version] \ user.config  - [guid] can for example be: 5r4uwcrxydhrpcwgbhkkrpgxknpckzw5  - [version] can be 3.2.0.44 At the bottom of the file is "ScriptEditorWindowLocation". Set the value to e.g. 0.0 and save.

Issue Connecting a 4-20mA sensor to an analog input on the MPM Product Line EcoStruxure Building Expert Environment Multi Purpose Manager (MPM) Cause "Input Type" for an Analog Input can only be set to either "Volts" or Ohms" Resolution A shunt resistor is required to be installed across the input and ground terminals on the MPM in order to be able to measure the voltage drop over the resistor (see image below). An AIC object is then used to convert the voltage readings to mA reading. Set up AI and AIC as shown in the images below Note: The shunt resistor needs to be a precision resistor of 0.05 % and needs to be mounted as close as possible to the data acquisition system. Preferably directly screwed into the differential inputs, otherwise, you will measure the voltage over the resistor minus the voltage drop of the additional cable which affects the accuracy of your measurement.

Issue Some of the Continuum attributes in b3/i2 objects are not listed for binding in Script, one such example is the ElecValue of an input object, in Continuum, the difference between the Value attribute and ElecValue attribute is the former is the software value while the latter is the actual value read from the sensor. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause For reasons that are beyond the scope of this article, not all Continuum properties have been included for binding in Script   For example, the list of bindable properties for a b3 Analog Input is missing the ElecValue property as can be seen below   Resolution In a b3 Script or Infinet Script Program, there is a way to access any property (attribute as they are known in Continuum) of an object by simply referencing the property's name right after a binding variable to the object's value   Consider the situation that can be seen in the screen capture below...     Due to some strange failure the software contains an incorrect value for the input, but accessing the input's electrical value from a b3 Script program reveals the sensor is reading the room temperature correctly.   Below, screen capture of how this is accomplished in b3/i2 Script program     NOTES "theInput" is bound to the value of the "RoomTemperature" input. "theInElecValue" is bound for output to an AnalogValue in the b3 where the program will place the electrical value of the input We access the property by adding its Continuum attribute name right after the variable bound to the input's value, you will need to know the exact Continuum name of an object's attribute in order to access it this way. This works for any attribute that is accessible by Plain English in Continuum including the PriorityArray of b3 commandable objects.

Issue Is it possible to connect eComission SmartX controller mobile application to a SmartX controller with no WiFi available in the building and BLE(Bluetooth) not turned on in the SmartX controller. Product Line EcoStruxure Building Operation Environment Building Operation eCommisioning Tool Building Operation Room Controller (RPC) Building Operation Multi-purpose Controller (MPC)   Cause The eCommission SmartX controllers mobile application supports device connection through BACnet Wi-Fi and wireless Bluetooth connection. Resolution Install eCommission SmartX controllers on a computer, connect to the SmartX controller using an IP cable connected directly from the computer to the SmartX controller and enable Bluetooth on the SmartX controller.   Disconnect IP cable from the SmartX controller if there is one connected. Restart the SmartX controller, since it can’t reach the DHCP server it will get an IP address in the range of 169.254.x.x. Make sure the computer IP address is in the same IP range as the SmartX controller. Connect the IP cable directly from the computer to port 2 in the SmartX controller. Start eComission SmartX controller mobile application and connect to the SmartX controller. For details please see the video.

Issue Many campuses are configured with 1 BACnet Network ID number for Primary IP that is unique per building whether or not they are in the same IP subnet or multiple (with BBMDs). Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause When reviewing the Technical Reference Guide and searching "BACnet and IP Routing", it does not clearly explain the configuration and it also does not extend to multi-building systems using BBMDs. Resolution BACnet network numbers are assigned at BACnet routers, with a Range of 1-65,534 (where 65535 is reserved for broadcasts). Routed networks are assigned unique network numbers and can only have 1 router per network. Routed networks are usually BACnet MSTP, BACnet Ethernet, and Secondary IP networks. Standard practice is to have primary IP networks consisting of IP routers/devices in the same IP subnet or across multiple IP subnets joined by a BBMD and/or foreign device configuration uses the default BACnet network number 1.

Issue Continuum has a limit on the number of entries that can be added to the BBMD table in the bCX and CyberStation. Do the AS and ES servers have the same limitation? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS-P, AS-B) Building Operation Enterprise Server Continuum Cause Limitations must be known for engineering design. Resolution The number of BDT Entries you can add to the BBMD table in EcoStruxure Building Operation is limited only by the available resources, so for all practical purpose there is no limit. Device BDT (Broadcast Distribution Table) FDT (Foreign Device Table) ES only limited by memory 64 (up to v1.4) 600 (from v1.5) AS only limited by memory 64 (up to v1.4) 254 (from v1.5) ASB only limited by memory 50 bCX1 32 32 Cyberstation 1024 1024 Always refer to the Architectural Guidelines for the latest information

Issue Emailing alarms if Microsoft Outlook is not used on the site? Product Line Andover Continuum Environment Continuum Cyberstation 1.73 and above bCX 4040 Netcontroller II (9680) ACX57xx Series (ACX II) Cause The customers site IT system is unable to provide reliable Email communications from Microsoft Outlook on the Continuum Workstations. Resolution The documented Outlook support: Initially Full Microsoft Outlook or Microsoft Exchange was specified as the requirement 1.92 to 1.94 specified Microsoft Outlook 2007 for Windows XP and Vista (Full Microsoft Outlook or Exchange) 1.94sp1 to 2.03 specified Microsoft Outlook 2007 Microsoft Outlook 2010 (Full Microsoft Outlook or Exchange software package)   For further information on outlook versions see the KB article Outlook 2007 and Outlook 2010 with Continuum email alarms. Notes Only 32bit Outlook was tested/supported Continuum does not support MS Outlook Express for emailing alarms From v2.0 CyberStation has internal SMTP email options see  SMTP Email Alarm Configuration in Continuum 2.00 to 2.03 There are other email option for emailing directly from controllers. There is a feature in the bCX (also NetController II, ACX II) controllers to be able to email messages directly to a SMTP server either manually or via Plain English programs, although this is not directly linked to the Continuum Alarm system and would require a Plain English program to determine what emails are to be sent. See the "bCX1 Controller Technical Reference" Commissioning section for details on how to set up the controller to send out emails to a 3rd party SMTP email server.  There is also the Continuum SNMP Configuration guide for use with SNMP alarming with a Network Management System. Then in the CyberStation online help see the "SendEmail" function help on how to use Plain English to get the bCX (Netcontroller II or ACX II) to send out messages via email.  

Issue How to migrate ebo_db from an old PostgreSQL/TimescaleDB PC to a new PostgreSQL/TimescaleDB PC Product Line EcoStruxure Building Operation Environment PostgreSQL TimescaleDB pgAdmin Building Operation Workstation Cause When using External log Storage (the TimescaleDB in PostgreSQL server) in EcoStruxure Building Operation, it is often required to migrate the TimescaleDB (ebo_db) to a new PC or a different HDD due to the hard-disk space issue.   Resolution Stop the External Log Storage (TimescaleDB) from all the EBO servers (ES & AS’s). Using the attached zip file, extract the XML TimescaleDB Search Export and import this to the root location of your server.   The resulting search results will provide ALL servers' Timescale objects and show the status of the Event and Trend configurations. allowing you to multi-select and change the Event and Trend configuration settings quickly.  Use the CRTL key to only select the relevant servers. Alternatively, follow the steps below to locate these properties manually.    Note the Export is for version 3.2.3 Expand the ES Server, expand the System folder, and expand the External Log Storage folder. Right-click the TimescaleDB and select the Properties. Disable the Event Configuration & Trend Configuration and save. Repeat the above operation for all the other servers (AS’s) that are enabled for the External Log Storage. Create a new database in the destination External Log Storage server PC using the “EBO External Log Storage Installer” tool. Refer to page 5 “Database Management” section of the “EBO External Log Storage Installer.pdf” document for detail. Backup the “ebo_db” from the source TimescaleDB server PC using the pgAdmin 4 (refer to https://www.pgadmin.org/docs/pgadmin4/development/backup_dialog.html ), or refer to page 8 “Backup” section of the “EBO External Log Storage Installer.pdf” document for detail. Copy the DB backup file to the destination TimescaleDB server PC and restore the database using the pgAdmin4 tool (refer to https://www.pgadmin.org/docs/pgadmin4/development/restore_dialog.html ). DB Restoration may take a couple of minutes to a couple of hours depending on the size of the database. DB restoration results may show an error caused by pre-existing information in some tables, but it can be ignored. Once DB restoration is completed, make sure to check the timestamp of the oldest log data and the latest log data to verify the result. Start the External Log Storage (TimescaleDB) from all the EBO servers (ES & AS’s) using the search provided in Step 1 or manually as follows: Expand the ES Server, expand the System folder, and expand the External Log Storage folder. Right-click the TimescaleDB and select the Properties. Change the Database name, Host address, User name, and Password for the new (destination) External Log Storage server PC Enable the Event Configuration & Trend Configuration and save. Repeat the above operation for all the other servers (AS’s) that were disabled in the above step 1.