Issue How to put in multiple email addresses for emailing from Email Notification Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES) Building Operation Automation Server (AS) Cause It is often required that alarm notifications to be sent to multiple stakeholders simultaneously for timely response.   Best Practice: Use an email distribution list (DL) or group on your mail server and reference that DL address in EcoStruxure Building Operation. This simplifies recipient management and reduces maintenance overhead. Resolution   Open Email Setup in WorkStation (or Project Configuration Tool) > navigate to Notification > Configure Email. In the “To” field, enter multiple addresses using this syntax: user1@domain.com;user2@domain.com;user3@domain.com Separate addresses with semicolons ( ; ) and do not include spaces. Alternatively, select user accounts or groups to manage recipients dynamically. Ensure each user account exists on the BMS server and has proper alarm handling permissions. Configure SMTP settings (server, port, SSL/TLS, credentials) under right click  Server Properties > Email.   Choose how notifications appear: Inline email text, or As an attachment (TXT, XLSX, or PDF), with dynamic filenames if needed. Example: user1@gmail.com;user2@gmail.com;user3@gmail.com If email delivery fails, Building Operation generates a system information alarm indicating SMTP issues. Recipient Limit Note: EcoStruxure Building Operation does not impose a hard limit on the number of email addresses in the “To” field. However, your SMTP server or email provider may enforce limits (e.g., Microsoft 365 allows 500 recipients per message; Gmail and ISPs have similar restrictions). To avoid delivery failures, use distribution lists or user groups for large recipient sets.

Issue After renaming a server, folder, or object, users may suddenly lose or gain access via WorkStation or WebStation. Access changes depend on the original permissions assigned to the user or group, and these permissions are not automatically updated following renaming. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES)  Building Operation Automation Server Premium (AS-P) Cause Permissions in EcoStruxure Building Operation are based on path names. When a Server, Folder, or Object is renamed, its path changes. Existing permissions remain tied to the old path—so users either lose or inherit permissions until these are updated. Resolution After renaming Servers, Folders, or Objects: Review all relevant Users and Groups in your system. Update path permissions to match the new names. Navigate in WorkStation to Control Panel → Account Management. Select the user or group, go to Software Permissions, and verify or adjust their assigned paths. Refer to WebHelp (Editing Path Permissions of User Accounts or User Account Groups - EcoStruxureWebHelp)  Validate effective permissions, ensuring they use the correct access levels: Read, Write, Create, Delete, Edit, Force, or Command. See also Relative Path Permissions. Refer to WebHelp (Assigning Relative Path Permissions to User Accounts or User Account Groups - EcoStruxure WebHelp)

Issue Communication between a DMS-3500 and a Niagara R2 UNC-520 is slow, causing point updates to occur very slowly. Users need guidance on settings that can be verified and optimized to improve performance. Product Line TAC IA Series Environment Niagara R2 UNC-5x0 DMS-35, DMS-350A, DMS-3500 Cause Several factors can contribute to slow communication: High count of polled objects Lower than optimal baud rate between UNC and DMS Non-optimal settings for the DMS Comm Service Resolution Follow best practices from the DMS Serial Driver Engineering Guide (F-27071). Key recommendations that do not require hardware changes include: Increase Baud Rate Use the maximum allowable baud rate for the DMS serial port (38.4 kbps for DMS-3500). Optimize DmsCommService Settings intermessageDelay = 1500 timeoutHostMsg = 215000 timeoutHostFragment = 110000 maxReadValues = 10 downDeviceRecoveryInterval = 1 maxMultipleMsgs = 3 autoCycleTimeOn = TRUE deltaCycleDifference = 10 deltaCycleChange = 25 globalCycleTime = 15000 Reduce Unnecessary Alarms Disable DMS point alarms that are no longer required from annunciating to the serial port. Optimize Polling Intervals Adjust minimumPollInterval for shadow objects. Example: Space temperature sensors can be set to 30,000–60,000 ms instead of the default 1,000 ms. Limit Poll-Always Points Keep below 600 points if polling at 1,000 ms.

