Building Automation Knowledge Base

  Issue When adding an Enterprise Server (ES) to Enterprise Central (EC), the process fails with Error - Object Does not exist Domain: Data Access. Details: Modules: Connect Plugin Module Code 73 Trace log shows the following text: nsp.csc.csm.ChangeSetTransaction Rollback due to Data Access Error: Object_Does_Not_Exist (0x40004) in module Connect_Plugin(73), moduleCode=73. "" nsp.csc.cspclient.AddServerCommandPassThrough Execute: Data Access Error: Object_Does_Not_Exist (0x40004) in module Connect_Plugin(73), moduleCode=73. "" nsp.csc.cspclient.ConnectionPool Terminating. GetConnection aborted [IP Address: port#] Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central  Building Operation Enterprise Server  Registered System Cause In this instance, the ES added to the EC is currently registered.  Registered Servers can only be the parent server and therefore cannot be added to a non-registered system or a different system.  Parent servers can only be registered, and any sub-servers inherit this registration from the Parent sever.    Resolution The registration should always be on the parent server. To remove the registration from the ES, the SystemID needs resetting as per the following procedure:  Resetting the System ID Once reset, the system is no longer registered, and adding the ES to the EC will be successful. 

Issue There isn't enough documentation on how to disable the different connection protocols. I.e. TLS or SSH. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Cause Increase the security of the system. Resolution SSL Communication Security Settings: You can edit SSL configuration in WorkStation Control Panel's Security Settings or in the Device Administrator SSL Security Settings tab. SSLv1,v2,v3 are all implicitly disabled. In EBO 2022 (4.0) or higher, TLS 1.3 is available and used as default when logging on with WebStation and for server-server communication with HTTPS. TLS 1.0 and TLS 1.1 are by default disabled but can be enabled in Control Panel. WorkStation is using TLS 1.2, disabling it would prevent logging on to WorkStation. In WorkStation, the only valid protocols are shown when you hover the mouse over disabled protocols. See below.   SSH Port: Port used for communication with Device Administrator can be disabled or changed so that the automation server communicates on another port using SSH. It is also possible to disable all SSH communication. SSH communication settings are available in Automation Server Properties – Network Tab, as shown below. Refer to Disabling Port 22 on SmartX Server and Adding an Additional SSH Port for a SmartX Server .  For more Security guidelines,  refer to EcoStruxure Building Management - System Hardening Guide, Security Overview, and Information Technology System Planning Guide 

Issue SoapEwsRestProvider serves data sourced from any EWS Server using the standard EWS SOAP protocol. The architecture for the SmartConnector REST Extensions integrates Swagger to provide a rich self-documenting API. Below errors indicate configuration issues. The User Name or Password were incorrect. "Message": "Authorization has been denied for this request. " "Message": "The HTTP request was forbidden with client authentication scheme 'Digest' " Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Building Operation Enterprise Central Cause Smart Connecter or EBO Incorrect configuration. Resolution Make sure that SboEwsRestProvider is started and has a correct port that is not used by any other Smart Connector data provider or other application.   Make sure that EWS server address has the following format: HTTP: http://ipAddress:port/EcoStruxure/DataExchange HTTPS: https://ipAddress:port/EcoStruxure/DataExchange For ES/EC, check software administrator to make sure there is no port conflict: Software Administrator shows red outline (box) on the Communication Ports (HTTP / HTTPS) - Communities (se.com) In EBO, make sure EWS server is enabled: Enabling the EcoStruxure Web Service Server Check if username and password used for the SOAP provide has correct permissions and can be used to login to EBO server. If the user is not located in the default domain, make sure to add the domain name in the Username string, ex. "Domain/User". If HTTP protocol is used (not recommended), check the following: In EWS server configuration, make sure that "Enforce Secure Communication" to Disabled. In Security Manager, make sure that "Enable Incoming http communication" is enabled.

  Issue Using active directory with Change Control  feature does not authenticate when signing  Product Line EcoStruxure Building Operation Environment Building Operation release 3.1 and above Building Operation Enterprise Central  Building Operation Enterprise Server Building Operation SmartX Controllers Cause The interaction of Active Directory and Change Control is not clearly defined in the documentation when both are in use.  Although Active Directory within Building Operation Domains can use both the Fully Qualified Domain Name (FQDN) and Netbios Windows Domain names it is recommended that only the Netbios Domain name be used if Change Control is implemented. Refer to EBO Known Issues & Solution topic  Change Control and Windows Active Directory not authenticating - Communities (se.com)  for updates.   Resolution When using Active Directory with Change Control only add the Windows Netbios name to the Building Operation Windows domain name entry:   Using the Full DNS Domain Name (examples include - apa.gad.schneider-electric.com ; pss.apa.local etc.) although these will allow user accounts to log on to servers it currently does not work when used to authenticate change control.    The easiest way to identify which domain name to use is to open WorkStation and refer to the name shown next to:  Log on as:    Secondly when authenticating change control actions with active directory user accounts, irrespective of the Default Building Operation Domain selected, the user account name must be prefixed with the Windows Domain Name 

  Issue TAC Xenta devices suddenly indicate that they Needs commissioning. Product Line EcoStruxure Building Operation. Environment • Building Operation Workstation • Xenta 401 • Xenta 301 • Xenta 281 Cause The flag "Needs commissioning" is suddenly set.     Resolution If the property "Needs commissioning" is set, something has changed in the settings. This could be Subnet/Node address in the Domain table, or a change in any LonWorks binding, that caused a change in the Selector, Address, and or Alias tables.   The property Needs commissioning may also be set after a TAC Vista upgrade (conversion) or similar situations.  

Issue After Sigma transition into EBO, upon alarm and alarm clear there is no requirement to acknowledge the alarm. In the Sigma Interface, the object alarm 'Type of Acknowledgement is set to 'No' and cannot be changed. Product Line Ecostruxure Building Operation, Satchwell Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause Alarm Priorities are incorrectly set in Sigma Alarm Manager. Resolution During the Data Import into EBO, the settings of the Sigma Alarm Manager is checked and the alarm acknowledgement type is set to a specific type. If no alarm priorities are set for acknowledgement in Sigma, then this is repeated in EBO.    To change to 'Single' so that alarms and alarm clears are able to be acknowledged, in Sigma: Open the Alarm Manager and go to the menu options: Configure > Acknowledgement Groups   Redistribute the alarm priorities into the the different acknowledgement groups as per the site requirement. The image below shows the default view on a new install of Sigma.   Redo the Data Import, the 'Type of Acknowledgement' is now seen to be set to 'Single'. However, If it is now showing 'Extended', then the KB article Type of Acknowledgement set to 'Extended' on Sigma Interface object alarm will explain how to change this.

Issue After a Sigma transition into EBO, alarm clears are requiring acknowledgements. In the Sigma Interface, the object alarm and hardware alarm 'Type of Acknowledgement are set to 'Extended' and cannot be changed to 'Single' Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause Alarm Clear Controls are incorrectly set in Sigma Alarm Manager. Resolution During the Data Import into EBO, the settings of the Sigma Alarm Manager is checked and the alarm clear acknowledgement type is set to a specific type. If acknowledgement on alarm clears is no longer required in EBO then it will need to be changed on the Sigma server,   To change to 'Single' so that alarms only are able to be acknowledged, in Sigma: Open the Alarm Manager and go to the menu options: Configure > Alarm Controls.   Uncheck the 'Alarm Clears Acknowledgeable' box.   Redo the Data Import, the 'Type of Acknowledgement' is now seen to be set to 'Single'. However, If it is now showing 'No', then the KB article Type of Acknowledgement set to 'No' on Sigma Interface object alarm will explain how to change this.

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 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 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 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 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 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 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 For various reasons, it is sometimes necessary to change a b3's mac ID. For example, a b3 that is removed from a site and will later be used at a different site needs to have its mac id reset to factory default to avoid the possibility of introducing a duplicate mac id. NOTE: To set the MAC ID to the factory default you need BACnet Service Tool version 1.110004 or newer.   Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum b3 Controller Continuum Service Tool RoamIO2 BACnet Service Tool Cause The MAC ID needs to be set or changed on a b3 controller. Resolution IMPORTANT: If the b3 has previously been assigned a valid mac id then proceed to step #1. If the b3 has factory default slave mac id then see  CHANGING MAC ID ON A BRAND NEW B3 FROM THE FACTORY below Make sure the b3 is disconnected from the MSTP network then connect the RoamIO2 directly to the b3 using the service port. Launch the BACnet Service Tool and de-select the 'By Networks' and 'BACnet only' menu options in the view menu. Click the green icon to make the RoamIO2 sync to the baud rate of the b3 and discover it. In the 'Tools' menu select 'Set Offline B3 Mac Id' as shown below.  In the 'Modify MAC Id' window enter the b3's serial number and the new mac id to be set then click Apply. (NOTE: To set the MAC ID to factory default enter 172, DO NOT USE ZERO) To set the MAC Id to the factory default you need BACnet Service Tool version 1.110004 or newer. Tested working on beta version 1.119903). This beta version is attached. Download it and remove the .txt at the end to make it a zip file, unzip then see the readme.txt. A feedback message 'Success! will be returned if the MAC id was changed EXCEPT when setting the MAC Id to factory default (172) When setting the MAC Id to the factory default you will NOT get SUCCESS feedback, this is because the default id of 172 is a slave id (chosen because in hex it is AC for Andover Controls). Slave Ids are not allowed to initiate communication on the MSTP network. So, as a result of that, the b3 is unable to report to the RoamIO2 that the id was successfully changed. A visual sign that the ID was changed to 172 is that the TD led on the b3's RS485 port will shut off. Disconnect and re-connect to have the RoamIO2 communicate with the b3 using the new MAC id (unless you changed it to the factory default of 172). CHANGING MAC ID ON A BRAND NEW B3 FROM THE FACTORY The RoamIO2 can also be used to assign a mac id to a brand new b3 which has a factory default mac id of 0xAC (172 decimal) but the steps are a little different. In order for a RoamIO2 to be able to send communication packets to the b3, it first has to sync up with the baud rate of the b3, it does by listening and analyzing the packets sent by the b3 until it is able to determine the baud rate. As mentioned before, the factory default mac id of a b3 is slave id 172 which prohibits the b3s from sending out packets and makes it impossible for the RoamIO2 to determine the baud rate. There are several ways to work around the baud rate issue... Set the baud rate manually. Click on the green icon to attempt to connect the RoamIO2 to the b3. You will get an error that the baud rate could not be determined, click YES to proceed anyway From the 'Tools' menu select 'Set B3 Baud Rate' and set the baud rate to what you believe the last baud rate was for the b3. (The factory default baud rate is 19200) You should now be able to set the mac id per the steps above. NOTE: You may have to try all the baud rates until you find the one the b3 is operating at.

Issue In EBO 2022 or higher the "Semantic Engineering View" button is grayed-out in EBO WorkStation and "Semantic DB authentication failure" is shown in Alarm View. "Semantic Engineering View" button is grayed-out and "Semantic DB authentication failure" alarm   Semantic db authentication error   Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause  EBO user that connects to the Sparql database has the wrong username and/or password. Resolution Make sure that the user configured in EBO semantic settings matches the user created in the GraphDB web interface. In WorkStation, in the System Tree pane, select the EBO server. Click the Control Panel tab. Click Navigate to Sparql database, this will open the GraphDB web interface. Login with the admin user account.  In the top right corner, make sure that correct repository is selected, default name is "nsp".  Go to Setup -> Users and Access. Edit user "nspService". Set a password for the "nspService" account and make sure it has access rights to the "nsp" repository then click save. In EBO WorkStation control Panel, open Semantic Settings. Set the password for username "nspService" to match the password set in the GraphDB interface. For more information, please refer to the GraphDB help: Secure GraphDB — GraphDB SE 9.10.0 documentation (ontotext.com)