Issue While Continuum controllers and EcoStruxure controllers do not utilize Power over Ethernet (POE), can plugging in a Continuum or EcoStruxure controller into a POE switch damage either the POE port or the controller? Product Line Andover Continuum, EcoStruxure Building Operation Environment PoE Ethernet Cause Controllers must be installed on a subnet served by a POE switch. Resolution According to the IEEE standard, a POE switch shall determine if the connected device is POE capable before turning on the power. The detection if a connected unit is POE capable is done by measuring the resistance between the pair #2 - #3 and pairs #1 - #4. On a POE capable unit the resistance is 25kohm, with some tolerance. If it is lower or higher it is not considered to be POE capable. As there are no Continuum or EcoStruxure ethernet controllers that apply a 25K ohm load, a properly functioning switch port will not enable PoE power and the device will not be damaged. Information on the PoE standard can be found in the following document. The Fundamentals of Power Over Ethernet (PoE)

Issue WebClient login screen has the TAC webClient background, but no login fields   Product Line Andover Continuum Environment webClient Cause This typically happens when webclient has been installed prior to IIS, so .Net framework does not get registered with IIS. Resolution  The resolution is to run the regiis.exe command as follows: For Windows 2000 Professional it is: "c:\WinNT\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i" "c:\WinNT\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i" For Windows XP Professional, Windows Server 2003 it is: "c:\windows\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i" "c:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i" Once this command is run the normal login prompt will be presented.

Issue There is a need to know if Continuum and/or EcoStruxure BACnet support NAT. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum EcoStruxure BACnet BBMD NAT Cause Many sites use NAT for security purposes.  Resolution NAT traversal is not supported in BBMD implementations (Continuum or EcoStruxure). It is an optional feature that has not been implemented. Requests to add this feature should be directed to Product Marketing to include on the backlog for prioritization. Related Continuum article: Can Continuum operate over a NAT Ethernet connection? Ashrae information: http://www.bacnet.org/Addenda/Add-135-2008o.pdf

Issue What is the Network ID-UDP Setting required for and does this need to be changed when commissioning a new BACnet Continuum controller? Product Line Andover Continuum Environment bCX4040 bCX4000 Cause Require information on the Continuum BACnet Network setting (physical layer). Resolution Each network segment in a BACnet network is assigned a unique integer as an identifier for ease of routing packets between these networks. For more information see Effect on a BACnet network if the Network Id - UDP setting in bCX40x0 have been set to different values   BACnet Network ID-UDP Setting This defines the ID number of the BACnet/IP network on which this controller resides. When creating a Continuum BACnet controller the default UDP Net ID is set to 1. This setting would need to be the same for all BACnet controllers that want to communicate with each other across the network.   Why would you want to change it? You may have a site for example that already has a BACnet network running on the ethernet and not want to communicate on the same BACnet UDP Net Id as their BACnet devices do. In this case you could change the UDP Net Id for your BACnet communications but it needs to be the same for all of your BACnet devices since the routing tables in the controllers would need to know which UDP Net Id to route to. If you changed the UDP Net Id to 2 then all controllers would need to be set to 2 to make sure they were able to communicate efficiently with each other.

