Building Automation Knowledge Base

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 A system with NIC852 keys has difficulty getting the Loytec Ports to come online after an upgrade to Vista 5.0.3. Environment Vista 5.0.3 NIC852 Loytec Ports Orion Stack Cause There was a product enhancement with 5.0.3 that Loytec PCI-709 network interfaces were replaced by NIC709-PCI100 (Vista Orion stack) Resolution Upgrade the LCONFIG software to the newest 3.0.1 version. This software is available from http://www.loytec.com.  

Issue In Niagara R2, device objects are not updating. Bundles were used to speed the linking to graphics. Environment Niagara R2 Cause The device objects are in bundles. Resolution Only native Niagara objects should be placed in bundles. This includes the Niagara AO, BO, AI, BI, and logic (if desired). Due to the nature of bundles they execute at their own rate. This interferes with the normal execution of BACnet, LON, GCM, ASD, DMS, MS and other hardware objects. For additional information on the use of bundles refer to The Standard Reference Manual pages 7-14 through 7-21 and pages 5-1 through 5-6 of the Web Solutions Guide.

Issue After upgrade of Xbuilder or opening a project built on another computer generating the project causes a "File not found:" error message.   Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment XBuilder Cause Find the alarm or event page that is causing this problem and view the reference field to identify the cause of the problem.   XBuilder was upgraded and the xmle files from the previous version are no longer present. XBuilder installation directory was on a different drive on the computer the project was last used on. Resolution In Xbuilder, right click on all the Alarm and Event pages, select Change reference, and browse in the new path to the referenced file.  

Issue I/NET Utility Patch - Upgrading I/NET 2.14 and above. Environment I/NET Cause Two directories are required C:\Program Files\INet Seven and C:\INet Seven Data. These changes occurred as a result of requirements for future release revisions of I/NET and Microsoft Vista - Microsoft 2005 Server Operating System.   Resolution When upgrading I/NET Seven revision 2.14 and above to the later versions using the patch on the web, you are required to run the utility patch twice. Note: When I/NET is compatible with MS Vista and MS 2005 Server a release announcement will be published. Caution: You should always perform a data base backup before you start any upgrade process. A new install of 2.14 will create the data directory in a different location than prior revisions. An upgrade install will not move the data directory from its current location. The patch utility is unable to determine that the data directory has moved. Therefore, it needs to run against both the program directory and the data directory. The following steps should ensure this is done properly: Using the patch utility, point to the program directory by selecting C:\Program Files\INet Seven and execute. Once completed, run the utility again and now point to C:\INet Seven Data and execute. This ensures that both the program files and bin files have the correct version for that revision. Note: Prior to starting I/NET force an upgrade on the database using the DBCreate Utility.

Issue Unable to create new OGC graphic pages in Xbuilder 5.0.2 or later.  The edit option has been grayed out and I cannot open the OGC graphic editor. Environment XBuilder TGML Graphics Editor Vista Cause In Xbuilder 5.0.2 the system was changed to support UTF-8 character encoding. Since OGC Graphics pages cannot support this change all new graphic pages added to XBuilder will be forced to be TGML pages which support the UTF-8 character encoding.  Resolution OGC graphics created in earlier versions of XBuilder will still display properly when those projects are upgraded to newer versions of XBuilder but they can no longer be edited. If changes need to be made to these files you can follow one of the two options listed below:  #1. In order to make changes to these graphics the files must first be upgraded to TGML graphics. This is done by opening the OGC graphics with the TGML editor and the graphics will be automatically updated. #2. It is possible for 2 versions of XBuilder to reside on one PC. You can download the 5.0.2 version of XBuilder and use this version of the tool to make the necessary changes. Once the changes are made you will save the project and open the edited project in the newer version of XBuilder.  

Issue When you run VisiSat after a reinstall you have lost all your network and remote site information. Environment Visisat Cause The process of uninstalling VisiSat removes the file. C:\Satchwell\Binary\VisiSat\SITES.DAT (default installation folder). This file holds the remote site information. Resolution Copy the SITES.DAT file before uninstalling VisiSat. When you have installed the later version of VisiSat copy the SITES.DAT file back to C:\Satchwell\Binary\VisiSat\SITES.DAT (default installation folder). Create a remote network The modem numbers should be there

Issue COV subscription links are being lost between MNB controllers Product Line TAC IA Series Environment MNB Controller Cause This is caused specifically by changing certain required link properties or by removing the objects that contain the link data. Resolution See TPA-RKFD-08-0001.00 "Avoid accidentally removing COV subscriptions (links) between MNB controllers" on The Exchange Download Center.

