Issue Do all b3 and i2 Controllers support  all PE commands Environment b3 i2 Controllers String Trig Cause Some PE commands can not be used on some b3 or i2 controllers Resolution The following Plain English system functions are not supported in the i2885, i2885-V, and i2887(L) controllers: (b3885,b3885-V, and b3887(L) controllers) ACOS, ARCCOSINE, ARCSINE, ARCTANGENT, ARCTANGENT2, ASC, ASIN, ATAN, ATAN2, CEILING, CHR, CLOSELIST, COS, COSINE, EXP, EXPONENTIAL, FACT, FACTORIAL, FIRST, FLOOR, GETOBJECT, LAST, LEFT, LEN, LENGTH, LN, LOG, MID, NUM_TO_STR, OPENLIST RANDOM, RIGHT, RND, ROUND, SD, SEARCH, SIN, SINE, STANDARD_DEVIATION, STR_TO_DATE, STR_TO_NUM, STR_TO_TIME, STRINGFILL TAB, TAN, TANGENT, VAL See - b3 technical data - i2 technical data - PE Programming guide

Issue If there is an online selection tool for all the HVAC sensors (room temperature sensors, duct pressure sensors, etc.) Environment All Schneider Electric Buildings product lines Cause Since Schneider Electric manufactures a huge amount of sensors for different product lines. Sometimes it takes a bit of time to search for the right sensor. Therefore, Schneider Electric developed an online selection tool to help customer pick the right sensors. Resolution Click here to go direct to the online HVAC sensors selection tool. Select the desired features of the sensor. All sensors match the requirements will be displayed on the right. Datasheets can be accessed by clicking on the image or the part number. NOTE: the listed sensors may not be available in some region. Please contact the local sales or Support team to confirm the information.

Issue Is an Xdriver (X-Driver) needed for OPC integration? Product Line Andover Continuum Environment Continuum CX(99xx) Cause OPC server requirements Resolution An Xdriver is not needed to operate the OPC Server. Link to OPC Server Datasheet Link to OPC Server Software

