Notifications

Ask Me About Webinar: Data Center Assets - Modeling, Cooling, and CFD Simulation
Join our 30-minute expert session on July 10, 2025 (9:00 AM & 5:00 PM CET), to explore Digital Twins, cooling simulations, and IT infrastructure modeling. Learn how to boost resiliency and plan power capacity effectively. Register now to secure your spot!

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Label: "andover continuum"

View in: "Building Automation Knowledge Base" | Community

2208 Posts | First Used: 2018-09-06

Building Automation Knowledge Base

Issue Personnel distribution shows error 5310 Product Line Andover Continuum Environment Cyberstation Cause Error 5310 (0x14BE hex) indicates a duplicate card number. Resolution Take a LAN capture of the distribution using Using WireShark to analyse communications on an Ethernet network and send it to PSS for analysis, a PSS engineer will decode the packet to extract the card number and card type that is being rejected as duplicate. Armed with the card number and type find the offending record in the DB and eliminate the duplication.

Issue Getting error "Unable to find an object in the database.Root\FolderName\OldAreaName" when creating new Personnel, in Personnel Manager. Following a change to Area names, the Personnel Profiles no longer contain these changed Areas. Product Line Andover Continuum Environment Continuum 1.81 and above Cause Do not rename Areas without removing/replacing them from the Personnel Profile. Resolution Always remove Areas from Personnel Profiles before changing the Area name, then replace Area If you simply rename the Area without removing that Area from the Personnel Profile, then the Personnel Profile will either get corrupted or the changed Areas will get removed from the Personnel Profile. If the Personnel Profile is corrupted then it needs deleting. Delete from Personnel Manager, if the corruption is such that it cannot be deleted from Personnel Manager, see Cannot delete personnel profiles Once the Personnel Profile deleted, recreate as required.

Issue The controller installation guides detail how to display the values in Water Column (WC), but how can this be displayed in metric units? Product Line Andover Continuum Environment Infinet controllers (i2865 & i2865-V, i2866 & i2866-V , i2885, i2885-V, i2850 &i2853 ) BACnet controllers (b3865 & b3865-V, b3866 & b3866-V , b3885, b3885-V, b3850 & b3853) Cause A conversion to metric units (Pascals) is needed. Resolution i28xx type of Infinet Controller has 0-2" WC (Water Column) range which corresponds to 0-2V so the input value can be read directly in WC. The 850 has a single airflow sensor on channel 8 The 853 has two airflow sensors on inputs 7 and 8 For 865, 866, and 885 the airflow sensor is on Input 7 Always use input type Voltage Set the units to Pascals The following conversion can be used on the conversion line: ElecValue * 500 The i28xx-V type of Infinet Controller has 0-1" WC (Water Column) range. For 865-V, 866-V and 885-V, the airflow sensor is on Input 7 Always use input type Voltage Set the units to Pascals The following conversion can be used on the conversion line: ElecValue * 250 For controlling the Damper motor output Create an Infinity Output point of type Triac on Channel 1 It can then be opened/closed like any other Triac output with the use of On, -On or Off commands. Also see Setting up the override value to show the damper feedback on an i2/B3 866-V for details on reading the damper feedback on the i2/b3886-V.

Issue When using the Modbus TCP/IP XDriver will the data type used by a 3rd party system be supported. Product Line Andover Continuum Environment Modbus TCP X-Driver Cause Not every possible format of data is included in the Modbus IP X Driver. Resolution The following data formats are supported in version ModbusTCPIP_2ndGen200018.xdr: Unsigned Integer 16 bit Signed Integer 16 bit Reverse Floating Point 32 bit Floating point 32 bit Long Integer Unsigned 32 bit Long Integer Unsigned Swapped 32 bit If the products used have a different data format then this would require a new development of the X Driver, please see Will Continuum communicate with a third party system? for contact details. Also ensure that the X Driver point type created (Numeric, Input, Output) is supported by the function code used. Check out the X Driver manual for the list of point types supported by each function code. For example Function code 3 can be used with Numerics and Outputs, but not Inputs.

