Issue Clarification on the term "Semi Online System" within EcoStruxure Building Operation environments. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Device Administrator Cause The term refers to a specific system configuration used when full internet connectivity is not feasible for all components of the Building Management System (BMS). Resolution A Semi Online System is designed for secure environments where internet access is restricted for core systems but still allows licensing and administrative operations. Here's how it works: System Components EcoStruxure BMS Servers Network These servers are not connected to the Internet. They cannot access the License Activation Server. Device Administrator Computer This computer is connected to the Internet. It has access to the License Activation Server. It can also connect to at least one field server within the BMS network. Licensing Implications The system is treated as online for licensing purposes. Offline licensing workflows are not required. Licensing and administrative tasks are performed via the Device Administrator, which bridges the gap between the internet and the isolated BMS servers. Benefits of a Semi Online System Security: Core systems remain isolated from the internet, reducing exposure to external threats. Flexibility: Licensing operations can still be performed without requiring full internet access for all components. Compliance: Suitable for environments with strict IT policies or regulatory constraint

Issue To downgrade an Automation Server, a DFU procedure must be performed on the device Product Line EcoStruxure Building Operation Environment Automation Server Cause When deploying a 'New Database' to an Automation Server, the controller must first be cleared of existing data. The firmware is then reloaded with a blank database image. This process may require placing the device into DFU mode to complete the installation successfully. Resolution To reset an automation server to DFU mode:   Start the Device Administrator. For more information, see Connecting to an Automation Server Using the USB Device Port . On the automation server, press the Reset button 3 times within 2 seconds.     Use a USB cable to connect the USB device port on the automation server with a USB port on the PC. Ensure that the automation server is displayed in the list and DFU mode is displayed in the Device status column.   The automation server is now ready for the upgrade procedure. For more information, see Uploading and Upgrading a Field Server .

Issue When attempting to log into a remote Enterprise Server using EcoStruxure Building Operation WorkStation, the following error is displayed: “No valid client license available. (Error -5: No such feature exists.)” This occurs despite the Enterprise Server having available client licenses   Product Line EcoStruxure Building Operation Environment EcoStruxure Building Workstation  EcoStruxure Building Operation License Administrator Cause The WorkStation application is attempting to acquire a client license from the local machine’s default license server address ( @localhost ). However, the active license is hosted on the Enterprise Server, which is configured as the central license server. Since no license is available locally, the request fails with error code -5 . Resolution To redirect the license request to the correct server: Launch License Administrator On the WorkStation client machine, open the License Administrator utility. Modify License Server Address Navigate to the License Server Address field. Replace the default value @localhost with the IP address or hostname of the Enterprise Server hosting the license. Example: From: @localhost To: 192.168.1.100 Apply and Restart Save the configuration and restart WorkStation to apply the new license server settings. Notes: Ensure network connectivity between the WorkStation client and the Enterprise Server. The Enterprise Server must have the License Server service running and properly configured. Refer to the WebHelp documentation for detailed steps on configuring license server addresses  License Server Address 

Issue When migrating a SmartX Controller (e.g., MP-C, MP-V, RP-C, IP-IO) from one Automation Server to another within the EcoStruxure Building Operation platform, you may encounter the following error: The following devices appear to be hosted by another server. In order to host them, you must first right click the device and select "Clear host information"   This happens because SmartX devices are designed to be hosted by only one Automation Server at a time. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Automation Server (AS-B, AS-P) Multi-purpose Controllers (MP-C, MP-V) Room Controllers (RP-C) IP-IO Modules Cause SmartX Controllers maintain persistent host binding metadata. When a controller is discovered by a new Automation Server,  it checks for existing host assignments. If the controller is still linked to a previous Automation Server, the system prevents reassignment to avoid conflicts in device management and communication. Resolution 1. Open Device Discovery In WorkStation, navigate to the Device Discovery tab of the target Automation Server. 2. Locate the SmartX Controller Initiate a BACnet device scan. The controller will appear flagged as hosted by another server. 3. Clear Host Information Right-click the detected controller. Select “Clear Host Information” from the context menu. This removes the previous host binding. 4. Re-host the Controller Add the controller to the new Automation Server’s configuration tree. Proceed with commissioning as usual. Best Practices Always ensure the previous Automation Server is offline or has released the controller before reassignment. Use consistent naming conventions and documentation to track controller assignments. Perform backups before making host changes to preserve configuration integrity.

