Building Automation Knowledge Base

Issue Modifying the bypass occupancy override duration of a Xenta 102-AX Environment Xenta 102-AX LNS Cause There are several locations to change the bypass occupancy override duration on a Xenta 102-AX. Resolution To edit the bypass occupancy override duration from the Xenta 102-AX Plug-In: Open the Xenta 102-AX Plug-In Go to the Operating Parameters tab Alter the value under Bypass Override Duration (Hour, Min)   To edit the bypass occupancy override duration from an LNS Browser: Open the LNS Browser The value is represented in the format (days, hours, minutes, seconds, milliseconds).  If it reads (0,2,0,0,0) that would be an override duration of 2 hours. Alter the hours and minutes to the desired value, but leave the days, seconds, and milliseconds at 0.   To edit the bypass occupancy override duration from the Vista Workstation: Navigate to the Xenta 102-AX in the tree structure. Open the VAV_Controller module. Double click the point named UCPTovrdDuration The description breaks out separate values for days, hours, minutes, seconds, and milliseconds.  Alter the hours and minutes to the desired value, but leave the days, seconds, and milliseconds at 0.

Issue Changing ElecTypes on points on a Continuum BACnet controller after the system is saved into the BACnet side can cause major database mismatch problems, COV failures, deletion of EventEnrollment points and graphic points. (Updated 10/27/08) Environment Continuum BACnet Cause Continuum delete the defaults BACnet object type "AnalogValue" in the database and create a new BinaryValue or vice versa. Resolution In a continuum BACnet system, the Continuum BACnet controller creates a BACnet point for every Continuum point that is created on the Infinity side. For instance if you create an InfinityNumeric it defaults as a BACnet object type "AnalogValue" and creates that point in that class in the controller. If that controller is then saved into the BACnet side through Cyberstation it will create that point in the Continuum database under the AnalogValue class. If you then program other controllers to use that point, a COV subscription will be created to the controller owning that point. If you later remember that you wanted this point to be a digital point so you change the BACnet object Type to a BinaryValue. What then happens is the controller changes the class the point belongs to in the BACnet side. When the controller is saved into the BACnet side, Continuum will delete the AnalogValue Bacnet point in the database and create a new BinaryValue point in it's place with a new Object ID in the Continuum database. This creates several problems. The first issue will be that any COV subscriptions for this point will now fail, because the Plain English program that was referencing the point will still try to subscribe to the AnalogValue point, but it is now a BinaryValue point. Data Sharing will stop. The second issue will be that the Save on the BACnet side will find a duplicate point in a different class and it will delete the older AnalogValue point and create a new BinaryValue point. During this process it will also create this point in the BACnet database with the "Full Name" of the object the same as it's Alias. Because the system needs to keep the Infinity side and BACnet side in sync, it will replace the full name on the infinity point with the Alias. Further issues such as this point being used in a graphic, an EventEnrollment, a report, etc.. Will be deleted from these objects because it is now a different point and will have to be reattached to these objects. To avoid these issues You should first disable the BACnet preference "Automatically save new BACnet devices to Database". This will stop automatic database synchronization on the BACnet side when you are creating, deleting and changing points during the site commissioning and programming. Secondly you should create points with the correct BACnet object type before referencing them in a data sharing program. Third you should only save the points into the BACnet side after you have completed the correct point configurations in all classes (Inputs, outputs, numerics, etc). Finally, if after the system configuration and programming is completed, if you need to change a BACnet object type, you should first delete the point from the BACnet side of the database, change and save the point back to the controller, and then recompile any Plain English programs in any other controllers that were referencing that point for a COV subscription. The controller can then be saved back into the BACnet side. If that BACnet point was used in a graphic, or an EventEnrollment it will also need to be reattached.

Issue Red X in Internet Explorer when attempting to view certain Menta objects in a Xenta 700 Environment Xenta Servers Xenta 701, 711, 721, 731 XBuilder Menta Internet Explorer Cause When importing a Menta object into a Xenta 700 XBuilder project from a file previously created in the normal version of Menta, be very careful with all the comment text within the file. All comment text has to have a defined text type in the file. For example say you had a Menta file with comments throughout that you set all of your font to Arial, bold and 10 point font. Then you created another file and copied the contents of the original file into the second file. You will lose the text attributes of Arial, bold and 10 point font but the normal version of Menta will still display the comments correctly. Now, if you import that second menta file into a Xenta 700 XBuilder database and download the Xenta 700, you will have problems. If any comment text does not have text attributes, Java can not load the file to be viewed in Internet Explorer / Menta viewer and you will get the red X when the file loads. Resolution Go through the entire Menta object in XBuilder, double clicking any comment. Focus efforts on any comments that are known to have been cut and pasted into the file. Check that a font, style, and size it attributed to each comment. Fix and redownload the XBuilder project.

