Building Automation Knowledge Base

Issue Required a VPAT (Voluntary Product Accessibility Template) or statement of accessibility for the Andover Continuum System. Product Line Andover Continuum Environment Andover Continuum Cause The Voluntary Product Accessibility Template (VPAT) is a document that evaluates how accessible a particular product is according to the Section 508 Standards. It is a self-disclosing document produced by the vendor which details each aspect of the Section 508 requirements and how the product supports each criterion. VPATs are used by buyers to determine how accessible a product is and where any potential deficiencies are. They are required by some buyers before a purchase is made. More Information can be found from the below public links: Section 508 of the Rehabilitation Act of 1973 Voluntary Product Accessibility Template (VPAT) Overview of Technologies and Formats WHAT IS A VPAT AND HOW IS IT USED? Resolution Schneider Electric does not have a VPAT document for Continuum.

Issue How to decode BACnet errors when they are encountered in the following products. Product Line EcoStruxure Building Operation, Andover Continuum, TAC IA Series Environment EBO Error Log Tool Continuum bCX4040 (BACnet) Continuum b3s Building Operation Multi-purpose Controller (MPC/V) Building Operation Room Controller (RPC/V) Building Operation IP-IO EBO Trace and System logs Cause Documentation is unavailable for these errors when reviewing log files against any captures.  Resolution The error in log files is composed of two fields, BACnetErrorClass and BACnetErrorCode. The BACnet Error Class (BEC) field is made of the high 16 bits and the BACnet Error Code (BE) of the low 16 bits.  0x800 indicates the error class and error code are in Hexidecimal format. Error Class 0x8001, when remove 0x800, 1 decodes to Object Error Code 001f decodes to Unknown Object Therefore, the error code is Object_Unknown Object, where the device indicates it has no knowledge of the object, either it does not exist or the device does not have the expected program/database installed. For b3, it could be memory was wiped on power failure and needs to be reloaded. It could mean the expected application needs to be downloaded for other devices.   The following are a subset of BACnet errors defined in the specification. If you have questions or encounter ones not listed, please contact Product Support Services.   Error Class List High 16 bits of Error. See BACnet spec clause 18. May not include 0x8000. (Example: could be 0x5002B instead of 0x8005002B for COV subscription failed) Error Class Hex(0x800) Dec Notes device 0 0   object 1 1   property 2 2   resources 3 3   security 4 4   services 5 5   vt 6 6   proprietary     64 is the first available code for proprietary error classes client 7FFD   0x7FFD0000 Reject 7FFE   0x7FFE0000 (error code is BACnetReject) Abort 7FFF   0x7FFF0000 (error code is BACnetAbort)   Error Code List Low 16 bits of Error. See BACnet spec clause 18. Error Code Hex (0x) Dec other 0 0 authentication_failed 1 1 configuration_in_progress 2 2 device_busy 3 3 dynamic_creation_not_supported 4 4 file_access_denied 5 5 incompatible_security_levels 6 6 inconsistent_parameters 7 7 inconsistent_selection_criterion 8 8 invalid_data_type 9 9 invalid_file_access_method A 10 invalid_file_start_position B 11 invalid_operator_name C 12 invalid_parameter_data_type D 13 invalid_time_stamp E 14 key_generation_error F 15 missing_required_parameter 10 16 no_objects_of_specified_type 11 17 no_space_for_object 12 18 no_space_to_add_list_element 13 19 no_space_to_write_property 14 20 no_vt_sessions_available 15 21 property_is_not_a_list 16 22 object_deletion_not_permitted 17 23 object_identifier_already_exists 18 24 operational_problem 19 25 password_failure 1A 26 read_access_denied 1B 27 security_not_supported 1C 28 service_request_denied 1D 29 timeout 1E 30 unknown_object 1F 31 unknown_property 20 32 removed 21 33 unknown_vt_class 22 34 unknown_vt_session 23 35 unsupported_object_type 24 36 value_out_of_range 25 37 vt_session_already_closed 26 38 vt_session_termination_failure 27 39 write_access_denied 28 40 character_set_not_supported 29 41 invalid_array_index 2A 42 cov_subscription_failed 2B 43 not_cov_property 2C 44 optional_functionality_not_supported 2D 45 invalid_configuration_data 2E 46 datatype_not_supported 2F 47 duplicate_name 30 48 duplicate_object_id 31 49 property_is_not_an_array 32 50   Common BACnet errors you may see: Error Code Translation Notes 0x8000001e Device + timeout likely something is offline 0x8001001f Object + unknown object likely b3/AS memory was wiped in power fail 0x80020020 Property + unknown property   0x80020025 Property + value out of range likely writing 0 to a multistate object 0x80020028 Property + write access denied   0x8002002c Property + not cov property trying to subscribe to non COV property  0x8002002e Property + invalid configuration data likely configured a change-of-value alarm on non-analog 0x80030000 Resources + out of memory   0x80050007 Services + inconsistent parameters   0x80050019 Services + operational problem   0x8005001D Services + service request denied   0x8005002B Services + COV subscription failed (0x5002B may show, not including the 0x800)   In Wireshark, using the display filter bacapp.type == 5 one will see errors dissected in the APDU packets in Decimal format. In this example, the BACnet device returns an error for Device (0) and operational problem (25) when responding to a readPropertyMultiple.

