Issue How to find and change the Domain ID of a LonWorks Network under a LonWorks Interface in an EcoStruxure Building Operation network. Product Line EcoStruxure Building Operation Environment Building Operation workstation Cause There may be scenarios where the Domain ID of a LonWorks network needs to be identified or modified—for example, during network troubleshooting, integration, or reconfiguration. Resolution To locate and change the Domain ID of a LonWorks Network: Open Building Operation Workstation. Navigate to the LonWorks Network under the LonWorks Local Interface. Right-click on the LonWorks Network and select Properties. In the Properties window: Go to the Advanced tab. Locate the Domain Table under Network Interface. The first row in the ID column displays the current Domain ID in decimal format. To change the Domain ID: Use the Addressing entry field labeled Domain ID Length. Enter the new Domain ID. Click OK to apply the changes.

Issue Certain Xenta controllers and I/O modules support 10k thermistor temperature inputs. A common question arises regarding the specific type of 10k thermistor that is compatible—specifically, whether it should be Type 2 or Type 3. Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX Xenta 420A, Xenta 450A Cause The Xenta 102-AX has always utilized 10k thermistors. More recently, some I/O modules and programmable controllers within the Xenta family (e.g., Xenta 420A and 450A) have also added support for 10k thermistor inputs. However, confusion often arises due to terminology differences. The terms “10k Type 2” and “10k Type 3” are specific to the Continuum product line and are not applicable to Xenta controllers. Resolution The 10k thermistors compatible with Xenta 42XA and 45XA I/O modules are the same as those used in the I/NET product line. These thermistors follow the Vishay Dale Curve #1 specification. For accurate configuration and calibration, refer to the Resistance vs. Temperature Conversion Tables provided in the linked PDF document below: 📄 Resistance vs Temperature Conversion – Vishay Dale.pdf

Issue Can TAC Xenta 401 and TAC Xenta 300 HW1 be upgraded to the latest system version? Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Xenta 401 TAC Xenta 301 TAC Xenta 302 Cause Upgrading to the latest system version is recommended to benefit from the most recent product fixes, performance improvements, and feature enhancements. Resolution   TAC Xenta 300 and Xenta 401 units can be upgraded to any system version. However, HW1 versions are not compatible with EcoStruxure Building Operation. All hardware versions, including HW1, are supported in the TAC Vista Classic system.  

Issue After transitioning from Sigma to EcoStruxure Building Operation (EBO), users may notice that alarm clears require acknowledgements. This occurs because the Type of Acknowledgement on Sigma Interface object alarms and hardware alarms is set to 'Extended' and cannot be changed directly to 'Single' within EBO. Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause The Sigma Alarm Manager settings are incorrectly configured during the data import process into EBO. Specifically, the Alarm Clear Controls are set to require acknowledgements, resulting in the 'Extended' acknowledgement type. Resolution To ensure that only alarms (not alarm clears) require acknowledgement in EBO, follow these steps on the Sigma server: Open Sigma Alarm Manager. Navigate to: Configure > Alarm Controls Uncheck the box labeled: 'Alarm Clears Acknowledgeable' Redo the Data Import into EBO. After re-importing, the Type of Acknowledgement should now be set to 'Single'. If it instead shows 'No', refer to the related article: Type of Acknowledgement set to 'No' on Sigma Interface object alarm for further guidance.

Issue Unwanted hardware alarms (and other alarms) are being received at the Enterprise Server from Sigma controllers. Product Line Satchwell BAS & Sigma, EcoStruxure Building Operation Environment EcoStruxure Building Operation Sigma Release 4_08 (Build 3_46_57) Cause Sigma controllers are configured to send hardware and other system alarms to the Enterprise Server, which may not be required in certain operational contexts. Resolution To disable these alarms: Access the Sigma Interface: Navigate to the Sigma interface within EcoStruxure Building Operation. Locate the Controller (OSN): Identify the controller from which you want to disable alarms. Modify Device Monitoring Settings: Select the controller. Go to the Basic tab in the Properties panel. Locate the Device Monitoring setting. Set it to Disabled to stop hardware and system alarms from being sent. Bulk Update (Optional): If multiple controllers need to be updated: Multi-select the required controllers. Open the Property Panel. Change the Device Monitoring setting for all selected controllers simultaneously.

