Building Automation Knowledge Base

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.  

Issue Questions regarding specifications of SmartStruxure Hardware Inputs and Outputs Product Line EcoStruxure Building Operation Environment SmartStruxure I/O Modules: AO-8, AO-8-H AO-V-8, AO-V-8-H DI-16 DO-FA-12, DO-FA-12-H DO-FC-8, DO-FC-8-H RTD-DI-16 UI-8-AO-4, UI-8-AO-4-H UI-8-AO-V-4, UI-8-AO-V-4-H UI-8-DO-FC-4, UI-8-DO-FC-4-H UI-16 Cause Different I/O modules have different electrical specifications Resolution Universal Input Specifications Universal inputs can be configured as voltage, current, thermistor, resistance, digital or supervised inputs. Voltage Input Specifications: Range - 0 to 10 VDC Resolution - 12 bit Accuracy - ±(0.7mV + 0.2% of reading) Current Input Specifications: Range - 0 to 20 mA Resolution - 12 bit Accuracy - ±(0.03 mA + 0.4% of reading) Resistance Input Specifications: 10 Ohm to 10 kOhm 10 kOhm to 60 kOhm Thermistor Input Specifications: Range - -50 to 150° C (-58 to 302° F) Thermistors: 10k Type I (Continuum), 10k Type II (I/NET), 10k Type III (Satchwell), 10k Type IV (FD), 1.8k (Xenta), 10k Linearized (Satchwell DRT), 10k Type V (FD w/ 11k shunt), 1k (Balco), 20k (Honeywell), 2.2k (Johnson Controls) Digital Output Specifications Form C Relay: Terminal - Common (C), Normally Open (NO), Normally Closed (NC) Minimum Pulse Width - 100 ms minimum Isolation - 1500 VAC minimum, coil to contact Cycle Life - At least 100,000 cycles Contact Rating - 250 VAC, 30 VDC, 3 A Form A Relay: Terminals - Common (C), Normally Open (NO) Minimum Pulse Width - 100 ms minimum Isolation - 1500 VAC minimum, coil to contact Cycle Life - At least 100,000 cycles Contact Rating - 250 VAC, 30 VDC, 2 A LED Specifications: LED Polarity - Represents the actual state of the output; ON if the output is active, OFF if the output is inactive LED Color - Green Analog Output Specifications Analog outputs can be configured as voltage or current. Module Voltage Output: Range - 0 to 10 VDC Resolution - 50 mV Accuracy - ±100 mV Terminals - Voltage (V), Return Minimum Load - Source, 2 mA; Sink, -1mA Current Output: Range - 0 to 20 mA Resolution - 0.1 mA Accuracy - ±0.2 mA Terminals - Current (I), Return Maximum Load - Output load should not exceed 650 Ohms Supervised Input Specifications Supervised inputs can be used to detect sabotage. Detected resistor values - Open circuit, short circuit, contact open, and contact closed. 5 volt circuit, 1 or 2 resistors, monitored - Series only, parallel only and series and switch combinations. For a 2-resistor configuration, each parallel. Resistor value range - 1k to 10 k resistors should have the same value. The selected resistor value needs to be defined in the system. RTD Input Specifications The specifications of the RTD-DI-16 are extensive and thus are best viewed directly in the data sheet available on the Buildings Download Center: RTD-DI-16 Specification Sheet You can also download the specification sheet here: IO Module RTD-DI-16 Specification Sheet (July 2014).pdf.

