Issue How are the pull down lists populated in the Personnel Manager for fields such as Department, Hair Color etc? How to edit/remove entries from those lists. In the screen shot below the site has changed the name of a department from 'Technical Support' to 'Product Support', how to go about removing the old department name from the list. Product Line Andover Continuum Environment Continuum Cyberstation Microsoft SQL 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. Cause Documentation Resolution The 'Department List' is populated from the department column of the Personnel table, the Personnel Manager walks the column and adds to the list any department name string that is not already present on the list. Since the list is dynamically populated from that database, to remove an entry from the list, all instances of personnel objects that have been assigned to that department must be changed until no personnel object remains with a department string equal to the string that we want removed from the list. In cases where only a few personnel objects are assigned to the department string to be removed, we can manually edit those personnel objects and change the department. In many cases the manual approach is not practical due to a large number of personnel objects that will need to be manually modified, in such cases the change can be made directly in the SQL database using the following query. ***** MAKE SURE TO HAVE A FRESH BACKUP OF THE DATABASE BEFORE MAKING ANY CHANGES DIRECTLY IN SQL **** update personnel set department = 'Product Support' where department = 'Technical Support'--------------------------> To rename an entry on the list. update personnel set department = NULL where department = 'ISIS'------------------------------------------------------------> To remove an entry on the list. Note the all personnel assigned to ISIS department will now have a BLANK department

Issue After switching the recovery model from Full to simple, the shrink task fails to shrink the transaction log file. Product Line Continuum Environment Continuum Microsoft SQL Server 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. Cause A transaction log cannot be shrunken while there is a process actively accessing the log file. Resolution Use the log_reuse_wait_desc function in a SQL query to help you identify the process that is preventing the shrinking of the transaction log. Open SQL Server Management Studio.  Click on the New Query button. In the query window type the following SQL statement: SELECT log_reuse_wait_desc FROM sys.databases WHERE name = 'ContinuumDB' Note: The name in single quotes should be the name of the Continuum Database. In some cases, it may have been changed to something other than "ContinuumDb." This query will return one or more of the following keywords.  Each of the following keywords indicates a transaction log process that is taking place. Here is a list of keywords that could be returned. NOTHING CHECKPOINT LOG_BACKUP ACTIVE_BACKUP_OR_RESTORE ACTIVE_TRANSACTION DATABASE_MIRRORING REPLICATION DATABASE_SNAPSHOT_CREATION LOG_SCAN OTHER_TRANSIENT For example, if this query were to return REPLICATION, this would indicate that the replication process has control of the transaction log.  In that case you might investigate the replication configuration or perhaps even turn replication off temporarily to successfully shrink the log. You can find a detailed description for what each keyword indicates by searching the following website Eight Reasons Transaction Log Files Keep Growing

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, EcoStruxure Security Expert, EcoStruxure Access Expert Environment Continuum AC-1 Continuum Net Controller Continuum Net Controller II Access Expert Controller Security Expert Controller 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. 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.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 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 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. 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 How to drive the IO on the DM-20 using an external pull up resistor and voltage source. Product Line Andover Continuum, Security Expert Environment Continuum CX Gen 1 Continuum Net Controller II Continuum DM-20 IO Module Security Expert Controller (SP-AC1) 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. Cause DM-20 IO does not have built-in pull-up resistors.  In order to be able to drive the IO without the DIO-20, external pull up resistors must be used. Resolution Attach a 10K resistor between the + termination of the 24VDC at the bottom left corner of the DM-20 and the termination at the female connector corresponding to the input/output to be driven.   In1, in the screenshot above, can be driven by removing and inserting the other end of the resistor into the input termination. Out5, in the screenshot above, a voltage meter is used, when the output is turned ON/OFF from the software, the voltage across the resistor will change from GROUND to 24VDC  

