Building Automation Knowledge Base

Issue Are the following SNVTs supported in Vista 5.1.6? SNVT_Amp_ac SNVT_Count_32 SNVT_Volt_ac Environment Xenta X5XX, X7XX, X9XX with firmware 5.1.6 Cause The SNVTs  SNVT_Amp_ac, SNVT_Count_32 and SNVT_Volt_ac are not included in the Xenta 5.1.6 firmware. They will be included in 5.1.7. There is however a workaround available in 5.1.6  Resolution Locate the SNVTtype.def file in the Xenta server. Connect to the Xenta server using an FTP client and locate the SNVTtype.def file under configdb/Lon/SNVTTYPE.def. Copy the file to your PC and make a backup copy Edit the file with a suitable text editor (notepad, notepad2 etc) -Locate the SNVT_amp definition -Add the following lines after SNVT_amp definition (see screenshot below): //---// amp_ac 139 2 1   INTEGER,,2,0,65535,1,0 //---// Repeat the process with the other 2 SNVTs - SNVT_count_32: Add the following lines after SNVT_count definition: //---// count_32 183 4 1 INTEGER,,7,-2147483648,2147483647,1,0,raw //---// - SNVT_volt_ac: Add the following lines after SNVT_volt definition: //---// volt_ac 138 2 1   INTEGER,,2,0,65535,1,0 //---// Replace the SNVTType.def file in the Xenta server using the FTP client.

Issue Airflow reading from Xenta 102-AX is jumping around and will not stabilize or is 0. Environment Vista Xenta 102-AX Plug-in LonMaker, NL-220 Cause For a variety reasons parameters may get changed in a Xenta 102-AX adversely affecting the controller's performance. Resolution Ensure that all of the parameters that affect the airflow reading are set properly. In some cases it may be best to restore the default parameters. Parameters that should be checked may be found through the Xenta 102-AX plug-in or through Vista but are grouped below how they are found in the plug-in starting with Unit Parameters: Unit Parameters Duct Area Ensure that the duct area is set properly for the box size. If a formula was used to determine the duct area from duct diameter verify that it yielded the correct result. For square or rectangular ducts use the following formula: For round ducts use the following formula: Pickup Factor The pickup factor is sometimes known as the K factor and is determined by examining the airflow curve diagram provided by the box manufacturer. It can often times be found on the box itself or in the manufacturer's literature. If the manufacturer's specs cannot be obtained use the default pickup factor, which is 2951.6. Box Constant The box constant is a product of the pickup factor and the duct area. It is sometimes available from the box manufacturer. If the manufacturer's data cannot be obtained use the default value, which is 1588.5. Note that the box constant will be changed from default if a CBC, or, calibrate box constant is performed. Airflow Parameters Velocity Pressure Gain The default settings here are 10 / 10 and are changed when a calibration is performed. If these numbers factor out to be very far from one you may want to reset them to their defaults and investigate if something went wrong with the calibration. For example these values may read 2957 / 3054 but since that factors out to 0.968 which is only about 3% off from one. However, if these numbers were 2957 / 6043 this would be a clear indicator that there was something wrong. Velocity Pressure Offset The default value here should be zero and considering that sensor is nominally set up for a 0-1" scale numbers greater than +0.1 or less than -0.1 should be cause to investigate further for mistakes during the calibration process.

Issue Is there a way to copy the setup parameters from one Xenta 102-AX VAV controller to another? Environment Xenta 102-AX NL220 Cause To assist in commissioning of many Xenta 102-AX controllers with similar configurations, parameters can be copied between controllers. Resolution Locate the controller you want to copy the parameters from. Right click on the controller and select "Copy configuration values to memory" Locate the controller you want to paste the parameters into. Right click on the controller and select "Paste configuration value(s) from memory" Then modify the parameters for that specific 102-AX as normal.

Issue Attempts to make changes to LonMaker drawing results in error message that write access is not available. Environment LonMaker 3.1 Cause When the drawing is opened write access was not granted. By default write access is enabled, but it can be turned off when multiple users are accessing the same drawing file. Resolution When opening the network ensure that the "Show all network options dialogs" checkbox is checked. When you reach the Username prompt screen ensure that the "Write Access" field is checked and then complete opening the drawing.