Issue webClient schedules getting error 'request for permission of type' system.security.permissions Product Line Andover Continuum Environment webClient Cause Require to run the Caspol commands. Resolution Run the Caspol commands, here is a batch file that runs these commands without typing them in. Click Here to download the batch file   Rename the caspolwebclient.txt to .bat Run the batch file at each WS that needs to access webclient schedules. Below are the actual commands: The following command will add FullTrust to the Internet_Zone in DotNet 2.0: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Internet_Zone -zone InterNet FullTrust -name FullTrust The following command will add FullTrust to the Trusted_Zone in DotNet 2.0: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Trusted_Zone -zone Trusted FullTrust -name FullTrust This will result in output like: The operation you are performing will alter security policy. Are you sure you want to perform this operation? (yes/no) Then select Y and you should see: Added union code group with "-zone" membership condition to the Machine level. Success In some configurations, you may need to add the IIS computer into Internet Explorer as a trusted site for each browser. Internet Explorer > Internet Options > Security > Click trusted Sites > Click Sites Type in http://yourservername/webclient and click Add (Ex. http://tacweb/webclient) Deselect the checkbox for Require server verification (https:) for all sites in this zone. Click OK and Ok Close Internet Explorer and access webclient See Removal of MS KB2858725 Dot Net 4.5.1 causes issues with Web Servers IIS Functions if this is for 1.94 SP1 -  Uninstalling KB2858725 * It may be necessary to give specific permissions in the registry if you are seeing system.permissions.UIPermission, mscorlib Make a backup of the From Windows, Start> Run> Regedt32.exe Expand the hives(folders) to HKEY_CLASSES_ROOT\CLSID\{00B01B2E-B1FE-33A6-AD40-57DE8358DC7D}\InprocServer32\2.0.0.0 Right Click on 2.0.0.0 and select export, name the file and save. (This file can be used to restore the original settings of this branch)  Right click on this folder again and select permissions, select Users and add Full Control See below for snapshots

Issue Can TAC BACnet (Viconics) thermostats have identical names or device ids within sub networks using their default names? Product Line Andover Continuum, EcoStruxure Building Operation Environment Viconic BACnet Thermostats BACnet BCX B4 MSTP Cause Viconic stats need a unique address and unique name across the entire BACnet network. Resolution BACnet Viconics thermostats must have a unique name and device id across the entire BACnet network. The BACnet data link layer has two key parameters: the device object name and the device object ID. The device object name must be unique from any other BACnet device object name on the BACnet network (i.e. not just the MS/TP sub-network). Typically this question comes up because a thermostat will not come online. Run an acctrace during the Find and you will probably see a duplicate MAC address. Once you have given unique names and comm addresses to each of the thermostats on the entire BACnet network, these devices should communicate and come online properly. Each of the Viconic stats are given a unique name that includes the address (once it has been made unique) To change the communication address: Hold down the menu button until the option for menu comes up Answer the questions for the various options and eventually you will be brought to change comm address. Change Comm address, select Yes and then use the up or down arrows to give this MSTP Viconic stat a unique address. There is a Configuration Tool to access and edit the name and device id unique naming scheme. Click here for ViconicsConfigurationTool.zip. Installing and using the Viconics Configuration Tool on a Windows Laptop  You will need a serial adapter connection to tie into the MSTP bus that the thermostat(s) are connected to Select the Viconics folder > ViconicsConfigurationTool.zip You can install this ZIP file in any directory you wish, but the bacdocm.ini file must be installed on your C:\Windows directory. Use the bacdocm.ini file to configure your network settings at the Configurator Tool level. You can set the MAC address of your tool, the baud rate of your connection (max 38400 - limited by the RS-232 to RS485 port and Windows) etc. The "Our Device Instance" value represents the MAC address of the tool which must be unique on the MSTP network. Also the "MaxMaster" value must be set to a higher value than the highest MAC value on the MSTP network. You can edit this INI file to modify your settings OR you can modify the settings by going though the BACdoor Configuration Tool. Once you launch the Configuration Tool, you'll notice a white applet appearing at the right bottom of your screen. That is the BACdoor MSTP sniffer that actually looks for devices and objects. If you click on that icon, and select the "Configure" tab, a configuration window will be displayed. Select the baud rate at which you want to communicate with your device. This BACdoor configuration does the same thing as changing the BACDOCM.ini file (if properly located in C\Windows). Launch the Configurator Tool application. It automatically looks for devices on that network (at the baud rate set in the bacdocm.ini file or in the BACdoor Configuration window). If no device is detected an error message will pop-up after 1-2 minutes. All discovered devices will show up in the "Device List" you have to "Connect to device" in order to list all the objects of that device. After you changed the Baud Rate, you have to click on the "Apply changes" button. Don't forget that the max speed of this tool is 38400. For the first connection, you need to power cycle the thermostat (if it was running at 76800 previously) so that it auto-detects the 38.4 network. Once you set it to 76.8, you can not connect to that thermostat with the tool because of that 38.4 limitation. Also this tool does not support Read Multiple Property so it reads every property of every object one at a time. In its default mode of operation, the device will automatically match its baud rate to the baud rate of the network. Automatic baud rate detection will occur when the MS/TP communication port is initialized (on power up). If the network speed is changed, the device will keep listening at the previously detected speed for 10 minutes before resuming auto-bauding. Re-powering the devices will force right away auto-bauding. SE7xxx series requires the tool. The SE8xxx series does not as access is available through the menu on the device.

