Issue The F3 Search function in EcoStruxure Building Operation (EBO) WorkStation does not return results for Notification File objects (e.g., .xlsx, .pdf, .txt), even when using wildcards.     Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WorkStation Search Cause This behavior is functioning as designed (FAD). Notification files generated using the "Write to File" option are not stored in the EBO database. Therefore, they are not indexed and cannot be retrieved using the F3 search function. Resolution Although these files are not searchable within EBO, they are saved locally in a fixed directory: ...\db\notifications To assist users in locating these files:  Create a Hyperlink Object in EBO that points to the above folder. Users can then open the folder directly within WorkStation and use the operating system’s search functionality to locate specific files. Note: The notification file path is not configurable. For more information, refer to the official documentation in WebHelp: Accessing a Notification Written to a File

Issue Can the EasyLogic range of controllers & RP-IO Modules work under Building Operation 3.2 as BACnet MS/TP third-party devices  Product Line EcoStruxure Building Operation Environment EasyLogic Controllers, EasyLogic RP-V, EasyLogic RP-C, EasyLogic MP-C EasyLogic RP-IO SpaceLogic Advanced, Pro, and Pro Plus Controllers that support native BACnet MS/TP (via a SpaceLogic RS-485 Adapters.   Standalone BACnet field controller Cause The documentation states that EasyLogic Controllers can be used as a Native BACnet MS/TP device. These devices must be configured using their respective supported Building Operation versions, such as Building Operation 2022 and above. However, there are no guidelines on whether they can be used as a third-party BACnet device, particularly in earlier versions such as Building Operation 3.2.    Resolution EasyLogic controllers can be used as BACnet MS/TP third-party devices in Building Operation 3.2 since the EasyLogic range of RP and MP controllers, and RP-IO I/O modules, natively communicate using the BACnet MS/TP protocol.  This same concept applies when using the devices as true 3rd-party devices (e.g., with Continuum and I/A systems) when older controllers fail, and these EasyLogic controllers are used as temporary replacements before a complete transition.   What MUST be understood before taking this approach is that there is no automatic conversion when migrating the site (and devices) to later Building Operation versions that support these devices natively. After the upgrade, the controller must be deleted from the database and hosted as a native EBO controller.   During this process, some programming may be lost. This risk may be mitigated by creating Custom Types for the application once engineered in Building Operation 2022 (or higher) to future-proof the site for upgrades.  Using the latest firmware for the EasyLogic range of devices is also recommended.     Furthermore, the SpaceLogic Controller Range that supports native BACnet MS/TP (via an RS-485 Adapters) can be configured in the same fashion as described for the EasyLogic range.   Refer to Hardware Overview for further details on each product line. 

Issue There is a performance issue affecting EBO Workstation and Product Support has requested logs. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Product Support has requested logs from EBO Workstation. Resolution The WorkStation logs and crash dumps are stored in the application data folder. The full path depends on the software installed:   EcoStruxure: %appdata%\Schneider Electric EcoStruxure\Building Operation\WorkStation\Logs %appdata%\Schneider Electric EcoStruxure\Building Operation\WorkStation\Crashes   StruxureWare: %appdata%\Schneider Electric StruxureWare\Building Operation\WorkStation\Logs %appdata%\Schneider Electric StruxureWare\Building Operation\WorkStation\Crashes     All files from the Logs folder starting with CoreLog or CrashLog must be included. All files from the Crashes folder must be included.   Perform the following to quickly access the appropriate folder above: Select link Paste into Windows Explorer Address Bar  If you can replicate an issue, perform this process to Temporarily Raise the Log Level before running the test and collecting the logs. Log in to WorkStation Click the Tools menu Click Options Hold down the left SHIFT key on the keyboard Click Apply Release the left SHIFT key on the keyboard and click OK to close the dialog The WorkStation log level is now set to INFO and will collect additional information Please note the logging level will remain at INFO while logging out and in.  To return the workstation log level to default close the Workstation and re-open.

Issue After correctly following the process outlined in Setup External Log Storage using MSSQL., EcoStruxure Building Operation (EBO) server fails to connect to the external database, generating the following System Alarms:  Unable to connect to data source Login failed for user The system alarm specifically details an issue with the ODBC SQL Driver as below: "The driver doesn't support the version of ODBC behavior that the application requested..." "Invalid connection string attribute" Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Premium (AS-P) External Log Storage [MSSQL]  Cause The system alarm details indicate an issue with the ODBC SQL Driver, specifically: "The driver doesn't support the version of ODBC behavior that the application requested..." "Invalid connection string attribute" This suggests a compatibility or configuration issue with the ODBC driver or connection string.   Resolution The following has been seen to correct the issue: Verify User Credentials Ensure that the username and password used for the ODBC connection are correct. Note: SQL Server credentials are case-sensitive, so double-check for any discrepancies in letter casing. Remove any uppercase for the username. In some cases, using only lowercase letters for the username in the ODBC connection string has resolved the issue, e.g,. Instead of "My_User" use "myuser"

Issue Cannot activate a license on an Automation Server although the entitlement works on other Automation Servers. The Device Administrator output is similar to the following:   Activate failed: ASEmbeddedAPI internal error: Binary response does not contain feature information Error status information: FNO server response: =V(BACK_OFFICE%DEBACK_OFFICE+]\fK%MDEVICEID|0}~;DEVICEID/jlSk\}K qq7!vi%DCH'~A%05pQWN]G|3^Jk+yaz_Kx/:Dy&w F7BWWN#`Ex|6S.d<Y^nV~@?*C.D0])"KO?[pS#GH|aMe+i|@4's9kNE\7gfocfVbRf$1VuH>sdp_JN6%4B.n|Zm$]wi9M|F8#Hrw~/L4%XU<?8o="P1S$uW6Fu5vAsAz|l>8.@XA|.'[v_ekh_P}c7 Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Automation Server (AS) Cause When an Automation Server fails in the field an RMA (Return Material Authorization) request is made, and the license is returned for re-use in the replacement Automation Server. Once this occurs the serial number of the faulty Automation Server is blacklisted to ensure that it cannot be licensed and reused. Resolution If the device was mistakenly added to the blacklist please supply the Automation Server serial number to Support. If an RMA number does not exist in the licensing system for this Automation Server, the support team can make a request to have the server removed from the blacklist.

