Building Automation Knowledge Base

Issue Firewall issues when trying to reach out to the activation server for a license Product Line EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Building Operation Licensing Firewall Cause If the corporate network has a very restricted firewall policy or rules, the port needed to reach and activate a license may be blocked. Note: The same license server is used for EcoStruxure Building Operation, Satchwell Sigma and TAC Vista software licenses. Resolution Open Port 443 (HTTPS) for the server hosting the license server, and ensure that the routing paths to the Flexnet Licensing server URL's are all fully open. The Licensing Server URL should be opened from the site, and it is:  https://schneider-electric.flexnetoperations.com ocsp.r2m02.amazontrust.com Ocsp.r2m02.amazontrust.com Ocsp.rootca1.amazontrust.com If the site of the old server has issues with non-secure communications or communications forwarding between the previous and the new server, a tool is available to configure EBO to only use the new server. See the Exchange Community article for the download: SBO License Setup Note: From EBO V2.0 only the new license server is used, port 80 is no longer required and HTTP is redirected to HTTPS.

Issue How does the import/export (IE) system work in the Continuum controllers? Product Line Andover Continuum Environment CyberStation All CXs All i2s, Infinet Controllers Cause Continuum controllers implement an Import/Export strategy in order to minimize network traffic when accessing the value of a point in a remote controller. The principle is that the value of a controller point that is referenced by other controllers on the network only needs to be sent out when it changes, much like the BACnet COV which stands for Change Of Value. The two parties involved in the IE transaction are the controller that owns the point (the owner) and the controller(s) referencing the point's value (the subscribers), a second CX controller may also be involved and acting as a router when a value is imported/exported from/to a remote field device under a remote CX. Resolution Read more in the attached document, Understanding Continuum IE System.  See how to correct Import Export tables KBA

Issue TGML graphic uses the NAM Standards component to display a SmartX Sensor Device with a dynamic cover model. The graphic always shows a blank faceplate instead of the correct face - 3 buttons, LCD, or Touchscreen. Product Line EcoStruxure Building Operation Environment SmartX Sensor Device (Living Space Sensor/Room Unit Device) NAM Standards Team Components TGML Library TGML Graphic Thermostat - SmartX Living Space Sensor - Dynamic AppRev1.02.05 Cause A script running inside the graphic component is expecting a well-formatted string representing the cover model on the cover model input binding. If that data is not delivered properly, the component defaults to a blank cover. Resolution Verify that the proper component is being used based on Sensor Firmware. Verify the proper IP controller firmware is installed to meet compatibility with the Host Server and also contain desired features. Once a controller is upgraded and the sensor has had time to upgrade, check the Sensor - Properties - Basic Tab - Application Software version. If greater than or equal to 1.02.05, then use Thermostat - SmartX Living Space Sensor - Dynamic AppRev1.02.05 Otherwise use Thermostat - SmartX Living Space Sensor - Dynamic   The TGML component should work as expected, but factors outside of the graphic can make it not work right. Click on the SmartX Sensor Device and look at Properties > Basic > Status Information > Cover model. Does that show a valid cover model (ex: SXWSCBXSELXX) or does it show ASCII gibberish? If showing nonsensical ASCII string, hotfix firmware is available to address this. Install firmware at or higher than 3.02.03.02109, which includes fix for Defect# 46054 and 47266 affecting the Cover Model SmartX IP Controller v3.02.03.02109 - Firmware Package File Release Date: 2021-Dec-19 https://ecoxpert.se.com/search?documentUUID=6b61d413-5cf8-47c0-ac4d-135391d375bf&title=SmartX%20IP%20Controller%20v3.02.03.02109%20-%20Firmware%20Package%20File Release Notes v3.02.03 - SmartX IP Controller Firmware Release Date: 2021-Dec-19 https://ecoxpert.se.com/search?documentUUID=1e29da8d-cf49-418d-92e5-e022bc4f33c7&title=Release%20Notes%20v3.02.03%20-%20SmartX%20IP%20Controller%20Firmware If the Cover Model is populated with a proper value, a previous firmware upgrade may have caused string values to stop writing properly through the TGML binding. There are two different resolutions to try in this order: Restart the AS-P Delete the SmartX Sensor Device (be sure to select "Keep references") and add it back as a new object with the same name and address.   The binding controlling the dynamic display of different cover models on the graphic can be overridden. Inside the TGML component are 3 groups named "3 Button," "LCD", and "Touchscreen." All are hidden. Find the proper face and change it to default to Visible. Find the Bind named "CoverModel" and delete the binding and script beneath it. This is what is responsible for auto-changing the cover and is no longer needed.