Issue Options are needed for truncating large amounts of extended log data, but with the ability to report on that data Product Line Andover Continuum Environment Continuum Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause Extended logs data can cause the Continuumdb to get large and needs to be truncated with the ability to continue to report from the old data Resolution Set up automatic truncation of extended logs (See the Check Purge Interval section in Stand Alone Continuum using SQL Server 2005 Express is not purging the ExtendedLog table) Ex. Year, 180 days Make a copy of the Continuum database on the existing server. In this scenario you would have ContinuumDB and ArchiveDB. Use one of the Cybers via Workstation Initialization) to temporarily switch to the ArchiveDB for reporting purposes and then switch back. Purchase the Extended Log Archiver uses a separate db for the archived data and truncates data from the Continuumdb automatically. For more information email COE@Buildings.Schneider-Electric.com

Issue When alarm is triggered in the controller sometime the alarm will immediately be displayed on the Alarm View as expected, you trigger the same point alarm a few times and some times there is a delay of up to a minute or two before the alarm shows up on the Alarm View. Looking at a list view of the alarms you can see the difference between the time stamp and the time of log Product Line Andover Continuum Environment CyberStation All controllers Cause The controller has been taught about CyberStation whose network ID has been since changed. Resolution Use a PE program to find out from the controller's perspective what it has been taught. If the controller contains entries in its table that it should not have, then reload the controller to remove them. See Visibility into a controller's list of peer controllers and Cyberstations following a teach for a sample PE program.

Issue When using the UI-8-10V for 0-10V analog input, the ElecValue of the input shows the half of the actually applied voltage. Product Line Andover Continuum Environment NetController: CX9900 , CX9940 , CX9680 IOU: UI8-10V (UI-8-10V) Cause UI8's 10V dip switch functions as the voltage divider. Resolution As the UI8's 10V dip switch functions as the voltage divider, it halves the 10V input voltage into 5V and uses it as the measured input. So, the ElecValue of the input shows the half of the actual input voltage. Note: When the input is configured for 10V operation, the input impedance is 4.4kΩs. Therefore, the sensor used would have to be able to source as much as 2.3mA. If input impedance is an issue for the sensor, then select the 5V input switch setting and use external resistors as detailed in How to use a 0-10V Sensor on a controller with 5V inputs.

Issue When executing a Find New BACnet Device a third party controller (Trane) would not come into the system. Product Line Andover Continuum Environment Continuum BACnet Trane Cause BACnet Network ID was assigned to 1 in the third party device. Both the CyberStation Device node ID and the third party device Node Id can not be set to 1. Resolution Have the vendor change the device node ID from 1 to a unique value on the network. See Could not learn in a new 3rd Party BACnet device.

Issue Site inquiring as to know the limit to how many workstations can be connected to a Continuum LAN system. Product Line Andover Continuum Environment Windows Server SQL Cause Site planning and architecture requires information on the limit of how many workstations can be connected to a Continuum LAN system. Resolution The Continuum LAN system itself has no real limit to how many workstations you can connect, but there are some limits to take into consideration. You can have up to 64 Workstations with ACC NET ID's between 191 - 254 which you will be able to setup to receive Continuum alarms. If the requirement is to have more than the 64 workstations allowed, you can add workstations after this limit but you will not be able to receive alarms and will need to set their ACC NET ID set to 0 If you add extra workstations you may also need to purchase additional Microsoft CAL (Client Access Licensing) licences for the Server and SQL which the database will reside on. For more information please see Microsoft Volume Licensing. Also see Client Access License (CAL) for more detail about CAL.

