Issue ACX5720 or ACX5740 backup to flash renders error message: "Unable to backup objects to flash for controllername_\XKD06.51_MCD.  Backup to flash failed.,WS3,conrollername_\XKD06.51_MCD" Product Line Andover Continuum Environment Flash Backup AXC5720 ACX5740 Cause Failure to backup to Flash Resolution Before claiming a faulty controller, it could be a corrupted point or program. Disable all the programs, and try backing up the controller. Disconnect everything except communication and power, and try to backup to flash again. If you have tried to re-flash and it still is giving this error, the controller might be the issue.   Email support with the results if this controller still will not backup to flash: product.support@buildings.schneider-electric.com For configuration and operation program write operations to flash, a counter is incremented for each save and you need to create the numeric INFFlashDisabled to monitor the number of write operations. When the 2000 limit is reached, INFFlashDisabled is set to a non-zero value and logs an error. Using CyberStation, reset this value to 0 and reboot the controller to enable write operations.

Issue What is the recommended process for Database and Workstation Initialization Product Line Andover Continuum Environment Database Initialization Workstation Initialization Cause Sometimes it is necessary to do Workstation and/or Database Initialization eg. following a Continuum service pack install Resolution Database initialization LAN systems (SQL is on a separate SQL server PC) Close all connections to the database (all cyberstations, webclient servers etc.) Open "Database Initialization" from Start/All Programs/Continuum Select "Server" Select "Update Existing Database", ensure Database Information is correct, fill in User Login Password Usually Enhanced Alarm Logging and Enhanced Alarm Delivery are ticked. Then select Continue Database initialization Stand Alone (Single User) systems (SQL is on a CyberStation PC) Close all connections to the database (all cyberstations, webclient servers etc.) Open "Database Initialization" from Start/All Programs/Continuum Select "Stand Alone" Select "Update Existing Database", ensure Database Information is correct, fill in User Login Password Usually Enhanced Alarm Logging and Enhanced Alarm Delivery are ticked. Then select Continue WorkStation Initialization Close the CyberStation on the PC being initialized (other CyberStation can be running) Open "Database Initialization" from Start/All Programs/Continuum Select "Workstation" Check both tabs and fill in the User Password Then select Continue See the Continuum Installation manual for further information   NOTE 1 With the some domains the following has been found - XP - "Right click" on the "Database Initialization shortcut" and “Run As” use local admin - Windows 7 - "Shift" & "Right click" on the "Database Initialization shortcut" and “Run as a different user”, use local admin To log on use the workstation name followed by user eg. WSUK1AB123ABC\dave   NOTE 2 Long CyberStation names can result in the error "Workstation name with invalid characters. Please enter it again" In this case use a shorter name, below 16 characters is best. This can occur even with an existing longer CyberStation name.

Issue Workstation Device Node ID and BACnet Device ID settings Product Line Andover Continuum Environment Workstation BACnet devices Cause Require information on configuring the workstation Device Node ID and Bacnet Device ID Resolution When setting up a workstation two of the parameters to set are the Network ID and the Device Node ID.  The Device Node ID corresponds to the BACnet Device ID or BACnet Instance ID in the BACnet protocol. Essentially the workstation is a BACnet device and when setting the Device Node ID during setup in a BACnet installation, consideration should be taken into account when setting this number. By default Schneider BACnet controllers use their serial number as the BACnet Device ID but when using 3rd party BACnet controllers, some vendors use different means when setting their BACnet Device ID. In the past instances have been observed where the workstations Device Node ID is set to 1.   If the 3rd parties BACnet Device ID is set to 1 as well, that device will not be found when using find new BACnet devices. A method of avoiding this is to reserve 191 to 254 for creation of the workstations and set the Device Node ID to the same as the Network ID in the Database Initialization workstation configuration. Or set the workstations with the Device Node ID's starting with 1, but be aware of this setting when configuring any 3rd party BACnet devices.  The Device Node ID/BACnet Device ID must be unique within the BACnet network.

