Building Automation Knowledge Base

Issue Need to filter on access event type such as Invalid Attempt Environment CyberStation Cause Documentation Resolution 1. Create a List View of AccessEvent or edit an existing one. 2. Go to the 'Qualifiers' tab 3. Configure a qualifier as per the screen shot below 4. Save the list view When the list view runs it will display a list of access events, select the one you wish to filter on

Issue If the pull-up resistor is disabled falsely, the sensor value or status that connects with this input may be wrong. For example, sensing temperature value has a great deal of error with the actual temperature value. Environment I2 controllers B3 controllers Cause If the pull-up resistor selection is wrong, the right value can not be gotten. Resolution The following is a schematic representation of the switch and its associated pull-up:   To measure temperature, the pull-up resistor switch associated with this input must be enabled. To measure voltage, the pull-up resistor switch associated with this input is usually disabled (OFF). To sense contact closures (Digital signals), the pull-up resistor switch associated with this input must be enabled. To count Pulsing signals or contact closures, the pull-up resistor switch associated with this input must be enabled.

Issue A specification for a power meter states that it provides KYZ pulse outputs. What is a KYZ pulse output? Product Line All Product Lines Environment Utility Meter with KYZ pulse outputs Cause Some meter specification sheets may state that the device outputs KYZ pulses. Resolution KYZ is a designation given to a relay used to create pulses for electrical metering applications. It is commonly a Form C relay (SPDT). The term KYZ refers to the contact designations: K for common, Y for Normally Open, and Z for Normally Closed.

Issue Windows Application logs may be requested by Technical Support to assist with a reported issue. Product Line All Product Lines Environment All Microsoft Windows Operating Systems Cause Unspecified cause. Resolution Press WINDOWS + R on keyboard of the Windows system that the report is to be from. The Windows key is usually located between the CTRL and ALT keys and has a picture of a flag on it. Type Eventvwr.exe and click OK Event Viewer will now start. Expand Windows Logs and then right click on Application. Click on Save All Events As... When prompted save the file as an *.evtx file to an accessible location. Email the *.evtx file to your support representative.

Issue Presenting FIPS-PIV credential at the door results in Invalid Attempt, FIPS-PIV Credential not valid. Environment CyberStation ACX5740 CX9680 Cause Either the credential number or the Individual Credential Issue field (or both) has a value of zero. Continuum does not allow zero in the credential number for any of the supported FIPS-201 card format types (FIPS-75, FULL-FASCN etc) Continuum does not allow zero in the Individual Credential Series (ICI) field for any FIPS-201card format  type that includes the ICI field such as FULL FASCN The card may have not been programmed correctly. Resolution 1. Upgrade controller firmware. The controller FW has been updated to allow zero in the Individual Credential Series (ICI) field. Credential number ZERO remains INVALID. CX9680 version 2.100048 or greater. ACX57xx version 1.100052 or greater. 2. Use FIPS-PIV credentials that have non zero values in the credential number and the individual credential issue. OR 3. In the PIVReaderFormat system variable in the controller, configure the format specifying that the field (or fields) be ignored. **** **** IMPORTANT Be aware that ignoring a field such as the Individual Credential Issue (ICI) may result in an otherwise invalid card to be granted access. For example, if a card with ICI set to 1 is lost and replaced with a card with ICI set to 2 but with all other FASCN field identical, the controller will grant access to both cards if configured to ignore the ICI field. For example, for a reader that outputs a 200 bit FULL FASC-N card signal configure the door like this... And set the PIVReaderFormat like this SS-Agency+System+Credential+SF+SF+PI-OC-OI-POA-ES-LRC (Note the SF token instructing the controller to skip the field when performing the card validation) NOTE: When the door configuration changes the controller automatically resets PIVReaderFormat based on the value of the door's card format, to keep the value of PIVReaderFormat at the proper custom value it is necessary to create a PE program in the controller. The program should be triggered by the PIVReaderFormat system variable.

Issue Continuum installer throws a Error 1904, dll failed to register error during the installation process. Environment Continuum Error 1904 Failed to Write to Registry. Cause Virus protection is preventing the Continuum install from writing a .dll to the registry. Resolution Uninstall Continuum completely. Reinstall Continuum with all malware protection software disabled and using a Local Administrator user account. Check the compatibility matrix to ensure that the Windows OS you are using is compatible with the Cyberstation version