Issue A database update from 1.94 to 1.94 SP1 will generate an Installation error [Microsoft][ODBC SQL Server Driver][SQL Server Implicit conversion from data type datetime to int is not allowed Product Line Andover Continuum Environment Continuum Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause A column in the db doesn't get converted properly. The SQL Server Implicit conversion from data type 'datetime' to 'int' is not allowed. The CONVERT function has to be used to run this query contained in the hotfix. Resolution 1. To correct this issue apply the following hotfix AFTER installing 1.94 SP1 but BEFORE running the database update 2.  Locate the hotfix on Exchange using the following link:  https://ecobuilding.schneider-electric.com/search#keyword/14191/tab/documents 3.  Find the item entitled:  "Error when Updating the Continuum DB while Upgrading to CyberStation 1.94 SP1 - TPA-CONT-13-0003.00" 4. Select download and read the release notes and install the hotfix Upgrading to CyberStation 1.94 SP1 - TPA-CONT-13-0003.00  

Issue Receiving Large Incorrect numbers in the log viewer. Environment Continuum 1.9X Windows XP Netcontroller II 9680 Cause NetController II needs updates. Resolution Go to: The Exchange Download the latest  NetController II  Flash. Edit the controller. Update OS Reload the controller.

Issue Can I add a NC2 9680 controller to Continuum 1.74 Environment Continuum 1.74 CX 9680 NC2 Cause CX 9680 compatibility with Continuum 1.74 Resolution Controller NC2 9680 is supported on Continuum Cyberstation with 1.74 service pack 2 Go to the Buildings Exchange Extranet Download and install SP2 for each Continuum workstation on site. Follow the directions in the readme file located in the service pack.

Issue What Techniques can be used to troubleshoot Modbus TCP/IP X Driver? Product Line Andover Continuum Environment Continuum Modbus TCP/IP X Driver Cause Advice/ tips required to help isolate & determine Modbus IP communications problems. Resolution The first thing to check is that you are using the latest release of the driver and manual, also that it is the correct one for the controller model you are using, currently V2.00002 for the 1st Generation controllers (e.g. Netcontroller CX9900 etc) and V2.00018 for the 2nd Generation controllers (e.g. Netcontroller II and bCX1). Download Modbus TCP/IP xDriver. Ensure you are using only 1 XDriver for all your Modbus IP comms, if say you are using Comm1 as your X Driver enabled port then all of the Modbus IP points must be under Comm1, you cannot have 2 X Driver ports loaded with this X Driver (See Can multiple Modbus TCP/IP XDrivers be installed on a single 2nd Generation NetController?). The following points should be checked with reference to the Modbus TCP/IP X Driver Manual downloaded with the software: Set the X Driver accordingly for Client or Server mode (Client mode and will be polling the 3rd party devices, server mode responds to requests for data). Check that your Configuration point has been setup correctly as a Infinity String and the parameters are correct for the mode you are using. For Client mode check that Param 1 is set to a polling rate that the 3rd party devices can cope with also that Param 3 is long enough for the devices to respond between 20 and 60 seconds. Use Parameter 4 to enable the error logging in an appropriate date format, this will then put the errors into the String array behind this point, ensure you have set the log size to say 50, automatic log and the interval to be 0 (a semi automatic log See How to log data only when a point changes). This will then log the error in the string each time they occur, you can view these errors with a function that loops for the log size printing out each line to the Message Window, or put a number of lines of the error log array lines on a graphic as lines of text. Create a Remote Device Status point to monitor the state of the remotely connected Modbus IP servers, again this can be put on a graphic to show which devices are on/offline. By selectively disabling or removing some of the X Driver points you can limit the polling to certain devices, that way each device can be tested in turn. Another tool that can help debugging Modbus IP comms is Wireshark as it allows you to monitor the IP comms between the Client and the Servers. Check the correct addressing and function codes are used in the polls and that the servers are responding correctly. As per the Compatibility Matrix check that your NCII has a compatible firmware loaded for the Cyberstation software used (2.0x or 2.1x) In Client Mode, ensure the 3rd party system does not poll the driver too fast, see Typical data throughput rates for Modbus XDrivers. Ensure the Xdriver Objects (usually Numerics) have correct details within the Parameter Fields. An incorrectly formatted IP address can cause the Controller to Cold Start following a download. The quickest way to check the Parameters is to load the Controllers with all the objects apart from the Xdriver Configuration String, then create a listview with parameters 1 to 6.  

Issue What are the main differences between Continuum v1.94 SP1 and Continuum v2.0? Product Line Andover Continuum Environment Continuum v2.0 Cause Required a quick list of differences between the versions of Continuum to evaluate if a site upgrade to v2.0 was beneficial. Resolution The main features that Continuum v2.0 has over v1.94 are listed below. Microsoft Internet Explorer 10 32 bit support SQL Server 2012  Microsoft Internet Explorer 11 32 bit support Software licensing Support. See Software Licensing for Continuum 2.0 and StruxureWare Solution. Email SMTP Support. See SMTP Email Alarm Configuration in Continuum 2.0. Extended Custom Wiegand Card* (ACX Series Only). See Extended Custom Wiegand features available for ACX57xx controller released in V2.0. Support for new door attribute 'ValidAttempt' see New Door attribute 'Valid Attempt' added in Cyberstation 2.0 for more information. You can also find more details in the v2.0 Feature Blast. And further information on Continuum v2.0 with the links in Continuum 2.0 Product Announcement, Feature Blast, Compatibility Matrix and Installation Guides.

Issue A Controller with X Driver support has been loaded up with the M-Bus (or M Bus) X Driver and connected to a M-Bus to RS-232 converter (i.e. Westermo AD-01) but is not getting data from the M-Bus meter. Note: This is M-Bus (Meter Bus) and not Modbus which is a different protocol Environment bCX1 and Netcontroller II 2nd Generation controllers with X Driver port enabled MBus, M Bus, XDriver, X-Driver Cause Incorrect comm port settings for the M-Bus interface will stop correct communications to the M-Bus meters. Resolution DefaultMode = Xdriver Baud = Baud300 Parity = Even Stopbits   = StopBit1 Datalength = Databits8 Connect up and configure the system as detailed in the M-Bus manual as supplied (downloaded) with the M-Bus X Driver software. Unless specified otherwise in the manual for the specific 3rd party meter being used, set up the Comm port on the Controller with the above parameters: These settings should be entered and verified through the Command line, then printed back to verify they have been accepted.

Issue Do I need a LAN System Configuration for CFR implementation? Environment Cyberstation 1.7X, 1.8X, 1.9X Cause Do I need a LAN System Configuration for CFR implementation? Resolution The Standalone CyberStation configuration does not support the CFR Compliance Pack. For more information download the Continuum CFR Compliance documents below. Continuum CFR Compliance Pack - Life Sciences Solutions FDA Code of Federal Regulations 21 CFR Part 11

Issue Requirement for a demonstration license for the OPC Server to get an idea about how it functions and to demonstrate to potential customers. Environment Continuum OPC Server Cause Require demonstration license for the software. Resolution There is a one hour demonstration mode that the software goes into if there is no valid license found. This should provide enough time for demonstration purposes. When starting the application without a valid license the below dialog is displayed.   You can download the Continuum Controller OPC Server from the downloads website at this link.

Issue Is the Continuum Cyberstation a B-OWS (BACnet Operator Workstation)? Product Line Andover Continuum Environment Continuum Cyberstation BACnet Cause Can't find reference to Continuum Cyberstation being defined as a B-OWS. Resolution The Continuum Cyberstation is a B-OWS and complies with ANSI/ASHRAE standard 135-2004.  However, the Continuum Cyberstation has not been BTL tested, please see the Schneider Electric BTL Listing of Tested Products.    The following selection is taken from the Andover Continuum Family of User Interfaces document describing Continuum's Cyberstation capabilities. Native BACnet B-OWS CyberStation communicates with the BACnet devices using BACnet/IP in strict accordance with ANSI/ASHRAE standard 135-2004 and is designed to function as a BACnet Operator Workstation (B-OWS) and BACnet Broadcast Management Device (BBMD). The CyberStation can communicate to all Andover Continuum BACnet Devices as well as any third party BACnet Device on the BACnet network.

Issue Is a controller shipped from the factory with the latest firmware revision supported in older versions of Continuum? Environment Continuum 1.xx Cause Running an older version of Continuum (1.74sp2) and bought a new Netcontroller II, that has 2.10000xx for a firmware version. Resolution Please refer to the Continuum Compatibility Matrix for Continuum versions and Controller firmware versions. Andover Continuum Software and Firmware Compatibility Matrix Versions 1.94 SP1 Example: Running Continuum 1.74sp2, first Continuum version to support the Netcontroller II 9680. Bought a new Netcontroller II 9680 and the current version of Continuum available is 1.92. The firmware installed on the controller (2.10000xx) is the latest available, and for older installations of Continuum you would need to down rev the firmware a version support per the Continuum Compatibility Matrix and in the instance of 1.74sp2 that would be 2.00000xx.

Issue Is Windows 7 supported in CyberStation? Environment CyberStation Cause Is Windows 7 supported in CyberStation? Resolution Versions of Continuum Cyberstation prior to 1.93 do not support Windows 7. See our Continuum Compatibility Matrix for supported OS and version Windows 7 is supported starting in Cyberstation v1.93

Issue Virtualization using VMWare, Virtual Server or other products is useful when deploying applications Is virtualization supported with Continuum?  Will Continuum work in a virtual environment?  Environment Continuum WMWare Virtual Server Windows XP Windows Vista Windows Server 2003 Windows Server 2008 Cause Continuum compatibility with Virtual Machines (virtualization - VMWare) Resolution VMWare VSphere 5.5 and 6.0 has now been qualified to work with Cyberstations and Web.Client in Continuum v2.0 and above. Note that this will require a software licence and that the virtual environment must comply with the minimum system requirements for Cyberstation and Web.Client Server. See the latest Continuum v2.0 Compatability Matrix for details.                                                         There have been reports from the field from engineers that  have used Continuum and SQL server with various virtual software not currently qualified. If there are any issues with this implementation with an unqualified solution, then it would be necessary to install Continuum on a supported configuration (see the Continuum Compatibility Matrix) prior to involving engineering to evaluate any problems. This solution has not been tested and is outside of what we currently support. These include: Other VMWare environments, Microsoft Virtual PC (HyperV), Citrix, Windows 7 XP Emulation, etc. Marathon Redundant SQL Servers is a very specific solution which does use virtual machine. This is an isolated case and does not apply to standard implementations of Continuum or Webclient.

Issue Internet Explorer 9 will not work with webClient Product Line Andover Continuum Environment webClient Windows 7 Windows Server 2003 Windows Server 2008 Cause Internet Explorer 9 isn't compatible with webclient 1.93 and below Resolution Certain versions of webclient are compatible with specific versions of Internet Explorer. Download Andover Continuum Software and Firmware Compatibility Matrix from The Exchange Download Center. Internet Explorer 9 has not been tested against webclient 1.93 or below, but there have been reports that it will not work with webpinpoint graphics. Two options to resolve: Downgrade Internet Explorer according to the Continuum compatibility matrix. web.Client v1.94 SP1 - Software (Release Date: 2013-Jul-14) for webClient 1.94 includes support for Internet Explorer 9.  

Issue Installation cable requirements Product Line Andover Continuum Environment Continuum Cause Need to specify a cable type for a site Resolution Installation cables have to be chosen taking in to account the local regulations and legislation, the installation environment and the electrical requirements. The Continuum specifications give the electrical requirements. For this reason actual cable types, makes or Belden numbers can not be stated, only as helpful guidance as a cable that may meet the electrical requirements only. BACNET MSTP - See What cable type should be used for BACnet MS/TP communications?. INFINET - See What cable type should be used for Continuum Infinet bus communications. CARD READER - See the manufacturers requirements for the cables, also Maximum Cable Length Between ACX and Card reader. ANALOGUE and DIGITAL INPUTS - See the relevant Continuum specification eg. I/O Modules. See Andover Continuum IO System Reference (especially note screening and grounding requirements) I/O MODULE (RS-485 & LON) - See the relevant Continuum specification eg. I/O Modules See Andover Continuum IO System Reference For ETHERNET, LON, MODBUS RTU, OTHER THIRD PARTY BUS/NETWORK - See the relevant external documents

Issue In what positions can Continuum controllers be mounted? Environment Continuum Product Line Cause Not sure if the controllers can be mounted on both the vertical and horizontal plane. Resolution There may be some specific mounting instructions for some of the controllers, but for the most part they can be mounted in any direction in the vertical plane. Controllers with relays should not be mounted with the edge the outputs are on facing down. Consult the installation instructions (found here) for each controller for any specific mounting requirements.

Issue An Infinity Program object appears In the Occupancy Point field of the schedule editor. When an attempt is made to browse, select apply the proper occupancy numeric, the same Infinity Program object reference reappears. Environment Continuum 1.74 Schedules Occupancy Point Database Cause This behavior was related to the behavior described in TPA-BOST-08-0005.00.  Resolution Apply the Cyber 1.74 SP2 HotFix For TPA-BOST-08-0005.00.

Issue What is the process to replace a CX9400 with a CX9680 NC2? Product Line Andover Continuum Environment Upgrading a CX9200, CX9400 Eclipse, CX9900, CX9940 to a NCII Netcontroller. CMX9924. Model Number, Type change. Cause Where can I get the process to upgrade my obsolete CX controller. Resolution Cyberstation V1.74 SP2 or above is required to support the upgrading process of a CX9200, CX9900 and CX9940 up to a Netcontroller 2. The upgrade process for this is detailed in Appendix B or the NetController II Operating and Technical Reference Guide. For the CX9400 Eclipse controller they require a minimum of V1.91 to support the upgrade. For the older versions of Cyberstation that do not support direct upgrading of a model number, you will need to bring the Netcontroller II on line as a new controller, then in offline editing copy /paste (or Drag /Drop) all objects over to the Netcontroller II. Then go online and fully reload the Netcontroller II and any connected Infinet controllers. The old controller can then be deleted from the system. The objects could also be copied over using edited ASCII dump files if you prefer that method, but either way you may still have to re-animate your Pinpoint graphics unless you upgrade to a version that supports the Netcontroller II replacement. NOTE ACC-LON RS-485 and ACC-LON FTT-10A protocol options A CX9900 may be labeled CPU-8M and a CX9940 labeled CPU-4M. Later CX99 models may have FT added, eg. CPU-8M-FT When replacing a CX9900 or CX9940 it is vital to know if it requires an RS485 or FTT10 IOU module port (if this port is being used) as this CANNOT be modified on site. See article titled No response from I/O module when learning in an IOU This process cannot be used to upgrade the CMX9924 controllers.  The available range of Netcontroller II controllers available has recently been reduced, see PA-00535 "Andover Continuum Offer Optimization"