Issue Considering changing the bCX MSTP BACnet MAC ID to an available value in the 1-127 range as indicated in the bCX web page configuration. The online Help provides the following information on the setting. BACnet MAC ID - Comm2 Identifies the MAC (Media Access Control) networking address of the controller on its MS/TP network, using integers ranging from 0 to 127. The default address is 0 and it only necessary to change this value if the value has already been assigned to another device on the network. Product Line Andover Continuum Environment bCX4040 bCX4000 b3 devices BACnet 3rd party device Cause BACnet MAC ID 0 (zero) on MSTP network already in use by third party device. Resolution Due to a limitation in the b3 devices the bCX's MSTP MAC ID should not be changed unless the bCX will only host third party devices on its MSTP (Comm2) and will NEVER be in a situation where MAC ID zero is available during a b3 learn operation. The issue is that when ID zero is made available (by changing the default in the bCX) the LEARN process done on b3s will assign ID zero to one of the b3s, because of design constraints, a b3 will not operate correctly if assigned MAC id zero. Product Support strongly recommends that if a third party device is using MAC ID zero on the MSTP, that the device be re-assigned a different ID in order to keep the bCX at its default value of MAC ID zero.

Issue Are the Infilink and B-Link interchangeable or can they be converted? Product Line Andover Continuum, EcoStruxure Building Operation Environment Infilink 200 B-Link Cause Both units are RS-485 repeaters; is there a difference? Resolution You cannot convert from an Infilink 200 to a B-Link. They are both RS-485 repeaters, but the circuitry is slightly different to handle the electrical requirements of the BACnet MS/TP and the Infinet. You must use the correct unit for the network type you have. The multiple ports on both repeaters (Infilink and B-Link) allow you to construct a star topology configuration, but note that devices in each spoke (port on the repeater) MUST be connected in a daisy chain topology. Neither product contains any firmware that can be changed.

