Building Automation Knowledge Base

Notifications

Community

Notifications

Categories
Forums
Knowledge Center
Blogs
Ideas
Events & Webinars

Share Your Feedback – Help Us Improve Search on Community!
Please take a few minutes to participate in our Search Feedback Survey. Your insights will help us deliver the results you need faster and more accurately.
Click here to take the survey

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Search in

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Building Automation Knowledge Base

Issue Error Message: AccDataservices.exe is missing or not found during system startup. Product Line Andover Continuum Environment Continuum AVG Anti Virus (or other antivirus software) Cause On February 15, 2012, updated virus definitions from AVG AntiVirus incorrectly flagged accdataservices.exe as malware, resulting in the file being quarantined. Resolution To resolve the issue: Restore accdataservices.exe from quarantine. Add the file to the exception/exclusion list in AVG or any other antivirus software in use. Restart the system to confirm the service starts correctly.

Issue The alarm bell icon, which should appear on Pinpoint door controls when the door is in an alarm state, is not visible. Product Line Andover Continuum Environment Pinpoint graphics interface Cause The door control is positioned on a lower graphic layer, and the alarm icon is being obscured by another graphic component placed above it. Resolution To resolve the issue: Select the affected door control in the Pinpoint interface. Right-click on the door control. Choose "Bring to Front" from the context menu. This action ensures the door control (and its associated alarm icon) is rendered above other graphic elements. Additional Notes: This issue is purely visual and does not affect the underlying alarm functionality. Consider reviewing graphic layer arrangements when designing or modifying Pinpoint views to prevent similar issues.

Issue Previously, Inovonics wireless sensor solutions were listed in our product catalog. Users are now unable to locate these products and are seeking alternative solutions. Product Line Andover Continuum Environment All Controllers Inovonics Cause Inovonics devices are no longer distributed by Schneider Electric. These products have been removed from our catalog and are now only available through third-party sales channels. Resolution Schneider Electric no longer offers Inovonics wireless sensors through its distribution channels. However, customers can still obtain Inovonics and other compatible third-party wireless devices via external distributors.

Issue NetController 2 IO Modules do not power up when using a third-party power supply. Product Line Andover Continuum Environment NetController 2, NC2, NCII IO Modules Cause When a third-party power supply (AC or DC) is used with the NC2, the IO modules do not receive power through the NC2 connector. Resolution To ensure proper operation: Use the Continuum Power Supply if you want the IO modules to be powered via the NC2 connector. If using a third-party power supply, the IO modules must be powered separately. Additional Notes This behavior is documented in the official NC2 documentation. Always refer to the product manual for detailed wiring and power requirements.

Issue Controller inputs or outputs cannot be reloaded. Product Line Andover Continuum Environment I/O Modules connected to NetController Cause The I/O module is offline, preventing successful reload operations. Resolution Verify communication status of the I/O module. Troubleshoot and resolve any connectivity issues between the NetController and the I/O module. Once communication is restored, retry the reload operation.

Issue When hovering the mouse cursor over the bang (!) icon in Continuum Explorer, the tooltip does not display any information indicating the issue. Product Line Andover Continuum Environment ACX57xx Windows 7 Cause Windows 7 may suppress tooltip display for certain UI elements, including the bang indicators in Continuum Explorer. Resolution To enable tooltips when hovering over the bang icon, modify the Windows Registry as follows: ⚠️ Important: Always back up the registry before making any changes. Open the Registry Editor (regedit). Navigate to the following path: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced Locate or create the following DWORD value: Value Name: ShowInfoTip Data Type: REG_DWORD Value Data: 0 – Tooltips Disabled 1 – Tooltips Enabled Set the value to 1 to enable tooltips. Exit the Registry Editor. Reboot the system to apply the changes. Additional Notes This registry setting controls tooltip visibility system-wide, not just in Continuum Explorer. If tooltips still do not appear after rebooting, verify that no group policies or third-party software are overriding this setting.

