Building Automation Knowledge Base

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.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue It is sometimes necessary to move a previously configured Infinet i2 device from one Infinet network to another in the same parent Automation Server. EcoStruxure Building Operation does not provide an automatic way to move an i2 device; it must be done manually. Product Line  EcoStruxure Building Operation Environment Building Operation Automation Server Cause Guidance on steps to move Infinet i2 device from one Infinet network to another in the same host Automation Server Resolution In this example, we are going to move multiple Infinet i2 devices from the Infinet network on COM-A to the Infinet network on COM-B.   Backup Make sure to make a backup of the Automation Server before attempting the steps below. This is in case there is a need to revert the changes for whatever reasons. Export Devices from COM-A From COM-A Infinet network, display a List View of the devices, making sure to have columns displaying the Infinet ID and Serial Number. Write down the Infinet IDs and Serial Numbers of the devices to be moved. In the List View, multi-select the devices to be moved, right click and perform an 'Export', leave the Export Reference Filter at default (Export). After successful export, right click on the selected devices again and delete them from COM-A Infinet network. Prepare COM-B for Import From COM-B Infinet network, display a List View of the devices, making sure to have columns for Infinet ID and Serial Number. Observe the Infinet ID column, and compare with the notes taken above of the moving devices' Infinet ID, for IDs that are already in use in COM-B, you will need to assign a new ID to the device moving from COM-A Infinet network to COM-B, update your notes to include an available ID on COM-B. (see example below of what the notes might look like)   Import Devices to COM-B ***  In the System Tree, select the COM-B Infinet network and perform an import of the XML file created via export above. Physically move the devices from COM-A Infinet to COM-B Infinet. When doing so, avoid introducing duplicated Infinet IDs into COM-B Infinet. Make sure to power down the devices you are moving, connect them to COM-B Infinet, and only then power up the devices. On power up, the devices perform an ID check and stay off the bus if they detect their IDs are already in use. Configure Devices in COM-B From COM-B Infinet network, display a List View of the devices making sure to have columns for Infinet ID and Serial Number. Right click each device moved from COM-A Infinet to COM-B Infinet, and select "Properties", in the "Advanced" tab, enter the appropriate Infinet ID and Serial Number for the device then click "OK". In the List View, right click the device from previous step again, select "Device->Commission", after successful commission the device should go ONLINE Final Steps After all the moved devices are online, you should download ALL (whether moved or not) the devices to have their programs recompile and rebuild their Import/Export tables. Fix any references that were lost due to devices changing Infinet network and Infinet ID *** NOTE Due to an issue that was corrected in EBO 6.x, import may fail with error "Invalid InfinetId", the workaround for this problem is to manually create the Infinet devices on the destination port using the appropriate name, serial number and Infinet ID, then do the import selecting the option to merge on conflict.

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

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Why is it recommended to not mix high and low voltage connections on the same side of an CRS-HH-REL-10? Product Line EcoStruxure Building Operation. Environment Building Operation Room Controller (RPC) 24 V Building Operation Room Controller (RPC) 230 V Cause According to the documentation, it is not recommended to mix high and low voltage connections on the same side of the device.   Resolution There must be a minimum distance between terminals connected to High Voltage and terminals connected to Low Voltage of at least 5.5 mm to prevent the chance of voltage creep between the terminals.

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 The instance values the Function Block program had when the backup was taken is lost when the backup is restored in an AS-P running in PCT. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause When the program is first initiated, the values for it is written to the database. If the “Program executions” Is turned off, the instance values the program had when the backup was taken is not read. Hence the values are set to 0.   On a real AS-P, a Cold start is performed after the restoring of the backup. When restoring a backup on an AS-P in PCT, one or two cold starts are done, followed by an additional warm start at least for the PCT 2. Resolution To get the instance values from the backup when it is restored, the “Program execution”/”Enable program” In PCT should be turned on before the restore is done.   Since a warm start is done for the PCT, the issue regarding Retain level vs. FB Backup property needs to be taken into consideration. https://ecostruxure-building-help.se.com/bms/Topics/show.castle?id=15741&locale=sv-SE&productversion=7.0&a=1

