Building Automation Knowledge Base

Issue Right-click on a Xenta Server 5/7/9xx in Vista Workstation to edit, but the option for Edit is gray (not enabled) or is not there at all. Environment Vista Workstation Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Cause A mismatch between the installed version of XBuilder and the specified XBuilder version in the properties of the Xenta Server. A different implementation of a Xenta 5/7/9xx controller. Resolution Check that this is being utilized as a true Xenta Server Check that the Xenta Server is added in the database using the object type Xenta Server.  All other implementations are not truly Xenta Servers, and will not have the option to edit XBuilder directly from Vista.  It may be a: Xenta 911 Communication Port Xenta 5/7/9xx LON node in an LNS database.  Vista only recognizes the XIF of the device In both of these cases, XBuilder is edited and stored locally, not in the Vista database.  Check the associated XBuilder version of a Xenta Server Make sure the correct version of XBuilder is installed on the PC. Right-click on the Xenta Server and select Properties. The version of XBuilder the system is expecting to find is shown here. This is a write-able field. If needed, change it to the correct version of XBuilder that is installed on the PC. Refresh the network and then the Edit option should be available.

Issue Configure a digital value to show as ON/OFF instead of 1/0 in a Xenta 5/7/9xx Value Page Environment Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Value Page XBuilder Cause XBuilder Values Pages will read and display raw data from a variety of sources. It can be formatted in a graphics page or a third party interface to be displayed in any desired format, however, a Values Page is a simple drag-and-drop configuration. To alter the display, values must be routed through Signal objects in XBuilder. Resolution Use the Enumeration Function. To create an enumeration that shows ON/OFF: On the Tools menu, click Enumerations. Under Enumerations, click New. Type the name (ON_OFF) and then press ENTER. Under Definitions, click New. For the value 0, ‘OFF’ then press ENTER. Under Definitions, click New. For the value 1, type ‘ON’ and then press ENTER. Click OK. To use the enumeration: Create a signal in the System Pane for the point. Select the signal and find the property 'Enumeration' Click on the dropdown list and select ‘ON_OFF’.

Issue A SNVT_press_p in a controller shows the wrong value in Xenta 511. Lonmaker and Vista are showing the correct value. Environment Xenta 511 SNVT_press_p Cause If US measurement system is selected all SNVT_press (P and F included) will show up in graphic and on value pages will be shown as PSI. Vista and LonMaker default to "WC (inches H 2 O). Resolution The best way to change the unit is to create a signal for the object and change the unit to “WC (inH2O). Then you will get the pressure in "WC everywhere you use the signal. You can also change it for just one graphic or value page by changing the signal under the graphic/value page.

Issue Host Trend Log reporting "?" for some values Environment I/NET Seven Host Trend Log Cause The reason for the "?" is because a rule was not complied with. The Print interval/Sample Interval did not result in an even number. Resolution The Basic rule for the "Host Trend Log" is the Print Interval (divided by) Sample Interval – must equal an even number. For example the default setting in this editor is as follows: Print Interval – 1440 Sample Interval – 30 So 1440/30 = 48

Issue There are some rules using the I/NET Seven "Working Offline" options. Environment I/NET site Cause  I/NET Seven "Working Offline" options Resolution If you take a DCUxxxx.sav file from an older version of I/NET Seven and open it up thru the "Work Offline" in a newer version of I/NET Seven (Rev 2.xx) and modify that save file. You will have issues with this DCUxxx.sav file, for instance if you return this modified DCUxxxx.sav file back in the older version of I/NET Seven you will see changes in the Time Schedules and "Door ATS" time schedules in a Mipped 7920 board. It adds two new lines in Time Schedules and the "Door ATS". Here is what you will see in the "Door ATS" APB (Anti Passback) settings for that door. APB Reset for that door. This is the Original ATS Schedule. So the Rule to follow is this: If you are working with DCUxxxx.sav from I/NET Seven rev 1.xx, then you must use the same version of :Work Offline. If you are working with DCUxxxx.sav from an I/NET Seven rev 2.xx, you must the 2.xx version of "Work Offline"

Issue When right clicking on some BACnet objects within Cyberstation (like EventEnrollments and Schedules) and clicking on "Rename", you may receive the following error message when you click Finish: "Cannot set the Name. An attempt has been made to write to a BACnet property with a value that is outside the range of values defined for the property." Environment CyberStation Cause This issue occurs when you specify a Name that does not conform to Alias constraints (16 characters, letters, numbers, period, and underscore only). Resolution Rename the object through its properties page to work around this limitation.

Issue Installing TAC Config on a PC that already has I/NET using MSDE SQL server installed. Environment PC that already has I/NET using MSDE SQL server installed Cause The installation will ask if SQL server is already installed. This can be confusing if it is previously installed for I/NET. Since a new instance is required, the correct procedure is to install new. Resolution When you install TAC config, the installation program will ask you if you want to install MSDE SQL server or "a Microsoft SQL server is already installed." You have to pick "Install MSDE SQL server..." even though you already have one instance of MSDE. TAC config will install a new instance of MSDE for Vista. You should only pick “a Microsoft SQL server is already installed” if you have another (not MSDE) SQL server installed on the machine that you want to use for Vista.

