Building Automation Knowledge Base

Issue How to change the firmware version in a controller. Product Line Andover Continuum Environment All flash-upgradeable controllers: CX9900, CX9940, ACX5720, ACX5740, all i2, b3, and bCX controllers.  Cause Controller firmware needs to be changed. Resolution Locate the firmware version that you need for each controller you want to change. The Continuum firmware files can be downloaded from the Schneider Electric Ecobuilding Exchange. The downloaded files are often a zip file which includes the release notes in PDF format and the flash file (UPD file). Note: You may need to upgrade or downgrade firmware (see also Is a controller shipped from the factory with the latest firmware revision supported in older versions of Continuum?) Make sure you check the document Andover Continuum Software and Firmware Compatibility Matrix for the appropriate firmware version for your system.   Copy the file to a disk drive accessible to your CyberStation workstation. Edit the controller object in ContinuumExplorer and click on the "Update OS" button. Browse to the file location in step 2 and click "Open". A progress box "Updating Controller OS..." will appear. During this time the controller is reset and not functional.  Once complete, and if successful, you will get  a dialog box indicating that the upload was successful and the controller will return On-Line momentarily. Click OK. Click the refresh button in the controller editor. Once the controller is on-line the version field should indicate the new version. At this point some controllers may need a reload, others will be reloaded from flash memory. This depends on the controller type. For example, the CX9900 has no flash memory and therefore will need to be reloaded. This procedure also applies to upgrading controller options such as adding Xdriver support. In this case a UPD file will be provided by the Repair Dept. In the case of added Xdriver support, after doing the Update OS procedure the version will not change. Look at the controller Options tab after it comes back online following the upgrade. The information here, such as a non-zero entry in the numbers next to the appropriate Xdriver Commport will be changed. The above procedure was based on an IP level controller such as the CX, bCX and ACX II. Infinet and MSTP controllers are done in a similar manner. IOU models are also upgraded similarly via the "Update IOU" button in the IOUModule editor. However, the files are .IOU files instead of .UPD files and the versions are in the fourth pair of characters in the Program ID field.  