Issue The last controller on a Microsmart trunk was removed and discarded without retrieving the End-of-Line (EOL) module. External resistors are needed to temporarily mimic the EOL module for communication stability. Product Line TAC IA Series Environment DMS (all models) Microsmart controller communication trunks Cause During site renovation, the last controller and its EOL module were removed and discarded, leaving the trunk without proper termination. Resolution Using external resistors is not recommended as a permanent solution. However, to stabilize communications until a proper EOL module (RBSC-16) is installed, replicate the following resistance values: Module Type: 8-pin Pin Connections: Pins 1–8: 3.3 kΩ resistor Pins 2–7: No connection Pins 3–6: 150 Ω resistor Pins 4–5: 3.3 kΩ resistor Resistor Specs: ¼ watt, 5% tolerance

Issue When attempting to rename an Enterprise Server (ES) or add a SmartX (Automation) server under an ES, the following error may appear: All subservers must be online at least once before adding (renaming)   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server – version 2.x and later Cause A mismatch exists between the contents of the MountPoints and Versions folders within the ES database. Although GUID(Globally Unique Identifier)-named pairs may look similar, their contents differ—and cannot just be copied. Resolution Backup: Confirm you have a clean, recent backup of the ES database. Identify unmatched files: Compare the following folders: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation x.x\Enterprise Server\db\System\MountPoints  C:\ProgramData\Schneider Electric EcoStruxure\Building Operation x.x\Enterprise Server\db\System\Versions Delete unmatched versions: In the Versions folder, delete only those GUID-named files that do not have a corresponding file in MountPoints.   Manual comparison required: You must compare GUIDs manually or via script—files can’t be auto-synced.    

Issue Understanding how unoccupied heating mode operates on a Type 2 Mode Control point in DMS Microsmart. Product Line TAC IA Series Environment DMS Microsmart Cause Perimeter radiation valves remain open or do not adjust correctly during unoccupied periods, causing the space temperature to be too warm when occupancy begins. Resolution The Heat/Cool Differential determines the occupied heating setpoint by subtracting its value from the occupied cooling setpoint. Example: Cooling Setpoint = 74°F Heat/Cool Differential = 4°F → Heating Setpoint = 70°F Night setup values: Cooling Night Setup = 80°F (must be higher than the occupied cooling setpoint) Heating Night Setback = 65°F (must be lower than the occupied heating setpoint) Both night setpoints require a Level 1 STOP command to engage.

Issue How to identify the point capacity of a DMS-3500 controller and verify the actual point count on an active system. Product Line TAC IA Series Environment DMS-3500 Cause When making additions to an existing DMS installation, it is necessary to confirm the remaining point capacity to ensure the system can accommodate additional programming. Resolution   A DMS-3500 supports 250 points maximum. To check the current point count on a live system using OPRIF 11.x: From any screen, press F8 to enter command mode. Type CANCL and press Enter to view the first point in the database. Type PNTID and press Enter to display the first point's name. The three-digit number to the left of the point name should read 001 (first point). Press F5 to display the last point in the system. The three-digit number to the left of the point name indicates the total point count (between 001 and 250).  

Issue What output does a DMS Loop Point provide when the setpoint and process variable are equal, and only a proportional constant is used? Product Line TAC IA Series Environment DMS control applications using proportional-only loop points Cause When using proportional-only control, the behavior of the loop output at equilibrium (setpoint = process variable) can be unclear, leading to confusion during configuration or troubleshooting. Resolution A proportional-only Loop Point assumes a midrange output when the setpoint and process variable are equal. Midrange means halfway between the loop output high range and low range (typically 100 and 0 respectively). For detailed configuration guidance, refer to DMS Operator Interface User's Guide (F-25467), Chapter 13.

