Building Automation Knowledge Base

Issue Some TGML javascript functions that work correctly in Vista Workstation stop working in Vista Webstation or break graphic performance. The following errors have occurred. Please correct these errors and/or contact the system administrator. An unexpected exception has occurred: Object reference not set to an instance of an object. System.NullReferenceException at TAC.WebStation.Modules.Graphics.TgmlLinkPage.CreateLinkData(TACOSTgmlPicture tgmlPicture, String oID) at TAC.WebStation.Modules.Graphics.TgmlLinkPage.GetLinkList(TACOSTgmlPicture tgmlPicture, String[] oIDs) at TAC.WebStation.Modules.Graphics.TgmlLinkPage.Page_Load(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) Product Line TAC Vista Environment Vista Webstation 5.x.x Graphic Editor TGML 1.x.x Cause Due to the differences in Vista Workstation and Vista Webstation being viewed through internet browsers some TGML javascript functions will not function, function as expected, or cause your TGML graphic page to be unusable resulting in a Java error message. Resolution To make TGML graphic pages compatible with Vista Webstation remove the following functions: getDate getYear getMonth getDay getHour getMinute getSecond To make TGML graphic pages compatible with Vista Webstation adjust the unexpected behavior of the following functions: setTimer - this function cannot be used in the OnDocumentLoad event getStatus - this function will always return a value of 2 invoke - this function can only be used on links, not bindings.

Issue Want to create a database to show / sort a list of the I/NET system configuration. Environment I/NET Seven 2.2x and above Cause Need to display a summary or generate a report showing each level of the I/NET configuration, Host, Link LAN and subLAN. Resolution You can display the I/NET System Configuration as follows:  From the I/NET Menu, select  Summary, Configuration. Select the level you wish to report / display Host; Link; Station; UC;  MR; DPU As you select each of these buttons I/NET will interrogate the network and display the necessary hardware at each of these levels. After selecting the level you want to report on, click on the Report Button The System Report selection box is then shown: Select the available options: All Devices or Select device Output Type – Comma Separated Values or Text Output destination The dialog box also displays the current level, by default this will always be Host If the Auto launch option is activate, the report file will automatically open. Otherwise, you can navigate to the Output destination folder and open the file manually As the report is being generated, a temporary status window will appear showing what devices are being queried. At any time while this window is visible you can click its Cancel button to stop the reporting process. When the report is complete, this status window will automatically close.

Issue When you browse a Lonmaker object, the temperatures display the incorrect units. Environment Lonmaker Windows XP Cause The regional settings on the computer are incorrectly set for the systems specific region and therefore show the incorrect units for temperature. Resolution The Regional Settings of your PC need to be correctly configure for your Region. The steps to correct this are: Navigate to Control Panel Open Regional and Language Options Under the Regional Option tab ensure the correct region is selected Select the Advanced tab and ensure that the correct Non unicode region is selected. Reboot the computer after these changes have been made. If you have updated the Vista database with these object you will need to delete them from the TAC Network in the System Plug-in. Then update the Vista Database without the effected controllers. Once the database has been updated to remove these effected controllers you can let the plug-in update the TAC network. After  the TAC Network update a Vista database update can be done. This will transfer the XIF files and set them to the correct units. Check the database for any links on these updated items and correct lost object paths. 

Issue Get the following error message when preview is used in the TGML editor when the graphic have a script in it: TAC Graphics Editor - Unexpected Error A problem occurred in this application Method note found: 'Void org.mozilla.javascript.Context.__ ()'. Environment TGML editor 1.1.5 - 1.1.6 Vista 5.1.5 - 5.1.6 Cause Some DLL files from Vista 5.1.4 have not uninstalled correctly and are left in the folder C:\Program Files\Schneider Electric\GraphicsEditor. Resolution Uninstall the latest version of Vista. Install Vista 5.1.4 Reinstall the latest version of Vista.