Issue When using a HyperLink in Vista WebStation graphic page the error message "This content cannot be display in a frame" is shown. Clicking the link to open this content in a new window will properly display the web page. Environment Vista WebStation 5.x.x Cause Newer web browsers support a HTTP header flag named X-Frame-Options which allows the remote web server to block display of its content within a web page frame. This is a security measure to stop "click jacking". Internet Explore 8, Internet Explorer 9 will display the error message Google Chrome will ignore the hyperlink. Resolution Instead of linking directly to the web page link to the folder that contains the Hyperlink object and then clicking on the hyperlink object will open the web page in a new window if the target property is empty or "_blank". Another alternative is simply click the "Open this content in a new window" link.

Issue The Xenta 104-A plug-in limits the temperature value input between 0°F and 18°F. It is not possible to input a negative value. Environment Xenta 104-A Plug-In Lonmaker 3.1 or Lonmaker 3.2 NL220 Cause The Xenta 104-A plug-in limits the temperature value input between 0°F and 18°F. It is not possible to input a negative value. Resolution In Vista follow these steps: Navigate to the Xenta 104-A controller. Browse down to the Node Object function block and find the nciSpaceTempOfst SCPT. Type in the designed space temp offset parameter from the default 32°F value. For example, if a -1°F offset is needed a value of 31 will need to be entered. If a +1°F offset is needed a 33 will need to be entered. 32°F represents zero offset.

Issue The Xenta 104-A plug-in limits the temperature value input between 32°F and 104°F. Environment Xenta 104-A Plug-In Lonmaker 3.1 or Lonmaker 3.2 NL220 Cause The Xenta 104-A plug-in limits the temperature value input between 32°F and 104°F. Resolution In Vista follow these steps: Navigate to the Xenta 104-A controller. Browse down to the 8030 function block and find the nciDischAirMax SCPT. Type in the designed high discharge air temp value.

Issue How to set a Xenta 102-AX back to factory default values.  Environment Xenta 102-AX Vista LonMaker NL220 Factory Default Cause Unwanted changes can be reset back to factory values. Resolution To reset a Xenta 102-AX back to factory defaults, recommission the device and select Source of CP Values to default.

Issue The engine is in the process of converting a database. Internal. NS#165 error occurs when the user is attempting to delete a portion of the LNS database. For example, the error will occur when doing group bindings because the first step in the automated group binding process is to delete the old bindings. The error will also occur when deleting a controller, snvt, bindings, etc, out of the LNS database. Environment Lonmaker 3.2 NL220 Cause All instances of this error have been reported after upgrading an LNS 3.1 system to 3.2, and the upgrade process somehow does not finish. This has been reproduced in NL220 as well. Resolution Send your LNS database to Echelon for analysis at support@echelon.com.

Issue Is it possible to invert an alarm that comes from a BACNET (or other) device via a Xenta 913? The signal is normally closed and the alarm is active when the signal = 0. Environment Tac Vista 5.1.X with alarms that come from devices under a Xenta 913 Cause Some devices have inverted (normally closed) alarm signal. Vista's default is that a signal is normally open. Resolution To invert the alarm signal go to the properties dialogue for the Change of State object and then the alarm tab. Change the Low limit to 0.5 and the high limit to -0.5.

Issue How to configure dynamic text in a Vista OGC Graphic. How do the set values affect the text and color? Environment Vista OGC Graphics OGC Editor Cause The order of the attribute values set in the OGC Dynamic Text editor will affect the operation on the live graphic page. Resolution Start by placing a generic text object on the page using the text tool from the toolbar.  Once the text has been placed on the page, double click it to open the Dynamic Text dialog. Browse to the Vista database value to monitor (ensuring that the Value attribute is selected). Enter the desired threshold values for each text string/color. Set the desired text and color for each value range. The values entered in the Value: dropdown list will act as a true hysteresis. In the above example with values 0, 10, 20, etc, if the value starts at zero, the text and formatting will remain constant until the value rises above 10. At that point, it will take on the text and style defined for 10. If the value drops back down to 9, it will remain unchanged. Only once it reaches the hysteresis value of 0 (or up to 20) will it change again. NOTE: Values defined in the Value: dropdown menu must be listed in sequential order or they will not perform as desired. For example, to add a value of -1 to the list, you would need to redefine all values 0-140 and > to come after the -1.