Issue The object identifier of a BACnet device (device id) must be unique internetwork-wide, different vendors use different methods for calculating the device id default value. When integrating devices from different vendors sometimes it become necessary to change a device's default object id. Product Line Andover Continuum Environment bCX4040 b3s Third party BACnet devices Cause BACnet integration Resolution If the BACnet device is a Continuum device (bCX4040 or b3), Continuum provides a mechanism for changing the default device id. For a third party BACnet device, VTS can be used to write to the Object Identifier of the device in order to change the device id. Note that this will only work if the device manufacturer has made the object identifier for the device object writable. Click here to download VTS Click here to see the procedure to follow to set a third party device id using VTS.

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. Issue Continuum i2 and b3 field devices use the same hardware. With the exception of their -V models and the bCX (bCX9640/bCX4040) controller, they were not designed to have their firmware swapped from Infinet to BACnet (or BACnet to Infinet) in the field. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum i2 Controllers (except -V) Continuum b3 Controller (except -V) Cause With the exception of the -V controllers, the devices were not designed to have their protocol (Infinet/BACnet) swapped in the field, however, due to changes in market needs R&D is now providing a method to allow the protocol to be changed in the field. Resolution To convert i2 field devices into b3 BACnet (or vice-versa) from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. Follow the procedure detailed below or as per the attached document. To swap the firmware of any non -V i2 device from one protocol to the other (in this case, from Infinet to BACnet b3), you use the following procedure.  For more information, see section 1.3 “Converting Infinet i2 Field Devices to BACnet b3 Devices from CyberStation” below. NOTE: This procedure was developed by Schneider Electric’s R&D and tested in the Product Support Services (PSS) lab.   Before starting the procedure, you need the following items: An I2 device(s) to be converted. A Continuum CyberStation with i2 device(s) configured and online. A special, conversion b3 upgrade file for the appropriate device model as provided by PSS A b3 bootloader file for the appropriate device model, provided by PSS Physical access to the device.  You need this to push its Restart switch or to access the switch or breaker where you can shut off power to the device to force a restart. A bCX4040 controller configured in CyberStation 1.2 Preparing the Field Bus for the i2 to b3 Device Conversion To ensure a smooth conversion, it is necessary that you reduce the traffic on the field bus as much as possible in order to provide the necessary bandwidth to the upgrade operations required for the conversion. Before starting the process with the conversion file, be sure to follow these instructions.    To prepare the field bus for the i2 to b3 device conversion Disable all the programs in all the devices residing in the field bus. Close all Continuum Workstations except the one performing the upgrade. In the Workstation performing the upgrade, close all graphics, List views, and anything else that could be polling data from the field bus. Make sure MS/TP field bus is on same baud rate as Infinet field bus, mainly 19.2K 1.3 Converting i2 Field Devices into b3 BACnet from CyberStation You can convert Infinet i2 field devices into b3 BACnet field devices by swapping the firmware of any non -V model i2 device. IMPORTANT: When using this procedure, be aware of the following guidelines: It applies ONLY to the firmware or communication protocol (Infinet or BACnet) of the device. It does not convert the control application in the device. Following conversion, the device’s memory is cleared, so you need to configure a new control application. It may result in a loss of critical data if not performed properly. Before beginning, ensure that all important data is backed up in the event of data loss or the device losing its application and becoming non-operational.  For more information, see section 1.1 “Introduction” above. To convert i2 field devices into b3 BACnet from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. You will be provided with an application file (namely, i2920toB3920B4.500077.upd) and a boot loader file (namely, B3920BootB4.500077.upd). From CyberStation, edit the i2 device and record its Serial Number and Infinet id. Consult the General tab to locate this information. From the Runtime tab, perform a Reset to clear the device’s database. Upgrade the i2 device using the application file provided by PSS. Once the upgrade is complete, the i2 device stays Offline since its communication protocol has now been swapped from Infinet to BACnet. Disconnect the device from the Infinet field bus of its host master controller (for example, a CX9680 or a bCX9640). Connect it to the bCX4040 MS/TP field bus. (MAKE SURE MS/TP FIELD BUS IS RUNNING AT SAME BAUD AS INFINET FIELD BUS DEVICE WAS ON, NAMELY 19.2K BAUD) In the bCX4040, configure a b3 device using the appropriate model as well the Serial Number and ID recorded previously. NOTE: You will need to provide BACnet Device ID. Typically, it will be the same as the Serial Number. You can also use a Learn to bring the device online under the bCX4040 and automatically assign the model, id etc.  Refer to this Knowledge Base article on using the serial number for the Device ID.  Remember here to set the Comm Port for comm2. Restart the device either by power cycling or using the restart button. The device will come online under the bCX4040 as a b3 device. Perform an Update b3 OS operation to send the appropriate b3 boot loader file provided by PSS. Go to the Runtime tab, and reset the device once the update is finished. Once the device reboots and comes back online, you can confirm it has the right boot loader by looking at the device from the BACnet side. The screenshots that follow display the before and after results of the i2 to b3 conversion process. Before: After:   NOTE Similar steps can be used to convert b3 device to i2 device, but once a b3 device has been converted to i2 using this procedure the device will ONLY accept conversion uprev files, attempt to uprev using regular uprev file will result in the following error:   This Uprev file does not match this type of controller. This applies to b3 to i2 conversion only, it does not apply to i2 to b3 conversion.

Issue What is the BACnet Network ID - UDP Product Line Andover Continuum Environment Continuum BACnet bCX4000 bCX4040 Cause Documentation Resolution The BACnet Network ID - UDP identifies the BACnet IP network that the bCX controller communicates on, it is 1 by default.  The BACnet Network ID - UDP should be the same for all bCX controllers that need to communicate on the BACnet IP network.  Consult UDP setting in bCX40x0 have been set to different values for additional information. Note: - CyberStation does not have a setting for BACnet Network ID - UDP.   CyberStation will communicate with all ethernet level BACnet devices regardless of the network they sit on.

