Building Automation Knowledge Base

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.

Issue Most of the xDriver points provide bit (binary) information in a word(integer) point in order to save register address. In order to interpret/decrypt the bit information out of the word(integer) value, PE programming is required. Environment Net Controller (CX99xx, CX96xx) bCX controller (bCX4040) ACX5740/5720 Cause Bit information is displayed as a number in the controller when read in to.  Need to have PE function to decrypt the number in to each bit information. Resolution Create InfinityProgram in the Controller as below; ' = = = = = = = = = Numeric locNum1 Numeric nBit0, nBit1, nBit2, nBit3, nBit4, nBit5, nBit6, nBit7, Numeric nBit8, nBit9, nBit10, nBit11, nBit12, nBit13, nBit14, nBit15 Line ReadAndSet   locNum1 = CIAlarms ' Read the xDriver point and set to local point.   Goto AAA Line AAA   ' Decrypt each bit information from the locally mirrored point.   nBit0 = (locNum1 bitand 2 ^ 0) > 0     nBit1 = (locNum1 bitand 2 ^ 1) > 0    nBit2 = (locNum1 bitand 2 ^ 2) > 0  . . . . .    nBit15 = (locNum1 bitand 2 ^ 15) > 0    Goto BBB Line BBB   ' Do something here for each nBit0~nBit15 such as below   ' If nBit0 then   ' set InverterTempAlarm = On   'Set the global point to ON   ' Else   ' set InverterTempAlarm = Off   'Set the global point to OFF   ' Endif   . . . . . .    Goto CCC Line CCC   ' Wait for 15 seconds and send to the first line to read the xDriver point again.   If TS < 15 then Goto CCC   Goto ReadAndSet Line E   If TS < 30 then Goto E   Goto ReadAndSet ' = = = = = = = = =

Issue What is the format of the SNMP alarm traps and where can I obtain the MIB's Product Line Andover Continuum Environment Netcontroller II CX9680, bCX1 & ACX57xx with SNMP alarming enabled. Cause Documentation on the SNMP Alarming is required. Resolution The Configuration guide for SNMP Alarming can be downloaded from The Exchange Download Center, link: Andover Continuum v1.9 SNMP Configuration Guide This will detail how the SNMP alarming is configured and operates. The SNMP Alarming sends the same alarm messages as shown in the Continuum alarm viewer out to the third party system via SNMP traps. The format of the traps is defined by Management Information Blocks (MIB's) these can also be downloaded from The Exchange Download Center, click on the following link: SNMP MIBs There is no facility to change these formats within the controllers or Continuum