Issue Finding the correct procedure for migrating Infinet controllers from a Continuum controller fieldbus to an AS-P. Product Line Andover Continuum,EcoStruxure Building Operation Environment Continuum Cyberstation Building Operation Automation Server Premium (1.9 onwards) Building Operation Automation Server Bundled (1.9 onwards) 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. Cause The wrong procedure has been followed which is not the approved and tested procedure to be used when migrating Infinet controllers from Continuum to EBO.  Resolution Procedure for Converting / Transitioning the Infinet Bus Prior to migrating the Infinet The RS-485 network cable should be routed in a continuous daisy chain bus configuration. There should not be any stub connections, stars or ring configurations. The bussed cable should pass through each node to be connected with no splits or branches in the cable network. Repeaters can be used to achieve the star, distributed star (backbone with clusters), off of the backbone. For additional information, review the article: EBO Webhelp Cabling Using the conversion tool and other engineering efforts, create the AS-P database for all Infinet devices, Infinet, Interface items, etc. in either a live AS-P or in the PCT. At the site From Continuum CyberStation,  the following must be completed to each Infinet controller that you are moving to an AS-P. Upgrade all Infinet devices that are going to be converted to the latest firmware version.  Firmware upgrading capability will not be available in EBO until a future release. Clear the memory of all Infinet devices involved before relocated to the AS-P com port by editing the controller object and selecting Runtime > Reset. If the conversion was done on the PCT, deploy the AS-P. Verify that the AS-P firmware is 1.9.0.73 or higher. Disconnect Infinet bus from the Continuum controller com port(s). Move the Infinet bus (busses) to the corresponding RS485 port(s) on the AS-P. Confirm that the Infinet devices are all showing online under the AS-P Download the Infinet devices. * Backup all Infinet devices to flash memory.   *  If the Infinet devices share data with other Infinet devices then it may be necessary to repeat this step in order to establish the complete Import/Export table. PLEASE NOTE The above steps are important! If not followed, offline and bus problems can occur. There may be a desire to skip the rest of the controllers, but the steps must be followed The likelihood is high that there will be substantial difficulties in getting the i2 controllers online and in a stable state to accept the download files. All of the Infinet controllers must be reset in Continuum before moving the bus to the AS-P.  The controllers should then be backup up to flash memory to ensure that they do not revert to their Continuum configuration following a cold start. If problems occur that make it necessary to abort the migration process and return the controllers to the Continuum system, all of the Infinet controller must have their memory cleared before re-attaching the bus on the comm port of the original Continuum controller.  For those controllers which have not established communications under the AS-P, this will mean performing a hard reset at the Infinet controller hardware. At no time should the Infinet bus be connected to the both the AS-P and the Continuum controller at the same time as this  confuses the Infinet controllers causes communications issues that will take some time to resolve. Please also see the "Infinet under the hood" community post Continuum Conversion Tool NOTES V3.0.x and v3.1.x Conversion Tools should not be used. The Workaround is to use the 2.0 Conversion Tool then upgrade. (The Conversion tool was fixed by v3.1.2.6000 (CP5)) V3.2.x onwards the Conversion Tool operates correctly v4.0.3 has an issue converting Infinet controllers, 4.01 or 4.02 should be used instead Now fixed in v4.0.3.5005 CP3(Known Issues) v3.x outperform 4.x, 5.x and 6x.(known Issues). The Workaround is to convert the dmp file in CCT 3.x then upgrade the DB to the expected version in PCT or AS-P.

Issue ACX5740 controller randomly re-boots and restore from flash, the controller does not attempt warm start but instead jumps directly to cool start.  Product Line Andover Continuum Environment Continuum ACX 2 Controller Continuum ACX 4 Controller Continuum Net Controller II Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. 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. Cause Door striker creating an electrical spike that can travel back down the output wiring to the controller. When this happens, it generally will not damage any of the hardware in the controller but it could cause it to reset or cause its memory to get scrambled. The fact that the controller does not attempt warm start but instead skips directly to cool start is a strong indication that memory corruption is taking place, on startup, the controller verifies RAM memory is intact and will not attempt warm start otherwise. Resolution Install Metal Oxide Varistor (MOV ) to add voltage suppression to the controller's output driving the door striker. (Put the MOVs at the end device and not the controller end)   Another option is to add an isolation relay to keep the electrical noise from reaching the controller's output. 

Issue When restoring a Continuum database the process fails with a Cannot show requested dialog error message. Index was outside the bounds of the array. Product Line Andover Continuum Environment Continuum Cyberstation Microsoft SQL Server Microsoft SQL Server Management Studio 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. Cause The version of SQL Server Management Studio is not compatible with the Microsoft SQL Server version. In this example the error occurred when attempting to use SQL Server Management Studio for SQL Server 2005 Express to restore a database on an SQL Server 2012 Express server. Resolution Uninstall the incompatible version of SQL Server Management Studio and then install a compatible version. The database can then be restored.

