Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

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…

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • Knowledge Center
  • Building Automation Knowledge Base
  • Building Automation Knowledge Base
  • Label: Andover Continuum
Options
  • My Knowledge Base Contributions
  • Subscribe
  • Bookmark
  • Invite a Friend
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.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Labels
Top Labels
  • Alphabetical
  • Andover Continuum 2,208
  • TAC Vista 2,045
  • EcoStruxure Building Operation 1,856
  • TAC IA Series 1,827
  • TAC INET 1,458
  • Field Devices 721
  • Satchwell BAS & Sigma 474
  • EcoStruxure Security Expert 333
  • Satchwell MicroNet 252
  • EcoStruxure Building Expert 228
  • EcoStruxure Access Expert 150
  • CCTV 53
  • Project Configuration Tool 47
  • EcoStruxure Building Activate 17
  • ESMI Fire Detection 13
  • EcoStruxure Building Advisor 12
  • Automated Engineering Tool 5
  • EcoStruxure Building Data Platform 3
  • EcoStruxure Workplace Advisor 1
  • EcoStruxure for Retail - IMP 1
Top Contributors
  • Product_Support
    Product_Support
  • DavidFisher
    DavidFisher
  • Cody_Failinger
    Cody_Failinger
See More Contributors
Related Products
Thumbnail of EcoStruxure™ Building Operation
Schneider Electric
EcoStruxure™ Building Operation
4
Thumbnail of SmartX IP Controllers
Schneider Electric
SmartX IP Controllers
1
Thumbnail of EcoStruxure™ Building Advisor
Schneider Electric
EcoStruxure™ Building Advisor
1

Related Forums

  • Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite

Label: "andover continuum"

View in: "Building Automation Knowledge Base" | Community

2208 Posts | First Used: 2018-09-06

Building Automation Knowledge Base

Sort by:
Date
  • Date
  • Views
  • Likes
  • Helpfulness
Options
  • Subscribe
  • Bookmark
  • Invite a Friend
  • « Previous
    • 1
    • 2
    • 3
    • …
    • 111
  • Next »
Label: "Andover Continuum" Show all articles

Schlage Lock Configuration

Issue Schlage step by step configuration. Environment Windows Xp, 7,  2008, 2008R2 Continuum 1.94 Cause Single Door set Up examples. Resolution Schlage Door setup examples attached.   Download here
View full article
Picard Product_Support
‎2018-09-11 06:01 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:15 AM

Labels:
  • Andover Continuum
1743 Views

How to setup automatic table truncation on Single-User SQL Express systems

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 How to setup automatic table truncation on Single-User SQL Express systems. Product Line Andover Continuum Environment Continuum Cyberstation Single-User SQL Express SQL Server 2005 Cause Only the ExtendedLog table is automatically truncated on an Single-User SQL Express Continuum system. The other tables that can fill up quickly and need to be truncated regularly are not catered for (accessevent, activityevent, alarmevent, and errorevent). Resolution IMPORTANT: Make sure to perform a full SQL Database backup before attempting to make any changes to the database. (See Move / Backup / Restore a database on a Single User SQL2005 Express system for details on how to backup your database and, if not already installed, where to get Management Studio from) Use the attached file SQLExpress to add table truncations.zip, to configure your Single-User SQL Express system to automatically truncate these tables when it does the ExtendedLog truncation. After downloading the file, follow the steps below. There are three files in the archive, these need to be copied to your Continuum folder on your Single-User system running SQLExpress as the database engine. LogTruncate.SQL This file is the SQL script that performs the truncation of the four tables (accessevent, activityevent, alarmevent, and errorevent) to the number of days you specify - I have selected 90 days as my default but you can change this to whatever you require for each table. CS_LogTruncate_OneOff.bat This batch file will run the LogTruncate.sql script once when manually executed. You will need to change the server name "PC3" to whatever your PC's name actually is on your system. CS_Hrly - with LogTruncat.bat This is the batch file that will be renamed and replace the existing "CS_Hrly.bat" file currently located in your Continuum folder. This is the same as your current file except it has added the LogTruncate.sql script so that this will now be executed every hour along with the rest. Backup "CS_Hrly.bat" file in Continuum folder by renaming the file to something like "CS_Hrly ORIGINAL.bat". Rename "CS_Hrly - with LogTruncat.bat" to "CS_Hrly.bat", copy into (overtop the existing file if you haven't renamed it) the Continuum folder, and change the server name "PC3" to your PC's name. This should now execute this table truncation script along with the other database maintenance scripts every hour.
View full article
Picard Product_Support
‎2018-09-10 10:05 PM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:15 AM

