Issue Templates cannot be changed for personnel because the option is grayed out in the Personnel Manager Environment Personnel Manager Cause This is an issue that was fixed in 1.82 and above. Resolution There are a couple of work arounds for this issue: Go into each template and select the Attribute data source tab Go to RefTemplate and change it from InheritFromTemplate to CopyFromTemplate Go back to the personnel and the ability to switch to other templates works The other option is to switch the Personnel Manager to False in the Cyberstation preferences to use the Personnel Editor. This is not an issue in 1.82 and above.

Issue With the BCX Controller you can use either the Comm 1 or Comm2 port for the Modbus RTU X-Driver or you could use both simultaneously. Product Line Andover Continuum Environment BCX Controller Modbus RTU X-Driver Cause Enable Comm port for X-Driver Resolution Use either Comm port for the Modbus RTU X-Driver as per page 16 of the Modbus RTU user guide. If you use Comm2 you forfeit the Infinet or MSTP port, you must also create the Communications Configuration Point (Function 99) to tell the X-Driver if it should use RS232 or RS485 on Comm2. This point is required because on the BCX Comm 2 the X-Driver needs to tell the BCX to use the RS485 port (if that is what you want to use) not the RS232 port it defaults to in its Operating System. If you did not create the point the driver would default to the RS232 port. RS485 is half duplex so when transmitting data out the RS485 port, the driver needs to turn off the receiver so that it does not receive its own transmission. Also normally RS232 is full duplex and does not have to do this. However be aware that on BCX's Comm2 both the RS232 and RS485 ports are Half duplex, which although does not normally cause issues with Modbus because it is a Master / Slave network where we never get unsolicited data, it could cause an issue on other protocols. You can have X-Driver enabled on either or both ports, and there is nothing to stop you from having 2 Modbus networks, one on Comm1 the other on Comm2. You could even use a RS232 to RS485 converter on Comm1 if necessary (An Infilink200 would work fine). NOTE: The ability to enable 2 comm ports using Xdrivers can be done, but is not recommended by the Xdriver developers nor supported by PSS. The RTU Xdriver is poll on demand. This type of driver can request a lot of data and starve the CPU on the controller which then makes the polling irregular. If 2 ports are being used then there are typically more devices being added and therefore more points increasing the requests and demand on the controller's CPU. Use one program to control the polling on both ports. Two programs attempting to control the polling asynchronously will cause communication issues. The BCX is able to run 2 X-Drivers but will be a little slower than having 2 BCX's. It is really down to the individual project. If it has big networks connected or update speed is critical then split across 2 controllers. If you just have a few devices on each port and the update time is not critical then you would be fine with 1 controller.