Issue How to collect log files from the Project Configuration tool 2.0. Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause When contacting Product Support about issues with the PCT, log files should be provided. Resolution Collect log files through the Web interface on both Windows and Ubuntu installations: Logon to PCT server, Click Diagnostic  Click Collect logs Log starts collecting. After the log collection process is complete, the file will either be saved to the browser's default download location or a window will pop up asking where to save the ZIP file. Select the desired location then click Save   Log collector tool for PCT for Ubuntu: If the PCT web interface is unavailable, you can use the Log Collector tool to gather log files. This tool is included with the PCT installation on Ubuntu, eg. pct-2.1.1.8-log-collector-ubuntu. Give the file proper permission to be able to run as an executable either using chmod command:  chmod +x pct-2.1.1.8-log-collector-ubuntu​ or via file properties, as shown in below screenshot: Run the log collector tool. ./pct-2.1.1.8-log-collector-ubuntu​ A zip file containing the required log files will be saved in the same folder where the log collector tool is located.

Issue Licenses required to upgrade SBO/EBO to EBO 2022 v4.0.x Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium - Secure boot Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause Clarifying licensing upgrade requirements for EBO 2022 v4.0.x Resolution Example: Upgrading a site SBO 1.x or EBO 2.x to EBO 2022 v4.0.x or later directly. Site has an Enterprise Server (ES) the ES has 7x Automation servers AS-Ps and 2x AS-Bs attached. One AS-P has a Modbus interface, and 1 AS-B has a Modbus interface. Adding 1 additional AS-P classic (non-secure boot), 1x AS-P-S secure boot and 1 AS-B scalable. The SBO 1.x or EBO 2.x licenses need to be upgraded to EBO 3.x first. Upgrade ES licensing from SBO 1.x license to EBO 3.x.  These licenses need to be activated using License Administrator.   1 x SXWSWESUP13010 ES Upgrade from 1.X to 3.0 with 10 or less AS  Note: Upgrading ES from 1.x gives the ability to host the maximum quantity of field devices / controllers at the Enterprise Server (600). Also, when a system is upgraded from 1.x, it will be provided with an unlimited (bounded by the maximums stated in the Architectural Guidelines) client license for connections to the Enterprise Server that has been upgraded.   The following additional licenses are required for each AS-x when upgrading a site from SBO 1.x to EBO 3.x or upgrading a site from EBO 2.x that was originally installed at SBO 1.x and upgraded to EBO 2.x. These are not required if the site was originally installed at EBO 2.0 and upgrading to EBO 3.x. These licenses need to be activated using License Administrator.   7 x SXWSWASUP00001 license will be required one for each AS-P. 2 x SXWSWASUP00001 licenses will be required one for each AS-B.   Note: If the site has more than 24 AS-xs then part number SXWSWASUP00099 provides 999 licenses. EBO 3.2.x architectural guidelines allows a maximum of 250 AS-xs per ES.   Upgrade ES license from EBO 3 to EBO 4 This license needs to be activated using License Administrator.   1 x SXWSWESUP30010 ES Upgrade from 3.X to EBO 2022 or later (i.e. to the current EBO version) with 10 or less AS Upgrade AS-P/B licensing from EBO 3 to EBO 4 or later These licenses need to be activated using Device Administrator.   For each AS-P (non secure boot AS-P and AS-P-NL), one of the following bundles would be required for each AS-P.   SXWSWASPUP30SA Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standalone SXWSWASPUP30SD Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standard SXWSWASPUP30EN Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle - Enhanced SXWSWASPUP30FU Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Full SXWSWASPUP30BP Full Bulk pack for upgrading AS-P-XX from EBO 3.x to EBO 2022 or later, contains 125 pieces of SXWSWASPUP30FU. For the AS-P with the Modbus interface, an SXWSWX000MBRTU license is not needed as Modbus is grand-fathered for AS-P classics.   Note: Once an AS-P license is upgraded, there is no differentiation between AS-P Secure Boot and AS-P Non-Secure Boot (Classic):   If the “SXWSWASPUP30SD Upgrades an AS-P from EBO 3.x to EBO 2022 or later AS-P Bundle – Standard” license was purchased for an AS-P classic, and later it requires an enhanced or full license.   SXWSWXUP00SDEN ASP Bundle upgrade - Standard to Enhanced SXWSWXUP00SDFU ASP Bundle upgrade - Standard to Full Would need to be purchased.   If the “SXWSWASPUP30EN Upgrades an AS-P from EBO 3.x to EBO 2022 or later AS-P Bundle – Enhanced” license was purchased for an AS-P classic, and later it requires an  full license. SXWSWXUP00ENFU ASP Bundle upgrade - Enhanced to Full Would need to be purchased.   For the AS-Bs (AS-B-24, AS-B-24H, AS-B-36, and AS-B-36H), one of the following bundles would be required for each AS-B. These licenses need to be activated using Device Administrator.   SXWSWASBUP30SD Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle – Standard SXWSWASBUP30FU Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle - Full A SXWSWX000MBRTU Modbus license is not needed with AS-Bs Note: Once an AS-B license is upgraded, there is no differentiation between AS-B Scalable and AS-B (L) Non-Scalable (Classic): If the “SXWSWASBUP30SD Upgrades AS-B from EBO 3.x to EBO 2022 AS-B Bundle – Standard” license was purchased for an AS-B (L) classic, and later it requires a full license.   SXWSWXBBUPSDFU ASB Bundle upgrade - Standard to Full, would need to be purchased.   To upgrade the AS-B-L (classic) type, the SXWSWASBUP30SD ASB Upgrade – Standard license is all that is required.   For the additional AS-P classic one of the following licenses would be required. SXWSWASPUP30SA Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standalone SXWSWASPUP30SD Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standard SXWSWASPUP30EN Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle - Enhanced SXWSWASPUP30FU Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Full For the AS-P with the Modbus interface, an SXWSWX000MBRTU license is not needed as Modbus is grand-fathered for AS-P classics.   For the additional AS-P secure boot one of the following licenses would be required. SXWSWXBU0000SA ASP Bundle - Standalone  SXWSWXBU0000SD ASP Bundle – Standard  SXWSWXBU0000EN ASP Bundle – Enhanced  SXWSWXBU0000FU ASP Bundle - Full  For the AS-P secure boot if a Modbus interface is to be used the SXWSWX000MBRTU Modbus license would be required. For the additional AS-B Scalable one of the following licenses would be required. SXWSWXBBU010SD ASB Bundle – Standard SXWSWXBBU050FU ASB Bundle – Full A SXWSWX000MBRTU Modbus license is not needed with AS-B scalable. If an additional AS-B classic was added one of the following licenses would be required. SXWSWASBUP30SD Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle – Standard SXWSWASBUP30FU Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle - Full A SXWSWX000MBRTU Modbus license is not needed with AS-Bs     Addition: If the site had an Enterprise Central (EC) at EBO 2.0 and was upgrading to EBO 2022 v4.0.x or later, one of the following licenses would be required to upgrade to EBO 3.x first:   SXWSWECUP23005 EC Upgrade with 5 or less ES SXWSWECUP23010 EC Upgrade with 10 or less ES Then one of the following licenses would be require to upgrade from EBO 3.x to EBO 2022 v4.0.x or later:   SXWSWECUP30005 EC Upgrade from 3.x - with 5 or less ES SXWSWECUP30010 EC Upgrade from 3.x - with 10 or less ES   For more information on the bundles, search for 'software bundles" in the  “Part Numbers and Hardware/Software User Matrix – EBO 2024”   For information on software and features that require licenses  

