Notifications

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Label: "ecostruxure building operation"

View in: "Building Automation Knowledge Base" | Community

1836 Posts | First Used: 2018-09-06

Building Automation Knowledge Base

Issue When a very long path is included in a request to the SmartConnector RESTful EWS gateway, such as when attempting to acknowledge an alarm with a long path, the gateway returns the error "HTTP Error 400: The request URL is invalid." <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd"> <HTML><HEAD><TITLE>Bad Request</TITLE> <META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD> <BODY><h2>Bad Request - Invalid URL</h2> <hr><p>HTTP Error 400. The request URL is invalid.</p> </BODY></HTML> Product Line EcoStruxure Building Operation Environment SmartConnector Cause In Windows, the default maximum number of characters in a URL path segment (the area between the slashes in the URL) is 260 characters. When the object path, after double URL encoding, exceeds 260 characters, it triggers error 400. Resolution To resolve this issue, follow these steps: Add a registry key "UrlSegmentMaxLength" to the following path in the SmartConnector PC registry: Path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters Name: UrlSegmentMaxLength Type: DWORD Value: 0 - 32,766 (e.g., set the value to 1000) After adding the registry key, restart the HTTP services or restart the PC. Detailed instructions for this process can be found in the "Http.sys registry settings for Windows" guide on the Microsoft Learn website. Http.sys registry settings for Windows - Internet Information Services | Microsoft Learn

Issue Packets from the EBO onboard packet capture utility are not ordered correctly. In the example below it can be seen that the sequence number of the ACK comes before the REQ despite the timestamp for the ACK being later than the REQ. Product Line EcoStruxure Building Operation Environment Building Operation Workstation SpaceLogic Server Cause Out-of-order packets are quite normal on a TCP level. Earlier packets can arrive later due to buffering and other reasons. Applications are able to buffer these messages and rearrange them before they are written to the application. Since the standard Wireshark pcap utility that EBO uses to capture packets does not sort packets in a batch by time stamp before delivering them to the capture file it is subject to the same irregularities that we would see on any OS. Resolution This is a common enough issue that Wireshark includes a command line utility named reordercap that can fix packets that can't have been on the network in that order (like an answer being sent before you see the request for it). In the example below the utility has run through a capture and reordered items and saved the file as a new file. See the Wireshark reordercap help topic for further information on this utility.

Issue Any third party BACnet client can initiate an EBO backup. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause As of EBO 2023 (5.0.2.109), EBO's BACnet backup operation requires no password which means any BACnet client with the EBO server BACnet interface's device ID can initiate an EBO backup without any restrictions. Any such backup can be identified by looking at the backup description in EBO, the backup will explicitly indicate that it was generated by third party BACnet Workstation. Resolution EBO 2024 (V6.0.1) or higher: In BACnet Interface basic tab, "Restrict backup and restore service" can be set to Yes to ensure that third-party BACnet clients cannot perform a BACnet backup or restore on the EcoStruxure BMS server. Refer to: BACnet Interface for an Automation Server – Basic Tab and BACnet Interface for an Enterprise Server – Basic Tab EBO 2022 (4.0.4CP2 or higher) and EBO 2024 (V5.0.3 or higher): A rule can be added to the BACnet service_blacklist to disable BACnet backup service. See https://community.se.com/t5/Building-Automation-Knowledge/BACnet-RULES-implementation-to-disable-features-such-as/ta-p/839 for details on how to create service_black list. Use the following syntax to create a rule that restricts BACnet back up initiated by 3rd party BACnet client on the EBO server. <blacklist> <global> <restrict-backup-service/> </global> </blacklist> Any BACnet client requesting backup from EBO server configured with the above rule will be presented with error similar to screenshot below.

Issue WorkStation can't connect via secure communication (HTTPS) to EBO server, although it can connect via non-secure communication (HTTP). Cloud connectivity also fails. WebStation can still connect via HTTPS. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation WorkStation Cause TLS V1.3 is supported in Windows 11 and Windows Server 2022 or later. Enabling it in earlier Windows versions is not support it can lead to problems, as explained in Protocols in TLS/SSL (Schannel SSP) - Win32 apps | Microsoft Learn Resolution Do not enable TLS V1.3, If the installed Windows version doesn't support it (Windows 10 and Windows Server 2019 or earlier), or disable it if it is already enabled by following the below steps: Open Windows Registry Editor, by writing "regedit" in Start menu. Goto registry path "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.3\Client" Make sure that "Enabled" is set 0, and "DisabledByDefault" is set to 1, this will disable TLS V1.3 for clients. Restart WorkStation. For more information, refer to: Transport Layer Security (TLS) registry settings | Microsoft Learn Warning! Improper use of regedit may damage PC’s operation.

