Issue The ACX57xx controller intermittently stops granting access through doors. The controller operates normally for a period but then ceases to grant access until it is reloaded. Replacing the controller does not resolve the issue. Product Line Andover Continuum, EcoStruxure Building Operation Environment ACX5740 ACX5780 Cause A single power supply is being used to power both the controller and the door strike outputs, which can lead to voltage drops or interference affecting controller performance. Resolution Install the ACX57xx controller according to the ACX57xx Controller Installation Instructions, ensuring separate and adequate power supplies for the controller and strike outputs.

Issue What is the maximum allowable cable length for the Continuum I/O bus when connecting IOU modules? Product Line Andover Continuum Environment IOU Modules Continuum I/O Bus RS-485 and FTT-10A network configurations Cause Cable length impacts signal strength and integrity. Longer cables cause signal loss and distortion, which can lead to communication failures. Resolution Follow these maximum cable length specifications for the Continuum I/O bus: RS-485: 2000 ft (610 m) FTT-10A: Double termination: 8858 ft (2700 m) Free topology: 1640 ft (500 m) Ensure proper termination and topology to maintain reliable communication.

Issue Older Continuum access controllers (CX9900, CX9702, ACX700, ACX781) only support one card credential per user locally. When the system is configured for dual credentials, these controllers cannot store the second credential, leading to unexpected access behavior. Product Line Andover Continuum Environment CyberStation CX9900, CX9702 ACX700/1, ACX780/1 Dual credential configuration Cause Older controllers lack the capability to store two credentials per user. CyberStation does not distribute the second credential to these controllers, causing reliance on remote validation. Resolution Enable remote validation on older controllers by setting the Access Server system variable to the ACCNetId of the primary access server (any value in the range 191–254 works, but use the primary server for consistency). Explanation: When the second credential is presented at a door managed by an older controller, the controller sends a remote validation request to the access server. Access is granted or denied based on the server response. Note: Changing Allowed Credentials in CyberStation does not affect older controllers. They will continue granting access to credential 1 until reloaded.

Issue When assigning a schedule to a personnel area located in a different Continuum network than the door, the schedule does not function as expected. Product Line Andover Continuum Environment ACX5740 ACX5720 Continuum Access Control systems with multiple networks Cause Objects cannot be passed between different Continuum networks. A schedule linked to a personnel area assignment must reside in the same network as the door that uses the area. Resolution Ensure that the schedule is located in the same network as the door requiring the area assignment. Best Practice:Place schedules within the controller for the door. This ensures that if the controller goes offline, the schedule will still operate correctly.

Issue Users need access to the Declaration of Conformity (DoC) documentation for Andover Continuum hardware to meet regulatory compliance requirements. Product Line Andover Continuum Environment Continuum controllers and devices Regulatory compliance documentation  Cause The location of the Declaration of Conformity documentation is unclear, making it difficult for users to find the required compliance certificates. Resolution The Declaration of Conformity documentation for Andover Continuum hardware is available through Regulatory Compliance on mySchneider Steps to Access: Navigate to mySchneider. Search for “Andover Continuum Declaration of Conformity” Download the relevant certificate for your hardware.

Issue What keypads are supported by ACX781 controllers? Product Line Andover Continuum Environment ACX781 Controller Access control systems requiring keypad input Cause The ACX781 controller circuitry only supports 3x4 matrix dry contact keypads. It does not support Wiegand keypads or voltage matrix keypads such as “2 of 7.” The reference to “2 of 7” in the ACX781 cutsheet is incorrect. Resolution Use a keypad that supports the 3x4 matrix dry contact interface, such as: Essex Keypad HID model 5355AGS00 If you require Wiegand keypads, you must upgrade to a controller that supports Wiegand, such as: ACX57xx series CX9900 + AC1 CX9680 + AC1

Issue The Error LED on ACX780 or ACX781 controllers is illuminated. Users want to know: Is the LED linked to the Errors system variable? What conditions trigger the LED? How can the error be cleared? Product Line Andover Continuum Environment ACX780 ACX781 Continuum access control system Cause The Error LED is associated with the controller’s Errors system variable. A non-zero value typically indicates an internal issue, most commonly a disabled program within the controller.  Resolution Use Command Line or CyberStation to check the Errors system variable. If the value is non-zero, investigate and correct the underlying issue (e.g., re-enable disabled programs). To clear the LED, set the Errors system variable back to 0 after resolving the cause. Note: Simply resetting the variable without fixing the root cause may result in the error reappearing.