Issue Modbus RTU Serial Device (RS485 - Slave) address greater than 247 Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server (AS, AS-P, AS-B)  Modbus RTU Master RS485 Network Cause Third party Modbus device has an address range between 248 and 255. Resolution For Modbus master/slave RS485 networks, the third party device must be in the range of 1 to 247, this is the Modbus RTU standard. This would apply not only to EBO but to other Modbus master/slave networks.   The KB article Modbus basics explains this amongst other Modbus topics.   If the third party Modbus slave device cannot be changed to an address to within this range, then contact with the product vendor may be required.   For TCP devices see the KB article Modbus TCP Device (Slave) address greater than 247.  

Issue How Permissions works in EBO Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Software Permissions are used to control user activities in a software application. For example, permissions can be setup to manage the type of data and commands the user has permission to within a workspace, panel, or domain. Resolution EBO software permissions comprise path permissions and command permissions. Path Permission: Path permissions give a user or user account group basic permissions to the objects defined in a path. The permission level set on a path applies to all sub levels unless you set a new permission level for a sub level. Command Permission: To make the system even more flexible and useful, you can assign a user account group with special command permissions. Use the command permission to control exceptions from path permissions that allow or deny actions on specific commands. Command permissions will not restrict a user from specific properties of a given window. They function to remove items from Action or Right Click menus. EBO uses the following basic rules to interpret software permission priorities: The path permission settings of lower branches overrule the settings of higher branches within a user account group For example, a user account group has the Read permission to the path /Trend_Logs and Full Access permission to the subbranch /Trend_Charts. Users in the user account group have permission to modify the objects in the /Trend_Charts but can only view the objects in the superior /Trend_Logs. If the path /System has the permission level Read, and the subbranch /Alarms has the permission level Full Access, the users in the group have full access to the objects in the /Alarms path. The highest permission rule wins between user account groups. For example, if a user has inherited the permission to accept an alarm from one group, this overrules settings from other groups that deny the user the permission to acknowledge alarms. The software permissions for a single user account overrule the permissions of any inherited user account group permissions. The path permission rules also apply to the basic commands Create, Copy, Paste, Cut, Move, Rename, and Delete. For example, you only need the Read path permission level to copy an object but you need the Full Access path permission level to paste an object. See the table for more details.       Download Software Permission.pdf, the detailed guide about how permission works in EcoStruxure Building Operation (Formerly known as SmartStruxure) and how to make it work.  Check out the SmartStruxure Software Permissions Quick-Help video on the Exchange.