Issue Link test fails when selecting graphics folder path in Pinpoint Options. Internet Explorer throws the following error when a graphic is launched.   Environment WebClient IIS Server Web Pinpoint Pinpoint Graphics Cause When specifying the location of graphics files in WebClient, the share must be a virtual drive as IIS not use a physical drive. Resolution Use the virtual drive share name when configuring the graphic file location under WebClient in Pinpoint options.

Issue Not able to select the Find New BACnet Device option in the BACnet folder, to bring new devices online. Environment BACnet Cause Not able to bring online new BACnet devices. Resolution The "Find New BACnet Devices" option should be selected by right clicking on the Root folder. You can not perform this operation from under the BACnet Devices folder.

Issue What are the part numbers for the IOU module terminals? Environment Netcontroller Netcontroller II IOU Modules (all) Cause Need to wire a remote or third party power supply to a Netcontroller; or to wire remote IOU modules. Not sure what parts need to be ordered for the module terminals. Resolution There are two separate terminals available, a male power supply connector  and a female IOU module connector.  Male Power Supply Connector (Left Hand Side)   01-2050-285  (Male Connector for PS NetController)            Female IOU Module Connector (Right Hand Side) 01-0010-840  (IOU Module Connector, BOX OF 20)       

Issue Group object log viewer shows gaps in graph when viewing ExtendedLog data. Environment Continuum Cyberstation Group object Cause The Group Graph Logviewer can support up to 20000 data values being plotted at the same time, anything beyond this you will receive dropped blocks of data. Resolution This was increased to 40500 in Continuum v1.94. If you are plotting more than 40500 total data points then you may see this problem where some data is dropped. Unfortunately this is a limitation of the Logviewer control and it cannot be increased beyond this. Reduce the number of data points being plotted by reducing the time being viewed or the number of objects being plotted on the same graph. Using the Report object to graph this data may be another alternative.

Issue What are the locations where Controller configuration data is saved? Environment Continuum Cyberstation Continuum Controllers Cause Unsure as to where controller configuration information is stored and how to clear/reset this information if required. Resolution There are a number of different locations that a controllers database (configuration information) is stored - there are four locations for a BACnet controllers database and three for an Infinity controller. 1. Continuum SQL Database - Infinet tree In Continuum Explorer, this is where the controller is originally created as a Device object under a Network Folder and commissioned into the Database. This is the location where objects (inputs, outputs, programs, etc...) are created. When creating a new object, it is created in both the SQL Database and also sent out to the controllers database at the same time. The controllers information stored in the SQL Database can be sent out to the controller at any time by performing a reload of that controller (right-click Device object, Send to controller). This information can be removed from the database and the controller by deleting individual objects or by deleting the entire Device object. If the Workstation where this delete was performed is online to the field devices then the same object(s) will be removed from the live controller in the field as well as from the SQL Database. If the Workstation is offline to the field controllers  (Workstations can be taken offline for offline editing) then this delete is only applied to the objects in the SQL Database – the objects will still be located in the controllers though, creating a mismatch between the two until the controller is reloaded. 2. Controller RAM This is the active location of memory on the controller where the running database resides. On most controllers there is a backup battery that keeps this RAM alive with a trickle current when there is no power to the controller. When the controller is powered up it first tries to load its active database from RAM - this is the most current backup. The database in controller RAM can be cleared by pressing the Reset button on the Runtime tab of the controllers Device object in Continuum Explorer. 3. Controller FLASH This is the backup location of where the controllers configuration database resides. At any time the active RAM database can be saved to backup Flash by selecting "save to flash" from the controllers Device object in Continuum Explorer. This then makes an exact copy of the database in RAM (excluding point values) that can be restored at a later date either manually or automatically if the controller reboots and their is no valid database in RAM. For Netcontrollers and bCX's, this database saved to Flash can be deleted from the controllers configuration page (configuration webpage) select Clear Database Backup and then commit changes to controller. If the controllers webpage cannot be accessed, pushing and holding down the controller's reset IP switch for 30 seconds clears any backup in flash in addition to resetting the IP address and ACC node id to default. Another way to clear a controllers flash is to save a blank controller database to flash. Create a new controller Device object and then save that to flash. 4. Continuum SQL Database - BACnet tree The information stored in the BACnet tree is the BACnet side of our configured Infinet objects. This is the BACnet objects as seen in the controller and as third-party BACnet Devices will see them. When performing a "send to database" on the BACnet side, the Workstation goes out to the controller in the field, grabs all the BACnet objects and exposes them in the BACnet tree so that they can be used within Continuum. These can be deleted from the BACnet tree without harming those objects configuration in the controller or the Infinet tree. To recap:   To Create and save objects to the controller requires a two step process. Step 1: Create Database objects using Continuum Cyberstation. Objects are added to both the active RAM of the Controller and the SQL Database. Step 2: Save to Flash on the Controller. The objects in active RAM are backed up to the Flash RAM. If unsure, the only way to know that the Database in the RAM and Flash is the same as that in the SQL Database is to perform a reload of the Controller and then backup to Flash. Step 3: Send to Controller to reload configuration information from SQL Database to Controller RAM. After reload, redo Step 2 to backup to Flash. To completely wipe configuration information from a controller in the field you will need to clear its active RAM and its backed up Flash. If you want to clear all information of the controller from the field and the SQL Database then you will need to clear the RAM and Flash and delete the Device object from both the BACnet and Infinet sides of the tree. If you want to remove specific configured points from the controller but retain it in the tree, you will need to first delete the BACnet side of the controller from the BACnet tree, then you can delete individual objects (or make changes) from the Infinet tree.  