Issue Problems installing Continuum Continuum will not install correctly SQL Express will not install correctly Product Line Andover Continuum Environment Continuum Cause Cyberstation fails to install or run correctly Resolution Continuum Cyberstation can normally be installed very quickly (usually less than half an hour) on a normal windows installation that fits within the Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation, this would include SQL for a stand alone (Single User) installation. The Continuum Cyberstation uses many Windows components and services, and runs many executable files and batch files within its normal operation. We do not have a published list of services that Continuum requires to run since requirements vary depending on the site configuration. We obviously use Active Directory and .NET, RPC, MSMQ, SMNP, and all DCE services. SQL Server Management Studio Express is a free down from Microsoft and is an excellent tool for checking the SQL install Up to v1.94sp1 SQL2005 https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-2017 v2.0 and beyond SQL2012 https://www.microsoft.com/en-us/download/details.aspx?id=35579 There are a few items that can interfere with the smooth installation or running of a Continuum Cyberstation Ensure the workstation PC is within the Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation for the version being installed, especially Windows service packs and .NET framework versions. Ensure the minimum requirement for the workstation PC, is observed, as stated in the Cyberstation installation guide. Ensure the recommended requirement is observed, if the Cyberstation will be used for video or other more intense operations.  Local administrator accounts are required for some version of installation with passwords set. See How to create a local administrator log on in Windows. Automatic updates. See the individual installation guides, however, it is normally wise or even mandatory (depending on Continuum version) to leave them off, as updates include service packs and .NET framework updates that would take the installation off the Compatibility Matrix and could compromise the installation. There have also been other updates that have caused issues. See 5 below. MSXML6 Update SQL Express install fails on MSXML 6 Firewall & Anti virus issues. These should be disabled during installation. Issues with starting Continuum after new installation (Anti-Virus and Firewalls) Error when starting Continuum 1.9: Cannot find acc video recording service Access denied errors when installing Continuum or Webclient Crash of ACCDataServices on start up or running Continuum Another example of antivirus interfering with Continuum install is getting Microsoft Visual V++ error when opening a pin point graphic, when the install is completed with AV "webRoot" enabled.  SQL2005 Express (1.82SA onwards) When creating the sa password ensure the password is tested in notepad before typing in Database Initialisation, as if the keyboard is not set up correctly, you may be using an illegal character (eg " rather than @, in this case you will need to uninstall SQL, before re-installing via Database Initialisation) Custom Windows Images - Some Windows Images installed on new PCs include modifications that interfere with the Cyberstation installation, always use a clean MS Windows if possible, as this avoid such issues. HP Protect Tools - MFC error on Continuum startup or Continuum won't start on HP PC IT tampered Windows & domains. It is important to install Continuum with local Administrator rights as item 3, above, beware of PCs locked down by IT departments, the installation can be slow and difficult Error 1001, windows event log full. Error 1001 when installing Cyberstation or Webclient Problems with MSMQ (MicroSoft Message Queue) can cause install problems MSMQ errors and Continuum fails to start MSMQ error starting Continuum. "There appears to be a problem with the configuration of this system. Please check to make sure that you have correctly installed MSMQ." MSMQ error message: "Appears to be a problem with configuration of system please check to make sure you have MSMQ correctly installed" Trying to install CyberStation 1.9x.  It completes but then pops up 6 errors saying "Access denied" "Access Denied" messages during a CyberStation 1.9x installation Microsoft Update issues see Windows updates and Continuum Continuum Version 1.93 Fails to install. IssueReceive AccDataservice errors on startup. Continuum Version 1.93 Fails to install For Windows 7 installs see Disabling administrator rights messages in Windows 7 OS and above (Also known as UAC / User Account Control) If you see a Continuum install Error -  "Error, unable to open documentation list \misc\doclist.txt" then you are running the incorrect "setup.exe", you should install using the one in the Cyberstation root directory, not the one in the Continuum sub-directory. It has be found that Microsoft "Strong" passwords are required not only for the SQL sa password but also for Andover97 password, see Password requirements for Andover97 SQL Login for details For a v1.82 Stand Alone and beyond, if the install admin user has no password, it has been seen that the tasks (CS_Minute, CS_Distn and CS_hrly) are not always created, see Getting AccDataServices error with AlmUtil.dll error when closing Continuum If a Continuum re-install, on a LAN CyberStation is required (were some part or program has broken) then uninstall Continuum, then re-install. A workstation initialization may be required. Deleting the Continuum directory and clearing out Continuum from the registry may also be required (check for any local held graphics, .mnu files, etc. before deleting the Continuum directory) Seeing "Can not change directory to Continuum" see Cannot change directory to Continuum error during installation of Cyberstation Re-Installing Continuum is sometimes required, for example, an automatic update to the Antivirus software has been seen to stop listviews from working. The only way around this was to uninstall Continuum then re-install it. There are different levels to uninstalling possible, 1.Simple uninstall. 2. Uninstalled followed by removing the Continuum Directory and other .ini files. 3. Uninstalled followed by removing the Continuum Directory and other .ini files, followed by cleaning of the registry.  In a few more recent cases where Controllers will not come online (after testing for other errors) or where persistent MSMQ errors cannot be resolved, a complete re-install of the OS may be required to ensure a "clean" Windows OS is available. Uninstalling some Continuum required programs can cause issues, especially SQL. see Problem uninstalling software. The following method has been seen to work: Stop service, uninstall, delete folders, run CCleaner (or Revo) and clean registry, reboot, run CCleaner (or Revo) and clean registry, reboot, re-install SQL Shared Memory errors seen with 32b systems and v2.0SP1, see "Shared Memory" error on startup of Continuum