Issue There is a limit of around 200 user-created objects in b3/i2 devices, once that limit is reached, an attempt to create a new object of any type in the device will result in  "Invalid Handle" error. See https://community.se.com/t5/Building-Automation-Knowledge/Creating-an-object-in-a-BACnet-B3-or-Infinet-controller-results/ta-p/9490 for more info.   Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum b3920 Controller Continuum i2920 Controller 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. Cause Each Continuum object is represented in the system by a "Handle Id", in b3/i2 devices, the handle ID is stored in the controller as a byte value which allows for a maximum of 255 handles, the system objects (System Variables etc.) use around 55 of the handles leaving around 200 for user-created objects.  CX controllers store handle IDs using a 2 bytes value, which allows for 65535 handles, CX controllers rarely run out of handle IDs. Resolution One way to deal with this limitation in the Continuum field devices is to combine InfinityNumeric, InfinityDateTime objects (when possible) into one object configured as an array (manual log).   EXAMPLE: The screen capture below shows 10 InfinityNumeric objects in an i2920 device that are used in the control application of a room named "MainLab"     Let's say for the purpose of this illustration that the following is the control program for MainLab     Since InfinityNumeric objects MainLab.a thru MainLab.j are used exclusivity to store values *** (i.e Setpoint etc), we can configure one of the objects as an array and have it hold all 10 values, thus allowing us to delete 9 InfinityNumeric objects and free 9 handle ids       Before deleting MainLab.b thru MainLab.j we need to modify ALL references to those objects, instead of referencing MainLab.b - MainLab.j we need to reference MainLab.a[1] - MainLab.a[9], note that MainLab.a holds its value (70) normally (not as part of the array), so in this case, we are only using 9 of the 10 array elements.     ***IMPORTANT Only InfinityNumeric and InfinityDateTime objects that are used exclusively to hold a value should be combined, if the object is being used for any of the following operations then it should be left as its own object.   Object triggers one or more programs Object is configured as a log Object is Occupancy flag of a schedule Object has alarms associated with it or is alarm point Object is a setpoint