Labels:
  • Andover Continuum
1997 Views

Conversion of Continuum devices from i2 to b3 and vice-versa in the field

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Continuum i2 and b3 field devices use the same hardware. With the exception of their -V models and the bCX (bCX9640/bCX4040) controller, they were not designed to have their firmware swapped from Infinet to BACnet (or BACnet to Infinet) in the field. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum i2 Controllers (except -V) Continuum b3 Controller (except -V) Cause With the exception of the -V controllers, the devices were not designed to have their protocol (Infinet/BACnet) swapped in the field, however, due to changes in market needs R&D is now providing a method to allow the protocol to be changed in the field. Resolution 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.
View full article
Captain AbeMeran Captain
‎2022-12-06 09:57 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:11 AM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
11542 Views

Emailing alarms if Microsoft Outlook is not used on the site?

Issue Emailing alarms if Microsoft Outlook is not used on the site? Product Line Andover Continuum Environment Continuum Cyberstation 1.73 and above bCX 4040 Netcontroller II (9680) ACX57xx Series (ACX II) Cause The customers site IT system is unable to provide reliable Email communications from Microsoft Outlook on the Continuum Workstations. Resolution The documented Outlook support: Initially Full Microsoft Outlook or Microsoft Exchange was specified as the requirement 1.92 to 1.94 specified Microsoft Outlook 2007 for Windows XP and Vista (Full Microsoft Outlook or Exchange) 1.94sp1 to 2.03 specified Microsoft Outlook 2007 Microsoft Outlook 2010 (Full Microsoft Outlook or Exchange software package)   For further information on outlook versions see the KB article Outlook 2007 and Outlook 2010 with Continuum email alarms. Notes Only 32bit Outlook was tested/supported Continuum does not support MS Outlook Express for emailing alarms From v2.0 CyberStation has internal SMTP email options see  SMTP Email Alarm Configuration in Continuum 2.00 to 2.03 There are other email option for emailing directly from controllers. There is a feature in the bCX (also NetController II, ACX II) controllers to be able to email messages directly to a SMTP server either manually or via Plain English programs, although this is not directly linked to the Continuum Alarm system and would require a Plain English program to determine what emails are to be sent. See the "bCX1 Controller Technical Reference" Commissioning section for details on how to set up the controller to send out emails to a 3rd party SMTP email server.  There is also the Continuum SNMP Configuration guide for use with SNMP alarming with a Network Management System. Then in the CyberStation online help see the "SendEmail" function help on how to use Plain English to get the bCX (Netcontroller II or ACX II) to send out messages via email.  
View full article
Picard Product_Support
‎2018-09-07 11:42 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:10 AM

Labels:
  • Andover Continuum
2315 Views

How to configure CX/BCX controller for 12 SNMP NMS devices

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

Last Updated: Crewman ContentModerator ‎2025-08-11 04:10 AM

Labels:
  • Andover Continuum
3076 Views

What controller ports and physical standards are supported by the Modbus X Drivers?

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

Last Updated: Crewman ContentModerator ‎2025-08-11 04:09 AM

Labels:
  • Andover Continuum
3442 Views

Schlage Integration with Security Expert

Issue Is it possible to integrate Schlage products with Security Expert? Product Line Security Expert Environment Security Expert Server (vv4.2.259.19 and above) SP-C controller Firmware (v2.08.923 and above) Cause Unable to migrate or convert a legacy access control system which has Schlage devices integrated to Security Expert Resolution With Security Expert Software (v4.2.259.19 and above) and SP-C firmware (v2.08.923 and above), the integration of Schlage devices (AD300 and AD400) with Security Expert software is supported.  It is always recommended to use the latest Security Expert Version and SP-C firmware version to avoid any known issues. For more information regarding the, Schlage Integration with Security Expert, download the attachment.  Refer to Security Expert Allegion Smart Reader Integration 
View full article
Commander Sampath_Konda Commander
‎2019-08-28 11:54 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:09 AM

