Issue When presenting a card to a card reader I see a message in the Active Event view that says "Custom Card" instead of "Valid Access" Environment AC1 ACX78x ACX57xx Netcontroller 1 Netcontroller 2 Active Event View Access Event Cause This is being caused by the controller not having an "AccessFormat" numeric set up.  The AccessFormat numeric is used to define the fields when using a Custom Card. Resolution   Use the below procedure to set up a Custom Card.  This procedure uses a Corporate 1000 35 bit card as an example. Custom Card Format for:  HID Corporate 1000, 35 bit Here is the information on creating a custom format in the Andover System. A custom format must be used when the card format is not one of the standard pre-defined formats. Only one custom format can be used in an ACX controller or NetController. Setting Up a Custom Wiegand Format In each ACX700 and ACX780/781 and NetController, create an InfinityNumeric point called AccessFormat (use this spelling exactly!). During the creation process, attach a manual array (log) with 19 entries to the point. Create he following Infinity Program, once created, can be copied to all other access controllers that need it. Program Name: SetArray FlowType: FallThru AutoStart: True Code: Set AccessFormat[1] to 35      'overall number of bits Set AccessFormat[2] to 0        'control mask Set AccessFormat[3] to 0        ' manufacturer’s code Set AccessFormat[4] to 0       ' start bit of man. Code (first bit is 0, not 1) Set AccessFormat[5] to 0       ' end bit of man. code Set AccessFormat[6] to 2       ' start bit of site code Set AccessFormat[7] to 13      ' end bit of site code Set AccessFormat[8] to 14      ' start bit of card number Set AccessFormat[9] to 33      ' end bit of card number Set AccessFormat[10] to 0      ' odd parity mask, first 16 bits Set AccessFormat[11] to 0      ' odd parity, next 16 Set AccessFormat[12] to 0      ' odd parity, next 16 Set AccessFormat[13] to 0      ' odd parity, next 16 Set AccessFormat[14] to 0      ' even parity, first 16 Set AccessFormat[15] to 0      ' even parity, next 16 Set AccessFormat[16] to 0      ' even parity, next 16 Set AccessFormat[17] to 0      ' even parity, next 16 Set AccessFormat[18] to 0      ' card number multiplier Set AccessFormat[19] to 0      ' card number divisor In each Door Configuration, select the Custom Wiegand card type. Other card types may also be selected. For each Personnel, select the Custom Wiegand card type, and enter the correct card number and site code.   If the card is not working, check the Event Log and determine the cause. For Invalid Card Parity errors, set all the parity masks to 0 and try again. For proximity cards, the parity check may be eliminated with little consequence.

Issue Cannot create a Netcontroller2 in CyberStation version 1.74 Environment CyberStation version 1.74 Netcontroller2 CX9680 Cause CyberStation version 1.74 does not support Netcontroller2 Resolution Install Sp2 for CyberStation version 1.74 to support the Netcontroller2

Issue Does a single controller (2nd generation controllers such as NC2 and bCX) support two(2) Modbus TCP/IP xDrivers on two(2) different comm ports?    Product Line Andover Continuum Environment Modbus TCP/IP XDriver NC2 (CX9680) bCX4040 Cause Need to have Modbus TCP/IP interface with 3rd party devices for both Server mode (Slave mode) and Client mode (Master mode).  Resolution You can have only one Modbus TCP/IP XDriver on a Controller(NC2 or bCX).  In order to have Modbus TCP/IP XDriver for both Server mode and Client mode, there should be two different CX controllers, and  different mode of Modbus TCP/IP XDriver should be installed and configured on different controller.   Note: This also includes any IP XDrivers. You can only enable one IP XDriver per Controller. (Ex. You can not enable a BACnet IP XDriver on one comm port and a Modbus IP XDriver on another, you would need two Controllers for this - one IP XDriver on each)

