Building Automation Knowledge Base

Issue Programming for the use of Smartware Technologies DUIC-5P-12v input multiplexer Product Line TAC IA Series, EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation RP-V VAV Building Operation Room Controller I/A Series N4 Jace 8000/9000 I/A Series N4 Enterprise Server Building Operation Automation Server Premium Cause Define the application programming and configuration of the DUIC-5P-12V in various enviroments using SpaceLogic contollers Resolution The DUIC-5P-12V Card allows for conversion of a single universal input channel to accept up to five voltage free contacts of any mixture such as mercury wetted, Triac, etc., which may have inherently large and varying resistances. The DUIC-5P-12V on-board circuitry allows the controller inputs to have a consistent input reading, unaffected by long lead lengths, varying resistances, etc.  Smartware Technologies Documents includes programming for use in SpaceLogic devices under an AS-P in the form of a Function Block program. When SpaceLogic controllers are used in the Niagara Frameworks Jace 8000/9000 or hosted directly under a Niagara Frameworks Enterprise Server, the programming is done in a Visual Script Programming format utilizing the Schneider MPX modules in Workbench. The documentation addresses the original use for the I/A Series MNL and MNB contollers as well. NOTE:  The device requires half wave 5 -12 DC or 24 VAC only to prevent damage

Issue Fail to apply CP or HF on AS Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation EcoStruxure Building Operation Automation Server (ASP/ASB) Cause The Automation Server is not installed next to the Power Supply. The requirement is stated in the Hardware Reference Guide, Position 1 is reserved for a power supply. Position 2 is reserved for an automation server. Resolution When the update process fails, please collect the DebugInformation. Next, check the System.log for the node ID. If the node ID is not  2 , it indicates that the AS is not installed at the correct address. In that case, the physical location of the AS needs to be corrected. Example of incorrect ID location Relevant Resource: Multiple Automation Servers on the same backplane

Issue PCT 2.0 shows "503 Service Temporarily Unavailable" error when trying to reach to PCT server. Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause The PCT 2 disk has a fixed size limit of 200GB and cannot be expanded by users. Once the disk reaches full capacity, access to PCT 2 becomes unavailable. Resolution Check the size of the "data.vhdx" file: The file resides in the "Virtual Hard Disks" folder. This folder can be found in the path selected during the installation. Folder location: Navigate to the installation path to locate the "Virtual Hard Disks" folder. File location: Inside the "Virtual Hard Disks" folder, locate the "data.vhdx" file. Check the size of the "data.vhdx" file.   If the disk size is over 200GB, contact local support and attach the information.   

