Building Automation Knowledge Base

Issue Users may encounter difficulties when attempting to use the first-generation Modbus RTU XDriver with the CX9200 controller. Product Line Andover Continuum Environment CX9200 X-Driver Modbus RTU Cause The issue typically arises due to uncertainty around compatibility between legacy drivers and newer controller hardware. Resolution The CX9200 is fully compatible with the first-generation Modbus RTU XDriver. There are no known limitations or issues when deploying this driver on the CX9200 platform. Additional Notes Ensure that the driver is correctly installed and configured according to the standard Modbus RTU setup guidelines. If communication issues persist, verify baud rate, parity, and device addressing settings. For advanced troubleshooting, refer to the Modbus RTU Integration Guide or contact Schneider Electric support.

Issue Upgrading a standalone workstation from version 1.74 to 1.9x fails with the error message: "Event Log is Full" Product Line Andover Continuum Environment Standalone Workstation Cause This error occurs when the Windows Application Event Log has reached its maximum size and cannot log additional events. Resolution To resolve the issue, follow these steps: Open the Windows Control Panel → Navigate to Administrative Tools → Open Event Viewer Clear the Application Event Log → In the left pane, select Application → From the Action menu, choose Clear All Events → When prompted to save the log before clearing, click Yes → Enter a suitable file name and click  Restart and Reinstall → Perform a cold start of the workstation → Reinstall Continuum version 1.9x

Issue The door output on the AC1 module remains energized continuously, rather than pulsing for the duration of the configured strike time. Product Line Andover Continuum Environment CX9900 CX9940 NC1 NC2 Cause The AC1 Plus module was replaced with a standard AC1 module, but the controller was not reloaded afterward. Resolution Reload the controller after replacing the AC1 Plus module with an AC1 module to ensure proper output behavior.

Issue A Continuum database configured for version 1.81 is not compatible with newer versions of the Continuum software. Product Line Andover Continuum Environment Continuum all versions Cause Continuum software and its database are version-dependent. Attempting to use a newer version of the software (e.g.1.9) with a database configured for an older version (e.g.,1.81) will result in incompatibility. Resolution To ensure proper functionality, the Continuum software version must match the database version exactly. For example: A database configured for version 1.81 will only work with software version 1.81. Attempting to use version 1.9 with a 1.81 database will fail. This applies to all versions of Continuum. Always verify that both the software and database versions are aligned before deployment or upgrade. Additional Notes This version dependency is critical for maintaining system stability and avoiding data access issues. Consider backing up your database before performing any upgrades. For upgrade paths or migration assistance, consult Schneider Electric support or your local technical representative.

Issue What are the output ratings for the digital outputs on the B3-920 controller? Product Line Andover Continuum Environment B3-920 controller Cause Clarification needed on the electrical specifications and configuration options for the B3-920 digital outputs. Resolution The B3-920 controller includes: 8 Digital Outputs Each output is a Single Pole Single Throw (SPST) Form C relay. Configurable Output Option Any two consecutive Form C outputs can be configured as one Form K Tri-state output. Electrical Ratings Maximum Current: 3A Voltage: 24VAC/VDC Transient Protection: ±1500V (Tested according to EN61000-4-4 standard)

Issue Is it necessary to create a separate Continuum network for a site located in a different time zone, even if it's the only one outside the Time Zone? Product Line Andover Continuum Environment Continuum system with sites across multiple time zones UTC time zone configuration Continuum Networks Cause The site in question operates in a different time zone than the rest of the sites being integrated into the Continuum system. This discrepancy can lead to complications in data logging, scheduling, and alarm management. Resolution While it is technically possible to manage schedules locally and have alarms timestamped according to the local time zone, these approaches are not optimal for system-wide operations in Continuum. Extended logs become difficult to manage when data points are logged by a controller in Time Zone A and then accessed by a CyberStation in Time Zone B. This mismatch can lead to confusion and inefficiencies in interpreting historical data. For this reason, it is not advisable to place controllers from different time zones under a single Continuum Network. Extended logs are stored in the database using UTC timestamps. CyberStation interprets these logs through reports or groups, which can lead to inconsistencies if time zones are not aligned across the network. Recommendation To ensure consistent data logging and system behavior, create separate Continuum networks for sites operating in different time zones.