Issue The "Change set error" occurs after trying to save a LonWorks network variable binding in SmartStruxure. Product Line> EcoStruxure Building Operation Environment Workstation LonWorks Network Cause The LonWorks bindings have become corrupt and need to be rebuilt. Resolution Rebuild LonWorks Bindings Right click on the LonWorks Network. Go to Advanced > Rebuild LonWorks Bindings. Select Yes.

Issue Even though the curve block is set to range between 0-100, the block just stays at a fixed output somewhere in the curve output range. Product Line TAC Vista Environment Vista Workstation Cause The curve requires the first entry of the X value to be the lowest value, and then the subsequent values to be larger than the previous X entry. Resolution Adjust the order of the XY entries on the curve block so the first entry in the X will be the lowest value. Example of Incorrect Curve Here is an example of a Curve that will not work. Note the first X entry is -2 and the last X entry is -6.  Example of Correct Curve To correct this curve, -6 is the lower number, so this should be the first X entry. Here is an example of the curve that has the correct X entry order.

Issue It is not possible to login to an Automation Server and it fails with the error "Domain Controller version too low' for certain users. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause Remnants of an EcoStruxure Building Operation domain exist in the controller where it has not been removed completely and it is set as the Default Logon Domain. Resolution Login with Administrative Rights: Use a user account with Administrative rights in the Local or another domain explicitly using the Domain name. Delete Partial Domain: Once successfully logged in, delete the offending partial domain. Retry Login: Attempt to log in again. Additional Information: Ensure that the domain is completely removed to avoid future login issues. Verify that the Default Logon Domain is correctly set after removing the partial domain.

