Building Automation Knowledge Base

Issue Where can you obtain the Database Schema for the EBO WebReports / Report Server Database Product Line EcoStruxure Building Operation Environment Building Operation Report Server Cause From EBO version 3.2.x WebReports/RS is no longer being developed as we move to External Log Storage with Postgres and Timescale DB.    To allow our customers to continue to work with existing WebReports/RS databases if they so wish, it may be helpful to provide the DB Schema. Resolution An inbuilt Report already exists within WebReports call 'Database Schema' which allows you to select which Tables you would like to see in the WebReports / RS Database Running this will produce a .pdf Report detailing the RS Database Schema tables, to aid with 3rd Party integrations and other DB manipulation. A full database schema report is attached for reference (Version 3.2.3) 

Issue There is a problem after upgrading the SystemDB to N4.10. Product Line TAC IA Series Environment I/A Jace 8000 N4.10 I/A Enterprise Server N4.10 Cause In Niagara 4.10, we upgraded SystemDB from Orient v2 to v3, and as a result of that change, any customers that are utilizing SystemDB on their Supervisor stations will need to re-index accordingly upon upgrading to 4.10. Resolution In Niagara 4.10, the SystemDB has been upgraded from Orient v2 to v3.  Because of this change, customers that are utilizing SystemDB on their Supervisor stations will need to re-index upon upgrade to 4.10.  Please note, re-indexing can take a considerable time upon upgrade, and the DB will not have accurate information when queried until the index upgrade is complete. After upgrading to 4.10, invoke the actions that force system indexing.  Be aware that re-indexing can take some time, and that the DB won’t have accurate information when queried until the index is complete. The following image shows how to invoke execute on the Local System Indexer: If the Station has a DB configured to contain information about points on other stations, the Niagara Network System Indexer should be used, rather than the Local System Indexer.  Additional details regarding indexer actions can be found in the Niagara System Database and System Indexing Guide.

Issue What should be considered when prepairing for upgrading to Niagara 4.10? What known issues should I be aware of when upgrading to Niagara 4.10 and how can I prepair for them? Product Line TAC IA Series Environment I/A Series N4 Enterprise Server I/A Series N4 Jace 8000 Cause Define potential issues with an N4.10 upgrade Resolution The following details a set of upgrade considerations and known issues and their workarounds regarding Niagara 4.10. Please review prior to upgrading to Niagara 4.10. Niagara 4.10 and Default NRE Memory Changes: The increased size of some core libraries in Niagara 4.10 required changes to the default NRE Memory Pool settings for use on a JACE-8000. MetaSpace memory needed to be increased to allow applications to run without issue.   Note: any previous custom memory configuration applied to the JACE-8000 will be reset upon upgrade to 4.10. Prior to upgrading your JACE-8000, please review Default NRE Memory Pool Configuration Changes In 4.10.     Niagara 4.10 System DB Upgrade: In Niagara 4.10, we upgraded SystemDB from Orient v2 to v3, and as a result of that change, any customers that are utilizing SystemDB on their Supervisor stations will need to re-index accordingly upon upgrading to 4.10.   Please note, re-indexing can take a considerable time upon upgrade, and the DB will not have accurate information when queried until the index is complete accordingly. Prior to upgrading your Supervisor, please review System DB Must Be Re-indexed for Upgrades to Niagara 4.10+ from Earlier Niagara.     Niagara 4.10 and Third-Party Modules Keeping your Niagara installations safe and secure is our highest priority. In Niagara 4.10, ALL third-party modules must be signed with either a trusted valid certificate or a self-signed certificate to successfully run on a station. This new policy greatly increases the security posture of Niagara installations by making administrators aware of any modules that may have been tampered with, compromised or derived from untrustworthy sources.   Niagara's new signature enforcement feature is being rolled out over multiple Niagara releases. The first iteration was built into release 4.8 to give developers adequate time to make the transition to always signing any third-party modules.   Niagara 4.8 produced console and Security Dashboard warnings about unsigned modules but allowed them to run on a station. As of Niagara 4.10, unsigned modules will not execute.   For more information, please review the Niagara documentation on Third Party Module Signing   Niagara 4.10 Updated Operating Systems, Browsers, and Databases For the latest information on supported operating systems, please refer to Supported OS and other software in the Niagara 4 Framework Installation Guide.   Tridium remains focused on keeping pace with advancing IT infrastructure to enable more efficient, long-term support of each release version. This policy enhances the security posture of a Niagara installation by ensuring that only the most robust, secure operating systems and enterprise applications are compatible with the framework. The list below provides information on what we will be supporting with Niagara 4.10.   OS, Browser, Database Version Red Hat Enterprise Linux 8.1 (64 bit), 7.7 Windows Server 2019 (64 bit), Server 2016 (64 bit), Windows 10 (64 bit) VMWare ESXi 6.7 Oracle Database 19.3, 18.3, ... 12.2/12.1 MySQL Database 8 MS SQL Database 2019, 2017, 2016 Browsers Chrome, FireFox, Microsoft Edge Mobile Browsers Safari (iOS 12, 13), Chrome (Android 8, 9, 10)   As with all software products, we must also deprecate support for some operating systems and enterprise applications.  Nevertheless, you can be confident that the above list will handle your needs moving forward.   Using Web Launcher with Niagara 4.10 Web Launcher 20.4.2 was recently revamped for Niagara 4.10 to include essential software dependencies updates along with critical defect fixes. This version of Web Launcher has Java version 8 update 275 and certificate management has been updated to work with Niagara 4.10 along with any legacy or prospective release.   Prior to using Web Launcher with Niagara 4.10, the customer should update Web Launcher accordingly (see steps below). Updating WebLauncher Web Launcher has a feature to check for updates over the internet and prompts the user when a new version is available in the cloud. However, the existing version of Web Launcher has a bug that prevents a smooth update. Users will be required to perform a fresh install by downloading the latest version from the cloud via the station web Login page.   Click on the Niagara Web Launcher Installer link on the station's Web Launcher Web Page, which can be reached via the link on the Login page itself. Once the download is successful, click on the msi file and follow the installation wizard. You do not have to uninstall the older version. The new installation will automatically update to the latest version.