Issue Upgraded Vista 3 to Vista 5 and Digital Points can not be changed on OGC graphic page Environment Vista 3 system upgraded to Vista 5 Digital points OGC Graphics Cause This behavior has only been seen after a upgrade from Vista 3 when following the recommended upgrade path and does not effect every single digital point. Resolution The inability to control a digital point in an OGC graphic page on Vista 5 Webstation can be fixed by opening the offending graphic page in the graphic editor and then saving it back to the Vista DB.

Issue When running I/NET Seven rev. 2.15, in the I/O Server editor, the "CCTV" button is Grayed out Environment I/NET DVR CCTV Cause Errors occurred during installation Resolution CCTV new DLL file Install Process from I/NET Seven CD (Rev 2.14 and above)  Load the I/NET Seven CD in the CD drive unit (D:\). The CD will try to auto-load, cancel that install. Then go to this location on the CD D:\Support\RVCTL_DLL\Rev 3.6.0.1 Copy the three DLL files (ijl15.dll, rvctl.dll & rview.dll) from the CD. Then paste them into this location C:\Program Files\INET Seven You must register one of the copied DLL files into the Windows Registry. Please follow these steps: Open a “CMD” prompt. Use Start>Run, type cmd and select OK Type the following: Cd\ Cd \Program Files\INET Seven Regsvr32 rvctl.dll You will see a message box with the message “DllRegisterServer in rvctl.dll succeeded” The CCTV Button in the I/O Server is now available to be used for integral DVR’s

Issue Arm/Disarm for I/NET IAS Environment I/NET IAS Cause Configuration Assistance Resolution Are you in the process of using I/Net as an IAS (Intruder Alarm System) and it is not working as you expect? Meaning that you can read a card, but it does not allow access to the door after the pin and code is entered? There is sequence that needs to be followed to ensure that this works properly:  Program door for equivalent reader and PIN if this feature is used. Set the ATS for Sec/Pin Select Features and program these as required Click OK and close out of that Editor, then select Schedules. Verify that the features are available and select the ones that will correspond to the ones set up in step 3 above. Hit OK and exit out. Press # Read card Enter PIN (either enter a leading 0 or press # to complete the string) Press #, the lights should be blinking red/green at this point Press 0 (function code entered in the function editor) Press 1 to Arm or 2 to Disarm

Issue "Network interface is being initialized" when using Remote Serial Port Driver in Vista Environment Remote Serial Port Driver (RSPD) Cause If using the Remote Serial Port Driver and seeing a "network interface is being initialized" error message in Vista when viewing points, then it might be an issue with the operating system and its Data Execution Prevention (DEP) setting. This problem is most likely found in Windows Server 2003 due to Microsoft using the wrong value as default in SP1. Resolution Verify that the Data Execution Prevention settings are configured for "Windows Services only" rather than "all programs" Reinstall the Remote Serial Port Driver program