Issue What speed and duplex settings do the DMS and GCM Ethernet Network Interface Modules (NIMs) operate at? Product Line TAC IA Series Environment DMS-ETH-001 GCM-ETH-001 Cause Uncertainty about the Ethernet configuration (speed and duplex) can lead to misconfigured switches or network devices, causing communication failures or degraded performance. Resolution Both DMS and GCM Ethernet NIMs comply with the IEEE 802.3 standard as defined in the early 1990s. Port Speed: 10 Mbps Duplex Mode: Half-duplex Ensure that connected network equipment (switches, hubs) is configured to support 10 Mbps half-duplex to maintain reliable communication.

Issue When Microsmart AP7 (Application Type 7)/Chain Calculation points are learned into Niagara G3 using the DMS driver, they appear as Numeric Points but are not writable. This prevents operators from sending setpoint values to LOOP points in Microsmart controllers. Product Line TAC IA Series Environment Niagara G3 DMS Microsmart Cause AP7 points are learned into the Niagara G3 station as Numeric Points without write capability. These points are not linked to the DMS database, limiting control functionality. Resolution To enable write capability for AP7 points: Locate the AP7 point in Niagara G3. Learn the PVALU element of the AP7 point into the database. Open the Property Sheet of the object and add a Command String. After adding the Command String, an Action option will appear on the Wire Sheet, which can also be transferred to a graphic for operator use.

Issue Customer needs to replace a failed DMS-35 controller and wants to know if a DMS-350A can be used as a substitute. Product Line TAC IA Series Environment DMS-35 Controller DMS-350A Controller Cause The original DMS-35 controller has failed. Customer has a spare DMS-350A from a previous retrofit project. Resolution Yes, a DMS-350A can replace a DMS-35 controller, provided the following conditions are met: Include at least one DCM MicroSmart controllers connect to the DCM, and the DCM connects to the DMS-350A. Firmware Compatibility Ensure the firmware level in the DMS-350A and DCM matches or exceeds the MicroSmart controllers. Example: If MicroSmart controllers are revision 10.x, then DMS-350A and DCM must be revision 10.x or 11.x. Database Considerations The DMS-35 database cannot be installed directly into a DMS-350A due to DCM requirements. Points in MicroSmart controllers must be re-linked, creating a new database.

Issue SAFR Face Scan successfully detects faces but does not authenticate users or grant access.        Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 SAFR Scan Reader using OSDP Cause The default SAFR Scanner Access Feedback Timeout is set to 300 ms, which is too short for proper authentication. In some cases, physical impact during transit may also require light sensor recalibration. Resolution   Access the SAFR Scanner configuration web page and log in. Navigate to System > OSDP settings. Change the Access Feedback Timeout from 300 ms to 1000 ms and click Apply. Test authentication. If issues persist: Perform light sensor calibration (refer to SAFR documentation). SAFR portal: https://safr.com/safr-portal/ (login required)

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 Command Request / Command Response window is not available when using the Niagara G3 DMS driver. Product Line TAC IA Series Environment Niagara G3 Microsmart driver Cause This feature was present in the Niagara R2 driver but was not carried over to the Niagara G3 driver. Resolution The only available option is to tunnel to the Microsmart controllers using OPRIF for command requests and responses.

Issue UltiVist cannot communicate with the DMS panel over a serial connection due to incorrect port settings. Product Line TAC IA Series Environment UltiVist Software DMS Panel Cause The DMS panel’s serial COM port settings were reset to factory defaults, which do not match UltiVist’s required configuration. Resolution Configure the DMS panel’s serial COM port with the following settings to enable communication with UltiVist: Parameter Value Port PORT1 (typically) or PORT2 Baud Rate 9600 Stop Bits 1 Data Bits 7 Parity Even Mode Multi-drop Modem None Note: PORT1 is commonly used for UltiVist connections. Ensure these settings are applied after any factory reset.