Issue Transitioning from Continuum to Struxureware Building Operation and replacing bCX's with Automation Servers. Product Line Andover Continuum, EcoStruxure Building Operation Environment b3865 Struxureware Building Operation Cause Unsure if the older belimo style VAV controllers are compatible with StruxureWare Building Operation. Resolution All of the b3xxx controllers (including both the -V and non -V) will work with the Automation Server under it's MSTP network. Also check out the b3 VAV Quick Start Video on the Community.

Issue Upgrading from older Continuum version using parallel dongle. Product Line Andover Continuum Environment CyberStation Cause The old style hardware key cannot be attached to newer machine that do not have a parallel port. Resolution It is not necessary to have a hardware key plugged into Continuum workstation pc when the c2v file is created. If you are able to read the key information and/or identify the serial number for the existing key, contact the EcoBuilding upgrade department at Upgrades.Continuum@schneider-electric.com and provide them with the serial number of the hardware key and a c2v file that was generated on the Continuum workstation. If you are unable to read the key information or identify the S/N from the old dongle, contact the EcoBuilding upgrade department at Upgrades.Continuum@schneider-electric.com. It may become necessary to sent the hardware key to the EcoBuilding Upgrade Dept to so that they can extract the serial number and key information themselves. See also Software Licensing for Continuum 2.0 and StruxureWare Solution.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Unable to enable or disable Enhanced Alarm Logging or Enhanced Alarm Delivery flags in Database Initialization. The Enhanced Alarm Logging flag goes back to what it was set to before making the change and the Enhanced Alarm Delivery flag is greyed out and uneditable. Product Line Andover Continuum Environment Continuum Database Initialization Cause The owner of the ContinuumDB is set to something other than the default andover97. In this specific case it was set to SA. The SA user was unable to write these changes to the database hence why the settings kept reverting back. To compound the issue it was found that an andover97 user had been created under the Security folder in the ContinuumDB, this then blocked attempts to change the owner to the correct andover97 user. Resolution Backup the ContinuumDB before making any changes. See Move / Backup / Restore a database on a Single User SQL2005 Express system. Attempt to change the db owner with the below query using the sp_changedbowner stored procedure. Select "New Query" and copy the query text shown below. Run the query. USE [ContinuumDB] GO sp_changedbowner 'andover97' GO If this produces an error "The proposed new database owner is already a user or aliased in the database" then see Unable to change the ContinuumDB database owner using the stored procedure sp_changedbowner for instructions on how to drop the incorrect user so we can use the correct one. After successfully dropping the user from the ContinuumDB, re-run the query in step 2 above to change the database owner to andover97. After successfully setting andover97 to the database owner you should now be able to toggle the Enhanced Alarm Logging and Enhanced Alarm Delivery options in Database Initialization. If you want these enabled; toggle them both off, update the database, toggle them both on, update the database again. This will ensure they have been enabled properly. Note: The definitive check to see if the Enhanced Alarm logging and Enhanced alarm delivery are both enabled is by checking the dbo.ACCDBVersion table in the SQL database using SQL Server Management Studio (or Express). New Alarm Logging and New Alarm Delivery should both be set to 1.

Issue Video integrations with Cyberstation want to bring in Pelco based alarms Product Line Andover Continuum, Pelco Environment Pelco DVR/SRV and encoders Continuum Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause Pelco devices have alarm abilities, but not all can be brought into Continuum Resolution Offline and motion alarms can be brought into Continuum. Any other Pelco hardware related alarms (i.e. dry contact or alarm inputs) cannot be brought into Continuum. See Video Monitor is not popping up video on alarm for troubleshooting motion or offline alarms.

Issue Continuum runs very slowly. Taking up to two minutes to first startup. Generally opening up Continuum Explorer and any other objects are seen to be slower than normal as well. Product Line Andover Continuum Environment Continuum v1.94 and above Cause There was no Security Key connected and Continuum was running in Demo mode. This symptom can also be caused by a missing or corrupt driver for the Security key, see Re-install of Continuum system and security key is not being recognized for details on re-installing the Security Key driver. Resolution Install valid Security Key and restart Continuum. Note: Want to know what features are supported in Demo mode? See How do we run Continuum in Demo mode and what features are available?