Issue How can Continuum be setup to read the 32 bit serial number from a Mifare smart card for use in access control? Product Line Andover Continuum Environment Using iClass serial number readers: R10, R15, R30, R40, RK40 Custom Wiegand, AccessFormat array Custom Format Cause Mifare smart cards that have been provided and programmed by others may not have the keys available to allow a reader to access the data on the card. Without sending the cards away for re-programming how can the card still be used for access control. Resolution The HID iClass readers (R10, R15, R30, R40, RK40) have the ability to read the 32 bit serial number from a Mifare Smart card. These readers will output a single 32 bit Wiegand string representing the card serial number. To use this on Continuum: Create a numeric point called "AccessFormat" and define it as a manual array with 19 entries. Create a Plain English program in the controller to fill up the array with values as per the Mifare Serial Number spreadsheet. In the door configuration select "Custom Format" and ensure one of the 4 site codes is set to 0. Swipe the card at the reader and open a list view of Events, this will show the card number as the serial number from the card. Create a new Person with card type Custom Wiegand, Site code 0 and set the Card number to the serial number as read in the list view. This may be a 9 or 10 digit number. Notes: If using card numbers in Plain English Programs or displaying in Pinpoint Graphics, you will be restricted to using a maximum of 6 digit numbers (maximum card number being 999,999). See Loss of resolution on metering points when the number is 7 digits or longer for details on this restriction. The old style Personnel editor will not allow the entry of site codes of 0. Use Personnel Manager or set attributes in List Views of Personnel.

Issue Both BACnet MS/TP and Modbus typically provide a robust and reliable communications channel allowing the Automation Server to effectively manage a large collection of equipment over extended distances. When the system does not come up operating as expected due to the communications integrity, considerable effort can be consumed troubleshooting or working-around the fault observations. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, TAC IA Series Environment Automation Server with BACnet MS/TP or Modbus RS485 networks connected to Port A or Port B. Cause The configuration of the RS485 network can create conditions that reduce the tolerance for EMI noise on the bus, electrical ground differences, transmission signal loss through the cable and/or component performance. Resolution A collection of application notes and Quick Start Best Practices Guides are available on the subject of BACnet MS/TP and Modbus RS485 network connections to the StruxureWare Automation Server.  These application notes and quick start guides provide recommendations in the areas of – BACnet MS/TP & Modbus RS485 Network Termination Network Biasing Options and Techniques Unit Load and associated Maximum Node Count Recommendations Isolated RS485 Interfaces and related Expanded Unit Load Cable Specifications and Suggested Cable Selections Cable Routing and Recommended Lengths The documents describe configurations of cable, network length, node counts and bias arrangements providing compliance with the EIA/TIA-485 Standard and TSB-89-A Guidelines with the objective of optimizing system tolerance for noise, grounding and transceiver component variations.  Most of the application notes and quick start guides target specific product families which include the Andover Continuum b3 Family, TAC I/A Series MNB Family, Legrand Power Meters and the Viconics VT7000 series sensors. There is also an application note and quick guide directed toward other “Generic” RS485 MS/TP and Modbus devices where the user is guided through a sequence of information collection steps to determine the appropriate recommendations.  The collection of application notes and guides are available on the Schneider Electric download center. The list of links below will take you to the applicable download page. AN01-RS485-Generic Application Note – General MS/TP & Modbus I/F to Automation Server Quick Guide-RS485-Generic Best Practices Guide - General MS/TP & Modbus AN02-RS485-B3 Application Note – Continuum B3 I/F to Automation Server Quick Guide-RS485-B3 Best Practices Guide - Continuum B3 I/F AN03-RS485-MNB Application Note – I/A Series MNB I/F to Automation Server Quick Guide-RS485-MNB Best Practices Guide – I/A Series MNB I/F AN04-RS485-Legrand Application Note – Legrand Meter I/F to Automation Server Quick Guide-RS485-Legrand Best Practices Guide – Legrand Meter I/F AN05-RS485-VT7000 Application Note – VT7000 Series I/F to Automation Server Quick Guide-RS485-VT7000 Best Practices Guide – VT7000 Series I/F Note:    If using the download center for the first time, you will need to register. See Register for The Exchange Download Center for more information. The Download Center requires the use of Internet Explorer (version 8 or higher), Google Chrome or Firefox browsers. Additional information is available in the Hardware Reference Guide Access the StruxureWare Building Operation Web Help. Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.