Issue Are SNMP traps in StruxureWare Building Operation sent using UDP or TCP? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Simple Network Management Protocol (SNMP) is an Internet-standard protocol for managing devices on IP networks. Need to know if SNMP messages are sent over TCP or UDP. Resolution SNMP traps in EcoStruxure Building Operation are sent using the UDP protocol.   Additional Information: UDP (User Datagram Protocol) is a connectionless protocol that allows for low-latency communication, making it suitable for SNMP traps which require quick delivery without the overhead of establishing a connection. TCP (Transmission Control Protocol), on the other hand, is connection-oriented and ensures reliable delivery of packets, but it is not used for SNMP traps in this context.

Issue Need to use the Automation Server port log to view BACnet MS/TP communication Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Need to capture BACnet MS/TP traffic for troubleshooting. Resolution In EBO 2024 (V6.0) and higher, there is an integrated packet capture feature available in EBO Servers with BACnet Interfaces. This feature allows users to create packet captures that record the BACnet messages that are visible to the EBO Server’s BACnet/IP and BACnet MS/TP networks. Refer to: Packet Captures in EcoStruxure Building Operation

  Issue How can I troubleshoot communication issues between SEAL app and EBO server? Does the SEAL app provide a detailed log for troubleshooting communication issues between the app and the EBO server? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Enterprise Server Ecostruxure SEAL Cause When troubleshooting SEAL communications issues to an EBO server, it may be helpful to get deeper information about the communication between the server and the SEAL application. To do this the following lines can be added to the appsettings.json application settings file as described below in the resolution Resolution Browse to C:\Program Files\Schneider Electric\SEAL Open the file appsettings.json. Depending on your user rights, you may need to copy and edit this file in another folder Go to line 26. After the closing brace }, enter a comma ,  Paste the following: "Serilog": { "Using": [ "Serilog.Sinks.File" ], "MinimumLevel": { "Default": "Information", "Override": { "Microsoft": "Warning", "Microsoft.Hosting.Lifetime": "Information", "SE.SEAL": "Debug", "SE.SEAL.Web.Auth": "Verbose" } }, "WriteTo": [ { "Name": "File", "Args": { "path": "%LOCALAPPDATA%/SEAL/logs/SEAL.txt", "rollingInterval": "Day", "shared": true } } ], "Enrich": [ "FromLogContext" ] }   Save the file. Try logging into the SEAL app and connecting to the EBO server Save the log found under: %LOCALAPPDATA%/SEAL/logs/SEAL.txt Restore the appsettings.json file to its original state.   Attached to this article is a ready-made file for use. Move the original file to another folder Place the attached file in C:\Program Files\Schneider Electric\SEAL After saving the logs, delete the attached file Move the original file back to its original location   In addition to this, it is always recommended to take an event view - Application log