Issue How to identify what ports are being used on a PC. Product Line All product Lines. Environment Any Windows OS Cause Running multiple applications on the same PC without managing TCP/UDP port assignments can lead to conflicts. Resolution TCPView will help you identify all ports and services to each application. Download from Microsoft's website http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx Detailed instructions are available at the site.

Issue For various reasons sometimes it is necessary to clear the error log in the controllers.   NOTE: First generation controllers such as the CX9200 and CX9900 (NetController 1) and Infinet1 devices do not support the error log utility, this article does not apply to those controllers.   Product Line Andover Continuum Environment CyberStation bCX9640 bCX4040 bCX4000 CX9680 ACX5740 ACX5720 All b3 devices All i2 devices Cause Guidelines for clearing the controllers error log in the field. Resolution bCX4040, bCX4000, b3s Error log is cleared by setting the Errors system variable to 0 (zero)   IMPORTANT It s not recommended to set the errors system variable from within a Plain English program, doing so risks damaging the controller's flash memory which has a limited number of write/erase cycles. Only reset the errors system variable to 0 from the command line or from the system variable object editor.   If the Errors system variable has a non zero value all that is required is to reset it to 0   NOTE: In some older version of the firmware, if the Errors system variable is at 0 then it has to be changed to a non zero value before it can be reset to 0 One easy way to generate an error is to create an InfinityProgram that attempts a DIVIDE BY ZERO I.e. Program is AutoStart and FallThru Numeric N n = 1/0   Create the InfinityProgram above in the controller, once the program saves and runs it will be disabled and the Errors system variable will increment by one. Remember to delete the program as it is no longer needed bCX9640 CX9680, ACX5740, ACX5720 Use the controller error log tool to clear the error log.

