Building Automation Knowledge Base

Issue When we display the SNVTs in Vista, NL220 or Lonmaker the name of the SNVTS are very generic. Environment NL220 Lonmaker Vista Cause The XIF file was uploaded from the device. On some devices the function specific names are not supplied from the controller. Here is a sample of non specific names when uploaded from the controller     Here is a sample of the same controller with the XIF download from the manufacturers website. Resolution Go to the controllers manufacturers website or contact them and get the functioned named XIF file for that device. Use this instead of the uploaded XIF from the device.

Issue How to enable Vista to log change of state events without trending every point. Environment TAC Vista Cause Need to log events to monitor change of state without using trend log.  Resolution There are two options to enable TAC Vista to log change of state events as shown below: Option1: Right click on the object you wish to monitor and open the properties of it. Change the watch settings from No watch to Watch. Note: Must use "Change of state" object.  It is not possible to do this under the Workstation or within a controller.  Right click on the TAC Vista and create a new folder - name the folder accordingly. Right click on the Folder which was newly created and create a new Object called change of state. Give a desired name and open the properties of the object. In General tab change the priority from 9 to Info. Select the Alarm tab set the low limit as 0 high limit as 1 and minimum change as 0. Select the object tab and navigate to the object to monitor. Close the popup by selecting OK. When ever there is change in state “on” to “off” or vice versa the event is recorded as object change in the Event view To see the events right click on the change of state object and select view events. Filter it by unselecting the alarms button on the window. Observe that events of the object are shown. Option 2: This needs to be done in your Menta file and it requires downloading to the controller. Open the Menta file of the desired device using edit option. Add a Alarm block to the Menta file. Connect the output / input block to the input of the Alarm block as shown. Right click on the Alarm block and select the edit option. In edit window of the Alarm block make sure the priority is set “0” (N.B. do not change it). Click on the edit button in the edit window of Alarm block and enter the desired text in the Alarm text. Steps 2 to 6 need to be repeated, if you need to do for more then one Input/Output Save the Menta file and download the same to the controller. These events are shown in Events views and not in the Alarms

Issue The sticker on the face of a Xenta 102-AX identifies the hardware version (1 or 2). If the board is changed out, then the actual hardware version may not match what is listed on the label. Visually inspecting the board can reveal if the board is a hardware version 1 or hardware version 2. Environment Xenta 102-AX Cause The orientation of components on the PCB of the Xenta 102-AX changed on the major revision from 1 to 2. Resolution Remove the plastic face plate from the Xenta 102-AX to reveal the logic board beneath. Look at the angle of the velocity pressure sensor. If the velocity pressure sensor is positioned perpendicularly to the controller (at a 90° angle), then it is a hardware version 1 controller. If the velocity pressure sensor is positioned at an angle, then it is a hardware version 2 controller. See image below for clarification:  

Issue When using the Generate project command in XBuilder the Generate output screen will not show any errors even though it reports an error was encountered or the error is visible but the info message indicating what it was trying to build the caused the error is not visible. Using the Window-> Restore Default Settings does not correct this. Environment TAC XBuilder Cause A filter has been applied to the Output window. Resolution Right click in the Output window and ensure that each of the following options are selected: Show Info Messages Show Warning Messages Show Error Messages

Issue Xenta 104-A ships from factory with a resistor on terminals 7 and 8 Environment Xenta 104-A Cause Terminal 8 is input U1, which is used by the controller for outside air temperature in the economizer calculation. Resolution The resistor is 1.8kΩ A temperature sensor on U1 would be a 1.8kΩ thermistor, if this input was being used. The resistor is a place holder to keep the unit out of economizer during initial setup if a thermistor is not going to be used.

Issue A controller with only 2 available outputs is being used to control a 3 stage device. Environment Three stage device control where lower stages must remain active. Cause Hardware or space limitations may prevent there from being enough outputs to control a three stage device. Resolution Two controller outputs in conjunction with a DPDT (dual pole, dual throw) relay can be configured to control a three stage device. This will allow you to activate stage 1, stages 1 and 2 or all three stages by activating either one or both of the controller outputs. An example of when this might be used is to control three stages of heat or a three stage fan. A standard "ice cube" type relay can be used (IDEC RH2B or similar) and should be wired as shown in the diagram below.   The controller should be programmed to activate only output 1 for stage 1, activate only output 2 for stages 1 and 2 and finally to activate both outputs for stages 1, 2 and 3. Note that certain application specific controllers may not allow the outputs to be configured in the way described above and thus cannot take advantage of this setup.