Issue When troubleshooting server issues, it can be helpful to look at the logs that are recorded within the Automation Server. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Within the Automation Server logs are many records that are logged as a part of normal operations and unexpected events. Resolution Automation Server: Automation Server error logs can be retrieved using Workstation, Device Administrator, or WebStation. Device Administrator can be used in case of crash information is required, ex. dump files, or if the Automation Server is not accessible via WebStation or WorkStation. Workstation: Connect to EBO system with EBO WorkStation. Select the target Server Expand the System folder Expand the Modules folder Expand the Trace folder and see Trace Settings For EBO 3.1 or higher, Double-click both Trace Log and System Log to open separately For EBO 3.0 and lower, including SBO 1.x Right-click in Trace Settings Select Trace Settings in the menu Select Get System Log Repeat to select Get Trace Log Device Administrator: Follow this WebHelp article: Getting Automation Server Debug Information If requested to retrieve a core dump, use this method to retrieve the Device Administrator Debug Information zip file. Then perform the following to make sure the zip file contains a core dump with a relevant timestamp for the event being investigated. Open Zip Open the folder containing the server name and IP address Open Server folder One should see file(s) with filename in this format core_dump_<Serial Number>_nsp_servers_<Timestamp>.tgz WebStation: NOTE: The steps below are no longer valid for EBO 2022 and above. See the Webhelp Topic on collecting these logs from Automation Servers: Viewing and Downloading Automation Server Log Files. This process is now similar to that described above for WorkStation. Credentials used to log in must be a member of a group that allows the policy of Web Configuration: Allow members to access Automation Server Web Configuration. Launch a web browser that is compatible with the installed EBO version as mentioned Webstation Specification Sheet. Type the IP address of the automation server to open the Webstation. Log into the Automation Server. Once logged into the Automation server, go to the Settings menu in the top right corner and click on Device Configuration. Click on the Server Log tab to view the automation server's log files. To save a copy of the log to your PC, click on the Get all log files link. The log files are compressed into a zip file and exported to downloads folder. Enterprise Server and Enterprise Central: For more information, check this article: Error logs from the Enterprise Server and Enterprise Central - Communities

Issue READ is a Script programming system function that reads trend data from a trend log into a Script program. If there is an External Logs Storage configured, is it possible to access trend log records from the External Log Storage? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause READ Script function doesn't return same number of records as trend log list or chart. Resolution The Script READ (for Trend Logs) system function can only read from the server's internal database and doesn't access records stored in the External Log Storage. For more information, refer to: Trend Log Access Functions.

Issue How to setup and configure External Log Storage in EcoStruxure Building Operation (EBO) when using Microsoft SQL Server as external log storage. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Enterprise Server Building Operation Enterprise Central Cause You use External Log Storage feature to store historical data from EcoStruxure BMS. The amount of stored data is limited only by the equipment you use, and not by the capacities of the feature. The External Log Storage feature uses an external database administered by either a combination of TimescaleDB and PostgreSQL software, or Microsoft SQL server. Resolution Please see the below video demonstrating how to: Create a database and user account in Microsoft SQL (MSSQL) Server using Microsoft Server Management Studio. Configure the External Log storage connection between EBO and MSSQL server in EBO. Also please note the following: In the video the "Host address" in EBO is set to the IP address or DNS name\SQLserver instance like this: localhost\SQLEXPRESS. If the SQL server is not located on the same computer as the EBO server only use the IP address or DNS name and no instance on "Host address". The video demonstrates using the version 5 script when configuring the database in the MSSQL server, search External Log Storage - MSSQL Installation Script to download the appropriate EBO version script. For the example query to manage user permissions download User Rights Script or see attached script.txt. If using MSSQL Express rather than the full MSSQL version it may be necessary to consult External log storage not working with SQL Server Express.