Issue Understanding whether a building automation product is certified by the BACnet Testing Laboratories (BTL) is crucial for ensuring interoperability, reliability, and compliance with industry standards. Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series Environment Schneider Electric Building Management Systems BACnet-compliant devices Cause In the world of building automation, interoperability and reliability are paramount. That’s why many professionals rely on products certified by the BACnet Testing Laboratories (BTL)—a globally recognized authority that ensures BACnet-compliant devices meet rigorous standards for functionality and interoperability. Resolution What Is BTL Certification? BTL Certification is a formal recognition that a product has passed independent testing based on the BACnet standard. Administered by BACnet International, the certification process involves: Testing by a Recognized BACnet Testing Organization (RBTO) Verification against the industry-standard BACnet test package Issuance of a Certificate of Conformance Inclusion in the BTL Listing of Tested Products database Certified products display the BTL Mark, a symbol of quality and assurance that the device will integrate smoothly into BACnet-based systems. How to Verify BTL Certification To determine if a product is BTL certified: Visit the BTL Listing Database Navigate to the BTL Listing of Tested Products and search by: Manufacturer Product name Product category Look for the BTL Mark Certified products typically display the BTL logo on: Packaging Datasheets Product casing Review the Product’s PICS Document The Protocol Implementation Conformance Statement (PICS) outlines supported BACnet features and is available in the BTL listing. Schneider Electric and BTL Certification Schneider Electric is a leading provider of BMS solutions, and many of its products are BTL certified. These include: EcoStruxure Building Operation Servers (AS-B, AS-P, ES) SpaceLogic Controllers (MP-C, MP-V, RP-C series) Smart Field UC Controllers Andover Continuum Controllers These products support native BACnet communication and are designed for seamless integration into smart building environments. For example, the SpaceLogic AS-B server is a BTL-listed BACnet device that supports BACnet/SC, Modbus, MQTT, and other protocols, making it a versatile choice for modern BMS applications. https://ecostruxure-building-help.se.com/bms/topics/show.castle?id=10930&locale=en-US&productversion=7.0&a=1 Why BTL Certification Matters Using BTL-certified products offers several benefits: Reduced Integration Costs: Certified devices are more likely to work together without custom programming. Lower Risk: Independent testing ensures reliability and minimizes project delays. Future-Proofing: Certified products provide a solid foundation for system upgrades and expansions. Conclusion BTL certification is a key indicator of quality and interoperability in BACnet-based building automation systems. Whether you're specifying products for a new project or upgrading an existing system, checking for BTL certification—especially for trusted brands like Schneider Electric—ensures smoother integration, better performance, and long-term reliability.

Issue How is a subnet defined, and what role does it play in IP networking? Product Line EcoStruxure Access Expert, EcoStruxure Building Operation, EcoStruxure Security Expert, TAC I/NET Environment This explanation is based on principles outlined in TCP/IP Network Administration by Craig Hunt, published by O’Reilly & Associates, Inc Cause Subnetting is a method used to divide a larger IP network into smaller, more manageable segments called subnets. This segmentation helps optimize IP address usage, improve routing efficiency, and enhance network security and organization. Resolution What Is a Subnet? A subnet (short for subnetwork) is a logical subdivision of an IP network. It is defined by applying a subnet mask to an IP address, which determines how the address is split into: Network portion – identifies the specific network. Host portion – identifies individual devices (hosts) within that network. How Subnet Masks Work A subnet mask is a 32-bit binary pattern that accompanies an IP address. It uses binary values to indicate which part of the IP address refers to the network and which part refers to the host: A bit set to 1 in the subnet mask means the corresponding bit in the IP address is part of the network. A bit set to 0 means the corresponding bit is part of the host. Example IP Address: 192.168.1.10 Subnet Mask: 255.255.255.0 (binary: 11111111.11111111.11111111.00000000 ) CIDR Notation: /24 This means: Network Address: 192.168.1.0 Broadcast Address: 192.168.1.255 Usable Host Range: 192.168.1.1 to 192.168.1.254 CIDR Notation Modern networks often use CIDR (Classless Inter-Domain Routing) notation to define subnets. CIDR expresses the subnet mask as a suffix (e.g., /24 ), indicating the number of bits used for the network portion. Common CIDR Blocks CIDR  Subnet Mask Hosts per Subnet /30 255.255.255.252 2 usable hosts /24 255.255.255.0 254 usable hosts /16 255.255.0.0 65,534 usable hosts Additional Notes Subnets are local constructs: They are meaningful within the internal network and typically not visible to external networks unless explicitly routed. Subnetting supports hierarchical addressing, which simplifies routing tables and improves scalability. Proper subnetting is essential for network performance, security segmentation, and efficient IP address management.