Issue PCT error 'Hardware virtualization is not enabled. Please enable in BIOS before continuing' Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool Windows 10 Cause Windows Hyper-V is enabled Resolution Firstly, in BIOS check and confirm the computer’s Hardware Virtualization is enabled.  See the following article which may provide assistance with this.  PCT Intel Processor Virtualization.   Once confirmed that this feature is enabled within the bios then, within Windows, open Control Panel\All Control Panel Items\Programs and Features, in the left pane select “Turn Windows features on or off” Check to see if Hyper-V is enabled: If it is, uncheck the checkbox next to Hyper-V. This change will require the computer to be restarted for the change to take effect.   If Hyper-V does not deactivate properly and gets launched automatically at startup, you can instead disable Hyper-V through an elevated command prompt with the following command: bcdedit /set hypervisorlaunchtype off  

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 Finding the correct procedure for migrating Infinet controllers from a Continuum controller fieldbus to an AS-P. Product Line Andover Continuum,EcoStruxure Building Operation Environment Continuum Cyberstation Building Operation Automation Server Premium (1.9 onwards) Building Operation Automation Server Bundled (1.9 onwards) Cause The wrong procedure has been followed which is not the approved and tested procedure to be used when migrating Infinet controllers from Continuum to EBO.  Resolution Procedure for Converting / Transitioning the Infinet Bus Prior to migrating the Infinet The RS-485 network cable should be routed in a continuous daisy chain bus configuration. There should not be any stub connections, stars or ring configurations. The bussed cable should pass through each node to be connected with no splits or branches in the cable network. Repeaters can be used to achieve the star, distributed star (backbone with clusters), off of the backbone. For additional information, review the article: EBO Webhelp Cabling Using the conversion tool and other engineering efforts, create the AS-P database for all Infinet devices, Infinet, Interface items, etc. in either a live AS-P or in the PCT. At the site From Continuum CyberStation,  the following must be completed to each Infinet controller that you are moving to an AS-P. Upgrade all Infinet devices that are going to be converted to the latest firmware version.  Firmware upgrading capability will not be available in EBO until a future release. Clear the memory of all Infinet devices involved before relocated to the AS-P com port by editing the controller object and selecting Runtime > Reset. If the conversion was done on the PCT, deploy the AS-P. Verify that the AS-P firmware is 1.9.0.73 or higher. Disconnect Infinet bus from the Continuum controller com port(s). Move the Infinet bus (busses) to the corresponding RS485 port(s) on the AS-P. Confirm that the Infinet devices are all showing online under the AS-P Download the Infinet devices. * Backup all Infinet devices to flash memory.   *  If the Infinet devices share data with other Infinet devices then it may be necessary to repeat this step in order to establish the complete Import/Export table. PLEASE NOTE The above steps are important! If not followed, offline and bus problems can occur. There may be a desire to skip the rest of the controllers, but the steps must be followed The likelihood is high that there will be substantial difficulties in getting the i2 controllers online and in a stable state to accept the download files. All of the Infinet controllers must be reset in Continuum before moving the bus to the AS-P.  The controllers should then be backup up to flash memory to ensure that they do not revert to their Continuum configuration following a cold start. If problems occur that make it necessary to abort the migration process and return the controllers to the Continuum system, all of the Infinet controller must have their memory cleared before re-attaching the bus on the comm port of the original Continuum controller.  For those controllers which have not established communications under the AS-P, this will mean performing a hard reset at the Infinet controller hardware. At no time should the Infinet bus be connected to the both the AS-P and the Continuum controller at the same time as this  confuses the Infinet controllers causes communications issues that will take some time to resolve. Please also see the "Infinet under the hood" community post Continuum Conversion Tool NOTES V3.0.x and v3.1.x Conversion Tools should not be used. The Workaround is to use the 2.0 Conversion Tool then upgrade. (The Conversion tool was fixed by v3.1.2.6000 (CP5)) V3.2.x onwards the Conversion Tool operates correctly v4.0.3 has an issue converting Infinet controllers, 4.01 or 4.02 should be used instead Now fixed in v4.0.3.5005 CP3(Known Issues) v3.x outperform 4.x, 5.x and 6x.(known Issues). The Workaround is to convert the dmp file in CCT 3.x then upgrade the DB to the expected version in PCT or AS-P.

Issue How to activate an embedded license for a SmartX Server using the Device Administrator when the computer with the Device Administrator is not connected to the internet. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Cause Device Administrator is used to manage licenses on SmartX servers The following features of a SmartX server need licenses: SmartDrivers SNMP Notifications Personal Dashboards TimescaleDB MQTT Resolution Building Operation 2022 Note: The offline entry of the Activation-ID License items is not all visible - ONLY the first 5 are shown.  This makes entering this information impossible. This has been fixed in the Maintenance Release 4.0.2 of the Device Administrator.  After activating the embedded license offline and transferring this license to the servers, a license violation may be still shown.  The license status should update within 24 hours.  Perform a warm start and then a Refresh License Status on the selected servers to force this update.   If an error is seen in the progress status indicating ASEmbeddedAPI internal error during the offline activation, check the following Embedded license activation fails - Communities to correct the corrupted storage.   This video will show how to activate an embedded license for a SmartX Server using the Device Administrator when the computer with the Device Administrator and/or the server is not connected to the internet. IMPORTANT NOTES: You need to be connected to the SpaceLogic (SmartX) Server using IP (select +Add server on Device Administrator).  It cannot be connected via USB. Ensure always to run the Device Administrator with admin privileges. Select "Run as administrator." Should Device Administrator be running on a computer that has internet access, then there is no need to swap between online/offline computers.  The offline activation process can be run from the same Device Administrator with no need to change computers.  The offline workflow is always the same and detailed on the webhelp topic Offline Activation of Licenses Workflow  The video below shows version 3 licenses. In Version 4, there are a few more license features and quantities required to enter.  The following article may assist in entering this information. License Features list for version 3.0 and 4.0 Product names     At the end of the video session, you will be able to: Create a request file using the Device Administrator on an offline (to the Internet) computer. Activate request files from the Device Administrator on a PC connected to the internet. Send response files to the SmartX Server from the offline Device Administrator.