Issue Installed the I/A Series(Niagara) R2 software on a new Windows computer but cannot get it to connect to an existing UNC that has the same release of the I/A Series R2 software.  One possible error, "Java.io.EOF Exception", that might be displayed is shown below: Another possible error message is an HTTP 401 error. This issue may also prevent the I/A Series R2 tunnel client from connecting to UNC. Environment Computer with any supported version of Windows software including the usual assortment of utility and security / anti-virus software. I/A Series (Niagara) R2 software (any version) installed on the computer. Cause The Windows Firewall and/or Anti-Virus/Internet Security software has been installed and configured such that it is blocking Ethernet communications into or out of the computer on certain Ethernet ports. According to the I/A Series Networking & Connectivity Guide, provided with the I/A Series (Niagara) R2 software, specific user definable Ethernet ports, must be open for two-way communications between the WorkPlace Pro software and a UNC.  If communications is blocked on these ports, the WorkPlace Pro software will not be able to communicate across the Ethernet network. Similar issues are caused by the firewall built into many of the Internet Security software packages.  The following programs have been known to cause port blocking issues: Trend Micro Internet Security - Workstation Edition Trend Micro Office Scan - Workstation Edition Symantec Internet Security Suite version 9 Avast 7 (Free) Antivirus with 30 day demo of Avast Internet Security Bitdefender Antivirus Software Kaspersky PURE 3.0Total Security Kaspersky Endpoint for Business Resolution Verify that the Windows Firewall has been configured to pass bidirectional Ethernet communications over the two required Ethernet ports (default ports are 80 and 3011 - for both the TCP and UDP protocols).  Refer to the online Windows Help for configuration information.  Note that  computers that are members of a Windows Domain may have firewall configuration restrictions enforced by domain policies.  In these situations, it will be necessary to contact the Domain Administrator or facility PC-Help Desk for assistance. Verify that any installed Internet Security software does not block the required Ethernet communications ports.  Some specific Internet Security software packages are known to permanently block the use of some Ethernet ports, for specific uses.  Any Internet Security software of this type must be totally removed from the computer before the required communications can be established.  Three known software packages of this type are the "Symantec Internet Security Suite, version 9", "Bitdefender Antivirus Software" and "Trend Micro Internet Security software".

Issue Problems upgrading/installing SQL server. The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine XXXXXXX Error:2147749896 (0x80041008). "Not clustered or the cluster is up and online” check fails. Note: In the screen shot above the clustering check was passed. Environment TAC Vista 5.X.X SQL Server 2000/2005/2008 all versions; upgrades and new installations. Cause The WMI (Windows Management Instrumentation) Control is a tool that enables you to configure WMI settings. Inadequate access permission will mean that the user is unable to access the WMI service. Resolution If one of these messages appears or other problems are encountered during installation or upgrading of an SQL server, follow the steps below: 1. Check the WMI settings Go to My Computer – either in the start-menu or go directly to the desktop icon if running windows in classic mode – and right-click on it. Select Manage. In the hierarchical tree in the pane to the left, expand Services and Applications. Locate WMI Control and right-click on it. Select Properties from the context-menu. If the message “Failed to initialize all required WMI classes” is displayed (see screenshot below) read on… 2. Change/check the DCOM settings Open the start-menu, click on Run and type “dcomcnfg”. The Component Services console should open. Expand Component Services and then expand the Computers folder. Select and right-click on My Computer. Select Properties. In the dialogue window that opens up select the COM Security tab. Under Launch and Activation Permissions select Edit Default. Check under Groups or user names to see if the group Everyone has been added. If not select Add, type in "everyone" and then click on Check names. Once the name is confirmed, click on OK. Ensure that the permissions Local Launch, Local Activation and Remote Activation are allowed for the group Everyone. Repeat the above steps for Launch and Activation Permissions but select Edit Limits.   Click on OK again to close the My Computer Properties window and then close Component Services.     3. Recheck the WMI Settings       Go back to the Computer Management console described earlier and locate WMI control under Services and Applications. Right-click on it and select properties. If all the steps have been followed the message should read "Successfully connected to local computer." After this it should be possible to upgrade/install SQL server.