Issue Unable to drag and drop a discovered RP-C with the Zigbee adapter into the Zigbee Device Import File. This action results in the following error: There are no device types that match this device. You must import a compatible Application defined type   Product Line   EcoStruxure Building Operation Environment Building Operation Room Controller (RP-C) Zigbee Cause The application-defined type is not fully universal, which prevents direct association between the discovered device and the imported proxy. Resolution To successfully associate the discovered RP-C device with the imported Zigbee proxy: Hold the Shift key on your keyboard. While holding Shift , drag and drop the RP-C device into the Zigbee Device Import File. This action bypasses the type validation and allows the association to complete successfully.

Issue How to be redundant with your intelligent Building Management System (iBMS) Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell Sigma, Security Expert, TAC INET Environment Existing intelligent Building Management System Open Mind High Availability Solutions (Deprecated by manufacturer) everRun MX ztC Edge Cause In engineering, redundancy is the duplication of critical components of a system with the intention of increasing the system's reliability. To be redundant with an intelligent Building Management System (iBMS) would take on two possibilities. Have an alarm on critical points alerting personnel who move into action quickly replacing control boards or devices in the event of failure. Have secondary backup controllers which upon failure, which are used to control devices resuming functionality. This is accomplished through programming the BAS with event sequences triggered from alarms or flags noting the failure. Redundancy capabilities and feasibility are site specific. Ascertaining failure in boards, points, or devices is crucial to creating secondary measures to keep seamless processes going and resume with functions.   Error detection and correction with maintenance is often the best practice for preventing failure. Worn components are the leading cause of failure, followed by a lack of planning and consideration in the protection of electrical components through power surges or failures.   For the database, backups including automated backups for MSDE, SQL Express, and Full SQL are available. For further information on database backups and options, take a look at Microsoft SQL Management Studio. For Host Computer backups, look at adding a secondary computer which replicates the database and can capture transactions and messages should a failure with the primary host computer take place. Also work with the local IT department to keep machines up to date, safe, and clean of 3rd party applications which may interfere with integrity. Schneider Electric’s building management systems are designed such that building control continues even when controller to server communication is disrupted. The BMS server is home to a database of alarm and historical data, as well as system parameters and programs. When a server or its network connection fails, the collection of data from building controllers halts until the problem is resolved. For data critical applications, this solution provides an environment capable of preventing the data loss that results from these types of failures.  Although we do support its use with EcoStruxure Building Operation, Security Expert, Continuum, I/NET, Vista, Sigma, and I/A Series as a disaster recovery solution, we do not provide direct support for EverRun. Resolution For Open Mind High Availability Solutions guide please look at the following link; Open Mind High Availability Solution guide For everRun MX solution guide please look at the following link; everRun MX guide For ztC Edge solution guide please look at the following link; ztC Edge guide   

Issue Where can we find the LON xif files for SE72xx, SE73xx, SE76xx controllers? Product Line EcoStruxure Building Expert,EcoStruxure Building Operation,Field Devices Environment SE7200 / SE7300 / SE76000 Room Controllers Cause xif files are needed for LON applications. Resolution All LON related files for these controllers are available for download on The Exchange Download Center:   XIF files and plug-ins Resource files (DRF kit)

Issue What specification should BACnet MS/TP cable meet? Product Line Andover Continuum, EcoStruxure Building Operation Environment MS/TP BACnet devices Cause Often an incorrect cable type is used when wiring MS/TP devices causing unreliable communications. Resolution The BACnet Controller Technical Reference defines the following cable specification for a MS/TP cable: RS-485 Cable Specifications: Cables used to form the RS-485 network should conform to the following specifications: Wire Size: 22-24 AWG Cable Type: Twisted-pair, copper wire, tinned Shield: Braid Nominal Impedance: 100-120 Ohms Velocity of propagation: 78% Capacitance: <12.5 pF/ft (~ 41pF/M) between conductors and < 22 pF/ft (~72pF/M) between the conductor connected to ground and the next conductor. An example of a cable that meets this specification is Belden 3105A. Also check out the SmartStruxure-RS485-Network Installation Quick-Help video on the Exchange.

