Issue Controller crashes during reload. Error log shows illegal instruction. 0xbadd0004 0x00002000 0x01802174 0x40102000 0x085be4d8 Reset (illegal instruction) Environment All CX controllers Cause Incompatible XDriver loaded. Continuum controllers can be either first or second generation. The XDriver used must be matched with the controller generation.   First generation controllers are 92xx, 94xx, 99xx Second generation controllers are 9702, 9640, 4xxx, 9680, and 57xx Resolution Load the appropriate XDriver in the controller. If upgrading a controller such as going from a 9200 to a 9680, review the Third Party Interface Data Sheet to locate the re-compiled second generation Xdriver. NOTE: Not all XDrivers have been made available for second generation controllers, if the Xdriver is not available check with the third party vendor to see if a standard ModBus or BACnet plug in/upgrade is available for the device.

Issue Panel layout. Environment  ERG-UNIV-ENC-1 ERG-UNIV-ENC-2 Cause Need to determine panel layout for a project using the universal enclosures. Resolution From the data sheet... Medium Enclosure: Andover Continuum Power Supply and NetController, and up to two I/O modules or up to six I/O modules or CX 9702 SiteController.   Small Enclosure: Up to three I/O modules or CX 9702 SiteController or NetController (without a Power Supply) or VS-8-4 Video Switch Module. Both units are designed to hold two standard 12 VDC 7AH lead acid batteries (not provided). See the full data sheet here.

Issue Do extended logs have accurate entries for the spring and fall time change periods?   Environment CyberStation, all Continuum controllers, extended logs, controller logs. Cause What happens to extended log data during time changes? Resolution When the clocks are turned back, log data in the controllers will not be updated for the time interval of the change and therefore that data will not be collected by the extended logs. When the clocks are turned forward, log data in the controllers is logged twice for the time interval of the change and therefore that data is collected twice by the extended logs.   This occurs due to the fact that each log entry in the controller does not consist of a value and a timestamp. The timestamp we see in a report is calculated by the time of the last log entry (LastLogTime) in conjunction with the configured logging interval (LogIntervalSecs). This mathematical calculation saves memory in the controllers. Extended logging is the mechanism most sites use to store, and report on data that is in excess of the amount of data stored in a controller. The extended log engine automatically collects the controller log data before it is overwritten. An added benefit of using extended logging is that the data can be easily backed up via several strategies such as database backups and/or running extended log archiving applications. In the controllers, not only is the memory limited, but the data is stored in volatile RAM, so extended logging is a more robust and long term strategy of collecting and storing the data. Extended logs can be set up on any of the automatic log types (LogInstantaneous, LogAverage, LogMinimum, LogMaximum).  During a period when the clock is moved forward, (for example, 2:00am Sunday March 11, 2012 on the east coast of the US), reports may display timestamps that essentially never existed (in this example 2:00am to 2:59:59am). It is recommended that these entries are simply ignored or crossed out. The period when the clock is moved backward is more difficult, if it is critical that data be captured for the duplicated time. An example is Sunday November 4, 2012. At 2:00am on the east coast of the US the clock is set back one hour. This means that the times from 1:00am to 2:00am occur twice. However, extended log reports will only show one set of data for the reason described above. The reports will show the first 1:00am to 2:00am data; the second 1:00am to 2:00am data needs to be captured separately.  If point log data must be captured for the duplicated timeframe, additional point configuration and Plain English (PE) programming must be used to capture and timestamp the realtime data values for the duplicated timeframe. This involves creating a numeric with a manual log  for each critical point which mirrors the live data value of the affected InfinityInputs, InfinityOutputs and InfinityNumerics. In addition, an InfinityDatetime point with a manual log must be created, one in each controller for each different loginterval of the points being mirrored in that controller. The PE program(s) capturing the point values will write the controller's date system variable to this InfinityDatetime at the same time it writes the live point value, thereby creating a timestamp that will be used for reporting. The last step will be writing the mirrored points and their corresponding timestamps to a file on disk and then printing and/or backing up that file for redundancy.  Click here to download a zip file containing sample dump files and a readme. This is an example of one way to accomplish the above data capture. 

