Building Automation Knowledge Base

Issue In the Personnel Manager, the template field shows an error: "Error in datagrid DataGridViewComboBoxCell value is not valid." Product Line Andover Continuum Environment Continuum 1.93 and below Personnel Templates Cause Error occurs while attaching the Personnel Templates to a personnel from the Personnel Manager. The selected Template is not in the default template folder (Personnel Templates). Note: It is still possible to attach the templates through the method of CSV importing/exporting of personnel. If the Templates are created under the "Templates" Folder, this error occurs. The Personnel Templates should be created under "Templates\Personnel Templates". Resolution Select all the Personnel Templates and move them (Right Click + Drag) to "Personnel Templates" Folder. It will give you an option to "Move Here". See the below screen shot. Click on "Move Here" to complete moving the Personnel Templates. Alternatively: Go to the "Properties" of the Template, then change the path of the Owner.

Issue BACnet alarm Change Of State 'Alarm On' field is blank in the Algorithm page. Product Line Andover Continuum Environment CyberStation bCX4040 b3s Cause BACnet alarm type must match the type of point that is associated with the alarm in the AlarmEnrollment object. For example, a Change Of State alarm requires a binary point. Resolution Make the object BACnet object type match the alarm event type (Change of State, Change of Value, Out of Range etc). In this example of a Change of State BACnet alarm, when the appropriate binary point is associated with the alarm, the 'Alarm On' field looks like this:

Issue Access control site where doors are typically held opened during business hours don't want annoying alarms during the day, specifically the site wants door ajar alarms sent only from 5:00 PM (17:00) to 8:00 AM (08:00) Environment CyberStation Cause Configure a separate Event Notification with recipient time range specified in 'From Time' to 'To Time' columns. Resolution When configured as above the alarms associated with the notification object will be logged in the database but not displayed in the Alarm Viewer during business hours.

Issue bCX going offline and logging multiple 0x1408s in its error log. Environment bCX4040 ALL CX master controllers. Cause Excessive traffic on the network causes controller to run out of message buffers. Every time a controller receives a communication packet it has to allocate a block of memory (a buffer) to place the packet until it can be processed. Under normal network conditions the packets are processed at a rate that exceeds the rate at which they are coming in, in some cases typically associated with network configuration issues or malfunctioning nodes on the network, (i.e. broadcast storms) the firmware in the controller is unable to keep up with the amount of packets being received which exhausts message buffers available and renders the controller unable to communicate properly. In many cases the condition is temporary and does not result in a major problem, it is not unusual to see sporadic 0x1408s in the error log but when the condition persists for longer periods it will have an impact on the ability of the controller to communicate properly on the network. Resolution Identify and remove the root cause of the excessive traffic.   In the WireShark capture above, a constant WHO-IS sent out by BBMD devices due to part of the network being disconnected was causing a "WHO-IS storm" resulting in the bCX controller on the subnet to go offline and register several 0x1408 errors per minute.

Issue How do the controller settings affect the Occupation Sequence in respect of temperature control. Environment Stand alone. Part of a system. Cause Customer is uncertain of how this process works, the rooms are cold. Resolution There are a number of settings that will affect this sequence, the screen shot below shows the sequence and the settings used.  

Issue Photos are taken with a webcam, saved as JPG and loaded from the file into the personnel record. Was working fine previously. Now they are being stretched (distorted) when added to the personnel records. Environment CyberStation with Badging Option, webcam Cause In Make/Edit Badge >> Capture >> Options the checkmark had been removed from the "Allow cropping" checkbox. Since the photo dimensions were wider than high, the resulting un-cropped photo had white space above and below it in the Make/Edit Badge screen and when that screen was saved (using the OK button) the image was stretched to fill the photo field in Continuum.  Resolution In Make/Edit Badge >> Capture >> Options add the checkmark from the "Allow cropping" checkbox.

Issue PE Programin bCX/b3 seens as disabled/idle in list view even though program is running and operating normally. AS In the screen shot above the program is reported as ACTIVE and ENABLED from a Continuum perspective (List View on the Infinity side) BUT idle and disabled from a BACnet perspective. (List view on BACnet side) Printing the programs BACnet properties from the command line shows that the program is actually In Service and executing. Environment CyberStation bCX b3 BACnet Cause Inconsistencies between Andover and BACnet protocol which in some cases have conflicting property values. Resolution When looking at properties of BACnet objects from Cyberstation make sure to be aware of the context in which the properties are being shown (BACnet or Continuum) and ignore non applicable properties. For example, if looking at the program from BACnet perspective look at the OutOfService property instead of the State property.

Issue When using the User Entry option in a Graphic to enter a value, the decimal place in the number is dropped. Entering a 1.5 in the Graphic User Entry results in 15 showing up in the linked object, entering 0.5 results in 5. Fig.1 - Configuring User Entry   Fig.2 - Inputting value in User Entry "calculator"  Environment Continuum Cyberstation Windows Regional Settings Cause The decimal symbol in Regional Settings was set to a comma (,) instead of a period (.). The Region and Language Format was set to French (Canada) which by default uses a comma as the decimal symbol. When using the User Entry "calculator" to enter a decimal number the correct decimal symbol needs to be used. Using a period when it is set to a comma in regional settings results in the symbol not being typed at all. Resolution Check the Region and Language settings to see what the Decimal symbol is set to and use that symbol in the User Entry in a Graphic or change this to the symbol you want to use. French Format Setting with Comma Decimal Symbol   English Format Setting with Period Decimal Symbol

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.