Issue Locate the Evaluation license for TAC Vista or EcoStruxure Building Operation Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista EcoStruxure Building Operation Cause EBO 7.0 and later: Building Operation 7.0 introduces the Engineering license, which enables a system to run during the project phase without the need for commercial licenses or what has previously been referred to as demo licenses/evaluation licenses which have a short validity and require frequent updates and re-engineering.   EBO 2024 (6.0) and earlier: There is an evaluation license for EcoStruxure Building Operation valid 3 months.    TAC Vista: Starting September 1, 2025, the evaluation license will only be available upon request for Schneider Electric employees using the support@Schneider portal. Should an EcoXpert™ partner require an evaluation license, they must request this from their Schneider Electric contact. Resolution EBO 7.0 and later: Engineering licenses can be downloaded from the EcoStruxure Power & Building Software Companion during the project phase, and when the time comes to commission and hand over the project to commercial operation, the portal provides the ability to convert Engineering licenses to Commercial licenses by simply submitting a license purchase order. No replacement or re-engineering of the license is required thanks to this one step operation.   Engineering licenses have a validity of 6 months, after which it is possible to extend for another 6 months if the project timeline demands it.   *Note that Demo licenses are still available for WorkStation Pro, enabling a limited time operation of WorkStation Pro use. For full uninterrupted operation, please use a commercial WorkStation Pro license.   EBO 2024 (6.0) and earlier: Evaluation license files are available for licensed partners on the EcoXpert Extranet. Follow the link and search for "evaluation". You must first register using your business email (i.e. CustomerName@partnerdomain.com) address to gain access to these files. Note: You may use any email address to register and view content, but downloads will only be granted to approved partner domain names.   TAC Vista: Only be available upon request for Schneider Electric employees using the support@Schneider portal To request a TAC Vista evaluation license, follow the steps outlined below: Open a case on ”Digital Offer Sales & Provisioning App Request” - What is your request related to? > Digital Supply Chain – Request - Please Select the Environment > Production - Please select the Offer > TAC VISTA - Please enter the SESA ID… > The SESA ID of the Schneider employee creating the ticket - Please select the type of Request > Create - Please select the type of Create new request > Demo license creation - Please select your country > The country of the person creating the ticket - Please provide business justification > Reason why the license is needed When submitting the ticket as above, the ticket will be handled automatically, and an email will be sent to the user. Subsequently the ticket will be closed automatically.

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 The added to parent column shows incorrect information. PCT 1.X  PCT 2.x Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause PCT doesn't detect detachment in WorkStation. Resolution Do not detach the child server from its parent in PCT 1.x and 2.x. Webhelp information: Adding a Virtual EcoStruxure BMS Child Server to a Parent Server.

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 When hosting objects from EWS/Smart Connector, such as Security Expert, into EcoStruxure Building Operation (EBO), additional or mismatched object names can result in unresolved bindings and duplicate EWS IDs. Common symptoms include:  - Duplicate EWS IDs with different names - Unresolved or broken bindings - Binding loss after deleting containers   Duplicate EWS IDs with different names Unresolved or broken bindings     Product Line EcoStruxure Building Operation, EcoStruxure Security Expert. Environment EcoStruxure Building Operation Enterprise Server (ES) Security Expert Smart Connector Integration EcoStruxure Web Service (EWS) Cause Typical reasons for this to occur: Hosted object names do not match those in Security Expert. Deleting containers without proper renaming can cause binding loss. Resolution   Best Practices for Future Hosting Always rename the hosted object in EBO before rehosting from the hardware folder. This ensures that existing bindings are preserved. Avoid hosting the entire `SecurityExpertServer` container—only host changed or new objects. For Unbound or Irrelevant Objects: - If objects have no bindings, naming is not critical from an EBO perspective - Delete the container and rehost the object from the **Hardware folder**.   To Retain Existing Bindings  Identify the correct object name in the Hosted Containers folder  Copy the name to avoid typos. Delete the duplicate object with the correct name. Rename the existing EWS ID to match the copied name. Save the rename Verify bindings: Right-click the renamed object Select Delete Click Show References Confirm bindings are still valid. Click No to cancel deletion. Repeat this process for each object (inputs, outputs, doors, etc.) that has existing bindings.  

Issue Unable to log into Workstation because the user password is unknown. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server (AS, AS-P, or AS-B) Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Project Configuration Tool (PCT) Cause The password for an Automation server or Enterprise server/Central has been forgotten. Resolution IMPORTANT: The session ID is unique for this session of WorkStation. You cannot close WorkStation until the password has been reset. If you close WorkStation, before the password has been reset, a new session ID is generated that cannot be used with the temporary password provided by your local Schneider Electric Buildings support team.       The following are the steps to populate the session ID, which is required for doing the password reset.   For servers with EBO older than V3.1.X In the WorkStation logon page, while holding the shift key, left-click the area near the EcoStruxure Building Operations Icon.   This will populate the Session ID. Copy the Session ID.   For servers with EBO V3.1.X:   In Device Administrator, select the server you need to perform the reset to. Check the box and click the hyperlink   From the top bar select Password Reset Select OK when you get the “Password reset token created” pop-up Now, on the WorkStation logon page, while holding the shift key, left-click the area near the EcoStruxure Building Operations Icon. This will populate the Session ID. Click the Copy button.    For servers with EBO V3.2.X and higher In Device Administrator, select the server you need to perform the reset to From the top bar, select the “Edit Connection Password/Reset password” and press OK Now, on the WorkStation logon page, while holding the shift key, left-click the area near the EcoStruxure Building Operations Icon. This will populate the Session ID. Click the Copy button.   For servers within PCT 2.X Start the server Left click on the Server Menu  Select "Set password reset mode"  Now, on the WorkStation logon page, while holding the shift key, left-click the area near the EcoStruxure Building Operations Icon. This will populate the Session ID. Click the Copy button.    NOTE (for servers with EBO V3.1.X and higher)  For the Automation Server password reset, ensure that the Automation Server is connected to your PC machine via a USB cable. For the Enterprise server and Enterprise Central password reset, add the server to the Device Administrator using the “Add Server” button on the top bar. Please note even if you enter the wrong password, the Server would still be added to the Device Administrator.     After having the Session ID:   Send the Session ID to your local Schneider Electric Buildings support team Once PSS provides you with the unlock key In WorkStation, ensure that the Session ID is still visible, enter: User Name: admin Password: paste the result from the webpage Domain: Local and click Log On This will pop-up the Change-Password form Fill in the “old password” field with the unlock Key Put in a new password you want to use and then enter the new password in again. Click OK   NOTE:  When attempting to reset the password and unlock with the sessionid/temp password, you receive the error: "Your account has insufficient permission to use the system. Contact your administrator. "  Open a case with your local Product Support group and submit a request to unlock the user.   NOTE: WebHelp article 6749   The following video shows the password reset procedure for EBO older than V3.1.X. It covers most of the important steps for newer versions. Quick-Help video    