Issue Alarms or Events are not being received as soon as they occur and there is a large delay before they are written to the Database. Product Line Andover Continuum Environment Continuum Cause Review the controller error log. If there are 6c0e errors, this indicates the comms buffer is filling up (see Controller error log: error transmitting (LAN_ERR_TRANSMIT_ERROR)). Another indicator is in the ACCTRace logs. Check if Alarms are being logged in the Database when the WS thread is receiving them. The time in the ACCtrace may be logged as the TimeOfLog. Investigate the programming to see if it is polling data from a BACnet controller constantly. There may be no delay in poll requests which can overload the controllers comms buffers. This will in turn delay some Alarms from being delivered to the Workstation to be displayed and logged in the Database. Resolution Fix programming so there are wait lines between each poll. Also see Controller error log: error transmitting (LAN_ERR_TRANSMIT_ERROR).

Issue How to upgrade from Continuum v1.4 Product Line Andover Continuum Environment Continuum Cyberstation Cause What are the steps in upgrading from Continuum 1.4 Resolution For a smaller site it may be quicker and more reliable to install the current Cyberstation version, then upload from the controller, this has the advantage of ensuring you have a clean database. The alarms, workstations etc, would needs to be rebuilt from scratch. If the current database is clean (Passing continuum analyzer is NOT proof of a clean database, only a helpful initial step) and it is decided to upgrade the existing database from 1.4, you will first need to upgrade to v1.5x, then follow Upgrading Continuum from 1.5x to Continuum 1.9x. The overall process can be a little complex as various operating systems need to be available/installed. See the Continuum Compatibility Matrix for details for the PC and Controller firmware requirements Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation See the Continuum installation guides for the PC hardware requirements The v1.4 graphics could be .pan or .pin files. The .pan would need to be re-drawn as .pin files, in order to be compatible Run Continuum Analyzer before/after each upgrade, also run Continuum to ensure it runs correctly.

Issue When running a listview on the alarm log it appears there are instances where the alarm was acknowledged before the timestamp. How can this happen? Product Line Andover Continuum Environment Time Sync Cause This issue can occur if the Continuum system is not properly time synchronized. In order to properly sync the system time, it's helpful to understand where the various alarm time attributes are set: TimeStamp comes from the controller's time TimeofLog comes from the SQL Server's time TimeofAck comes from the Acknowledging CyberStation's time Resolution Make sure all the components of the system are properly time synchronized. Methods of synchronizing server and workstation times may vary based on the workstation operating system and if your network is using active directory. Refer to the network administrator to verify if time sync is being done, and under what conditions (logon only and/or a schedule) and how often. If Continuum is on an isolated network refer to http://support.microsoft.com and search on network time synchronization to learn about the different options for the particular network configuration. As for the workstation-to-controller time sync, Time sync controllers to workstations includes a program to which will sync the workstation time to the controllers. TimeOfLog and TimeStamp columns in an Alarm or AccessEvent listview are different covers a couple of conditions where the TimeStamp and TimeofLog may vary considerably. Periodically, verify that all the components are in sync.

Issue Continuum general preferences show the system is configured to purge extended log data after X days, yet the extended log data is not purged. Product Line Andover Continuum Environment CyberStation Cause LAN System The SQL agent responsible for purging extended log data is missing or disabled. For Single User system see Stand Alone Continuum using SQL Server 2005 Express is not purging the ExtendedLog table Resolution LAN Systems (for Single User see Stand Alone Continuum using SQL Server 2005 Express is not purging the ExtendedLog table) In SQL Server Management Studio expand SQL Server Agent, then expand Jobs If ExtLog_Purge_ContinuumDB job is present verify its properties (see image below), make sure the job is enabled and properly configured to run. If the job does not exist it can be recreated by following these steps: Close ALL Continuum Cyberstations/Web Client From SQL Server Management Studio run the following query against the ContinuumDB update ACDBVersion set ACDBVersion = 0 Run Continuum DB Initialization and update the database from the server tab, when prompted to run the ImportExport fixup tool select NO Verify the job was created then run Continuum

