Building Automation Knowledge Base

Issue Using Download Wizard 32 with Application set to Clear Memory, one will get an error that "The application file could not be found! Product Line EcoStruxure Building Operation Environment Building Operation Workstation Xenta Programmable Controller Cause EBO Workstation does not include the Lonm<Model Number>.MTA file. Resolution There are two solutions: Create a minimal MTA file for the device type. Open Menta Editor Change the device specification for the appropriate Xenta Type. Add one PVR block Save the file. In DWiz, change Application selection to Download New and Browse in the new file. Perform the steps again with the expected files in the same folder as DWiz. Download the attached Lonm.zip (derived from Menta 5.1.9) Extract the files in the zip to the same Workstation folder where Dwiz.exe is found. Sample Location: "C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 3.2\WorkStation\DWiz.exe" Perform the download again with the same Clear Memory selection under the Application section.

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 Correcting failed links between programming objects after upgrading files from .vsd to .vsdx Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech Building Operation Workstation (WorkPlace Tech Editor) Cause After existing .vsd files from pre-WorkPlace Tech 5.10 versions can have corrupted links that stay red when programming objects are added or modified. Resolution This video demonstrates how to correct binding failures that can occur when existing Visio drawings are converted from .vsd to .vsdx format when upgrading to Workplace Tech 5.10 and EBO 4.0 and newer WorkPlace Tech Editor. Note: The objects in the original drawing will no longer show a Master Shape reference (below) The frame around the object appears a little different as well.  The Mega Master will not be changed so this has no effect on the performance of these objects.

Issue Receive error "Property value out of range" when creating a BACnet interface on the Enterprise Server   Following problems after upgrading SmartStruxure servers to 1.5: Attaching an Automation Server to or detaching it from an Enterprise Server will fail with “Property value out of range” error. Changes to the ~/System/Interface Manager/BACnet fail to be propagated lead-shadow functions through to the child servers. Automation Server controllers dropping offline following an upgrade to 1.5 (BACnet command priority related  also may see numerous "Changeset Rollback errors") Product Line StruxureWare Building Operation 1.1, 1.2, 1.4, 1.5 and above Environment Enterprise Server (ES) BACnet IP Interface Windows XP, Windows 7 and Windows Server 2008 R2 Cause Their may be various items that generate this error, checking the Enterprise Server (ES) system log in the Software Administrator may assist in pin pointing the error.  If you see an error that ends with ~/BACnet Interface/IP Network, then this error is generated when their is no valid IP Network.  For SmartStruxure 1.5 or above or planning to upgrade from 1.4 to 1.5 (and above)  This issue only occurs if a BACnet interface is used and the site has changed the BACnet "Default Priority Level" from the default value of 16, to 8 or a smaller numeric value in the Automation Server while running in V1.4. The "Property value out of range" message relates to the new Force priority level in 1.5 and the Default priority level in 1.4.1 being mismatched. Resolution The ES must be connected to an IP network. To resolve this error follow these steps: Close all Workstations (if running) Connect the Enterprise Server to a valid IP network (with a valid IP address). Stop and Restart the Enterprise Server service through the Software Administrator application. This should now allow the BACnet Interface to be created successfully For SmartStruxure 1.5 or above or planning to upgrade from 1.4 to 1.5 (and above) Please refer to TPA-SBO-14-0005.00 Before upgrading to 1.5 make sure the "Default Priority Level" within the Automation Server is set to 9 or higher.  If the system has been upgraded with the incorrect values, then: If the site uses single servers, or the ES/AS communication still operates correctly, then this can be corrected by changing the setting in both the AS and the ES to a value of 9 or higher.   If after upgrading a multi server configuration and the AS does not stay online, then a Hotfix can be used fix the problem using the following steps: Apply the hot fix #1.5.0.4301; available from Product Support Services Fix the multi-server (by detaching/re-attaching the servers) Correct the two properties (AS and ES). WARNING: It is essential for any BACnet system at 1.5 or later that the "Default Priority Level" must have a larger numeric value than the "Force Priority Level, otherwise some BACnet functions may not behave as expected. Note: This also applies even if the hot fix has been installed. The effects of not setting the Default above the Force Priority level are: If Force Priority Level is equal to the Default Priority Level: Changing the Value of a BACnet value or a BACnet output object will cause the Value to appear Forced. This applies to the BACnet objects in both SmartStruxure servers and those in 3rd party BACnet devices.   If Force Priority Level has a larger numeric value than the Default Priority Level: Changing the Value of objects mentioned above will cause the Priority Override icon overlay to be turned on next to the Value property in the WorkStation’s property grid.   