Issue In Swagger user can login but can't get the id of the root container. Below response is received: "Message": "Container Id not found" Product Line EcoStruxure Building Operation Environment SmartConnector Cause EBO user password need to be changed due to Password Expiry configured in the password policy. When user tries to login to WorkStation or WebStation, below change password dialog will be recieved. Resolution Make sure to change the user password before reaching the limit the days configured in the Password Policy. Password expiry can also be reconfigured to change number of days or disabled if not needed, refer to Configuring the Password Policy using WorkStation or Configuring the Password Policy using WebStation

Issue The en1 network adapter is not an option for assignment when configuring an IP port Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series N4 Jace 9000 Building Operation Multi-purpose Controller / VAV (MP-C / MP-V) Building Operation Room Controller / VAV (RP-C / RP-V) Building Operation IP-IO Cause With the switch to Linux for the Jace 9000's operating system, some functions such as sensing adapters work differently when configuring a controller station. Resolution In N4.13, we have added a new action to find adapters when Jace's are being pre-configured offsite. Start by confirming in the TCP/IP Configuration page that the desired port is configured and enabled. Make sure that some communicating device is connected to the desired port, exhibited by the port's lights on the unit. Examples include a workbench connection, a BACnet IP device/router, or another Niagara Device. Right-click on the "Link" component under the port, and select the "Query For Adapters" option. You should now see the port in the dropdown. Note: With N4.14, using the en1 as a DHCP server is possible. If using this with BACnet IP MP, RP or IP/IO in Space Logic controllers engineering with Niagara, this is an important consideration for network applications.

Issue How to configure and test RP controller web service Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) 24 V Building Operation Room Controller (RPC) 230 V Cause In the RP application, a REST (Representational State Transfer) Web Service API is available to facilitate secure HTTPS communications and allow you to obtain BACnet objects and properties from the controller. Resolution The following video will illustrate how to: Use the SpaceLogic certificate configuration tool to configure keys and certificates in the RP controller. Configure RP controller Web Service settings. Use SoapUI to test RP controller Web Service. Things you need: Software EBO 2022 or later server (Enterprise Server, AS-P or AS-B) and WorkStation. SpaceLogic RP controller, RP-C Advanced, RP-C Pro, RP-C Pro Plus and RP-V Advanced, with firmware V4.00.01 or later. SpaceLogic Certificate Configuration Tool, available from Exchange. Tools SoapUI (to be used for testing) For more information and how to generate certificates, please check RP Controller | Developer Portal. Note: Before configuring the Web Services in RP controller, make sure that there no pending IP changes, by checking "Changes pending" property in IP Network Settings Properties – Basic Tab. If "Changes pending" is true, click Activate changes in the IP commands menu, as explained in Configuring BACnet/IP Controller IP Network Settings For EcoStruxure Building Operation version 4.0.3 or later, a new EBO Workstation command named Export device identifying information is available. It is found in the main context menu of SpaceLogic RP Series controllers and allows the user to save an xml file that can later be imported into the SpaceLogic Certificate Configuration Tool to aid in the efficient configuration of SpaceLogic controllers within the tool. The user may select one or more RP Series controllers when executing the command. Refer to: Exporting Device Information to the SpaceLogic Certificate Configuration Tool

Issue When viewing WebReports one of the reports has a red dot Product Line EcoStruxure Building Operation Environment Building Operation WebReports Cause Need to understand what the red dot indicates Resolution When viewing the list of WebReports and the reports show one or more with a Red Dot, this designates the report as a dashboard report. A dashboard report is a report that processes fixed or predefined filtering criteria to generate report output. Unlike prompted reports, dashboard reports process the report output based on the predefined filtering criteria and generate the report output when you select the report. It is not necessary to enter filtering criteria or click the Run button to generate the report. Please see Dashboard Reports for additional information.

Issue When logging in to Web Reports, the "Reports Tree" to the left is not shown, and an error message is shown stating that login has failed for the user "NT AUTHORITY\IUSR". Product Line EcoStruxure Building Operation Environment Building Operation WebReports Cause This is a result of not following the Web Reports installation guide. The SQL Server must be installed with an instance name, and the SQL Server must be started by the user "SYSTEM". Resolution There are two solutions to this issue: Reinstall the SQL Server and Web Reports following the installation guide Use the SBO Reports Agent Config tool on the Community to give access to the 'NT AUTHORITY\IUSR' Alternatively for a more in-depth answer consult How to Fix Login Failed For User NT AUTHORITY IUSRS to add the user "NT AUTHORITY\IUSR" to the SQL Server