Issue What is the limit of how many devices a BACnet controller can know about (Known devices) and what does that mean. Product Line Andover Continuum Environment BACnet bCX bCX4040 Cause More details required about Known devices Resolution The known device limit of a Continuum Ethernet level BACnet controller is 255 and for a B3 level MSTP controller it is 32. This limit means is if a controller needs to either subscribe to a COV from another controller or deliver alarms (Event notifications) to a workstation, that each one of these target devices is a known device. So, for example, if a b3 controller is subscribing to COV's from 30 other controllers and needs to deliver alarms to 3 WorkStations, it would require 33 known devices and the last request for a target device would fail. If a Controller is making 30 COV Subscriptions from one a single controller that would only count as 1 known device. This limit does not apply to the number of other controllers which a COV exporter can deliver COV data to. For example, if a controller had a global point (OAT) that 50 other controllers needed to subscribe to, this is allowed because each COV subscription has within it the target controller's address information and does not use the known device limit. There are two cautions that must be considered. Refer to What are the differences between Standard Continuum Import/Export and Continuum BACnet COV?. Each COV subscription in an exporting controller takes away user memory. Each subscription uses approximately 56 Bytes of user memory. So the limit of how many other devices can subscribe COV's in an individual controller is limited by free memory in the exporting controller. NOTE: To reset  the known devices following a change in the Controllers that will effect the number of known devices, the controller needs to be reloaded.

Issue What specification should BACnet MS/TP cable meet? Product Line Andover Continuum, EcoStruxure Building Operation Environment MS/TP BACnet devices Cause Often an incorrect cable type is used when wiring MS/TP devices causing unreliable communications. Resolution The BACnet Controller Technical Reference defines the following cable specification for a MS/TP cable: RS-485 Cable Specifications: Cables used to form the RS-485 network should conform to the following specifications: Wire Size: 22-24 AWG Cable Type: Twisted-pair, copper wire, tinned Shield: Braid Nominal Impedance: 100-120 Ohms Velocity of propagation: 78% Capacitance: <12.5 pF/ft (~ 41pF/M) between conductors and < 22 pF/ft (~72pF/M) between the conductor connected to ground and the next conductor. An example of a cable that meets this specification is Belden 3105A. Also check out the SmartStruxure-RS485-Network Installation Quick-Help video on the Exchange.

Issue If an application hangs or crashes, Windows systems are sluggish or have problems, or new software fails to install properly one of the first places to look for information on what may be happening is the Windows Event Log. Product Support personnel may ask to see a copy of the Windows Event Log. Product Line TAC INET, TAC Vista, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, Field Devices, EcoStruxure Building Operation, Other, EcoStruxure Building Expert, Access Expert, Security Expert Environment Windows Operating System Cause If an application hangs or crashes, Windows systems are sluggish or have problems, or new software fails to install properly one of the first places to look for information on what may be happening is the Windows Event Log. Resolution   Open the Event viewer by one of the ways below: Start Event Viewer by pressing Windows key + R to open the Run dialog box and type eventvwr. Right-Click on "This PC" and select "Manage" then navigate to Computer Management (Local) > System Tools > Event Viewer. Select the type of logs the need to be exported. Application, Security, and System logs in the Windows Logs and Schneider Electric Security Expert logs under Applications and Services Logs (for Security Expert cases) are required.  For each log, view recent messages then click the "Action" menu and select "Save All Events As". Enter the log name, include the log type (Application, Security, or System) in the log name, and location the click "Save". For non-English Windows, make sure to select English (United States) in "Display information" then click OK. 

Issue While Continuum controllers and EcoStruxure controllers do not utilize Power over Ethernet (POE), can plugging in a Continuum or EcoStruxure controller into a POE switch damage either the POE port or the controller? Product Line Andover Continuum, EcoStruxure Building Operation Environment PoE Ethernet Cause Controllers must be installed on a subnet served by a POE switch. Resolution According to the IEEE standard, a POE switch shall determine if the connected device is POE capable before turning on the power. The detection if a connected unit is POE capable is done by measuring the resistance between the pair #2 - #3 and pairs #1 - #4. On a POE capable unit the resistance is 25kohm, with some tolerance. If it is lower or higher it is not considered to be POE capable. As there are no Continuum or EcoStruxure ethernet controllers that apply a 25K ohm load, a properly functioning switch port will not enable PoE power and the device will not be damaged. Find information on the PoE standard in the Fundamentals of Power Over Internet (PoE) PDF