Issue Steps on how to setup BACnet Time Synchronization to 3rd Party BACnet controllers. Product Line EcoStruxure Building Opertaion Environment SmartX Enterprise Server (ES) SmartX Automation Server (AS) BACnet Cause It is not always clear what is required to setup BACnet Time Synchronization and how to confirm that EcoStruxure Building Operation is actually performing it properly. Resolution To use the Time Synchronisation you will need to bring the 3rd Party BACnet device (Eg. Continuum bCX) under the EBO BACnet Interface -> IP Network: Go to the BACnet Interface Time Synchronization Recipients Tab. Add a new Local time synchronization recipient with the '+' button. Select recipient type as 'reference' In the Recipient device object reference field browse for your BACnet Device. Press OK and then save the changes. Right-click on the BACnet Interface and select send time sync now. This will send out an unconfirmed-req TimeSynchronization to that specific Device only.   Test Scenario with a bCX setup as a third-party BACnet controller You will see a unconfirmed-req TimeSynchronization packet being sent from the ES in WireShark but with no response from the bCX.  You may not see responses back from other 3rd party devices. The time in the bCX should be seen to change from within Continuum, (assuming it was incorrect in the first place) 

Issue Removing software from a PC may leave behind unused / old registry entries and folders from the removed software, this in some cases may prevent software re-installation Product Line Andover Continuum,EcoStruxure Building Operation,Satchwell BAS & Sigma,Satchwell MicroNet,TAC INET,TAC Vista Environment All supported Operating Systems Cause This is due to the windows uninstall program not fully removing all elements for the software. Some of this is due to windows thinking the the software may have been removed unintentionally and therefor all the previous settings will still be saved in case of  re-installation. For example, when SQL is uninstalled the program folders that contain the database will remain intact. This may be an issue if, for example, the software is removed due to a problem with the original installation. This is when a complete removal off all components and registry entries may be needed. Resolution The best solution for removing all the unused registry entries is to use a program designed to remove obsolete registry entries and temporary files. Some examples of these are: CCleaner, which will allow you to clean up your PC by removing past installation components. Revo Uninstaller  which is useful for removing redundant folders / files / Registry entries.   It may be useful to use both of these programs to ensure a complete cleanup. Revo Uninstaller can be used to remove unused software and then CCleaner to get rid of all the Temp files etc.  Finally remove the relevant folders from within the windows explorer, Example: C:\Program Files (x86)\Continuum Once done you should then be able to install a fresh clean copy of the application software. This solution is current in all versions of Windows including windows 10  

Issue Are there drawing templates available for AS’s, modules, RPC etc for use in BMS wiring diagrams. Product Line EcoStruxure Building Operation Environment Building Operation equipment Cause Need for CAD drawings of PS, AS, or I/O Modules Resolution Drawings in AutoCAD format (DWG, DXF) are available on the EcoXpert Extranet. DXF files are able to be imported into Visio.

Issue Content Types are not working correctly. A Content Type that was just created appears under the ES but not under the AS in which it was created in. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Premium Building Operation Software 1.9 or greater Cause Problems with or changes to the network configuration are affecting both the function and the lead shadow relationship of Content Types. Resolution   The following video will help us, Understand the Lead/Shadow aspects of Content Types Diagnosis and correct possible issues regarding the Lead/Shadow Online help topic for further information is also available here: Content Types (se.com)  

