Issue The technical documentation for the RP-C-EXT-DALI-M-PD states a guaranteed DALI current limitation of 64 mA. It is unclear whether this limitation applies per DALI port or to the controller as a whole. Product Line EcoStruxure Building Operation. Environment RP-C-EXT-DALI-M-PD. Cause The product documentation lists two current values: 250 mA: Theoretical DALI standard maximum bus current. 64 mA: Guaranteed current output of the RP-C-EXT-DALI-M-PD module. This discrepancy has led to confusion regarding whether the 64 mA applies to each port individually or to the total output across all ports. Resolution The RP-C-EXT-DALI-M-PD module provides a total guaranteed DALI current of 64 mA, which is shared across all four DALI ports. Key points: If only one port is used, it may utilize the entire 64 mA. If multiple ports are used, the combined current draw must remain within the 64 mA limit. This limitation is enforced by hardware and cannot be exceeded, even with external devices. Use of external DALI repeaters with integrated power supplies (e.g., Helvar 405) is not supported due to certification constraints and potential conflicts with the module’s internal power supply. The 250 mA figure refers to the DALI standard, not the module’s actual output capability. As illustrated in the attached diagram, all four DALI ports are powered by a single internal DALI driver, which is the source of the 64 mA limitation.    

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 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 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 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 After performing successive ColdStart or WarmStart operations on an AS-P, the device becomes inaccessible over IP (Workstation, WebStation, Device Administrator). It can only be accessed via USB using Device Administrator. A power cycle is required to restore IP connectivity. Product Line EcoStruxure Building Operation Environment Automation Server Premium (AS-P)  AS-P running se3linux (EBO v3.2.x onward) Cause The underlying Linux systemd service manager interprets repeated restart commands as a failure condition. When multiple WarmStart/ColdStart operations occur in quick succession, systemd assumes the EBO server process is crashing and hits the start-limit threshold, preventing further automatic restarts. Relevant systemd configuration (from /etc/systemd/system/nsp_servers.service StartLimitIntervalSec=270s StartLimitBurst=2 This means: If the service restarts more than twice within 4.5 minutes, systemd stops trying to restart it. System logs confirm this: systemd[1]: se-nsp-server.service: Start request repeated too quickly. systemd[1]: se-nsp-server.service: Failed with result 'start-limit-hit'. Resolution Avoid performing multiple WarmStart/ColdStart operations in rapid succession. If the AS-P becomes inaccessible: Connect via USB using Device Administrator. Perform a power cycle of the AS-P to restore IP connectivity. Best Practice: Allow sufficient time between restart commands to prevent systemd from triggering the start-limit condition.

Issue When using External Log Storage in EBO, the following log message may appear: "Couldn't find a matching record in the internal storage, re-reading everything." Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation External Log Storage Cause This message indicates a failed synchronization attempt between EBO’s internal log storage and the configured external log storage system. It does not imply a misconfiguration or data corruption. EBO attempts to locate the last successfully transmitted record in its internal storage. If that record is missing—typically due to log purging based on retention settings—EBO cannot resume from that point and instead re-sends all available data to the external storage to ensure continuity. Common Scenario EBO is configured with a short log retention period (e.g., 1 day). The external log storage system is unavailable for a period longer than the retention window. The last record previously sent to external storage is purged from EBO’s internal storage before synchronization resumes. EBO cannot find the matching record and re-transmits all current log data. Resolution No action is required. This behavior is expected and intentional. It ensures that the external log storage receives all available data, even if some records were purged from internal storage during downtime. Recommendations Review and adjust log retention settings in EBO to align with the availability and recovery time objectives of the external log storage system. Ensure high availability of the external storage to minimize downtime and avoid unnecessary data re-transmission.

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 After commissioning HID Signo OSDP readers in Security Expert, they do not log card events. Readers cannot be brought online in Security Expert. Product Line EcoStruxure Security Expert Environment Security Expert HID Signo Smart Card readers HID Reader Manager App Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. 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 Both sides of the commissioning process require proper installation steps: HID Signo reader configuration using the HID Reader Manager App Security Expert configuration Resolution Confirm Cards Work with Reader Before starting OSDP commissioning: Set the HID Signo reader to Wiegand mode. Connect it to the Security Expert SP-C Reader Expander port. Configure the Reader Expander and Door records for the correct format and credential. Badge a card at the reader and check events in Security Expert to confirm the reader is reading the correct format. Once confirmed, proceed to Commissioning HID Signo OSDP readers.   Commissioning HID Signo OSDP readers involves two main steps: Reader configuration in the HID Reader Manager App Security Expert configuration Step 1: Configure Reader in HID App for OSDP Install Mode Open the HID Reader Manager App. Navigate to: Inspection Report → Detailed Configuration → Communication Protocol Inspect Reader Enable Install Mode:  Scroll down and select Add to Template. Select Apply Selected Items. Enable OSDP Wait for the reader update to complete, then exit the menus. Writing changes Step 2: Configure Reader Expander in Security Expert In Security Expert, go to: Reader Expander → General tab Set Port Network Type to OSDP.  Saving changes creates two new Smart Reader records. Configure the Smart Reader:  Set the Address correctly (1 + the address value set in the HID Reader App). Under the Reader tab, set:  Reader One Format to the correct format. Reader One Door to the correct Door record. Activate OSDP Install Mode:  Right-click the Reader Expander record → Activate OSDP Install Mode. Expected Events Install Mode Activation by <operator> on Module <module> Module <module> Registered With Serial No (####) These indicate the command was processed and the expander attempted to register. Important: These events appear whether the OSDP handshake succeeds or fails. The only way to confirm success is to badge a card and check for events. OSDP Install Mode may need multiple attempts for successful handshaking. When successful, the HID Reader Manager App will automatically disable Install Mode, which can be confirmed in the App. Key Notes Always verify card functionality before starting OSDP commissioning. Multiple attempts may be required for OSDP handshake. Successful commissioning is confirmed by card events in Security Expert.  

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 After enabling Federal Information Processing Standard (FIPS) Compliance in Windows Security settings, the following issues are observed in Device Administrator:  Cannot export server list Error: "The server list could not be exported." Reason: The file could not be encrypted. "The server list could not be exported." Reason: The file could not be encrypted Cannot export root certificate with private key Error: "Export of CA root certificate failed: Could not encrypt the certificate." Export of CA root certificate failed: Could not encrypt the certificate. Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator FIPS compliance Cause Device Administrator is not FIPS compliant. Enabling FIPS mode in Windows enforces the use of FIPS-compliant cryptographic algorithms across all applications. This can lead to failures in applications that do not support these standards. Resolution To work around this issue: Temporarily disable FIPS on the affected PC or Use another PC where FIPS is not enabled to perform the export operations.

Issue You need to configure an output to latch (activate) when any input from a group is enabled (open), and unlatch (deactivate) when all inputs are disabled (closed). Product Line EcoStruxure Security Expert Environment Security Expert Cause Uncertainty around how to use Security Expert's Area and Output features to achieve this logic. Resolution To implement this logic, use the Ready Output functionality within a dedicated Area. Understanding Ready Output The Ready Output is activated when all inputs (including trouble inputs) in an Area are closed, indicating the Area is ready to be armed. It is deactivated when any input is open or the Area is armed. Configuration Steps Create a Dedicated Area In Security Expert, create a new Area specifically for this input group logic. Assign Inputs to the Area Add the desired Inputs to this Area. Set each Input’s type to "Instant" (or another appropriate type based on your use case). Configure the Ready Output Go to the Areas tab → select your Area → navigate to the Outputs sub-tab. Scroll to the bottom and locate the Ready Output section. Assign the Output you want to control based on the state of the Inputs. Optional: Invert the Output If your Output device requires the opposite logic (i.e., activate when any input is open), go to the Outputs tab → select your Output → check the Invert Output option under the Options sub-tab. Ensure the Area Is Disarmed The Ready Output only functions when the Area is disarmed. If the Area is armed, the Output will not behave as expected.

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 Users need clarification on what happens when a Software Companion subscription is expired or approaching expiration. Key questions: What messages appear in EcoStruxure Building Operation (EBO)? Are email notifications sent to customers? Can expiration notices be silenced at the EBO front end? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation subscription licenses Cause The License Enforcement and Information page in Webhelp provides limited details regarding Software Companion subscription expiration behavior. Resolution 1. What messages appear at the EBO level? 30 days before expiration: A banner appears in EBO stating: “System license renewal date is approaching. Please renew.” After expiration: The banner changes to: “System license renewal date has passed. Renewal required.” 2. Are email notifications sent? EBO does NOT send email notifications. Software Companion notifications: Up to two designated Renewers per system receive email reminders at: 6 months 3 months 1 month prior to renewal date Within Software Companion: System status color changes as renewal date approaches Red indicates the renewal date has passed 3. Can the expiration notice be silenced in EBO? Users can temporarily hide the banner using the Hide button. Permanent removal requires applying a valid license (subscription renewal).

Issue After applying a third-party (SP) certificate to the EBO workstation, users experienced significant performance degradation. Symptoms included: - Slow login times (over one minute) - Laggy graphics interaction - Trend logs and charts loading slowly or failing to load Product Line EcoStruxure Building Operation  Environment EcoStruxure Building Operation (EBO)  Service Provider (SP) Certificate applied to EBO Cause The applied SP certificate contained DNS names in its extension fields (e.g., CRL Distribution Points and Authority Information Access) that the EBO system could not resolve. These unreachable DNS names caused delays during certificate validation, leading to the observed performance issues.   Expanded Technical Explanation Certificate Extensions and Their Role Digital certificates often include extensions that provide additional metadata. Three key extensions involved in this issue are: a. CRL Distribution Points (CDP) Specifies where the system can find the Certificate Revocation List (CRL) to check if the certificate has been revoked. If the URL in this field is unreachable (e.g., internal DNS like http://xxxxxprod1.xxx.local/...), the system may hang or delay while trying to access it. b. Authority Information Access (AIA) Indicates where to retrieve the issuing CA certificate or access OCSP responders. Similar to CDP, if the AIA URL is unreachable, the system will repeatedly attempt to connect, causing login delays and UI lag. c. Subject Alternative Name (SAN) Lists additional identities (e.g., DNS names, IPs) for which the certificate is valid. If these names are internal or misconfigured, they may trigger unnecessary DNS lookups, further slowing down operations. Why This Affects Building Operation Performance When the certificate includes unreachable URLs in CDP, AIA, or SAN: EBO attempts to resolve these URLs. If DNS fails or times out, it causes delays of several seconds to minutes. These delays accumulate across multiple components, leading to system-wide sluggishness. Resolution To identify URLs embedded in a certificate: Use an online certificate decoder, such as SSL Shopper Certificate Decoder. Upload the certificate file (e.g., .pem or .crt) and review the output for fields like: CRL Distribution Points Authority Information Access (AIA) Subject Alternative Name Alternatively, ask Copilot: Upload the certificate file (e.g., .pem, .crt, or .cer) - In some instances, the certificate file may need to be opened in a Text Editor such as Notepad++ and the text copied to allow CoPilot to interrogate the certificate files. Ask: "Can you extract all URLs from this certificate?" Copilot will return a list of URLs found in the certificate's extensions. Some (edited) examples should be shown as follows:   CRL Distribution Points: http://xxxxxprod1.xxx.local/AIA/SPAuth.crt http://xxxxxprod2.xxx.local/AIA/SPAuth.crt Authority Information Access (AIA): http://xxxxxprod1.xxx.local/AIA/SPMAuth.crt http://xxxxxprod2.xxx.local/AIA/SPMAuth.crt LDAP URLs: ldap:///cn=SPAuth,cn=AIA,... ldap:///cn=SPMAuth,cn=AIA,... Best Practices to Avoid This To prevent this issue: Avoid including internal-only or unreachable DNS names in certificate extensions. Use publicly resolvable URLs or omit non-essential extensions. Validate certificates using tools like: SSL Shopper Certificate Decoder OpenSSL ( openssl x509 -in cert.pem -text -noout ) Regenerate certificates with only the necessary fields: Common Name (CN) Valid SAN entries Minimal or no CDP/AIA if not required Additional Resources Configure the CDP and AIA Extensions on CA1 | Microsoft Learn Configure & Troubleshoot CDP And AIA | Encryption Consulting Scheneider Electric WebHelp - Certificates  

Issue Guidance is needed for converting Andover Continuum to EcoStruxure Building Operation (EBO) using the Continuum Conversion Tool (CCT), including best practices and troubleshooting tips Product Line EcoStruxure Building Operation Environment Continuum Conversion Tool (CCT) Andover Continuum EcoStruxure Building Operation Cause Although documentation for the Continuum Conversion Tool exists, it is spread across multiple resources and formats (Knowledge Base articles, WebHelp, training materials). This fragmentation can lead to confusion or missed steps during migration. Resolution Refer to the following official resources for detailed guidance: EcoStruxure Building Operation - Technical Reference Guide - Version 6.0 Starts at chapter 214, Page 6312 Andover Continuum to EcoStruxure Building - Frequently Asked Questions - Technology Refresh Training Resource Library: Continuum Transition(Forum) Webhelp: Continuum Conversion Workflow Webhelp: Continuum Conversion Tool Best Practices Perform a Full Backup Back up all Continuum databases and controllers before starting the conversion process. Validate Firmware Compatibility Ensure all Continuum devices are running supported firmware versions prior to migration. Reference:  Continuum Infinet Transition - Make Ready incompatible controllers Conversion of Continuum devices from i2 to b3 Migrating Infinet controllers from Continuum to EBO Change the firmware version in a Continuum controller Continuum Software and Firmware Compatibility Matrix Use a Test Environment First Run the conversion in a non-production environment to identify potential issues before live deployment. Check Naming Conventions Standardize object names in Continuum before conversion to avoid conflicts in EBO. Review Converted Objects After conversion, verify that all points, alarms, and schedules have migrated correctly. Reference: Converting Continuum b3/i2 Tristate outputs to EBO Multistate outputs Document Changes Maintain a detailed record of conversion steps and any manual adjustments for future reference. Plan for Downtime Schedule migration during low-occupancy periods to minimize operational impact. Reference: Andover Continuum Conversion Tool Slow Troubleshooting Common Issues Issue Possible Cause Resolution Conversion Tool Runs Slowly Large database size or insufficient system resources Close other applications, ensure adequate RAM, and run conversion in smaller batches. Missing Objects After Conversion Unsupported object types or naming conflicts Review conversion logs, manually recreate unsupported objects, and standardize names before retrying. Licensing Errors Incorrect EBO license or missing feature Verify EBO license includes Continuum conversion support; update license if needed. Firmware Mismatch Continuum devices not on supported firmware Upgrade firmware to recommended versions before conversion or use Roam I/O to upgrade after conversion. Alarms Not Migrating Correctly Alarm configuration differences between Continuum and EBO Validate alarm mappings post-conversion and adjust manually where necessary.

Issue The sort order of Areas displayed on different keypads is inconsistent when scrolling through them. Product Line EcoStruxure Security Expert Environment Security Expert SX-KLCS Keypad Cause In the keypad configuration, the "Area this LCD belongs to" setting determines the primary Area associated with the keypad—typically the Area where the keypad is physically installed. This Area is intended to appear first when a User logs in. Keypad Area If this setting is left as <not set>, the keypad will default to sorting Areas by their Area ID, rather than prioritizing a specific primary Area. Resolution The order in which Areas appear on the keypad is determined by the Access Levels assigned to the User who logs in. Specifically: The keypad displays Areas in the order they are defined within the User’s Access Levels. To ensure consistent Area sort order across all keypads, the Access Levels must be assigned in the same order for each User record. Important: Once Access Levels are added to a User record, they cannot be re-ordered. To change the order: Remove all Access Levels from the User record. Reassign them in the desired order.

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 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 Need to quickly and accurately count field devices in an EcoStruxure Building Operation (EBO) system for license validation or upgrade planning. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation SEAL Script: Standard Scripts → Field Device Count Cause Manual counting of devices is inefficient and error-prone. SEAL provides an automated script to scan the system and report the total number of licensed field devices. What is SEAL? SEAL(Schneider Electric Automation Library) is an external Schneider Electric toolbox designed to automate and simplify engineering tasks for EBO. Key features include: DWG to TGML converter for graphics. Script utility for automating EBO engineering tasks such as: BACnet object conversion. Generating trend logs. Advanced bindings and search/replace. Automated duplication of devices or folders. Ability to run standard scripts (like Field Device Count) or create custom scripts. Further information on SEAL can be found in the EcoStruxure SEAL Forum Access: SEAL is available to EcoXpert partners (Registered, Certified, Master) and Schneider Electric employees. SEAL can be downloaded from the EcoXpert Extranet Resolution Steps to Use the Field Device Count Script Open SEAL Launch the SEAL application. Access the Script Click Scripts in SEAL. Use the Quick Filter to search for Field Device Count. This script is part of the Standard Scripts package. Configure and Run Connect SEAL to the top-level server (Enterprise Server or highest Automation Server). Set options: Include Subservers: Checked (to scan the entire system). Output to Results View: Optional (for quick review). CSV File Path: Optional (to export device list).   Review Results The script outputs a list of detected field devices and a total count. Use this count for license compliance or upgrade planning. Export Data (Optional) If a CSV path was specified, review the exported file for detailed device information.