Issue After the successful installation of Continuum 1.9x, users are receiving a DCOM Permission error when logging on to Continuum webClient. The error is intermittent. Product Line Andover Continuum Environment Microsoft Server 2008 Standard Microsoft Windows 7 Continuum 1.9x and 2.0 Continuum webClient Server Remote Desktop Cause When a remote desktop connection is made on Windows 7 or Windows 2008 Server the console occasionally gets locked. It stays locked until the local session is restored with a logon. Resolution Create a .bat file. **************************************************************************************** @echo off REM Restores session 0 to the "console".  Thus allows local machine REM to return to the service accounts desktop without being locked. REM ------------------------------------------------------ tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 1 /dest:console @%windir%\System32\tscon.exe 2 /dest:console **************************************************************************************** Place this file on the desktop of the Continuum webClient Server system. When you disconnect from the remote session run this Bat file. Do not just disconnect. This must be run "As an Administrator." This will disconnect the session and restore the console.

Issue Accessing Continuum Security Key information using MMC to determine what features are enabled. Product Line Andover Continuum Environment Continuum Security Key Cause Users need the ability to know what version of Continuum is supported on their key Resolution Note: The MMC method for viewing enabled key features mentioned below no longer works with Windows10 or greater and because of CyberSecurity issues ActiveX controls have been deprecated by Microsoft in favor of more secure web technologies.  This feature will not be updated for Cyberstation.   Some Cyberstations do not have Microsoft Office with Excel installed but the security key information may be accessed using Microsoft Management Console instead. Go to Start> Run, Type in MMC.exe and click OK Select File> Add/Remove Snap-in Click the Add button (bottom left) Click On ActiveX control and click Add Click Next while in the Insert ActiveX Control dialog Scroll Down until you find SecurityKeyReader Control and highlight it and click Next Leave the default name and click Finish Close the Stand Alone Snap-in dialog Click OK on the Add/Remove Snap-in dialog Click on the SecurityKeyReader Control and highlight it and it will display the Key info If you want to save it, File> Save and enter the name SecurityKey.msc Windows 7  (32-bit system) Go to Start> Run, Type in MMC.exe and click OK (64-bit system) In Command Prompt  enter  mmc /32 Select File> Add/Remove Snap-in Click On ActiveX control and click Add Click Next while in the Insert ActiveX Control dialog Scroll Down until you find SecurityKeyReader Control and highlight it and click Next Leave the default name and click Finish Click OK in the Add or Remove Snap-in dialog Double click on the SecurityKeyReader Control in the right-hand pane and it will display the Key info If you want to save it File> Save and enter the name SecurityKey.msc To reopen Go to Start> Run, Type in MMC.exe and click OK File> Open and select Ex. SecurityKey.msc To copy to another computer File Search> Enter SecurityKey.msc (or whatever you named it above) Copy the file to the other computer and paste it into the Administrative Tools folder Ex. C:\Documents and Settings\Administrator\Start Menu\Programs\Administrative Tools  

Issue There is only 1 input available, but the end-user wants more than 1 sensor to be connected, where the reading will be averaged. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 Cause The wrong sensor type or incorrect wiring might have been used. Resolution 4 resistive sensors of the same type are required. Depending on scenario, 2 sensors may have to be fitted adjacent to each other, or fit 2 sensors into 1 sensor housing to achieve the correct number of zones to be monitored. For wiring follow the drawing below:

Issue Windows System Information may be requested by Technical Support to assist with a reported issue. Product Line All Product Lines Environment Microsoft Windows Operating System Cause Unspecified cause. Resolution Press WINDOWS + R on the keyboard of the Windows system that you wish to obtain the report from. The Windows key is usually located between the CTRL and ALT keys and has a picture of a flag on it. Type Msinfo32.exe and click OK The System Information tool will start. Click on File > Sav When prompted, save the *.nfo file to an accessible location. Email the *.nfo file to your support representative.    Note: This application can also be accessed from Start, All Programs, Accessories, System Tools, and System Information. Using this method will open the System Information for XP and Windows 7, 32 and 64-bit computers. Refer to: Description of Microsoft System Information (Msinfo32.exe) Tool

Issue What SQL collation is supported by CyberStation Product Line Andover Continuum Environment CyberStation SQL Server Cause Which SQL collations are supported by CyberStation. Resolution Only the SQL_1xCompat_CP850_CI_AS collation has been tested with CyberStation. Note: In more recent versions of SQL server (i.e 2005), you can have the Collation on a per-database basis so ContinuumDB will have its collation set to SQL_1xCompat_CP850_CI_AS and another database can use a different collation setting. Also when the continuum database is restored it will retain the original collation that it was created with.