Labels:
  • Andover Continuum
  • EcoStruxure Security Expert
  • TAC INET
1506 Views

Can TAC BACnet (Viconics) thermostats have identical names and deviceids within sub networks using their default names?

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

Last Updated: Crewman ContentModerator ‎2025-08-11 04:09 AM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
1691 Views

Continuum Database Sizing and SQL Server selection

Issue How do you determine how large a database will grow when using Continuum? How do you know if a Stand Alone or LAN install should be used? Which version of Microsoft SQL Server is needed? Product Line Andover Continuum Environment Windows XP Windows Vista Windows Server 2003 Windows Server 2008 MSDE SQL Express SQL Server Standard SQL Server Enterprise Cause A database will grow based on the number of objects and logging requirements for a project. Estimating how much a database will grow over time based on the number of controllers, points and logging should be done to determine which Microsoft Database solution is needed for the site. Microsoft has placed database size limitations on the free versions of their database engines called MSDE and SQL Server Express. The size limitations are 2 and 4 gigabytes respectively. If this size limitation is exceeded, it can produce unwanted results including database corruption. If the estimated size of a database over time exceeds these limitations then a full Microsoft SQL version must be implemented. Resolution An Excel spreadsheet has been developed to help evaluate the size of a Continuum database, to determine if a Stand Alone or LAN is needed and which version of SQL should be used. The Continuum database estimating spreadsheet takes into consideration 6 main areas: Extended Logs- total amount of logs, intervals and the number of days to retain  Access Events- total amount of access events and the number of days to retain Alarm Events- total number of alarms and the number of days to retain Error Events- total number of Cyberstation errors and the number of days to retain Activity Events- total number of Activity events of all Continuum users and the number of days to retain Continuum Database objects- Total number of Netcontrollers, Infinet, BCXs , mstp controllers, total number of inputs, outputs and numerics. Any of the objects not mentioned above. Consider all objects not mentioned above The number of data logs, extended log intervals, number of days to retain data and other estimation information can be inserted into the spreadsheet. The sheet will calculate the information and do the following: Estimate the space required for that object type and the sum of all object types Indicate if a Stand Alone or LAN system is needed Indicate which version of SQL Server is needed Download the Continuum Database Size Estimation Tool.
View full article
Picard Product_Support
‎2018-09-07 05:20 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:08 AM

Labels:
  • Andover Continuum
2786 Views

"Invalid attribute property" error when trying to create NetController II in Continuum v1.74 SP2 as Controller Type "9681".

Issue "Invalid attribute property" error when trying to create NetController II in Continuum v1.74 SP2 as Controller Type "9681". Environment Continuum v1.74 SP2 NetController II Cause Trying to create new NetController II device object with a "Controller Type" of "9681". "A Guide to Version 1.74 Support for NetController II and ACX 57xx" states that there is only one NetController model, the CX 9680. Please ignore references to the 9681. Resolution Create the Netcontroller II as  a Controller Type "9680" as stated on page 15 in document number 30-3001-1001 "A Guide to Version 1.74 Support for NetController II and ACX 57xx".
View full article
Picard Product_Support
‎2018-09-07 06:52 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:08 AM

Labels:
  • Andover Continuum
2007 Views

Access denied error when editing the Continuum menu or the x86 path is incorrect