Issue What is enabled on a Continuum Security Key? Product Line Andover Continuum Environment Continuum Security Key Cause There's a need to know what version of Continuum is enabled on the key. Resolution The supported version of the keys and what options are available on the key can be verified by doing the following using Microsoft Excel on a Workstation with Continuum and the key installed: Open MS Excel Select Insert> Object Select SecurityKeyreader Control and then Ok You will see an object inserted into the spreadsheet with a list of products on the left and options on the right. Example: Serial Number 1016019 Options Number of Points -1 Adv.WebServerEnable Number of Personnel -1 EpiSuiteEnabled Platform Lan(Multi) OPTxtLoggingEnabled Type Prog.Intg. PESourceCntlEnabled Max Version 1.79 Global 1 0 Global 2 0 Global 3 0 Global 4 0 Windows 7 64 bit will not support the MMC.exe option (mentioned below)   Use the command       mmc.exe /32     This will allow the activex snap-in to be added and will work on a 64 bit PC   ActiveX controls in Excel 32 bit are not exposed by default. Use the following Excel spreadsheet (zipped) to read the security key instead. (Excel must be installed and must be on a 32 bit PC(64 bit shows this as blank) Security Key Reader Excel File You may be prompted to enable the activex control Excel 2003 - The application is about to initialize ActiveX controls that might be unsafe. If you trust this document, select Yes and the control will be initialized. Excel 2007/2010 - Notice the Security Warning below the Toolbar                                   Click options                                   Select Enable this content Upgrading a key requires a call to repair (978-975-9464) for a cookie to update the key. In order to install the cookie, you must be use the program, CyberKeyWriter2.exe to enter the new key which is on every Cyber CD in the Continuum\bin folder.  Note: Also see Accessing Continuum Security Key information using MMC instead of Excel that describes another method to see this information using MMC.

Issue You get an error, "Unable to load the .Net control for this page." when trying to open a schedule in WebClient. Product Line Andover Continuum Environment webClient Cause The problem is that the .Net zone permissions are not set on the browser machines. Resolution Depending on the revision of the WebClient the procedure for correcting this on the browsing machines is different. If you are running WebClient version 1.73 or below then refer to the WebClient installation guide on setting the .Net zone permissions. If you are running WebClient version 1.74 or higher, which uses .Net 2.0, the procedure is different. Below is the procedure that will need to be performed on the browser machines at the command prompt to set the .Net Zone Permissions for .Net 2.0. The following command will add FullTrust to the Internet_Zone in DotNet 2.0: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Internet_Zone -zone InterNet FullTrust -name FullTrust The following command will add FullTrust to the Trusted_Zone in DotNet 2.0 C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Trusted_Zone -zone Trusted FullTrust -name FullTrust This will result in output like: The operation you are performing will alter security policy. Are you sure you want to perform this operation? (yes/no) Then select Y and you should see: Added union code group with "-zone" membership condition to the Machine level. Success You should then be able to open the .Net 2.0 editors on your web.client browser machine. In some cases adding the webclient IIS PC to the trusted sites in the browser is needed Internet Explorer> Internet Options> Security> Click Trusted Sites> Click Sites Type in http://your server name/webclient and click Add (i.e your server name is specific to your install) Deselect the checkbox for 'Require server verification (https:) for all sites in this zone Click Ok, Ok Close explorer and access webclient schedules Note: Every browser PC that will be accessing schedules needs to have the caspol commands run on it. Download a batch file that can be run on each PC (Rename the .txt file to .bat and run at a DOS prompt  C:\> caspolwebclient.bat)   Note: When using 1.94 SP1 check the application pools .net version selected Name .Net Version ASP NET v4.0 4.0 ASP NET v4.0 Classic 4.0 Classic .NET AppPool 2.0 Default AppPool  2.0 WebClient  4.0 Note: If .net framework 4.5.x has recently been installed on browser PCs, see Webclient Cannot open .net editor with .NET Framework - 'There was an error trying to create the .NET control for this page'.

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 Services for assistance. Issue Is there a way to globally change the path of active animation controls so that each control does not have to be edited manually? Pinpoint graphics will be very slow to open if the image file is on a network drive that is no longer available. Product Line Andover Continuum Environment CyberStation Cause A method to make the change globally in one operation is required system the design does not provide a way to do it. Resolution As of version 1.94 Continuum does not provide a mechanism to globally change the path of image files in active animation controls in Pinpoint. This can be a problem when a large number of active animation controls have been created using a given path and the image files then need to be moved. If the image files must be moved, every effort should be made to retain the path that was used in the controls, otherwise the path to the files will have to be manually changed in each active control that references the path in the graphic panel. With the above said there is a way to go in the Graphic PIN file and change the path, it requires a hex editor such as HxD. Using a hex editor the path for a control like this Can be found and changed in the PIN file itself, like this... *** Warning *** Please note that the length of the new path string must be the same length (i.e. take up the same number of characters) as the original path string, otherwise the file may become corrupted. As an example the following cannot be used replacing C:\Program Files\Continuum\NewGraphicsFiles with E:\Graphics, but the following could replace C:\Program Files\Continuum\NewGraphicsFiles with E:\Program Files\Continuum\NewGraphicsFiles   Notes: If a system is upgraded (new PCs) or a network drive that contains the image files is no longer available, then the graphics can be very slow to open.