Issue Using Database Initialization to add a workstation to an existing system results in an error. After inputting all required information on the Workstation dialog, the below error is seen and the Workstation is not initialized into the database. "Failed to initialize workstation" Environment Continuum Cyberstation BACnet Devices Cause Third-party (or our own) BACnet controllers are interfering with the creation of the workstation device object. The BACnet Device ID's are clashing. All workstations require an ID. If you have a BACnet system, in the Device Node ID field, enter the BACnet ID for the workstation. (Each workstation requires a unique BACnet ID number.) It can be any unique ID number between 1 and 4194302. Note: In a BACnet network, this ID is unique for workstations and controllers alike and is vendor-independent Each BACnet Device (including the Continuum workstation's) must have a unique ID that does not conflict with any other device on the same BACnet network.   Resolution You can identify BACnet Device ID's already used within the Continuum Database and then choose one that does not conflict. Create a Listview looking at Device class with a path type of AllPaths. As a minimum add the following columns; Name, InstanceId, NetworkId, NetworkNumber. Run the listview. The list it generates is all of the BACnet Devices defined within your Continuum Database. The last portion of the InstanceId (after the backslash) indicates that Devices BACnet Device ID.   You will need to identify a free number that is not being used and change the Device Node ID value you were trying to use in the Workstation Configuration dialog window. With this new Device Node ID that is not conflicting, you should now be able to initialize your workstation successfully.

Issue An attempt to flash the firmware in the controller results in error, "The UPREV code could not communicate with the specified controller." Product Line Andover Continuum Environment bCX CX9680 ACX5720 ACX5740 Cause Uprev operation attempted using the wrong flash file. Resolution Re-try the operation using the flash file that matches the model number in the controller. Note that regardless of what the model number reads from the InfinityController editor in CyberStation, the verification is done at the controller level. Do not go by what you see in the CyberStation as this user configured field could have been entered incorrectly. Verify the model number from the controller's web page configuration.

Issue Want to view and change all COVIncrement values through one listview but the attribute is not showing up in the drop down list. Environment Continuum BACnet AnalogInput AnalogOutput AnalogValue Cause Selecting the wrong object class for the Listview. The COVIncrement attribute is only applicable to the BACnet points AnalogInput, AnalogOutput, and AnalogValue. Resolution In the ListView object, change the object class to one of the following: AnalogInput, AnalogOutput, or AnalogValue. Now the COVIncrement attribute can be selected from the attributes on the Columns tab. Note: If you need to change the COVIncrement values, you can do a mass change by selecting all the ones you want to change from the Listview and then right-click -> Set attributes.

Issue Can Continuum Engineering Units be changed and/or added to? Environment Continuum Cyberstation Continuum Infinity Controllers Continuum BACnet Controllers Cause Want to change or add an Engineering Unit as the unit I require is not present. Resolution Engineering Units are handled differently depending on the type of controller being used. Infinity Controllers are able to have there units defined to be whatever you want (defined as up to 12 digits of text) in the Units field of the Input or Output object.   BACnet Controllers Input and Output Units are predefined by the BACnet specification and are chosen from a set list of Engineering Units. These cannot be changed or added to.  

Issue When browsing for an object to attach to a control in the Graphics the object is seen in the Browse window yet when the object is selected the system generates the error 'Object Not Found' Environment CyberStation PinPoint Cause There is a 'space' or other non alpha numeric character in the name of one of the objects that form the full path to the object being selected. The offending character can be in the Network name, Main Controller name, Field controller name or the name of the object itself. Resolution The exact root cause of this problem is under investigation as the space character is valid in Continuum object names. In databases that have exhibited this problem the solution has been to remove the space (or other offending character) from the name. It has also been noticed that once the problem is fixed the original name can be restored to the object and the problem does not come back.