Issue Configured Loytec LConfig application as a service but still do not get communication from the LonWorks Network. Not able to get Service pin from LON devices connected with Loytec NIC from Enterprise Server Product Line EcoStruxure Building Operation Environment Enterprise Server 1.1 Loytec NIC852 (LConfig Tool) Windows 7 Cause LConfig tool version is too old. The LConfig tool, even if set to start as a service, also still needs to start before the Enterprise Server (ES), otherwise the Enterprise Server fails to establish its connection with the LonWorks interface. For information on how to set LConfig to run as a service refer to Not able to get Service pin from LON devices connected with Loytec NIC from ES. Resolution To rectify the cause 1, click here to verify if the LConfig version is the most recent one. If not please download the most recent NIC - LOYTEC Network Interface Software. To rectify the cause 2, you must set the Loytec (LConfig) application service to be a dependency of the Enterprise Server (ES), to do this follow these instructions: Using RegEdit (or similar) edit the Registry Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\StruxureWare 1.1 Enterprise Server NOTE: For SmartStruxure version 1.3 and above, go to path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Building Operation 1.3 Enterprise Server Locate and edit the DependOnService string Add the text LoytecSrv (service name for the LConfig application). Close the editor and reboot the PC Note: When running the LConfig as a service the LConfig Tool is not available from the System Tray and must be started from the program shortcut, located under Start > Programs> LOYTEC Network Interfaces> LConfig As a quick visual check, to see if configured correctly, you can perform a LonWorks Device Discovery on your Enterprise Server, this will show the NIC which has been defined with a red box (see image below). If these are all blue then you will not be able to receive any communications from your devices. Also remember if using the Loytec LIP devices that these should be configured in Smart Mode.

  Issue How can I troubleshoot a communication issue with the Smart Connector. Is there a log available within the AS or ES that shows the Smart Connector communication. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Building Operation Enterprise Server Cause When troubleshooting Smart Connector issues in an AS or ES it can be helpful to see the communication between the Server and the Smart Connector device to help identify this issue. The trace log within both server types is available and is configured as described below in the resolution. Resolution Open Workstation and navigate to [AS/ES name]/System/Modules/Trace/Loggers/nsp/nsp.csc/nsp.csc.CWSServer. Right-click "nsp.csc.CWSServer" and choose Properties. Under Level, change from "Information" to "Trace", then click ok. Let it run a few minutes. If there are some user input needed to recreate the Smart Connector issue, then perform these steps now. Retrieve the log by right-clicking [AS/ES name]/System/Modules/Trace/TraceSettings and choose Trace settings->Get trace log.  Save the log file. Once debugging is complete remember to change log level back to "Information" (reverse of step 3). Note: If the ES or AS is reset, i.e. cold started or warm started, the log level will return to 'Information', so if further increased logging is required, the procedure will need to be repeated. Note2: This option is only availabe for EBO version 6.02 and onwards