Issue How can a temperature input be calibrated in a Xenta programmable controller. Environment Menta 5.x.x Cause The sensor input block in Menta does not have any calibration features. Instead these must be done with the program by the use of a calibration value. Resolution Use a PVR block and add this value to the raw senor input value to result in a calibrated value. By making the addition block public and giving it a name it will be visible from a Vista front end. If necessary it can be output as a SNVT as well. In this situation it might be advised to leave the AI block SAT_Raw public flag unchecked to provide a less cluttered view to the end user. While the calibration PVR is left at zero you will see the raw value from the sensor.

Issue After installing Lonmaker 3.1 with Visio 2002 the file menu within Visio is not displayed properly. You don't have any contacts in %s that can be chosen as your default business card. Using %s, add a contact and try to select a business card again. Or, select another PIM application from.... Product Line TAC Vista Environment Lonmaker 3.1 Visio 2002 Dell Latitude E600 & E610 Windows XP Cause The cause is unknown, but this issue has been observed on multiple occasions with fresh installs on Lonmaker 3.1 with Visio 2002, on Dell Latitude E600's & E610s with Windows XP Update: It seems to be the Bluetooth on these computers that causes this behavior.    Resolution Uninstalling Lonmaker 3.1 and reinstalling has proven to fix this issue on multiple occasions. If the uninstall and reinstall does not fix the issue please contact Echelon for further product support at lonsupport@echelon.com. Update: Before uninstalling LonMaker, try to disable the Bluetooth in BIOS and uninstall the Bluetooth software.  

Issue nvoBoxFlow or nvoAirFlow drops down to zero or flutters back and forth from zero to the actual flow value when trying to maintain a low amount of airflow. Product Line TAC Vista Environment Vista Workstation Xenta 102-AX Xenta 102-AX Plug-in Cause The Xenta 102-AX application filters out any velocity pressure readings below a certain threshold in order to prevent nuisance readings that may adversely affect the operation of the controller. Resolution There is a parameter named UCPTpressCutOff that determines at what pressure level should readings be seen as valid and at below what pressure level should readings be rounded to zero. The default setting for this parameter is 0.016 inches of water column although this number is seen as 0.02 when viewed through Vista Workstation since it is truncated to 2 decimal places. Whenever the velocity pressure reading detected by the Xenta 102-AX drops below this level it will change it to zero instead. Fluctuations in pressure readings at about zero are often a result of this filter. Check to see if the nvoAirPressure reading is at about this point just before dropping out to zero. Also, check to see that all of the VAV parameters are set correctly including duct area, pickup factor, and box constant. While it is possible to lower the UCPTpressCutOff parameter there is no guarantee of the accuracy on any readings below the default setting.

Issue If there is an online selection tool for all the HVAC sensors (room temperature sensors, duct pressure sensors, etc.) Environment All Schneider Electric Buildings product lines Cause Since Schneider Electric manufactures a huge amount of sensors for different product lines. Sometimes it takes a bit of time to search for the right sensor. Therefore, Schneider Electric developed an online selection tool to help customer pick the right sensors. Resolution Click here to go direct to the online HVAC sensors selection tool. Select the desired features of the sensor. All sensors match the requirements will be displayed on the right. Datasheets can be accessed by clicking on the image or the part number. NOTE: the listed sensors may not be available in some region. Please contact the local sales or Support team to confirm the information.