Issue Continuum i2 and b3 devices share the same hardware platform, however, power consumption on the devices IO Expansion Port differs depending on the communication protocol firmware (Infinet or BACnet) running in the device. Product Line Andover Continuum, EcoStruxure Building Operation Environment All i2 devices All b3 devices Cause Even though the hardware of an i2 device is identical to that of its counterpart b3 device, the difference in firmware causes variation in power consumption on the device's Expansion IO port, specifically, it has been observed that the b3 devices adhere more strictly to the 180 mA limit than the i2 devices, resulting in loss of operation on IO channels located on the Expansion Port if the power limit is exceeded.  Now that conversion of devices from one protocol to another is occurring in the field, it has become evident that there are cases where the 180 mA limit is exceeded in an i2 device without any negative results, but once the i2 device is converted to a b3 device, all IO on the expansion port stop working. Resolution Before converting an i2 device to a b3 device in the field, it is crucial to review the Expansion IO Datasheet (attached) to ensure that the configuration does not exceed the specified power consumption limit. If the configuration exceeds the 180 mA limit, take the following steps: Remove any additional xP module causing the limit to be exceeded. Reconfigure the xP modules to ensure that the configuration does not consume more than 180 mA.

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 EcoStruxure Building Operation, Andover Continuum Environment b3 controller i2 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 Cannot do a backup to flash on bCX4040. Distribution Properties indicates "The flash for this controller does not need to be backed up." Product Line Andover Continuum Environment bCX4040 Cause ACCStatusBackup is set to ACCBackupInactive when ACCRestartMode is set to ACCWarmStartOnly. This occurred when a bCX9640 was flashed to a bCX4040.  ACCWarmToCool is the default ACCRestartMode for the bCX4040. Resolution Change ACCRestartMode to ACCWarmToCool and then try the backup. For more information on the ACCRestartMode refer to Chapter 5 of the bCX1 Series Controller Technical Reference document # 30-3001-890.

Issue Verification of BBMD broadcast table list Product Line Andover Continuum Environment bCX CyberStation Cause Where is the location of BBMD broadcast table list. Resolution Using a web browser connect to the bCX using the IP address and login. Select the "BBMD Configuration" option to the left.  (If this in not available then BBMD is not enabled). The BBMD Configuration page lists the IP address, broadcast mask, and network port for each BBMD that the bCX knows of. After a successful "Save All To Flash" has been executed from the BBMD Configuration webpage the "Saved" buttons will be checked off. After a "Teach" has been executed from the BBMD Configuration webpage, the Teach Results webpage will be displayed. If there is an entry in the BBMD Configuration webpage that has a "rejected" status on the Teach Results webpage, either continue to troubleshoot until the teach is successful or remove that entry from the BBMD Configuration webpage.

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. 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. One way conversion: Conversion of b4920 to b3920 is not reversible, once the b4920 controller has been converted to b3920 device, it cannot be converted back to b4920. Issue A b3920 device has failed in the field and the only available replacement at hand is a b4920 Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum b4920 Cause The b4920 is a Continuum BACnet router its hardware is almost identical to that of the b3920 device, the only difference is the Ethernet port in the b4920, which is not populated in the b3920. When a b3920 must be replaced, and the only available replacement is a b4920, use the steps outlined in this article to convert the b4920 to a b3920. Resolution Before starting the procedure, you need the following items: The b4920 device to be converted. The serial number of the b4920 device to be converted. Continuum Cyberstation with b4920 to be converted, configured, and online. (***) A RoamIO2 and BACnet Service Tool A special firmware b4920 application upgrade file provided by Product Support A b3920 bootloader file provided by Product Support Steps to convert b4920 into b3920 Contact Product Support and request the b4920 to b3920 conversion files. You will be provided with an application file (e.g. b4920toB3920B4.500077.upd) and a boot loader file (e.g. B3920BootB4.500077.upd). From Continuum Workstation, take note of the baud rate of the MSTP operating under the b4920 (In Comm1 settings) From Continuum Cyberstation, edit the b4920 controller object and take note of the BACnet Device ID and the controller Serial Number, typically they will be the same but this is not always the case. In the "General" tab, click 'Update OS' and send the Application file provided by PSS. Please note that once the application file has been sent and the controller re-starts, its MSTP will shut down and RoamIO2 is required to re-start the MSTP for operation as a b3920, the reason for this is Continuum uses mac id 0 (zero) for router controllers such as the b4920 and the bCX4040, in Continuum, b3 devices are not allowed to use mac id 0. Disconnect the Ethernet cable from the b4920, the Ethernet port is now unusable. Connect the RoamIO2 directly to the b4920's Service Port then cycle power to the b4920. Start the BACnet Service Tool In the BACnet Service Tool, de-select View by networks, then click the connect icon, the conversion from b4940 to a b3920 causes the now b3920 device to come up with an unknown baud rate and an invalid (for b3s) mac id 0, so now need to find out the baud rate the converted b3920 is using From the "View" menu, select "RoamIO2 Properties and take note of the MAC ID the RoamIO2 is using   From the 'Tools' menu, select 'Set b3 baud rate' and set it to Baud9600, and click apply    From the 'Tools' menu, select 'Set offline b3 MAC id' and enter the serial number of the device and a valid MAC ID ( DO NOT ENTER ZERO NOR THE MAC ID IN USE BY ROAMIO2), then click on 'Apply'   If you get the message below, repeat the steps above for the next baud rate... when you have found the correct baud, you will see the message below after setting the MAC ID   Once the baud and MAC id have been set successfully, the device will automatically pop up in the tree, but it will only be partially online, to bring the device fully online, click the red disconnect icon on the BACnet Service Tool to disconnect from the device, wait about 30 seconds then  click the now green connect icon to reconnect the BACnet Service Tool to the device Right-click on the device, then select 'Update OS' and send it the appropriate boot loader file provided by Product Support Once the uprev of the boot loader has completed, click 'Done' button to dismiss, select the device, right-click and select 'Cold start device', and click 'Yes' on the confirmation window   You should now be able to commission the converted device as a b3920, either as a new device or as a replacement device, following the steps for replacing a b3 device. (those steps are not in the scope of this procedure) *** b4920 controllers are not easily defaulted to factory settings. If one gets an old b4920 from the shelf, use the steps below to find out the controller's current IP address and ACCNetId which are needed to put the controller online in Continuum. IP ADDRESS Upon start-up the b4920 sends a gratuitous ARP, use Wireshark to connect directly to b4920 controller using a crossover Ethernet cable, restart the controller, and inspect the gratuitous ARP to determine the IP address configured in the b4920 ACCNetID Once you have the IP address, use the attached utility tool to discover the ACCNetID of the b4920. Unzip the attached file and use the Windows Command Line to execute FindEnodeID.exe as seen below  