Issue The preventDefault() JavaScript function does not work as expected when used with the Mouse Up event. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Users may attempt to override the default behavior of the Building Operation Properties Editor by using preventDefault() on the Mouse Up event. However, the editor is triggered by the Mouse Click event, not Mouse Up. Resolution To successfully prevent the default behavior and override the launch of the Properties Editor: Select the TGML Script where the interaction is defined. Use the onClick event instead of onMouseUp. Add the following line inside the onClick function: evt.preventDefault();​

Issue Xenta Groups do not come online under Echelon LTA in Vista Classic or Xenta 911, and no alarms are received from any Xenta devices. The LTA is online, and the LonWorks network is commissioned and operational, but the Xenta groups remain offline. Product Line TAC Vista Environment Vista Server Cause The group master controller may be offline, causing the entire Xenta group to report an offline status. Naming convention issues such as: Use of spaces Exceeding character limits Use of unsupported characters (e.g., slashes) Resolution To resolve the issue, follow these steps: Verify the group master controller is online. Ensure no object name exceeds 20 characters, including: LTA name LonWorks group name Xenta group name Individual Xenta device names Avoid using spaces in any names. Use underscores (_) instead of spaces. Do not use slashes (/ or \\) in names. Replace with underscores (_) instead. Additional Notes Consistent naming conventions are critical for proper communication between devices in the LonWorks network. If the issue persists after applying these steps, consider reviewing the network configuration or contacting support.

Issue User names and passwords configured on a Building Operation Domain are not accepted by the Automation Servers (AS). Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause A new Domain was configured on the Enterprise Server (ES), exported, and then imported to each AS. This process creates unrelated Domains across servers, which is not the intended operational setup. It results in duplicate user accounts with potentially different passwords, leading to a complex and unmanageable configuration. Resolution To correctly configure a shared Domain across the ES and ASs, follow these steps: Add ASs to the ES Connect the Workstation to the ES and add the Automation Servers in the usual way. Create a New Domain on the ES Navigate to Control Panel > Domains. Click Add, assign a meaningful name to the Domain. Select the ASs that will share this Domain with the ES. Click Create. Note: The new Domain will be visible when reviewing the ASs, but nothing will appear in the Domain folder on an AS. Set the New Domain as Default (Optional) Right-click the Domain and select Set as Default Domain.                                         Repeat this step on each server. Verify ES IP Address Ensure the ES IP address is correctly configured on all ASs. Create User Groups, Users, and Workspaces Set up the necessary User Groups, Users, and Workspaces for the new Domain. Restart the ES and Log In Log off the Workstation. Restart the ES. Log back in using the new Domain credentials. Log In to ASs Use the new Domain credentials to log in to each AS.