Issue Comm4 on the NC2 is RS-422, will this operate as RS-485 if the TX & RX lines are linked? Environment CX9680 NCII with Modbus RTU X Driver XDriver Cause Linking the TX & RX lines can cause the transmitted data to be fed back into the transmitting controller. Resolution Yes, you can use comm 4 as a Modbus RTU X Driver to talk to 3rd party RS-485 devices. The Netcontroller II Comm 4 is defined as an RS-485/ RS-422 port and the X Driver will close off the RX port using the RTS line while it is transmitting. The loopback required for a 2 core screened cable is: Connect TX+ to RX+ Connect TX- to RX- Use shield connection Note: If communications are still not able to be established, confirm that the Comm4 configuration in the Netcontroller II's web configuration page has been changed from the default RS-422 to RS-485.

Issue Are DDC Controllers Leadership in Energy and Environmental Design Certified? Environment Site wanting Green Building Council Certification Cause Are DDC Controllers Leadership in Energy and Environmental Design Certified? Resolution The USGBC does not certify particular devices or controls systems such as I/NET, Continuum, or Xentas. LEED focuses on the design of the building and not on its actual energy consumption, and therefore it has suggested that LEED buildings should be tracked to discover whether the potential energy savings from the design are being used in practice. Five basic categories make up the design points system. Totaled together, these points determine your certification level. The level of certification depends upon the total number of points. As you can see, energy and atmosphere along with indoor environmental quality factors make up half of the available basic points. Five categories for accumulating points 1. Sustainable sites.... 26 Points 2. Water efficiency ....14 Points 3. Energy and atmosphere ....35 Points 4. Materials and resources.... 10 Points 5. Indoor environmental quality.... 15 Points 6. Innovation and Operations.... 6 Points 7. Regional Priority.... 4 Points Subtotal: 100 Points LEED 2009 for Existing Buildings: Operations & Maintenance 100 base points; 6 possible Innovation in Operations and 4 Regional Priority points Certified 40–49 points Silver 50–59 points Gold 60–79 points Platinum 80 points and above The U.S. Green Building Council is a national, non-profit organization that works to “promote the design and construction of buildings that are environmentally responsible, profitable and healthy places to live and work” (USGBC Mission Statement). The USGBC created the Leadership in Energy & Environmental Design® (LEED) Green Building Rating System. LEED was fashioned to provide a standard of measurement for defining a “green” building. It takes a whole building approach that encourages and guides a collaborative, integrated design and construction process. The program evaluates and recognizes performance of your buildings in accepted green design categories—Energy & Atmosphere, Water Efficiency, Materials & Resources, Indoor Environmental Quality and Sustainable Sites. Buildings are given a certification rating based on the number of points they receive in their evaluation. The four levels of LEED certification include: Certified Level, Silver Level, Gold Level, and Platinum Level. By becoming certified, building owners are given third-party validation of their contribution environment; qualify for various state and local government incentives; contribute to the growing knowledge base; receive a LEED certification plaque and official certificate; and receive marketing exposure through the USGBC website, case studies, and media  

Issue Microsoft Visual Studio causes Just-In-Time Debugging Environment Windows Operating System Cause Visual Studio is installed on the PC and when attempting to perform a task, an error appears claiming Just-In-Time Debugging.  Resolution To disable Just-In-Time debugging: On the Tools menu, click Options. In the Options dialog box, select the Debugging folder. In the Debugging folder, select the Just-In-Time page. In the Enable Just-In-Time debugging of these types of code box, select or clear the relevant program types: Managed, Native, or Script. To disable Just-In-Time debugging, once it has been enabled, you must be running with Administrator privileges. Enabling Just-In-Time debugging sets a registry key, and Administrator privileges are required to change that key. Click OK.

Issue Some Alarms are not being sent as Emails, while others on the same site are being sent properly. Environment Continuum BACnet bCX1 b3xxx Cause Some EventNotification objects were not configured properly to enable email on alarm. Resolution Ensure that each EventNotification is enabled to allow alarms to be sent as Emails. There are two options that need to be enabled in each EventNotification.   1. Actions tab - Enable "Email on Alarm".     2. Delivery tab - In the Recipient, enable "Primary Email".