Issue Continuum 1.62: Personnel objects are losing their template associations Environment Continuum CyberStation Personnel Templates Cause Personnel objects are losing their template associations Resolution Install all Continuum 1.62 service packs.

Issue How to display the currently configured access level for all User objects without having to open each User individually. (logon security groups) Environment Continuum Cyberstation Cause Want to see the access level for all User objects at the same time but unfortunately this attribute is not viewable in a ListView of all User objects. Resolution The Users access level is viewable as the KeyRings attribute in the text "dump" file of the User objects. Select and Right-click the User objects you want to dump to file. Select "Send To -> Text File..." and provide a file name. In the resulting dump file you will see that the KeyRings attribute shows the enabled groups in binary encoded hexadecimal. Group1 corresponds to bit1, Group2 to bit2 and so on; the KeyRings value is the hexadecimal representation of this binary value.

Issue What is the pin configuration for Modbus RTU when using a 9 pin comm port on a BCX controller. Environment BCX Modbus RTU Cause Connecting a BCX or CX controller to a Modbus RTU device. Resolution RS232 connection for a 9 pin BCX comm port.   BCX Comm 1 (9 Pin)            RJ 45 Connector @ Modbus device Pin 1 CXD        -->                 Pin 1 DTR Pin 7 RTS        -->                 Pin 2 CTS  Pin 4 DTR        -->                 Pin 3 CXD Pin 8 CTS        -->                 Pin 4 RTS Pin 5 GND       -->                 Pin 5 GND Pin 3 TD           -->                 Pin 6 RD Pin 6 DSR        -->                 Pin 7 DSR Pin 2 RD           -->                 Pin 8 TD        

Issue What is the maximum number of Network Controllers (InfinityController object) that I can have in my Continuum Database? Environment Continuum Cyberstation Cause Site expansion. What is the maximum number of Network Controllers (Netcontroller, ACX, etc...) that the system can grow too. Resolution There is no logical limit. Although you can only have up to 190 in one network folder. That is because the ACCNetID’s for controllers only go up to 190, after 190 controllers you will need to create a new Network object to house any new Network Controllers.

Issue Programs don't work in an i2 controller after being copied from another working controller. Environment CyberStation Plain English Plain English InfinityPrograms Cause Programs not working properly in an i2 Controller. Resolution When dragging objects from one controller to another... Do not drag the source InfinityController onto the target controller.  Rather, from the object view window, select all objects in the source controller and drag them to the target controller object. From the Options menu in Continuum Explorer, under the Name Conflicts tab, make sure the first four options are checked.

Issue I cannot connect to a b3 controller, even when it is removed from the MSTP bus. I cannot connect to an Infinet controller, even when it is removed from the Infinet bus. Environment Continuum Roam IO MSTP Infinet i2 b3 Cause Need to connect with a local controller using RoamIO. Resolution In some cases we have found that RoamIO has trouble connecting to an individual i2 or b3 controller.  If you are having trouble connecting via RoamIO to a controller that is not connected to the controller bus, try connecting two controllers together and attempting to connect.