Issue You receive the following error message in Windows Event Viewer: "Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)" The full error message is: System.FormatException: Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). at System.Guid.TryParseGuidWithNoStyle(String guidString, GuidResult& result) at System.Guid.TryParseGuid(String g, GuidStyles flags, GuidResult& result) at System.Guid..ctor(String g) at TAC.DSS.BusinessLogic.TrendLogProcessor.GetLogValues(XmlDocument filterXml, ITrendLogValuesInterface values) at DssCliLib.TrendLog.GetLogValues2(SByte* pszConnectionString, Char* bstrFilter, ITrendLogValues* pValues) Product Line TAC Vista Environment Vista Workstation Cause This error occurs when Trend Log Calculation Objects are misconfigured. Specifically, the "Trend Log Object" field is left blank. When Vista attempts to execute the trend log calculation, it tries to retrieve data using the GUID of the associated trend log object. If the field is blank, Vista returns a placeholder like "126??"—which does not conform to the required GUID format. The GUID (Globally Unique Identifier) is essential for linking the trend log calculation to its data source. A missing or malformed GUID causes the system to fail when parsing the identifier. Resolution To resolve this issue: Review all Trend Log Calculation Objects in your Vista configuration. Ensure that each object has a valid reference to a Trend Log Object. Update any blank or incorrect fields to include the correct GUID. Tip: You can use the Vista Workstation to inspect and edit these objects. Look for any entries where the "Trend Log Object" field is empty or contains invalid data.   Additional Notes This issue typically appears at regular intervals, depending on how frequently the trend log calculations are triggered. Correcting the configuration should eliminate the error from the Event Viewer.

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. Issue The Media Gateway Card is unable to send panel messages to the converter, which translates the panel language into Modbus/BACnet protocols. Product Line ESMI Fire Detection. Environment FFSULH1007. Cause The TCP/IP port on the Media Gateway Card is not functioning correctly, impacting BMS integration with the panel. Resolution Check Firmware Version Navigate to Engineer Options → System Information. Ensure the LAN cable is connected to ETH 1 port. ETH 0 should be set to DHCP. Verify the firmware version: Expected version: S794_V01.109 Firmware Update (if needed) If the version is not visible or outdated, update the firmware. Refer to this article: Esmi Ultima Media Gateway Card Firmware Update Configure Graphics / Third Party & VR Settings Go to Engineer Options → Configuration → Panel Module → Media Gateway Card Select Graphics / Third Party Settings and apply changes as per reference images.   Submit the settings. Then go to VR Settings and apply changes as per reference images. Outcome After applying the above steps, the issue should be resolved

Issue Understanding common Modbus error codes that appear in Building Operation trace logs. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Enterprise Server Modbus Cause Modbus protocol errors are seen when looking at Building operation trace logs. Resolution Below are common Modbus error codes observed in trace logs, their meanings, and example log entries. Error Code 4 – Server Device Failure Message: RESP_DATA_MISMATCH Meaning: This error indicates that the Modbus slave device encountered an unrecoverable internal error while attempting to execute the requested command. This is a problem within the slave device itself, not a communication error on the client side. Possible Causes: Attempting to write to a protected memory area Device in an unsuitable state for the command Example Log Entry: Dec 27 08:15:01 AS-P-18E4A6 nsp_servers[1151]: 2024-12-27 08:15:01.767 [1654641088] nsp.pin.modbus.SerTransport Flush buffer. Protocol error code = 4 Error Code 10 – Illegal Data Value Message: Flush buffer. Protocol error code = 10 Meaning: This error suggests the slave device rejected a data value sent by the master. Possible Causes: Value out of acceptable range Attempt to write to a read-only address Example Log Entry: Dec 27 08:15:01 AS-P-18E4A6 nsp_servers[1151]: 2024-12-27 08:15:01.774 [1654641088] nsp.pin.modbus.SerTransport Flush buffer. Protocol error code = 10 Error Code 7 – CRC Header Issue Message: Flush buffer. Protocol error code = 7 Meaning: This error indicates a CRC (Cyclic Redundancy Check) mismatch in the response message. Possible Causes: Incorrect CRC calculation by the device Incomplete or corrupted packet Example Log Entry: 2025-07-22 10:14:39.636 [1666360064] nsp.pin.modbus.SerTransport Flush buffer. Protocol error code = 7

Issue Need a Menta programming solution to monitor pulse signals from water, electric, or gas meters. Product Line TAC Vista Environment Vista Workstation Cause A Menta program is required to interpret pulse signals from various utility meters. Resolution The Menta macro provided below is configured to receive and process pulse signals from three types of meters: Water meter Electric meter Gas meter You can download the source file by clicking the image of the Menta macro below: Additional Notes This macro can be customized to suit different pulse rates or meter types. Ensure proper signal conditioning if the pulse signal is noisy or irregular.