Issue Receive "Initialization error" when trying to start I/NET with SQL 2008 When we installing SQL Server 2008 Standard for I/NET Filemaster, what are the main components we should include? When editing / adding a new I/NET Configuration Profile the Database Server section is blank DBCreate does not start.  Appears in task Manager but no user interface is shown. Within DBCreate the restore option is grayed out Product Line TAC INET Environment I/NET Seven 2.4x Microsoft Windows Server 2003, Windows XP, Windows Vista, and Windows 7 families of operating systems. (both 32 and 64 bit) Microsoft SQL 2008 Standard or Express Editions Microsoft SQL 2008 R2 Standard or Express Editions Cause I/NET must have the SQL 2005 Backward compatibility file installed.  If this is not installed I/NET will not locate the SQL Server and hence will issue an “initialization failure” error.  This is can also be identified in either the DBCreate or I/NET Configuration application editors which will show no entries in their "Database Server" settings. The document also details information that is necessary for a Standard or Express editions of SQL 2008 / SQL 2008 R2. Resolution Follow the instructions below extracted from the document called "SQL2008 Expr Install Inst.pdf".  This document is found on I/NET Seven CD under the 'SQLExpress' folder.  For SQL 2008 R2 installations refer to the following document SQL2008 R2 Expr Install.pdf, also found in this same folder .  Installing SQL Server 2005 Backward Compatibility SQL Server 2005 backward compatibility must be installed for SQL 2008. To install SQL Server 2005 Backward Compatibility Navigate to the SQLBcm directory on the TAC I/NET Seven installation CD. Launch the SQLServer2005_BC.msi file. Follow the prompts on each screen and accept all defaults. After the install check the SQL Server Services SQL Server Browser is RUNNING SQL Server (MSSQLSERVER) is RUNNING Check the SQL Server Network Configuration Protocols Enable Named Pipes Enable TCP/IP Completing the Installation Proceed with the installation of TAC I/NET Seven on your PC. For installation instructions, refer to TCON298, TAC I/NET Seven Getting Started. Note: Run Inetcfg.exe before starting TAC I/NET Seven for the first time. This is necessary to attach TAC I/NET Seven to the database and avoid an “Initialization failure” error. Note: Before file equalization will operate, the system must be rebooted or the INETEQZMERGE service must be manually started.   Also refer to Installing I/NET 2.42 or higher and Vista 5.1.7 or higher on a 64-bit operating system for additional details on installing I/NET with SQL 2008 R2.

Issue Graphics not working in Webstation. Only the menu bar is shown. Some graphics might work. The graphics are working fine in the Workstation and in the editor. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation TGML Cause Some images (PNG, JPEG, BMP) can have wrong information in the image file. In some cases, this corrupted image information will block the graphic from being rendered in Webstation although it works fine in the editor and in Workstation. Resolution Make a copy of a graphic that is not working and delete all the images in the graphic. If the graphic can now be viewed in Webstation, delete the images one at a time viewing the graphic in Webstation after each save.  This will allow the location of the image(s) having the issue. Open the image in a graphics editor such as PaintBrush and save it with a new name. Import the new image and save the graphic. Check that the graphic can be viewed in Webstation Another option to easier find the file image having the issue, is to extract the images from a graphic that is not working in Webstation with the "TGML Image Extract" tool, and run all the images through an image checker, such as "Bad Peggy" or "Corrupt JPEG Checker"

Issue When creating a Modbus device template in XBuilder Device Editor which Modbus register data type should be used? Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 XBuilder Modbus Register Bitmask Cause Lack of consistency between Modbus slave manufacturers there is a large number of data formats that can be selected. Each register format interprets the value differently based on byte order or purpose of the specific bits. Resolution Consult Modbus slave product documentation Use trial and error to find the correct register format. Perform communication logging to capture the raw data and compare with a known value to determine the format. As a tool to assist with these steps please consult the Definition of Modbus Registers.