Issue Remote Factory Reset of SmartX IP controller MPX RPC IPIO Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RPC) Building Operation EasyLogic RP-C Building Operation EasyLogic RP-V Building Operation EasyLogic RP IO Expansion Module Building Operation EasyLogic MP-C Cause From v3.1 there is a facility to remotely Factory Reset a SpaceLogic BACnet/IP devices (formerly known as SmartX) and EasyLogic BACnet MS/TP devices. A quick look at the process and what versions of SmartX controller firmware are required Resolution Remote Factory Reset fails if the Controller is at v2.00. Remote Factory Reset operates correctly if the Controller is at v3.00 or higher. A Remote Factory Reset on a Controller with Static IP is best avoided. Although a Factory Reset is now possible, it should not be considered standard work process, but it shows that using DHCP serving of IP addresses does have advantage if a factory reset is required.

Issue When a SED-TRH-G-5045 sensor is positioned outside the range of the main EBO Zigbee wireless mesh, what is the recommended method or product to extend the wireless coverage? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Cause The SED-TRH-G-5045 is a Zigbee pro sleepy end device. Resolution Any Zigbee router within the system can function as a repeater to extend the radio communication. The router should be positioned within the radio range of the sensor and within the range of the RPx or another router. If a Zigbee device is powered by mains, it typically operates as a router. While there are currently no SE products designed solely with "repeater capability," several SE products possess router capabilities in addition to other capabilities, SE8000 SpaceLogic room controller Wiser plug CCTFR6500 Wiser Power Micromodule CCTFR6730 Wiser Room Thermostat with display CCTFR6400 or CCTFR6401. We have not officially tested any 3rd party Zigbee routers, however the IKEA TRÅDFRI repeater is known to work effectively.

Issue The first batch of White TRCs (produced in 24H1) could appear too bright in some low-light level situations. All future batches (post 24H1) do not have the issue. See the precise list of affected serial numbers in the appendix section below. Product Line EcoStruxure Building Operation Environment SpaceLogic Touchscreen Room Controller Cause The housing color is set in the device’s manufacturing configuration to tell it what color the screen bezel is (black or white). White TRCs produced with an incorrect housing color will read a higher value for light level. This has a direct impact on the backlight dimming levels, and the only effect will be the screen staying brighter in dark rooms. Resolution Customers experiencing brightness issues may simply adjust the backlight brightness parameters to a lower value, which are configurable in the TRC configuration screens and via BACnet/Modbus. This would reduce the overall brightness of the devices immediately, without fixing the housing color. We recommend going with a permanent fix, by setting the housing color via the USB port. The steps to fix this permanently would be: Connect USB-C cable to TRC Log in as an administrator into the TRC’s configuration screens (to enable USB connection) Open a terminal app like hyperterm or putty, with settings: Speed (baud): 115200bps Data bits: 8 Stop bits: 1 Parity: None Paste in the command: #001000061009FE00009C! Device responds: #000E00071009FE0051! To confirm or test, paste in the command: #000C00001009FEE8! Device responds: White housing: #001200011009FE000000F9! Black housing: #001200011009FE000001FA! Examples Below is an example of 4 white TRCs: The two (2) outermost devices are too bright (leftmost and rightmost white TRCs). The two (2) devices in the middle have been corrected to show adequate brightness. Appendix Since the Touch Room Controller’s serial number includes the date code, knowing whether a unit is impacted is very straightforward. Follow these instructions to determine if the unit of interest is impacted: Retrieve the serial number from the unit you suspect has the incorrect housing color. Example: FL24075TRC00002 Examine the serial number date code, wrapped between the “FL” and “TRC” substrings. Example: 24075 Decrypt the date code, using this logic: 24: year 2024 07: week 07 of 2024 5: day 5 of week 7 of 2024 If the date code is between the values 24074 and 24285, the product is impacted. Products outside of this date code range are not impacted, and no fix to housing color will be needed.

Issue Required a VPAT (Voluntary Product Accessibility Template) or statement of accessibility for EcoStruxure Building Operation. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause The Voluntary Product Accessibility Template (VPAT) is a document that evaluates how accessible a particular product is according to the Section 508 Standards. It is a self-disclosing document produced by the vendor which details each aspect of the Section 508 requirements and how the product supports each criterion. VPATs are used by buyers to determine how accessible a product is and where any potential deficiencies are. They are required by some buyers before a purchase is made. More Information can be found from the below public links: Section 508 of the Rehabilitation Act of 1973 Voluntary Product Accessibility Template (VPAT) Overview of Technologies and Formats WHAT IS A VPAT AND HOW IS IT USED? Resolution Schneider Electric does not have a VPAT document for EcoStruxure Building Operation.

