Issue When an Engineering License ("New system") is created and activated on an Enterprise Server (ES) that has been upgraded from EBO 6 or earlier to EBO 7.0.3, the feature licenses do not propagate to Automation Servers (AS) that are still running EBO 6.0 or earlier Product Line EcoStruxture Building Operation   Environment Software Companion Device Administrator Centralized Licensing   Cause The current Engineering License offering with the "New system" does not support scenarios where the top-level server has been upgraded from EBO 6 or earlier to EBO 7.0.3. In such cases, the license propagation mechanism may not function correctly. Resolution To ensure proper license propagation: Recommended Setup: Create and activate the Engineering License ("New system") on a top-level server with a clean EBO 7.0.3 database. In this configuration, feature licenses will be inherited correctly by AS units running EBO 7.0 and earlier. Alternative Workaround: If the ES has been upgraded from EBO 6 or earlier to EBO 7.0.3 and AS units cannot be upgraded immediately ( Multi-system) : Consider manually assigning feature licenses ( Demo lic)  to the AS units. Or, migrate AS units to EBO 7.0 or later to restore automatic license propagation.

Issue When launching VisiSat 2.1 Build 185 on certain Windows XP Pro / Visio 2003 systems, the following error may appear: Internal error 0x86DB08A9 VisiSat 2.1 Build 185 cannot find the “CustomiseUI” add-on to Visio. Some or all files required by VisiSat are missing. You may need to re-install Visio and/or VisiSat to clear the problem. Product Line Satchwell MicroNet Environment VisiSat 2.1 Build 185 Cause Visio 2003 may fail to recognize or properly register the VisiSat 2.1 Build 185 installation, particularly the CustomiseUI component. Resolution Open Visio 2003 (not VisiSat). From the menu bar, go to: Tools → Options Select the Advanced tab. Click on File Paths. Delete all entries listed. Click OK to confirm and close the dialog. Close Visio 2003. Launch VisiSat again. It should now start without error. If you close VisiSat and reopen Visio 2003, the file paths should now be correctly displayed.   Additional Option If you're running on Windows 7, consider upgrading Visio to Visio 2007 or Visio 2010 for improved compatibility.

Issue Customers using Device Administrator for offline license activation in EBO 7.0.3 face challenges due to changes in how entitlements are delivered via Software Companion. Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator (v7) Software Companion Portal FlexNet Licensing Portal Offline systems (no internet access) Cause The current Software Companion tool does not generate an HTML entitlement certificate compatible with Device Administrator. Instead, it provides a PDF summary, which the Device Administrator cannot read or import. Resolution The simplest way is to enable Internet access for Device Administrator and add the entitlement ID. To activate licenses offline in Device Administrator: Do not use the PDF summary generated by Software Companion — it is not compatible with Device Administrator. There are several options available, each differing in complexity and time requirements.    Contact support with your Entitlement ID, and they will send you an HTML version of your license for import into Device Administrator. (Internal use only) Access the FlexNet Licensing Portal: Home Page - FlexNet Operations End-User Portal: Log in using the Entitlement ID. List all Entitlements. Select one Activation ID Use the View Certificate option. Download and save the certificate locally in HTML format. When using Save As - ensure you select the "Webpage, complete (*htm;*html) option  Repeat for each Activation ID listed in the Entitlement Import each HTML certificate into Device Administrator to load the entitlement offline. Create a server list away from the site, using Device Administrator, that has Internet access. Caution: this will wipe the current server list, remove all certificates (if used), and remove all servers added to Device Administrator. If the server list has already been created on site, save and export this list. Off-site or on a PC with Internet access, import (from step 1) or create a new server list in Device Administrator. Add the necessary entitlement IDs. Save and export the server list. Back on the on-site PC, import the exported server list to Device Administrator. If using a new server list (that is, no servers added from Step 1), add the required certificates and servers. Save this new list. It is advisable to export it as a backup in case of any issues. Proceed with the offline activation. EcoStruxure BMS Server Licensing on Servers not Connected to Internet Workflow. Once activated, remember to save and export the list for safekeeping. Alternatively, the Activation IDs from the Entitlement ID can be manually entered into Device Administrator.   Comment: Investigation into why Software Companion does not generate HTML certificates is ongoing.  Device Administrator still requires either the HTML certificate or manual entry of activation IDs.