Issue Xenta 102-AX space temperature sensor calibration offset can be set through Vista Workstation. If using degrees Fahrenheit, it is helpful to change the units on that value from "°F" to "°F, diff" to eliminate the 32° offset and make it more intuitive to the user. Environment Xenta 102-AX Vista Workstation Classic Network UCPTvavSelection.CSS Cause 0°C (whether a temperature value or an offset value) converts to 32°F. If referring to an offset value, the units of °F, diff eliminate this 32° offset. Resolution Navigate to the VAV in the network structure in Workstation Go to VAV_Controller and find UCPTvavSelection.CSS Double click the value Click on the Unit field and choose °F, diff from the drop down menu Click OK Open the value again, now enter any desired calibration offset for the space temperature.

Issue Xenta Repeater offers signal restoration and conditioning on LON networks Lon communication issues Completion-event failures Environment Vista Lon Networks Xenta Repeaters (Part # 007309120) Cause Lon Networks can suffer communications problems due to the physical length of the network and / or due to the number of devices on the network. A Xenta Repeater can help to resolve these problems and allow for a longer physical communications network and a larger number of devices to be used. Resolution A Xenta Repeater is a device that uses a standard Xenta 400 base and is installed in the middle of the Lon network channel and separates it into two segments. (Note: Lon channels are sections of a Lon network that are separated by a router while segments are sections of a channel that have divided using a repeater.) One segment of the Lon channel is connected to either of the pairs of COM 1 terminals and the other segment is connected to either of the pairs of COM 2 terminals. Each Lon segment must stay within the recommended length limits as seen below:   Cable Max. bus length, doubly terminated bus topology (m)/(ft) Max. node-to-node length, singly term. free topology (m)/(ft) Max. length, singly terminated free topology (m)/(ft) Belden 85102, single twisted pair  2,700 8,858 500 1,640 500 1,640 Belden 8471, single twisted pair  2,700 8,858 400 1,312 500 1,640 UL Level IV 22AWG, twisted pair  1,400 4,593 400 1,312 500 1,640 Siemens J-Y(st)Y 2x2x0.8  4-wire helical twist, solid, shielded 900 2,953 320 1,050 500 1,640 TIA568A Cat.5 24AWG, twisted pair  900 2,953 250 820 450 1,476   The following rules must be adhered to: A maximum of 128 devices can be placed on a Lon channel A maximum of 64 devices can be placed on a Lon segment A channel may use up to 2 repeaters creating a maximum of 3 segments If a router is not being used on a channel then there may only be 64 devices on that channel since the channel is made up of only one segment. It is recommended to limit the number of devices per segment to 50 when engineering a Lon network. This will allow for some devices to be added or re-distributed as needed during installation. The Xenta Repeater consists of two internally connected Lon transceivers, each with a transient suppression circuit. Data packets are picked up by the transceiver on one segment and re-broadcast onto the next segment using the second transceiver. Only Lon packets are read and re-broadcast rather than simply amplifying the signal along with all of the noise on the network. This provides for a strong, clean and noise-free signal on either side of the Xenta Repeater.

Issue Get Error message "Error: Unable to create blueprint file" when trying to download to Xenta device Environment TAC Vista Xenta 301 Xenta 302 Xenta 281 Xenta 282 Xenta 283 Xenta 401 Cause This can be caused if one or more of the I/O modules from the device does not have any subnet/node address defined. Resolution Click on the Xenta in Workstation In the pane to the right double click on $IO Right click and select properties on the I/O modules Make sure that all modules have subnet node defined.

Issue Tooltip feature for TGML Graphics was hotfixed in Vista 5.0.3 (Hotfix 20) and was disabled later versions of TAC Vista based on customers requirement. Refer to TPA-MALI-08-0007.01 for more details Product Line TAC Vista Environment TAC Vista 5.0.3 and later versions. Cause By default, the tooltip feature in TGML Graphics was removed. Resolution To enable the Tooltip option in TGML graphics following these steps: The Tooltip snippet is available under Snippets > Basic Functions > Tooltip. If the editor does not have this snippet, download the attached Tooltip.zip snippet. Close all the TGML windows and Install the tooltip snippet Open the TGML editor and you can find the tooltip snippet under My Snippets Drag and drop the tooltip snippet on to the graphic objects window to see the tooltip feature. After drag and drop the tooltip snippet on to the graphic, the Metadata – TooltipContainer will be added to the object properties. Tooltip will now be available for this graphics Object. Repeat steps 4 and 5 for each other graphics Object.

Issue SMTP Copy to Blind copy to Reply to Environment Vista Xenta Cause In order to CC, BCC and the option to let a user reply to a sent alarm you need to configure the Xenta's SMTP settings Resolution There are 3 options under SMTP settings in Xbuilder   Copy to - The same as CC in outlook Blind copy to - The same as BCC in outlook (A copy of the email sent discrete to chosen email) Reply to - When a user gets an email about an alarm and clicks on reply, the address will become the same as the one specified here.  

Issue When you run a test from Lonworks Plug and Play on your dell PC the card fails the test. Environment Dell laptops E6410, E6510, and E5510 Cause There is a known issue with theses laptops and a PCC-10 LonWorks card Resolution To solve the problem with Dell E6410, E6510, and E5510 laptops and a PCC-10 Lonworks card follow these solutions provided by Echelon. Link to solution 

Issue The following error message appears when browsing to webstation: Environment Windows 2008 Server TAC Vista 5.1.5 Server VistaWepApps 5.1.5 Internet Explorer Cause The current Internet Information Services (IIS) settings do not allow execution of all the .dll files webstation requires. Resolution Change the .net Trust level to full for the webstation application in IIS: Go to the start-menu and type inetmgr in the search field. Once Internet Information Services (IIS) manager has opened locate the Webstation application under %Computer Name%\Sites\Default Web Site\Webstation. In the pane to the right of the hierarchical tree, double-click on .Net Trust Levels. Change the level to Full and click on apply. Re-run webstation and confirm that it now works.

Issue Xenta 700 System Report shows "Menta: IO error (Error#:62464) Environment Xenta 700, 701, 711, 721, 731 Cause Some of the causes could be following: Might be configured to use wrong I/O Modules Wrong Neuron ID configured Menta program issues Resolution To resolve this error, check the following: Upgrade Xenta Firmware with Latest Version from the Exchange Extranet. Ensure correct I/O modules are configured. Ensure all the controllers and I/O modules are online.

Issue Background image is cut off when viewing TGML graphic Fit the image to the background, but it does not stretch to fit when viewing the graphic White bars on the side or top of live graphic Environment TGML Cause The TGML root object has a few attributes that default to: Background = #FFFFFF (white) Stretch = None Height = 600.0 Width = 800.0 These may not be appropriate for the graphic being created. Resolution In the TGML editor, navigate to the Objects pane. If the Object pane is not visible, go to View > Objects and make sure that is checked. Click on the root Tgml object.    Available properties are shown in the Properties pane below. If the Properties pane is not visible, go to View > Properties and make sure that is checked.   In a pure TGML graphic, the Background color will represent the color behind all of the components. If a large background jpg or bmp image is used, the Background color will represent the color that will show up as bars on the top and right of the graphic when it is not sized perfectly to fit in the viewer's window (if Stretch is set to None). Stretch will have three different options (this is also a user defined option, this attribute merely sets the default presentation): None -- The size of the graphic in the TGML editor is preserved in the viewer's window. This may result in blocks of color on the top or right of the graphic. It may also result in sections of the graphic being cut off from the view requiring the user to scroll to view. Uniform -- The graphic is stretched to fit the larger of either the height or width of the viewer's window. The aspect ratio of the graphic is preserved. This may result in blocks of color on the top or right of the graphic. Fill -- The graphic is stretched in both the horizontal and vertical direction to fill the entire screen. This may result in a stretched or skewed presentation of the graphic. Height and Width will set the height and width of the graphic when Stretch is set to None. In a pure TGML graphic with all vectored components, the height and width are merely relative to the size of the components and aren't of great concern. However, when a background jpg or bmp image is used, the height and width should be set to match the dimensions of the background image.

Issue When the Event Viewer is selected by any user other than the default users a error message is displayed. Environment Vista 4.42 Windows XP SP3 Cause The error that is displayed when you select Event Viewer is caused from the user not been included in the $Administrator Group. This prevents them from launching the event viewer. Resolution To enable user to access the Event Viewer follow these steps. 1. Under the root directory of Vista locate the $Administrator group. 2. Right mouse click on $Administrator  and select properties. 3. In the Users section add required users to the group using the add button. 4. Finish selection with the OK button.

Issue Suggested configuration for Xenta 121, STR-150 in single occupancy zones (Hotel Operation): Single setpoint display for ease of use for hotel guests Erasing setpoint offsets between guests automatically on transition from unoccupied to occupied Disable fan overrides Product Line TAC Vista Environment Hotel rooms Xenta 121, ZBuilder STR-150 Cause A hotel room is a unique application of the Xenta 121 and must be tailored to fit the temporary residents and be as easy to use and understand via an STR-150 as possible to reduce the amount of calls to the on-call maintenance department. Resolution The important thing to remember is that the Xenta 121 and STR-150 do not have duplex communication capabilities. Communication is one way from the stat to the controller. There is no capability for the controller to override/control the stat display. Because of this, it will be very important to standardize setpoints between the stat, the controller, and system-wide. Set Up the STR-150 Refer to the STR-150 User’s Manual for additional information. Push the fan and bypass buttons simultaneously for 2 seconds to enter P0. In P0, hold down the bypass button and push the fan button three times. The wrench symbol is lit when the STR-150 is in configuration mode. Parameter Function Value/Range Set Value P0 Software Version - - P1 °C or °F temperature display 1=°C, 2=°F 2 P2 Reference temperature (Reftemp) 15-30°C / 60-90°F 72 1 P3 Setpoint or room temp. as default 1=Setpt, 2=Room 1 P4 Timeout 5-90 seconds 10 P5 Fan settings 0= No fan 1= On/Off fan 2= Two-speed fan 3= Three-speed fan 0 2 P6 Room temperature and setpoint display resolution 0.1 or 0.5°C 0.2 or 1.0°F 0.2 P7 Max adjustable setpoint span above or below Reftemp (P2). ±0 - ±5°C ±0 - ±10°F 10 P8 Bypass button and occupancy indication When = 2, no bypass command is sent to the controller 1= Symbol on, off or flashing 2= Symbol always off 2 1 Reference temperature should equal the average of the Xenta 121 occupied heating and cooling setpoints. Assuming 70°F heating and 74°F cooling for this example. 2 There is no way to give only AUTO/ON override control to hotel guests, so fan override capabilities should be disabled. Wire STR-150 to Xenta 121 STR-150 Xenta 121 Mode 11 Y1 5 Data 12 X1 7 M 13 M 6 Set Up the Xenta 121 - ZBuilder Connected devices > Room unit Select STR-150 and Check the box for "Activate STR-150 reset offset function." Engineering TAC Xenta 120 Manual Chapter 9.1.2 states: There is a so-called hotel reset function for room unit STR-150. When activated, an 'old' offset value is not taken into account when going from Unoccupied to Occupied until the Offset is changed (probably by a new hotel guest). Control > Setpoints Center all control setpoints around reference temperature of the STR-150. In this example, the reference temperature is 72°F, so cooling and heating setpoints have been centered around that. Setpoint calculation mode is set to method A which preserves symmetry around a base setpoint, but since these setpoints are already symmetrical, that is not of great importance. Expose normalize setpoint is important for the hotel staff to see the same setpoint as the stat is displaying to the hotel guest. Operation STR-150 defaults to reference temperature as setpoint 72°F. Xenta 121 uses default setpoints. In cooling maintaining 74°F. If the stat is set to display setpoint by default, the customer will only see the setpoint and won't be aware of the 2-degree dead band offset. Hotel guest decides 72°F is too hot and lowers the setpoint on the stat to 70°F. Xenta 121 interprets this as a -2°F offset on setpoints and now maintains 68°F heating/72°F cooling. Guest checks out and the room is set to unoccupied. Stat continues to display 70°F but the larger unoccupied dead band actually controls to set default of 80°F for cooling. Next guest checks in and the room is set to occupied. Stat continues to display 70°F but the Xenta 121 has erased the offset from its calculation and maintains 74°F. Guest feels this is too warm and lowers the stat from 70°F to 69.8°F. A new offset of -2.2°F is sent to the Xenta 121 which now controls the cooling setpoint to 71.8°F. The guest believes they have lowered their setpoint by 0.2°F  but in reality have effectively lowered it 2.2°F. As soon as they make a change to the setpoint, they resume control of the offsets.

Issue The output window in XBuilder will show three different message types: Info Warning Error If an error is occurring during a Generate command, it may be difficult to locate the exact error in and among hundreds of warnings. Environment XBuilder Cause The "Previous Error" command when right-clicking in the output window will take into account both Warnings and Errors. Resolution Right-click in the output window of XBuilder Expand the Filter Messages option Uncheck the options for "Show Info Messages" and "Show Error Messages" The output window will now only show true error messages and it will be much easier to determine the error that is stopping the generate command from completing.

Issue Downloading new NXE or APB files using Lonmaker for controller updates Product Line Other, TAC Vista Environment Lonmaker 3.2 Cause Updating of software in a controller for more features or fixes. Resolution To update a new NXE or APB in a Lonworks controller using lonmaker follow these steps. 1. Download the NXE or APB file you intend to use. If it is a 100 series controller the files are available on extranet. Here is the link to the Xenta 100 series NXE files.   2. Locate the device you wish to upgrade in you Lonmaker drawing and select the load option 3. The next option screen will indicate the existing template name. Retain this name if the SNVTs are not changing. You may want to create a new template name if the SNVTs are being amended. 4. Select the Next option and then in the image name area browse to the NXE or APB file you want to download to the controller. 5. Select the next option then select the state you would like the device to be in after the new NXE has been downloaded. Then select the finish button. The application will then be downloaded to the selected controller.

Issue -Can't save Xbuilder project to Vista -Error message: The project contains errors and was not saved to Vista -Error message: Name must be supplied, Error building "name" Environment TAC Xbuilder TAC Vista Cause If you in Xbuilder add a device that uses a template (for example Modbus) and then give that device the same name as the one in the template itself you will get an error when trying to save it to Vista (saving the project standalone works fine). Resolution Change the device name in Xbuilder or in the device template and you can save it to Vista.