Issue Can Strings be used in all controller types? Product Line Andover Continuum, EcoStruxure Building Operation Environment All Continuum Controllers b3, i2 Controller (EcoStruxure Building Operation) Cause Some Controllers do not support strings Resolution The String class of object are supported in the following products: CX series (including all Netcontrollers), bCX series, CMX series, ACX series, i2 series (except i2885, i2887), BACnet series (except b3885, b3887), DCX 250, CyberStation.

Issue After 2000 backups an attempt to perform a backup to flash results in the error 'Flash backup for this controller has been disabled.' Product Line Andover Continuum Environment Continuum b3920 controller Continuum i2920 controller Cause Flash memory has a limited write count; Controllers implement a flash circuit breaker that trips after 2000 backup operations in order to protect the flash device from damage. Resolution (Applies to all b3 and i2 controllers) EcoStruxure Building Operation In EBO, a command has been added that will re-enable backup to flash after the circuit breaker has been tripped (2000 backups) From Workstation, in the object tree, right-click the i2/b3 device. From the context menu select, DEVICE->ENABLE BACKUP TO FLASH Andover Continuum From CyberStation command line set the ACCStatusBackup system variable of the device to ACCBackupEnable. NOTE: The flash circuit breaker CANNOT be reset from Script/Plain English.  This is by design as it was deemed too risky to allow resetting it programmatically.  A poorly written program could very quickly cause damage to the flash device.

Issue When opening a BACnet AnalogInput  from (the Blue) BACnet device side, the value of the object displays as 3 decimal digits by default. The format can be changed in the format field as desired, however when clicking the "Apply" button, an error prompt box pops up with the message "An attempt has been made to write a property defined as inaccessible through the BACnet  protocol write services". if the "Apply" buttonis clicked again, the error disappears and the format is been changed successfully. Product Line Andover Continuum Environment Continuum BACnet BCX1 B3s Cyberstation V2.02 and earlier. Cause Format is not a standard BACnet property, it is a Continuum attribute and when the format is changed Cyberstation sends a command to change the "present value" of the point in the controller. The present value of AnalogInput cannot be written so the error occurs. When clicking "apply" or "OK" for the second time Cyberstation only writes the attribute of the point in the database rather than the controller. Therefore we can get a successful change of format for AnalogInput by clicking "Apply" twice. For AnalogValue, the "present value" of  AnalogValue can be written in BACnet, so there is no error when changing the format of an AnalogValue. Resolution Ignore the error when making the change, click the "Apply" button twice after updating the "Format". Or upgrade to V2.03 where this issue has been resolved.