Issue You need to integrate both: VingCard lock MTH-G-5045 / WDC-G-5045 window and presence contacts …into a Zigbee network on the same RP-C (Room Controller) device. Product Line EcoStruxure Building Operation. Environment Building Operation Room Controller (RPC) 24 V. Zigbee Cause When performing device discovery: If using Zigbee VingCard Network, the MTH-G-5045 / WDC-G-5045 devices are not found. If using Zigbee Standard Security Network, the MTH-G-5045 / WDC-G-5045 devices are found. This occurs because the two Zigbee networks are fundamentally different in protocol and device compatibility. Resolution It is not possible to use both Zigbee VingCard Network and Zigbee Standard Security Network simultaneously on the same RP-C device. You must choose one Zigbee network type per RP-C: If you need VingCard lock integration, use Zigbee VingCard Network. If you need MTH-G-5045 / WDC-G-5045 integration, use Zigbee Standard Security Network. ⚠️ Important: These networks are mutually exclusive on a single RP-C. Consider deploying separate RP-C devices if both network types are required in the same installation.

Issue When configuring BACnet alarms in EcoStruxure Building Operation (EBO), users may encounter a potentially misleading message in the Monitored Variable description: Monitored variable: Choose the method for referencing the property that you want to monitor. Select System reference to define a path-based reference to an object or property that is currently located on the EcoStruxure BMS server. While technically correct, this statement may cause confusion. It suggests that any object or property on the EBO server can be used as a monitored variable for BACnet alarms. However, only specific BACnet objects and properties are supported for each alarm type. Product Line EcoStruxure Building Operation Environment EcoStruxture Building Workstation Bacnet Alarms Cause The ambiguity arises from the assumption that all BACnet objects and properties are valid for alarm monitoring. In reality, only a subset is supported depending on the alarm type. Misconfiguration can lead to unexpected behavior or non-functional alarms. Resolution To ensure proper configuration, refer to the table below for supported combinations of BACnet objects and properties for each alarm type: Alarm Type Monitored Variable Object Monitored Variable Property Change of State BACnet Digital Input Value BACnet Digital Output Value BACnet Digital Value Value BACnet Multistate Input Value BACnet Multistate Output Value BACnet Multistate Value Value Change of Value BACnet Analog Input Value BACnet Analog Output Value BACnet Analog Value Value Floating Limit BACnet Analog Input Value BACnet Analog Output Value BACnet Analog Value Value Floating Limit Setpoint Reference BACnet Analog Input Value BACnet Analog Output Value BACnet Analog Value Value BACnet Loop Setpoint Out of Range BACnet Analog Input Value BACnet Analog Output Value BACnet Analog Value Value BACnet Digital Input Value BACnet Digital Output Value BACnet Digital Value Value BACnet Multistate Input Value BACnet Multistate Output Value BACnet Multistate Value Value Buffer Ready BACnet Trend Log (Any) — Additional Reference For more details, see: 🔗 BACnet Alarm Types and Monitored Variables Table

Issue What is the maximum density of people that the Insight sensor (SXWREISBLE10001) can detect? Product Line Field Devices, EcoStruxure Building Operation Environment Insight sensor. Cause There is no official specification available that defines the exact density of people the Insight sensor can detect. This limitation makes it difficult to provide a precise number for maximum detection density. Resolution The maximum raw count for the people counter is 32 individuals within the detection area. Accuracy of detection is up to 90%, but it decreases as the number of people increases within the detection zone. The detection area is influenced by the mounting height of the sensor. A higher mounting position typically results in a larger detection area but may reduce accuracy in crowded conditions. Additional Notes For optimal performance, ensure the sensor is mounted according to published guidelines. Consider environmental factors such as lighting, movement patterns, and obstructions that may affect detection accuracy. If higher accuracy or density detection is required, consider deploying multiple sensors.