Issue EPI Builder will not run even though the security key is enabled for badging Get error Badge Manager Cannot init license after clicking on Create/Edit Badge in Personnel Manager BadgeManager Cannot init license Environment Continuum EPI Builder Windows XP Keywords: account, admin, administrator, user, account, dongle, permission Cause The logged in user account does not have enough permission to run EPI Builder Administrator account runs EPI Builder OK Resolution Give the required user account enough permission to run EPI Builder Eg. Windows "Users" account may not have enough permission to run EPI Builder, where Windows "Power Users" normally have enough permission to run EPI Builder

Issue Problems installing Webstation 5.1.4 on PCs running Internet Information Services (IIS) 7 or higher. The installation appears to be OK but just before it finishes it "rolls back" to the beginning and webapps is not installed. Installation problems - Webstation 5.1.4 on Windows 2008 server Installation problems - Webstation 5.1.4 on Windows 7 Vista 5.1.4 webapps software crashing during install Environment Windows 2008 server Windows 7 (not officially supported) Vista webapps (webstation) Cause This issue is caused due to compatibility issues with IIS 7. Vista 5.1.5 is compatible with IIS 7. Vista 5.1.4. is not compatible with IIS 7. Resolution In order to install TAC Vista Webstation successfully on Windows Server 2008 it has to be done in the following order: Note : Make sure all installation is done as an administrator (Right click the file/application and select "Run as administrator")! 1. Install IIS 7 with IIS 6 Management Compatibility Start the Server Manager (Right-click on Computer in the start-menu or the Computer desktop icon if running classic start-menu and select Manage). Right-click Roles and click Add roles. In the dialogue that opens up click Next and then select Web Server (IIS). In the dialogue that follows click Add Required Features. Click Next (twice). On the select Role services page select ASP.net. In the dialogue window that appears click Add Required Role Services. Click on "Add roles" and then "next" in the dialogue window that opens. Scroll down to "IIS 6 Management Compatibility", check the box and follow the rest of the installation wizard. 2. Install TAC Vista Server 3. As administrator, Run the ASP.NET IIS Registration Tool (Aspnet_regiis.exe) for ASP.NET version 2.0 Run the command prompt as administrator and type in the following: %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i 4. Install TAC Vista Webstation 5. As administrator, Migrate the ASP.NET application configuration to IIS7 Run the command prompt as administrator and type in the following: %SystemRoot%\System32\inetsrv\appcmd migrate config "Default Web Site/" 6. Change the Application Pool in IIS7 Go to the Webstation/ScreenMate settings in IIS. Select "Advanced settings" under "Manage Application". Change Application Pool" from "DefaultAppPool" to "Classic .NET AppPool". 7. Change the application pool identity Locate the Application Pools in IIS Locate the "Classic .NET AppPool" application Pool Right-click on it and select "Advanced settings". Locate the Identity attribute and set it to "Local System".

Issue The status of a TAC Xenta 301 or 302 does not go 'online' in TAC Vista, although the Neuron Status property of the controller is 'online' and 'Commission and Download' from TAC Vista is apparently successful. Values read "Failed to Read Signal" in a values page of a classic network. Values read "Invalid Address" in a values page of an LNS network (also see [Invalid Address]) Controllers without /N/P (networking and presentation) designation cannot communicate in a Network. Product Line TAC Vista Environment Vista Workstation Vista Server Xenta 301 Cause Attempt to commission a standalone (non-/N/P) TAC Xenta 301 or TAC Xenta 302 in a TAC Vista Classic LON network.  Non-/N/P controllers are designed to run stand-alone and be configured/interact only with a Xenta OP. Resolution Check the sticker on the side of the controller where the controller type, hardware version, and neuron ID are found. Example of a 302/N/P label. Example of a non-/N/P 302 label.    If the sticker does not have /N/P following the controller type, this is not a network presentation controller.  It will never communicate on a network Replace the non-/N/P controller with an /N/P enabled version.