Issue Problems adding i2 or b3 controllers to systems and causing the network to go down or devices to not learn on. Product Line Andover Continuum Environment i2 Controller b3 Controller Cause Duplicate ID's,  incorrect baud rates or faulty controller Resolution Infinet and BACnet field controllers have the capability to autobaud and auto correct duplicate ID's on a network. They do this by listening to the network on powerup and determining what Baud Rate and currently operating controller ID's are on the network. If an existing controller is on the network and the newly added controller has the same ID assigned, the new controller will zero out its own ID so as not to cause a network problem with duplicate ID's. Then learning or manually commissioning the controller will give it a unique ID. It is therefore critical that when adding a controller to a network, that the controller is connected to the network before the controller is powered up.  Failure to do so could cause network problems such as duplicate ID's or conflicting baud rates which could bring the network down. If the new controller causes these types of problems it is recommended to power down the suspect controller(s) and re-power them to eliminate these issues.  Run acctrace when the learn is being done and there will be an indication of what is happening.  Send a controller error log to PSS.   If nothing else works even with a clean database then replace the Master and if that works send the controller in to repair.

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 If TLS 1.0 is disabled on Microsoft Server 2016 you cannot connect to SQL Server 2016 database using Continuum database initialization. Product Line EcoStruxure Building Operation, Continuum Environment Continuum Cyberstation Microsoft SQL Server 2016 Microsoft Server 2016. Cause Microsoft no longer supports TLS 1.0 protocol and IT departments are disabling it. The current version of the ODBC driver (SQL Server) used with Continuum will not function correctly when TLS 1.0 is disabled on Windows Server 2016 in order to use TLS 1.2. A defect/hotifx QC#2290 has been issued for this issue. Resolution There is a hot fix for QC#2290 that needs to be applied to the cyberstation after the installation of the ODBC driver version 13. Use the following link to download the appropriate version of the ODBC driver for your version of the OS. Link to download ODBC driver version 13 https://www.microsoft.com/en-us/download/details.aspx?id=50420 This hotfix fixes the following defect 2290 = When TLS 1.0 is disabled on server 2016 ODBC does not connect to SQL database. Hotfix is attached below. Contact PSS for the hotfix for Cyberstation 2.03 Please note: The ODBC Driver 13 for SQL Server needs to be installed before the hotfix is applied Deprecation date   Steps to apply this hotfix: Create a ContinuumDB backup Shutdown Continuum if it is running Make a backup of OmsInst.exe in the Continuum folder Extract the OmsInst.exe from the hotfix zip file and copy the new file to the Continuum folder Do an update/initialized database Start Continuum