Issue The user logged into Windows doesn't have permissions to the folder that contains the Continuum.mnu file,  the file is set to read only or the path in the continuum.mnu is incorrect. Product Line Andover Continuum Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Permissions are restricted to the Continuum.mnu file or the path in it is incorrect. Resolution One of the follow solutions will resolve this: Click to download an edited default path Continuum.mnu and Menu.bmp  (links for the default path C:\Program Files (x86)\Continuum) Copy these files to each workstation that has an incorrect path Manually edit the file yourself if you have a path that is other than (C:\Program Files (x86)\Continuum) Grant permissions to the folder. The folder that contains the Continuum.mnu can be located by editing the Cyberstation in Continuum Explorer. WS Edit> Preferences tab> The file name of the main menu  Ex. c:\program files\continuum\userprofile\continuum.mnu Right click on Continuum.mnu and select properties. Deselect Read Only if it is selected. Change the path to the Continuum.mnu file to a folder that you have access to and copy the continuum.mnu to it. Ex. c:\program files\continuum\continuum.mnu While in edit mode, right click on each of the buttons and select Properties Use the browse button to select the correct x86 path (C:\Program Files (x86)\Continuum) Repeat this for each of the buttons and then save the Continuum.mnu file Copy these files to each workstation that has an incorrect path Also see Continuum.mnu file with C:\program files (x86) on 64 bit PCs points to C:\program Files and shows a blank screen.
View full article
Picard Product_Support
‎2018-09-07 08:46 PM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:08 AM

Labels:
  • Andover Continuum
2048 Views

How are the i2/b3920 controllers internal varistors connected to the power input?

Issue As part of a site power feed problem investigation where varistors are being blown, how are they connected to the power feed? Environment i2920, b3920, b4920. Cause When a site is experiencing power problems and the mains input varistors blow, it is required to know how the damaged varistor is connected. Resolution The 3 varistors are connected between: Live and Earth, Neutral and Earth, Live and Neutral. The attached sketch shows how  the 3 varistors are connected. The connections are the same for the i2920 and b4920.
View full article
Picard Product_Support
‎2018-09-11 07:48 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:08 AM

Labels:
  • Andover Continuum
1689 Views

Plain English Shell statement to run Windows programs from a workstation

Issue How can I run Windows programs from a workstation plain english program? Environment Cyberstation Plain English Windows programs Cause Launching windows programs from Continuum Resolution Please see this link for information on using the Shell plain english function NOTE A Plain English script can be added to some graphics objects (Plain English Script tab), so for example you could run a batch file (in the continuum directory) from a graphics button using Shell "test.bat"
View full article
Picard Product_Support
‎2018-09-07 11:38 PM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:08 AM

Labels:
  • Andover Continuum
1561 Views

Using WireShark to analyse communications on an Ethernet network

Issue General use of the Wireshark program. Product Line Access Expert, Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Ethernet Networks Cause General Information on using WireShark. Resolution Wireshark is an Ethernet packet analysis programme, Which can be downloaded from: Latest version available from Wireshark Locally stored version 1.0.9 Installing Wireshark If necessary, unzip the WireShark executable file to a suitable location on the PC/Laptop you wish the programme to be installed on. Run the executable file and follow the on-screen instructions. Rules for capturing LAN traffic using Wireshark: Do not use a switch or router to connect the LAN capture PC to the network as these will filter important network activity that you will need to see. You will want to capture everything that is passing over the network at the point of concern. Usually, this means tapping into the ethernet at the Controller or controllers, that is having an issue. midBit-Technologies-LLC-10-100 is an example of a device that can be used to easily tap into the network to take the capture. The monitoring PC must see all traffic from the controller's point of view. The monitoring PC can be connected in either two ways: Connected to the network at the controller The customers IT department can mirror all the network traffic from the controllers port to another port the PC can be connected to. If connected to the network at the controllers, the connection must be made through a true ethernet hub. A hub will not selectively filter important network traffic as a switch or a router will do. More information on what a "true ethernet hub" can be found at http://wiki.wireshark.org/HubReference There are however some switches that feature port mirroring, please see How to Configure a NETGEAR Prosafe Plus Switch for Mirroring. If connected to a mirrored port, the port must mirror 100% of the network traffic to and from the controller. No filtering should be done. Once a complete capture file has been obtained it can be filtered after the fact using WireShark or EtherReal. Using Wireshark Run WireShark Start a trace by choosing the "Capture" menu and then select "Interfaces" Choose the appropriate interface. Generally, this can be identified by its IP Address, but if not, then the packets increasing are an indication. Press the "Start" button. The trace will start and will be similar to the following screenshot. After an appropriate time, the trace can be stopped by selecting "Capture" menu and "Stop" To save the capture file, choose "File" menu and "Save As".
View full article
Picard Product_Support
‎2018-09-07 11:51 PM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:07 AM