Issue Define what Network 8000 devices that can be integrated with EcoStruxure Building Operation. Product Line EcoStruxure Building Operation, TAC I/A Series Environment EcoStruxure Building Operation Automation Server version 1.2 until and including 3.2 Network 8000 Cause Need to know the supported devices for a Network 8000 to EcoStruxure Building Operation upgrade. Resolution EcoStruxure Building Operation supports the following Network 8000 LCM devices: LCM EcoStruxure Building Operation supports the following Network 8000 ASD devices: Microzone II MicroFlo II LIM PEM The following Micronet 2000 products are supported: MN-FLO MN-FLO3T MN-HPFC MN-ASDI The following Network 8000 products are not supported in EcoStruxure Building Operation: CCL GCM LNC SIM GCM PLC Note: EcoStruxure Building Operation version 4.0 (EBO 2022) and higher are not supported

Issue How to remove an unknown Embedded Demo License Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Device Administrator v4.0.5 (EBO 2022) and below Cause The Embedded Demo Licenses are handled from the Device Administrator software. However, if the installed Embedded Demo License in the SpaceLogic servers does not comply with the file in the Device Administrator, the installed Demo License could not be removed. Resolution Instructions shown in the video below are for EBO 2022 (v4.0.5) and below. In the later releases EBO 2023 (v5.x) and above, a feature now allows the Demo licenses to be returned from selected servers. See WebHelp topic Returning All Demo Licenses from the Selected SpaceLogic Automation Servers For any License activations/returns to occur, there must be a trusted state (Certificate State) between the server and Device Administrator. Ensure that this is in place before attempting either resolution. For more info, see Certificates Managed using Device Administrator If this function does not work, you can attempt the manual file name manipulation described below. To check the name of the installed Embedded Demo License, log in to the SpaceLogic servers from Workstation. Navigate to System, LicenseManager, LicensingMetadata, ClientMetadata, Product 0. In ProductID, you will see the filename of the actual file. Rename a Demo license file and import it into Device Manager to uncheck the selected Demo License file. At the end of this session, you will be able to: Remove Unknown Demo License in SpaceLogic servers

Issue How can I troubleshoot a communication issue with the Modbus protocol Is there a log available within the AS or ES that shows the Modbus communication between Modbus devices Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Building Operation Enterprise Server Cause When troubleshooting Modbus issues in an AS or ES it can be helpful to see the communication between devices 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.pin. Right-click "nsp.pin.modbus" 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 Modbus 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. A useful tool available on the Community, the Modbus decoder can be used to assist in viewing/debugging the Modbus trace log file information saved in the previous step. 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: From v6 (2024), adding the trace below can be helpful for Modbus RTU /[ASName]/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.sport/nsp.pin.sport.DeviceRS485 Here is a video showing the above process.

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

SmartConnector RESTful gateway returns error "HTTP Error 400. The request URL is invalid."

What is the BACnet MSTP unit load of the SpaceLogic SLP sensors or Plant Room Air Quality sensors (PRAQ)

Packets from the EBO onboard packet capture utility are not ordered correctly

How to prevent BACnet client from triggering EBO backup

WorkStation HTTPS connection and cloud connectivity fail if TLS V1.3 is enabled in a non-supported Windows

Collect logs from an Automation Server

Can Script program read trend logs records from External Log Storage

Setup External Log Storage using MSSQL

SmartConnector RESTful gateway returns error "Container Id not found"

Jace 9000 Missing BACnet IP Adapters

Configure and test RP controller web service

Red Dot Report shown when viewing WebReports Reports Tree

Reports Tree not shown when logging in to Web Reports

Remote Factory Reset of SpaceLogic and EasyLogic devices

Extending EBO Zigbee Wireless Mesh Using Repeaters

Screen Brightness Issue on White TRCs

VPAT or statement of accessibility for EcoStruxure Building Operation

EcoStruxure Building Operation integration to Network 8000 - Supported Network 8000 devices

Remove Unknown Embedded Demo License

Capture a Modbus trace log in EBO/SBO

Building Automation Knowledge Base

Related Forums

This is a heading