Issue When using mstpcap.exe to capture, it automatically stops after 65535 packets. Similarly, when using Wireshark, it will stop capturing if the dissector encounters an issue. This article provides a solution to continuously capture BACnet MS/TP traffic in a ring buffer and store it as files. Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series Environment Wireshark Any BACnet MSTP RS-485 network Cause Analyze BACnet traffic via capture files. Resolution Install Wireshark. Ensure TShark is checked when installing options.  Ensure Wireshark is installed with Npcap (default) or WinPCap has been installed by IA Series Workplace Tech. Install mstpcap.exe referencing BACnet MSTP Capture Application. Ensure that mstpcap.exe has been configured for the correct port and baud rate. Here is an example for Command Prompt and PowerShell: # Command Prompt cd "C:\Program Files\Wireshark\extcap" mstpcap.exe com3 38400 # PowerShell cd 'C:\Program Files\Wireshark\extcap' ./mstpcap.exe com3 38400 Run Tshark to determine the interface being used by mstpcap so that one can reference it by number. For this example, we are going to choose 9. COM3 (BACnet MS/TP on COM3). Please change the number below to the number of your interface.  Start Tshark capture by entering the following command, updating as needed. The commands below save Test01.pcap to the Username's desktop. Please store to a location that the user has access to write.  # Command Prompt cd "C:\Program Files\Wireshark" tshark.exe -i 9 -b duration:3600 -b files:72 -w "C:\Users\Username\Desktop\Desktop\Test01.pcap​"​ # PowerShell cd 'C:\Program Files\Wireshark' ./tshark.exe -i 9 -b duration:3600 -b files:72 -w 'C:\Users\Username\Desktop\Desktop\Test01.pcap​' Note: Change  -i 9  to the number of the interface on the capturing machine. Change  -b duration  to time in seconds (3600 is one hour). Change  -b files  to the number of files to cycle through (72 is 3 days of 1-hour captures, 3x24). Change  -w  to write to the location and filename you choose. Change  \Username\  to your Windows User, if you want to save to that user's Desktop Reference: tshark(1) Manual Page (wireshark.org)

Issue Customer request of a sample Plain English program to unlock a list of doors by toggling a switch. NOTES Sample program provided here as proof of concept only, and is not intended as a complete solution but rather as general guidelines, significant modifications maybe 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. Resolution Sample PE Program in PE Editor   See attached text file   