Issue Blank window while capturing a photo using "Logitech HD Pro Webcam C920". Product Line EcoStruxure Security Expert Environment Security Expert Cause While capturing a user photo using "Logitech HD Pro Webcam C920", it shows up as an image source (in the drop-down along with Topaz). When selected however, the screen is blank. Resolution With this webcam, you need LWS software by Logitech installed on your machine. G Hub has replaced LWS however it seems like G Hub is not currently functional with the integration. Find more information about the  "LWS280" driver HERE.  The driver can be downloaded from the attachment.

Issue Is it possible to integrate Schlage products with Security Expert? Product Line Security Expert Environment Security Expert Server (vv4.2.259.19 and above) SP-C controller Firmware (v2.08.923 and above) Cause Unable to migrate or convert a legacy access control system which has Schlage devices integrated to Security Expert Resolution With Security Expert Software (v4.2.259.19 and above) and SP-C firmware (v2.08.923 and above), the integration of Schlage devices (AD300 and AD400) with Security Expert software is supported.  It is always recommended to use the latest Security Expert Version and SP-C firmware version to avoid any known issues. For more information regarding the, Schlage Integration with Security Expert, download the attachment.  Refer to Security Expert Allegion Smart Reader Integration 

Issue Set up a MR-VAV-AX (ASC) as Standalone Product Line TAC INET Environment MR-VAV-AX Cause Air balance must be done to calibrate the airflow sensor on the MR-VAV-AX. Resolution Download Tech Tip 072   Equipment: Air Balancing Hood or Manometer and Digital Thermometer.   Assumptions: The MR is powered up. An I/STAT, or an M/STAT is plugged into the service port of a S/STAT or W/STAT, which is plugged into the MR-VAV-AX. The AHU is running. The Space sensor is installed. The Duct static pressure is constant. The dip switches are set properly for the desired VAV configuration. (See TCON 147) You have a Pocket Reference Card (TCON 149). You are familiar with the use and operation of the I/STAT / M/STAT with respect to navigating the Service mode to various mnemonics’ menus. (See TCON 147)   Initial Setup You should notice that two things have already happened: The MR is in the unoccupied mode. The setpoint adjust has defaulted to "-5", making the setpoint display appear low. For the MR to work in a Standalone mode the use of an off-board time clock for the occupied and unoccupied times is recommended. It should be connected to the "Local Occ" point(TB5 input #2 to TB5 ground.) The "Occ" mnemonic under Unit Parameters must be set to ONE for the "Local Occ" point to be used. If the MRs are to be left in the occupied mode indefinitely, install a jumper across the "Local Occ" point instead of using the time clock contacts. Connect the jumper to (TB5 input #2 to TB5 ground.) Using the I/STAT or M/STAT go to Set Temp and increase the value by 5°. This will get the Setpoint Adj. back to zero.   "Cooling Low Flow" (CLF - min. CFM) and "Cooling High Flow" (CHF - max. CFM) Setup Put the I/STAT or M/STAT into the Service Mode. Go to "AP", select "CLF", (the value displayed is "multiplied by" 1000 so 0.24 is 240). Enter the minimum CFM by using the arrow keys to position the LED for the digit to be changed and enter the value by using the "+" and "-" keys. Notice the decimal position will not move. You are entering the value "multiplied by" 1000. Refer to the Pocket Reference Card (TCON 149), paragraph 5. Usually the minimum air flow value can be found on the Mechanical box schedule drawings. The lowest reading that the ASC’s sensor can sense is about .03" to .05" of Water Column(W.C.) Therefore, the "CLF" must be set above this level. If the ASC is required to control in that range, it will tend to oscillate. Select "CHF" and enter the maximum CFM for this box at 1" W.C., this can be found on the DeltaP to CFM graph that is associated with this VAV box’s pickup device, or the box schedule may also provide the maximum cfm value.   Central Plant Heat "Heating Low Flow" (HLF) and "Heating High Flow" (HHF) Setup Use only if Central Plant Heat is required and setup Unit Parameter’s(UP) CPH set to "1". An open contact at Input 3 will indicate that the Central Plant Heat mode is on. A closed contact indicates CPH is off. Using the procedure described above for "CLF" and "CHF" instead select "HLF" and "HHF" and enter the desired Low and High Flow CFM values for the Heating Mode. Otherwise go to the next section. NOTE: If you have a auxiliary stage of heat, it will not be energized unless the CFM input is reading at least 80% of the "HLF" setting.   Calibrate the flow pickup: Go to Unit Parameter "UP", select "dd" (duct diameter). Enter the duct diameter this will enable the MR to calculate the Pickup Factor "PF" for us. NOTE: It is recommended that you begin with the value provided by the VAV Manufacturer for the pickup factor. Then calibrate if necessary using the following procedure. Go to "AP", select "PPF" (pickup factor calibration). The MR will drive the box open and modulate the damper to maintain the "CHF" level. This may take 5 - 10 minutes. NOTE: The stroke time is defined using the Damper Stroke (ds) parameter. The ASC provides several means of synchronizing the point with the physical damper position. 1. When this point is controlled to a value of 0, the decrease pulse will be on for 125% of the damper stroke. 2. When this point is controlled to a value of 100, the increase pulse will be on for 125% of the damper stroke. 3. When the damper stroke duration is modified, the decrease pulse will be on for 125% of the damper stroke. 4. When the power is cycled on the ASC, the decrease pulse will be on for 125% of the damper stroke. 5. Any time the ASC is the target of an Update_ASC or a Copy_Parms, the decrease pulse will be on for 125% of the damper stroke. After the reading has settled out, take a reading with a Hood or Manometer, which has been setup, and measure the actual CFM and enter that value now into the I/STAT-M/STAT using the Select and change buttons. The software has entered a unique Pick-up Factor "PF" in the MR for this box.   Calibrate space temperature (if necessary): To calibrate the Space Sensor while in the Service Mode, go to "oP" Operational Parameters. Select "CSS" (calibrate space sensor). Measure the actual temperature with a digital thermometer and enter the value. If your box has no heat or has a fan with electric heat. You’re finished. Go to the next box.   Hot water coil: If you have a hot water valve on your box and the stroke time is not 600 seconds: Go to "UP" (Unit Parameters) and select "Ho", Heating Output. Select1 for 1-OutPWM, 2 for 2 Out-PWM(Floating), or 3 for Duty Cycle 1 output. Go to "UP" Unit Parameters and select "HS" (heating stroke) and enter the actual stroke time in seconds.   Air Balance: If you require closely calibrated CFM readings proceed with the following steps: Go to "AP" (Airflow Parameters) Select "CPL" (calibrate low flow) and the damper will begin to close. Remember, the damper motor may take 3 minutes to get to the Cooling Low Flow setpoint. With a Hood, measure the total air flow and enter the measured CFM value. Select "CPH" (calibrate high flow). The damper will drive open to the Cooling High Flow setpoint. (remember the damper motor has a 185 sec stroke). When the reading stabilizes, take your measured CFM reading and enter it now. This procedure will de-calibrate the CFM input from the 0-1"readings to compensate for box, pickup, or hood irregularities/errors. Caution: When the decision is made to connect the MR-VAV-AX to a MRI or MCI please note the following: Avoid updating the MCI or ASC after initial setup as this will delete any MCI resident calculations, ATS, etc. that you may have added off-line that are residing at the same point addresses that the MR-VAV-AX is using. There are a variety of box types and a variety of other things that can be change if your application requires it. (Refer to TCON147)

Issue Set up the sensor and controller for use with a Dale Thermistor sensor Thermistor is reading incorrectly on controller Thermistors supported on which controllers. Product Line TAC INET Environment I/NET Cause Requirements installing thermistors on I/NET Controllers including conversion coefficients and point configurations. Resolution Requirements installing thermistors on I/NET Controllers including conversion coefficients and point configurations. See Tech Tip G069.

Issue On a 7718 controller, why do none of the discrete outputs provide 24vdc when energized? Product Line TAC INET Environment I/NET site Cause Using the 7718 controller, why do none of the discrete outputs provide 24vdc when energized Resolution Verify that fuse F9 is not open. (TCON106)

Issue When having issues with a specific NCI (SCPT or UCPT) in a XIF file it can be hard to understand the FILE definition in the XIF file in order to troubleshoot a given issue For information regarding NCI's that are not part of a FILE definition, refer to Understanding the NVVAL part of a XIF file Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment LonWorks XIF Cause The FILE definition can be somewhat cryptic - here is an example   FILE template 0 2 "1.1;" "2,23.24.25.26.27.28.29.30.31.32.33.34.35.36.37.41.42.43.45.46,0\x80,49,2;" "1,1,0\x80,60,12;" "1,1,0\x80,52,2;" "2,0.2.3.5.6.7.8.9.10.16.17.18.19.20.21,0\x80,48,2;" "1,0,0\x80,17,31;" "1,1,0\x80,34,2;" "1,1,0\x80,23,2;" "1,1,0\xA4,169,1;" "1,1,4\x80,3,8;" "1,1,4\x80,5,17;" "1,1,3\x80,1,2;" "1,1,4\x80,4,9;" "1,1,4\xA4,13,1;" "1,1,4\xA4,14,1;" "1,1,4\xA4,15,1;" "1,1,4\xA4,16,1;" "1,1,4\xA4,17,1;" "1,1,4\x80,18,1;" "1,1,0\x80,42,2;" "1,1,0\x80,36,2;" "1,1,0\x80,193,2;" "1,1,4\x80,8,2;" "1,0,3\x80,2,2;" "1,0,0\x84,165,1;" "1,0,0\xA4,166,1;" "1,1,6\xA4,2,8;" FILE value 1 1 116 0x0B, 0xB8, 0x09, 0x1D, 0x09, 0xFB, 0x0B, 0x80, 0x08, 0x77, 0x07, 0x98, 0x06, 0x13, 0x00, 0x02, 0x23, 0x28, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x78, 0x7F, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x80, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0xFF, 0x7F, 0xFF, 0x7F, 0xFF, 0x13, 0x88, 0x00, 0x00, 0x02, 0x0B, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 Resolution The FILE section describes the configuration variables (or SCPT's and UCPT's) for a device. Here is an explanation of the various parts of the FILE section.

Issue Access Initiated Control with Anti-passback (APB) /Anti-tailgate Product Line TAC INET Environment I/NET Cause Application Assistance Resolution Please see the following link: Access Initiated Control & APB/Anti-Tailgate.doc

Issue TAC Xenta 527 - Embedded Web Server Product Line TAC INET, TAC Vista Environment I/NET Seven or Vista site Cause Need information concerning the TAC Xenta 527 - Embedded Web Server Resolution Information Technology Brief: The TAC Xenta® 527 is a web based presentation system for TAC Vista LONWORKS and I/NET Seven® networks. In addition, to supplementing the host workstation interface with web access, the TAC Xenta 527 can also be used as the sole operator interface into I/NET Seven and TAC Vista LONWORKS systems. A single Xenta 527 will handle small to midsized systems, and several devices can be used to handle larger networks. The web pages are based on standard Internet technology as HTML and Java™ Applets. Alarms can be forwarded as e-mail. Please use the following link: Xenta 527-23 June.doc

Issue PIN Pad functionality and I/NET Seven Product Line TAC INET Environment I/NET Keypad, Key Pad, Pinpad, Door Code  Cause Setting up Pin Pad in I/NET Resolution Please use the following link: PinPadSetup.doc

Issue I/NET Cold Case "Card Reader" Mystery. Product Line TAC INET Environment I/NET site with Access Control Cause There are some basic differences between the Indala/Motorola and HID/Dorado card readers. Resolution Please look at the attached link point for this information. Mystery of the card readers.doc

Issue Memory requirements for converting access control to large numbers (Hex) Product Line TAC INET Environment I/NET Cause When using HEX card numbers the SLI will reserve memory for all required cards. Resolution The attached link will explain the memory requirements for the SLI using the Large (Hex) Number scheme. SLI Storage Capacity.doc

Issue Can TAC BACnet (Viconics) thermostats have identical names or device ids within sub networks using their default names? Product Line Andover Continuum, EcoStruxure Building Operation Environment Viconic BACnet Thermostats BACnet BCX B4 MSTP Cause Viconic stats need a unique address and unique name across the entire BACnet network. Resolution BACnet Viconics thermostats must have a unique name and device id across the entire BACnet network. The BACnet data link layer has two key parameters: the device object name and the device object ID. The device object name must be unique from any other BACnet device object name on the BACnet network (i.e. not just the MS/TP sub-network). Typically this question comes up because a thermostat will not come online. Run an acctrace during the Find and you will probably see a duplicate MAC address. Once you have given unique names and comm addresses to each of the thermostats on the entire BACnet network, these devices should communicate and come online properly. Each of the Viconic stats are given a unique name that includes the address (once it has been made unique) To change the communication address: Hold down the menu button until the option for menu comes up Answer the questions for the various options and eventually you will be brought to change comm address. Change Comm address, select Yes and then use the up or down arrows to give this MSTP Viconic stat a unique address. There is a Configuration Tool to access and edit the name and device id unique naming scheme. Click here for ViconicsConfigurationTool.zip. Installing and using the Viconics Configuration Tool on a Windows Laptop  You will need a serial adapter connection to tie into the MSTP bus that the thermostat(s) are connected to Select the Viconics folder > ViconicsConfigurationTool.zip You can install this ZIP file in any directory you wish, but the bacdocm.ini file must be installed on your C:\Windows directory. Use the bacdocm.ini file to configure your network settings at the Configurator Tool level. You can set the MAC address of your tool, the baud rate of your connection (max 38400 - limited by the RS-232 to RS485 port and Windows) etc. The "Our Device Instance" value represents the MAC address of the tool which must be unique on the MSTP network. Also the "MaxMaster" value must be set to a higher value than the highest MAC value on the MSTP network. You can edit this INI file to modify your settings OR you can modify the settings by going though the BACdoor Configuration Tool. Once you launch the Configuration Tool, you'll notice a white applet appearing at the right bottom of your screen. That is the BACdoor MSTP sniffer that actually looks for devices and objects. If you click on that icon, and select the "Configure" tab, a configuration window will be displayed. Select the baud rate at which you want to communicate with your device. This BACdoor configuration does the same thing as changing the BACDOCM.ini file (if properly located in C\Windows). Launch the Configurator Tool application. It automatically looks for devices on that network (at the baud rate set in the bacdocm.ini file or in the BACdoor Configuration window). If no device is detected an error message will pop-up after 1-2 minutes. All discovered devices will show up in the "Device List" you have to "Connect to device" in order to list all the objects of that device. After you changed the Baud Rate, you have to click on the "Apply changes" button. Don't forget that the max speed of this tool is 38400. For the first connection, you need to power cycle the thermostat (if it was running at 76800 previously) so that it auto-detects the 38.4 network. Once you set it to 76.8, you can not connect to that thermostat with the tool because of that 38.4 limitation. Also this tool does not support Read Multiple Property so it reads every property of every object one at a time. In its default mode of operation, the device will automatically match its baud rate to the baud rate of the network. Automatic baud rate detection will occur when the MS/TP communication port is initialized (on power up). If the network speed is changed, the device will keep listening at the previously detected speed for 10 minutes before resuming auto-bauding. Re-powering the devices will force right away auto-bauding. SE7xxx series requires the tool. The SE8xxx series does not as access is available through the menu on the device.

Issue Is there a way to get damper position out of a MNL VAV controller? Product Line TAC IA Series Environment WorkPlace Tech Tool Cause The hardware does not provide for direct damper feedback position. Resolution Click on the link below for objects can be added to an existing application to provide a calculated damper position. V2-23012-PosInd for Visio2002.zip

Issue Sigma graphic only updates when first opened and no regular updates occur there after or only some graphic data values update. Product Line Satchwell Sigma Environment Sigma Controllers Cause A Sigma graphic update is controlled by the tolerance setting on the Sigma object and defines when the new value is transmitted from the controller to the server.  If the update does not occur, then the Tolerance value could be set to high. Resolution Reduce the tolerance value via the Sigma object editor. Download the object to the controller. Restart the graphic. Note:  Reducing the tolerance too far can lead to graphic updates dominating communications resources in the controller. For example; A temperature object can be set to 0.05 to give an update for every 0.1 degrees. A change of state programmable object should be set to 0.5 as it will returned true/false statement (equivalent to 1/0). A pressure sensor measuring Pascal’s (100's) may need the tolerance setting higher (e.g. 10) as pressure can change rapidly at higher values.  For globally changing the tolerance values for the Sigma objects, download the Sigma Tolerance Utility

Issue TS-8XXX and TS-9XXX 1,1000 Ohm Balco sensor, Fahrenheit resistance table. Product Line Field Devices Environment Field devices Balco temperature sensors Cause Reference for integration and calibration Resolution Download spreadsheet file of chart below.     Temp (°F) Resistance (Ohms) Temp (°F) Resistance (Ohms) Temp (°F) Resistance (Ohms) -50 760.816 50 956.9 150 1185.2 -49 762.6 51 959 151 1187.7 -48 764.4 52 961.2 152 1190.1 -47 766.2 53 963.3 153 1192.6 -46 768 54 965.4 154 1195 -45 769.9 55 967.6 155 1197.5 -44 771.7 56 969.7 156 1199.9 -43 773.5 57 971.8 157 1202.4 -42 775.3 58 974 158 1204.9 -41 777.1 59 976.1 159 1207.3 -40 779 60 978.3 160 1209.8 -39 780.8 61 980.5 161 1212.3 -38 782.6 62 982.6 162 1214.8 -37 784.5 63 984.8 163 1217.3 -36 786.3 64 986.9 164 1219.7 -35 788.2 65 989.1 165 1222.2 -34 790 66 991.3 166 1224.7 -33 791.9 67 993.5 167 1227.2 -32 793.7 68 995.6 168 1229.7 -31 795.6 69 997.8 169 1232.2 -30 797.5 70 1000 170 1234.7 -29 799.3 71 1002.2 171 1237.3 -28 801.2 72 1004.4 172 1239.8 -27 803.1 73 1006.6 173 1242.3 -26 804.9 74 1008.8 174 1244.8 -25 806.8 75 1011 175 1247.3 -24 808.7 76 1013.2 176 1249.8 -23 810.6 77 1015.4 177 1252.4 -22 812.5 78 1017.6 178 1254.9 -21 814.4 79 1019.8 179 1257.4 -20 816.3 80 1022 180 1260 -19 818.2 81 1024.2 181 1262.5 -18 820.1 82 1026.5 182 1265.1 -17 822 83 1028.7 183 1267.6 -16 823.9 84 1030.9 184 1270.2 -15 825.8 85 1033.2 185 1272.7 -14 827.7 86 1035.4 186 1275.3 -13 829.6 87 1037.6 187 1277.8 -12 831.5 88 1039.9 188 1280.4 -11 833.5 89 1042.1 189 1283 -10 835.4 90 1044.4 190 1285.6 -9 837.3 91 1046.6 191 1288.1 -8 839.3 92 1048.9 192 1290.7 -7 841.2 93 1051.1 193 1293.3 -6 843.1 94 1053.4 194 1295.9 -5 845.1 95 1055.7 195 1298.5 -4 847 96 1057.9 196 1301 -3 849 97 1060.2 197 1303.6 -2 850.9 98 1062.5 198 1306.2 -1 852.9 99 1064.8 199 1308.8 0 854.8 100 1067 200 1311.4 1 856.8 101 1069.3 201 1314 2 858.8 102 1071.6 202 1316.7 3 860.7 103 1073.9 203 1319.3 4 862.7 104 1076.2 204 1321.9 5 864.7 105 1078.5 205 1324.5 6 866.7 106 1080.8 206 1327.1 7 868.6 107 1083.1 207 1329.8 8 870.6 108 1085.4 208 1332.4 9 872.6 109 1087.7 209 1335 10 874.6 110 1090 210 1337.7 11 876.6 111 1092.3 211 1340.3 12 878.6 112 1094.7 212 1342.9 13 880.6 113 1097 213 1345.6 14 882.6 114 1099.3 214 1348.2 15 884.6 115 1101.6 215 1350.9 16 886.6 116 1104 216 1353.5 17 888.6 117 1106.3 217 1356.2 18 890.7 118 1108.7 218 1358.9 19 892.7 119 1111 219 1361.5 20 894.7 120 1113.3 220 1364.2 21 896.7 121 1115.7 221 1366.9 22 898.8 122 1118 222 1369.5 23 900.8 123 1120.4 223 1372.2 24 902.8 124 1122.8 224 1374.9 25 904.9 125 1125.1 225 1377.6 26 906.9 126 1127.5 226 1380.3 27 909 127 1129.9 227 1382.9 28 911 128 1132.2 228 1385.6 29 913.1 129 1134.6 229 1388.3 30 915.1 130 1137 230 1391 31 917.2 131 1139.4 231 1393.7 32 919.2 132 1141.7 232 1396.4 33 921.3 133 1144.1 233 1399.2 34 923.4 134 1146.5 234 1401.9 35 925.4 135 1148.9 235 1404.6 36 927.5 136 1151.3 236 1407.3 37 929.6 137 1153.7 237 1410 38 931.7 138 1156.1 238 1412.8 39 933.8 139 1158.5 239 1415.5 40 935.9 140 1160.9 240 1418.2 41 937.9 141 1163.4 241 1421 42 940 142 1165.8 242 1423.7 43 942.1 143 1168.2 243 1426.4 44 944.2 144 1170.6 244 1429.2 45 946.3 145 1173 245 1431.9 46 948.5 146 1175.5 246 1434.7 47 950.6 147 1177.9 247 1437.4 48 952.7 148 1180.3 248 1440.2 49 954.8 149 1182.8 249 1443         250 1445.7

Issue Step-by-step instructions for calibrating airflow on a Xenta 102-AX (or I/NET MR-VAV-AX) using the M/STAT. Test and air balance procedure for balancing airflow Product Line EcoStruxure Building Operation, TAC INET, TAC Vista Environment Xenta 102-AX MR-VAV-AX M/STAT Cause The preferred method for calibrating airflow in Xenta 102-AX or MR-VAV-AX is through the plug-in.  However, this is not always an option, especially when the responsibility for calibrating is given to a third party test and balance company.  Pocket references exist for navigating through the M/STAT menu, but there aren't clear step-by-step instructions to tell exactly how to perform the calibration. Resolution Click here to download this document in Microsoft Word format Connect M/STAT Plug the M/STAT into the jack on the thermostat. The initial display shows the set temperature.   Enter Password Press the Service button. This prompts you to enter the service mode password. Default password is 183. Use the +/- keys to set each digit and the enter key to submit. If the password is incorrect, the display will blink. Airflow Parameters If the password is correct, the first menu option – Unit Parameters (UP) – is displayed. Hit the select button down twice until Airflow Parameters (AP) is displayed. Press enter. Cooling Low Flow Setpoint The first option is Cooling Low Flow Setpoint (CLF). Press enter to view the setpoint (divided by 1000). Record this value. Press the service key to escape out of the menu. Cooling High Flow Setpoint Navigate to Cooling High Flow Setpoint (CHF). Press enter to view the value (divided by 1000). Record this value. Press the service key to escape out of the menu. Reset Factory Calibration Navigate to Factory Calibration Settings (FCS) and press enter. Use the change keys to display “YES” and press the enter key. This will set the box back to default settings. This is a good idea to do prior to every calibration. Press the service key to escape out of the menu. Calibrate Low Airflow Navigate to Calibrate Low Airflow (CPL). Press enter and the current airflow is displayed. Wait for the airflow to reach the CLF and level out. Once the value is steady at setpoint, press the enter key only once. The display does not change. Enter Actual Low Airflow Measure the actual airflow. Use the change keys to set the display value to the measured value. Press the enter key. Choose One or Two-Point Now Calibrate High Airflow (CPH) is displayed. If one-point (offset only) calibration is desired, press the service key to escape out of this mode and calibration is complete. If two-point (gain and offset) calibration is desired, press enter to continue to the next step. Calibrate High Airflow The current airflow is displayed again. Wait for it to rise to meet the CHF and level out. Once the value is steady at setpoint, press the enter key only once. The display does not change. Enter Actual High Airflow Measure the actual airflow. Use the change keys to set the display value to the measured value. Press the enter key. CPH is displayed again, this time as a general menu item. Escape Service Mode Press the service key to escape out of the menu. If you are finished configuring the box, escape all the way back out of the service menu before disconnecting the M/STAT. Disconnecting in configuration mode can leave the stat displaying “00” or other incorrect numbers.

Issue In the event of a lost or broken connection between the Vista Server and SQL server, the Vista Server will begin to queue up its events and log values in the $queues\insertevents and $queues\insertlogvalues directories. Once your connection has been re-established those queued files will then be written to the Vista DB, however this process can take an extremely long time,  and possibly cause the Vista server to hang at start up and even crash.  Product Line TAC Vista Environment Vista 4.3.0 or higher with SQL  Cause Broken SQL connection between Vista and local or remote SQL server. Resolution If you are not in the need to this queued event and log data you can manually delete all of these queued files. Opening this directory with Windows, highlighting all files and deleting them usually does not work, because of the enormous amount of files that may be stored in their respective directories. The best way to delete these files is to use DOS. Remember stopping both TAC Vista Server and the DSS Writer service before deleting the files.   Method 1: The proper steps to delete these files with DOS using the "rmdir" command are: Click Start > Run Type "cmd" and press enter Use the DOS command "cd.." followed by enter to navigate up one folder in the hierarchy.  Repeat this command until the prompt is at the root directory and shows C:\> Use the DOS command "cd " to navigate to the Vista database folder location and the $queues folders.  For example: C:\>cd Projects C:\Projects>cd School C:\Projects\School>cd VistaDB C:\Projects\School\VistaDB>cd $queues Type "rmdir /S /Q insertevents" - all files and folders including the "insertevents" folder will be deleted Use the cd.. and cd commands to navigate up one folder and back down into the insertlogvalues folder C:\Projects\School\VistaDB\$queues\insertlogvalues> Repeat step 5.   Method 2: The proper steps to delete these files with DOS using the "del" command are: Click Start > Run Type "cmd" and press enter Use the DOS command "cd.." followed by enter to navigate up one folder in the hierarchy.  Repeat this command until the prompt is at the root directory and shows C:\> Use the DOS command "cd " to navigate to the Vista database folder location and the $queues folders.  For example: C:\>cd Projects C:\Projects>cd School C:\Projects\School>cd VistaDB C:\Projects\School\VistaDB>cd $queues C:\Projects\School\VistaDB\$queues>cd insertevents C:\Projects\School\VistaDB\$queues\insertevents> Type "del *.*" and then "Y" to confirm that all files on that directory will be deleted. C:\Projects\School\VistaDB\$queues\insertevents>del *.* C:\Projects\School\VistaDB\$queues\insertevents\*.*, Are you sure (Y/N)? y Use the cd.. and cd commands to navigate up one folder and back down into the insertlogvalues folder C:\Projects\School\VistaDB\$queues\insertlogvalues> Repeat step 5. Now both of these directories should be emptied and if your SQL connection issue has been rectified your events and logs will write as normal to SQL.     Alternatively, this utility will split the queued files into folders of 4,000 files each.  Windows can handle each of these folders and make the task of deleting the queued files more manageable.  Click the screen capture below to download the utility.