Issue There is an error message on the LCD display of the old style Infinet controllers. What do these errors mean? Product Line Andover Continuum Environment Infinet Controller Cause Information on the error code received on the LCD display. Resolution Infinet controller is displaying error 1 on its LCD display. This message indicates that the controller received a bad packet of data on the Infinet. If the problem persists follow troubleshooting instructions. Verify Infinet cable connections, approved twisted shielded pair cable, less than 4000 feet of network cable between Infilink repeaters, no more than 31 controllers between Infilink repeaters. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Check the baud rate switch on the Infilink repeater module, although the Infinet controllers auto baud, the Infilink baud rate must be manually switched. Break down the network in segments to identify the bad controller or network segment. A binary search is recommended. (i.e. break the network in half, if this resolves the problem add half of the deleted back on, if it does not resolve the problem cut the remaining network in half, etc.). Once the offending segment has been identified, troubleshoot to the cable segment or controller level Infinet controller is displaying error 2 on its LCD display. This message means that it could not pass a token to another controller on the Infinet. If the problem persists follow troubleshooting instructions. (No response to the Infinet token pass) Verify Infinet cable connections, approved twisted shielded pair cable, less than 4000 feet of network cable between Infilink repeaters, no more than 31 controllers between Infilink repeaters. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Check the baud rate switch on the Infilink repeater module, although the Infinet controllers auto baud, the Infilink baud rate must be manually switched. Break down the network in segments to identify the bad controller or network segment. A binary search is recommended. (i.e. break the network in half, if this resolves the problem add half of the deleted back on, if it does not resolve the problem cut the remaining network in half, etc.). Once the offending segment has been identified, troubleshoot to the cable segment or controller level Infinet controller is displaying an error 3 on its LCD display. This means that the input reference voltage is out of range on the analog inputs. Verify that inputs coming from external transducers are not exceeding the voltage input range, either 5 or 10 volts depending on model, if so use a voltage divider on the input. Verify that any input wiring is not run in the same conduit as high voltage cable, or is properly shielded and grounded. If there is voltage getting coupled into the input wiring, separate the input wiring from the interference, or shield the cables. If the interference is being caused by the end device such as an auxiliary contact form an high voltage device, a cap between .01 and 1 microfarads across the input terminal to earth ground may alleviate the problem. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it. Power down the Infinet controller and restart while connected to network. This will eliminate this unit having a duplicate ID on the network and it will also run the power up diags. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it. Infinet controller is displaying an error 4 on its LCD display. This means that the analog output reference voltage is out of range. Verify that inputs coming from external transducers are not exceeding the voltage input range, either 5 or 10 volts depending on model, if so use a voltage divider on the input. Verify that any input wiring is not run in the same conduit as high voltage cable, or is properly shielded and grounded. If there is voltage getting coupled into the input wiring, separate the input wiring from the interference, or shield the cables. If the interference is being caused by the end device such as an auxiliary contact form an high voltage device, a cap between .01 and 1 microfarads across the input terminal to earth ground may alleviate the problem. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it. Power down the Infinet controller and restart while connected to network. This will eliminate this unit having a duplicate ID on the network and it will also run the power up diags. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it. Infinet controller is displaying an error 5 on its LCD display. This indicates the controller underwent a reset of power down and retained memory ( warm start). If there is not reason for this to occur power outages etc., then troubleshoot the problem. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Measure the AC power at the controller, Verify it is within specification (nominal +/- 20%). Typically 24 VAC power that is daisy chained will drop the voltage along the connections leaving the power below the acceptable level even if the transformer is sized correctly. Verify that any outputs that are driving inductive loads such as relays, actuators, or valves, have a varistor across the coil n the field device. Verify that any input wiring is not run in the same conduit as high voltage cable, or is properly shielded and grounded. If there is voltage getting coupled into the input wiring, separate the input wiring from the interference, or shield the cables. If the interference is being caused by the end device such as an auxiliary contact form an high voltage device, a cap between .01 and 1 microfarads across the input terminal to earth ground may alleviate the problem. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it.

Issue SCU in double-address mode and the second station is not responding. Once a card is read at any of the readers, a Reader Entry is displayed in the Transactions Window but the strike never fires. The DO point can be manually controlled through Software but not by any of the readers. Environment I/NET SCU1284 Cause The MCU Configuration must be set to restore the DPU. Resolution Connect to the controller, then go to MCU Configuration. Both of the addresses on the DPU should be Blue. Turn the second address to Internal and exit the editor. Open the Editor again and change the setting to DPU. Perform a DPU restore and try the card again. A Reader Entry should show up in the Transactions Window and the strike should fire, indicating that it is working properly.

Issue Anti-PassBack (APB) Flag functionality Environment I/NET Seven APB Cause Anti-Passback flags will not broadcast across links Resolution Keep in mind the limitations of the APB flag. The broadcast of the APB flag will not cross links nor is it intended to cross links. An NPR is used to connect links to a front end or to another link. The APB flag cannot be broadcast through this device. Only doors and controllers on the same Link (CLAN) as the sending device can receive the APB broadcast. When designing APB systems, ensure that doors for the same zone are all on the same link.  