Issue CyberStation is unable to connect to the database. ODBC test also fails when testing the connection to the database. Product Line Andover Continuum Environment CyberStation SQL server SQL management studio Cause SQL server not on UPS. Server shut down due to a power failure. Looking at the ContinuumDB using the SQL Management Studio shows the database has been marked as suspect.  ContinuumDB (SUSPECT) The database may be marked suspect for the following reasons System Issues Transaction Log File is Missing SQL Server Crash Database Files are inaccessible SQL Server Database Operation Failures Due to Improper shut down of SQL Server System (as mentioned above) Due to Sudden Power Outage Low Disk Space Issues Hardware Failure Resolution The database may have been damaged by the ungracious shutdown. The restore option is grayed out and must first be re-enabled before a restore operation can be allowed. How to recover a database in suspect mode Clear the suspect mode of the database using sp_resetstatus DatabaseName. This will clear the suspect flag and make the database available online. The SQL Server must be stopped and re-started. Change the database status to Emergency using the following command. ALTER DATABASE DatabaseName SET EMERGENCY; Restrict database to single user by changing the access mode as mentioned below ALTER DATABASE DatabaseName SET SINGLE_USER; If the restore option is now enabled skip step 4 Run the CHECKDB command with “REPAIR_ALLOW_DATA_LOSS” option. This option should be tried as the last option as it always behaves the way it is named. We are not sure of what data it removes. DBCC CHECKDB (DatabaseName, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS, ALL_ERRORMSGS If the repair operation is successful the database is now usable but if a recent backup is available it is strongly recommended to restore the database. Restore the most recent backup of the Continuum database. Set the ContinuumDB owner using the query SP_ChangeDBOwner 'Andover97'  

Issue A b3 controller that is shown as offline in CyberStation can incorrectly change to online when RoamIO2 is connected to the bus.   Product Line Andover Continuum Environment RoamIO2 bCX CyberStation b3 Cause When a RoamIO2 is connected to the MSTP bus and the BACnet Service Tool software is started, it assigns itself a BACnet MAC Address. It may assign itself the BACnet MAC Address of an offline b3. If at the same time you are running a listview of b3 controllers on that bus in CyberStation, and displaying commstatus, the offline b3 with that BACnet MAC address will appear online. However, attributes such as VersionNum, BACnet DeviceID, Port, and InstanceID will be blank in the listview - tipping you off that this is bogus.   Resolution Be aware of this situation and add the attributes described in the cause section above to confirm what you are seeing.  

Issue Receive an Error message "Outlook not installed"  when starting  Continuum Product Line Andover Continuum Environment Windows 7,  64Bit Continuum  1.9X Microsoft Outlook  64 Bit. Cause Outlook 64 Bit is not supported at this time. Resolution Uninstall 64-bit Outlook.  Then install 32-bit Outlook.

Issue The SQL Server 2008 is running the 64-bit version as well as the Continuum Workstations are using 64-bit Operating Systems. In the interest of increasing the SQL access speeds can the ODBC connection between them also utilize the 64-bit ODBC driver? Product Line Andover Continuum Environment Continuum v1.94 (or greater) Microsoft SQL Server 2008 64-bit Microsoft SQL Server 2012 64-bit Microsoft SQL Server 2014 64-bit Microsoft SQL Server 2016 64-bit Cause Want to know if the SQL access speeds can be increased by taking advantage of using the 64-bit ODBC drivers. Resolution The Continuum application itself is a 32-bit application, this will require the 32-bit ODBC drivers to make a connection to the SQL Server. Even though we support Continuum in a 64-bit environment, it is still only a 32-bit application so the 32-bit ODBC drivers are used for the SQL connection. Be aware that this is just the communications on the SQL side, the SQL application itself will still process data at 64-bit speeds if the 64-bit version is used.

Issue Continuum has a limit on the number of entries that can be added to the BBMD table in the bCX and CyberStation. Do the AS and ES servers have the same limitation? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS-P, AS-B) Building Operation Enterprise Server Continuum Cause Limitations must be known for engineering design. Resolution The number of BDT Entries you can add to the BBMD table in EcoStruxure Building Operation is limited only by the available resources, so for all practical purpose there is no limit. Device BDT (Broadcast Distribution Table) FDT (Foreign Device Table) ES only limited by memory 64 (up to v1.4) 600 (from v1.5) AS only limited by memory 64 (up to v1.4) 254 (from v1.5) ASB only limited by memory 50 bCX1 32 32 Cyberstation 1024 1024 Always refer to the Architectural Guidelines for the latest information