Issue One of the following error messages are displayed. Internal server error Server already part of a system Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation Server Cause Version Mismatch: The Automation Server is either not the same version as the Enterprise Server or it is still connected to a different Enterprise Server. If the Automation Server is still connected to another Enterprise Server then it must be detached before it can be added underneath a new Enterprise Server. User Permissions: In some instances, the User Permissions "System Address" is not added to the user account that is attempting to add the server.    Resolution If you are given an error that states "Domain: Internal Server Error" then you need to download the same version of firmware to the AS that is installed on the ES. Resolution #1: Detach the Automation Server Log in to the Automation Server.   In the system tree pane, right-click on the automation server and go to Advanced > Detach server.   The Disconnect Automation Server window will open; click yes.   The Automation Server is now detached and can be added to an Enterprise Server. Resolution #2: Verify User Permissions Check a current backup using the SBO xbk Analyzer and verify the number of servers listed under Reports>Servers Log on using the default admin account and see if these servers exist. Detach the server(s), as described above. If the secondary user still requires permission to add and see ALL servers: Go to the user and select the Permissions tab Ensure the ES path is selected Click on the Add System button (identified with the arrow) Enable all options to allow read/write, create etc.  Save these changes and log off and back on with this user to see the changes. This user should now be able to add/see ALL servers.

Issue What temperature limit should the CPU Temperature stay within? Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause From EBO version 3.2, the CPU Temperature is added. Resolution The CPU temperature parameter displayed in the UI property dialog Automation Server Properties – Basic Tab is intended for internal debugging purposes only. Users are not required to monitor or take action based on this value, as there is no specified maximum CPU temperature level that requires user intervention or indicates potential CPU performance degradation.  