Issue Sending an email from the controller via PE or Web Page shows incorrect sent time. Environment NC2 - CX968x ACX2 - ACX57xx bCX Cause Time settings not configured correctly from controller's web page. Resolution From a web browser login to the controller's web configuration (point your browser to the IP of the controller) Go to "Controller Configuration\Time Setting" Enter the appropriate UTC offset for your time zone, for example if the controller is in the Eastern time zone enter -300 Use the "Daylight" Savings option to specify whether daylight savings time is in effect Finally click on the "Submit to Controller" button, there is no need to commit changes and re-start the controller.

Issue The StandAlone workstation is not getting alarms delivered to the active alarm view. Environment Continuum Cyberstation standalone. CX Controller Cause Alarms are not being delivered to the workstation. When the point is edited, the point shows that it is in alarm. Resolution Cyberstation was gracefully shut down. Start Continuum Database Initialization for StandAlone Enhanced Alarm Delivery was deselected. Database was initialized Continuum was restarted Points were set to an alarm value Alarms were delivered.

Issue When trying to edit or create a new Plain English program the editor fails to open. Environment CyberStation Plain English Editor Cause Corrupted PlainEnglish.ini file Resolution Open Windows Explorer Go to the Windows directory Find the PlainEnglish.ini file and delete it. When the Plain English editor is opened after this file is deleted it will recreate a new PlainEnglish.ini file with all the default settings.

Issue What is the default IP address for BCX, ACX57xx, CX9702 & Netcontroller II? Product Line Andover Continuum Environment Controller Netcontroller II (9680) BCX ACX57xx CX9702 Cause Default IP address for BCX, ACX57xx, CX9702 & Netcontroller II Resolution The default for all these controller types is: IP address: 169.254.1.1 Subnet: 255.255.0.0 Gateway: 169.254.0.0

Issue Is there a way to tell if the battery is bad in a controller? Product Line Andover Continuum Environment BCX - 4000, 4040, 9640 ACX5740, 5720 Netcontroller II 9680 Infinet II controllers B3 controllers Cause Determine if a battery is good Resolution Battery health is tricky to measure.  Open circuit voltage COULD look ok with a marginal battery.  The only sure way is to pull the power on the Netcontroller and see if it holds the data for our specified time.  Most sites will not want to take their controller down for that long. Take the battery out and measure it with a voltmeter, it should read not much lower than --- BCX and ACX model controllers  3.6V Netcontroller II, Infinet II and B3 controllers 2.7V BCX Spec Battery section: Replaceable, rechargeable battery. Provides 30 days typical accumulated power failure backup of RAM memory All data stored in Flash on power loss. ACX Spec Battery section: Replaceable, rechargeable battery. Provides 7 days typical accumulated power failure backup of RAM memory All data stored in Flash on power loss. I2/B3 Coin type battery: The small coin battery in the i2 / b3 is rated 41mAH;  if you calculate based only on the SRAM and RTC current draw you get about 85 days.  Netcontroller II: The battery type here and SRAM are typical of infinet II controller battery life and will maintain backup of SRAM down to 2.7v. NOTE: Backup Flash is non-volatile memory and once written will hold unless manually cleared. SRAM is a part of memory that holds information as to where to start programs when power is re-applied to the controller in cases of main power loss. The problem is that battery life is highly dependant on number of charge / recharge cycles which is beyond our control.   You don't find the battery manufacturers giving such specs either.  Example:  The coin cells in our i2 / b3 have a shelf life "up to 10 years". Day to day use it is suggested that batteries should be replaced every 5 years.