Issue What is the compatible SpaceLogic BACnet/IP device firmware version for my EBO or Tridium Niagara N4 installation? Product Line EcoStruxure Building Operation, TAC IA Series Environment SpaceLogic BACnet/IP devices Tridium Niagara N4.10 and later versions Jace 8000 Tridium Niagara N4.10 and later versions Enterprise Server  Cause The SpaceLogic (formerly known as SmartX) IP Controllers shipped from the factory may not have the latest firmware installed. It is essential to verify that the controller has the latest firmware build loaded for the EcoStruxure Building Operation version or Tridium Niagara N4 build being used before programming the controller. Resolution The below table contains the supported SpaceLogic BACnet/IP devices firmware for each EBO release.  * CPs are available on: EBO Hotfix List Note: Versions not mentioned in the table above are out of full support. Refer to earlier versions' release notes for the older versions' compatibility matrix, refer to EBO- Release Notes and Software Support Policy for EcoStruxure™ Building Operation   Note: RP-C is only supported on EBO 3.0 and later SpaceLogic/EasyLogic versions compatibility SpaceLogic BACnet/IP devices can be upgraded using WorkStation, as explained in Updating Firmware in BACnet/IP Controllers.  SpaceLogic BACnet/IP devices firmware can also be upgraded using the eCommission SmartX Controller mobile application, you can download firmware to either a single BACnet/IP controller or multiple controllers, even if not hosted. This is only supported over an IP connection, as explained in Using the eCommission SmartX Controller Mobile Application to Download Firmware to BACnet/IP Controllers   Tridium Niagara N4 Compatibility Note: Previous to Version 1.0, SpaceLogic BACnet/IP devices firmware is only approved at v3.02.03 for Jace 8000 and Niagara Enterprise Server using N4.10 and newer platforms. Starting in Version 2.0 (Build 77) firmware v4.00.04.02002 CP1 is approved for use.  Make sure and reference the controller type in the table above as well. Release Notes  Starting with Version 3.1 (Build 85), firmware 6.00.03.03007 CP2 and 7.x RC can be employed. The EasyLogic controllers are supported by the Niagara modules with these releases.  N4.10, 4.13 and 4.14 are the only versions with these modules. Product Annoucement      

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.     

Issue Why do the Architectural Guidelines specify a maximum of 1500 Extended Trend Logs in Automation Servers, whereas such a limitation did not exist with the Continuum Net Controllers, like the NetController II.   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause EcoStruxure Building Operation's architectural guidelines specify a limit of 1500 Extended Trend Logs for the Automation Servers (AS-P/AS-B). Sites transitioning from Andover Continuum to EcoStruxure Building Operation need to understand the architectural differences that necessitate this limit. Resolution The architectural differences between Continuum and EcoStruxure Building Operation means that it is crucial that Extended Trend Logs are managed effectively to ensure ensuring optimal system performance.   In Continuum: Controller Role: Controllers do not participate in Extended Trend Log functionality beyond sending data from intrinsic logs upon request from Cyberstations. Log Management: Extended Trend Logs reside at and are managed by Cyberstations. Load Distribution: Multiple Cyberstations, configured to collaborate, maintain the Extended Trend Logs, minimizing the load on controllers.     This design puts very little load on the controllers when it comes to Extended Trend Log functionality.   In EcoStruxure Building Operation: Distributed Database Architecture: Extended Trend Logs are managed by the AS-P/AS-B servers. Server Load: The server performs tasks typically handled by multiple Cyberstations in Continuum, which often run on more powerful PC hardware. Performance Management: To prevent Extended Trend Log servicing from overwhelming the Automation Server's resources (CPU, memory), a limit of 1500 logs is enforced. Exceeding this limit can degrade server performance and potentially cause reboots due to critical memory usage.  This can be seen in the following example trace log entry: Nov 30 15:39:58 PSS-AS02 memcritsv[1011]: Memory usage critical!    

Issue PCT2 is unreachable using IP 192.168.10.2, with messages similar to: 504 Gateway Timeout Server error - server 192.168.10.2 is unreachable at this moment. Product Line EcoStruxure Building Operation Environment Project Configuration Tool (PCT) 2 Cause The Hyper-V Virtual Ethernet Adapter in Windows, labeled vEthernet (SwitchPctInternal), is not configured with the proper static IP address. It may be incorrectly configured as DHCP or with an incorrect static IP address Resolution Open Properties for vEthernet (SwitchPctInternal) Go to the Networking tab. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties. Configure the IP Address: Select Use the following IP Address. Ensure the IP address is set to 192.168.10.1. Set the subnet mask to 255.255.255.0. Leave the gateway field blank. Additional Notes Ensure that no other network adapters are conflicting with the vEthernet (SwitchPctInternal) settings. Verify that the PCT2 device is properly connected to the network.

Issue Building Commission (EBC) self closes at Login screen in Windows. It seems to be after application is unused for an extended period of time. Product Line EcoStruxure Building Operation Environment Building Commission Tool Cause There is a fault in Microsoft.ui.xaml.dll as observed in the Windows Event Viewer. Resolution Uninstall the application via Windows Add or Remove Programs Reinstall the application via the Microsoft Store Open this link in a browser Building Commission - Free download and install on Windows | Microsoft Store Click Open in Store App button in upper right by sign-in

Issue EcoStruxure Building Operation allows using a period embedded in the name of an object (i.e My.AnalogValue) and  the name of a binding variable in the Script program cannot contain a period.     In the Script program all the periods in the binding variable names have to be changed to a different character such as the underscore (_).   This in turn causes a problem for a programmer that has created many objects using the period in the names as it is now NOT possible to use the default name matching binding template. Product Line EcoStruxure Building Operation Environment Script Programs Enterprise Server Automation Server Cause Script programs do not allow a period '.' in binding variable names because the period has special functionality in the Script compiler. Resolution Create a new path matching binding template or edit an existing one to map the underscore to the period.     Here is a second example:   Name of point/value contains embedded '.' as well as spaces      This is what the binding variable would look like in the Script program   and here is the Path Matching Template