Issue Reading registers from an ATV600 via Modbus TCP in EcoStruxure Building Operation (EBO) Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Modbus Cause Users may need to access and monitor data from an ATV600 drive using Modbus TCP but require guidance on configuration steps and tools. Resolution Step 1: Download Required Tools SoMove: Software for configuring ATV600 Download SoMove DTM Library for ATV600: Install the correct model Download ATV6xx DTM Library Step 2: Configure Password The default password for ATV600 is in the manual. Change the password via the device menu 8.7 or through a web browser. How do I access the embedded web page on an ATV630 drive? | Schneider Electric USA Step 3: Log In and Configure IO Mapping Use the DTM tool to log in to the device. Navigate to IO Mapping. Add the register table according to your requirements. Step 4: Configure Workstation Protocol: Modbus TCP Device ID: 255 (for logical register mapping). Create points in Workstation and enter CHANNEL information based on the IO mapping list. Example: In DTM: CHANNEL 1 corresponds to register number 3203. In Workstation: Enter 1 to access the logical register map. ✅ Tip: Always verify that register addresses in Workstation match the IO mapping in ATV600.

Issue When upgrading a TAC Vista site to EcoStruxure Building Operation (EBO), LonWorks devices may not be discovered during the device discovery process in the AS-P. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P). Cause This issue typically occurs when the original TAC Vista database was configured using a third-party network management tool such as LonMaker or NL220. These tools can assign a custom domain ID to the LonWorks network. Default Domain ID in TAC Vista: 1/11 Default Domain ID in EBO: 1/254 If the domain ID used during the initial setup differs from EBO’s default, the AS-P will not detect devices on that domain. Resolution Identify the Current Domain ID Use the existing TAC Vista database to determine the domain ID configured on the LonWorks devices. Alternatively, use NodeUtil to identify the domain ID. Refer to the article: Finding LON devices under a different domain length with NodeUtil  Configure a Spare AS-P Set the domain ID on a spare AS-P to match the existing domain ID used in the site. For guidance, see: How to locate and change the LonWorks domain ID  Discover Devices Use the spare AS-P (now configured with the matching domain ID) to perform device discovery. The previously undetected devices should now appear and be accessible. Decommission Devices In the AS-P, navigate to the Actions menu for each discovered device. Select Decommission to revoke the device’s address and stop communication. Reintegrate Devices After decommissioning, re-add the devices to the LonWorks network. They should now be discoverable by an AS-P configured with the standard EBO domain ID (1/254).

Issue Is it possible to view license information for all Automation Servers connected to an Enterprise Server (ES), including details such as the Entitlement ID, Product ID, and Fulfillment ID? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium(AS-P) Building Operation Automation Server Bundled(AS-B) Cause In certain scenarios, it may be necessary to verify the licenses activated on all Automation Servers connected to an Enterprise Server. This includes identifying the Entitlement ID, the specific Product ID, and the Fulfillment ID associated with each license. Resolution Yes, it is possible to retrieve license information for all connected Automation Servers via the Enterprise Server. Follow the steps below: Open the Enterprise Server (ES) in WorkStation. Perform a search for "Product 0" : Use the Search function in WorkStation. Ensure that the search is conducted across all folders and that subservers are included in the search scope. Review the search results: Add columns for: EntitlementID ProductID FulfillmentID This method provides a centralized way to audit and verify the licensing status of all connected Automation Servers from the Enterprise Server.  