Labels:
  • Andover Continuum
  • CCTV
  • EcoStruxure Access Expert
  • EcoStruxure Building Expert
  • EcoStruxure Building Operation
  • Satchwell BAS & Sigma
  • Satchwell MicroNet
  • TAC IA Series
  • TAC INET
  • TAC Vista
7937 Views

What is the format of the 26 bit Wiegand standard format?

Issue How are the bits allocated in a 26bit Wiegand card format? Environment Access control peripherals data format Cause Although this is an openly published data format, sometimes the actual data bit format is required. Resolution The Wiegand 26 bit format consists of 24 bits of data and 2 Parity bits (Odd and Even) The 24 data bits are split between 8 bits for the Site code and 16 bits for the card number. Giving a card number range of 1 to 65535, and a site code range of 1 to 255. A spreadsheet defining the format can be downloaded here.
View full article
Picard Product_Support
‎2018-09-07 02:34 PM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:07 AM

Labels:
  • Andover Continuum
  • Field Devices
  • TAC INET
2374 Views

Grayed out fields in the basic alarm tab on BACnet b3 controllers

Issue Alarms cannot be created in a BACnet b3 controller because the fields are grayed out. Product Line Andover Continuum Environment Continuum Cyberstation b3 BACnet MS/TP controllers Cause Alarms are created differently in a BACnet controller than with an Infinet controller.  These fields are grayed out since they are not used for alarm creation in a BACnet controller. Resolution There are instructions in the BACnet section in the Continuum help for creating an event notification and then mapping the point and the event notification within an alarm enrolment. For an example see AlarmCreatingAndConfiguring BACnet.doc
View full article
Picard Product_Support
‎2018-09-09 09:49 PM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:07 AM

Labels:
  • Andover Continuum
1686 Views

OPC Server for Andover Continuum and TAC I/NET

Issue OPC Server with third party and alternatives Product Line Andover Continuum, TAC INET Environment System requiring third party connectivity Cause OPC Server to communicate between hardware and the iBMS (intelligent Building Management System). Resolution The OPC server is a software program that converts hardware communication protocol into the OPC protocol. The OPC client software is any program that needs to connect to the hardware. The OPC client uses the OPC server to get data from or send commands to the hardware. OPC Client Servers are used to communicate between BACnet IP interfaces and iBMS (intelligent Building Management System) programs such as TAC I/NET or Andover Continuum. There is also no Continuum OPC Client software to use for a direct OPC link. The best way to integrate from 3rd party EIB or OPC protocols is using BACnet IP on Continuum; there are third party interfaces and gateways that will convert to BACnet/IP and others that go from OPC Client/ Server to BACnet/IP. I/NET OPC For I/NET a great solution is to install a Xenta 913 controller which gives the capability to go with Modbus or BACnet/IP to third party solutions. The I/NET to Xenta 913 allows communication with Continuum BCX, StruxureWare AS-B, and other 3rd Party solutions. Continuum OPC Standard 3rd party gateways are established to communicate between the protocols such as BACnet and Modbus. Andover Continuum has an OPC Server available here. The hardware requirements are Windows NT 4.0 or Win2K. If wanting to run on XP or newer operating systems, please be aware that no testing has not been done with these OS. For more info on the OPC and XDriver, please see OPC Server Integration. Only one instance of the OPC server on a computer. Each system would need a separate PC with license key to connect to the individual systems and host controllers. The Andover Controls OPC server must be running a separate 3rd Party OPC client computer and cannot be on the same computer as CyberStation. From there it is configured to retrieve point values from a the suggested dedicated Infinity (CX) Controller. It is suggested to install a OPC gateway Infinity Controller since this controller will constantly be busy with OPC traffic. Therefore it is the separate third party vendor computer which requires the ACC OPC Server security key, not Cyberstation security key. Both USB and parallel port keys are available. If no choice is available for OS, one alternative is to check on 3rd party OPC servers like Kepware and Matrikon. Note: For Continuum, determine which one of your controllers will become the “Primary Controller” The Server requires that you designate one external Andover Controls Infinity or Continuum controller located on the same network as its “Primary Controller.” This controller must have had the network taught to it prior to selection. (This is done through the “Teach” function in the workstation.) The Server gets its information about the network through this controller. This suggested single controller is designated as the interface through which all point access is obtained. Controller Type Select the type of network where the controller is located. For a NetController, b4920, CX9702 or upgraded Infinity controllers that can be connected to a Continuum network you would select “Continuum”. For older Infinity controllers, select Infinity. Works with any IP level controller. There is no limit on the quantity, but rather it depends on how you tune.
View full article
Picard Product_Support
‎2018-09-10 12:27 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:07 AM