Issue Where are example Plain English programs and functions stored for typical BMS applications? Product Line Andover Continuum Environment Plain English (PE) Functions and programs. ACSM, PID, Optimiser, ISM, First Aid. Standards Bacnet Optimiser Cause It is always easier to write your Plain English programs starting from documented examples rather than a blank page. What is available? Resolution The following link is to a .zip file containing various BMS standard modules originally developed by the UK Application engineers for Infinity SX8000 and were known as the Infinity Standard Modules (ISM's), they were then updated to Andover Controls Standard Modules (ACSM's) for Continuum. These modules are example functions or building blocks that can by used globally by application engineers to provide the control and monitoring appropriate for your own buildings. Link: Click here. In addition to these functions other examples are in the online help for the corresponding Plain English keywords, and other applications can be found on the Forums; see Sample PE functions and programs for further details. For Smart Sensor examples see Example programs for Smart Sensors TTS-SD-LCD-1 and TTS-SD-LED-1 for details. For example Security programs see the Download Center link, Click Here.

Issue The binding between an Enterprise Server and Automation Server or between two Automation Servers shows Unresolved Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Binding Diagnostics Cause The communication between the two servers is incorrectly configured, blocked by software such as firewalls or antivirus or another application is using the port. Resolution For Firewall Issues: Ensure the Windows firewall on the Enterprise Server PC is set up correctly, for example follow Creating Windows Firewall rules to allow Building Operation to communicate on the TCP port to set up inbound and outbound rules.   Alternatively configure the Windows firewall using the Firewall Config tool on all PC's having EcoStruxure software installed. Problems with firewall settings can arise if the Enterprise Server PC is removed during the commissioning process and the firewall settings swap between Private Networks and Public Networks. For example All the Automation Servers may appear online, but the "Unresolved" bindings issue may be seen. Automation Servers cannot be restored via the Enterprise Server If a suitable option temporarily disable the firewall to see if it fixes the issue.   For 1.4 or 1.5 Servers with a name containing the "&" symbol: Ask Product Support for Hotfix R1.4.1.16201 (or later version) for version 1.4 and R1.5.0.1601 (or later version) for version 1.5.    For other Causes: Follow these troubleshooting steps in order until the issue has been resolved. Check that the ES IP address is the same as the PC IP address.  If they do not match, follow How to set the Enterprise Server IP address to change the ES IP.  All ports must be open between the ES and AS, for port numbers search "Network Ports" in the Information Technology System Planning Guide. If the address of the ES is a domain name, try using the IP address instead. If there are more than one network adaptor on the ES can, for example, take the address of a wireless adaptor, VMware virtual adaptor or VirtualBox adaptor.  The ES should be using the NIC adaptor, either follow the link in item 1 or disable the other network adaptors. Right click on the ES and select Advanced > Repair Server Communication.  This should update the Communication tables of the servers. Detach the automation servers from the ES and then add the automation servers back.  Follow Unable to add an Automation Server underneath an Enterprise Server. Select each server and click on the Communication Tab.  If communication is valid, it should list the details of every other server. Try to disable any network monitor function of anti-virus software on the computer. If a Schneider laptop is used, right click the Trellix software in the system tray and Enable Firewall Timed Groups. Although not a supported architecture if a user installs the Enterprise Central and Enterprise Server on the same PC with default settings the ports will conflict.  Either remove the unsupported Enterprise Central or if for testing stop the service and set appropriate usable ports.    

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 Some IO modules status showing as 'Blacklisted device detected" or "Address shift detected" or a system alarm is received indicating the condition. AS trace logs may show one of the following entries... 2015-08-18 17:41:02.675 [1256862784] nsp.pin.cio.IODevice Module at address 14 is reporting Internal Error Code 32 2015-08-18 17:41:02.757 [1256862784] nsp.pin.cio.IODevice Module at address 28 is reporting Internal Error Code 32 2015-08-18 17:41:02.825 [1256862784] nsp.pin.cio.IODevice Module at address 12 is reporting Internal Error Code 32 2015-08-18 17:41:02.869 [1256862784] nsp.pin.cio.IODevice Module at address 13 is reporting Internal Error Code 32 2015-08-18 17:41:02.951 [1256862784] nsp.pin.cio.IODevice Module at address 15 is reporting Internal Error Code 32   2015-06-18 10:05:13.912 [1255584832] nsp.pin.cio.CIOException Error: Bad_Address (0xb0000), module Automation_Server_Io_Bus(31), moduleCode 0, dispString "AS address is invalid", techString "nsp_servers/plugins/CentralIOPlugIn/CIO/source/IOManager.cpp line 460" 2015-06-18 10:05:20.789 [1255584832] nsp.pin.cio.IOBus IOBusServer::run: Caught CIO exception from slot 3   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause One or more terminal base may have to be replaced. Intermittent IO connection (typically in S-cable). Resolution Follow this document or Blacklisted Device Detected for steps to resolve the problem.

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 Need to replace and upgrade AS (Classic) to AS-P-NL. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS) Building Operation Automation Server Premium non-LON (AS-P-NL) Cause From EBO v3.2 the AS-P-NL is available, there is a need to upgrade an AS (Classic) but the AS is only supported up to v3.1. Resolution A lower version of EBO can be installed into the AS-P-NL e.g. from v2.01, but this must only be for the purpose of upgrading the database.   Therefore the upgrade path can be as this example shows, there is a requirement to upgrade an AS from v1.6: Upgrade AS v1.6 to v3.1.x) . Backup the AS. Install v3.1.x) on AS-P-NL ( x needs to be same as in step 1). Note: Installing 3.1.x on an AS-P_NL is only for the purposes of upgrading the database, the following steps 4. and 5. must be completed . Restore backup on AS-P-NL. Upgrade to v3.2 or later.   For details regarding upgrade paths see article - Upgrade path from version 1.0 to current version 