Issue The Function Block in LonMaker has a completely different set of SNVTs than the associated MTA file. Environment LonMaker Menta Cause It is possible to have 2 completely different TAC Xenta (300/400/280) controllers that have the same program ID. LonMaker will use the same template for all devices with the same program ID. To fix this you have to get a new program ID for one of the controllers. Resolution Follow the steps below to get a new program ID for your controller: Open the application from System plug-in by right clicking on controller and select configure-edit. To give the application a new XIF either add a “dummy” SNVT or go to device configuration and uncheck the tick box for “XIF header generated according to LonMark standard”. Hit F12, select commands and generate. Hit F12 again and save the application to the hard drive by selecting File-save as. In system plug-in, browse in the application that you just saved on the hard drive. Update TAC Network and TAC Database. If you are asked to resynchronize, do so. Download application and parameters to the controller.

Issue Limitation of Groups/Units in one Vista DB Environment Vista database Xenta groups LonWorks groups Cause Network design limitations, maximum number of controls used on a network. Resolution No more than 30 TAC Xenta groups per LonTalk Adapter. No More than 30 TAC Xenta base devices per TAC Xenta group. Maximum of 400 TAC Xenta base devices per LonWorks network No more than 50 LonWorks groups per network. No more than 64 LonWorks units per LonWorks group. Maximum of 1000 Devices using standard SNVT communications.

Issue Reverting to an older version of Vista / Downgrading Vista Environment TAC Vista Server IV Cause Typically done on an engineering PC, downgrading a version of Vista can result in problems since this is not a practice that is rigorously tested. Resolution When restoring a previous version or downgrading Vista the first thing to do is to delete the TAC Shared Folder (Program Files/ Common Files/TAC Shared). After the directory is removed then run the older version install files. If you are using Vista 4.3.0 or higher, be certain that your Computer Name in Instance field of Server Setup/SQL Server is correct, (ComputerName/TACVISTA). You can test the SQL connection to verify it is correct after the installation is complete.

Issue Displaying “??781”, “??782”, ”??787” or similar values. Environment Vista Workstation Cause The "??781," "??782," "??787" are in fact a Vista error codes, however, these codes are not documented. We have used the following approaches to get the device talking. Resolution In Vista right-click and upload parameters to the devices. Right-click > Properties > XIF File, browse in the XIF file to the Vista database.  In LonMaker Recommission the devices and Update the Vista Database. Try to delete the device from LonMaker, update the Database then reinstall the device. There is not a known proven method; these are things to try. Observe the results of the steps and please call if you are unsuccessful at seeing a change

Issue   LonMaker repeatedly prompting to drop items on a resynchronize command Environment Echelon LonMaker Cause When LonMaker resynchronizes there is an option that is sometimes overlooked to "Automatically add shapes to drawing." If this is unselected then the process may take a very long time to fix the drawing of large networks because of the manual placement of shapes. Resolution Select "Automatically add shapes to the drawing" in the Resynchronize prompt to avoid manually placing each new shape.  

Issue   Microsoft Visio will start stand-alone but will not start if launched from Echelon LonMaker Environment Microsoft Visio Echelon LonMaker Cause Without an administrative login, the software will have limited functionality or not function at all. Resolution Ensure the logged in Windows user has administrative rights.   

Issue If you take a DCUxxxx.sav file from an older version of I/NET Seven and open it up thru the "Work Offline" editor, in a newer version of I/NET Seven (Rev 2.xx) and modify that save file, you will have issues with this DCUxxxx.sav file.  For instance: If you return this modified DCUxxxx.sav file back in the older version of I/NET Seven, you will see changes in the Time Schedules and in other functions. In the "Door ATS" schedules, using a Mipped 7920 board, you will see two new schedule entries with “APB” (Anti-Passback) this could effect the way the door functions. Environment I/NET Site Cause hazards using the “Work Offline” function in I/NET Seven Resolution The Basic rule to follow - If the Sav file came from an I/NET Seven rev (1.xx) system, then use the “Work Offline” from the same I/NET Seven rev (1.xx). The same rule applies for the I/NET Seven rev (2.xx) – stay within the same system. Never try to use any I/NET Seven “Work Offline” function on any I/NET 2000 DCUxxxx.sav files. This will corrupt the I/NET 2000 DCUxxxx.sav file beyond repair.