Issue Control loops linked via antlers. Environment Control objects Cause When a number of Control objects are used for multi loop control. The lower stage output antler of Control loop in some cases failed to function correctly; the Antler node connection going to '---'. Resolution This has been corrected with MicroNet 50 controller Firmware version 5 released August 2008. Additional information on firmware 5 can be found in TPA-LOND-08-0014.00

Issue How can a WorkPlace Tech application be identified as created/edited with version 3.2sp1 (or older) so it can be converted by WPT 4.x or WPT 5.x? Product Line TAC IA Series Environment WorkPlace Tech Cause Jobsite with an installed base of MNL or MNB controllers but the version of WorkPlace Tech used is not known. Resolution NOTE: Do not allow the application to be converted, if so prompted. Open the application file in an appropriate version of Visio. (WorkPlace Tech not needed). While holding down the left-shift key, right click on the background of the application and select "Show ShapeSheet", holding the left-shift key down until the ShapeSheet window is displayed. Verify that the text table window that is opened shows the file name followed by "". If not, close the shapesheet window and repeat step 2. The left-shift key must be held down until the ShapeSheet table is displayed. Look for the "User-defined Cells" table in the displayed information and verify that an entry named "User.wptVersion" is shown. This field will show the version of WorkPlace Tech that created the application. If either the "User-defined Cells" section or the "User.wptVersion" field are not displayed in the shape sheet, the application was created / edited with a version of Workplace Tech prior to version 3.2sp1. Close Visio. Respond by clicking NO if Visio prompts to save the document. In Visio 2010, the ShapeSheet is located on the Developer tab, which is not displayed by default. To show the Developer tab, do the following: Click the File tab. Under Help, click Options. Click Customize Ribbon. Under Customize the Ribbon, select the Developer check box. To open the ShapeSheet, do the following: On the Developer tab, in the Shape Design group, click the arrow below Show ShapeSheet and then do one of the following: To open the ShapeSheet for a selected shape, click Shape. To open the ShapeSheet for the active page, click Page. To open the ShapeSheet for the entire drawing, click Document.  

Issue Can certain Analog Input values be read with up to 3 decimal places in WorkPlace Tech? Environment WorkPlace Tech MNL series MNB series MicroNet 2000 Network 8000 Cause The MNL, MNB, MicroNet 2000 and Network 8000 controllers have the capability of working with values from -163.83 to 16,383 and never use more than 2 digits after the decimal place. This is something that all of the controllers have used for many years. This is documented on page 25 of WorkPlace Tech Tool 4.0 Engineering Guide (F-27254). Resolution In certain applications where it is necessary to read very small values beyond 2 decimals, a work around has been used.  The technique should only be used by those who fully understand the concept and its implementation.  The technique to overcome this is to set the output scaling factors of the Analog Input object (in WorkPlace Tech) to values at a factor of 10 or 100 (or other suitable number) thus giving the resolution and therefore (no loss of) accuracy that is required.  This requires scaling the value down by the same factor at the head-end (or wherever) to get the proper and accurate reading.  Multiply the scale properties by a factor then divide by the same factor for display or logic calculations. Example:  A pressure transmitter that reads a pressure range of -.25 to .25 in. wc at 4 to 20 mA, the Analog Input properties needed for such a transmitter would be as in this table: Input Low Value:     4 mA Scaled Low Value:  -.25 inwc Input high Value:     20 mA Scaled High Value: .25 inwc There is an issue with a device that has such small sampled values.  The controllers can only register at most 2 digits after the decimal.  Therefore the controller can be fooled by setting the properties such that the controller thinks that it has a device transmitter attached that reads pressures from -25 to 25 In. WC.  This is a factor of 100 and all values would be 100 times larger than the true reading.  This of course needs to be accounted for in any calculations and GUIs.  The properties for this would be as in this table. Input Low Value:      4 mA Scaled Low Value:  -25 inwc Input high Value:     20 mA Scaled High Value: 25 inwc In using this technique, remember to factor the number when displaying it or using it with other logic.  Since the controller can use negative numbers no smaller than -163.83, no properties can be entered smaller than that value.  In the table below the same transmitter is used but a factor of 1000 is used for the properties.  This can not work due to the scaled low value being less than -163.83. Input Low Value:     4mA Scaled Low Value: -250 inwc Input high Value:     20 mA Scaled High Value: 250 inwc The workaround is well proven and sufficient to satisfy needs.

Issue Is there any way to setup Niagara R2 station passwords such that they expire and must be changed on a periodic basis? Environment Niagara R2 station Cause No settings to define password expiration. Resolution This feature is not available in Niagara R2.