Issue How do you determine how large a database will grow when using Continuum? How do you know if a Stand Alone or LAN install should be used? Which version of Microsoft SQL Server is needed? Product Line Andover Continuum Environment Windows XP Windows Vista Windows Server 2003 Windows Server 2008 MSDE SQL Express SQL Server Standard SQL Server Enterprise Cause A database will grow based on the number of objects and logging requirements for a project. Estimating how much a database will grow over time based on the number of controllers, points and logging should be done to determine which Microsoft Database solution is needed for the site. Microsoft has placed database size limitations on the free versions of their database engines called MSDE and SQL Server Express. The size limitations are 2 and 4 gigabytes respectively. If this size limitation is exceeded, it can produce unwanted results including database corruption. If the estimated size of a database over time exceeds these limitations then a full Microsoft SQL version must be implemented. Resolution An Excel spreadsheet has been developed to help evaluate the size of a Continuum database, to determine if a Stand Alone or LAN is needed and which version of SQL should be used. The Continuum database estimating spreadsheet takes into consideration 6 main areas: Extended Logs- total amount of logs, intervals and the number of days to retain  Access Events- total amount of access events and the number of days to retain Alarm Events- total number of alarms and the number of days to retain Error Events- total number of Cyberstation errors and the number of days to retain Activity Events- total number of Activity events of all Continuum users and the number of days to retain Continuum Database objects- Total number of Netcontrollers, Infinet, BCXs , mstp controllers, total number of inputs, outputs and numerics. Any of the objects not mentioned above. Consider all objects not mentioned above The number of data logs, extended log intervals, number of days to retain data and other estimation information can be inserted into the spreadsheet. The sheet will calculate the information and do the following: Estimate the space required for that object type and the sum of all object types Indicate if a Stand Alone or LAN system is needed Indicate which version of SQL Server is needed Download the Continuum Database Size Estimation Tool.

Issue "Invalid attribute property" error when trying to create NetController II in Continuum v1.74 SP2 as Controller Type "9681". Environment Continuum v1.74 SP2 NetController II Cause Trying to create new NetController II device object with a "Controller Type" of "9681". "A Guide to Version 1.74 Support for NetController II and ACX 57xx" states that there is only one NetController model, the CX 9680. Please ignore references to the 9681. Resolution Create the Netcontroller II as  a Controller Type "9680" as stated on page 15 in document number 30-3001-1001 "A Guide to Version 1.74 Support for NetController II and ACX 57xx".

Issue Recommended USB to Serial RS-232 adapter Environment I/A Series R2 UNC’s, G3 ENC’s, MicroNet 2000 MN-CIM, and MicroSmart MSC-LIM. (NOTE: MN-CIM is obsolete as of December, 2011. See Product Announcement PA-000164. There is no functional replacement available) Cause PC or Laptop without RS-232 Serial Port (DB-9 male) connector. Resolution IOGEAR (p/n: GUC232A) has been validated to work in the following applications: 1. HyperTerminal  with a direct connection to the ENC/UNC’s serial port (COM1) using RS-232 adapter and Schneider Electric p/n: UNCC-405 (RJ-45 socket to DB-9 socket adapter, null modem) and CBL-RJ45-** (flat silver satin cable). 2. MN-CIM interface module for use with the TAC MicroNet 2000 series controller interface and Air Balance software. 3. MSC-LIM interface module for use with the DMS MicroSmart Controller Interface (equipment with a handheld port). Click here for product data sheet on the IOGEAR adapter

Issue Instructions and programming example for using nviEmergCmd to control the damper on the Xenta 102-AX Environment Xenta 102-AX Menta Cause In some situations it is necessary to have the Xenta 102-AX damper open to 100% for smoke control, or other sequence of operations specific tasks. There are different emergency modes which all perform a different function. Resolution The damper position on the 102-AX can be controlled to 100% or to 0% by using the SNVT input nviEmergCmd. Please see the attached Menta file as a programming example. The enumeration breakdown and controller actions of nviEmergCmd are as follows: 0 = Emerg Normal - Normal operation of the controller without any emergency command. 1 = EmergPressurize  - 102-AX will control to its max cooling CFM setpoint. 2 = EmergDepressurize - 102-AX will control its damper to 0% and shut off all other outputs. 3 = EmergPurge - 102-AX will control the damper to 100% 4 = EmergShutdown - 102-AX will pause control on the damper and disable all other outputs. 5 = EmergNull - Null SNVT value NOTE: Any value change on nviEmergCmd will initiate a damper resynchronization. This will cause the controller to fully close its damper, fully close any floating control outputs, and disable any other hardwired outputs for their full stroke time (throttling range).

