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 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

Issue The RUS.exe utility throws the following error when an attempt is made to activate a license for the first time on a host machine. Product Line Andover Continuum Environment Continuum Cyberstation Hasp Sentinal Continuum Virtual License Cause While it is not clear what causes this error, Product Support has occasionally run into cases where a change to the host machine configuration in some way taints the license fingerprint.  In such cases the license activation file (.v2c) is no longer applicable to the host machine, even though it was created produced from a license information file (.c2v) that was created on the same host. Resolution   There must be no configuration changes made to the host machines on which Continuum will be licenced from the time that the license information file (.c2v) is created until the time when the activation file (.v2c) is received and applied using the RUS.exe tool. This includes the following virtual machine settings... Memory allocation Processor Hard Disk Network Adapter This the following hardware on the physical machine that hosts the virtual machine. Hard drive Network Adapter Memory Processor In some cases when a Cloned host error is occurs upon applying the license activation file (.v2c) to the host machine, rebooting the virtual machine has cleared error.  In cases where rebooting the virtual machine does not resolve this issue, the virtual machine instance will have to be deleted and a new vm created on which the license software can then be installed.    A charge will apply in cases where it is necessary to generate a second activation file (.v2c).     

Issue Guidance is needed for creating a PE program for announcing access by VIP to a door Product Line Andover Continuum Environment Continuum Cyberstation Continuum Net Controller II Continuum ACX 2 Controller Continuum ACX 4 Controller Cause Need a way to identify a sub-set of credential holders, (Personnel Objects), with access to the site and take some action when one of those individuals gain access to a door. Resolution The subset of credential holders is defined via the Department Code which is an attribute of the personnel object.   PERSONNEL CONFIGURATION   Any person with a Department Code of 600 will be identified as VIP by the PE Program.   DOOR CONFIGURATION  The door(s) need to be configured with a department point (InfinityNumeric)  *** In this example we are only doing the entry side of the door, the program can be easily modified to handle the exit side of a door as well. Upon valid access, Continuum will automatically place the department code from the personnel object in the value of the InfinityNumeric configured at the door for department point.   INFINITY PROGRAM CONFIGURATION (Program resides at the controller)  ***In this example an alarm is sent when VIP enters a door, program/configuration can be easily modified to take other actions such as sending email, sounding an audible alarm, etc.   Here is the code for the InfinityProgram  'This program monitors the Front Lobby door for access by VIP individuals 'an alarm is dispatched upon door access by VIPs 'Program is LOOPING/AUTOSTART Object theDOOR Numeric theCODE Object theDepPOINT Line INIT theDOOR = MainLobby 'PUT THE FULL PATH TO THE DOOR TO MONITOR HERE theDepPOINT = theDOOR LastDepEntrdPnt theCODE = 600 'PUT THE DEPT CODE THAT DENOTES VIP HERE Goto MONITOR Line MONITOR VIP_Flag = False If theDOOR ValidAccess then If theDepPOINT Value = theCODE then Goto SendALM Endif Line SendALM VIP_Flag = True Goto MONITOR Line E If TS > 0 then Goto INIT

Issue Some of the fieldbus controller Output values presented on the Infinity controller's webpage do not agree with those values when viewed from Cyberstation and WebStation.  Product Line Andover Continuum Environment Continuum Cyberstation Continuum webClient Server Cause Some controller outputs configuration are limited to specific output types.  On the b3920 for example outputs 9 through 16 cannot be configured as digital outputs.   The ElecType (the outputs electrical type) stored in the Continuum database should match the output configuration in the controller's database.  But this is not always the case.  This can happen when the output configuration was imported from a text file.      Controller output configuration viewed while the workstation is in Online mode   Controller output configuration viewed while the workstation is in Offline mode     When the controller webpage is displayed in a browser, the parent controller (cx9900, cx9680, bcx4040, bcx9640) makes a call for the point value to the fieldbus controller.  If the ElecType for the output which is stored in the Continuum database is incompatible with the controller's output type, the parent controllers' call for the output value will fail. Resolution Switch CyberStation to Offline mode Correct the outputs ElecValue to an appropriate type for the controller output Return CyberStation to Online mode Reload the fieldbus controller