Issue There is a need to get logging details for troubleshooting video integration issues in Continuum. Product Line Andover Continuum Environment Continuum Windows XP Windows Vista Windows Server 2003 Windows Server 2008 Cause There is an issue with the video integration and there are specific instructions to enable video troubleshooting in Continuum. Resolution Continuum versions 1.9x and above contain a helpful tool for troubleshooting video integration issues To enable video logging, follow these instructions: Shut down Continuum on the Cyberstation you will use to create the log file Using Windows notepad, edit the file log4net.config located in C:\Program Files\Continuum At the bottom of the file locate the following text:  <root> <level value ="WARN"  /> Change WARN to DEBUG (Ex. level value ="WARN" ---> level value ="DEBUG" ) From the pull down menu, File> Save and close the file         4.Start Continuum and test one isolated procedure at a time (Ex. video isn't displaying on alarm)         5. Email the video.log file from the C:\Program Files\Continuum folder to the support engineer for analysis Note: Make a copy of the video.log file ( to save the file ) and then delete the original. A new video.log file is created each time Continuum is started with the level value="DEBUG" set Video log changes for 1.92/1.93/1.94 The instructions to enable the video.log are the same as for 1.91, however the results have been broken into a number of different files VideoAdmin.log - used for configuration  AccVideoRecordingServc.log - used for camera learn VideoLayout.log - used for video layout  AlarmView.log - used for video alarms Easiest way to see what file was written to is to sort the Windows folder by the Type column and check the txt file(log) dates Note: In Microsoft Vista or Windows Server 2008, if account control is not disabled the video log files may get written to "C:\users\username\AppData\Local\VirtualStore\Program Files\Continuum" Caution: Once the debugging process has been completed, go back into the log4net.config file and edit the file. Change the DEBUG to WARN (Ex. level value ="DEBUG" ---> level value ="WARN") From the pull down menu, File> Save and close the file This will stop the files from growing too large.

Issue What attributes are available on a Continuum Activity Listview? Environment Continuum Cyberstation Listview Cause Available attributes for Activity Listview Resolution Creation of a Activity Listview the following attributes are available: ActionCode CallerCode Description EventObjectID EventObjectName Id NodeName OperatorText OTUser TimeStamp UserId UserName

Issue i28xx type of Infinet Controller has different range of WC (Water Column) than i28xx-V Infinet Controllers. What are the input voltage settings for i28xx and i28xx-V controllers' AirFlow sensor input? Environment Infinet controllers (i2865 & i2865-V, i2866 & i2866-V , i2885 & i2885-V) Cause Input settings for Velocity Pressure Sensor is different than the other regular analog input (voltage input) configuration. Resolution The i28xx type of Infinet Controller has 0~2" WC (Water Column) range, the input voltage should be set to 0~2V. The i28xx-V type of Infinet Controller has 0~1" WC (Water Column) range, the input voltage should be set to 0~1V.

Issue What are the solutions available for database fail over system Environment Continuum Cyberstation Stratus Technologies Cause Information about Database fail over / redundant systems. Resolution The everRun product  from StratusTechnologies (formerly Marathon Technologies) is what many sites use for a database fail over system. You can find more information in the everRun Datasheet and on their website below. http://www.stratus.com

Issue Error displayed "Array index too large or too small" when reloading a controller with SmartSensor (Smart Sensor) program created, or saving the SmartSensor (Smart Sensor) program to the controller. Environment Infinet Controllers (i28xx) Bacnet controllers (b38xx) bCX4040 bCX9640 Cause SmartSensor (Smart Sensor) control program uses 7 arrays of the LCDDisplay (or LEDDisplay) InfinityNumeric object to get the keypad input data, display data, change the display format and control the point.  When the point is created with no array, the SmartSensor program fails in saving.  Or, if the LCDDisplay (or LEDDisplay) InfinityNumeric object has been changed from 7 manual entries to no array since the SmartSensor program was created, it fails when reloading the program or the reloading the controller. Resolution Edit the LCDDisplay (or LEDDisplay) InfinityNumeric object and set the 7 manual entries in the Logs tab of the point editor and resave the program or reload the controller.

Issue i2/b3 controller getting error " . . .  OS update fail. Please retry" after OS upgrade is done.  The Continuum Explorer shows exclamation mark (bang) on the controller icon. The control works normal, but it is confusing. Environment Infinet controllers (i2 controllers). Bacnet controllers (b3 controllers). NC2 (CX9680) ACX5740 ACX5720 bCX4040 Cause Controller OS upgrade has failed in the first try due to network issue or unstable system environment but succeeded on the second try or the next try. Resolution Bring up a listview of i2/b3 controllers. Find the one that displays the yellow exclamation mark (bang). Perform SetAttribute (right click on the controller and select "Set Attributes") for the ObjectStatus. Select the ObjectStatus and set the value to 0 .

Issue Viconics Stats will not come on line. Environment Continuum 1.XX Windows XP, 2003 Viconics Stat Cause Viconics Comm address set to 50 BACnet Max Master set to low,  Set to 32. Resolution Open Continuum Explorer Expand Bac Net devices Edit the BCX ( Bac net view) Change the BACnet Max master value

Issue The ACX 57xx series controller supports up to 2 xP or xPB (bi-directional) expansion modules, plus a display for extended input and output configurations. The ACX 57xx series controller is compatible with all of the TAC expansion modules. For more information about expansion modules, see the xP Expansion Module Reference, 30-3001-840 and/or the xPB Expansion Module Reference, 30-3001-883. What are the valid channel numbers for expansion IO on the ACX5740/5720? Environment CyberStation ACX5740 ACX5720 Cause The expansion IO channel number assignments is different in the ACX5720 due to the fact that it has only half the onboard IO as the ACX5740 Resolution The ACX5740 has 12 onboard inputs and 4 onboard outputs, therefore the first expansion input channel is 13 and the first expansion output channel is 5 The ACX5720 has 6 onboard inputs and 2 onboard outputs, therefore the first expansion input channel is 7 and the first expansion output channel is 3

Issue Some Netcontrollers support 32 I/O Modules, others only 16, how to find out what the limit is when adding more modules to an existing system. Environment Continuum Netcontroller CX9900, CX9940, Netcontroller II CX9680, CX9940 16IO-T X Driver Cause When a site is being extended by adding extra IOU Modules, it needs to be determined if the Netcontroller will support these additional modules. Resolution If the controller is online to Cyberstation, Edit the controller and check the value of "Max IOU Modules" on the Options tab, this will show 16 or 32. If the controller is not online the following apply: All Netcontroller II (CX9680) controllers support 32 IOU Modules. All Netcontroller 1 CX9900 with 8Mb RAM support 32 IOU modules, Most CX9940 with 4Mb RAM support 32 modules the only exception was the 4M-16I/O-T (now obsolete) that supported 16 modules. To determine if the CX9940 is a 4M-16I/O-T, check that the Model on the right side of the unit is defined as CPU-4M also that there are no connectors for the RS485 fitted to the unit on Comm1 or Comm4 (you will see holes where the connectors are not fitted). The CX9940 16IO/T can support an X Driver on RS232 Comm1, but no other port. The 4M-16I/O-T and 8M-32I/OT Do not support any Infinet nodes and cannot be upgraded to support them as the required hardware is not fitted as the time of manufacture.

Issue When Acknowledging an Alarm from one workstation it is not making it to all workstations. Environment CyberStation Alarm Cause The workstation that was not receiving the Acknowledgement had two network cards in it.  Resolution Remove the second network card from the PC.  Pleas note Continuum only supports one network card in a CyberStation.

Issue When ordering Andover Continuum Keys what is the definition of I/O Points? Environment Cyberstation Keys Cause When ordering Andover Continuum Keys what is the definition of I/O Points? Resolution This pertains to the versions of CyberStation keys which include a limitation on the number of Infinity I/O points, such as 250 or 500.  Infinity I/O points are the total number of Infinity Input and Infinity Output points that are configured in the database.  These types of points can be connected to Infinet controllers, Eclipse I/O cards, Continuum IOU modules, or IOU boards  (on the Lbus).  This does not include numerics. 

Issue Does the CX 9702 support Infinet controllers? Environment Continuum Cyberstation CX 9702 Infinet I2xxx Cause Verification of Infinet bus support on CX 9702 Resolution CX 9702 has a node limit of 4 and will support Infinet controllers up to the node count limitation.