Issue Niagara R2 UNCs using the bacnet-2.305.523b.v1 (or newer) jar file may need  have the bacnet.properties file modified in order to work properly. Environment Niagara R2 UNC with bacnet-2.305.523b.v1 will need the bacnet.properties file modified in order to work properly. If the station is upgraded to bacnet-2.305.527i.v1, -2.305.529.v1, or -2.305.232.v1, the bacnet.properties file modified in order to work properly. New stations created with bacnet-2.305.527i.v1, -2.305.529.v1, or -2.305.232.v1 will have the correct bacnet.properties file  by default. (revised 9-23-2011) Cause Upgrading bacnet jar files. Resolution Two lines near the end of the file must be un-commented by removing the leading # sign. The two lines are: pollHeartbeatCheck=true PollRestartEnabled=true No other modifications to the file are recommended. The UNC must be rebooted to utilize the revised settings. (revised 9-23-2011)

Issue Creating Critical, Priority, Routine, Transaction event pages on a 527/731 Environment Xenta Server Xenta 527, 731 Cause When using Vista to access an I/NET network you have 4 views for the Alarms and transactions. To create these views on the web with a Xenta 527 or Xenta 731 you will need to create event pages with different filters. Resolution Add a new event page in Xbuilder and use the InetAMT filter file. Right click on the event page and select Setup Event Viewer. Click the filter icon in the top left corner and use the following guidelines for the type of page you are trying to create: Critical Alarms - Priority From 1 To 1 Priority Alarms - Priority From 2 To 2 Routine Alarms - Priority From 3 To 3 Transactions - Tenant: * Each event page will have a different filter. To match I/NET or Vista you will need to create four pages.

Issue OPCEnum not at remote OPC server Environment Vista OPC Server Cause Some times the OPCEnum will not exist on remote PC with server installed. In this case, Vista can not find the OPC server and DCOM can not be configured for OPCEnum. Resolution Download and install this small package, and you will have OPCEnum installed. http://ftp.softwaretoolbox.com/support/updates/OPCEnumInst.exe

Issue Lon Tunneling does not function with Workplace Tech 5.7. Environment Workplace Tech 5.7 Cause In order for Lon Tunneling to work, the Echelon OpenLDV Network Driver, version 3.4 is a requirement. Resolution To determine what driver version is currently installed, follow the steps outlined on page 7 of the WPT 5.7 Installation Instructions (F-27367-4). If "Echelon OpenLDV 3.4" is not listed, install the Echelon OpenLDV Network Driver software. The installer file for this driver is provided on the WPT 5.7 CD or it can be downloaded from The Exchange Download Center: 153-0212-01A_OpenLDV340.exe. Alternatively, it can be downloaded from the Echelon website (www.echelon.com). In order to download from Echelon’s website, a (free) user account is required. Once it is created, proceed to “Recommended Downloads” and the LDV driver will be listed (towards the bottom):"OpenLDV 3.4 Network Drivers for Windows Vista/XP/2000/Server 2003 (includes drivers for i.LON 10/100/600 RNI, PCLTA-20/21, PCC-10, and U10/20".

Issue Monitoring duct temperature on a Xenta 102-AX without putting it into Morning Warmup (Central Plant Heat) mode Environment Xenta 102-AX Cause The Xenta 102-AX Plug-in allows you to configure the hardware inputs for several different purposes.  If you configure Universal Input 1 as a duct temperature, that is assuming duct inlet temperature.  Any time the duct inlet temperature is higher than the room temperature (suggesting that central plant heat is being provided by the air handler) the action of the damper will reverse and the box will show HVAC_MRNG_WARMUP as its application mode.  If it is really the duct reheat outlet temperature that is being measured, this could be an undesirable result. Resolution There are two options to read in a duct temperature without it affecting the internal logic of the Xenta 102-AX.  The recommended method is: Connect the temperature sensor to Universal Input 1. Configure the Xenta 102-AX Plug-in, Hardware Configuration, Input 1 Section to "None." This will continue to report the temperature on UnivIn1_Sense.nvoAuxTemp1 but will not affect the internal logic of the controller. The other option is: Connect the temperature sensor to Universal Input 3. Configure the Xenta 102-AX Plug-in, Hardware Configuration, Input 3 Selection to "OA Temp. Sensor." This will report the temperature on UnivIn3_Sense.nvoAuxTemp2 but will not affect the internal logic of the controller.  