Issue  To convert a 0 - 20 mA signal into an acceptable form to be used into a variety of controller types. Environment Sigma BAS Micronet X96 controllers X32 controllers IAC controllers Micronet controllers Cause Some controllers will not accept a 0 - 20 mA signals and therefore the signal must be converted. Resolution To achieve this conversion, please follow the instructions below. Install a 500 ohm 0.1% resistor in series with the 0 - 20mA signal. From across the resistor, take the signal to the controller . The Universal Input or Analogue Input should be set as a standard voltage input.

Issue An easy way to monitor K and V digital output states of a Xenta 121 in LonMaker for troubleshooting purposes. Environment Xenta 121 Vista Lonmaker Cause Uncertain of the output state on a Xenta 121. There are SNVT outputs to represent different functions of the Xenta 121, but they do not always represent the final RAW DO Status. Resolution Monitoring the SNVT nvoRawDOStatus to tell what state the output is in. nvoRawDOStatus is displayed as a 16 bit binary value. Each output will be represented by a bit. Bit 0 is the least significant/leftmost bit, and bit 15 is the most significant/rightmost bit. K1-K4 are displayed 1 for closed relay, 0 for open relay, Bit 0=K1 Bit 1=K2 Bit 2=K3 Bit 3=K4 V1-V4 are displayed 1 for on, 0 for off. Bit 4=V1 Bit 5=V2 Bit 6=V3 Bit 7=V4 X1-X3 are displayed 1 for shorted to ground. 0 for open. Bit 8=X1 Bit 9=X2 Bit 10=X3 U1 value is 0 not configured as digital input, 1 configured for digital input. Bit 11=U1 In Lonmaker right click on the Xenta 121 device Select Browse Navigate to nvoRawDOStatus Select Ctrl+M to monitor the nvo

Issue When navigating in TGML pictures, some are opened, a few then the picture "hangs" and I get thrown out from Webstation and have to log in again. Get logged out form webstation after opening a couple of TGML graphics   Environment TAC Vista 5.1.x TAC Webapps 5.1.x (Webstation) Windows 2003 Server Cause If the site admin has set the  properties on the application pools to restrict the memory a process can use this restriction will be applied to the SE.ASP.NET v4.0 Classic application Pool that webapps are using. These restriction have to be taken or set to a higher value. Resolution Open IIS Manager Expand Application Pools and right click on SE.ASP.NET v4.0 Classic Select properties Uncheck Maximum virtual memory and maximum used memory (or type in higher values) Click ok and restart the website.