Issue Need to capture steps taken to reproduce a problem or a solution Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, OTHER, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows 7 Windows 10 Windows Server 2008, 2012, 2016 Cause A series of screen captures will help to demonstrate the steps needed to reproduce a problem or a solution. You can use this tool to capture the steps you take as a problem occurs and send the output to someone so they can see a screenshot of each step. Resolution In Windows click on the Start menu button  Type "PSR" Windows 7Windows 7 Windows 10, 2012, 2016Windows 10, 2012, 2016 Open the Problem Steps Recorder Windows 7Windows 7 Windows 10. 2012, 2016Windows 10. 2012, 2016 Click Start Perform the desired tasks Click Stop Choose a location to save the file output The .zip file will contain a .mht file which can be opened in a web browser The screenshots will appear in order  This will be followed by a detailed output of keystrokes and mouse movements. For additional information please refer to Microsoft webpage on this topic: Record steps to reproduce a problem 

Issue Listview columns show a number but the meaning is not shown Product Line Andover Continuum Environment Listview Cause There is some data in a listview where the exact meaning of an integer is not clear. Resolution There is a text file called stsvs.txt located in the Continuum folder that can be viewed to explain the integer to text relationship for many types of object. An example is Activity "CallerCode" which only returns an integer value. Searching the "stsvs.txt" files shows the equivalent text.

Issue What is the limit to the number of objects that can be created in a Workstation? Product Line Andover Continuum Environment CyberStation Cause Want to create a large number of AnalogValue's and BinaryValues in the Workstation for programming and display purposes. Resolution There are no limits to the number of variable objects that can be created in the Workstation. There may well be some practical limits based on the SQL limitations but for all intents and  purposes this limit will most likely not be reached on a full SQL install. There maybe issues with DB size on an SQL Express system but even then, the AV / BV objects don't actually take up that much physical space. As an example, tested this on a v1.94 system and have been able to create over 2500 AV's in my Workstation folder without any issues. NOTE - Running a large number of Programs on a CyberStation can cause issue. System control, etc. should be from a Controller rather than CyberStation.  

Issue Modem commands for the internal modem for the 9680 are needed Environment 9680 RAS Cause Troubleshooting the modem in the 9680 may require knowledge of the Microtech modem and the commands Resolution The Netcontroller II Operation and Technical Guide references "RJ Modem AT Commands Reference" in order to customize the modem initialization string Click her to download RJ Modem AT Commands Reference There is no option for changing the DTMF frequency Guide"

Issue Clarification on documentation which does not indicate the addition of an xPDI8 and an xPDO4 being a valid combination to add to a b3 or i2 controller.   Environment xP modules xPDI8 xPDO4 Cause An addition to a existing i2 controller with an expansion port requires (4) more digital outputs and (8) more digital inputs. However, the documentation does not list the combination of the xPDO4 and xPDI8 as valid. Resolution That combination of expansion modules is not a tested, valid combination. The only tested combinations are those in the attached pages from the i2 Technical Reference

Issue How to add Templates to new Personnel using the Personnel Import Utility. Environment Continuum Personnel Import Utility Access Control Cause It can be unclear as to how to add a Template to new Personnel when creating them from CSV file using the Personnel Import Utility (PIU). Resolution You will need to add the Template field to your attribute mapping list on the configuration tab and modify the XSL file to also include the RefTemplate field.   1. In the PIU attribute list, map the Template data source attribute to the RefTemplate Continuum personnel attribute.   2. Open the CSVToContinuumTransformation.xsl file (or the transformation file you will be using), search for the " " tag and at the tail end of this add the RefTemplate attribute as shown below.   3. Select the CSV file to import and press the Preview button then go to the Transformed Data Tab and you should see the RefTemplate field populated if everything was correct.   4. Upon importing the CS file you should then see the new Personnel with your defined RefTemplate assigned.   Here is a sample transformation and CSV import file

Issue From Continuum version 1.94 when you enable the Operator text when acknowledging alarms prompt, the messages will not save Environment Continuum Alarm acknowledgement Windows  Cause This was caused by a defect in the software which includes version 1.94 to version 2.0  Defect #368 = Alarms - Operator text entered before ACKing an alarm, is not stored in regions other than US. Resolution There is now a hotfix which corrects this issue which you must apply after you have Continuum 1.94 SP1 This hotfix has also been applied and tested successfully on version 2.0  Please download this file and replace the file as instructed in the READ ME.txt document 

Issue What track is used for ABA data? Environment ABA Magnetic stripe cards and readers. Cause Card format information required. Resolution ABA data is usually stored on Track 2 and requires a track 2 reader to decode the data. ABA Magnetic Stripe Format.