Issue The 102-AX will not energize its digital outputs to control electric heat strips, but the controller does have a -100% terminal load. Environment Xenta 102-AX Cause The 102-AX is configured for 1-3 stages of electric heat without a fan, and the heat will not energize. This is because the controller is not seeing enough airflow to safely control the electric heat. Resolution Troubleshooting Electric Heat on a Xenta 102-AX The Xenta 102-AX controller supports up to two stages of auxiliary heat on two digital outputs. This document suggests troubleshooting techniques to help narrow down the cause of improper operation of these digital outputs. Start with the Universal Outputs On the Status tab of the 102-AX Plug-in, each of the universal outputs are listed under the “Network Bound Inputs” column. In the 102-AX Plug-in version 5.1.4, this column has been erroneously omitted. Download TAC Toolpack version 5.1.4 Hotfix 72 from the Buildings Business Extranet to resolve the issue. The outputs that represent the outputs are Universal Output #2 and #3. The first thing to do is attempt to override the output on. Note: verify that proper airflow is available to prevent overheating. Figure 1. Network Bound Inputs If the heating stages energize correctly, then the unit parameters and wiring are all correctly configured. Skip directly to the chapter entitled “Overriding the Output Successfully Energized the Heat.” If the heat did not successfully energize, proceed to the next chapter where three possible problems are addressed. Overriding the Output Failed to Energize the Heat There are three main reasons why overriding the output would fail to enable the output. Unit Parameters The Unit Parameters tab of the 102-AX Plug-in is where Universal Outputs #2 and #3 are configured as digital outputs. Verify they are set for OUTPUT_DISCRETE and do not have a very long delay on start value. Wiring Check the wiring of the heat to the 102-AX. It should be wired as follows: Point Label Terminal Universal Output #2 V2 15 Universal Output #3 V3 16 Ground G0 13 Actuator The last step to troubleshoot an issue with the heat not turning on is to test the electric heat itself. This can be done by jumping out the enable signal to 24Vac power. If the heat still does not turn on, then it is faulty and should be replaced. Overriding the Output Successfully Energized the Heat If overriding the output causes the heat to enable, then the configuration of the output and the physical configuration are all correct. The 102-AX controller logic is not calling for heating. There are a number of reasons why this might be occurring. The Basics The 102-AX must be in a heating mode to enable heat. It may be displaying either HVAC_HEAT or HVAC_MRNG_WARMUP. The space temperature must be below the effective setpoint to be in heat mode and will generate a negative terminal load down to -100%. The terminal load determines when each stage of heat will be enabled (based upon how many are defined). Check that the heating/cooling setpoints and heating/cooling bands are set such that no overlap in the two modes occurs. Heating/cooling bands must be greater than 0°. Hardware Configuration If the 102-AX is not configured for a sufficient number of stages of heat, it will not enable correctly. If there is no fan, then only one stage of heat needs to be defined. However, if a fan is defined, then there needs to be at least two stages of heat, because the fan is considered the first stage. Figure 2. Fan Type and Heat Stage If the auxiliary heating is to be utilized in morning warm up mode (when the duct inlet temperature indicates that the air handling unit is providing central plant heat), then the hardware configuration must state that supplemental heat is allowed during warm up. Figure 3. Enable Heat on Warm Up If a supply temperature sensor is wired to Universal Input #1, it could be that it is sending the VAV into morning warm up mode when the heat is enabled, and thus, disabling the heat. If this is the case, there are two options. Universal Input #3 can be used instead and set as an outside air temperature. Alternatively, Universal Input #1 can be configured as “None.” Figure 4. Input 1 Selection Setting Input 1 Selection to "None" will not disable the reading of the sensor. UnivIn1_Sense.nvoAuxTemp1 will continue to report the duct supply temperature. Setting it to "None" disables the signal from affecting the internal logic – preventing the 102-AX from entering morning warm up mode. Note: If the VAV is already in morning warm up mode when the input it set to "None," the box will remain in morning warm up mode. Override the input temperature to something below room temperature prior to changing the input selection. Application Mode The SNVT input VAV_Controller.nviApplicMode can allow a supervisory controller to override the current mode of the VAV. Upon receipt of a new application mode, the 102-AX will encounter a brief synchronization period where the terminal load is held to 0%. If the SNVT is being sent from a data manager, and the period on the output SNVT in Menta is set to 60 seconds, then the 102-AX will zero out the terminal load every 60 seconds, preventing proper operation. Set the SNVT output to a period of 0 seconds, and it will only write a new value on change and allow proper external control of the mode. Airflow Setpoint The Warm up Maximum airflow setpoint must be greater than or equal to the Heating Minimum airflow setpoint.  If this is not the case, then the airflow setpoint will default to the unoccupied flow setpoint (typically 0 CFM) any time the VAV is in heat mode, and the heating output will not be utilized.  This can be easily overlooked in applications where Warm up Mode is not being used, but this one parameter must still be set. This is fixed in the Xenta 102-AX firmware v2.18. Figure 5. Airflow Setpoint Actual Airflow In order for the heating outputs to be energized, the airflow must be at least 80% of the minimum heating airflow setpoint. This is hard coded into the controller and cannot be disabled. The only way to remove the interlock is to set the minimum heating airflow setpoint to 0 CFM; however, in this situation, the VAV will close the damper in an attempt to provide 0 CFM of airflow. The heating will modulate without any airflow at that point. Figure 6. VAV Status not providing 80% Airflow Check on the VAV Status tab of the 102-AX plug-in to compare the airflow to the airflow setpoint. If the box cannot provide the necessary 80% of setpoint or there is no airflow available during the commissioning stage, lowering the airflow setpoint can allow checkout to continue. This 80% airflow requirement is looking at the on-board flow sensor of the Xenta 102-AX. If the flow value is coming from another controller on the network via the nviBoxFlow SNVT, the heat will be disabled. The nviBoxFlow input will override flow values for damper control, but heating outputs will ignore it. In this situation, setting the pressure offset (UCPToffsetPress) to 1” will bypass the limitation. This will be fixed in the Xenta 102-AX firmware v2.18. Wrap Up If everything is configured properly physically and in the 102-AX Plug-in, then the box should be enabling and disabling electric stages of heat to maintain the space temperature setpoint. Disclaimer The information contained in this document is subject to change without notice. It is also subject to change with versions of TAC Xenta 102-AX. If further assistance is required, or if you would like to add to steps suggested here, please contact Product Support.