Issue How to use the Known Occupancy Count (KnownOccupCount) number of an Area in Plain English (PE) programming. Product Line Andover Continuum Environment Continuum Cyberstation Continuum Access Control Cause Need to be able to retrieve the Known Occupancy Count number of an Area for use in Plain English programming for limiting access to an Area. The attribute does not show up in the list of attributes in the Area Listview. Resolution Even though we can't see the attribute in an Area Listview, you can use the "KnownOccupCount" attribute at the command line or in Plain English programs. Example 1 - Print Known Occupancy Count to command line. print AreaFolder\Area1 KnownOccupCount Example 2 - In a Workstations Program, set a pre-defined AnalogValue to the Known Occupancy Count of an Area. Area1KnownCount = AreaFolder\Area1 KnownOccupCount Note: The Known Occupancy Count will not function with Entry only doors. Both Entry and Exit readers are required on the doors within the Area. See Known Occupancy Count number does not increase when Personnel enter the Area on this.

Issue Controllers IP address needs to be changed but any attempt to do so results in the IP address reverting back to what it was previously configured for. Product Line Andover Continuum Environment Continuum CX9702 BCX controllers NC2 controllers ACX57xx controllers Cause The Controller has hit the Flash writes circuit breaker and is no longer able to save any changes to Flash. This includes updating Device settings such as IP address and ACC Node ID. The controller error log may also contain an error similar to below when attempting to make any such changes. 10/08/2014 19:00:22.00 0x00004406 0x03b76100 0x0004cb68 0x003e2000 0x000007d1 DEVICE_ERR_ERASE_LIMIT (Flash circuit breaker tripped. CX97XX code base) Resolution One of the two methods to reset the Flash circuit breaker listed below should then allow the controller to write to Flash again. 1. accstatusbackup = accbackupenable For more information see Caution when using PE programs to perform an automatic flash backup on a controller. 2. INFFlashDisabled. Create a numeric in the controller with the following name and alias: INFFlashDisabled A value greater than 0 usually indicates that the flash circuit breaker had tripped, though in some cases you may find these errors occurring when INFFlashDisabled = 0. In either case, once the value of this numeric is set to 0 and applied, the flash circuit breaker errors should stop.

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

Error 5310 on Cyberstation personnel distribution

"Unable to find an object in the database.Root\FolderName\OldAreaName" when creating new Personnel Profile

Display i28xx and i28xx-V airflow in Pascals

Modbus IP X Driver supported data formats

Options for archiving extended log data

CyberStation Alarms are delayed by 30 to 60 seconds

Actual measured voltage of 0-10V analog input of UI-8-10V module with dip switch set to 10V range

Can not learn in a new 3rd Party BACnet device in Continuum

Number of workstations possible on a Continuum LAN system

Transitioning Belimo Bacnet b3865 VAV controllers to an Automation Server

How to upgrade old parallel dongle to a keyless Continuum License

Unable to enable or disable Enhanced Alarm Logging or Alarm Delivery flags in Database Initialization

Alarms from Pelco devices in Continuum

Continuum runs very slowly, taking up to two minutes to first startup

Alarms or Events are not received as soon as they occur

How to upgrade from Continuum v1.4

How can an alarm be acknowledged before it occurs?

Continuum is not purging the extended log data

Known Occupancy Count (KnownOccupCount) number of an Area in Plain English programming

Attempts to change Controllers IP address fails and unable to reset to default IP address

Building Automation Knowledge Base

Related Forums

Welcome!