Issue How to connect a SpaceLogic IP Controller via MSTP Product Line EcoStruxure Building Operation Environment Workstation Automation Server (ASP/ASB) Space Logic IP Controller RS-485 Adapter Cause Only certain SpaceLogic IP Controller models and versions support the new BACnet MSTP Adaptor and details are required on how to configure these controllers for BACnet MSTP. Resolution The following video will illustrate how to: Configure ASP/ASB for BACnet MSTP Communication. Configure a SpaceLogic IP Controller as a BACnet MSTP device. Discover the SpaceLogic IP Controller on the BACnet MSTP network. Things you need: Software EcoStruxure Building Operation Workstation 2022 Building Commission Application (available from Google Play, Apple Store, or Microsoft Store) Hardware ASP/ASB version 4.0 or higher RP controller (hardware version 10 ) RS-485 Adaptor (Isolating or Non-Isolating) RJ45 UTP Straight Through Cable (12"/300mm or less) Note: - if the RP controller does not show MSTP settings check the Space Logic IP controller firmware release notes and install firmware corresponding to the EBO version.  For example firmware versions 3 and below do not have settings for MSTP configuration. Before attempting to install a SpaceLogic controller on MSTP consult the following: Isolated RS-485 Adapter and Non-isolated RS-485 Adapter for SpaceLogic IP controller types supporting the RS-485 MSTP adapter RP-C BACnet MS/TP Support for RP models supporting BACnet MS/TP Installing an RS-485 Adapter for information on installing the BACnet MSTP adapter Connecting an Isolated RS-485 Adapter and Connecting a Non-isolated RS-485 Adapter for port usage and CAT 5 UTP connection cable Allocating Flexible Ports for additional considerations on port usage Enabling the BACnet/IP Controller to Communicate on an MS/TP Network Please see the video below:

Issue Alarms with an invalid Source path cannot be removed from ES or AS Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation 3.0 and higher Cause The invalid path prevents alarms from being deleted. In earlier releases of EBO, there was an issue whereby an error could occur in the source path of an alarm if the Automation Server was renamed. Most invalid alarms observed originate from this type of error. Resolution Use Alarms Integrity Check in the following steps.  Automation Servers first, then Enterprise Server, and finally, if installed, Enterprise Central last. See Alarm Cannot be Acknowledged Due to Invalid Paths for additional details.   Expand System, Right-click the Alarm Control Panel,  Choose Advanced - Alarms Integrity Check.   The command runs quickly. There is no confirmation that the check has run, but a review of the alarms will show that the invalid alarms have been removed.

Issue Enabling Scattered read for Modbus device that doesn't support it can lead to poll fail, with Point Modbus Error: Illegal function code. Product Line EcoStruxure Building Operation Environment Building Operation Workstation (1.5 and above) Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Building Operation Enterprise Server Cause Requirement to optimize communication over Modbus to improve performance. Resolution The following is an extract from Web Help. The complete section can be viewed at  Modbus Batch Read Function:   'Scattered read is an enhancement to the batch read function that enables multiple, non-contiguous slave device registers to be read in a single Modbus query. By using the scattered read function, you can enable the Enterprise Server or Automation Server to avoid reading a large block of contiguous registers when it is only necessary to read a few registers. Also, using scattered read avoids the multiple use of group function codes 03 (analog output holding registers) and 04 (analog input registers) in order to read non-contiguous registers. Group function codes 01 (discrete output logic coils) and 02 (discrete input contacts) are not supported for scattered read.   Scattered read is available only for supported devices, for example, Schneider Electric branch circuit power meters with split core CTs. Furthermore, the scattered read function applies only when the Enterprise Server or Automation Server is operating as the client, not as a server. You can enable the scattered read function in the properties of all Modbus devices. If a device does not support scattered read: In V6 or higher: the polls will fail with an Illegal function code, so scattered read needs to be disabled if not supported by the Modbus device. In V5 or below: the device is polled by the master device in the same way as if you had not enabled scattered read.'   The image below shows the properties dialogue window for a Modbus device and the corresponding setting.  The left is version 3.1 and above, the right is version 3.0 and below where it is referred to as 'Non-contiguous read'.  Refer to the Modbus TCP Device  section on Web Help for more information.