Issue How to perform the activation of an embedded demo license Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Cause The embedded demo License is a temporary license used for demonstration purposes, training, site engineering, when waiting on a permanent license order, or license support. This license file has a .Bin extension and can be downloaded from the EcoStruxure Exchange (ecoxpert.se.com) and is valid for a limited time (3 months). Resolution This video will demonstrate where to download, and how to activate an embedded demo license on an Automation Server using the Device Administrator.

Issue MQTT data points are no longer published to MQTT broker with "MQTT - Buffer overflow" alarm. System alarm: Buffer overflow - Not all MQTT messages have been sent Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause Long MQTT queue can be caused by, too many variables define in MQTT data groups, fast publishing, i.e. low interval or low delta value, Low CPU and RAM resources, or slow network. Resolution Once MQTT Buffer overflow alarm is generated, the below configuration shall be checked: Data points interval value, if the interval is enabled, make sure it is not a very low interval. Data points delta value, for event driven, make it is not very low value, especially for fast changing variables. Review the network performance. Make sure that the EBO server has sufficient CPU and RAM resources, and check Architectural guidelines for the effect of the Number of MQTT Data Points on the CPU Load. For Automation Server, the system memory usage should never exceed 80% and CPU usage should stay below 60%.

Issue There is no fully detailed explanation of how to install an SSL Certificate from an External CA Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause When trying to install an SSL certificate from an external CA can fail Resolution Configure a DNS name for the AS/ES (This prevents the certificate from being locked down to a specific IP. I.E. Configure an A record for "AS_Name".com Purchase SSL Cert through a 3rd party, or use your organization's internal CA/ root CA Download and install OpenSSL or can use OpenSSL installed with EBO  Run Command Prompt as an administrator Use command "cd c:\program files\OpenSSL-Win64\bin Use OpenSSL to generate a CSR in order to obtain the certificate from the 3rd party openssl req -new -newkey rsa:2048 -nodes -keyout EcoStruxure.key -out EcoStruxure.csr Follow the prompts to fill out the information for the CSR Supply CSR, other certificate contact information, and a means of validating the request to the 3rd party CA Verify identity with CA (this may not be necessary if you use your company's internal CA/ root CA Receive host and intermediate CA certificates from 3rd party CA Make sure the CRT/CER files are in the C:\Program Files\OpenSSL-Win64\bin directory of Windows Explorer Use OpenSSL to convert the CRT or CER files into PEM files, as PEM is the only format EBO will accept openssl x509 -in certFileName.cer -outform PEM -out convertedCertFileName.pem Use OpenSSL to convert the private key file generated at step 6 from .key to .prv openssl rsa -inform pem -in filename.key -out filename.prv Run WorkStation as administrator In WorkStation, Control Panel > Certificates click on the server you are trying to add the cert to, either an AS or ES. Click on Manage Certificates > Add Existing  Put in a name for the certificate (it can be anything you'd like) Click the ellipsis next to host, intermediate, and private to add the appropriate PEM files and click ok  Select the newly added certificate from the drop-down and save the changes to activate Warm start the server After this process is completed, verify that connection to WebStation via HTTPS shows a secure connection/trusted certificate.

Issue In EBO BACnet device discovery, how is the BACnet MAC address defined? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause A BACnet device is uniquely identified by a network number and a MAC address. Resolution BACnet MS/TP A BACnet MS/TP device supports device MAC addresses in the range 0-127 for masters and 0-254 for slaves. Device MAC addresses are often configured using DIP switches or a configuration tool.   BACnet/IP MAC addresses for BACnet/IP devices are a combination of the IP address and BACnet/IP UDP Port expressed in hexadecimal notation. For example, if a BACnet/IP device is configured with an IP address of 192.168.1.5 and a UDP port of 47808 then:   IP address expressed in hexadecimal is 192 = C0, 168 = A8, 1 = 01, 5 = 05 UDP port expressed in hexadecimal is 47808 = BAC0   Therefore the MAC address will be, C0:A8:01:05:BA:C0   BACnet/SC BACnet/SC nodes are identified by their 6-octet virtual MAC (VMAC) address in form of a IEEE EUI-48 identifier which is randomly generated. A BACnet/SC device attempts to resolve its own VMAC in the network. If it detects another device is already using this VMAC, it will generate a new Random-48 VMAC address and try again.

Issue Metasys® N2 Integration to SBO Product Line EcoStruxure Building Operation Environment Struxureware Building Operation Metasys N2 Cause This Quick Start Guide will assist the Schneider Electric branch or dealer installation team with the basic steps to bring the virtual BACnet devices emulated by the S4 Open: BACnet-N2 Router into the SmartStruxure environment as part of a Johnson Controls Metasys® N2 integration into SBO. This document is not intended to be a full tutorial or user manual for either the S4 Open: BACnet N2 Router or the SmartStruxure system. Refer to the manufacturer’s documentation for each of these systems for detailed information. S4 documentation, the complete Device Template library, and support utilities can be found on the support CD delivered with your S4 Open appliance. Please contact the S4 group for any questions on this process.  Resolution Step 1:   Follow the installation instructions provided with the S4 Open: BACnet-N2 Router to discover and publish the N2 devices in the Metasys® installation to BACnet IP. All operations in SmartStruxure will be against these emulated BACnet IP devices each representing the underlying N2 device. Investigate before you integrate! Validate the N2 bus to make sure that it is electrically in spec and that all N2 devices are working properly before starting the integration process. Assign a unique BACnet virtual network number to each S4 Open: BACnet-N2 Router. N2 devices connected to this S4 Open appliance are published as emulated BACnet IP devices under that network. The Configure Wizard in the S4 Open Management Console will assist you with generating a unique BACnet Device ID for each N2 device. Point instance numbers are included as attributes in our Device Templates for all application-specific controllers. Either of these can be manually overridden in the S4 Open Management Console to meet unique requirements. The S4 Metasys® Configuration File Conversion Utility can be downloaded from the S4 Group web site and will assist you in creating custom Device Templates for DX-9100 devices or application-specific controllers. You will need the corresponding .DMO or .PRN files as input to this utility. A detailed understanding of Metasys® N2 devices, the Metasys® system, and the associated configuration and commissioning utilities are necessary to support successful integrations. If you don’t have this expertise in-house, The S4 Group can recommend a consultant to assist you. NOTE: We highly recommend that you attend a two-day S4 Boot Camp to make sure that you have all the skills necessary to install and configure the S4 Open: BACnet-N2 Router. Step 2: Bring up the SmartStruxure BACnet discovery tab and select BACnet devices. In this example, you can see that the S4 Open BACnet-N2 Router was defined in Network 1 and the N2 devices are in Network 122. The other device in Network 1 in this example is a JCI NAE. The best practice is to assign the S4 Open: BACnet-N2 Router to the BACnet network that you are using as your BACnet backbone. As with any BACnet device, the BACnet-N2 Router must be assigned a unique BACnet device ID. Step 3: Expand the navigation pane to expose the BACnet Interface / IP Network folder. Then select and drag the N2 devices from the Device Discovery tab to the IP Network folder. SmartStruxure will tell you that an Upload is required. Respond OK. Step 4: Navigate to the IP Network folder, select the properties page for each device, and request an Upload operation. This will bring the device properties and point list for each N2 device into SmartStruxure. SmartStruxure will respond with the following confirmation as each upload is completed. Step 5: When the Upload process is completed for all N2 devices and the S4 Open: BACnet-N2 Router, you can continue your SmartStruxure installation process as you would for any BACnet device. Note that there will be no points published under the S4 Open: BACnet-N2 Router itself but you will be able to confirm the Operational Status of the system from SmartStruxure. The Schneider Electric support organization will supply pre-sales engineering support and first-level technical support for the Metasys® N2 to SBO integration solution. The S4 Group will be available to provide 2nd level support to these integration projects.  

Issue This tool will help calculate the required M&B conversion coefficient for a given analog value in I/NET. Product Line TAC INET Environment All I/NET Controllers I/NET Resident Point Editor Cause Need to calculate an I/NET Conversion Coefficient (M&B) for a special sensor Resolution Click here to download an Excel spreadsheet that has several functions for calculating the correct M&B.

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  

Issue What is the difference between an EBO SmartDriver and Smart Connector? Product Line EcoStruxure Building Operation Environment Building Operation SmartDriver Cause SmartDriver and Smart Connector enhance the openness for the EcoStruxure Building Operation, EBO, BMS system. They enable integration between EBO and 3rd party systems, even via not supported or nonstandard protocols. Resolution SmartDriver: SmartDriver enables you to create a customized interface to monitor and control 3rd party devices from the EBO server. The following block diagram shows a SmartDriver Interface and a SmartDriver Driver. The SmartDriver Interface (similar in concept to other protocol interfaces such as Modbus and BACnet) is part of EcoStruxure Building Operation software and enables you to create SmartDriver objects in the System Tree pane. The SmartDriver Driver is installed on the server drive and provides the network communications control. More information at Web Help SmartDriver Overview. Smart Connector: A development framework that simplifies and accelerates integrations with third-party systems or other data sources. It is an open, extensible and configurable application framework that allows developers to create innovative new capabilities, applications, and solutions that extend and enhance EcoStruxure Building solutions. The Smart Connector itself runs outside the EBO server and consume or server data to EBO server via the EcoStruxure web services "EWS". Watch short explainer video for more information: https://www.youtube.com/embed/DXHvRRL4ycY   For more information, visit the Smart Connector Developer Community on the Exchange: https://community.se.com/t5/SmartConnector/ct-p/smart-connector   For developers wanting to get started using the Smart Connector framework visit: https://www.smartconnectorserver.com   Smart Connector shop at Exchange:  https://shop.exchange.se.com/en-US/home 

Issue Is it possible to print alarms automatically with SBO Workstation in matrix printer whenever there is an alarm? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause A number of sites still prefer to directly connect a Dot Matrix Printer to their BMS to automatically print off incoming alarms rather than using more modern emailing of alarms available from EBO. Resolution The following File2Printer software has been made freely available on the EcoStruxure Building Operation Community for exactly this purpose. https://community.se.com/t5/EcoStruxure-Building-Operation/File2Printer/m-p/351127#M71948

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 There is a limit of around 200 user-created objects in b3/i2 devices, once that limit is reached, an attempt to create a new object of any type in the device will result in  "Invalid Handle" error. See https://community.se.com/t5/Building-Automation-Knowledge/Creating-an-object-in-a-BACnet-B3-or-Infinet-controller-results/ta-p/9490 for more info.   Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum b3920 Controller Continuum i2920 Controller Cause Each Continuum object is represented in the system by a "Handle Id", in b3/i2 devices, the handle ID is stored in the controller as a byte value which allows for a maximum of 255 handles, the system objects (System Variables etc.) use around 55 of the handles leaving around 200 for user-created objects.  CX controllers store handle IDs using a 2 bytes value, which allows for 65535 handles, CX controllers rarely run out of handle IDs. Resolution One way to deal with this limitation in the Continuum field devices is to combine InfinityNumeric, InfinityDateTime objects (when possible) into one object configured as an array (manual log).   EXAMPLE: The screen capture below shows 10 InfinityNumeric objects in an i2920 device that are used in the control application of a room named "MainLab"     Let's say for the purpose of this illustration that the following is the control program for MainLab     Since InfinityNumeric objects MainLab.a thru MainLab.j are used exclusivity to store values *** (i.e Setpoint etc), we can configure one of the objects as an array and have it hold all 10 values, thus allowing us to delete 9 InfinityNumeric objects and free 9 handle ids       Before deleting MainLab.b thru MainLab.j we need to modify ALL references to those objects, instead of referencing MainLab.b - MainLab.j we need to reference MainLab.a[1] - MainLab.a[9], note that MainLab.a holds its value (70) normally (not as part of the array), so in this case, we are only using 9 of the 10 array elements.     ***IMPORTANT Only InfinityNumeric and InfinityDateTime objects that are used exclusively to hold a value should be combined, if the object is being used for any of the following operations then it should be left as its own object.   Object triggers one or more programs Object is configured as a log Object is Occupancy flag of a schedule Object has alarms associated with it or is alarm point Object is a setpoint

Issue Are there any Example Reports for the new native Notification Reports which came out in EBO 3.2 to replace the now deprecated WebReports and Report Server? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause As of EBO 2022 (4.0) WebReports and the Report Server have now been deprecated and replaced by External Log Storage using Postgres SQL and Timescale DB, plus the new native Notification Reports which are now built into EBO 3.2 and above, but there are no examples to help new starters to get going. Resolution A Schneider-Electric Community page has been set up specifically for Notification Report users so that they can share their Reports and collaborate on Reporting ideas: https://community.se.com/t5/EcoStruxure-Building-Operation/Reports-showcase-share-your-reports/m-p/388619#M75732

Issue PT1000 temperature sensors RTD Input Product Line EcoStruxure Building Operation Environment AS Classic, ASP  UI16, RTD-DI-16 - Central IO Module ASB, RPC, MPC Need for temperature to be extremely accurate PT1000 platinum resistance thermometer, RTD Resistance Temperature Detector Cause The AS Central IO Module Universal Inputs (UI16) were designed to interface to various thermistors that can have resistance values that are usually much higher than 1000 ohms. They were not designed to interface directly to a PT1000 RTD, and will not provide good accuracy when measuring these lower resistance sensors. The resistance input type was intended to allow for measuring the position of a 10K potentiometer that is used on some wall sensors. The accuracy specification for a resistance input is: +/-(7+0.004*R) ohms. This would result in an error of +/-11 ohms at 1000ohms – therefore a temperature measurement error approaching +/-3.0C. Resolution AS, ASP For RTD PT1000 (Pt100, Pt1000, Ni1000, LG-Ni1000, JCI-Ni1000) use RTD-DI-16 - Central IO Module, then choose 2 or 3 wire RTD Temperature Input ASB Choose 2-wire RTD Temperature Input (Pt1000, Ni1000, LG-Ni1000, JCI-Ni1000) RPC, MPC, MPV Choose RTD Temperature Input (Pt1000, Ni1000, LG-Ni1000)   For more details see SpaceLogic Hardware Reference Guide

Issue When a value in one Automation Server is transferred to a value in another Automation Server what port is used? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation EcoStruxure Building Operation Automation Server (ASP/ASB) Cause Documentation required on ports being used Resolution EcoStruxure Automation servers can use one of three different communication protocols: Transport Control Protocol - TCP Hypertext Transfer Protocol - HTTP Hypertext Transfer Protocol Secure- HTTPS   The communication protocol and ports are configured in the Server wizard when you add an EcoStruxure BMS server via the Enterprise Server   EcoStruxure Automation servers can listen on one of the three communication protocols from Version 1.3 upwards. The TCP port is fixed but please refer to Changing the Automation Server HTTP/HTTPS ports TCP on port 4444 (fixed) HTTP on port 80 (default) HTTPS on port 443 (default)   Each EcoStruxure Automation server maintains a list of all the other EcoStruxure servers in the system and the communication parameters of those EcoStruxure BMS servers. To see the list and which protocol/port is being used select the server (1), select the Communications tab (2) and view the list (3) or individual server settings (4). Note when selecting an Automation Server the individual server settings (4) of other Automation Servers will be greyed out.   When an automation server is added, its communication parameters are distributed by the Enterprise Server to all other EcoStruxure BMS servers in the system. For additional information please refer to EcoStruxure BMS Server Communication   If the IP address or protocol port number in an already commissioned EcoStruxure Automations server is changed, this information must be manually updated in the Enterprise Server Communication view. The Enterprise Server then distributes the new parameters to the other EcoStruxure Automation servers. Select the Enterprise Server (1), select the Communication tab (2), select the server to be changed (3), update the settings (4):   If there are problems with the communication parameters please refer to Inconsistent Communication Parameters