Issue Getting modbus devices to communicate to Continuum may require some trial and error. Product Line Andover Continuum Environment Continuum Modbus RTU, ModbusRTU Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Manufacturers of modbus devices may have an offset for their register values and addressing these values requires trial an error. Resolution This article was created as a starting point. There are a lot of tools and methods to get values from modbus devices communicating. This resolution discusses some important concepts as well methods for trying to bring values in. The Modbus RTU protocol is a Master/Slave style of protocol. The Andover Controls CX will be the master on the Modbus RTU network. There can be only one (1) master at a time on the Network. The Slave number is always set in the third party device. This could be either a hardware setting such as dip switches or a software setting. Modbus-IDA (also known as Modbus.org) has set the limit that the slave address can be between 1 and 247. Address 0 is allocated as a broadcast message. The Andover Controls x-driver can support addresses in the range of 0-255. The third party manufacturer should be able to tell you what the expected function codes are for the points that you are interested in. Modbus.org has defined the function codes in a very loose manner and leaves it up to individual interpretation. Andover controls supports the following standard function codes: 1-8 15,16. Since when you request information from a Modbus RTU device you receive the exact value that is in the register Andover Controls has provided some special function codes that will help to convert some of the common engineering values into usable values. The listing in the x-driver documentation shows the special function code, what is expected from the third party and the equivalent function code that is truly sent to the device. For instance if a point is a Intel float and resides in the 40,000 range then function code 245 would be used in the Andover Controls x-driver. This will still send out a function code 3 in the Modbus message but the x-driver will take the value sent in from the third party device and convert it into a usable float. Most confusion occurs when talking about the data registers, (also known as addresses or channels). Modbus.org has the following statements about the addresses in the protocol document. All data addresses in Modbus messages are referenced to zero. The first occurrence of a data item is addressed as item number zero. For example: The coil known as ‘coil 1’ in a programmable controller is addressed as coil 0000 in the data address field of a Modbus message. Coil 127 decimal is addressed as coil 007E hex (126 decimal). Holding register 40001 is addressed as register 0000 in the data address field of the message. The function code field already specifies a ‘holding register’ operation. Therefore the ‘4XXXX’ reference is implicit. Holding register 40108 is addressed as register 006B hex (107 decimal). Register number also known as address. When setting the start channel number parameter on the x-driver tab the x-driver is expecting the exact decimal address that you are looking to obtain. For instance: if a device shows a listing for the first point to occur at 40,001 then the start channel number is typically 0. This can be confusing since some manufacturers have decided to have 40,001 as being 1 and not zero while others manufacturer have decided that 40,001 is 0. There are two ways of determining how the manufacturer has started the numbering system for the device if it is not documented: Method 1 is a trial and error method. Where you set the value to minus 1 of the register address, the actual register address and plus 1 of the register address and see which one you a response from. Method 2 uses a third party software to poll all the points to see what addresses are populated. There are many shareware Modbus RTU software packages on the Web. One such program is called ModScan32 by Win-Tech. www.win-tech.com Number of channels. The least amount of channels that will be requested is 1 so number of channels should always be 1 or greater. If the data is stored in multiple channels then you will need to set the number of channels equal to the number of registers. If you are not using a special function code you will need to set up a separate numeric with a manual log with the number of entries equal to the number of channels. When you poll for the value of the channels the data will then be stored in the manual log of this second numeric. The first element of the log will be the first channel that is requested. For instance if a value is stored in registers 40,000 through 40,003 then the start channel number will be set to 0 and the number of channels would be 4. Another numeric with a manual log of 4 would be created and linked in the x-driver numeric by placing the name of the new numeric in the annex point parameter. Once the x-driver point is polled the returning information will be stored in the annex point. The manual log of the annex point will contain the data for the 40,000 register in location 1. The data for each subsequent register location will be in the next manual log location. I.E. annexpoint[4] will contain the data for register 40,003 The Modbus RTU x-driver is a poll on demand x-driver. What this means to the user is that either a Plain English (PE) program, graphic or editing the x-driver numeric will cause a poll to occur. It is best to mirror the x-driver point and use PE to poll the x-driver points. A simple program would loop through and perform a simple line of mirroredpoint = x-driverpoint. This will avoid multiple polls to the same point tying up more CX resources then necessary. Then you can use the mirrored point in programs and graphics. If you try to get values from a slave device that is offline (not responding) the x-driver will poll each point three times before it moves on to the next point. This will cause the CX scan time to rise to seconds instead of tenths of a second. It is helpful to have a single x-driver point in the third party slave device that will return a known value, (Product ID or serial number for example). This can be used to avoid running the scan time of the CX up if the slave device can not communicate. Inside of the polling program try to poll for the value of this point. If the value does not come back then skip the polling for the rest of the points for this slave device. This point can also be used as an alarm for the offline device as well. For example: 1: If ProductID1 = 15 then Mirroredpoint1 = x-driverpoint1 Goto 2 else Goto 2 endif 2: If ProductID2 = 15 then Mirroredpoint2 = x-driverpoint2 Goto 1 else Goto 1 endif Some data may come back as a value when you need only a bit of information. In this case you will need to use the Bitand operator in PE to extract the exact bit that you are looking for. As seen below the PE code will take an alarm point from a Liebert AC unit and break out the individual bits of information. AC9_Alarm1 = x_ac9alarm1 'setting the mirrored point AC9_CommFail = AC9_Alarm1 bitand 1 'extracting bit 1 AC9_LocalOff = AC9_Alarm1 bitand 2 'extracting bit 2 AC9_RemoteOff = AC9_Alarm1 bitand 4 'extracting bit 3 AC9_HiHeadPrs1 = AC9_Alarm1 bitand 8 'extracting bit 4 AC9_HiHeadPrs2 = AC9_Alarm1 bitand 16 'extracting bit 5 AC9_LossAirFlow = AC9_Alarm1 bitand 32 'extracting bit 6 AC9_StbyGlycolOn = AC9_Alarm1 bitand 64 'extracting bit 7 AC9_LiquidDet = AC9_Alarm1 bitand 128 'extracting bit 8 AC9_ChangeFltr = AC9_Alarm1 bitand 256 'extracting bit 9 AC9_HighTemp = AC9_Alarm1 bitand 512 'extracting bit 10 AC9_LowTemp = AC9_Alarm1 bitand 1024 'extracting bit 11