Issue Are 64-bit operating systems supported on the Andover Continuum product line? Product Line Andover Continuum Environment CyberStation webClient Cause Compatibility requirements for Andover Continuum with 64-bit operating systems Resolution Release 1.93 and earlier: For all machines with CyberStation or webClient software installed, only operating systems running in 32-bit environments are supported. 64-bit environments are not supported.  However, for the Database Server on a LAN system where no Cyberstation or webClient software is installed, a 64-bit version of Windows Server 2008 (SP2) or Windows Server 2008 R2 may be used on systems running V1.92 and above. These will also require Microsoft SQL 2008 running in 64-bit mode. Release 1.94 and later: Release 1.94 supports 64-bit Operating Systems, however, Microsoft recommends the 32-bit version of Office 2010 because it prevents potential compatibility issues with other 32-bit applications, specifically third-party add-ins that are available only for 32-bit operating systems. Please refer to the release notes for compatibility notes in specific versions.

Issue Which printers, signature pads, and capture devices are supported with the badging editor? Product Line Andover Continuum Environment Epi-Suite Epi-Builder Cause Determine which ImageWare systems (Epi-Suite or Epi-Builder) to use with the Continuum system. Resolution Continuum OEM's third-party badging software from Image Ware Systems are Epi-Suite and Epi-Builder. If your using Continuum version 1.8 and newer versions, Continuum uses the Epi-Builder version. For versions of Continuum 1.74 and prior, they use Epi-Suite as the badging editor. The hardware compatibility list for the Image Ware products can be found on their website. www.iwsinc.com Once on their website select Support/Customer Service/ either IWS Epi-Builder or IWS Epi-Suite. The page that is displayed after these selections you'll notice a link on the left-hand side of the page for Compatible Hardware. The lists for printers, capture devices, and signature pad readers can be displayed when clicking on the links for each. The peripherals can be found at: https://www.iwsinc.com/support/epi-suite-builder-hardware-compatibility/

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Introducing a previously commissioned Continuum IOU module such as an AC-1 to an Access Expert or Security Expert site can cause communication issues in the LON bus due to duplicated node id. Product Line Andover Continuum, Security Expert, Access Expert Environment Continuum AC-1 Continuum Net Controller Continuum Net Controller II Access Expert Controller Security Expert Controller Cause When IOU modules are commissioned in a Continuum system, the Net Controller assigns each module a Node ID, this is in addition to the LON Module ID that is unique to each module hardware, the purpose of the Node ID, is to decouple the identifier used by Continuum for communication from the specific piece of hardware, this in order to facilitate the replacement of a failed module without the need to change its Continuum identifier. The module stores the Node ID in nonvolatile memory so that it persists across power loss. If a Continuum IOU module is introduced to a LON network (Security Expert SP-AC1 or Access Expert AX-SSC) without clearing its Node ID, there is a risk of creating a duplicate Node ID condition that will prevent the LON network from operating properly. IMPORTANT This should not be an issue during the normal transition of Continuum site to Security Expert or Access Expert, as all the modules on the running LON bus should have unique Node IDs, this is only a problem when adding a module, or replacing a module with one that has been used before. Resolution In order to signal its presence on the LON network, each module will transmit on resetting its status network variable. If upon receiving this message, the Net Controller determines that the module is NOT in its local database, the controller will decommission the module by setting its Node ID to zero. Before introducing a Continuum IOU module that has been previously commissioned to the LON network of an SP-AC1 or SX-SSC controller, decommission the IOU module using the steps below: Attach the module to an empty Net Controller that is powered down with its battery removed. For a Net Controller II, in order to be absolutely sure that the Net Controller has an empty database, you may need to clear its backup in flash from a browser or by the use of the reset IP switch. See LL on how to use the controller's reset IP switch to clear its flash backup https://community.exchange.se.com/t5/Building-Automation-Knowledge/How-to-clear-the-controller-flash-backup-from-the-hardware-using/ta-p/5877 Power up the Net Controller Once the CPU led on the Net Controller starts blinking, press the 'Reset' button on the IOU module. Wait 30 seconds to make sure the decommissioning process has completed. Power down the Net Controller Remove the IOU module