Issue Upgrading Loytec L-IP to the latest firmware or checking current firmware version. Environment Loytec L-IP Vista Network Interface Cause UL 864 v.9 for Smoke Control requires at least version 5.04 firmware in all system L-IP's. Resolution Verifying L-IP Firmware Version via Console Connection To use the serial interface, the DB9 console connector of the L-IP can be connected to the RS-232 port of a PC. The L-IP-3ECTB and L-IP-33ECTB use a standard null-modem-cable must be used to connect the L-IP’s DB9console connector to the RS-232 port of the PC. The PC will communicate with the L-IP using a HyperTerminal program with the communication settings set to 38,400 bps / 8 data bits / no parity / 1 stop bit / no handshake. The L-IP displays the console menu shown in Figure 1 upon a successful HyperTerminal connection initiated by a “enter” keystroke or power cycle of the L-IP: LOYTEC electronics GmbH www.loytec.com L-IP Configuration Menu ======================= [1] Show device information [2] Serial firmware upgrade [3] System configuration [4] EIA-709 configuration [5] IP configuration [6] EIA-852 device configuration [7] EIA-852 server configuration [8] Reset configuration (factory defaults) [9] Device statistics [0] Reset device Please choose: Figure 1: L-IP main menu. Select Option 1 to Show device information  This menu item shows information about the L-IP and the current firmware version. The output should look like what is shown in Figure 2. Product information =================== Product code: L-IP-3ECT Firmware: L-IP Primary image Version: 5.0.5 Build date: Fri Mar 18 10:41:29 2005 Serial number: 002304-80000000E73C Free memory: 557K,57K System temp: 33.3C Supply volt: 12.0V Unique Node IDs =============== Port 1: 80 00 00 00 E7 3C EIA852: 80 00 00 00 F7 92 Figure 2: Device information. (For UL 864 v9: If the Firmware Version does not reflect a Version 5.0.4 or Version 5.0.5, you must update the firmware to an approved version in the next steps. If the L-IP contains an approved version, further action is not required.) L-IP Firmware Upgrade To download the firmware via the console connected the L-IP to the RS-232 port of a PC via its console interface as outlined above. Download the lswitch_lipxxx.zip located at www.loytec.com to the PC. Install the LOYTEC serial upgrade tool (LSU Tool) by double clicking LSU_2_0_1setup.exe. Double click on the lswitch_lip_xxx.dlc file. This will start the LSU Tool and load the firmware image referenced in the . lswitch_lip_xxx.dlc file. The start window of the LSU tool is shown in Figure 3. *note that the lswitch_lip_xxx.dlc file and the lswitch_lip_xxx.dl file must be stored in the same folder. Figure 3: LSU Serial Upgrade Tool in idle mode. If the L-IP is not connected to COM1 you can change the port to COM1, 2, 3, or 4. Press “Download” to start the download. A progress bar as shown in Figure 4 can be seen. Figure 4: Progress bar during firmware download. If the upgrade is successful the following window appears (Figure 5). Figure 5: Successful firmware upgrade. Exit the LSU Tool. Reconnect through HyperTerminal connection and  initiate the console by a “enter” keystroke or power cycle of the L-IP. At the console main menu, select option [1] Show device information, and press Enter. This will bring up the current device information as shown in Figure 2, for verification that the firmware version has updated successfully.

Issue When trying to open TAC Webstation the following error message appears: Webstation error," Could not load file or assembly 'IKVM.AWT.WinForms' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded." Environment Vista 5.1.5, Windows 2008 server 64 bit Windows 2003 server Cause Wrong Application pool is used for Webstation in the IIS, a ASP.Net version 2 is used instead of a .Net version 4. Webstation 5.1.5 is developed in ASP.Net 4. Resolution  In the IIS, under Websites\Default Web Site\Webstation - right click and select Properties and then the ASP.NET tab, change the Application pool from the DefaultAppool(ASP.NET version 2) to SE ASP .NET v4.0 classic (ASP.NET version 2) Application pool. 