Issue bCX shows BACnet Network Number zero in the Continuum Explorer Device Editor even though the BACnet Network Id - Comm2 shows value such as 2765 in the bCX configuration web page. Product Line Andover Continuum Environment CyberStation bCX4040 bCX4000 b4920 b3 devices Cause bCX sits on IP level network which Cyberstation identifies as network 0. Resolution The value entered in the bCX's BACnet Network Id - Comm2 from the configuration webpage is the number of the network the bCX will host on its MSTP port.  The bCX itself is located on the IP level network that CyberStation identifies as Network 0. BACnet devices located in the MSTP field bus of the bCX will show their BACnet Network Number as the value configured in the bCX's BACnet Network Id - Comm2 (default value 2765)

Issue Update OS, changing a controller, BACnet to Infinet or Infinet to BACnet Can b3 controllers be converted to i2 controllers? Can i2 controllers be converted to b3 controllers? Converting between bCX4040 and bCX9640   Product Line Andover Continuum, EcoStruxure Building Operation Environment i2 b3 Controllers - See Compatibility Matrix bCX Controllers - Continuum 1.7 onwards Cause Only a limited number of controllers can be converted, BACnet to/from Infinet, using Update OS. Resolution The following controllers can be converted between Infinet and BACnet, using the appropriate firmware files: bCX (bCX4040 to/from bCX9640) (options like Xdrivers, node count, IO modules and expansion IO modules are not effected) i28xx-V - b38xx-V (i2865-V to/from b3865-V, i2866-V to/from b3866-V, i2885-V to/from b3885-V) Please see link for swapping the firmware of non -V model i2/b3 Attempting to flash (Update OS) any other controllers BACnet to/from Infinity is not recommended. In nearly every instance, the result will be a non-functioning controller.   UPDATE: A procedure is now available to convert the non -V i2s to b3s in the field https://community.se.com/t5/Building-Automation-Knowledge/Conversion-of-Continuum-devices-from-i2-to-b3-and-vice-versa-in/ta-p/416712    (Note: In the bCX controllers, the ACCNetID will revert back to the default of "1", you may need to change this in the Controllers configuration webpage back to what it should be.  See Will IP settings persist when flashing a bCX4040 (BACnet) to a bCX9640 (Infinet)? for details.)   Please refer to Exchange for specific firmware: BACnet Firmware Infinet Firmware The following can be used as a general rule to determine which OS is currently running in the controller. bCX only. (b3 & i2 CPU is green) CPU LED is Green = BACnet OS CPU LED is Yellow = Infinet OS

Issue How to reset an ACX 57xx model controller Product Line Andover Continuum Environment ACX 57xx Cause While upgrading/downgrading the controller firmware, communications were lost and the controller is not communicating afterwards. Resolution Consult How to reset a ACX 57xx controller to reset the controller and then re-commission.

Issue Seeing "An Object_Identifier has been specified for an object that does not exist in the object database of the addressed BACnet device", when trying to open a BACnet Device in Continuum Product Line Andover Continuum Environment bCX 4040 BACnet Cause When trying to send a controller's obejcts to the Database on the BACnet side the following messages are seen in the Distribution Properties window. 10/10/2013 12:50:07 PM The operation 'Save to Database' is finished. 10/10/2013 12:50:07 PM Unable to save objects to the database from Id:36922175.           An Object_Identifier has been specified for an object that does not exist in the object database of the addressed BACnet device. 10/10/2013 12:50:07 PM The operation 'Save to Database' is starting.   In the case of the affected controller being a bCX, all b3's underneath the bCX are able to be seen and their objects opened, but a user is unable to open any of the objects in the bCX itself on the BACnet side of the Continuum system tree.  Some/all objects are either not located in the BACnet side of the bCX Device or they have been malformed as they were initially created. Resolution The Device needs to be removed and re-discovered Delete the BACnet side of the bCX Device. Perform a "Find new BACnet Devices" from the Root. Then "Send to Database" on the BACnet side to upload all of the BACnet objects back into the Database.  