Issue Upgrading to I/NET Rev 2.13 steps to follow if changing to Server/Remote Client configuration Environment I/NET site with release prior to 2.13 Cause Help with upgrade to 2.13 Resolution Rev 2.13 Introduces a Server/Client option for I/NET Seven. The following steps should be taken if the upgrade is to change from a Filemaster with Equalized Clients to the new Server/Remote Client Configuration. Otherwise the normal upgrade procedure should be used. Note there are new DCU binary files as well as new DPU48k and SCU1284 binary files in this release. The DCU files introduce the Reliable messaging capability and the DPU48k and SCU1284 binaries introduce the door code control option. Open I/NET Config on each Equalized Client Host and drop the equalization. Open Host Masking on each Equalized Client and Clear all masks on all Links. Open I/NET Config on the Filemaster and make sure all Clients have been dropped. Open Host Masking on the Filemaster and make sure masks have been set to receive messages and trends from all hosts and NPRs on the network. Open Network Configuration on the Filemaster and make the Filemaster the Restore Host for all Links. Stop I/NET on all hosts. Start DbCreate on the Filemaster and make a backup. Install I/NET Seven Rev 2.13 on all hosts. Configure one host (Filemaster most likely) to be the Standalone Host which will act as the Server. Configure the remaining hosts to be Remote Clients pointing to the Standalone host. If ID Works was installed on an Equalized Client pc, use Administrative Tools on that pc to configure the System DNS Seven ODBC to connect to the SQL Server on the I/NET Seven Server pc. If there were Seven Trend definitions only on an Equalized Client, they must be created on the Server after the upgrade since Trends are no longer saved on the Remote Clients. Make sure the message and trend archiving is configured as desired on the Server since archives are no longer saved on the Remote Clients. If there were any Network Functions specified only on an Equalized Client they must be created on the Server since the Remote Clients no longer perform Network Functions.

Issue Controlling a SNVT_Occupancy from a Vista Time Chart Environment SNVT_occupancy Vista Workstation Time Chart Cause Vista Server allows you to create local time charts that run a user defined schedule, however the output values of the chart are not directly editable and this can lead to a problem when you are trying to control an occupancy signal which expects a zero for an on value. Resolution To resolve this problem you can send the time chart output to a Menta program, however if you had a Menta application available you likely would have just created the schedule in the programmable controller. If a programmable controller is not available and you only have Vista Server and an ASC controller with an occupancy input you can follow these steps to control the input: Create a local time chart in Vista. Under the general tab change the Paired texts to "1,0" instead of "0,1". Create an object transfer object in Vista. Under the Transfer tab specify the time chart as the From object and set the property to "Auto Value". Set the To object to the occupancy input and the property to "Value". The destination of the object transfer will now reflect an occupancy value based on the time chart. Warning: Vista Server must be running for this connection to work  

Issue "TrendLogWizProfiles not found" error when trying to create a trend log Environment Vista Workstation Trend Log Cause This error can be caused when the Trend Log wizard profiles file has become corrupted. Resolution Browse to the TAC Vista directory in Vista Workstation Double click on the $TrendLogWizProfiles object. At the bottom is the "Source File Name". Click on the data field and click the browse button "...". Browse on your hard drive to $ini directory found in the Vista Installation directory (C:\Program Files\TAC\TAC Vista 4.5.0\$ini for Vista 4.5.0). Select the $TrendlogWizProfiles.xml file and click "Open" and then "Ok". The profiles should now be updated and you should be able to use the create trend log wizard again.

Issue How to create a link to an Alarm/Eventview in a TAC Vista graphic (OGC). Environment TAC Vista IV OGC Graphic Editor Cause This feature is really good if you have multiple sites in the Vista database and need to access events or alarms from one site from your graphic. Resolution In Graphic editor, create a link area. In the link area, browse other graphics. You can also manually write a path to an object. Write the path to your Event or Alarmview object Save the graphic to database Close the editor. Open the graphic in Vista Workstation, click on the link area and your personal alarm view will appear.

Issue In I/NET 2.13, cannot access NP Routers, when Link Type is equal to Netplus Router (NPR) Environment I/NET Site Cause I/NET 2.13 site and cannot access NP Routers Resolution As a workaround... Edit the configuration profile Choose None, or Direct Link, enable TCPIP, then close the window. Restart I/NET (close I/NET and I/O Server, re-open) Go back to I/NET Configuration. Click modify and then should be able to access the NP Routers button. (You need to do this every time you need to access the Netplus Router directly.)

Issue Vista Workstation Alarm: "The SQL database size has fallen below the size threshold" Environment Vista Workstation Cause TAC Vista always monitors the database size of the SQL server and if the size grows bigger than the limit set in TAC Vista, there is an alarm (this is because the limitation in the free desktop version of SQL server MSDE). If the size has been above the limit and returns below the limit again, the alarm reads "The SQL database size has fallen below the size threshold." Resolution Sometimes this alarm will display in the alarm list even though the size never grew above the size limit. If there hasn't been any alarm that says that the size has grown over the limit, the alarm "The SQL database size has fallen below the size threshold" is nothing to worry about.