Issue There is a need to connect a legacy MicroNet system to the EcoStruxure Building Operation (EBO) platform. The traditional MN-MI interface is now obsolete, prompting the search for alternative integration methods. Product Line EcoStruxure Building Operation Environment Automation server Enterprise Server MicroNet interface Cause The MN-MI interface, previously used to bridge MicroNet systems with EBO, is no longer supported. A replacement solution is required to maintain system connectivity and functionality. Note: In EBO 2022 (4.0) and later, Satchwell MicroNet Integration is no longer supported. Resolution MicroNet systems operate using one of two communication protocols: Native Communications Protocol (NCP) Attached Resource Computer Network (ARCnet) If using NCP: The MicroNet LAN can be connected directly to the AS-P or ES. A MicroNet interface can be added and configured within EBO. If using ARCnet: The MN-MI is required to convert RS-232 to ARCnet. The MN-MI connects to the AS-P/ES via an RS232-to-RS485 converter. 100 Series MicroNet Controllers: These may allow removal of auxiliary ARCnet cards and reconfiguration to NCP protocol, enabling direct connection to AS-P/ES. 50 Series MicroNet Controllers: These cannot be reconfigured due to integrated communication components on the main board. Reference: For detailed connection options and configurations, refer to document PA-00246.

Issue Building Management System (BMS) equipment may malfunction due to electromagnetic interference (EMI) from nearby electrical devices. Diagnosing and resolving such issues can be complex and costly, making preventive installation practices essential. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment All electrical equipment Cause Improper installation can lead to the generation or exposure to high- and low-frequency EMI, which may disrupt system performance or cause equipment failure. Resolution To ensure reliable operation and minimize EMI-related issues, follow these key EMC installation practices: Key EMC Practices Follow Manufacturer Recommendations Always adhere to the installation guidelines provided by equipment manufacturers, as they are tailored to the specific EMC requirements of each product. Proper Cable Routing Separate power and signal cables. Avoid parallel runs near high-interference sources (e.g., motors, transformers). Shielding Use shielded cables for sensitive signals. Ground shields correctly—typically at one end to prevent ground loops. Grounding and Bonding Establish a low-impedance ground path. Bond all equipment to a common ground reference. Surge Protection Install surge protection on power and communication lines. Protect against lightning and switching transients. Filtering Use EMI filters on power inputs. Apply ferrite beads or chokes on signal lines where needed. Physical Separation Maintain spacing between high-voltage and low-voltage components. Isolate noisy equipment from sensitive electronics. Enclosure Design Use metal enclosures for shielding. Ensure proper sealing and grounding of enclosure panels. Installation Environment Avoid placing equipment near strong EMI sources (e.g., radio transmitters, welding equipment). Maintain clean, dry conditions to prevent corrosion and poor connections. Compliance Testing Verify installations against relevant EMC standards (e.g., IEC, EN). Conduct site surveys if persistent issues arise. Reference Document: Practical Installation Guidelines for Electromagnetic Compatibility

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 Zoning is reverting to the original state set on the RP-C controller after deployment or runtime changes. Product Line EcoStruxure Building Operation RP-C Series Controllers Environment Building Operation Workstation  RP-C firmware version: any Zoning configuration applied within a Custom Type 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 Zoning functionality is being used within a Custom Type, which causes the zoning configuration to revert to its original state. This occurs because Custom Types are designed to enforce consistency across instances, and any runtime changes to zoning are overridden by the base definition of the Custom Type. Resolution To prevent zoning from reverting: Avoid using zoning within Custom Types. Zoning should be configured directly on individual RP-C controller instances rather than within a Custom Type. Recommended Practice: Create zoning configurations on the RP-C controller outside of any Custom Type. If a Custom Type is necessary for other aspects of the configuration, exclude zoning from the type definition and apply zoning manually to each instance.

Issue A user wants to deploy the RTD-DI-16 module with a 3-wire PT100 sensor in an environment where temperatures drop below -50°C. The concern is whether the module can accurately read such low temperatures. Product Line Field Devices. EcoStruxure Building Operation, Environment Building Operation I/O Module 16 Ch RTD Cause The RTD-DI-16 module is designed to operate within a temperature measurement range of -50°C to +150°C. This limitation is defined in the product datasheet and reflects the module’s internal resolution and calibration capabilities. Temperatures below -50°C fall outside the supported range, which means: Resolution and accuracy are guaranteed only within this specified range. Values below -50°C will not be read and may result in inaccurate or undefined behavior. Resolution Do not use RTD-DI-16 for applications requiring measurements below -50°C. Consider alternative modules or solutions that support extended temperature ranges, such as those designed for cryogenic or ultra-low temperature environments. While the PT100 sensor itself may be capable of measuring lower temperatures, the RTD-DI-16 module cannot process those values accurately.