Issue Communications with other Lon network devices are lost after the IC-Lon/IC3-Lon has cold-started. Product Line Satchwell Sigma Environment Sigma IC-Lon Integration controllers IC3-Lon Integration controllers Cause The controller has been cold-started either manually or through the automatic process. Resolution The final part of the engineering process of the IC-Lon/IC3-Lon, is for the file named NVConfig.bin to be uploaded from the IC-Lon/IC3-Lon to the Sigma server. If this file is not uploaded, then the IC-Lon/IC3-Lon reverts to its non-bound state. The NVConfig.bin file contains information about the Lon bindings and is modified during the binding process when using LonMaker. To upload the NVConfig.bin, carry out the following: Open "System Diagnostics"  on the Sigma server. Select the correct controller number. From the "Options" menu select "Upload Files" and NVConfig.bin This file will now be uploaded and overwrite the existing file in the controller folder, and therefore when the controller next cold-starts, the correct file will be downloaded to it. For more information on the Engineering process of an IC-Lon/IC3-Lon, please click here.   The Sigma system is now out of its support period, consideration should be given to transitioning or upgrading to SpaceLogic - EcoStruxure Building Operation.

Issue How can more than 50 globals be transmitted from a Sigma controller when I have a lot of digital objects states to pass between controllers? Environment Sigma Controller (all) Cause Sigma controllers are limited to 50 broadcast globals. Resolution Up to 16 Sigma Digital objects states can be reference in a single programmable object.  By performing a binary count the various states can be represented by a single analogue value which can then be broadcast as global data. Sigma programmable object MASK command can be used to decode analogue representation of a single analogue value that represents up to 16 digital states (on/off).   For example the value of 901 represents the state of a number of Sigma DI Objects where each bit indicates the on/off.  Hence, this translate to the 16-bit binary value  0000001110000101  where 1 = on and 0 = off To set-up bit masking click here for details. 1.  Create a program object in the transmitting controller that 'binary' counts up to 16 digital objects. 2. In the receiving controller create up to 16 programmable objects to decode the transmitted analogue value.  e.g

Issue The user logged into Windows doesn't have permissions to the folder that contains the Continuum.mnu file,  the file is set to read only or the path in the continuum.mnu is incorrect. Product Line Andover Continuum Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Permissions are restricted to the Continuum.mnu file or the path in it is incorrect. Resolution One of the follow solutions will resolve this: Click to download an edited default path Continuum.mnu and Menu.bmp  (links for the default path C:\Program Files (x86)\Continuum) Copy these files to each workstation that has an incorrect path Manually edit the file yourself if you have a path that is other than (C:\Program Files (x86)\Continuum) Grant permissions to the folder. The folder that contains the Continuum.mnu can be located by editing the Cyberstation in Continuum Explorer. WS Edit> Preferences tab> The file name of the main menu  Ex. c:\program files\continuum\userprofile\continuum.mnu Right click on Continuum.mnu and select properties. Deselect Read Only if it is selected. Change the path to the Continuum.mnu file to a folder that you have access to and copy the continuum.mnu to it. Ex. c:\program files\continuum\continuum.mnu While in edit mode, right click on each of the buttons and select Properties Use the browse button to select the correct x86 path (C:\Program Files (x86)\Continuum) Repeat this for each of the buttons and then save the Continuum.mnu file Copy these files to each workstation that has an incorrect path Also see Continuum.mnu file with C:\program files (x86) on 64 bit PCs points to C:\program Files and shows a blank screen.