Issue How to Set Up BACnet Enabled ABB Variable Frequency Drives for Use With Continuum Product Line Andover Continuum, Other Environment ABB Variable Frequency Drives Continuum Cause ABB VFDs must wired and configured properly to be used with a BACnet Continuum network. Resolution When wiring an ABB drive up to the Continuum BACnet MSTP network make the following connections: Terminal X2 Type (+) (-) Reference Drive Only 29 30 31 Bypass 27 28 29  ABB recommends that when using a two conductor cable with shield that the shields not be connected  to any pin (Note that pin 29 would be unused) but simply connected together with a wire nut. However, they do say that the shields can be connected to pin 29 if the drive communication is intermittent.  If the ABB drive does not have an E-Clipse bypass (E-Clipse is the ABB brand name for the bypass portion of the VFD) use the following settings:  Parameter  Setting Notes 9802  BACNET  Sets the communications protocol of the VFD. 5302  MAC ID Create a unique ID. A good practice is to set this to the Infinet ID + 1000. For example, if the Infinet ID is 5 then set this to 1005. 5303  Baud Rate  Set the baud rate being used on your BACnet network. 5311  Device Instance ID                   This is the Infinet ID and should be set to an available number between 1-127. This will display as a hexadecimal value in the BACnet side of Cyberstation. 1001  COMM  Set this if you want to start & stop the VFD over BACnet. 1103  COMM  Set this if you want to control the drive speed over BACnet. 1604  COMM  Set this if you want to reset VFD faults over BACnet. If the ABB drive does include a bypass the following settings must all be entered (notice that 5302 and 5311 are now specific to the VFD portion of the unit whereas the 5002 and 5011 are specific to the bypass portion) All of these parameters as well as the parameters listed above must be entered at the bypass. Parameter Setting Notes 5302  Drive MAC ID  Create a unique ID specific to the VFD. 5311  Drive Device Instance ID  This is the Infinet ID specific to the VFD. 5002  Bypass MAC ID  Create a unique ID specific to the bypass. 5011  Bypass Instance ID  This is the Infinet ID specific to the bypass. NOTE If the ABB drive is ACH550. Then the parameter below need to be set as a minimum. Other points will also need to be set depending on your site requirements, but the ones below will get communications up and running    Parameter  Setting Notes 5301   x5xx -This parameter indicates the active protocol and its revision. It should read x50xx if BACnet is properly loaded. If this is not the case, confirm that drive parameter 9802 = BACNET (5). 5302  MAC ID -This parameter sets the drive’s BACnet MS/TP MAC ID. A temporary value of 0 places the protocol channel in reset. 5303  Baud Rate -Set the baud rate being used on your BACnet network. 5304 Set to 0 -This parameter sets the BACnet MS/TP character format as follows: 0 = 8N1 1 = 8N2 2 = 8E1 3 = 8O1. 5311 EFB PAR 11  - Instance ID part1 This parameter, together with parameter 5317, EFB PAR 17, sets BACnet instance IDs: • For the range 1 to 65,535: This parameter sets the ID directly (5317 must be 0). For example, the following values set the ID to 49134: 5311 = 49134 and 5317 = 0. • For IDs > 65,535: The ID equals 5311’s value plus 10,000 times 5317’s value. For example, the following values set the ID to 71234: 5311 = 1234 and 5317 =7 5317 EFB PAR 17  - Instance ID part2 This parameter works with parameter 5311 to set BACnet instance IDs. See parameter 5311. 1001  COMM -Set this if you want to start & stop the VFD over BACnet. 1103  COMM -Set this if you want to control the drive speed over BACnet. 1604  COMM -Set this if you want to reset VFD faults over BACnet.

Issue Cannot connect to a Network Share with Pinpoint Graphics. Environment Continuum 1.93 Windows Server 2008 Windows 7 IIS Cause Due to enhanced security by Microsoft a Domain Service Account needs to be applied to IIS for the share. Resolution Open IIS Management Create a  Virtual Directory Enter the name "New Graphics Files" Enter the path   \\servername\sharename Click on "Connect as" Enter Service account name and password. Notes* Service account should be a member of the Backup Administrators group.

Issue Receiving a RPC error when switching to another graphic in webClient. Environment Windows 7 Continuum 1.93 Windows 2008 Server Cause Windows Defender is running on Client systems. Resolution Open Control Panel Select Administrator tools Open Services Disable Windows Defender

Issue How to view the current Priority level controlling a BACnet object using Plain English. Environment Continuum Cyberstation BACnet AnalogOutput, AnalogValue Cause 3rd party is controlling a BACnet object at an unknown priority level. We want to see what the current Priority level is and relinquish this control. Resolution We can use the PriorityArray attribute to view the value of each Priority level. Then using a For loop we can loop through all 16 priority levels to determine the current priority level controlling the BACnet object. Below is a program that will allow you to see the current priority (aaPriorityValue) controlling your object (PriorityTest) and at what priority level (aaPriorityIndex). You will need to create two numerics (configure as AnalogValue) for this program to work (aaPriorityIndex and aaPriorityValue). With the method below we can see if a non-zero value is the current priority and at what priority level.  Unfortunately a 0 value is seen the same as a NULL value (both seen as 0), so if a 0 value is currently controlling the object we are unable to determine at what priority level this is set. If aaPriorityValue is 0 and aaPriorityIndex is < 16 then we know that aaPriorityIndex is the level of the non-zero value and can relinquish all priorities down to that level if needed. Still not exactly what we want but it does give a bit of flexibility to actually control the current priority level. ======================= ' Program to get the highest priority value and its index number ' Flow: Looping Numeric count Numeric PriorityValue CALC:   For count = 1 to 16   'Loop through the priority array, looking for the first non-Null value     PriorityValue = ReadProperty(PriorityTest PriorityArray, count)     If PriorityValue is not NULL then       Break 'stop at the first non-Null value. Side effect, also first non-zero value     Endif   Next count   If PriorityTest = 0 then 'Check for 0 value     aaPriorityValue = 0     aaPriorityIndex = count   Else 'If not 0 or NULL value, set current priority value and index     aaPriorityValue = PriorityValue     aaPriorityIndex = count   Endif =================================  