Issue How many TC900 thermostats can be connected to a single BACnet MS/TP network on an AS-P? Product Line EcoStruxure Building Operation, Field Devices. Environment Building Operation Automation Server Premium. Building Operation Automation Server Bundled. TC900 Protocol Series Thermostat Cause Understanding system limitations for a single COM port when using BACnet MS/TP protocol. Resolution   Maximum Number of TC900 BACnet Devices per MS/TP Network Port Device Type Baud Rate Max Devices AS-P 9600 bps 7   19200 bps 16   38400 bps+ 26 AS-B 9600 bps 4   19200 bps 10   38400 bps 15   76800 bps 20 Additional Notes Performance Optimization: MS/TP field buses perform better with an RS-485 repeater. This may be necessary depending on the network layout and connected devices. Device Load Consideration: All devices (including TC900 and third-party BACnet devices) should present a 1/8 Unit Load to ensure proper bus performance. Recommended Baud Rate: For optimal balance between speed and reliability, 38400 bps is typically the best choice.

Issue Can a single transformer be used to power both full-wave and half-wave devices, such as an AS-P controller and a DuraDrive actuator? Product Line Field Devices, EcoStruxure Building Operation, Andover Continuum, Satchwell MicroNet, TAC INET, TAC Vista Environment Full-wave and half-wave devices Cause There may be a need to simplify power distribution by using a single transformer for multiple device types. Understanding Rectifier Types Full-Wave Rectifiers Function: Converts both halves of the AC waveform into DC. Components: Uses four diodes in a bridge configuration. Efficiency: More efficient than half-wave rectifiers, providing a smoother DC output with less ripple. Half-Wave Rectifiers Function: Converts only one half of the AC waveform into DC. Components: Uses a single diode. Efficiency: Less efficient, resulting in higher ripple in the output voltage. Resolution Yes, a common transformer can be used to power both full-wave and half-wave devices provided the following conditions are met: External Isolation Transformers Non-isolated, connected devices of varying rectifier types require their own external isolation transformers. Use external isolation transformers for each device if there is doubt regarding whether an installation may cause equipment damage Transformer Sizing: Ensure the transformer’s VA rating exceeds the combined power requirements of all connected devices. Undersized transformers can lead to voltage drops, overheating, or device malfunction. Installation Guidelines: Before installation, refer to the document titled “Guidelines for Powering Multiple Actuators From a Common Transformer - Integration Guide.” Isolation & Compatibility: Confirm that devices do not interfere with each other’s operation when sharing a transformer. Avoid connecting devices with incompatible grounding or isolation requirements.

Issue When manually binding the PowerFail system variable via a Numeric Input in the program header of a b3 controller, the value shown in the Binding Variables window may appear incorrectly (e.g., 1536 instead of a binary value like 1 or 0 ). Product Line EcoStruxure Building Operation Environment b3 controllers Script Program Editor Cause The Script Program Editor for b3 controllers does not recognize PowerFail as a predefined system variable. As a result, it displays an unexpected integer value in the Binding Variables window. Resolution Despite the incorrect display (e.g., 1536 ), the PowerFail variable functions correctly when bound to a Numeric Input. During compilation and execution, the system properly interprets the value. Best Practices for Scripting Treat PowerFail as a binary input: use logic based on True/False or ON/OFF . Ignore the displayed integer value in the Binding Variables window. Be aware that PowerFail is only active for one scan cycle immediately after power is restored following a loss. Example Usage Additional Notes This behavior is expected and does not impact the actual functionality of the PowerFail variable.

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 What are the NEMA or IP ratings for a specific product? Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment All devices Cause Users often need to know whether a product is protected against: Water ingress Intrusion by foreign objects (e.g., dust, fingers) Resolution To determine a product’s protection level, refer to the Degrees of Protection document, which includes: IP Rating Chart NEMA Enclosure Rating Chart 🔹 Understanding IP Ratings An IP rating consists of two digits: First digit: Protection against solid foreign objects Second digit: Protection against water Examples: IP20: Protected against fingers (≥12.5 mm), no water protection IP10: Protected against objects up to 50 mm, no water protection If a product datasheet does not specify water ingress protection, the second digit defaults to 0. 🔹 Typical Building Products Many building automation products: Prevent insertion of fingers (≥12.5 mm) Do not offer water protection → Common rating: IP20 📎 Attachment Degrees of Protection.pdf (Includes full IP and NEMA charts)

Issue When using a Windows PC with Microsoft Visual Studio installed, an unexpected error message appears referencing Just-In-Time (JIT) Debugging. This can interrupt normal operations and confuse users unfamiliar with debugging tools. Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating System Cause Visual Studio includes a feature called Just-In-Time Debugging, which attempts to launch the debugger when a program crashes or encounters a critical error. If enabled, this feature can interfere with other applications or workflows by prompting unexpected debug dialogs. Resolution To disable Just-In-Time Debugging, follow these steps: Open Visual Studio. Go to the Tools menu and select Options. In the Options dialog box: Expand the Debugging section. Select the Just-In-Time page. In the Enable Just-In-Time debugging of these types of code box, uncheck the relevant options: Managed Native Script Click OK to apply changes. Note: Disabling JIT debugging modifies a registry key. You must have Administrator privileges to make this change.