Labels:
  • Andover Continuum
  • TAC INET
4129 Views

Continuum Security Site Verification Checklist and DS Guide

Issue The purpose of this verification checklist is to provide documentation to the Project Manager that the Site Engineer has confirmed the Continuum Security configuration. Basic Settings Access Events Reporting Alarm Event Notification and Alarm Enrollments Door Alarms Other Alarms Time Sync Video including Pelco Digital Sentry IP Camera System Administrative Tasks Other Tasks Basic Checklist Access Events Reporting Checklist Alarm Event Notification and Alarm Enrollments Checklist Door Alarm Checklist Other Alarm Checklist Time Sync Checklist Video Checklist Administrative Tasks Checklist Other Tasks Checklist Environment Continuum with Security enabled Pelco Digital Sentry IP Camera System Cause Beneficial checklist for Verification of security site settings. Resolution Please find the attached pdf document which will walk you through the Continuum Security Checklist. The first section provides step by step instructions for novice users. The second section is the actual checklist where each task should be initialed by the Site Engineer, and the whole document signed by the Site Engineer and the Project Manager. To print the Checklist section of this procedure, start printing on page 21 of the attached checklist. Please find the attached pdf document which will guide you through a Pelco Digital Sentry IP Camera System Quick-Setup
View full article
Picard Product_Support
‎2018-09-10 01:23 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:07 AM

Labels:
  • Andover Continuum
  • CCTV
4465 Views

How may IOU modules can be powered using the ACXX-X power supply?

Issue IOU Modules power requirement Environment CX9900 CX9940 CX9980 ACC LON IOU Modules Cause Limit on AC power supply capacity. Resolution See "Maximum number of I/O modules' in the I-O System Reference Guide document.
View full article
Picard Product_Support
‎2018-09-10 12:15 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:07 AM

Labels:
  • Andover Continuum
24336 Views

What transport type should be used when setting up an ACX57xx, CX9702, or bCX9640?

Issue What transport type should be used when setting up an ACX57xx, CX9702, or bCX9640? (UDP TCP Netcontroller) Environment ACX5720 ACX5740 CX9702 bCX9640 Cause What transport type should be used when setting up an ACX57xx, CX9702, or bCX9640? Resolution The definition on the transport type settings from our Technical Reference Guide states that: UDP - This controller will communicate with other controllers and Workstations primarily using the UDP protocol. TCP - This controller will communicate with other controllers and Workstations primarily using the TCP protocol. TCP/UDP - This controller will communicate with other controllers and Workstations primarily using the TCP protocol, but can also speak to controllers and Workstations that communicate primarily using the UDP protocol.   You can set the controller to use either or both transport types for communication with other devices depending on your specific network requirements. UDP is the preferred option for Continuum devices. See the Andover Continuum Network Ports document for details on what specific ports are required. Three things you need to be aware of with this: Make sure that both the transport setting in the device object and the controllers IE configuration webpage are the same. No matter what transport type you choose make sure that any network firewalls are setup to allow packets through on those ports. View this document for some reasons to use Continuum's reliability layer over UDP rather than TCP.
View full article
Picard Product_Support
‎2018-09-10 06:33 PM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:07 AM

Labels:
  • Andover Continuum
3362 Views
  • « Previous
    • 1
    • 2
    • 3
    • …
    • 111
  • Next »
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

Welcome!

Welcome to your new personalized space.

of