Issue In EcoStruxure Building Operation (EBO) version 6 and later, users may encounter a persistent Modbus Network Offline alarm, even when all Modbus devices under the network are online. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium(AS-P) Building Operation Automation Server Bundled (AS-B) Cause The Modbus communication architecture was restructured between EBO versions 5 and 6. In EBO version 5, the system could generate alarms for the Modbus network itself being offline. In EBO version 6 and later, network-level offline alarms are deprecated. Alarms are now only generated at the device level, not for the network. If a site is upgraded from version 5 to 6, any existing Modbus network offline alarms will persist, but EBO will no longer monitor or clear them, as it no longer tracks network-level status. Resolution  To remove the obsolete Modbus network offline alarm in EBO version 6, you have two options: Hide the Alarm Since the alarm is no longer relevant in version 6, you can simply suppress or hide it from the alarm list. Delete and Recreate the Modbus Network This method ensures complete removal of the alarm. Important: Ensure you have a verified backup before performing these steps: Export the Modbus network configuration. Delete the network using the “Keep Bindings” option. Re-import the network configuration.

Issue Startup programs can slow down system boot time and cause application conflicts if loaded in the wrong order. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Windows XP, Vista, 7, 8, 8.1, 10, 11 Cause Applications configured to launch at startup may: Increase boot time Cause system instability or delays Load in an incorrect sequence, affecting performance Resolution Windows XP, Vista, 7 Click Start → Run Type msconfig and press Enter Go to the Startup tab Uncheck items you want to disable Click Apply → OK Restart your computer 🔹 Windows 8, 8.1, 10, 11 Press Ctrl + Shift + Esc to open Task Manager Click the Startup tab Right-click any item and choose Disable Restart your computer for changes to take effect 💡 Tip: Only disable items you recognize. Disabling essential services may affect system functionality. Additional Notes Disabling startup items is useful for troubleshooting slow boot times or software conflicts. For persistent issues, consider using tools like Autoruns from Microsoft Sysinternals for deeper analysis.

Issue According to the product documentation, it should be possible to configure temperature and humidity offsets via Modbus or BACnet for SLP room sensors using specific registers. However, these registers are unresponsive (e.g., return errors or appear offline). Product Line EcoStruxure Building Operation Environment Building Operation SmartX Living Space Sensor Cause The customer is attempting to calibrate the temperature reading, which appears incorrect on the sensor display. However, not all SLP units support the offset feature. Resolution Supported Models: Only SLPSLX2 units produced after Week 26 of 2024 support the temperature and humidity offset feature. Unsupported Models: Units manufactured before Week 26 of 2024 do not support this feature and cannot be field-upgraded. Action Required: If the installed unit does not support the offset feature, it must be replaced with a newer unit that includes the updated firmware. Identifying Production Date: The production date is printed on the box label and on the SLP itself. Use this to verify whether the unit supports the offset functionality.

Issue A red border appears around the bindings window when interacting with the binding interface. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause This behavior occurs when the cursor is pointing to a binding title (typically green in color) that is not editable. The system visually indicates this by displaying a red border around the bindings window. Resolution This is expected behavior and serves as a visual cue to the user. To avoid the red border: Ensure the cursor is not hovering over a non-editable binding title. Move the cursor to an editable field or outside the binding title area.

Issue Supported Import and Export File Formats in Graphics Editor Product Line EcoStruxure Building Operation Environment TGML Cause Clarification of Supported File Formats in TGML Resolution TGML Overview TGML (TAC Graphics Markup Language) is an XML-based declarative language designed for creating dynamic 2D graphics within EcoStruxure Building Operation. Graphics developed in the Graphics Editor are saved with the .TGML file extension. When a graphic is created, a TGML root object is automatically generated and placed at the bottom of the Objects tree in the editor’s object pane. This root object also serves as the default layer in the Graphics Editor workspace and cannot be deleted. For more info: TGML File Format 

Issue When attempting to rename a newly created Enterprise Server, the following validation error may be encountered: "Validation failed for property 'HttpPort' Path: 'Enterprise Server/HttpPort' Type: 'HttpPort' The value '0' is outside the range of allowed values" Product Line EcoStruxure Building Operation Environment Enterprise Server Cause Although the error message references an invalid HTTP port assignment, the underlying issue is typically related to the Enterprise Server's certificate configuration. This scenario often arises when a new Enterprise Server is created from a backup containing a base configuration, which includes an outdated or incompatible certificate. Resolution To resolve the issue: Remove the active certificate associated with the Enterprise Server. EBO WebHelp documentation for detailed instructions on certificate removal: Removing a Certificate Using WorkStation  Once the certificate is removed, the renaming operation should proceed without triggering the validation error.