Issue When attempting to install the Loytec NIC software, the USB driver installation fails and an error screen is displayed. Installing USB Drivers Failed LOYTEC NIC Driver Installer Error Installing USB Drivers: Could not pre-install Drivers Product Line TAC Vista Environment Vista Server Cause The failure occurs due to insufficient administrative privileges, even when logged in as a domain administrator. The installer requires local administrator rights to successfully install USB drivers. Resolution To resolve the issue, follow these steps: Locate the installer executable file (.exe) for the Loytec NIC software. Right-click on the file and select “Run as…”. Choose the local administrator account (not the domain admin). Proceed with the installation. The USB drivers should now install successfully. Additional Notes This issue is commonly encountered in environments where domain policies restrict driver installations.

Issue Step-by-step instructions for installing and configuring a Loytec NIC852 dongle (Orion Stack) for enhanced LNS communications. Product Line TAC Vista Environment Vista Server Cause A single Vista server typically supports up to four average-sized LNS networks. Larger networks or multiple LNS ports on one server can degrade communication reliability. The Orion Stack modifies how Vista communicates with the LNS Server, allowing support for up to 28 LNS Ports. Resolution Pre-Installation Notes If LonWorks Interfaces were previously configured as your Network Interface, delete the computer’s IP address from the IP-852 tab before proceeding. Installation Steps Insert the NIC852 Dongle into a USB slot on the Front-End computer. Ensure the dongle remains plugged in at all times for Orion Stack functionality. Install Required Software using the Loytec CD: Hardware drivers LConfig interface Update Drivers Download the latest NIC interface drivers from: Loytec Driver Downloads Verify Installation The Loytec symbol should appear in the Windows system tray. Right-click the icon and launch LConfig. NIC852 Configuration via LConfig In LConfig, go to the NIC852 tab: Enable the device Set Transceiver to IP-10L Select the number of LNS Applications (LNS databases) Click CNIP Configuration: Enter IP addresses for: Device (Front-End Computer) Configuration Server Enter the Device Name (Computer Name) Click OK twice to apply settings Test the configuration before closing Vista & LonMaker Setup Open LonMaker: Open the first drawing directory with “Show all network options dialogs” checked Configure the Network Interface: Check “Network Attached” Select the first NIC_852 entry Proceed through dialogs by clicking “Next” Save and exit To configure each LNS network interface: Go to LonMaker > Network Properties in Visio Use the Network Interface tab to select the correct NIC   TAC Network Communication Port Setup Open TAC Vista System Plug-In: Navigate to LonMaker > System Plug-In > TAC Vista System Plug-In Right-click the Network (top of controller tree) Click Settings Under the Network tab, select Communication Port – Loytec Click OK Update the TAC Network Repeat Steps 6–10 for each LNS database: Use a different Network Interface for each Final Notes Once all NICs are configured, the Orion Stack setup is complete. Tip: Add a note on the site’s main graphics page indicating that an Orion Stack is installed. This helps inform remote support engineers and other users.

Issue The TAC Vista to SmartStruxure Interface fails to connect when the operating system is set to a non-English format. Product Line TAC Vista Environment Vista server Cause This issue occurs due to the Windows Format setting being configured to a non-English language. The interface requires the format to be set to English for proper connectivity. Resolution To resolve the issue: Open Control Panel in Windows. Navigate to Region and Language settings. Under the Formats tab, change the format to English. Click Apply to save the changes. Note: This issue is resolved in Vista version 5.1.9. For instructions on creating the Vista interface in SmartStruxure, refer to How to Create TAC Vista Interface to SmartStruxure.