Issue Current information will be stored and updated in release notes and online documentation. Compatibility Matrix of Operating Systems, Video, Product Announcements, SQL Compatibility Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating Systems and iBMS (intelligent Building Management System) Software Cause Compatibility, Firmware, Product Announcements Resolution Please see release documentation for current and recent products. For the Firmware compatibility matrix for: I/NET, it is available HERE or the EcoBuilding Download Center Continuum, click HERE Xenta Software Downloads HERE Vista, click HERE EcoStruxure Building Operation, click HERE Product Announcements can be a great tool for discovering which products have been tested and are compatible with the different versions. These documents are available on the Extranet, but have been compiled here for ease of access: I/NET 2.40   Product Announcement 2.41   Product Announcement 2.41a Product Announcement 2.42   Product Announcement and Compatibility Matrix (page 5) 2.43   Product Announcement PA-00239 2.44a Software Available from Exchange Download Center 2.45   Software Available from Exchange Download Center 2.46 Software Available from Exchange Download Center 2.47 Software Available from Exchange Download Center 2.47a Software Available from Exchange Download Center 2.47b Software Available from Exchange Download Center 2.48 Software Available from Exchange Download Center Operating Systems and SQL Supported Video Compatibility Support Policy PA-00279 Software Support for TAC I/NET Continuum v1.92 Product Announcement v1.93 Product Announcement v1.94 Product Announcement PA-00210 1.94 SP1 Product Announcement PA-00273 1.9 - 2.1 Software, Firmware, & Video Compatibility Matrix Concerning IE10 and IE11 browser support  2.0 Feature Blast 2.0 + 2.01/ 2.02 Update Compatibility Matrix 2.0  Product Announcement PA-00353 2.0 CyberStation Installation Guide 2.0 WebClient Installation Guide 2.0 Software License and Ordering Activation Process 2.0 Software and Controller Upgrade Process Andover Continuum PA-00333 Support Policy PA-00272 for Andover Continuum Vista v5.1.5 Product Announcement v5.1.6 Technical Product Advisory v5.1.7 release note document, TAC Vista Compatibility Matrix, SNVT Matrix documents, and TPA-VSTA-11-0020.00 v5.1.7 Product Announcement x5.1.8 Release Note TAC Vista 5.1.8 and TAC Xenta 500/700/900 5.1.8 v5.1.9 Vista Compatibility Matrix SecurityIAS Product Announcement PA-00291 Product Announcement TAC Vista transition to SmartStruxure solution overview  Support Policy PA-00274 for TAC Vista Satchwell Sigma v4.05 SEB Release Notes v4.06 Release Notes v4.06 Release Note Supplement v4.07 Release Notes Satchwell Sigma Standard Edition Installation and User’s Guide Support Policy PA-00297 for Satchwell Sigma v4.08 Release Notes PA-00397 Sigma Version 4.08 Sigma server on a virtual machine Satchwell Micronet data sheet - MicroNet View 2.1 OS Compatibility - Micronet View PA-00228 Product Announcement Support Policy PA-00298 for Satchwell MicroNet PA-00228 Satchwell MicroNet End of Commercialization Announcement I/A Series PA-00163 I/A Series R2 & G3 Product Announcement PA-00114 Legacy Products Windows 7 Compatibility I/A Series R2 with Windows Compatibility Chart PA-00243 Software Product Update - Q2 2013 PA-00251 Hardware Product Update - Q2 2013 PA-00278 Software Product Update - Q3 2013 I/A Series (Niagara) R2 Windows Compatibility Matrix with additional detail I/A Series (Niagara) AX/G3/N4 Windows Compatibility Matrix with additional detail Support Policy PA-00280 R1 for TAC I/A Series StruxureWare Building Operation Please visit Maximum number using StruxureWare Building Operation (Scalability and Capacity) SmartStruxure Lite Please visit SmartStruxure Lite solutions