Issue For various reasons, it is sometimes necessary to change a b3's mac ID. For example, a b3 that is removed from a site and will later be used at a different site needs to have its mac id reset to factory default to avoid the possibility of introducing a duplicate mac id. NOTE: To set the MAC ID to the factory default you need BACnet Service Tool version 1.110004 or newer.   Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum b3 Controller Continuum Service Tool RoamIO2 BACnet Service Tool Cause The MAC ID needs to be set or changed on a b3 controller. Resolution IMPORTANT: If the b3 has previously been assigned a valid mac id then proceed to step #1. If the b3 has factory default slave mac id then see  CHANGING MAC ID ON A BRAND NEW B3 FROM THE FACTORY below Make sure the b3 is disconnected from the MSTP network then connect the RoamIO2 directly to the b3 using the service port. Launch the BACnet Service Tool and de-select the 'By Networks' and 'BACnet only' menu options in the view menu. Click the green icon to make the RoamIO2 sync to the baud rate of the b3 and discover it. In the 'Tools' menu select 'Set Offline B3 Mac Id' as shown below.  In the 'Modify MAC Id' window enter the b3's serial number and the new mac id to be set then click Apply. (NOTE: To set the MAC ID to factory default enter 172, DO NOT USE ZERO) To set the MAC Id to the factory default you need BACnet Service Tool version 1.110004 or newer. Tested working on beta version 1.119903). This beta version is attached. Download it and remove the .txt at the end to make it a zip file, unzip then see the readme.txt. A feedback message 'Success! will be returned if the MAC id was changed EXCEPT when setting the MAC Id to factory default (172) When setting the MAC Id to the factory default you will NOT get SUCCESS feedback, this is because the default id of 172 is a slave id (chosen because in hex it is AC for Andover Controls). Slave Ids are not allowed to initiate communication on the MSTP network. So, as a result of that, the b3 is unable to report to the RoamIO2 that the id was successfully changed. A visual sign that the ID was changed to 172 is that the TD led on the b3's RS485 port will shut off. Disconnect and re-connect to have the RoamIO2 communicate with the b3 using the new MAC id (unless you changed it to the factory default of 172). CHANGING MAC ID ON A BRAND NEW B3 FROM THE FACTORY The RoamIO2 can also be used to assign a mac id to a brand new b3 which has a factory default mac id of 0xAC (172 decimal) but the steps are a little different. In order for a RoamIO2 to be able to send communication packets to the b3, it first has to sync up with the baud rate of the b3, it does by listening and analyzing the packets sent by the b3 until it is able to determine the baud rate. As mentioned before, the factory default mac id of a b3 is slave id 172 which prohibits the b3s from sending out packets and makes it impossible for the RoamIO2 to determine the baud rate. There are several ways to work around the baud rate issue... Set the baud rate manually. Click on the green icon to attempt to connect the RoamIO2 to the b3. You will get an error that the baud rate could not be determined, click YES to proceed anyway From the 'Tools' menu select 'Set B3 Baud Rate' and set the baud rate to what you believe the last baud rate was for the b3. (The factory default baud rate is 19200) You should now be able to set the mac id per the steps above. NOTE: You may have to try all the baud rates until you find the one the b3 is operating at.

Issue Controller is unresponsive and does not respond to a hard reset or power cycle with the battery disconnected..  CPU light remains on constantly. Product Line Andover Continuum Environment InfinityController, b3 Controller NetController II, CX9680 ACX57 bCX Cause Controller stopped functioning after power cycled. Resolution Test controller with a known working PS power supply and/or test the supply voltage is correct If the controller still does not respond to a hard reset then return for repair. See the appropriate manual for reset instructions