Issue How to redirect from default website to webstation. Want users to get to webstation even if they only type in the server name Environment TAC Vista 5.1.5 Windows 2008 IIS7 Cause It is easier for customers to just type in the server name and not have to remember the /webstation Resolution  Open IIS manager Click on Default Website Double click on HTTP redirect     4.Type in the URL to Webstation (default http://localhost/webstation) 5. Click on apply under actions.

Issue Vista Workstation Errors: 'No such entity' , sometimes accompanied with  'Could not parse blueprint' and 'Failed to parse application' error messages in alarm pane. Error occurred: Failed to retrieve property from database. The property page will be disabled. No such entity Environment Vista Workstation Menta OP tree Cause There is a mismatch between the .mta in the Xenta and the .mta in the Vista database. Vista asks for a value that does not exist in the device and errors. Unused constants in the Menta file Error in the OP tree Transfer of the .mta to the controller upon download was invalid or failed. Memory is low or has been totally consumed in the Xenta programmable controller. PVR blocks that have invalid values, eg. 2,0E-16 or similar. This can happen sometimes if you save in simulation mode in Menta Resolution Most common: If all of the signals are showing "No Such Entity", this is a sign that the controller does not contain a Menta file. Though you may think it should, it does not. The following are reasons why the controller did not download or is applicationless. Applicationless controllers require a "direct connect" and download to the controller. Errors in OP NOTE: if you've customized the OP menu, changes will be lost In Menta editor, Tools>OP Configuration, Tree>test. Test to see if there are errors in the OP tree. Tree>Build and select "Yes" to replace the current tree. Tree >Generate. Tree>Test. This will verify your errors have been fixed. Save the OP file. In simulation mode select Command>Generate, File>Save to Vista database or save the Menta file to your hard drive with the intention of manually browsing in the .mta to the device. Incorrect .mta in the Vista Database Browse in a newly saved .mta, Download the controller. Application Too Large Downloading through Vista may appear to be successful though an error exists. Using a serial connection is the most reliable way to reveal memory errors. Use one or more of the following to free up memory in a Xenta which is "Out of Memory". Checked the free memory in Menta via Options>Memory Usage and make sure that the Application is not too big Reduce application size by limiting the amount of "public" values and "descriptions" by un-checking public in the Menta block properties and deleting the description. Delete unnecessary not connected outputs (TANVO's) Delete the OP Menu if it is not needed. Alternatively, build the OP Tree instead of Auto Generating one for a smaller file. Time schedules/charts consume significant amount of memory. Check all TSCH blocks and delete any unnecessary Week/Alt charts. Replace the Xenta controller with a larger capacity controller (from a X280 to X300 or from X300 to X400) Re-write your program to use all Menta blocks more efficiently. Split the task among controllers but keep in mind limitations with TAC network variables and network traffic. Invalid Values In Menta, go to simulation mode Go to Preferences uncheck view diagram Now you get all the signals in a list that you can easily scroll through and find any value that are to small or large Change the value to the real value Hit F5 and F12 and save in edit more.   If only some of the signals are showing "No Such Entity" there is a mismatch of what signal values are trying to be retrieved from the controller, and the signals that are actually present in the controller. This is known as Unused Constants. Unused Constants In Menta, go to Options>Constants Tables and choose "Delete Unused" to remove all orphan variables Download to the controller.

Issue TAC Vista Webstation licenses are not released after the Webstation browser is closed. When log into Webstation again, get error message: The following errors have occurred. Please correct these errors and/or contact the system administrator. X No license available Product Line TAC Vista Environment TAC Vista Webstation Cause Closing the Webstation browser does not log out the user. Logged in user needs to use the “Log Out” button (as shown in the picture below) or wait till the Webstation times out in order to log out. The default time out period is twenty minutes. Setting can be changed in Webstation settings. Resolution If need to change the time out period setting, please follow the steps below: Go to “Start/All Programs/Schneider Electric/Web Applications X.X.X/Vista Web Settings” (by default). NOTE: for TAC Vista 5.1.3 and prior, go to “Start/All Programs/TAC/Web Applications X.X.X/ Vista Web Settings” instead.   Select “Preferences/Login and Logout/Automatic Logout”. In the right panel, click on the down arrow to expand the drop down list and choose the desired the logout time period.  

Issue When Vista Server starts another window opens up with the title of TAC Central IPCL Interpreter. This window will not close while Vista Server is running. Environment Vista Server 4.xx, 5.x.x Cause TAC Central IPCL Interpreter is a tool used for programming and communication management for legacy System 7 controllers that predate Vista 3.3. In the absence of System 7 hardware the TAC Central IPCL Interpreter was started and configured to run automatically by mistake with the Vista Server interface. Resolution Disable the Automatic Start of the CIPCL Interpreter. Start Vista Server Select File->Log In. Log in to the Vista Server. Select Configure->CIPCL ->Auto Start. Restart Vista Server to confirm the program does not launch again.