Issue How to print a Control Backslash (CTRL\) character from a PE program in Continuum systems. Product Line Andover Continuum Environment Continuum PE(Plain English) Cause The PE device driver expects an escape sequence starting with CTRL\  followed by a specific code. Without this sequence, the output will not be interpreted correctly. Resolution The following line will send the expected esc sequence followed by the value of the Minute system variable out of comm1 (assuming the port is already opened for printing): Print "|28", Minute to comm1

Issue Users encounter Runtime Error 312 when attempting to access the embedded webpage of controllers such as NC2 and BCX. Product Line Andover Continuum Environment Embedded Webpage NC2 Controller BCX Controller ACX B4 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 The error occurs due to malware present on the PC accessing the embedded webpage. Resolution Run a full virus scan on the PC. If the virus scan does not successfully remove the malware, format and reinstall the operating system to ensure the PC is clean.

Issue When ordering a bCX1 controller (models 9640 or 4040), the number of controller nodes displayed on the options page is one more than the ordered quantity. Product Line Andover Continuum Environment bCX1 9640 bCX1 4040 Cause All bCX1 controllers include one additional node beyond the ordered quantity. This extra node is reserved for connecting a RoamIO device to either the MS/TP or Infinet network. Resolution The additional node is intentional and allows the RoamIO to connect to the network. When designing a system, always leave one node available for RoamIO. Example: An 8-node controller supports up to 9 nodes. A 32-node controller supports up to 33 nodes. If all nodes are used, offline editing may be required to add the last node.

Issue When an active video event appears in the Video Monitor interface during an alarm, the events disappear after closing the Video Monitor. Users cannot locate or replay these events later. Product Line Andover Continuum Environment Andover Continuum 1.91 and above Cause This behavior is by design. The system does not store video event lists for historical access. Resolution Video events are only available while active in the Video Monitor interface. Historical video event lists are not saved in the system. To search and replay recorded videos based on alarm events, use the Continuum Video Inquiry add-on application.

Issue During the installation of Microsoft SQL Server 2005, the process appears to hang for an extended period, particularly at the “Setting File Security” step. Product Line Andover Continuum Environment Microsoft SQL Server 2005 Cause This is a known Microsoft issue. Under certain conditions, the installation process stalls while setting file security due to network-related factors. Resolution Disconnect the machine from the network before starting the installation. This typically allows the process to complete quickly. Alternatively, apply the cumulative hotfix provided by Microsoft to resolve this issue.

Issue Users need to install Continuum or webClient but do not currently have the security key connected to the PC. Product Line Andover Continuum Environment Continuum webClient Cause The installation process does not require the security key; however, the application cannot run without it. Resolution Yes, you can install Continuum or webClient without the security key connected to the PC. The security key is required only to run Continuum Cyberstation or the webClient server after installation. Ensure the key is available before attempting to start the application.

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

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

Issue When adjusting the Elevator Relay Time in the elevator reader, the option to save appears, but the setting does not persist. Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Mercury MP1502 controller (version 08-2.4.0.653) OSDP Reader Cause The Access Expert Client has an issue with saving individual elevator relay time settings. Resolution Workaround: Navigate to Instance Settings and set the relay time globally. This applies the same relay time to all readers; individual reader settings cannot be saved until the underlying issue is resolved. Additional Notes: Client version: 25.9.26 Controller version: 08-2.4.0.653 A permanent fix will be provided in a future release.