Issue SE8000 Best Practices Product Line Field Devices, EcoStruxure Building Expert Environment SE8000 Cause Best Practices for commissioning SE8000 room controllers Resolution The following information has been contributed by a field engineer and their experience to assist others in commissioning the SE8000 device. It brings together or provides leads to various articles that can be found on the Download Center. SE8K Programming Tutorial v1.1

Issue Trouble synchronizing the time of the Automation Server or Enterprise Server to a NTP server or between each other Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Enterprise Server EcoStruxure Building Operation Automation Server Cause The Enterprise Server and the Automation Server (ASP/ASB) do not synchronize time to each other, they must use an NTP server for synchronization Resolution The information below is mainly concerned with synchronizing the time setting but not the actual time.   Overview To synchronize the server times an NTP Server will be required, they do not synchronize time with each other. A common misconception is that the Automation Servers sync time with the Enterprise Server via server-to-server communications. To find an external NTP server consult support.ntp.org . Alternatively, an existing internal NTP server can be used or consult Setting up a Local / Internal NTP Server to configure the Enterprise Server computer as a time server The time settings on the Enterprise Server are configured through the operating system settings on the computer where Enterprise Central is installed.  EcoStruxure Building Operation cannot be used to configure the NTP server for the Enterprise Server. Please refer to Network Time on WorkStation, Enterprise Server, and Enterprise Central To find the Network Time Protocol (NTP) configured on a WorkStation, Enterprise Server, or Enterprise Central computer open a command prompt and enter w32tm /query /peers. If configured the peer NTP server(s) will be listed If you need to ensure an NTP server is actually running on certain IP or DNS address, please reference Ensure IP or DNS address is valid NTP server The time settings on the Automation Servers can only be configured via the Workstation. As per the image they can be configured to look at an NTP server (1) or set manually (2). For synchronization, they must use an NTP Server. Please refer to  Network Time Server on an Automation Server on Webhelp Starting in version 1.5, the time adjustment depends on how much the Automation Server drifts from the NTP server. The faster the Automation Server drifts, the more frequently the time is updated.  Please refer to How often will an Automation Server ask the NTP server for the time?  If the time server is a URL, such as time.nist.gov, then it is critical that a Primary DNS is set for each Automation Server, and possibly a Secondary DNS via Device Administrator. Without a DNS, the Automation Server will be unable to resolve the URL to an IP address. Please refer to Configuring the Automation Server IP Address on Webhelp The time displayed for a server in Workstation (Properties -> Basic) will reflect the time zone of the local computer that Workstation is installed on. All events and alarms will be automatically modified to match the time of the workstation that was used to log into the server. The "Server time" will represent the date and time of the server adjusted to client local time zone, while the fields below "Server time" represent the settings of the Automation Server.   How to synchronize date and time settings on multiple Automation Servers   IMPORTANT: Only the time settings are synchronized via the Lead/Shadow configuration, the time itself IS NOT synchronized via the Lead/Shadow but rather by all servers synchronizing with the configured timer server.   The synchronizing of multiple Automation servers can be achieved with a lead/shadow relationship. The primary and secondary network time server settings for connected shadow Automation servers are defined on the Enterprise server. Setting up the Primary and secondary time servers in the Enterprise Server only passes those configuration settings to the AS controllers, it does not send the actual time and date value.   Select the Enterprise server (1), click the Date & Time tab (2), select Enable (3) and enter the Primary time server (4) and, if used, the Secondary time server (5) the Automations Servers will use. Ensutre the time zone for the Enterprise Server is set correctly (6).   Save the settings  From EBO version 2.0 all Automations Servers are automatically configured to shadow the date and time settings configured in the Enterprise Server. To verify this expand the System folder of an Automation Server and select Time Settings -> Date and Time (1). Observe the Date and Time are Shadow-Read only (2), replicating the Enterprise Server settings. Attempting to change any of the settings, other than the Lead object (3), will result in an error. All the Automation Servers will be 'looking' to the same Primary (4) and Secondary time servers, i.e. they will all receive the same time and be synchronized Similarly, select the Time Zone (1) of the Automation Server in the System Tree; this will also be shadow-read only (2). The lead object is set to the Time Zone on the Enterprise Server (3) Before EBO version 2.0 the Automation Servers were not automatically set to shadow the Enterprise Server settings but this could easily be achieved en masse using Search . In the Search box in the top right corner of the Workstation, type "Date and Time" and click Search (1) to find the date and time object of all connected servers. In the Search view select the servers (2) that require their Date and Time settings synchronized to the Enterprise Server, the Enterprise Server does not need selecting. Select the Time tab (3) and then click the triple dots (4) to navigate to and select the Date and Time object on the Enterprise Server (5)   You may need to stop and start the Enterprise server to get the configuration settings to pass down to the shadow Automation servers Note: To set up synchronization of the time zone settings follow the above search steps for date and time but search on Time Zone Tip/Tricks To see the time of on the Enterprise Server and multiple Automation Servers use the Search to find the Date and Time object (1). Individually select each server (2) and then drag the Date and Time object (3) into the Watch Window (4) It is the Automation Server that initiates the synchronization. To check the Automation Server communication settings select the Automation Server (1) and in the Communication tab (2) select the Enterprise Server (3) and make sure the Automation Server has the correct IP address (4) To check the Enterprise Server communication settings select the Enterprise Server (1) and in the Communication tab (2) select each Automation Server (3) and make sure the correct IP address is specified for each Automation Server (4).  If a firewall exists ensure that the ports are open so the Automation Server can connect to the Enterprise Server. Please search for the EcoStruxure Building Operation IT Reference Guide on Exchange for details Further Information Release 1.2.0 and higher Until the time is set, b3 data will not update in the Watch Window Until the time is set, BACnet COV will not be functional Automation Server time does not synchronize directly with the Enterprise Server. Instead, all servers can synchronize to the same accessible time server To adjust the Automation Server time, time zone, and DST, access to the Automation Server is through a WorkStation