Issue ACX57xx Continuum controller frequently reboots itself, loses configuration and/or stop granting access to doors until reloaded.     In the controller error log frequent and spontaneous re-starts of the controller can be observed without an apparent cause such as power failure for example.     Here is another error log from different controller with same issue, a similar signature can be observed in the following screen shot   Product Line Andover Continuum Environment Continuum ACX 2 Controller Continuum ACX 4 Controller Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. 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. Cause Electrical noise coming from door striker corrupting controller's memory.   Resolution An external Varistor may be installed for Noise Suppression of a Door Strike. Here is a link to a part that may be used for this purpose:   https://www.digikey.com/en/products/detail/bourns-inc./MOV-07D470KTR/13420467?utm_adgroup=General&utm_source=google&utm_medium=cpc&utm_campaign=PMax:%20Smart%20Shopping_Product_Zombie%20SKUS&utm_term=&utm_content=General&gclid=Cj0KCQjwteOaBhDuARIsADBqRei7ZmpR8CRYf12zRH1bfTIK7GHk3NC6XStbVoCBrPizkZvEPDlCaFEaAjLFEALw_wcB    The part should be installed at the Door Strike, from the switched 24VDC terminal to the common 24VDC terminal, like this:  

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) 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. 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 IMPORTANT: If a RoamIO2 is available, it can be used to do the conversion without the need to have Continuum Cyberstation and Continuum controllers. https://community.se.com/t5/Building-Automation-Knowledge/Conversion-of-Continuum-devices-from-i2-to-b3-and-vice-versa-in/ta-p/448337    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 xP Expansion I/O Note If the device to be converted from i2 to b3 has any expansion modules attached, make sure the modules do not exceed the power capacity of the expansion port (180 mA), 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.  See attached xP Expansion IO Datasheet for information on power consumption of each xP IO module.   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 1 If Continuum system is not available it is also possible to convert i2 to b3 using RoamIO and EBO server using the following steps Disconnect device from field bus and connect RoamIO directly to i2 device. Use InfinetServiceTool to send the application conversion file to the i2 device. After the uprev operation is done disconnect RoamIO and cycle power to the i2 device Connect converted device (now a b3) to MSTP of AS-P or other EBO server that supports BACnet MSTP Perform a b3 learn operation to bring the device online Right click the b3 device and proveed to 'Device->Update firmware...' Navigate to appropriate boot loader file for the b3 model After uprev of boot loader is complete, cycle power to the b3 device. NOTE 2 Similar steps can be used to convert b3 device to i2 device. Make sure to use the V2 version of the b3 to i2 conversion files as it was found the original set of b3 to i2 conversion files did not work in some cases. Please note that 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 Currently, a procedure exists to do conversion of i2 to b3 and vice versa using Continuum Cyberstation and NetControllers.   However, it is much simpler to do the conversion using the RoamIO and the Infinet/BACnet Service Tools. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum i2 Controllers (except -V) Continuum b3 Controller (except -V) 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. Cause This article describes an alternate and simplified conversion method to the original procedure published to convert i2 to b3. Before using this procedure, read the Conversion of Continuum devices from i2 to b3 and vice-versa in the field Knowledge Base article in its entirety for important information about converting i2/b3 controllers in the field.  Resolution Before starting the procedure, you need the following items: The device to be converted. The serial number of the device to be converted. A RoamIO2 configured to communicate with your PC via Bluetooth and the Infinet and BACnet Service Tools A special, firmware application upgrade file for the appropriate device model as provided by Product Support A bootloader file for the appropriate device model, provided by Product Support To convert i2 field devices into b3 BACnet using RoamIO2 Contact Product Support and request the conversion files for the specific model(s) you wish to convert. You will be provided with an application file (e.g. i2920toB3920B4.500077.upd) and a boot loader file (e.g. B3920BootB4.500077.upd) for each model you are converting. Connect the RoamIO2 directly to the i2 device (make sure device is disconnected from field bus) Launch the InfinetServiceToolPC.exe (attached) and click on the connect icon Once the device shows up on the tree, right click on it then select 'Uprev firmware...' Send the conversion application file provided by Product Support Once the uprev operation is complete, click the connect icon to disconnect the Infinet Service Tool from the i2 device then close the InfinetServiceTool app. Cycle power to the RoamIO2 then start the BACnet Service Tool In the BACnet Service Tool, de-select View by networks, then click the connect icon, the conversion from i2 to a b3 causes the device to default to baud 38400 and an invalid BACnet master MAC id, so upon connection the following error will be shown... Click 'Yes' to continue From the 'Tools' menu select 'Set b3 baud rate' and set it to Baud38400  From the 'Tools' menu select 'Set offline b3 MAC id' and enter the serial number of the device and a valid MAC id then click on 'Apply' If 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', send it the appropriate boot loader file provided by Product Support Once the uprev of the boot loader has completed, select the device and click on 'Cold start device' After the device re-start, click on the device in the tree and select 'Switch view', confirm the firmware and boot loader versions are correct. (you may need to do a refresh from the 'Tools' menu)

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. 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. 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 Following a clean upgrade from Continuum 1.74 to 1.93, all ACX78x controllers have the No Server LED illuminated. Product Line Andover Continuum Environment ACX780 ACX781 Cause The SystemStatus system variable is set to No Database. Additionally, the AccessServer system variable on the ACX78x controller is not correctly configured—it is not set to the ACCID of the primary access server workstation. The No Server LED illuminates when the controller cannot establish a valid connection with the access server. This typically occurs due to misconfiguration of the AccessServer variable. Resolution To resolve the issue: Set the SystemStatus variable to Normal. Ensure the AccessServer variable is correctly configured: It must be set to 0 or to the controller’s own ACCID. Do not set it to the ACCID of a workstation or any other device. Important Note Setting the AccessServer to any value other than 0 or the controller’s own ACCID will trigger the No Server LED, indicating a failed server connection.

Issue Can a door switch input be configured to operate without an input resistor? Can supervised inputs be configured to work without an input resistor? Product Line Andover Continuum Environment NetController ACX5720 ACX5740 AC_1 AC_1 Plus Cause When designing or troubleshooting a security access control system, it's essential to understand whether hardware requirements—such as input resistors—are optional or mandatory. This ensures proper functionality and avoids misconfiguration. Resolution In the Continuum door object class, the input type is fixed as a supervised input—it cannot be changed or configured otherwise. As a result, input resistors are mandatory and must be installed for the system to function correctly. Supervised inputs rely on these resistors to detect tampering or wiring faults, which is critical for maintaining system integrity and security.   Additional Notes This requirement applies to all Continuum door objects regardless of controller model. Failure to install input resistors may result in false alarms or failure to detect door status accurately.