Issue What is the maximum size you can set the EventLogSize in a Continuum Access Controller? Environment ACX5720 ACX5740 CX9900 Netcontroller II Cause The default setting of the EventLogSize system variable is 1,000, how much can I increase this by? Resolution The EventLogSize system variable determines how many Event log entries that a controller will buffer; if it ever loses Ethernet communications to the workstations. So is only utilized during a network failure. Typically the default 1,000 is sufficient for most projects, but this figure can be increased depending on the available Freemem in the controller. So the more personnel, doors and other objects created in the controller the lower the max value that can be entered in EventLogSize. Each event will use 68 bytes from the Freemem value of your controller, so by checking the available Freemen you can calculate the maximum size of EventlogSize that can be defined. However never use all the available memory from a controller, always leave a few thousand bytes of Freemem for future use. Typically the value can be increased to over 100,000 on most configurations if so required.

Issue Each Cyberstation has a path to pinpoint graphics and the graphic file could be different on each Cyberstation. A way is needed to access and update one set of pinfiles. Environment Continuum Webclient Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Configuration is needed to allow updating and accessing one set of pinpoint files. Resolution Share a folder (Microsoft sharing and permissions) on one Cyberstation or Server that will contain the Pinpoint graphic files (including backgrounds and images) Copy all edited pinpoint and graphic files needed to the shared folder Go into Pinpoint on each Cyberstation and go to the View > Options Edit the Graphic, Image and Background paths to point to the shared folder. Once there are not Red Xs, the path has resolved and pinpoint will then use that folder for its graphic files on that Cyberstation

Issue PE programming required to display a check list doc, report etc on specific alarm link of an object such as a door. Environment Continuum provides built in functionality to run a program when any of the 8 alarms associated with an object goes into alarm. In order to execute some actions on a specific alarm some PE programming is required. This article provides sample User Defined PE Alarm function to display a particular document depending on which of the alarm links associated with a door object is active. Cause Not known cause Resolution Configure the Cyberstation that will be displaying the doc, report etc for User-Defined Alarm Function (See Cyberstation online help for instructions on how to do the configuration). In the PEAlmFunction use code to qualify the alarm and display the doc or report that applies to the particular alarm type. -- SAMPLE CODE Arg 11 AlarmENROLL Arg 12 EventNOTIF  if EventNOTIF is not "DoorAlarm" then return 'Only looking for door alarms in this example. if AlarmENROLL = "Door Forced Open" then SHELL "C:\Temp\CheckListForDoorForcedOpen.doc" if AlarmENROLL = "Door Ajar" then SHELL "C:\Temp\CheckListProcedureForDoorAjar.doc" -- END SAMPLE CODE NOTE: The alarm function will be invoked every time any alarm comes in; in the example above all door alarms have been associated with the same EventNotification (DoorAlarm) in order to make sure the function can execute only when door alarms are reported.

Issue Integration of multiple Continuum databases. Environment Cyberstation Cause Unsupported configuration. Resolution DO NOT share a controller between databases, doing so will cause communications issues amongst others. Alarms can be reported to the other 'sites' via email etc but integration within the Continuum system is not possible.

Issue Handle id limits on Continuum controllers. Environment All master level controllers (bCX, CX) All b3 controllers All i2 controllers Cause Handle id limits on Continuum controllers. Resolution Field controllers have a total limit of 255 objects, approximately 50 of them are reserved for system variables and other system objects, leaving approximately 200 that can be user created in the field controller. All IP level devices in the Continuum line follow the handle specifications of the Continuum protocol. This includes the BACnet devices such as the bCX-4040. Handle numbers for most object types (including all BACnet types) are in the range 7,000 to 65,535. That allows for 58,536 objects, which is more than the memory can hold. Continuum style alarms (not BACnet alarms) have handles in the range 1,000 to 4,999. Controller will run out of memory before it runs out of handles.

Issue Duplicate Infinet ids can result if previously configured i1/i2 device is connected to field bus after power up. Environment All i1 and i2 devices. Cause Duplicate Infinet ids can result if previously configured i1/i2 device is connected to field bug after power up. Resolution When an Infinet device with an assigned Infinet id comes up before it joins the Infinet token passing it performs a self test routine that detects whether its id is already in use, in which case the device rolls its own id back to factory default (zero) and stays off the bus until commissioned. In order to make sure the duplicate id detection works, the device MUST be connected to the Infinet BEFORE it is powered up.

Issue "Windows 7 displays .NET 2.0 Not Installed" error when launching Pinpoint graphic in Webclient. When trying to open a Pinpoint graphic in WebClient, Windows 7 notifies me that .NET 2.0 is not installed even though .NET 2.0 is installed on the client machine, .  I have set the Windows 7 User Account Controls Setting to never notify but this has made no difference. Environment Continuum WebClient Windows 7 .Net User Account Controls Settings Cause Windows 7 in not presenting the notification that it wants to install software on the client machine. Windows 7 User Account Control Settings notification level set too high.   A reboot of the Windows 7 workstation is required in order to apply changes made to User Account Control Settings Resolution Change Windows 7 User Account Control Settings level Never Notify.    Reboot the PC Once the first graphic has displayed successfully the notification level can be increased and future graphics will launch successfully.