Issue Measuring dry bulb temperature and relative humidity and need to use them to calculate the following Enthalpy Wet Bulb temperature Dew Point temperature Product Line TAC Vista, Ecostruxure Buildings Operation Environment Function Block applications Cause Need to calculate Enthalpy, Wet Bulb Temperature, or Dew Point Temperature.  These values are typically used to compare the latent heat in the outside air versus inside air for economizer cycles, in chilled water applications where condensation must be avoided, or in humidity control applications. Resolution Enthalpy - the total energy of both the dry air and water vapor per pound of dry air. Wet Bulb temperature - the temperature a volume of air would have if cooled to saturation by evaporation. Dew Point temperature - the temperature to which a volume of air must be cooled for water vapor to condense into water. Download the appropriate HFB below: Psychrometric Calculations in US Imperial Measurements Psychrometric Calculations in SI Metric Measurements

Issue MBus to Modbus TCP Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Mbus Modbus Cause How to read MBus devices into a BMS System using Modbus TCP Resolution There are different methods, but these are generally using a Modbus RTU / Mbus gateway and then converting it to Modbus TCP. The following ADFweb solution allows Mbus to be read directly into a Modbus TCP device. Click here for the datasheet.

Issue During installation of hotfix for EBO you get a "Hotfix file signature validation" error saying that Device Administrator cannot verify the issuer of the file signature's certificate.   In older versions of Device Administrator you might get an alternative error message "Invalid hotfix file" saying that the file does not have a valid Schneider signature. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Device Administrator Offline system Version 3.1 and later Cause EBO hotfixes for SmartX Server are signed with a certificate to ensure that only valid files can be used. This certificate must be validated before you can use a new PC to install a hotfix. If the PC has not had any internet connection while previously installing a hotfix or does not have an internet connection, the certificate cannot be validated and hotfix installation therefore fails. Resolution There are two solutions Solution 1 Connect your PC to the Internet and install the hotfix on a SmartX Server. The certificate is validated, and the PC can subsequently be used to install hotfixes on other SmartX Servers, even if you are offline. Solution 2 You can manually import certificates and CRL (Certificate Revocation List) Download and save the following files: http://s1.symcb.com/pca3-g5.crl http://sv.symcb.com/sv.crl If the above URL's are blocked by your browser please download them here or the attached ZIP file.  Start a command prompt (cmd.exe) as administrator. Browse to the folder where the files from step 1 are stored. Run the following commands: CertUtil -AddStore CA pca3-g5.crl CertUtil -AddStore CA sv.crl Export host, intermediate, and root certificates from the hotfix file. Install the 3 certificates with the default selection. Restart Device Administrator and install the hotfix. Video for step 5 and 6:

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.