Issue How to retain an AccessEvent history of visitor names when using a generic pool of visitor access cards? (personnel)  Environment Continuum Cyberstation Cause Need to record a history of access events for visitor cards with the visitor name and the card number assigned to them at the time. Resolution Using the Personnel Manager. Setup a Personnel Profile for Visitors with default areas assigned. For example, use the existing "Visitor" profile. Setup a Personnel Profile for Visitors with no areas assigned. For example create a new one called "Visitor No Access". This will allow just the required distributions to be sent down to access controllers when they are required. Create a new personnel object for each visitor assigning a dummy card number to them with the "Visitor No Access" profile you created in step 1. Save the object. Issue a temporary card for that personnel with the "Issue Tmp Card" button; using one of your visitor cards and add area access by using the "Reset Access Rights" button to assign the "Visitor" profile created in step 1. After applying the changes to the Personnel object they will then distribute access down to the controllers. When the card comes back, restore the original dummy permanent card with the Restore Tmp Card" button and reset the access rights back to "Visitor No Access"; freeing up the visitor card to be used again. Save the object.   This will provide you with an AccessEvent audit trail of the visitor card number and the personnel name associated with it at the time it was being used.

Issue Infinity schedule randomly fails to turn on occupancy flag for a given day. Environment Cyberstation All IP level Infinity Controllers All i2 Infinet devices Cause Empty Holiday schedule can cause schedule issues, if you have not entered any events in your holiday schedule you need to add and inactive event at mid-night, adding this event does not have any effect in terms of changing the value of the schedule but solves a series of potential issues caused by the holiday schedule having no events at all in its event list. Resolution Add one event to Holiday schedule as follows: 12:00:00 AM - Inactive

Issue Trying to find all BACnet devices under a bCX by right clicking the device in the Continuum Explorer and selecting 'Find BACnet Device', no error is received but no devices are found even though there are BACnet devices on the bCX's MSTP port. Furthermore, a Wireshark capture shows who-Is message was qualified with bCX's device id. (example, who-Is, 2587214-2587214) Environment Cyberstation bCX4040 b3s Cause When a 'Find BACnet Device' is issued from a specific bCX device, Cyberstation direct the who-Is message to the particular device. Resolution To find all BACnet devices right click the root folder and select 'Find BACnet Device' from the root.

Issue Unsure how to enable Demo Mode and what features are available in this mode. Environment Cyberstation webClient Cause Need to know what features are supported and how to use demo mode. Resolution Demo mode will only work on a single PC (Single User mode not LAN mode) if there is no Continuum Security Key plugged into the Cyberstation. Make sure that you have never plugged in a Continuum Security Key to the workstation that you want to use in demo mode. (If you have and it is not working then go here.)   The demo mode gives you access to the following Continuum Security Key options: -B Badging Option -D Data Exchange Option – includes Personnel Import Utility -E Endura integration option -F FIPS 201 option -WCxPRO Option to add web.Client Pro to Single User CyberStation (SU), x user connections = 1, 2 With some limitations: Demo mode lasts for 4 hours and then the Cyberstation will pop a warning message before shutting down "Demonstration Mode" shows on the Continuum splash when starting Continuum. Only one network controller can be used and it must be ACCNetID = 1.   Note: When using Continuum v1.94, or greater, in Demo mode you might experience it being very slow to start, possibly taking up to two minutes to initially startup. See article here for further details.

Issue When attempting to follow the instructions for setting up RAS communication with a Windows Vista or Windows 7 PC, there are instructions that do no apply or RAS will not work. Environment Continuum Windows Vista Windows 7 Cause Microsoft changed the way that RAS is used to communicate in Windows Vista and Windows 7. Resolution RAS is not supported in Microsoft Vista and Windows 7 with Continuum 1.9x or 2.x. This is indicated in the notes on the compatibility matrix when Windows Vista was added as an OS. It's also indicated in 1.93 matrix and now includes this note for Windows 7.  It would require an  additional code revision to allow Windows 7 to work with future revisions of Cyberstation and since demand of RAS has slowed it is not in the roadmap.

Issue System generates error "No designated List View for class name" when right clicking a class and selecting view in the Continuum Explorer. Environment Cyberstation Cause This can happen after the default list views have been moved Resolution 1. Delete the default list view objects. 2. Run the Continuum Database Initialization utility. 3. Check the "Create Default List Views" box and update the database.

Issue Some actions selected in the event notification repeat each time an alarm is repeated and others do not Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Some actions can be repeated when using repeat alarms and others are not Resolution Actions that will repeat are:  Display alarm view- time stamp may be the only change Display Graphic Run Program Display Video All these items are listed in the points alarm tab with specific object links at the bottom   Actions that will NOT repeat are:  email pages beep blink print etc