Issue Which values in the 102-AX plug-in affect the ultimate airflow reading output on nvoBoxFlow? Formula for converting velocity pressure to flow. Setting air balance parameters -- airflow coefficient, velocity pressure gain, offset, and cutoff, duct area, pickup factor and box constant. Environment Xenta 102-AX Cause Incorrectly configured boxes can cause erroneous airflow readings or unexpected behavior during calibration. Resolution The Xenta 102-AX uses a differential pressure sensor to convert velocity pressure values from 0-1" water column to a 0.25-4.0 volt output. The voltage signal is converted to a 10-bit digital value. The digital value is filtered and passed through the calibration gain and offset adjustments. Any value below the lowest velocity pressure threshold will be treated as 0"wc. Airflow_Sense.UCPTairFlowCoeff Airflow Parameters > Airflow Setting > Airflow Filter Coefficients (%) This value ranges between 0 to 99% where 0 is no filter and 99% is the maximum amount of filter. All process controls using the airflow reading use the filtered value. The default filter is 80%. The filter equation is defined as follows: display value = [previous display value * filter] + [new data value * (1 - filter)]   Airflow_Sense.SCPTgain Airflow Parameters > Airflow Setting > Velocity Pressure Gain (multiplier/divisor) This value is multiplied with the raw velocity pressure reading to provide calibration gain to the final signal. The default gain is 10/10 (1). Resetting the box to factory calibration settings prior to calibrating the box will ensure that no invalid values are adversely affecting the operation.   Airflow_Sense.UCPToffsetPress Airflow Parameters > Airflow Setting > Velocity Pressure Offset (WC) This value is added to the raw velocity pressure reading to provide calibration offset to the final signal. The default offset is 0. Resetting the box to factory calibration settings prior to calibrating the box will ensure that no invalid values are adversely affecting the operation.   Airflow_Sense.UCPTpressCutOff Airflow Parameters > Airflow Setting > Lowest Velocity Pressure (WC) At the low end of the measurable velocity pressure, the sensor is inherently unreliable. The lowest velocity pressure threshold will zero out any value too low to reliably be measured. The default value is 0.016"wc. If airflow is reading 0 CFM despite the velocity pressure being above 0"wc, it may be that the threshold is set too high. The calibrated velocity pressure value is used in the following calculation for airflow: Airflow = Square Root(Velocity Pressure) * Duct Area * Pickup Factor -or- Airflow = Square Root(Velocity Pressure) * Box Constant The operator has the ability to enter the duct area and the pickup factor as separate values, or enter the box constant of the VAV terminal unit. The box constant is the duct area multiplied by the pickup factor. If the duct area or pickup factor is entered last, they will be used in the calculation. If the box constant is entered last, it will be used in the calculation. The pickup factor and box constant are sometimes referenced as the K-Factor(FPM) and K-Factor(CFM) respectively. This information must be taken from the VAV box itself and is usually displayed in a format such as the one shown below. Airflow_Sense.SCPTductArea Unit Parameters > Box Settings > Duct Area (sq feet) The cross sectional area of the duct in square feet. Most ductwork diameters are measured in inches. For round ducts, the equation for area is: Area = π * [(d/2)/12] 2 where d = diameter or Area = π * (r 2 / 144) where r = radius An 8" diameter duct would have a cross sectional area of 0.349 sq feet.   Airflow_Sense.UCPTpickupFactor Unit Parameters > Box Settings > Pickup Factor (Imperial Units) This coefficient is provided by the VAV manufacturer and represents the feet per minute flow speed of the air at 1"wc of pressure. Typical values in HVAC VAV applications are between 2200 and 3300. Default value is 2950.   Airflow_Sense.UCPTboxConstant Unit Parameters > Box Settings > Box Constants (Imperial Units) The box constant is the area multiplied by the airflow pickup factor. Airflow is determined by multiplying the square root of the velocity pressure by the box constant. The final value is reported out the following SNVT: VAV_Controller.nvoBoxFlow Status > VAV Status > Airflow (CFM) This is the final airflow value in CFM as measured by the Xenta 102-AX. After calibrating the velocity pressure probe, the displayed value should match the flow values measured by a highly accurate magnahelic hood.

Issue Device Monitor has no devices appearing in its window. Environment Sigma 4.05 all releases Cause No devices are appearing in the Device Monitor window. Resolution Since Sigma 4.00 Device Monitor is now fully integrated into Sigma. If the utility Sigma Ping has been used it should now be un-installed. In Sigma go to System Setup > Network and Devices > highlight "your site" 1. Use right hand tab "Device Monitor" and using the drop down menu select Sigma server where the monitoring is to take place. 2. Select using the check boxes any devices to be omitted.