Issue Unable to establish communication between the enterprise and automation servers through the TCP Port 4444. Values are not being passed between the enterprise to the automation servers or between automation server to automation server. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Workstation Cause Windows Firewall is not allowing inbound or outbound information from passing through the TCP port 4444. Resolution First download and run TCP View. With TCP View running, sort the list by the Local Port and find all devices that are talking on port 4444. If the automation servers are in a state of LISTENING then rules must be created to allow communication. Copy the file path of SE.EnterpriseServer.exe in order to create the rules. This can be found by right clicking on one of the SE.EnterpriseServer.exe process > Process Properties... (C:\Program Files\Schneider Electric\StruxureWare 1.2\Enterprise Server\bin\SE.EnterpriseServer.exe) If the automation servers are in the state of ESTABLISHED, then take a look at Binding between ES and AS or two AS shows Unresolved and "Communication Failed" Alarm occurs when Adding an AS. Source: /Server 1/Servers/ASL/System/Server Communications/Models/2deef04c-05d1-41ae-9c3f-f84a9f7e0b41 for more troubleshooting help.   Change Windows Firewall Settings to Allow Programs Go to Start > Control Panel. Click on Windows Firewall. Click on "Allow a program or feature through Windows Firewall" on the left hand side of the window. Find "StruxureWare Building Operation" in the list of programs and make sure Home/Work and Public networks are selected.  Note: If you do not have permission rights to make changes in this area of Windows, move on to the next section where you can set up inbound and outbound firewall rules.   Creating Inbound and Outbound Windows Firewall Rules Go to Start > Control Panel.  Click on Windows Firewall. Click "Advanced settings" on the left side of the window. Select Inbound Rules on the left side of the window and then click New Rule... on the right side of the window. On the first screen of the New Rule Wizard, choose Program. Click Next. In "This program path:" either browse to SE.EnterpriseServer.exe or paste the file path that was copied earlier from the TCP View into the box. Click Next. Select the option to "Allow the connection". Click Next. Leave Domain, Private, and Public checked unless otherwise desired. Click Next. Name the rule StruxureWare. Click Finish. Select Outbound Rules on the left side of the window and then click New Rule... on the right side of the window. Follow steps 5 through 9 to create the Outbound Rule. Note that the SBO Firewall Config tool on the community can be used to automatically create the required firewall rules.

Issue Understanding and Troubleshooting Modbus Product Line EcoStruxure Building Operation, TAC IA Series, Other  Environment All Modbus environments. Cause Modicon first introduced Modbus in 1979. Modbus is an open standard,and it is the most widely used in the industrial environment. Modbus is publicly available and,due to its simplicity, many manufacturers use Modbus as a solution for integration in their own products. Many commercial products and systems support the Modbus RTU and Modbus TCP protocols. For further information, visit the Modbus website at http://www.modbus.org. Resolution For a brief understanding on Modbus and how to troubleshoot Modbus, refer to the Modbus Troubleshooting PDF