Issue On a special holiday, sometimes it is necessary to specify an alternative time schedule to overwrite the original time schedule. For example, an AHU normally turns on from 8:00AM to 5:00PM, however, on the New Years day, this AHU needs to be turned on only from 13:00 PM to 15:00 PM. Unlike the Xenta time schedule which is created in Menta, Vista server local time schedule does not have the option to point to an alternative time schedule. Therefore, how to setup the local time schedule in TAC Vista Workstation in order to achieve this result? Environment TAC Vista Workstation TAC Vista local time schedule Tested on Vista 5.1.6 Cause Since Vista server local time schedule (also called Time Chart-Local) does not have the option to point to an alternative time schedule like Xenta time schedule does, users need to specify the alternative schedule within the local time schedule by specific steps which are described in the resolution. Resolution Since Vista server local time schedule’s alternative time schedule options’ priorities are according to the order when they were created (newer alternative chart has higher priority). It is necessary to create a “OFF all day” alternative chart to overwrite the regular schedule before create the actual time schedule for the special occasion date. Open the local time schedule by double click on it or right click and choose “Properties”.   Click on “New…” in “Event” section. Then, Uncheck “Weekly” and specify the special occasion date. Select “OFF all day” under “Time” section. Choose “Select all” under “Valid weekdays”. Click “OK”.   Repeat step 2 to create another schedule to cover the actual holiday schedule. Choose “Specify time” instead of “OFF all day” under “Time section” in this step. The alternative time schedule should work by now.  

Issue  Routers and Channels must be added in the proper order to successfully move devices. Environment LonMaker Vista TP/FT10 Cause LonMaker will only allow devices to be moved to a location on the network that has an established communications path to the Network Interface. Attempting to do so will result in LonMaker denying the request to move the device.  Resolution This example consists of a network containing L-IP Ethernet to TP/FT-10 Router (LIP) with a single TP/FT-10 Channel (FT10) and six devices. (Device 1-6). The topology and hardware used in a LonMaker network can vary greatly but the same technique should be followed to successfully insert routers, channels, and move devices around in the network.    2 TP/FT-10 to TP/FT-10 routers (LPR10_1-2) will be placed on the existing TP/FT-10 Channel Drag the Channel Stencil onto the drawing and designate it as a TP/FT-10 Channel. Drag the appropriate Router Stencil into the drawing. The New Router Wizard will then allow you to name the Router (LPR10_1)and designate the Near/Far side Channels. Channel A (near side) is designated on the old FT10 channel and LPR1 Channel B (far side) is designated on the new FT10_1 Channel.   Repeat steps 1 through 4 for LPR2. which will result in the following The original TP/FT-10 Channel can now be renamed to represent the FT10 Backbone. Select devices to be moved onto the new FT10_ 1 and FT10_2 channels. Right Click each device and select "Move Device > Change Channel".  (Device1) In the Channel Select Wizard, Change the Destination Channel to the Desired new Channel. (FT10_1) Repeat for Devices 2-5 on the FT Backbone to the desired new FT-10 Channel.