Issue Questions regarding specifications of Central I/O Inputs and Outputs Product Line EcoStruxure Building Operation Environment SmartStruxure I/O Modules: AO-8, AO-8-H AO-V-8, AO-V-8-H DI-16 DO-FA-12, DO-FA-12-H DO-FC-8, DO-FC-8-H RTD-DI-16 UI-8-AO-4, UI-8-AO-4-H, UI-8/AO-4-2, UI-8/AO-4-H-2 UI-8-AO-V-4, UI-8-AO-V-4-H, I/O UI-8/AO-V-4-2, UI-8/AO-V-4-H-2 UI-8-DO-FC-4, UI-8-DO-FC-4-H, UI-8/DO-FC-4-2, UI-8/DO-FC-4-H-2 UI-16 Cause Different I/O modules have varying electrical specifications Resolution Universal Input Specifications Universal inputs can be configured as voltage, current, thermistor, resistance, digital or supervised inputs.   Voltage Input Specifications: Range: 0 to 10 VDC Resolution: 12-bit (UI-8 v2: 16-bit) Accuracy: ±(0.7mV + 0.2% of reading) Current Input Specifications: Range: 0 to 20 mA Resolution: 12-bit (UI-8 v2: 16-bit) Accuracy: ±(0.03 mA + 0.4% of reading) Resistance Input Specifications: 10 Ohm to 10 kOhm 10 kOhm to 60 kOhm Thermistor Input Specifications: Range: -50 to 150° C (-58 to 302° F) Supported Types: 10k Type I (Continuum) 10k Type II (I/NET) 10k Type III (Satchwell) 10k Type IV (FD) 1.8k (Xenta) 10k Linearized (Satchwell DRT) 10k Type V (FD w/ 11k shunt) 1k (Balco) 20k (Honeywell) 2.2k (Johnson Controls) Digital Output Specifications Form C Relay: Terminals: Common (C), Normally Open (NO), Normally Closed (NC) Minimum Pulse Width: 100 ms Isolation: 1500 VAC (coil to contact) Cycle Life: ≥100,000 cycles Contact Rating: 250 VAC, 30 VDC, 3 A Form A Relay: Terminals: Common (C), Normally Open (NO) Minimum Pulse Width: 100 ms Isolation: 1500 VAC Cycle Life: ≥100,000 cycles Contact Rating: 250 VAC, 30 VDC, 2 A LED Indicators: Polarity: Reflects actual output state (ON = active, OFF = inactive) Color: Green Analog Output Specifications Analog outputs can be configured as voltage or current. Voltage Output: Range: 0 to 10 VDC Resolution: 50 mV Accuracy: ±100 mV Terminals: Voltage (V), Return Minimum Load: Source 2 mA, Sink -1 mA Current Output: Range: 0 to 20 mA Resolution: 0.1 mA Accuracy: ±0.2 mA Terminals: Current (I), Return Max Load: ≤650 Ohms Supervised Input Specifications Supervised inputs detect sabotage via resistor monitoring. Detected Conditions: Open circuit, short circuit, contact open/closed Circuit: 5V, 1 or 2 resistors Configurations: Series only, parallel only, series + switch Resistor Range: 1k to 10k Ohms (must be equal values) Note: Resistor value must be defined in the system. RTD Input Specifications RTD-DI-16 specifications are extensive. Refer to the official datasheet: RTD-DI-16 Specification Sheet  

Issue The Exchange Download Center contains all of the assets you once accessed through the Buildings Extranet are now available on a brand new platform. It's easy to search and fast to download. Stay tuned for more great features as we roll this into the all-new extranet solution for Buildings. We ask that you register for a new account on The Exchange.   Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Other, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Exchange Download Center Cause You can utilize the new Buildings web experience from The Exchange. Resolution Navigate to https://www.se.com/myschneider/content/ww/en/gc/general/ecoxpert-landing-page.jsp * Use a modern browser for the best experience: Google Chrome, Mozilla Firefox, Microsoft Edge, and Microsoft Internet Explorer version 8 or later. If you receive the following error in Internet Explorer despite using version 8 or later, the browser displays the page in Compatibility View. Click here for more information on Compatibility View and how to disable it. The Download Center will not function properly in Compatibility View.   On the header bar, you will see the option in the top right corner for “Login / Register.” Click it.   If you are already registered, enter your email address and password. If this is your first time registering, click the link for “New to the Download Center? Register here!”   Answer whether or not you are a Schneider Electric employee using the radio buttons. If you are a Schneider Electric employee, enter your SESA ID and your desired password for The Exchange. Click to accept Schneider Electric’s Terms and Conditions and hit “Create Account.” * The first time you register, you must be connected to the Schneider Electric network or connected via VPN. This is only required at registration. All future logins can be done externally. If you are not a Schneider Electric employee, enter your first name, last name, company name, location, business email address, and desired password for The Exchange. * It is important to use your business email address if you are a licensed partner. Your email address is used to automatically validate your Partner status and assign the correct permissions to your user profile.   An email is sent to your designated inbox with a link to click through and validate your email address. Once this is done, your login is created, and you are ready to start using the Download Center. * If an error is displayed when trying to validate your authentication code, please try to log in. This happens when an email address has already been verified and oftentimes does not indicate an error with the registration.   Once logged in, you can search and download assets available to your user profile. If you attempt to download a file that you do not have access to, you will be given a chance to report if this is in error. Your username, email, and the asset you are trying to access are recorded. Please enter a message if any further description is required and hit “Submit.” A member of our team will get back to you promptly with a resolution. Web Site Support For any issue regarding The Exchange Download Center, please contact us at exchangesupport@schneider-electric.com.