Issue How to load up archived data in a report using Seven Reports Product Line TAC INET Environment I/NET Seven  SevenReports Archiving Cause Reports show nothing or have one blank page and fail to show data that meets the date window specified Resolution When using Seven Reports to view data, archived data can be viewed and put into a report.  From the Archives pull-down menu, Mount/Dismount the archive files. Files, by default, are stored in the c:\INET Seven Data\Arch folder. After mounting the needed reports (look at the date of the files in the archive folder), the report used must have the word ARCHIVE in the file name. This specifies that the reports will be pulled not from the current database but rather from the mounted files and on the dates specified. The reports should now be from the Archived files mounted. Archive Reports are located on the install CD under CD\Program Files\INET Seven\Reports To download, click on the link below and select to save the report to your hard disk in the c:\INET Seven Data\Reports folder:   I/NET Seven Release 2.20 and Prior files: ArchiveOverrideBillingSamples.rpt ArchiveRuntimeSamples.rpt ArchiveTransactionsDoors.rpt ArchiveTransactionsIndividuals.rpt ArchiveAnalogSamples.rpt ArchiveConsumptionSamples.rpt ArchiveDemandSamples.rpt ArchiveDiscreteSamples.rpt   I/NET Release 2.21 to current: ArchiveAnalogSamples_xi.rpt ArchiveConsumptionSamples_xi.rpt ArchiveDemandSamples_xi.rpt ArchiveDiscreteSamples_xi.rpt ArchiveOverrideBillingSamples_xi.rpt ArchiveRuntimeSamples_xi.rpt ArchiveTransactionsDoors_xi.rpt ArchiveTransactionsIndividuals_xi.rpt   Tip: In some instances, while the report is running and the data is being compiled, if you move the mouse or strike a key, the process starts all over. The solution is to start the report and wait for a few minutes if you have input a broad range of data to search and produce.

Issue As part of a site power feed problem investigation where varistors are being blown, how are they connected to the power feed? Environment i2920, b3920, b4920. Cause When a site is experiencing power problems and the mains input varistors blow, it is required to know how the damaged varistor is connected. Resolution The 3 varistors are connected between: Live and Earth, Neutral and Earth, Live and Neutral. The attached sketch shows how  the 3 varistors are connected. The connections are the same for the i2920 and b4920.

Issue When using the I/A Series R2 (Niagara) WorkPlace Pro to commission LON controllers under an existing LNC-100, configure the Local LON device to match the Domain Length, Domain ID, and Subnet ID programmed in the LNC. Product Line TAC IA Series Environment I/A Series R2 (Niagara) WorkPlace Pro I/A Series Network 8000 LNC-100 Cause When a third-party network management tool is used to define and commission a LON network, the commissioning tool frequently uses specified domain address instead of the default "zero-length" domain address.  When using the I/A Series (Niagara) R2 WorkPlace Pro to learn a previously commissioned network, Workplace Pro will not be able to discover the LON devices until it has been configured to match the domain address of the network. Resolution Click here to see this procedure including screen captures. If the LNC-100 is already communicating to existing controllers on the LON trunk, document the Domain0, Subnet0, and Node0 addressing in either the SYS:SIM or SYS:SIM2 blocks. You don't need to change the existing address in order to add new LON controllers. If you will be using Niagara to commission the new LON controllers, set up the LonWorks Service so that the Local LON device is on the same Domain and Subnet as the LNC-100. Set the Domain length and Domain ID; go to the Properties of the LonWorksService, Netmgmt tab, Engineering tab, domainId, length, domainId. For example, if the SYS:SIM block in the LNC-100 has "DOMAIN0=0D, SUBNET0=01,NODE0=120,..." then in the UNC, it should be domain length = 1 (byte), and domainId = 0D. Apply the changes. Set the Niagara subnetNodeId properties: subnetId = 01, nodeId = 127. The subnet matches SUBNET0 in the SYS:SIM block. Leave the Node ID set to 127 Apply the changes Recommission the Local Lon Device. (Remember to disconnect the LNC-100 from the trunk before commissioning!) With the new controllers connected to the LON trunk, go to the Lonworks service, Lon Device Manager, and run the “find” command; the new controllers should be added to the list of nodes. You can use the Lonworks Utilities, command = identify, SubCommand = service pin to be sure you have the correct node. Then commission the new nodes. Note: Should the LNC-100 be accidentally commissioned, refer to Network 8000 LNC-100 cannot communicate to LON devices under it but can be accessed with WorkPlace Tech or a LON commissioning tool.

Issue Satchwell D?T sensor temperature to resistance Environment Satchwell DOT DRT DDT DWT DST DOS Cause Find the resistance value of a D?T sensor at any temperature in Centigrade. Resolution Referred to Satchwell T type Sensor resistance chart. Click here.