Issue How can a BACnet b4920 be reset back to its factory default IP address? Product Line Andover Continuum Environment BACnet b4920 Cause There is no Reset IP switch on the b4920 Resolution There are 2 ways of accomplishing this.   Method One - The first method resets the controller to factory default address settings: IP Address: 169.254.1.1 Subnet Mask: 255.255.0.0 Gateway: 0.0.0.0 Webserver Port: 80 Web User Name: acc Web User pwd: acc EnergyNet ID: 1 BacNetMstpNetId: 2764 BacNetUDPNetId: 2765 During controller startup, there is a 2 minute window in which the controller will be restored to factory defaults based on the following: Seconds since startup is < 120 A Ping packet is received by the controller with a matching Ethernet address but unmatched IP address. Ping payload size of 255 bytes. Prior to running the procedure, the controller must be on the same network as the PC that that is used to issue commands.  The engineer will need to have on hand (1) IP address that is both valid and NOT in use on the network that the PC and Controller are connected to.   Get the Controller's MAC Address Each controller has a 6 byte hardware address, also known as the MAC address or Ethernet address. The address is represented in HEX. The first three bytes of the MAC address are constant and represent Andover Controls vendor ID : 00-40-11 The last 3 bytes of the MAC address are derived from your controller’s serial number. The controller’s serial number is printed on the board and is represented as an Integer value. You must convert this value to HEX in order to obtain the last 3 bytes of your controllers MAC address. Ex. Integer Serial Number: 1033394 Converted to Hex: FC4B2 Controller’s MAC: 00-40-11-0F-C4-B2   Create a batch file Create a batch file named Acc.bat with the following content: arp -s %1 %2 ping -l %3 %1 arp -d %1   Restart the b4920 Controller Within 2 Minutes of restarting, run the batch file with the 3 arguments: Acc.bat IP_Address 00-40-11-XX-XX-XX 255 Where IP_Address = valid IP on the network Where XX-XX-XX = last 3 bytes of controller’s MAC Where 255 = Ping Payload size   After Issuing the command, the controller should restart, and the factory default address settings are restored.    Method Two - Capture the Controllers Currently Configured IP Address This second method is easier to do and is currently recommended because of its ease. Download and install a network sniffing application, such as Wireshark which can be downloaded from their website here. Connect a Cross over Ethernet cable between the b4920 and a PC running the network sniffing application. Start up the network sniffing application and then reset the b4920 by hitting the reset button on the controller. On start up, the controller will send out the IP address (Gratuitous ARP Packet) which it currently has assigned to it.  Once this IP address is captured with Wireshark etc the IP of the Workstation can then be changed to allow connection to the controller's web configuration page to change its IP address as required.  

Issue What has to happen for CyberStation to generate an offline controller alarm. Product Line Andover Continuum Environment CyberStation Infinity Controller Offline alarms Cause Receiving offline controller alarms yet controller appears to be online. Resolution Controllers can be offline for many reasons, such as a broadcast storm or will not come online, but consider the following points: In order to determine whether a controller is offline, a CyberStation will send out a probe to the controller.   The frequency with which CyberStation sends out the probe is determined by the value of the Probe Time field on the General Page of the workstation configuration. If an Infinity Controller does not respond to a probe, CyberStation will wait until a probe can be sent to all other Infinity Controller nodes in the system.  If the controller fails to respond to a second probe the controller is designated as Offline by CyberStation. Each CyberStation evaluates the commstatus of all controllers and reports alarms to the database.  Occasionally a CyberStation will show a controller as being offline while another CyberStation will show the same controller in an online state. When more that one workstation detects that the same controller is offline, this information is negotiated so that there will normally not be multiple offline alarms for the same controller.  Some versions of Continuum handle this better than others.  When an offline controller responds to a probe it is marked as Return to Normal. The controller may also be marked as Return to Normal if the workstation receives some other communication from the controller.