Issue What is the limit of how many devices a BACnet controller can know about (Known devices) and what does that mean. Product Line Andover Continuum Environment BACnet bCX bCX4040 Cause More details required about Known devices Resolution The known device limit of a Continuum Ethernet level BACnet controller is 255 and for a B3 level MSTP controller it is 32. This limit means is if a controller needs to either subscribe to a COV from another controller or deliver alarms (Event notifications) to a workstation, that each one of these target devices is a known device. So, for example, if a b3 controller is subscribing to COV's from 30 other controllers and needs to deliver alarms to 3 WorkStations, it would require 33 known devices and the last request for a target device would fail. If a Controller is making 30 COV Subscriptions from one a single controller that would only count as 1 known device. This limit does not apply to the number of other controllers which a COV exporter can deliver COV data to. For example, if a controller had a global point (OAT) that 50 other controllers needed to subscribe to, this is allowed because each COV subscription has within it the target controller's address information and does not use the known device limit. There are two cautions that must be considered. Refer to What are the differences between Standard Continuum Import/Export and Continuum BACnet COV?. Each COV subscription in an exporting controller takes away user memory. Each subscription uses approximately 56 Bytes of user memory. So the limit of how many other devices can subscribe COV's in an individual controller is limited by free memory in the exporting controller. NOTE: To reset  the known devices following a change in the Controllers that will effect the number of known devices, the controller needs to be reloaded.

Issue When using the Modbus RTU and Modbus IP XDrivers it is important to determine which controller and port can support the electrical standards used by the 3rd party device. Product Line Andover Continuum Environment Continuum Netcontroller II and bCX1 controllers that have been XDriver enabled. XDriver, Modbus RTU, IP, Infilink, Infilink200, B-Link. RS-232, RS-485 JBUS Cause Controller ports and 3rd party devices come in various electrical standards (RS-232, RS-485, RS-422), which ports support the various standards? Resolution There are two Continuum Modbus XDrivers: Modbus RTU: This allows the connection of 3rd party Modbus RTU slaves via the serial data RS-232, RS-485 or RS-422 electrical standards. RS-232 is a point to point connection to 1 device, RS-485 & RS-422 support a bus topology for connection of multiple 3rd party devices. The Continuum controller will be the Modbus RTU Master and will poll the 3rd party device that must be a slave. The bCX1-CR controllers have 2 ports that can be configured for Modbus: Comm1 RS-232 Comm2 RS-232 or RS-485 port The Netcontroller II controllers support: Comm1 - RS-232 or RS-485 Comm2 - RS-485 Comm3 - RS-232 Comm4 - RS-422 The ACX57xx controllers support: Comm1 - RS-485 Notes An Infilink200 or B-Link may be used to convert RS-232 to RS-485 if required. The J Bus protocol is a subset of the Modbus protocol and so the Modbus XDriver is used for J Bus Systems. Modbus IP: The bCX1, ACX57xx and the Netcontroller II all support the Modbus IP protocol that connect via the Ethernet IP connection. This XDriver can be configured to support either Client or Server modes. Although the communication is physically via the Ethernet port, one of the Serial ports is required to be X Driver enabled to load the software, this serial port is then no longer available for other purposes. This XDriver requires Ethernet X Driver support to be enabled on the port. NOTE Netcontroller II and bCX1 can have an XDriver ENABLED on more than a one Comms port, however only one IP XDriver should be INSTALLED on each controller, also only one Modbus RTU XDriver should be INSTALLED on each controller. It is possible to INSTALL a Modbus RTU and a Modbus TCP/IP XDriver on a single controller, but it would be very easy to overload the controller, so this setup is only suitable for smaller networks. (note the difference between enabling XDriver support and Installing an XDriver) See Articles  Can multiple Modbus TCP/IP XDrivers be installed on a single 2nd Generation NetController? and BCX Controller can use Comm 1, Comm2, or both ports for Modbus RTU X-Driver  