Issue In EcoStruxure Building Operation (EBO) version 3.1 and later the password reset function have changed, how does it work, and what is changed from before? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Project Configuration Tool (PCT) Cause The changes have been done due to cybersecurity issues. The basic workflow is the same as before but the generation of the reset token has changed. Resolution IMPORTANT: The session ID is unique for each session of WorkStation. You cannot close WorkStation until the password has been reset. If you close WorkStation, before the password has been reset, a new session ID is generated that cannot be used with the temporary password provided by your local Schneider Electric Buildings support team.  See online help topic: Copying the Session ID when Resetting the Password   To get a password reset token in version 3.1 and later you need to set the server in password reset mode(valid 24 hours)   For Automation Server(AS, AS-P, AS-B) this is done using the Device Administrator(DA), a USB connection is required between the computer and the server   For the Enterprise Server(ES) administrator privileges on the PC where the ES is installed are required. The ES is set in password recovery mode using the DA, the DA needs to be started as an administrator.   For the virtual server environment, Project Configuration Tool (PCT) tool is used. To get access to the password reset mode, the server needs to be started.     For detailed information please see the video: 

Issue BACnet requires applications to listen on the same port across the IP subnet to receive BACnet discovery broadcasts. Two applications running on the same machine can not use the same port as the Listening Port. Product Line EcoStruxure Building Operation, Continuum, TAC I/A Series Environment Building Operation Enterprise Server I/A Series WorkPlace Tech Continuum Cyberstation Cause The site can not provide a separate machine or VM for each BACnet application, which is recommended for independent operation. Resolution With this configuration, one application will act as BBMD to receive and distribute BACnet Broadcast Messages. The other application will act as a Foreign Device, relying on BBMD to relay BACnet Broadcast messages. Once BACnet devices and the Application, configured as Foreign Device, have shared their IP and Port, messages between them will be unicast and will not pass through the BBMD. Ensure one application can be configured as a BACnet BBMD and the other as a Foreign Device. Configure one as BBMD, usually EBO Enterprise Server Configure the other application as a Foreign Device referencing the BBMD IP and Port

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 "Debug", then click ok. In EBO 7.0 and higher, "Debug" will report 1 line per transaction, where "Trace" will report 8 lines for the same transaction. In EBO 7.0 and higher, instead of logging all Modbus with "nsp.pin.modbus," you can log separately Modbus TCP and Modbus Serial using either "nsp.pin.modbus.CommunicationLayer.ModbusCommsLogger.Serial" or "nsp.pin.modbus.CommunicationLayer.ModbusCommsLogger.TCP" 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. 

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 BACnet/IP controllers are not configured in RSTP Mode by default, therefore must be configured during installation. Having RSTP Mode disabled by default allows one to connect BACnet/IP controllers to any switch, even with port security configured to detect BPDU packets and disable the port. Product Line EcoStruxure Building Operation, TAC IA Series Environment Multi-purpose Controller (MP-C) Multi-purpose VAV (MP-V) Room Controller IP-IO I/A Series N4 Jace8000 SmartX IP Driver for Niagara Cause RSTP protocol requires that controllers, switches, and network architecture are configured to ensure the protocol will operate as expected.  Resolution Setting RSTP Mode for BACnet/IP Controllers ALL devices in the RSTP loop MUST BE IN RSTP MODE to function properly. This is not a huge issue because during startup you can unplug 2nd side of the loop and it will function properly in a daisy chain. Ensure the SmartX Controllers are configured correctly Configuring BACnet/IP Controller Device Settings A factory or network reset returns the RSTP setting to Disabled. Important: Whenever you change RSTP settings, the controller MUST be WARM START. If you fail to perform this restart, the BACnet/IP controller will continue communicating using its previous RSTP settings. 'Activate IP Changes' does not affect RSTP mode. Ensure the switch is configured correctly per Configuring RSTP on a Managed Switch for SmartX IP Controllers. If asked to review this for a case, please provide PSS screenshots from the switch configuration page(s).  Bridge Priority = 4096 Hello Time = 2 sec Max Age = 40  (40 is the maximum value allowed by the protocol. Default is 20) Forward Delay = 21 sec Bridge Priority Considerations Change Bridge Priority by adding 4096 as switches get further away from AS. (8192, 12288, 16384, 20480, 24576, 28672) DO NOT set the priority as 32768 or higher because that is the built-in Bridge Priority of BACnet/IP Controllers. First, configure the Root Bridge Switch (closest to the Automation Server) settings. Then, configure the additional Switches in order of increasing Bridge Priority. Plug in 2nd side of the RSTP Loop If all devices stay online, then it is working properly. Now test line breaks or controllers that are powered off. If all devices go offline and/or the switch LED is flashing rapidly, then go to RSTP Troubleshooting. Managed Switch Troubleshooting Consult the documentation or contact the vendor or manufacturer to assist with configuration for the items below. Ensure the switch is IEEE 802.1D - 2004 capable. BACnet/IP Controller Networking Term Definitions RSTP Ring mentions the Rapid Spanning Tree Protocol is specified in IEEE 802.1D - 2004. Ensure the firmware is up-to-date by contacting the vendor or manufacturer or downloading it from its website. Ensure ports not participating in RSTP are configured as Edge Port, Admin port, or have STP disabled. Nomenclature for those settings on your specific managed switch may vary. Adding BACnet/IP controllers to site-managed switches, work with Local IT to add these devices to their network. They will need to work with their switch vendor/manufacturer/support group to ensure the configuration of those switches because it could be more complex than changing the minimum recommended four settings above. Also, since RSTP Protocol is limited to Max Age = 40 (hops including site switches and BACnet/IP controllers), each loop's size may be limited based on their site switch network configuration and architecture.  Determined the proper configuration (or disable) for the following features. DHCP snooping Dynamic ARP inspection Denial-of-service (DOS) mitigations BPDU Guard BPDU Filter RSTP Troubleshooting Check each BACnet/IP Controller -> Diagnostics -> Device Report to confirm in RSTP Mode MANUAL CHECKOUT Double-click MP - Diagnostics Files - Device Report It will open in the default text editor Review the Device Settings section near the bottom. In firmware 1.00.0x, the report should report RSTP Mode: Enable In firmware 2.00.0x or higher, RSTP: Enabled and RSTP Status: Operational If it reports disabled, then perform Setting RSTP Mode for BACnet IP Controllers Step 1 until RSTP is working properly. USE SEARCH & EVENTS EBO 2.x MP Device IP and Settings.xml for EBO 2.0 as it only includes MP controllers EBO 3.x SmartX Device IP and Settings.xml for EBO 3.x or higher Import attached search USE RSTP STATUS GRAPHIC IN WEBSTATION MUST BE EBO 3.1 or higher which includes ClientAPI support Frontline Fridays Episode 02 - Rapid Spanning Tree Protocol (RSTP) Date: 2022-11-11 Mike Botens posted the following in the thread: RSTP Status TGML dated 2022-11-09 PDF of the presentation Fusion Fridays - Session 07 ​​​​ Date: 2020-05-28 The start of the video shows the graphics page in use RSTP Status.zip is downloaded via the link below the video. Extract the TGML and drop it on the AS to import. The suggestion is to store TGML directly under the AS to help with navigation in Webstation. bind Network to the BACnet/IP network with the BACnet/IP Controllers. (You may need a second TGML page if BACnet/IP controllers are on Primary and Secondary IP) Run from web browser via WebStation because utilizes ClientAPI KNOWN ISSUES Offline controllers that are scattered are NOT an RSTP issue. Check to see if there is a possible DHCP issue by verifying controllers are still at their AUTO-IP address (IP 169.254.nnn.nnnn Subnet Mask 255.255.0.0). RSTP communications issues affect the entire RSTP loop or one contiguous group of controllers. Factory Reset or controller replacement should leave one ethernet cable unplugged until configured for RSTP per these articles: Replace a BACnet/IP Controller in an RSTP Ring Network Workflow and MP Controller Reset Modes If BACnet/IP Controller Device Report OR RSTP Graphic reports RSTP Status: Changes Pending instead of RSTP Status: Operational, disable RSTP Mode, Warm Start, re-enable RSTP Mode, Warm Start, and check again. SmartX is now SpaceLogic. KNOWN ISSUES with Firmware affecting RSTP: If Firmware 3.02.01 is installed, please upgrade to 3.02.02. RSTP not performing as expected with Static IP addressing RSTP does not work well on RPC HW RPC-16-B HW revision 6

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 How can EcoStruxure BMS server serve data to external devices or software? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Third party devices or software Cause The EcoStruxure Building Operation software supports the major communication protocols in building automation and security management. In many projects, it is required that an EcoStruxure BMS server serve data to external devices or software, E.X. HMI, SCADA or power monitoring. Resolution The following is a summary of the available options to serve EcoStruxure BMS server data to the external world: BACnet:  When you create a BACnet Interface, the system automatically creates the Application and IP network folders within the BACnet Interface folder on the System Tree. If you create a BACnet Interface for a SmartX server, you can optionally create an MS/TP network. You can create BACnet objects in BACnet application folder of EcoStruxure BMS servers and these object will be visible for external BACnet clients. More information about EBO BACnet interface: BACnet Interface   Modbus Slave network:  If you configure the Modbus Slave Network (and associate it with a serial port), you can set up any external Modbus master device to communicate with the internal Modbus Interface. In this example, a Modbus Slave Network is set up on an EcoStruxure BMS Server and the external master device is configured with the same Modbus properties as the Modbus Slave Network object. The Modbus master device can also be an HMI device. More information about Modbus serial interface: Modbus Serial Networks Modbus server network: You can create a Modbus TCP Network on an Ethernet network (TCP/IP).  You can create an internal interface which acts as the server to an external client/clients. More information about Modbus TCP interface: Client and Server Networks   MQTT: MQTT is a lightweight and flexible data transfer protocol for IoT resources. EcoStruxure Building Operation, V3.2 or higher, can be configured to send data to an MQTT broker on interval or event-driven. The below are the tested brokers: Microsoft Azure IoT Hub Amazon IoT Core IBM Watson IoT Mosquitto More information about MQTT interface: MQTT Overview LonWorks Interface: EcoStruxure BMS servers can have a local node on their networks that can act as a LonWorks node. In the local node, you can create your own NVs that can be bound to external LonWorks devices using LonWorks bindings. The NVs in your local node can then be used in EcoStruxure Building Operation bindings for applications and graphics. More information about LonWorks interface: LonWorks Engineering   SNMP: Simple Network Management Protocol (SNMP) is an Internet-standard protocol for managing devices on IP networks. The EcoStruxure BMS servers support SNMP version 3. The SmartX servers support several SNMP traps. SNMP traps enable an agent to notify the management station of significant events by way of an unsolicited SNMP message. More information about SNMP: SNMP EcoStruxure Web Service (EWS) server: EcoStruxure Web Services allows seamless sharing of operational data, including alarms and historical information, between software from different Schneider Electric Business Units. When the EcoStruxure BMS server is an EcoStruxure Web Service server, it exposes objects, such as values, to another EcoStruxure system that is an EcoStruxure Web Service client. The EcoStruxure Web Service client can read and change values on the EcoStruxure BMS depending on the configuration of the EcoStruxure BMS server. More information about EBO EWS Server: EcoStruxure Web Service Server Smart Connector: A development framework that simplifies and accelerates integrations with third-party systems or other data sources. It is an open, extensible and configurable application framework that allows developers to create innovative new capabilities, applications, and solutions which extend and enhance EcoStruxure Building solutions. Ex. SmartConnector can be used to serve EBO data in a RESTful manner, refer to: Configure SmartConnector RESTful EWS Gateway to serve EBO data   For further information watch the Smart Connector explainer video or visit the Smart Connector Developer Community on the Exchange: For developers wanting to get started using the Smart Connector framework visit: https://www.smartconnectorserver.com Smart Connector at Exchange:  EcoStruxure Building Operations SmartConnector 

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.