Issue Error message of "default port unable to find object in the DB" from InfinityProgram objects when trying to export the controller to a dump file backup by performing "Send To" --> "Text File" from workstation. Environment Continuum Workstation (LAN & SU) NetController (CX99xx, CX96xx, CX97xx) InfinetController (i2xxx , i1 controllers) Cause The controller was created by importing a dump file created from different system DB or by importing a dump file from a different type of controller followed by poor/incorrect modification. Resolution Recreate the InfinityProgram object again manually as below. Copy the source code of the InfinityProgram in a text file. Delete the InfinityProgram from Continuum. Create a new InfinityProgram with the same name. Paste the source code from the text file into the InfinityProgram editor, save the InfinityProgram. 

Issue PIN on card reader keypad is not working and no access event is created. Environment All ACX and AC-1 products with doors configured to Validate PIN or with General Code selected, i.e., PIN only or card plus PIN.  ACX5740, ACX5720, CX9900 or CX9940 with AC-1, AC-1A, AC1-PLUS, ACX700, ACX781 Cause This situation can be the result of either cardholder error or can be due to incorrect keypad configuration. Resolution If the problem is due to cardholder error it is likely that the cardholder is forgetting to press the keypad # key after entering his/her PIN. The # key is what sends the PIN to the controller for validation. If the keypad is configured incorrectly it may not be sending the PIN correctly, even if the cardholder is pressing # after the PIN. This is because the keypad data needs to be sent as an 8-bit burst in order for the NetController or ACX to correctly interpret it. Some card reader/keypads can be reconfigured with a special configuration card from the manufacturer (such as HID iClass). Check with the manufacturer if you think the keypad data output configuration is incorrect. 

Issue How does controller part number relate to the controller type Environment Continuum 1.7 onwards for bCX Continuum 1.74SP2 onwards for NC2 Cause Require details on Controller type, these detail are available in the Operation and Technical Reference Guide Resolution Part Number Type NC2  9680 bCX1-R-?? 4000 bCX1-CR-??? 4040 bCX1-CR-???-INF 9640 The actual type can be confirmed by logging on to the controller web page Full details from relevant guide CX9680 NetController II with optional Network Security code linked with firmware, although the code may not be activated at run-time. This option provides secure, encrypted communication between the controller and a workstation. CX9681 NetController II without optional Network Security code linked with firmware. bCX4000 BACnet Router and BBMD only .. bCX1-R-64 = 64 MS/TP Nodes No xP module support No PE Driver support BACnet/IP, BACnet/Ethernet bCX4040 BACnet controller with MS/TP Bus xP expansion bus for up to 2 I/O modules + 1 Display module 1 MS/TP port and 1 RS232 port BACnet limitations are indicated by the bCX1 part number, and include: .. bCX1-CR-0 = 0 MS/TP Nodes .. bCX1-CR-8 = 8 MS/TPNodes .. bCX1-CR-32 = 32 MS/TP Nodes .. bCX1-CR-64 = 64 MS/TPNodes .. bCX1-CR-127 = 127 MS/TP Nodes .. bCX1-CR-0-SA = 0 MS/TP Nodes w/SMNP Alarming .. bCX1-CR-8-SA = 8 MS/TP Nodes w/SNMP Alarming .. bCX1-CR-32-SA = 32 MS/TP Nodes w/SMNP Alarming .. bCX1-CR-64-SA = 64 MS/TPNodes w/SMNP Alarming .. bCX1-CR-127-SA = 127 MS/TP Nodes w/SMNP Alarming bCX9640 Full function controller with Infinet Bus xP expansion bus for up to 2 I/O modules + 1 Display module, 1 Infinet and 1 RS232 port Infinet bus limitations are indicated by the bCX1 part number, and include: .. bCX1-CR-0-INF = 0 Infinet Nodes .. bCX1-CR-8-INF = 8 Infinet Nodes .. bCX1-CR-32-INF = 32 Infinet Nodes .. bCX1-CR-64-INF = 64 Infinet Nodes .. bCX1-CR-127-INF = 127 Infinet Nodes .. bCX1-CR-0-INF-SA = 0 Infinet Nodes w/SMNP Alarming .. bCX1-CR-8-INF-SA = 8 Infinet Nodes w/SNMP Alarming .. bCX1-CR-32-INF-SA = 32 Infinet Nodes w/SNMP Alarming .. bCX1-CR-64-INF-SA = 64 Infinet Nodes w/SNMP Alarming .. bCX1-CR-127-INF-SA = 127 Infinet Nodes w/SNMP Alarming The bCX can have XDrivers on comm1, comm2 or both ( add -X1, -X2 or -X12)