Issue Customers may require dynamic logging of alarm events, including specific values or metadata at the time of the event. Substitution codes provide a flexible way to embed such data directly into the file output. Product Line EcoStruxure Building Operation Environment EcoStructure Building Operation  Cause When using write to file notification objects it may be desirable to have dynamic text containing actual values etc. Resolution Write-to-file notification objects in EcoStruxure Building Operation can be configured to include dynamic content using substitution codes. These codes allow insertion of real-time alarm properties into the message body written to the file, enabling more informative and context-aware logging. Summary Substitution codes are supported only in the message body, not in the file name. The syntax for substitution codes is: @([property]) where [property] corresponds to a valid alarm attribute. If an invalid or unsupported property is used, the system will replace the substitution code with an empty string. Example: Alarm triggered at @([TimeStamp]) with value @([Value]) from source @([Source]). Important Notes Ensure that the substitution code used is applicable to the specific alarm event type. For email-based alarm notifications, refer to: Displaying different properties of an alarm in an email notification.

Issue How to display custom text and properties of an alarm in the email notification. Product Line EcoStruxure Building Operation Environment Email Notification Substitution Codes Cause To enhance the clarity and relevance of alarm email notifications, EcoStruxure Building Operation supports the use of substitution codes. These codes allow dynamic insertion of alarm-specific properties—such as the value at the time of the alarm trigger—into the email subject or body. Resolution  To customize alarm email content: Navigate to the Email Notification object in the system. In the Properties pane, locate the Subject and Text fields. Enter  desired message, incorporating substitution codes where needed.   Example: Subject: Alarm Triggered - %AlarmName% Text: The alarm '%AlarmName%' was triggered at %TimeStamp%. Value at trigger: %Value%. In scenarios where detailed context is required (e.g., documenting the exact value that caused an alarm state change), substitution codes enable automated inclusion of such data in the notification message. This is particularly useful for operational audits, troubleshooting, or real-time monitoring Available Substitution Codes Below is a list of commonly used substitution codes: Code Description %AlarmName% Name of the alarm %TimeStamp% Time the alarm was triggered %Value% Value of the monitored point at trigger %Priority% Alarm priority level %Source% Source object of the alarm   For a complete list of supported codes: Alarms Substitution Codes 

Issue Customer observed repeated logon/logoff events occurring within 1 second at 30-minute intervals for all Automation Servers. These events appear in the Event Viewer but do not impact system performance. Product Line EcoStruxure Building Operation Environment Building Operation Automation Servers Building Operation Device Administrator Building Operation WorkStation Cause When left open and connected to the server, the Device Administrator continuously polls the server status. This polling requires authentication, resulting in a logon followed by an immediate logoff. The behavior repeats at a fixed interval (approximately every 30 minutes) as part of the status check mechanism. Resolution Close Device Administrator when not actively in use. This will stop the periodic login attempts. If login events persist after closing Device Administrator, further investigation is required to identify other sources of admin logins.

Issue Is it possible to return an Engineering license from Device Administrator? Product Line EcoStruxture Building Operation  Environment Device Administrator  Cause Starting from version 7.0, EcoStruxure Building Operation introduced a Centralized Licensing Model. This model allows license management to be handled centrally via the Device Administrator, streamlining operations across BMS servers. Resolution  Yes, Engineering Licenses can be returned using Device Administrator. Follow the steps below: Prerequisites Ensure the system is running EcoStruxure Building Operation version 7.0 or later. The Top Server must be added to Device Administrator. Steps to Return an Engineering License Open Device Administrator. Select the Top Server from the list. Locate the Engineering License you wish to return. Click Return. Choose either: Online Method – if the system is connected to the internet. Offline Method – if the system is not connected. Note: Only systems running version 7.0 and above support centralized licensing. Systems running versions prior to 7.0 use the legacy licensing model and are not compatible with this procedure.

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