Issue What ground connections are required when wiring a voltage input? Product Line EcoStruxure Building Operation Environment AS/ AS-P Power Supply AS-B Universal Input Modules 0-10V, 0-5V sensors Cause The required connections are different for isolated and non isolated voltage inputs. Consideration of the system grounding is also required. Resolution If your input sensor is isolated it can be directly connected to the UI and RET terminals of the Universal Input module. An isolated sensor will have 4 terminals (2 power terminals G0 and G, 2 output terminals M and X) the power ground G0 is not directly connected to the output ground M terminal. However for non isolated sensors (usually 3 terminal devices) the signal terminal X will be wired to the UI input, but the sensors signal common G0 should be wired directly to the Signal Ground for the installation, not to the RET terminal of the IO Module. On every Input modules ensure that one RET terminal from the IO Module is wired directly to the Signal Ground. Full details of the required wiring and an example wiring drawing showing isolated and non-isolated voltage inputs can be found in "Wiring" section of the Hardware Reference Guide available on the Download Center or in WebHelp: Wiring.

Issue EcoStruxure Building Operation different types of licenses and all features Version 1.9 and older: Difference between Workstation standard and Workstation professional Product Line EcoStruxure Building Operation Environment All versions Cause Due to different features of each license, customer may get confused which license to order. Resolution See the version of the latest EcoStruxure Building Operation Part Number Summary document on the Exchange for all license part numbers.   Versions 2.0 and Newer Note: The licensing part numbers and structure has vastly changed starting in version 2.0 and newer.  See the search query below on the Exchange for more detail regarding the Scalable Pricing Policy that started in version 2.0. EcoStruxure Building Operation Scalable Pricing Information   Versions 1.9 and Older Note: There is no part number for WebStation; it is a default feature of the Automation Server and Enterprise Server (with no need for additional licensing)  

Issue Bindings to graphics and programs on SpaceLogic IP controllers are being unexpectedly added or removed. Product Line EcoStruxure Building Operation Environment SpaceLogic IP Controller Custom Types 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. Cause When a custom type is modified, a re-typing process is automatically triggered. The outcome of this process—specifically whether bindings are retained or lost—depends on the reference type used within the custom type. Resolution Care should be taken when designing custom types, as bindings within the type can be defined using one of three reference types: - No Reference Inner Reference Outer Reference Each reference type behaves differently during re-typing operations and can impact whether bindings are retained, added, or removed.     When a custom type is modified or re-applied (e.g., attached to an object instance, version-changed, or undo check-out), a re-typing process is triggered. The behavior of bindings during this process depends on how they are defined in the custom type:   No Bindings in Custom Type If the custom type does not contain any specific bindings, then during re-typing, existing bindings in the instance will be removed. Bindings Should Be Defined in the Custom Type To preserve bindings during re-typing, they should be explicitly added to the custom type using either: Inner References Outer References (with inner reference locked) Inner Reference Behavior If inner reference bindings are defined in the custom type, they will be automatically added to the instance during re-typing, even if they were not previously present. Outer Reference (Locked) Using outer references with inner reference locked ensures that bindings are preserved and not unintentionally modified during re-typing For more detailed information on the re-typing process and reference behavior, please refer to the Re-Type section in WebHelp.