Issue Creating many TGML graphics that use the same or similar links and bindings can be difficult and time consuming. Environment TGML Vista Workstation Cause The copy and paste feature does not work on more than one link at a time. Resolution Whenever a Vista database export is performed on a group of TGML graphics, a .zip file is created that contains a source TGML file for each selected graphic, and one XML file describing all of the links and bindings contained in the database for those graphics. By editing this XML document and leveraging find/replace capabilities of text editors, the process of manually populating links and bindings can be sped up substantially. Warning: Always back up your database before performing any manipulation of XML files. There is a potential for your graphics to be ruined if a mistake is made, so be sure a current backup is available in this event. This is an advanced operation and should only be attempted by individuals with an understanding of Vista TGML graphics. This example shows how to populate the links on a standard menu that appears on every TGML graphic in a database. For simplicity, the database has three graphics: AHU1, AHU2, and AHU3. But the steps can be applied to hundreds of graphics just the same. A menu is created in TGML with a link to each graphic. The links are named AHU1, AHU2, and AHU3. These will correspond with the TGML objects in Vista that are also named AHU1, AHU2, and AHU3. The names do not have to match, but it is a good design standard to follow whenever possible. Right-click on the first graphic and choose Open Links Window. The first graphic should be populated manually to give a template for the rest. Populate each link using the traditional drag-and-drop. Verify the links are populated correctly. Go to File > Database > Export.... Select "Get a customized copy of the database.  This is the only option that needs to be selected. Highlight all of the graphics and drag them into the Export window. Click the green arrow in the upper-lefthand corner of the Export window and give the .zip file a name. Click Save. A message will appear stating "Vista Database Export completed" Find the resulting .zip file in the location specified in Step 4. Right-click and extract all files. Depending on the operating system and software, this step may vary. Unzip the specified file. In the resulting folder, find VistaDbImportExport.xml. Right click and open with Notepad or other text editor. Find Objects of type "TGML_LINK." If the RELREFID is populated, then this link has a destination. If it says RELREFID="" then this link is not yet populated. Time for some strategic find/replace. In this example, AHU1 has all of the links populated. But AHU2 does not. There are three links on each page that all share the same destination. Find the populated entry for AHU1 links: Object TYPE="TGML_LINK" NAME="AHU1.AHU1" DESCR="" SHCP="" SHCR="" IOLABEL="" RA="" WA="" KEYLABEL="" RELREFID="Graphics-AHU1" _PROTECTED="0" Find the non-populated entry for AHU1 links: Object TYPE="TGML_LINK" NAME="AHU2.AHU1" DESCR="" SHCP="" SHCR="" IOLABEL="" RA="" WA="" KEYLABEL="" RELREFID="" _PROTECTED="0"   Select everything after the graphic name that is not unique and perform a find replace: Find: AHU1" DESCR="" SHCP="" SHCR="" IOLABEL="" RA="" WA="" KEYLABEL="" RELREFID="" Replace: AHU1" DESCR="" SHCP="" SHCR="" IOLABEL="" RA="" WA="" KEYLABEL="" RELREFID="Graphics-AHU1"   Repeat this action for AHU2 and AHU3. When all of the edits have been made to the XML document, save and close it. Highlight the XML document as well as all of the TGML files in the unzipped folder. Right click and select Send to > Compressed (zipped) folder. This will create a modified database export file. In Workstation, go to File > Database > Import. Browse to the .zip file created in Step 12. De-select Perform alarm refresh and hit OK. A message will be displayed that says "Vista Database Import completed. All of the links on every page are now populated.

Issue When using multiple .lic files, Vista Licensing Server can  have issues reading all the files. If the license features were not purchased on the same Entitlement, manually consolidating the licenses into one file will be necessary. Product Line TAC Vista Environment Licensing FlexLM Vista Cause Multiple licenses not read which results in purchased features not unlocking. Resolution   Open the .lic files in Notepad, Wordpad or text editor of your choice. Verify that each license to be consolidated are entitled to the same MAC address or Dongle.  Line 2 of the files should all have matching "Server This_host xxxxxxxxxxxx" Chose one of the files to become the "Master" Copy and paste the "INCREMENT" contents of the files at the end of the "Master" The final result will be a file with one "Header" and listing all of the features below.