Issue ACCDataServices crashes when starting CyberStation or during normal operation. Product Line Andover Continuum Environment CyberStation Cause Windows permissions issues Windows Firewall configuration Mixed CyberStation versions (e.g., 1.94 and 1.94 SP1) Heavy resource usage on standalone systems Third-party BACnet devices flooding trend logs Resolution Step 1: Software Updates Do NOT mix 1.94 and 1.94 SP1 CyberStations on the same database Install CyberStation 1.94 SP1 or greater 2.03 is the most current version and Upgrade controller firmware to the most recent Step 2: Installation Requirements Ensure user has Local Admin rights during CyberStation installation. Turn Windows Firewall OFF during installation. (Open ports Disable VirusScan software during installation (Turn on during normal operation) Step 3: Event Notifications Avoid unnecessary recipient options (Pager, Log, Forward, etc.) to reduce traffic. Check enhanced alarm delivery in Database Initialization > Server (or Stand Alone). Examples of unnecessary recipient options Step 4: Action-Object Mapping Ensure each Event notification action (e.g., Display Graphic) has a corresponding object for point alarming. Step 5: Stand-Alone Cyberstation Systems Heavy resource usage when extended logging, graphics, SQL Server, CyberStation run together can contribute to errors Eliminate Windows error log issues and disable certain functions like graphics to see if that feature contributes to the errors Consider server-class PC for demanding sites Step 6: Third-Party Devices Disable/unplug 3rd party BACnet devices or disable their trend logs Step 7: Liebert Sitelink Versions 1.93 and below: Bacnet trendlogs may affect Continuum by flooding data Upgrade to 1.94 or greater and disable trend logs Step 8: Diagnostics Run acctrace, Continuum error log, Windows application log and Wireshark to detect errors. Use Windows application logs, system info Reference Article: Top 10 Steps for Troubleshooting Cyberstation and webClient issues

Issue There are many issues that can happen at Cyberstation and methods are needed to troubleshoot. Product Line Andover Continuum Environment Cyberstation Cause There are software updates and environmental reasons for issues coming from Cyberstation and there are a number of tools to help troubleshoot. Resolution This guide covers both software and hardware troubleshooting steps for Cyberstation and webClient issues. Use these methods and tools to diagnose problems: Determine Scope Is the issue isolated (one workstation) or system-wide (multiple workstations)? Isolated issues may relate to: Installation problems Windows OS or hotfixes Hardware failures Check Continuum Compatibility Verify versions of: Continuum Service Packs Windows OS (including Service Packs) Microsoft SQL Server Internet Browser webClient Software and Firmware Compatibility Matrix Version 2.03  Review Cyberstation Error Messages Look for error messages displayed on screen. Access help: Press F1 in Cyberstation → Index → Type “Error” → Select “Error Messages” Locate Cyberstation error messages How do you locate error messages in Cyberstation?     4. Check Windows Event Viewer Look for errors or event IDs at the time of the issue. Use logs to: Search online for solutions Share with support Sharing Windows Event Logs for Troubleshooting Purposes  Verify Windows Updates Were any Service Packs or hotfixes recently applied? List all updates: Windows: How to List All of the Windows and Software Updates Applied to a Computer Check Installed Software Review recently installed programs: Windows XP: Control Panel → Add/Remove Programs Windows 10: Control Panel → Programs and Features Scan for Viruses/Malware Ensure Anti-Virus and Malware tools are updated. Run full scans to clean infected PCs. Inspect Hardware Common failure points: Memory: Use BIOS diagnostics Hard Drive: Run CheckDisk; reformat if needed NIC (Network Interface Card): Swap if faulty Graphics Card: Update drivers or replace Use Windows Device Manager Look for devices with an exclamation point. Error codes in Device Manager in Windows Gather System Information System Info (Msinfo32): Description of Microsoft System Information (Msinfo32.exe) Tool  Restore Point or Reinstall Use Windows Restore Point (XP, Vista, 7): What is System Restore? If unsuccessful: Reformat hard drive if necessary and Reinstall Cyberstation or Windows OS

Issue What is a suitable replacement for SHM-001 or SHM-002 short haul modems used with DMS control systems? Product Line TAC IA Series Environment DMS Systems using SHM-001 or SHM-002 short haul modems Cause Failure of SHM-001/002 short haul modems or inability to source discontinued models. Resolution   Recommended replacement: Model 1000SM from Patton Electronics Product details: Patton Electronics Model 1000SM Refer to original SHM-001/002 datasheet for wiring and installation guidance (Attachment: shorthaulmodem.pdf).

Issue Can the MF41-6043 actuator be wired to and controlled by a DMS MicroSmart MSC-V-511 controller when replacing a defective actuator? Product Line TAC IA Series, Field Devices Environment DMS MSC-V-511 MF41-6043 Cause The original actuator is defective and discontinued, making it impossible to replace with an identical unit. Resolution The MSC-V-511 controller can control the MF41-6043 actuator using its triac outputs. Terminals D1 to D4 on the MSC-V-511 provide 24 Vac, which matches the actuator’s voltage requirement. No external power source is needed because the MSC-V-511 supplies 24 Vac power. Wiring and programming details: Refer to MSC-V-511 Installation Guide (F-25710), page 18. Refer to MF41-6043 Installation Guide (F-26736), page 6 for wiring diagrams. Power considerations: Actuator requires 2.3 VA. MSC-V-511 digital outputs can supply up to 12 VA.