Issue How to determine if SU (single-user), LAN, or WEBC (WebClient) license keys are required for your project. Product Line Andover Continuum Environment Continuum Cyberstation Continuum WebClient Cause The Engineer is unsure as to which Continuum License Keys are required for a new site or if additional Cyberstations or WebClient users can be added to an existing site. Resolution Depending on how large your system is and how many Cyberstations are required, you will have one of the four system configurations described below: A stand-alone system, which is comprised of up to three (3) PCs; (PC 1) Requires a SU key allowing SQL Express + Continuum. (PC 2) Requires LAN key allowing Continuum. (PC 3) Requires LAN key allowing Continuum. Note1: When changing from a LAN configuration to a SU configuration, an existing LAN key can be used in place of having to purchase a new SU key.) A stand-alone system with WebClient, which is comprised of up to three (3) PCs; (PC 1) Requires a SU key with WC1 or WC2 option allowing SQL Express + Continuum + one or two WebClient browser users. (PC 2) Requires LAN key allowing Continuum or no key allowing WebClient browser user connection. (PC 3) Requires LAN key allowing Continuum or no key allowing WebClient browser user connection. Note2:  In a stand-alone system there can be a maximum of 3 client connections; 3 Cyberstations OR 2 Cyberstations and 1 WebClient OR 1 Cyberstation and 2 WebClients. Note3:  When using this option of having WebClient running on the same system as the Cyberstation and SQL Server, make sure that the system has enough resources to adequately support these resource-hungry processes. A LAN system, which can be comprised of many PC's; (PC 1) No key required. Allows SQL Server only. In a LAN environment the Continuum Cyberstation is not installed on the same PC where SQL Server is installed). (PC 2) Requires LAN key allowing Continuum (PC 3) Requires LAN key allowing Continuum (PC 4) Requires LAN key allowing Continuum (PC 5) Requires LAN key allowing Continuum etc... A LAN system with WebClient, which can be comprised of many PC's; (PC 1) No key required. Allows SQL Server only. In a LAN environment, the Continuum Cyberstation is not installed on the same PC where SQL Server is installed. (PC 2) Requires WEBC key allowing WebClient on dedicated IIS server (up to 1, 2, 5, 10, 15, 20, or 25 WebClient user(s) licenses available). (PC 3) Requires LAN key allowing Continuum (PC 4) Requires LAN key allowing Continuum (PC 5) Requires LAN key allowing Continuum etc... Note4 :  An SU key cannot be used in a LAN system as it does not allow a remote SQL connection. To connect to a remote SQL Server a LAN key is required.)   For more information on Cyberstation License Key part numbers and the different options available for these keys, see "CyberStation & web.Client v2.0 PA-00353" or similar on ExchangeOnline.

Issue Continuum CX/BCX controller provides up to 12 SNMP NMS notification devices (2 devices IP addresses in controller's non-volatile memory and 10 devices' IP addresses in volatile memory), but its SNMP Alarming configuration page shows only two edit boxes for the IP address of the NMS devices (destination IP of the notification) to be set in non-volatile memory. Where should the rest of the 10 devices' IP addresses be set? Product Line Andover Continuum Environment CX controllers BCX controllers NC2 controllers ACX57xx controllers Cause Continuum CX/BCX controller's SNMP Alarming configuration page shows only two edit boxes for the IP address of the NMS devices (IP address of the destination devices of the notification) to be set. Resolution The first two(2) NMS Devices IP addresses are saved in non-volatile memory of the controller by entering them on the SNMP configuration page of either the Command Terminal Interface (hyper terminal for the 1st Gen controllers) or the Configuration WebPage interface (web browser for the 2nd Gen controller). The 10 rest NMS devices' IP addresses are saved in volatile memory of the controller by entering them on accNotifyTable using the NMS software's MIB Browser. Please refer to the attached "SNMP Configuration.pdf" file page 21 for an example of the MG_Soft MIB Browser in that regard.

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"