Issue bCX9640, CX9680, ACX5720 and ACX5740 do not have ACCRestartMode system variable. Product Line Andover Continuum Environment CyberStation bCX9640 CX9680 ACX5720 ACX5740 Cause The restart mode of the second generation Infinity CX controllers (9640, 9680, 5720/40) is not user selectable. Resolution The second generation Infinity CX controllers (9640, 9680, 5720/40) have a fixed startup sequence as follows: Warm to Cool to Cold, meaning the controller will ALWAYS first attempt to WARM start, if warm start is not possible the controller will attempt a COOL start, if cool start if not possible the controller will attempt a COLD start. Warm start: Controller is re-starting with its RAM memory intact because the controller has remained powered or the memory has been kept by the battery. In this case all the configuration data (points, programs) and run time data (logs, points current values) is restored. Cool start: Controller is re-starting with its RAM memory erased or is unable to restore data from RAM for whatever reason. In this case the configuration data only (points, programs) is restored provided it has been previously backed up to flash memory. NOTE: Personnel objects are NOT kept in flash, upon cool start the controller will automatically request a personnel distribution from its access server CyberStation. Cold start: Controller unable to warm start or cool start, all configuration and runtime data will be lost. It must be reloaded from CyberStation.

Issue Controller loses data following power failure or mains noise (from transients or spikes). Product Line Andover Continuum Environment All CX, ACX, i2, bCX, b3 controllers Cause Controllers are exposed to operating conditions outside their operating envelope and tested limits. This can cause them to reset, go offline or lose data. In extreme circumstances, poor installation can take controllers outside their operating envelope and cause damage requiring a repair. Resolution If a controller is setup on a bench with a clean power supply and the correct grounding, you will be able to turn off/ on the power and the controller will warm start every time. This test will confirm the controller is operating correctly, not faulty and that the software settings are correctly set for warm starting. Also that the RAM backup battery is connected and operating. If site resets, lockups, loss of memory or other corruption are seen on a site, then here are some of the installation issues to consider: Grounding - All controllers require a clean low impedance earth to sink all of the noise and emission energy a controller may be exposed to. The noise protection circuitry within a controller is designed to dissipate this energy down to earth, if this path is not low impedance the energy can cause a controller to reset or even be damaged permanently. Shared Ground - The earth cable to the Controller should not be shared with any other equipment that is a high inductive or capacitive load, these can generate noise spikes back into the controller. This includes motors (pumps/ fans etc) lighting circuits (capacitive loads), inverters (high frequency noise). Induced emissions - The controller should not be installed near any equipment that may induce excessive radiated emissions into the unit, the radiated emissions from Motors, inverters, radio & microwave equipment, lighting circuits, power wiring can all produce radiated emissions that could exceed the specified limits of the Controllers. By fitting the controllers into earthed metal enclosures you can minimize the external emissions by effectively creating a Faraday cage protecting the controllers circuitry. Power feed - The power requirements for every controller is defined in its datasheet with the defined tolerance, taking the power levels outside these limits can cause incorrect operation. Power spikes - Surges or spikes in power feeds or connection I/O cabling can cause controllers to reset, lose data or even become damaged. Fitting varistors to the power supplies and across any output loads can minimize the impact on the controller, See What Varistors should be used?. Shared Supply - The power feed to a controller should never be shared with other equipment that can generate electrical noise. Never use the same supply to power both controllers and field equipment like valve/ damper actuators in BMS systems or magnetic door locks in Access control, both actuators and the solenoids in Mag locks can generate large back EMF pulses into the controllers that can cause resets or even damage.. Fitting power filters or an external UPS on the controller can protect it from spikes on power up/ down, it is however always best to remove the noise spikes at source, so fit filters the generators, motors, contactors etc. It is also possible for the above issues to cause Infinet networks to Reconfig as well as other networking problems. Note: All controllers are approved and tested to the defined limits for FCC and CE induced and radiated emissions as detailed in the datasheets, for a controller to fail, restart or lose data it must be exposed to levels exceeding these specifications. They are not however power equipment and cannot be exposed to the noise levels power and industrial controls equipment is designed to withstand.