Issue When attempting to run LonMaker, the following errors may occur in succession: Could not listen on poet/tcp: The address specified is already in use (Error -2532) Database error: (Subsystem: LNS, #25) [DB #-2506] The global database is not open. (Subsystem: LNS, #64) Additional errors that may be caused by the same underlying issue: Problem connecting with the database server process: (Subsystem: LNS, #36) [DB#-2523] Error opening LCA Global database Product Line EcoStruxure Building Operation, Satchwell BAS & Sigma, TAC IA Series, TAC Vista Environment LonMaker for Windows 3.1 and 3.2 Sentinel Protection Installer 7.6.1 Cause  The issue is typically caused by a conflict between the Sentinel Protection Server and the POET Server, as both attempt to use the same port(s). Sentinel Protection Installer 7.6.1 installs the Sentinel Protection Server, which manages Sentinel SuperPro and UltraPro keys used with Satchwell Sigma and other products This service is not required for the dongle driver to function and can interfere with LonMaker’s operation. Refer to: Error: LNS #25 lcaErrDatabase for more technical details. Resolution To resolve the issue: Stop the Sentinel Protection Server: Open the Windows Services console: Press Windows + R , type services.msc , and press Enter. Locate Sentinel Protection Server. Right-click and select Stop. (Optional): Disable the service if not needed: Right-click > Properties > Set Startup type to Disabled. ✅ This will allow POET Server to operate without port conflicts.

Issue How to estimate the thermal load (in BTU/hr or Watts) that your controllers and equipment will produce. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Applicable to all electrical equipment used in building automation systems. Cause Understanding the thermal load is essential for: Sizing air conditioning systems Ensuring proper ventilation Avoiding overheating in enclosures Not all equipment datasheets provide thermal dissipation values, so manual calculation may be necessary. Resolution You can estimate the thermal load using the power consumption of each device. Formula To convert power (in Watts) to thermal load: BTU/hr = Power (W) × 3.412141633 Watts = Power (W) (already known) Note: 1 Watt = 3.412141633 BTU/hr Example Calculation Using the Continuum AC-1 I/O module: Power consumption: 2.6 W (without attached reader) Thermal load: BTU/hr = 2.6 × 3.412141633 = 8.87 BTU/hr Watts = 2.6 W If the reader is powered by the AC-1, include its power consumption in the total. International Units Reference Unit Conversion 1 Watt 3.412 BTU/hr 1 BTU/hr 0.293 Watts Additional Notes Use this method for any device where power consumption is known. For grouped equipment, sum the total wattage before converting. Consider using an online calculator for quick conversions.

Issue A BS5308 Part 1 Type 1 cable was installed under the assumption it would be used for Modbus communications. However, it was later determined that the application required M-Bus communication. This raised the question: Is the BS5308 cable suitable for M-Bus? Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, TAC Vista Environment M-Bus communication systems BS5308 Part 1 Type 1 cable (2-pair, individually screened) Cause The incorrect assumption that the communication protocol would be Modbus led to the installation of a BS5308 cable. Upon discovering that M-Bus was required, concerns arose regarding the cable’s compatibility with M-Bus communication standards. Resolution While the recommended cable for M-Bus communication is J-Y(ST)Y, which is specifically designed for indoor telephone applications and optimized for analog/digital signal transmission, the BS5308 Part 1 Type 1 cable can still be used for M-Bus under certain conditions. Key characteristics of J-Y(ST)Y cable: Designed for indoor telephone and data transmission Aluminium-laminated plastic foil static screen with tin-plated drain wire to minimize high-frequency electromagnetic interference Twisted pair (TP) structure to reduce crosstalk BS5308 Part 1 Type 1 cable considerations: Originally designed for instrumentation and control applications Features individually screened pairs, which can help reduce interference Electrical characteristics must be evaluated to ensure compatibility with M-Bus requirements Conclusion: Yes, the BS5308 Part 1 Type 1, 2-pair individually screened cable can be used for M-Bus communications, provided that its electrical characteristics meet the M-Bus system requirements. Refer to the attached calculation chart and datasheets for detailed compatibility analysis.

Issue The H909HV-S6 current transformer does not change state, even though current flow is present. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet Environment H909HV-S6 Current Transformer Cause The issue is due to incorrect wiring between the current transformer and the DDC controller. The installation instructions may appear to indicate that four connections are required to the DDC controller. However, this is not correct—only two connections are necessary. Resolution To resolve the issue: Review the wiring diagram in the installation instructions carefully. Ensure that only two connections are made between the CT and the DDC controller: The status output has two terminal sets, but only one connection is required from each set. Correct the wiring to match the proper configuration. 📄 Download the H909HV-S6 Datasheet