Issue Xenta 102-AX goes to Unoccupied Minimum airflow setpoint instead of Heating Minimum airflow setpoint when in HVAC_HEAT mode Environment Xenta 102-AX version 2.17 and prior Cause Revision 2.12 of the 102-AX added the capability to do airflow reset in heat mode. To do that, it uses warmup high flow to create the range to reset. If that setting is lower than the heating minimum airflow setpoint, it does not know what to do and reverts to the unoccupied airflow setpoint. Resolution Set the warmup high flow setpoint to be greater than the heating minimum flow setpoint. The warmup high flow setpoint should not be set to 0 even if there is no warmup/central plant heat on the unit. Alternatively, upgrading the Xenta 102-AX firmware to version 2.18 or newer.

Issue Creating a Backup of the SQL Database Environment I/NET Seven Cause A backup of the database should be done once a month, at least, to ensure that everything is saved in the event of a crash or an upgrade is needed. This will assist in getting the system up and running again with little or no downtime Resolution Close I/NET and I/O Server Go to Start > Programs > I/NET and select DBCreate Utility Log on using the username/password that was created when I/NET was installed Select the option for backup database Select the location where this backup would be placed. Preferably on another folder outside of I/NET Select Start and name the file the date that it is being done on for easy reference and then let the program run Upon completion, verify that the file was created with the date and time stamp.

Issue Can a Master schedule in a Niagara R2 Enterprise server station trigger slave schedules residing in a PollOnDemand object in a UNC station? Environment Niagara R2 Enterprise Server UNC station Cause To trigger slave schedule, be sure to link a slave calendar to the slave schedule. Resolution Schedule objects do not care that the folder is PollOnDemand. Only driver points (ie. shadow objects) will be affected by the fact that their parent is a PollOnDemand container. Be sure that there is a slave calendar linked to the slave schedule in the same station. Calendar to schedule links do not work across an external link.

Issue How can you tell the difference between a I2/B3xxx -V and a I2/B3xxx controller through Continuum Explorer? Environment I2/B3xxx I2/B3xxx -V Cause Determine the version of a controller remotely through Continuum Explorer Resolution In Continuum Explorer, right click to edit a I2/B3xxx -V controller Select the runtime tab Looking at the version of the controller is the way to distinguish between the different Models. The I2/B3xxx -V will have a version number similar to 3.501027 A regular I2/B3xxx will have a number similar to 3.300006. Notice the location of the 1 in the -V version number. The -V models will have the 1 in the location as above while the non -V model will not.

Issue Continuum single user system database backup with SQL 2005 Express. Environment Continuum Cyberstation single user (SU) Cause Method to backup system database. Resolution Continuum single user system database backup with SQL 2005 Express. Using SQL Express Management tool Right Click on the Continuumdb> Tasks>Backup Add a Destination where you want the .bak file to be located Click Ok Using sqlcmd With the limited release version of Continuum 1.82 and future 1.9x releases SQL 2005 Express will be the database platform that is used for Single User configurations. Some of you may remember backing up databases in earlier versions of SQL from the windows command line and recall having to create a backup device in order to perform the backup operation. This is the case for backing up a database in the SQL 2005 Express version as well.  Open up the Windows command line and type in CD\ and press enter. This puts us at the root of the drive. Log on to the SQL 2005 server, by typing sqlcmd -Syourmachinename\sqlexpress and press enter. You should see 1> at this point. If you do not see the 1> prompt at this point, a few things could be going on. Make sure you type in your computer name without spaces following the -S switch. Another problem could be that your user logon doesn't have admin privileges. You need to have admin privileges to backup the database.  Once at the 1> create a backup device. Type EXEC sp_addumpdevice 'disk', 'MyDBbackup','c:\myTest.bak' and press enter, which should bring you to the 2> prompt At the 2> type in GO And press enter. This will create a device that we can now use to backup the database. The device should only need to be created once. Now that we have a device named MyDBbackup (you can name yours differently) and are at the 1> again, type in BACKUP database continuumdb TO MyDBbackup with init press enter and you should be at the 2> now type in GO You should have a backup of your database at the root of c:\ named mytest.bak It would be a wise idea to write down the name of the device you have created, since you can use the same device again.  Using the windows task scheduler, you can setup a task to backup your database automatically at the times you've specified in the task scheduler is an easy thing to do.