Issue Some attributes used within Continuum PE programs on b3 controllers are no longer appropriate with SmartStruxure Script programming Environment b3 AS ES ASP ASB MSTP bacnet Cause Some attributes used within Continuum PE programs on b3 controllers are no longer appropriate or cannot be used with SmartStruxure Resolution An example of this would be the ElecValue attribute for an input or output. This can be used within the Conversion field of an input but cannot be used within a Script Program or Script Function. The Continuum example PE program for an STR502 or STR504 includes the line "If STR5xx ElecValue <= 0 then Return Upper" The correct result can be obtained within SmartStruxure by dropping the "ElecValue", so "If STR5xx <= 0 then Return Upper" Then ensure the STR5xx analog input is a Voltage type with no conversion configured. Note: The ElecValue keyword can still be used in the Conversion line of an Analog Inputs (e.g. for Counter input scaling). Some other Attributes not supported in Script Programming are: Size LogType

Warning COMPLEX PROCEDURE REQUIRED. The resolution of this article has many complex steps that may result in unforeseen results if not performed correctly. If you are at all unfamiliar with the requirements, please contact Product Support Services for assistance. Issue In some situations, when doing a learn on the CX/BCX controller, the learn process aborts and an error prompt pops up, "Can not learn this controller, it contains an unknown model number." Product Line Andover Continuum Environment Cyberstation CX/BCX I2/B3 Cause Learn process has been executed more than once and at least one has not completed. Some controllers that reside in the CX/BCX have not been cleared and have a duplicate infinetID with some controller in the database. Reloading the CX/BCX controller will indicate which controller has the duplicate InfinetID. Resolution It is recommended to create I2/B3 controllers manually (not by learn) to avoid this problem. If this problem happens: Open the BCX/CX controller and click "reset" Reload BCX/CX controller, from the distribution properties window to find out which controller has the duplicated InfinetID Go to the Continuum Explorer, right click the i2/B3 controller which has the duplicated InfinetID and then select "send to text file" Open the text file, change the infinetID for this controller to another number that does not exist in the database. Delete the i2/B3 controller which has the duplicated ID and import the text file. Reload the CX/BCX controller, there will be no more error. Do learn again on the commport of BCX/CX controller, that should execute successfully. For any other installation issues that also result in this error, please refer to Unknown model number error when learning I2/b3 device

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. Issue Alarms cannot be sent to recipient CyberStation (Workstation) when controller has lost the link to the CyberStation in regard to the alarmed point in Import/Export table. The new alarm shows up in Active Alarm View only after the CyberStation is rebooted Product Line Andover Continuum Environment Workstation, CyberStation NetController (CX99xx, CX96xx) Cause Import/Export table in the NetController does not have the link to the workstation for the alarmed point. Resolution Backup current DB. Shutdown Continuum from all the CyberStations. Execute ImpExpFixupUtil.exe from Continuum install folder (C:\Program Files\Continuum). Reload all the NetController with the "Do not reload attached objects" option.

Issue NC2 and ACX57xx controllers with network security applied will no longer respond to a ping command after upgrading to newest firmware. Product Line Andover Continuum Environment Network Security ACX5740 ACX5720 NC2 CX9680 Cause The ping command was used to monitor controllers offline/online status.  CX9680 and ACX57xx controllers (with network security applied) stopped responding to  a ping command after respective firmware versions  v2.100048 and v1.100052 were applied. Resolution This is functioning as designed due to the hardening of the controller's firmware for security reasons when network security has been applied.