Issue Support for OPC or DDE integration with EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Cause The OPC Server is a software program that converts hardware communication protocol into the OPC protocol. The OPC client software is any program that needs to connect to the hardware. It uses the OPC Server to retrieve data from or send commands to the hardware. Resolution Supported Functionality OPC UA Client functionality is available in EBO version 6.0.1 or higher. Refer to: OPC UA Client Support Currently Not Supported OPC UA Server OPC DA Client/Server DDE Configurations Alternative Integration Options If integration with unsupported protocols is required, consider the following alternatives: Protocol Conversion Use a converter to translate between OPC and a protocol supported by EBO. Examples: OPC Server → BACnet Server EBO BACnet Points → OPC Recommended 3rd Party Tools (not supported by Schneider Electric): Kepware Matrikon SCADA engine Note: Ensure the EBO server's role is clearly defined (e.g., exchanging point values) to determine compatibility. SmartConnector Extension Use a SmartConnector Extension as middleware between EBO and an OPC client/server. Resources: Exchange shop SmartConnector Server EBO SmartDriver and Smart Connector Additional Notes These integration methods involve 3rd party software and may require additional configuration and validation. Schneider Electric does not provide support for 3rd party tools.

Issue When attempting to connect from a TAC Vista Remote Workstation, the following error appears: "Ensure that TAC Vista Server is started" This occurs even when DCOM settings appear to be configured correctly. Product Line TAC Vista Environment Vista Server Workstation Cause This issue typically arises when both the TAC Vista Server and the Remote Workstation are part of a workgroup rather than a domain. In such configurations, authentication and DCOM communication can fail if certain conditions are not met. Resolution To resolve this issue: Verify DCOM permissions are correctly configured on both the server and the workstation. Ensure that the Administrator account password is identical on both machines. This is necessary for authentication in a workgroup environment. Restart both the TAC Vista Server and the Remote Workstation after making changes. Additional Notes This issue does not typically occur in domain-joined environments, where centralized authentication handles these permissions. For more information on DCOM configuration, refer to the TAC Vista DCOM setup guide

Issue Users are unable to open files from a TGML graphic in TAC Vista Webstation using the OpenFile command. Product line TAC Vista Environment Vista Webstation Vista Workstation Cause The OpenFile command is not supported in web browsers, which prevents documents from opening directly in Webstation. Resolution To enable file access from TGML graphics in both Workstation and Webstation, follow these steps: In TAC Vista Workstation Use the OpenFile button as usual. Files (PDF, DOC) open without issues. In TAC Vista Webstation The OpenFile command does not function in a browser. Instead, define a hyperlink in TAC Vista: Place the document in the server folder: C:\Inetpub\wwwroot Use the format: http://<ip_address>/<docName> Typical Graphic Behavior Document Type Workstation Behavior Webstation Behavior PDF Opens normally Opens in same window (even with _blank target) DOC Opens in extra window (must be closed manually) Opens normally Additional Resources For an alternative way of viewing the reports and other files, refer to TAC Vista - Web Reports - Schneider Electric Community

Issue Is it possible for multiple Automation Servers to be placed on the same backplane and use one power supply? Some known issues in this unsupported configuration: Automation Server only partially discovers the IO Modules Function Block Programs (FBP) remain in an unloaded state (see FBP Unloaded) EBO 2022 (v4.0) and higher, Alarm: IO Driver unexpectedly timed out Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Automation Server (EBO 2022 and above) EcoStruxure Building Operation Power Supply (PS-24V) EcoStruxure Building Central IO Modules Cause The terminal bases provide a path for communication between all connected units on the same backplane; as such, the connection of two or more Automation Servers will cause communication issues between all connected units on that same backplane. See the following article on how to check the CIO node the Automation Server is using: How to identify Automation Server(AS) ID node count   Resolution From EBO 2022 (v4.0.1) due to changes in the Central I/O (CIO), checks are now made in the Automation Server to verify that the server is physically in SLOT 2; if this is not the case, then all Tasks are disabled and will not run.    You cannot connect more than one Automation Server to the backplane. Only one Automation Server is allowed per power supply, the architecture is always "PS-AS-....." and after that I/O modules with additional PS units as needed, but only one Automation Server can exist on the same backplane.   Note that an alarm will also generate if you attempt the following configuration (also not supported)  PS-AS-PS-AS  Alarms will only clear after a restart (warm) of the server