Issue When trying to dump the Gerry Log from several controllers on the network, the header and errors appear to be identical. Product Line Andover Continuum Environment CX99xx NetController Controller error log Cause The NetController requires a direct physical connection via RS232 to access diagnostic logs. Network-based retrieval is not supported for first-generation models. Resolution To successfully retrieve the Gerry Log from a first-generation NetController: Connect directly to the controller using an RS232 serial cable. Use the Continuum CyberStation or compatible terminal software to initiate the log dump. Ensure the correct COM port is selected and communication parameters (baud rate, parity, etc.) match the controller’s settings. If multiple controllers show identical logs, verify each connection individually to rule out cabling or port configuration issues.

Issue Understanding the impact of exporting point values over a wireless bus in Continuum systems. Product Line Andover Continuum Environment Continuum wireless solution Cause Exporting point values—especially in large numbers—can affect wireless bus stability due to the nature of wireless communication protocols. Resolution If numerous points are configured for export on a wireless bus, it may lead to network instability. This is because: Wireless exports are point-to-point communications, unlike wired Infinet which uses broadcast messaging. Every value change, even those triggered by alarms, can result in an export, potentially overwhelming the network. To mitigate this: Apply thresholds to exported points: A threshold ensures that a point's value is only exported when the change exceeds a defined limit. This is especially critical for analog points with alarms, as they can generate frequent exports due to continuous value changes. Review and optimize export configurations: Avoid exporting non-critical points. Use alarm filters and deadbands where applicable. Monitor wireless bus performance: Regularly assess traffic load and adjust configurations to maintain stability. Best Practices Use thresholds to reduce unnecessary traffic. Prioritize critical points for export. Avoid exporting points that change frequently unless absolutely necessary.

Issue After creating a new bCX controller, system objects such as system variables are not visible. Product Line Andover Continuum Environment CyberStation bCX4040 ACX57xx Cause CyberStation did not fully create the new controller object in the database. This can occur due to a communication or initialization issue during the creation process. Resolution To resolve the issue: Delete the newly created controller from the Continuum Explorer. Restart CyberStation to ensure all services are refreshed. Recreate the controller using the standard procedure. Tip: Ensure that CyberStation is running with appropriate permissions and that the database connection is stable before recreating the controller. Additional Notes: If the problem persists after following the steps, verify the controller firmware version and compatibility with CyberStation.

Issue Access cards that were previously functioning correctly now return an “Invalid Read” error when presented to the card reader. Product Line Andover Continuum Environment Card reader Cause The card reader’s power supply failed to deliver adequate power. The backup battery had also been depleted, resulting in insufficient voltage being supplied to the reader, which caused the “Invalid Read” error. Resolution Inspect the card reader’s power supply and backup battery. If the power supply is faulty, repair or replace it. If the backup battery is depleted, replace it to ensure consistent voltage delivery. After replacement, test the reader with a known working access card to confirm functionality.

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.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Unable to find file error.

Alarm Bell Indicator Missing on Pinpoint Door Controls

Are the Inovonics wireless sensors still available for Continuum Controllers?

NetController 2 IO Modules not powering up when using third party power supply

Cannot reload a NetControllers Inputs or Outputs.

No descriptors appearing when mouse is hovered over the bang on a controller in Continuum Explorer.

Trouble retrieving the Controller Error Log from a first generation NetController.

What are the effects of points that are flagged for export on a wireless bus.

Created new bCX and can't see any of the system objects like system variables

Access Cards Previously Functioning Now Return “Invalid Read” on Card Reader

Will the first generation Modbus RTU xdriver work on the CX9200?

Upgrade from 1.74 to 1.9x returns "Event Log is Full" error.

Door output on AC1 module stays energized continuously.

Can a New Version of Continuum Software Access a Database Configured for an Older Version?

What are the Output ratings on a Digital Output for B3-920

Configuring sites that are located in different time zones in Continuum

preventDefault() Javascript function not working on Mouse Up

Xenta Groups offline in Vista classic or not getting any alarms

User names and passwords configured on a Building Operation Domain are not accepted by the AS's.

Get the following message in Windows Event Viewer "Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)"

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!