Issue Users and customers often confuse the terms hotfix and upgrade when discussing updates to the EBO platform. This article clarifies the distinction to help with proper planning and communication. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Central Server Building operation MP, RP and other upgradable field controllers. Cause The confusion typically arises due to: Similar version naming conventions (e.g., 4.0.1 vs. 4.0.1 CP1). Lack of awareness about the scope and impact of each type of update. Misunderstanding of the validation requirements for regulated environments. Assumption that all updates require the same level of planning and downtime. Resolution EBO Hotfix or Consolidation Point (CP) Purpose: Targeted fix for specific bugs or issues. Scope: Minimal — typically affects only a few files or modules. Impact: Low risk; does not change the database schema. Versioning: Minor version change (e.g., 4.0.1 → 4.0.1 CP3). Use Case: Applied when an issue needs resolution without waiting for a full release. Installation: Quick and simple; may not require full system downtime. EBO Upgrade Purpose: Introduces new features, performance improvements, and broader fixes. Scope: Comprehensive — affects multiple components and may include database schema changes. Impact: Higher risk and complexity; requires planning and validation. Versioning: Major or minor version change (e.g., 4.0.1 → 5.0.1). Use Case: Planned system enhancement, often requiring customer approval or validation. Installation: More involved; typically requires backups, downtime, and post-upgrade testing.

Issue A Plain English Script program that works correctly on an AS-P controller does not function as expected when used on a b3 or i2 controller. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server b3, i2 controller Script Program Cause Bindings are missing. Resolution To resolve this issue, ensure that all bindings are complete. The Script Editor provides a check that explicitly identifies this problem. For example, the Check may display the message Invalid Compilation:   Behavior Differences Enterprise Server (ES) and Automation Server (AS) Programs These programs can be saved and will function even if some bindings are incomplete. However, any logic relying on missing bindings may not behave as expected. b3 and i2 Script Programs These programs will save successfully but will not function correctly unless all bindings are complete. This is because b3 and i2 devices execute scripts at the firmware level, requiring all inputs and outputs to be fully defined and bound for proper operation.

Issue Editing a script program can result in bindings being lost or unintentionally removed Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Script Program Cause If a script program line labeled as "Numeric Input", "Numeric Output", or "Numeric Public" is modified and the change includes a syntax error or reserved word when saved, the binding for that line may be lost. For example, in the image below, all bindings remain intact   After editing the "Numeric Input" line and using a reserved word (e.g., allowed), the associated bindings are removed. Resolution Exercise caution when modifying script programs on an active site to avoid unintended disruptions. Always be especially careful when working with scripts running on a live plant.   In such cases, it is recommended to add a new "Numeric Input", "Numeric Output", or "Numeric Public" line rather than modifying an existing one. This approach helps preserve existing bindings and reduces the risk of introducing syntax errors or reserved words that could break functionality.   For example, the bindings shown below remain intact when a new line is added instead of modifying an existing one.   NOTE: This issue has been resolved starting from version 1.7.

Issue SpaceLogic MP-C and RP-C controllers may fail to download firmware to Room Units when sensors are connected to the sensor bus. Disconnecting and reconnecting the Room Units does not resolve the issue. Product Line EcoStruxure Building Operation Environment SpaceLogic MP Controller series SpaceLogic RP Controller series Cause The file system of the SpaceLogic IP controller has been re-initialized, resulting in the deletion of Room Unit firmware files. This can occur during a factory reset.  The Device Report can be used to verify whether the Room Unit firmware files are present on the controller. If the files are listed in the report—as shown in the image below—it confirms that they exist on the device.     If the Room Unit firmware files are not listed in the Device Report, the controller will not initiate a download to the Room Units. Resolution To resolve the issue, perform a firmware upgrade on the SpaceLogic IP controller.  Upgrading to the same version currently running will restore the missing Room Unit files. For further details, please refer to the RP Controller Reset Modes or MP Controller Reset Modes in Web Help, as extract below: - Important: A factory reset of an MP or RP controller affects the controller's ability to support upgrading connected devices, such as SpaceLogic Sensor devices, RP controller expansion modules, and Wireless Adapter - Advanced. This is because the necessary firmware files are deleted. After a factory reset, ensure that the controller is upgraded to restore the files needed to support upgrading the connected devices. For more information, see BACnet/IP Device Firmware Management .