Issue What alternatives are available for accessing Continuum WebClient from browsers other than Internet Explorer? Product Line Andover Continuum Environment Continuum WebClient Server Cause While Internet Explorer is the only officially supported browser for Continuum WebClient, Microsoft has announced that support for Internet Explorer will end in June 2022.   When accessing WebClient sites using Microsoft Edge in Internet Explorer mode. WebClient server returns an error, indicating that Internet Explorer is needed to access WebClient. Resolution It is possible to access WebClient using Microsoft Edge in Internet Explorer Mode. 1. In Edge click on the ellipses (...) top right then select Settings and set like the snapshot below. a. Allow sites to be reloaded in Internet Explorer Mode(Allow) b. Add the webclient machine's login page (http://webclientservername/webclient/logon.aspx) 2. Setting Internet Explorer compatibility mode and Internet Explorer mode for future use. Navigate to the webclient URL with Edge and select Reload in Internet Explorer mode By default, these settings will be Disabled, Set both of the buttons to Enable as shown below. Note: you may have to go through the process twice to enable both buttons   A snapshot of a successful login to webclient with Edge and also the selection in yellow to Exit Internet Explorer Mode if necessary to run other web applications.   The method of specifying Internet Explorer Mode for a site’s webClient URL will depend on how the customer treats the configuration of Edge – either settings at the individual Edge level or via group policy settings.

Issue Changing the Module ID after physically replacing a modules gives error "Incorrect response (or no response) from IO module" Product Line Andover Continuum Environment CyberStation CX9900 CX9940 CX9680 IOU Module Cause Controller's OMS database is out of sync with SQL database. Resolution To synchronize the OMS database with the SQL database:- Put CyberStation in offline edit mode. Edit the IOU Module object and enter the new Module ID. Save the object Return CyberStation to online edit mode. Perform a Send to controller, reloading the controller will sync the OMS db in the controller with the SQL database. Note the following: Make sure to use the option to reload attached objects but not attached controllers If IOUs go offline when sending to controller after doing this, manually get IOUs online, perform a send to database and send to controller. If a number of IOUs were replaced this process may need to be repeated several times until the send to controller works with no errors.

Issue A dialog of "Cannot open .NET editor with .NET Framework" comes up with new installation of Webclient or after a Microsoft update of .NET 4.5.x. There was an error trying to create the .NET control for this page. Product Line Andover Continuum Environment Continuum Webclient Windows 7 Windows Server 2008 Windows 10 Internet Explorer Cause Microsoft changed the behavior of Internet Explorer when .net 4.5.x is installed on a PC. It turns off .net 2.0 support which is needed for several editors to function on Webclient browser PCs Resolution See web.Client v2.0 .Net Editor Hotfix on the EcoXpert Extranet This is a registry key file that installs the registry keys mentioned further down in this article. It allows Internet Explorer to utilize .net 2.0 that several webclient editors use. This hotfix contains a .reg file which changes the registry, it is recommended to make a Windows Restore point or a backup (export) of the existing registry folder (hive). The hotfix only updates the following keys, so the changes can also easily be made manually. On an 32-bit (x86) Operating System Add a DWORD attribute with the name EnableIEHosting to KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework Set the value to 1 On an 64-bit Operating System Add a DWORD attribute with the name EnableIEHosting to KEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework Set the value to 1 A reboot of the webclient browser PC is required after the change is made. Each browser PC will need to have this fix applied. Microsoft Edge can also be used on newer client PCs, see the following article: Microsoft Edge can be used for webclient client PCs   

Issue Error 'The UPREV engine was asked to process an invalid code type' when flashing the firmware in the controller. Product Line Andover Continuum Environment bCX9640 CX9680 ACX5720 ACX5740 Cause RAM issues Resolution Using a browser login to the controller and perform a 'Clear Database Backup', commit changes and restart the controller. When the controller has re-started  disconnect the battery, power down the controller and after a minute power the controller up and re-connect the battery. Wait for the controller to come back online and then try the uprev operation once again.

Issue Can the user set the 'Number of States' and the 'State Text' in a multi state object? Product Line EcoStruxure Building Operation Environment BACnet b3 controllers Multi-state values Cause The b3 firmware does not allow the Number of States or State Text to be modified This is Function as designed. Resolution Continuum DOES NOT allow changes to the default number of states and state labels. The 'Number of States' field is read only. An attempt to change any of the label will result in the following error: An error code was returned from a BACnet operation, but the reason could not be determined. The same is seen in EBO if any attempt is made to edit the State Text, see below

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.

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.