Issue In a Niagara R2 and DMS integration, some points in the station are not updating after changes to the DMS database. Product Line TAC IA Series Environment Niagara R2 (all versions) DMS (all versions) Cause Controllers and associated DMS points were deleted as part of housekeeping. When points are deleted, added, or re-ordered in the DMS database, the Niagara R2 station does not automatically refresh its point list. Resolution Whenever DMS points are modified or the DMS database is downloaded via OPRIF, perform a re-learn of the DMS panel from the Niagara R2 station: In Niagara Workbench, right-click the DMS container. Select Go > PointListManager. Click GetPointListFromDevice to upload the current DMS database into the station. Important Notes: These steps will not affect existing objects under the specific DMS container. For detailed instructions, refer to the I/A Series Niagara DMS Serial Driver Engineering Guide (F-27071), section “Re-learning The DMS Panel.”

Issue Clarification is needed on whether the Ethernet NIM (Network Interface Module) settings are included when performing a DMS database backup. Product Line TAC IA Series Environment DMS-3500 with Ethernet NIM OPRIF 11.4 & 11.6 Cause Backup requirements can be confusing because the DMS database, controller databases, and NIM configuration are stored separately. Users may assume a single backup command covers all components, which is not the case. Resolution A complete DMS backup consists of three steps, all performed using OPRIF: Backup the DMS database Backup each individual MicroSmart controller database Backup Ethernet NIM configuration data separately Important Note: Echelon NIMs do NOT require backup. Ensure all three steps are completed during maintenance to guarantee full system recovery capability.

Issue On a DMS jobsite, the Operator Interface (OPRIF) does not display MicroSmart controllers on the screen. Although multiple controllers are confirmed to be communicating with the DMS, they do not appear in the controller list in OPRIF. Product Line TAC IA Series Environment OPRIF DMS MicroSmart Cause OPRIF displays controllers in groups of 32 per screen and reserves address slots even if they do not exist. If controller addresses start at 33 or higher, the first screen appears blank because it only shows addresses 1–32. Resolution Use the Page Down and Page Up buttons in OPRIF to navigate between controller lists: Page 1: Addresses 1–32 Page 2: Addresses 33–65

Issue A jobsite is visited periodically, and it appears that certain database elements have changed since the previous visit. These elements are not expected to change (unlike setpoints or schedules). The question is whether there is a built-in feature in a DMS panel or the OPRIF programming tool that provides database analysis. Product Line TAC IA Series Environment DMS OPRIF Cause The DMS product does not include built-in database analysis tools. Historically, supervisory computers provided this functionality using tools like UltiVist or SIGNAL, which could analyze databases and save information for future review. Resolution No built-in database analysis feature exists in DMS panels or OPRIF. When only OPRIF is available: Take screenshots of point configuration screens to store values for later comparison. DMS databases are not formatted for offline viewing, so direct comparison between copies is not supported. To compare two database states: Use a second DMS panel as a reference. For advanced analysis, consider using a supervisory computer with compatible tools (e.g., UltiVist, SIGNAL) if available.

Issue What is the best way to completely clear an existing database from DMS3500 and DMS350A before reinstalling? Product Line TAC IA Series Environment DMS3500 DMS350A Cause When reinstalling a database, remnants of the previous database may cause conflicts or unexpected behavior. A full hardware-level clear is required to ensure the old database is completely removed. Resolution For DMS3500: Connect via OPRIF and enter Command Mode. Type the command: DBCLR After completion, log back into the DMS3500 and begin the new database installation. For DMS350A: Sign on using the keypad. Enter the command: DBCLR For each connected DCM: Set all 8 toggle switches to ON. Cycle power to the DCM. Wait 10 seconds, then re-address the DCM and cycle power again. Once complete, use OPRIF to start the database installation. Note: The DBCLR command combined with setting toggle switches to ON is considered a hardware-level database clear, ensuring no residual data remains.