Issue New Door Attributes KeyPadString and KeyPadCommand in ACX57xx Environment Information about the new door attributes and configuration helps users with the capability. Cause ACX57xx Continuum V1.82 Resolution New Door Attributes KeyPadString and KeyPadCommand in ACX57xx in latest versions of Continuum Requires versions of Continuum V1.82 or above and Rev 1.1xxxxx ACX Entering an Input String at a Keypad for Use in PE Programs From a keypad connected to an ACX2 door, you (the user) may also send additional data to the controller, which in turn passes it to a Plain English (PE) program for execution in an Andover Continuum control application. This capability enables you to use the keypad to send input to a PE program for any purpose. For example: A user can enter a string that a PE program uses to turn lights or fans on or off, or to control other HVAC equipment. A user can enter a string indicating the user’s purpose for entering an area. The PE program can capture this information as input to a PE program for tracking reasons for activity in a secure area.  Handling String Input at the ACX2 controller Before you can use the keypad for PE program input, you must create a Plain English program that processes the string entered at the keypad and returns a value to the system based on the entry. The ACX2 door contains two attributes that are used by the PE program KeypadString door attribute. Your PE program reads this attribute to obtain the content of the string entered at the keypad. KeypadCommand door attribute. Your PE program sets this numeric value to provide feedback via the reader/keypad LEDs to the person entering the keypad code about the status of the operation. Other commands are also sent to the door via the KeypadCommand attribute such as enabling or disabling Keypad Input. Entering String Input from Keypad The process for entering string input at a keypad has the following steps: The user presents a valid access card and/or PIN (if a PIN is required) to the door reader. The controller for this reader accepts the user’s credentials, and the door unlocks. Within three seconds of the door unlocking, the user enters two consecutive asterisks ( ** ) at the keypad to enter escape sequence mode. The keypad LED flashes slowly to indicate that it is waiting for input. The user enters a numeric string of up to 30 characters (not including the two asterisks), and then terminates the string with the pound sign (#). For example: **10# or **6986310# The door makes the string available to a PE program via its KeypadString attribute. Entry Rules for String Input The following rules apply to using a keypad connected to a door to enter string input:   After the door unlocks for a valid access, if more than 3 seconds elapse before the user enters two asterisks, the door exits escape sequence mode. The user must begin the process for string input again. If a user enters more than 30 characters (not including the first two asterisks), the door detects when the 31st digit is entered. The door then replaces the 30th character with T to indicate Tamper, and sends the string to its KeypadString attribute (no # is needed). Subsequent characters entered as part of the string are ignored. For example, if the user enters **123456789012345678901234567890123, the door sends 12345678901234567890123456789T to its KeypadString attribute. The user can enter asterisks within the string if needed. These asterisks are converted to periods when sent to the door’s KeypadString attribute. For example: 69*8*6310 is converted to 69.8.6310 when sent to the door’s KeypadString attribute. If more than 4 seconds elapse between keystrokes, the door exits escape sequence mode. The user must begin the process for string input again. If a user presents an access card to the card reader while the door is in escape sequence mode, the door exits escape sequence mode. The user must egin the process for string input again. PE Feedback to the Door After the PE program receives the string input and interprets its value, the PE program assigns an appropriate value to the door’s KeypadCommand attribute. One of the following values is transmitted back to the door through its KeypadCommand attribute: 0 - Disable keypad Input at the door. 1 - Clear string. 2 - Recognize the escape sequence entry (success). 3 - Do not recognize the escape sequence entry (fail). 255 - Enable keypad Input at the door. NOTE: Clearing the string in the door using the Clear String command is recommended after each string input in escape sequence mode. Based on the numeric value returned to the door through the KeypadCommand attribute, the PE program uses the reader LEDs to indicate to the user whether or not the string input is valid or invalid. The LED pattern to indicate valid/invalid entry is the same as the selected access control LED pattern used to indicate valid/invalid card and PIN entry. Sample PE Program The PE program in the following example is used to unlock a door for unrestricted access for the amount of time specified in the Keypad Input String. For instance, at the door, the user enters 100*3600, the "*" gets translated to "." (period) so the keypad input string contains 100.3600. The program recognizes 100 as the door timed unlock code and 3600 as the time to unlock the door for (in seconds, 3600 is the number of seconds in an hour), thus entering 100*3600 at the keypad instructs the PE program to unlock the door for an hour. 'This program processes the 'Timed Unlock' keypad code (100) entered at a door's keypad 'The form of the code is 100.xxx where 100 is the command identifier and xxx is the amount of time 'to unlock the door for. String Str Numeric KypdCode, DrUnlockTime, SeparatorPos Line Init   Jetway1 KeypadCommand = 255 'Enable door for keypad input string   Jetway1 KeypadCommand = 1 'Clear any previous keypad input string Goto WaitForKypdCode Line WaitForKypdCode   'Wait here until something goes in the keypad string   If len(Jetway1 KeypadString) > 0 then Goto ProcessKypdCode Line ProcessKypdCode   'The string should contain 2 fields separated by a period   'Get the keypad code identifier which is to the left of the separator   SeparatorPos = search(Jetway1 KeypadString, ".")   Str = left(Jetway1 KeypadString, SeparatorPos)   KypdCode =StrToNum(Str)   'Now get the unlock time value which is to the right of the separator   Str = right(Jetway1 KeypadString, (len(Jetway1 KeypadString) - SeparatorPos))   DrUnlockTime = StrToNum(Str)   'The only keypad code this program handles is the time unlock (100)   If KypdCode = 100 and DrUnlockTime > 0 then Goto UnlockDoor Else Goto InvalidKypdCode Line UnlockDoor   Jetway1 KeypadCommand = 2 'Flash the valid access LED pattern to give   'feedback that the code has been accepted   Jetway1 TimeUnlock = DrUnlockTime 'Unlock the door for the time specified   'in the keypad code   Goto ClearStr Line InvalidKypdCode Jetway1 KeypadCommand = 3 'Flash the invalid attempt LED pattern to give   'feedback that the code is invalid   Goto ClearStr Line ClearStr   Jetway1 KeypadCommand = 1 'Clear the keypad input string   Goto WaitForKypdCode

Issue CyberStation key cannot be found when a laptop is removed from its docking station, but when it is connected to the docking station, it finds the key without problem. Environment Cyberstation key Laptops with docking stations Cause Sentinel driver must be installed while the laptop is disconnected from the docking station. Resolution Remove the laptop from its docking station Uninstall the Sentinel driver from Add/Remove programs in Windows control panel Reinstall the driver while the laptop is disconnected from the docking station

Issue What BACnet Command priority does a Cyberstation program use in changing value of BACnet points? Environment Cyberstation Cause Change the value of BACnet points Resolution When you use the WriteProperty() function, you must use the BACnet path of the object for WriteProperty() function. - If the priority# is given in the WriteProperty() function, it sets the value of the point with the given priority#. - If the priority# is not given in the WriteProperty() function, it sets the value with priority#16 by default. When you don't use WriteProperty() function. - If you use BACnet path ( Ex; BACnetDevices\BCXName\MyNum = 12.340), it sets the value with the priority# that is defined in the attribute of BACnet Command Priority for Cyberstation Programs in the BACnet Preferences. - If you use Infinity path ( Ex; MyNetworkName\BCXName\MyNum = 12.340), it sets the value with priority# 10 by default.

Issue How many Video Servers can be used with CyberStation? Environment CyberStation Cause The answer to this question depends on the revision of CyberStation that is being used. Below is a list of CyberStation revisions and what quantity of Video Servers they support. Resolution CyberStation Revision   Quantity of Video Servers Below Revision 1.60   0 Revision 1.60 to 1.71   10 Revision 1.73 to 1.74 w/o SP2   50 Revision 1.74 SP2 to 1.82   100 Revision 1.90 and above   unlimited

Issue Configuration of BACnet Alarming from 3rd party BACnet IP Device that does not support Dynamic Device Binding. (i.e Notifier Fire Panel and etc.) Environment 3rd Party BACnet IP device Notifier Fire Panel Cause When 3rd party BACnet IP device (i.e. Notifier fire panel) supports Dynamic Object Binding, as Continuum WS supports Dynamic Device Binding only, the alarm recipient device (i.e. alarm recipient Continuum WS) needs to be set up in a different way to provide Static Binding information to the 3rd party device as below in order to get the alarm delivered to Continuum WS from the 3rd party BACnet IP device. Resolution Open the editor of the EventNotification in the 3rd party IP device from BACnet View. Go to Delivery tab, click Add Recipient button, or double click the existing recipient WS. Check "BACnet Address" checkbox, and uncheck "Guarantee Delivery" checkbox. Type NetNumber:MACAddress manually as below and save. ** The NetNumber is the BacNet Number from 3rd party device's perspective. The netnumber is 0 by default for most devices but need to consult with the device vendor to get the correct NetNumber. NetNumber of 65535 can be used for broadcasting. ** The MACAddress is the WS's IP address in Hex+BAC0 at the end. For example, Continuum WS IP address is 10.11.12.13, the MACAddress should be 0a0b0c0dBAC0. ** The value for the attribute is 0:0a0b0c0dBAC0. (It can be set to 65535:0a0b0c0dBAC0 for Broadcasting)

Issue How does BACnet point mirroring (COV subscription) work when the source BACnet controller is offline. Environment CyberStation BACnet controllers Cause Obtain information about the functionality of COV subscription when BACnet controller is offline. Resolution When you mirror a BACnet point between BACnet controllers via a pulling PE program using the (local point = remote point) syntax or the ReadProperty() function, Continuum subscribes the information in the COV Subscription Table of the source controller. Once the COV subscription is set up, low-level embedded code in the source controller checks the current value of the point and compares it to the COV Increment. When it finds the change is greater than the COV increment value, the source controller transfers the new value to the destination controller. In the destination controller, low-level embedded code receives the value from its transceiver buffer and writes it to its local memory. And now, the pulling PE program reads the value from the local memory and updates the value to the point object. As a result, the pulling PE program in the destination controller still reads the last value from its local memory even if the source controller goes offline. This functions the same way as the standard Continuum import/export.

Issue How can I convert my BACnet B4920 to a BCX 4040 Using Cyberstation Environment Cyberstation BACnet B4920 bCX 4040 Cause Change model number from b4920 to bCX 4040 using Cyberstation. Resolution In Cyberstation V1.90 Service pack 1 the capability to convert a b4920 to a BCX 4040 has been added. In order to change the model you open the controller editor on the b4920 and from the model pulldown, select bcx 4040. This is a non reversible change so make sure you have a database backup before doing this. Once the model is changed, you will need to edit comm2 and verify that it has the same settings for the MSTP as comm1 did on the b4920. If you have not already done so you will also have to reassign any I/O points that were on the b4920 to different hardware such as XP modules or another b3 Controller. The conversion will leave the I/O points in the database but all the channels will be set to "0" so that any programs that reference them will stay in tact. Make sure to set the Bcx up with the same ACC Net ID and do not change the Bacnet Device ID or the comm2 and UDP Net ID's. They will stay the same as the b4920 had them. Once you have connected the BCX to the network and the MSTP controllers to comm2, you simply reload the Bcx, but you do not have to reload the b3 controllers. They should come online after the Bcx is reloaded. Prior to this version a deletion of the b4920 and all b3 controllers was required, and edited dump files needed to be imported into the Cyberstation to recreate the BCX and b3's, followed by a reload of all controllers.

Issue What is a valid range for Bacnet Network Id - Comm2 on a BCX? Does each vendor get a specific range allocated? Environment Continuum BCX Series Cause Set a supported ID for Bacnet Network ID  Resolution The valid range is 1 to 65354 Since bacnet is an open standard, no specific ids have been set for certain companies. Each company decides on its own to use a specific default network id. In our case the default is 2765 which is an attempt to be somewhere in the middle of the range to not affect other controllers from other vendors. Caution must be used with this setting because using the same number can cause collisions amongst manufacturers on the network. Each Continuum BCX on a system must also have a unique number for this setting. For example, a small system with 3 bCX's might use 2765 for one bCX, 2766 for another bCX and 2767 for the third.

Issue Access Events are not being logged with an ACX 57xx in 1.81 Environment ACX 57xx Continuum Cause The most common reason for this is because the ACX 57xx is shipped with a 1.1x version of firmware and NC2 with 2.1, but there are updates in this firmware that are specific to Continuum V1.8x and V1.9x. Resolution Revised 3/15/2018 This article was recently referenced and updated. 1. Uprev Continuum to 1.9x or greater with ACX 1.1x or NC2 2.1x firmware 2. Down rev the firmware in the ACX to the most recent 1.0x or NC2 2.1x version of firmware with 1.8x or less. (Not recommended)

Issue Error using webClient webpinpoint, "You have been assigned a web object but do not have the appropriate permission to view it" Graphic option isn't available in the web browser client, other options are there. Environment webClient Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause There are 2 different types of webClient. PM for security and PRO for security and HVAC Resolution WebClient Pro and webClient Personnel are two different products. The Personnel version doesn’t allow for graphics. Verify the serial number of the security key with the Repair Department to determine if the Personnel product is enabled on the key. If so, request a cookie upgrade for the key.

Issue Creating a test database for troubleshooting Product Line Andover Continuum Environment Continuum test database Cause There are times when troubleshooting an issue when creating a test database is useful. Resolution Open up Database Initialization Select Server if you have a LAN install with a Full SQL license or Stand Alone if you are using MSDE or SQL Express Click on the Create New database radio button (bottom right) which opens up the needed fields Change the Database name from Continuumdb (default) to Testdb Under Device Information, Change Database from ContinuumDev to TestDev Under Device Information, Change Database from ContinuumLog to TestLog Ensure the path is correct for DB File location Enter in the sa password Click Continue (This creates 2 files TestDev.mdb and TestLog.ldb in the DB File folder) Go to Database Initialization again Select Workstation Leave the info on the workstation tab exactly as they are Click on the Database tab Change the Database Name from Continuumdb to Testdb Click Ok (This will resolve the workstation to the new test db) Start Continuum and perform the test and see if the issue still happens on this clean db. Once the test is completed, delete the Testdb database from Enterprise Manager or use osql Go to Database Initialization again Select Workstation Leave the info on the workstation tab exactly as they are Click on the Database tab Change the Database Name from Testdb to Continuumdb Click Ok (This will resolve the workstation back to the Continuumdb)

Issue When attempting to restore a ContinuumDB database while using SQL Express Management Studio, you receive the following error: The database ContinuumDB is not accessible. If you click Ok, you are able to continue, but when you select Restore from Device and click the Add button, you get the error: Cannot access the specified path of file on the server. Environment SQL Express Studio Cause The most common reason for receiving this error is because when SQL Management Studio is started and you are prompted for a username and password, Windows authentication is selected instead of selecting SQL Server Authentication. Resolution Verify that you have the necessary security privileges and that the path or file exists.  

Issue ASP.Net is not showing as a user to select in dcomcnfg list configuring webclient on XP Environment Windows XP ASP.NET Cause This is usually caused because .Net was installed prior to IIS. Resolution Run the aspnet_Regiis.exe -i to re-register the .Net framework with IIS C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i Go back into dcomcnfg and asp.net will now be available. This normally does not require a reboot or restart of IIS

Issue How do you get a list of previous operator history on a specific point from the active alarm view? Environment CyberStation Cause A report will need to be attached to a graphic to see a point's operator text history from the active alarm view. Resolution Create a report for this point to get the operator text Source Tab Data Source: AlarmEvent Report Type: Alarms-for-an-event-object-with-alarm-enrollment Type: Text Filter Tab Path: select the controller the point is in Member Object: Select the point you need Time Interval or Log Filter for the desired range   Setup a graphic page with a button to launch the report In the properties of the Active Button Action: Open Object Object: This is the path to the report you created in step 1.   Setup the point on alarm tab to open the graphic In the point editor that you want the operator history from, select the Graphic field by setting the path to graphic that contains the button for the report from step 2.   When the alarm is triggered in the active alarm view, click on the alarm then the Pinpoint button in the tool bar. This will launch the graphic with the button for the report you created.   Click on the button to launch the report which will contain the operator history for that point. Notes: For multiple points, the same graphic can be launched each time, but separate reports will need to be created for each point and a different button to launch those reports.

Issue Serial Commport Settings when using Roam IO/2 Environment RoamIO/2 Cause Serial commport settings Resolution The serial commport settings used to connect to the Roam IO/2 tool are listed below. Bits per second: 9600 Data bits: 8 Parity: None Stop bits: 1 Flow control: None When using the Roam IO/2 with a Serial Cable, please make sure cable uses the following pinout assignments. Pin Signal 2 RXD (Received Data) 3 TXD (Transmitted Data) 5 GND (Ground) NOTE: In the field we've seen some success when using USB to Serial converters, but not all devices will work. Using Serial 9 pin to 9 pin with the above configurations is the preferred method for Serial connection.

Issue How do I use the Corporate 1000 card format on sites with a mixture of CX9900 and CX9680 controllers? Environment CX9900 CX9680 Corporate 1000 card format Cause You cannot use the card type of Corporate 1000 directly in a system that has access controllers other that Netcontroller II and ACX II's on it Resolution The problem here is that the CX9900 does not directly support the Corporate 1000 card type. The only way to do it on the CX9900 is to use a custom format which means the card type on the personnel record is also set to Custom Format. Setting up the AccessFormat on the CX9900 is standard but when trying to use this format on the CX9680 you will get an error. The reason for this is because in order to implement the Corporate 1000 card type on the CX9680 we had to create a custom format for it behind the scenes since the AC-1's could not directly support this new card type. In order to create this as a Custom Format on the CX9680 use the special numeric AccessFormat2 and set it up the same as you did in the CX9900.

Issue CyberStation stops sending Alarm Emails Environment Continuum CyberStation Cause There are spaces or special character in EventNotification names, which cause the emailing of alarms to stop. Resolution In order to send emails from Alarms you must make sure your EventNotification names do not have any spaces or special characters in them.

Issue How to install hotfixes that replace executable files. Environment Continuum Cyberstation Cause No longer need the existing executable file and want to replace with the hotfix file. Resolution The correct way to install a hotfix that replaces an executable file is to either delete the original file before installing the hotfix or to do the below. In Windows Explorer drag and drop copy the original file so you end up with a file called Copy of xxxxx.exe Delete the original file through Windows Explorer. Then extract the hotfix file into the Continuum directory through Windows Explorer.