Issue Can not find Controller Web Server documentation on the web sites. Product Line Andover Continuum Environment Continuum Custom Web Server pages Infinity Web Server Cause Unable to find Continuum Web Server documentation. Resolution The attached Web Server chapter is extracted from a Plain English programming guide.  The Infinity Web Server User Guide is also relevant to Continuum. Also an example program can be seen in How to create custom web pages in the CX controller using Plain English.

Issue Distinguishing whether an xDriver-enabled commport on a controller is set for Modbus RTU or Modbus TCP/IP. Environment CX9900, CX9940 CX9680 bCX4040 Cause How does one know if the xDriver-enabled commport on a controller is for Modbus RTU or Modbus TCP/IP? Resolution Open the controller editor and go to the Options tab. At a minimum the Modbus RTU XDriver, like all Xdrivers, requires Bit 0 for the commport be Xdriver enabled. The most common example would look like this: Xdrvr Commx: 00000001(####). In the above example x = commport number. The four digit number in parentheses indicates whether an Xdriver file is loaded into the port. If it is 0000 then no Xdriver file is loaded into the port. A number such as 4767 corresponds to "Xdriver Valid" line at the end xdriver XDR file. You can edit the XDR file with a text editor and go to the bottom to see this.   In addition to Bit 0 being enabled for the commport, the Modbus TCP/IP Xdriver requires Bit 3 to be Xdriver enabled.  A common example of this would look like this: Xdrvr Commx: 00000009(####). The 00000009 is in hexadecimal format -  converting this to an 8-bit binary number you get 00001001. The furthest right bit is Bit 0 and the 4th from the right is Bit 3. Both are set to 1 which means they are Xdriver enabled. For a further explanation see page 15 of the linked Modbus TCP/IP Xdriver User Guide.   Note: Since Bit 0 is enabled in both of the above examples, the Modbus RTU Xdriver will work on either. But only the second example will load the Modbus TCP/IP Xdriver.      

Issue Where can I find documentation and network architecture diagrams for the Building Analytics service? Product Line EcoStruxure Building Analytics Environment Building Analytics Cause Users require access to product documentation and network architecture information to support: Deployment Configuration Troubleshooting Resolution Documentation and diagrams for Building Analytics are available through the following resources: 📂 Schneider Electric Download Center Access product manuals, guides, and technical documentation. Visit the Download Center 🗺️ Network Architecture Diagrams A diagram illustrating typical Building Analytics network architectures is available: Building Analytics Network Architecture PDF

Issue An end user has requested guidance for their IT department on how to secure a Building Automation System (BAS) effectively. Product Line Andover Continuum, EcoStruxure Building Activate, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Building Automation Systems (BAS) IT/OT Network Infrastructure Cybersecurity Best Practices Cause With the increasing convergence of IT and OT systems, securing Building Automation Systems has become critical. Customers are seeking best practices to ensure their systems are protected from cybersecurity threats and vulnerabilities. Resolution To assist with securing your Building Automation System, Schneider Electric provides a comprehensive white paper authored by the Buildings BU IT Security Group. 📄 Download the white paper here: Best Practices for Securing an IBMS (PDF) This document outlines: Key cybersecurity principles for Building Automation Systems Network segmentation and access control strategies Secure configuration and hardening guidelines Monitoring and incident response recommendations Compliance with industry standards (e.g., IEC 62443, ISO/IEC 27001) 🔍 Additional Resources Schneider Electric Cybersecurity Solutions Scheider Electric Cybersecurity Support Portal IT System Planning Guide - EcoStruxure Building Management EcoStruxure Building Operation Webhelp

Issue Need to verify whether specific network ports are open, as certain ports may be blocked. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment TCP/IP Communication Command Prompt Telnet Command Cause Suspected network port blockage affecting communication between devices or applications. Resolution You can check if a port is open using the Telnet command in Command Prompt. ⚠️ Note: Telnet uses the TCP protocol only. It cannot be used to test UDP connectivity. 📌 Command Syntax: telnet [domainname or IP] [port] [domainname or IP] – The server's domain name or IP address. [port] – The port number the server application is listening on. 🧪 Examples: telnet 192.168.0.20 9001 → Closed port: Displays a "connect failed" message.   telnet 192.168.0.20 9003 → Open port: Displays a blank screen.   🚪 To Exit Telnet Session: Press Ctrl + ] Type quit and press Enter. 📝 Note: Telnet may be disabled by default on some machines. Refer to Microsoft's documentation for instructions on enabling Telnet.

Issue How do I use a Plain English program to unlock a list of doors by toggling a switch? Product Line Andover Continuum Environment NC2 ACX Plain English Cause Customer request of a sample Plain English program to unlock a list of doors by toggling a switch. Resolution This sample program is provided as a proof of concept only and is not intended as a complete solution but rather as a general guideline. Significant modifications may be required to adapt the sample program to an acceptable solution per local site requirements. The sample program as written works with a "maintain position" toggle switch, if site is using a "momentary" switch then the program will need modifications. Sample PE Program in PE Editor   See attached text file   

Issue Start up of Continuum Workstation sees the below error. The Continuum Workstation may continue to start up if the OK button is pressed or may crash.   ContinuumServer.exe error An error occurred during initialization of Continuum Shared Memory by "ContinuumServer.exe". Please restart your system. If this problem persists, please contact technical support. Product Line Andover Continuum Environment Continuum v2.0 SP1 A Windows 32-bit Operating System Cause Beginning with the Andover Continuum 2.0 SP1 Release, Continuum applications now take advantage of the upper memory address space that is available natively on 64-bit Operating Systems (OSs). In order to access these memory addresses on 32-bit OSs, you must reconfigure your 32-bit OS to support applications that are Large Address Aware (LAA).  Resolution Enabled Large Address Aware (LAA). A Windows batch file is included as part of the Continuum 2.0 SP1 release that allows you to reconfigure your 32-bit OS to support applications that are LAA. You will need to ensure that Windows Firewall and Windows Defender are turned off and then run the "laa_update.bat" batch file as an administrator from the installation CD or zip folder.  See page 19 of the Cyberstation v2.0 SP1 Installation Guide for further details.

Issue i2 controllers randomly go offline then back online 10 minutes later. During this period of showing as offline, all points under the i2 controller can be viewed. Environment Continuum i2xxx Controllers Netcontroller II (CX9680) Cause After an i2 controller goes offline on a noisy Infinet, the Netcontroller II can miss receiving the reconfig of the i2 controller coming back online. It fails to see the i2 controller come back online but still continues passing requests down to it and receiving responses. After 10 minutes of not receiving the token, the i2 controller announces that it is on the bus. At this point the Netcontroller II gets the controller online message and the network reconfigures again bringing in this controller to the token pass. Resolution This has been fixed in a new build of the Netcontroller II v2.100031 which can be found at the link below. Netcontroller II v2.100031

Issue Upgraded CX9200 chips and not able to load Bacnet PTP xdriver Environment Continuum Cyberstation CX 9200 Bacnet Xdriver Cause Upgraded chips on CX9200 and cannot load the Bacnet PTP xdriver. Resolution Use the latest Bacnet PTP xdriver version BacnetPTP1.00001.xdr

Issue Need to download the XIF and NXE files for a SVEA Lon I/O Module DR-N-3D1M (0-10V) module, but having difficulty locating these files on the Extranet. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment SVEA XIF NXE Cause The difficulty in locating these files, is due to them being identified by their article number, in this case DR-N 3DIM. This number was used when these were classified as the SVEA devices. The Schneider version is now known as MTN881001, and not DR-N 3DIM. Resolution The Schneider Electric (MTN881001) files are located on The Exchange Download Center Download the XIF / NXE files for the SE MN881001 Download the XIF / NXE files for the SVEA DR-N 3DIM Note: It appears that although these devices are both classified as Lon I/O Module 1-10V, the XIF / NXE files are different.

Issue Enabling XDriver on the first generation of controllers, 9200, 9400, 9940, 9900 including the enabling of TCP/IP Product Line Andover Continuum Environment Older Continuum sites Cause Connectivity to third Party devices using the old NCI or First Generation Controllers requires an updated file. Resolution For 1st generation controllers, a .upd file is needed to turn on the bit for the Comm port. There is 1 bit per port to enable X Driver then a second bit to enable IP X Driver support required for the Modbus TCP/IP driver. The same principle applies to the generation1, 9200, 9400 controllers.   These controllers have flash memory just for things like the Serial number, model num, & X Driver settings, even though the controllers have EEPROM's for the firmware   As far as loading these drivers using hyperterminal, apart from firmware, one can load the X Driver file/ code through hyperterminal if required, but easier to do through Cyber'.   These files which enable the Xdriver for the Comm port, and TCP/IP are available by filling out the Driver Request Form, then they will be emailed directly to the customer from the factory in U.S.   X Driver list (Search for 'Third Party Driver List') and Order Forms (Search for 'xdriver order form') are located on the Exchange Download site  Difference between first and second generation controllers, visit What is the difference between 1st and 2nd Generation X Drivers. For information on Physical Ports, visit What controller ports and physical standards are supported by the Modbus X Drivers?  For Second Generation Controllers, visit How to order a controller with or upgrade a controller to have XDriver support.

Issue What X Drivers are available? Environment All Continuum controllers that support X Drivers (XDrivers) 3rd Party interfaces Cause How to find out what standard X Drivers are available to integrate with Continuum controllers. Resolution The Third Party Communicates Interface and Protocol Brochure can be found on The Exchange Download Center that lists all available X Drivers and product compatibility. Also all of these listed drivers are available for download from The Exchange Download Center here for use on X Driver enabled controllers. Should a new driver development be required, or other special interface; then you can contact the team that develop X Drivers: Adam.Summers@Schneider-Electric.com You will need to provide protocol details if you require a quotation.

Issue When setting up a Video Server the option for Pelco Type 2 (Endura) can not be selected. Environment Continuum V1.91 and above. See the Video Compatibility matrix for supported Pelco Endura products on the various Continuum versions, link: Video Matrix link Cause Continuum requires the security key to be enabled for Endura video to allow this option to be available. Resolution The Endura option cannot be purchased from the Factory.  In order to obtain the Endura option you must contact our Upgrades department. The upgrade part number is: UPG-ADD-ENDURA You can reach Upgrades by email at upgrades.continuum@schneider-electric.com Note: for testing purposes a Single User may be run in Demo mode for a few hours which will allow the Endura option to be selected.

Issue On the extranet site, there are two .zip files (SNMP+V1.0+MIBs.zip and SNMP+v2C+MIBs.zip). What is the difference? Environment SNMP Alarming Cause Not sure which file to use.   Resolution On The Exchange Download Center, there are two .zip files (SNMP MIBs v1.0 and SNMP MIBs v2C). The choice between the above files will likely be dictated by the site IT Department, based on their Network Management System. The V1.0 and V2C is the version of the SNMP protocol and is independent of the Continuum controller model and version.  Here's some background information on the protocol versions: http://en.wikipedia.org/wiki/Simple_Network_Management_Protocol#SNMPv1_.26_SNMPv2c_interoperability  

Issue Where is the information on LVIS Display/Screen Environment Lon Bacnet Loytec LVIS L-VIS L-VIS Touch Panel for BACnet networks   Cause Information on Loytec L-VIS Resolution The L-VIS from Loytec uses bacnet MSTP or LON. See Product Announcement - LonWorks and BACnet Touch Panels release for more information. All support for this product is via Loytec

Issue Where is the download for the LonWorks Xdriver file located? Environment cx99xx cx96xx Cause The LonWorks Xdriver file is not located under the Drivers\LonWorks folder on the Buildings Business Extranet where the LonWorks documentation is located. Resolution The LonWorks XDriver, for both Generation 1 and Generation 2 controllers, is hidden under the Standard Protocols heading. Download the LonWorks Xdriver from The Exchange Download Center.

Issue What are all of the Key and Reserved works used in Plain English and object naming? Environment Names and Alias used in Plain English programming and object creation. Cause Keyword list required. Resolution Reserved Words are split into different types: Statements (used in Plain English) Functions Operators Local Variables System Variables System Constants A full list of all reserved and keywords are in the Plain English Language Reference, see Chapter 7: Keywords also Appendix B: Reserved Words.