Building Automation Knowledge Base

Issue What X Drivers are available? Environment All Continuum controllers that support X Drivers (XDrivers) 3rd Party interfaces Cause How to find out what standard X Drivers are available to integrate with Continuum controllers. Resolution The Third Party Communicates Interface and Protocol Brochure can be found on The Exchange Download Center that lists all available X Drivers and product compatibility. Also all of these listed drivers are available for download from The Exchange Download Center here for use on X Driver enabled controllers. Should a new driver development be required, or other special interface; then you can contact the team that develop X Drivers: Adam.Summers@Schneider-Electric.com You will need to provide protocol details if you require a quotation.

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 What details are available on the "Condition Threat Level" feature in Continuum. Environment Continuum Cause What details are available on the "Condition Threat Level" feature in Continuum. Resolution Detailed information: Available in the "Access Control Essentials Guide" page 153 (Condition Threat Level) and 149 (Area Lockdown). This document is installed with your Continuum software on your Cyberstation. General information: To download the documents below, you must log in to The Exchange . Feature Blast v1.80 (Area lockdown support) Video support ACX Series Controller NetController II

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)

Issue Some system administrators wish to set up very limited privileges for certain users but need those same users to be able to do a controller reload. What are the minimum user security "keys" required to set this up? Environment Continuum CyberStation Cause Incorrect user security settings (locks vs. keys) will not allow a logged on user to reload a controller. Resolution In order for a limited user to be able to reload a controller, that user must have user security settings to reset, teach, create, and edit (if applicable) every item inside that particular controller (i.e., InfinityNumerics, Infinity Inputs, schedules, groups, etc.) as well as  the same privileges for controller object itself. See also the CyberStation Online Help System under Security Editor topic.  

Issue I connected the new cable and the netcontroller immediately reset and lost memory. I reloaded the Netcontroller and before it was completed it reset and lost memory. Environment NC9680 LA1 Xdriver Veederoot Cause Improper Veederoot point configuration. Corrupted Veederoot point objects. Resolution Deleted all of the Veeder-Root points. Manually entered the points one at a time. Reloaded the Netcontroller.

Issue Want to update only the events not the commanded variable or configuration points. When using the copy option, this command also change the configuration points. When copying a schedule with only a few events added, the schedule in the target controller has all other events cleared.   Environment Cyberstation Schedules Cause The limitations of Mass Create and Mass Change. Resolution In order for the copy function to work, the schedules have to be configured identically. When a copy operation takes place Continuum tries to resolve the object name with respect to the target controller. If it cannot find the same numeric in the target controller, since schedules can only be configured to control numerics or outputs in the local controller, the name cannot be reconciled. When this happens the configuration point link is dropped. Continuum cannot be configured to ignore the name the Occupancy point, the Occupancy start DateTime or the Occupancy Stop date time. Continuum will not merge schedule events within the source schedule with schedule events existing in the target schedule. It simply replaces all events with the events from the source schedule.

Issue When adding an additional WS to an existing SU(SingleUser) SQLExpress PC, DBInit -> Workstation Configuration gets error message "SQL Server PC_Name does not exist or access denied. Workstation Setup Failed! Please try again or click Cancel to exit." Environment Continuum Cyberstation version 1.82 and higher with MS SQL Express. Cause MS SQL Express requires Instance Name as SQLExpress for Database connection. Resolution Set value of the Server Name in Workstation Configuration of DBInit to "SU_PC_Name\SQLExpress". For example, if the computer name of the existing SU Workstation is "MyPC01", you need to type "MyPC01\SQLExpress" in the Server Name attribute of the Workstation Configuration of the additional Cyberstation. Note: A SU SQL Express database can only support up to 2 additional Workstations.

Issue Although i2 infinet controllers were installed, when the site was built offline i1 Infinet controller objects were created. How can I change the Infinet controllers from i1 controllers to i2 controller?  Environment i1 i2 Infinet InfinityInfinetController Cause Programmer selects the wrong type of Infinet Controller objects. Upgrading from i1 Infinet controllers to i2 InfinetControllers. Resolution In Continuum 1.9 and up the Infinity controller model can be changed after the InfinityController object has been created.  Note: Some older versions of Continuum do not support all controller models.  Make sure the controller model you are installing is selectable under Controller Type in the controller editor. To upgrade to an i2 controller from an i1 Controllers Edit the controller Select the correct model number, enter the new serial number and apply. Reload the controller. Also consider any EMX Expansion modules fitted, these will need to be replaced by appropriate point count xP modules, the i2 controllers support a maximum of 2 modules.