Issue CyberStation displays a DCom or similar error message during operation. Extended logging errors may appear. CyberStation may show “Error connecting to database” yet continue running. Alarms may not appear in the Active Alarm window. Product Line Andover Continuum Environment Continuum Cause This issue typically arises from a PC-level fault or a CyberStation configuration error that prevents proper database connectivity. Potential causes include: Hard disk or RAM failure Corrupted CyberStation installation Network or permission issues Further investigation is recommended to determine the root cause. Resolution To resolve the issue: Reinitialize the database Ensure all CyberStations are shut down before proceeding. For LAN installations, select “Server” mode. For standalone setups, use “Stand Alone” mode. Reinitialize the workstation Close CyberStation completely. Restart the workstation and launch CyberStation to test connectivity. Additional Notes If the issue persists after reinitialization, consider checking system logs, hardware diagnostics, and reinstalling CyberStation. Contact Schneider Electric support for deeper troubleshooting if needed.

Issue When attempting to create an object in a controller, Continuum throws the error: "Unable to insert row in Database Table." Product Line Andover Continuum Environment SQL CyberStation Cause This issue typically occurs when a new database user is created with restricted permissions. During Continuum DB initialization, the system creates the Andover97 user in SQL and assigns essential database access permissions. If these permissions are restricted or modified, it can impair routine operations such as object creation. Resolution To resolve this issue: Verify SQL Permissions for the Andover97 user. Ensure the following permissions are granted: INSERT, UPDATE, DELETE, and SELECT on relevant tables. Access to stored procedures used by CyberStation. If permissions were altered, restore them to default or re-run the DB initialization to reapply correct settings. Additional Notes This issue is commonly seen after database migrations or security audits where user permissions are tightened. Always validate user roles and permissions post-deployment to avoid operational disruptions.

Issue What enclosure is supported for the I2-866-S? Product Line Andover Continuum Environment Infinet I2-866-S UL 864 compliance Cause Clarification needed on enclosure compatibility for UL 864-certified I2-866-S devices. Resolution The VAV-ENCL-S enclosure is the supported option for the I2-866-S device within the Andover Continuum product line, specifically for applications requiring UL 864 compliance.   Additional Notes: Ensure the enclosure installation meets all local and national fire safety regulations. Refer to the UL 864 documentation for detailed compliance requirements. For further assistance, consult the Schneider Electric support team or your local representative.

Issue What does the Infinity System Variable named Rdr1Connected through Rdr8Connected detect? Product Line Andover Continuum  Environment CX9702 ACX5720 ACX5740  Cause Information on Infinity System Variable named Rdr1Connected through Rdr8Connected Resolution The Infinity System Variables — Rdr1Connected, Rdr2Connected, ..., Rdr8Connected — are used to determine the connection status of card readers on specific controller models.   Functionality: These variables return a Boolean value (true or false) indicating whether a card reader is connected to each respective channel. The controller checks the connection by monitoring the voltage applied to the reader. LED1 is used as an indicator: If LED1 is correctly connected, the corresponding RdrXConnected variable is set to true. If not, it is set to false. Note: The voltage check may cause the LED to flicker at a high frequency. This flickering is typically not visible to the human eye.

Issue What is the maximum allowable distance for installing an xP expansion module? Product Line Andover Continuum Environment xP Expansion Module Cause Clarification needed on the cable length limitations when connecting xP expansion modules to controllers. Resolution xP expansion modules can be connected in two ways: Direct Connection: Modules may be attached directly to the bottom of the controller using the built-in expansion port connector. Remote Connection via Ribbon Cable: Modules may also be connected remotely using either: A 3-foot (~1 meter) ribbon cable A 10-foot (~3 meter) ribbon cable Important: The total cable length used across all expansion modules must not exceed 10 feet (~3 meters). Mounting Guidance: Each xP module includes four mounting holes in the base plate for secure installation. Additional Notes Ensure proper cable management to avoid signal degradation. Avoid exceeding the total cable length to maintain system reliability.