Issue Upgrading from rev 2.1X to 2.16 Environment I/NET 2.1x site Cause desire to upgrade to newer release of I/NET Resolution When upgrading from revision 2.10 and higher to 2.16, there is an additional step that is required. If you get to 2.16, start I/NET and only question marks are displayed when you connect to the controller, or it takes a long time to connect. There are two work-around things to try for this. Run the 2.15 patch or reinstall 2.15 and then upgrade to 2.16. Run DB Create, force an upgrade to the database and verify that the database version does in fact match the revision that you are running. To get to the revision number, click on the header on DB Create, then select about, it would show this information. The other work around is to just close I/NET and I/O Server and restart them again.

Issue Will VisiSat work with Visio 2002 Environment VisiSat Visio 2002 Cause VisiSat Version 2.1 build 148 service pack 1 will not work with Visio 2002. Resolution Although we would recommend using the latest version, VisiSat Version 2.1 build 137 can be used with Windows XP Pro and Visio 2002. VisiSat Version 2.1 Build 137 is available for download via Exchange OnLine. Note: File size = 30 Mb.  

Issue How do I select an actuator and valve combination? Environment Actuator Valve Cause Select the correct actuator and valve part numbers. Resolution Refer to the TAC Catalog F-27414-*. Read the section on valve part numbers. Select the valve body needed. Refer to Catalog F-27382-*. Read through the actuator selection for MA, MC, MF, MK, MM, Mp, and MS to identify the desired actuator. Refer to TAC Catalog F-27414-*. find the page with the chosen actuator valve combination. Verify from the close off table that the actuator will meet the valve performance requirements. Turn to the actuator assembly code table and select the assembly code needed to complete the valve assembly number. ie: Vx-XXXX-XXX-X-XX. Order valve. If valve is not available as a factory assembly, order the individual parts and field assemble. The valve close off table provides the correct linkage kit required to couple the actuator and valve body, not all actuators require linkage kits.

Issue How does the nciSetpts snvt integrate to Niagara R2 for a Viconics Thermostat Model # VT7200C1018E (programID = 80:0:c5:55:0:4:4:1b) Environment Niagara R2 Viconics Thermostat (Model# VT7200C1018E) Cause Information will help configure the Niagara R2 for a Viconics Thermostat. Resolution The correct shadow object is T7XFCr. Use the SnvtTempSetptCmd object to link with the nciSetpts snvt. Note that if a setpoint is changed at the thermostat's local display, it will be used as the controlling setpoint regardless of the value provided by the nciSetpts snvt.

Issue When using Workplace Tech 5.x, after clicking on a help button assigned to various objects, the following pop-up message appears:  “Cannot find the WPTech5.hlp file. Do you want to try to find this file yourself?” Environment WorkPlace Tech 5.x Cause The file in question was removed, but not all shortcuts were updated to point to the new document. Resolution The link should have pointed to the “WPT 5.7 Engineering Guide Supplement .pdf”, which is located in the WorkPlace Tech\Help folder. “.hlp” files, referred to as “Windows Help” files, are not supported in Vista, and are problematic in XP. That is why it was replaced with the functionality of Adobe documentation. As a temporary solution, create a desktop shortcut to the .pdf file for quick access.

Issue Is a Niagara R2 driver still available for integrating a System 6000 Apogee from Siemens? If so, what is the part number? Environment Niagara R2 driver System 6000 Apogee Cause Need to order the driver to integrate a System 6000 Apogee from Siemens. Resolution Yes, the driver is available. Call Customer Support Services and order part number TRD-DRV-S600.

Issue There is an adapter which allows for connection between the USB port of a laptop or computer to Micronet via a MicroNet 2000 MN-Sx sensor. Environment MicroNet 2000 software (MN-CI, MN Flow Balance) MicroNet 2000 controller with attached sensor (MN-S, MN-SO, MN-SDK) Cause Computer without a serial port Resolution This connection requires the use of both part numbers MN-CIM (MicroNet Controller Interface Module) and UC232A (USB to Serial Adapter). The UC232A adapter can be attained from B&B Electronics. (NOTE: MN-CIM is obsolete as of December, 2011. See Product Announcement PA-000164. There is no functional replacement available) Steps: Load the UC232A driver Select unused Com port in setup (can not conflict with any other ports being used) Reboot computer

Issue A Vista alarm set up to display a value (such as the temperature being monitored to trigger the alarm) is coming through with question marks where the value should be. Product Line TAC Vista Environment Vista Workstation Alarm queue Cause By default Vista should read the .PV when no other attribute is defined, but sometimes it does not. Resolution Add ".PV" to the end of the text string to display the value.