Building Automation Knowledge Base

Issue Can not access the SQL database with a Windows domain user, but it works with a local user on the computer. Environment Vista 5.x.x Cause By default, the Windows users in the administrator group on the PC have enough authority in the Vista SQL database.   Resolution Add the Windows domain user to the administrator group on the PC and it will work.

Issue How should a Echelon Lon Talk Adapter (LTA) be configured if used in a Vista classic network? Why is the network and controllers offline in Vista Classic? Environment Vista 4.x.x Vista 5.x.x Echelon LTA (PCC-10, PCLTA-20) Cause The NI application of the LonTalk adapter needs to be configured as NSI not VNI (Virtual network interface) in the LonWorks Plug n' Play which configures the LTA. Resolution Change the NI application of the LonTalk adapter. Open the Windows Control Panel Select the LonWorks Plug N' Play. Change the NI Application For a PCC-10 LTA select NSIPCC For a LTA-20 LTA select NSIPCLTA Click Apply Start Vista Server.

Issue Changes made to Device Templates in the XBuilder Device Editor for interfaces with Modbus, BACnet, etc are not seen by the controller after download. Environment XBuilder 5.x.x Xenta Server 5xx/7xx/9xx Cause Device Template files are not recognized by the device until the unit has restarted. Resolution When downloading the project to the Xenta Server select to "Send all project files".  This will force a warm start of the device causing the changed Device Template to be recognized.

Issue A TGML script has stopped working since upgrading to Vista 5.1.5. The string.split method is not able to identify the "^" character in Vista 5.1.5 TGML scripts. Environment TAC Graphics Editor TGML 1.1.5 (Vista 5.1.5) Cause Unknown. Resolution Use string.split("\\^") instead. This may also apply to other characters but this has not been tested.

Issue The following files are left in the root directory of the drive that Vista is installed on: eula.1028.txt eula.1031.txt eula.1033.txt eula.1036.txt eula.1040.txt eula.1041.txt eula.1042.txt eula.1049.txt eula.2052.txt eula.3082.txt globdata.ini install.exe install.ini install.res.1028.dll install.res.1031.dll install.res.1033.dll install.res.1036.dll install.res.1040.dll install.res.1041.dll install.res.1042.dll install.res.1049.dll install.res.2052.dll install.res.3082.dll vcredist.bmp VC_RED.cab VC_RED.MSI Environment Vista 5.1.5 Cause A bug in Microsoft's Install Shield which is a software tool for creating installers or software packages. Resolution Delete the files shown under "Issue".

Issue Get "Error: Device type specified in MTA file is not what TAC Vista expected, Info: Download Application and Parameters"  when downloading to a Xenta controller from TAC Vista. Environment TAC Vista TAC Xenta 30x, 28x, 401 Cause The type of controller that you specify in the device specification in the Menta application have the be to exact type you are downloading to. So either there is a mismatch or there is another controller on the network with the address you are using. Resolution Right click and Edit the controller in TAC Vista Workstation. Log in to view the Menta application Check in Options > Device Specification that it is the right type. If not, change to the right type.

Issue Get error message "Create fail for Windows TAC Graphics Editor,0,tadrawMain" when trying to start the OGC editor in a Windows 2008 server 64 bit. Environment Windows 2008 server 64 bit Vista 5.1.5 Cause Data Execution Prevention (DEP) settings are incorrect. Resolution Open Properties on "My computer"" Click the Advanced tab Click on Settings for Performance Set Data execution Prevention" to "Turn DEP on for essential Windows programs only"

Issue Choosing the wrong shape from the Loytec stencil set for L-IP and L-Switch routers can result in devices on the far side not coming online even though the Loytec routers are apparently configured correctly. Environment Vista, Lonmaker Cause Loytec provide a set of Visio shapes for use with their L-IP and L-Switch devices in Lonmaker.  Each device has two shapes associated with it - a (Router) and a (Switch). The (Switch) shape should only be used if the Loytec device is to be used in "Smart Switch Mode".  If the (Switch) shape is used with a Loytec device intended for use in "Configured Router Mode" it will not work, even though the device properties are correctly configured in Lonmaker and the DIP switches on the device are correctly set (DIP1 OFF and DIP2 OFF). Resolution For a Loytec device to be used in "Configured Router Mode", choose the appropriate (Router) shape, set the Router Type of the selected port to "Configured" (each port must be set individually) and ensure the DIP switches are correctly positioned (DIP1 OFF and DIP2 OFF)

Issue What is the difference between Vista Upgrade Package vs. Vista 5 Package? Environment Vista 5 installation Vista 5.1 Software Packages - Standard, Manager, Professional, Enterprise Cause Each Vista 5 licensing package has an analogous Upgrade version (marked -UPG).  When ordering the license, it may not be known what that -UPG means or when to order an Upgrade versus a regular license. Resolution The Vista Upgrade packages are the same delivered product as the typical Vista Packages. There is no check for previously installed software during the installation of the upgrade package. The installation of both are the same. However, because the upgrade packages are offered at a discounted price, Order Entry personnel restrict the purchase of upgrade software for sites where a record of a previous Vista installation does not exist, Upgrades are not meant for new site installations, and are only available for upgrades from latest previous version, i.e. 5.0 to 5.1.

Issue Unable to start the DSS writer service. Get a message that "certain services stop automatically when not in use". Environment Windows 2008 server 64-bit Vista 5.1.4 Cause Vista 5.1.4 is not compatible with 64-bit operating systems. Resolution Run Vista 5.1.4 on Windows 2008 server 32-bit or upgrade to Vista 5.1.5 which can be run on Windows 2008 server 64-bit.

Issue How to change the default SMTP port in Vista 5.1.5 running on 64-bit operating systems Environment Window 7 64-bit Windows 2008 server 64-bit Vista 5.1.5 Cause The registry key that allows the SMTP port to be changed is located in a different folder when running 64-bit operating systems. Resolution Open the registry editor. Start\run and then type regedit Go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TAC AB\TAC Vista\5.1.5\SMTP and locate the entry named Port. Double click on this entry and change it to the desired port number. Click OK. (The Wow6432Node folder is a folder that contains information about 32-bit applications being run on 64-bit operating systems).

Issue Network variables from LON devices not included in export file. Environment Vista 5.1.X Workstation Cause The user does not have system manager (or higher) authority. Resolution Grant the user that will be carrying out the export/import function system manager authority level. Here is some information on the different authority levels in Vista (taken from the help file) Authority Level In this field you can choose between: User has the lowest rights and is in principle only allowed to see values (and not change them) and acknowledge alarms. Field Manager is, in addition to this, allowed to change values of points and force variables in the installation. Operation Manager is, in addition to this, allowed to program everything; to create and delete objects, to configure objects, to assign authority to objects, to create and edit color graphics. He may also disable alarms and change parameter settings in the installation. However he has no access to functions that affect system security. System Manager has all rights and can for example create/delete user profiles, log out other operators, set passwords, assign authority to objects, define network nodes etc. Normally, very few persons have these rights.

Issue Need the Part Number for a Xenta 527 or 527-NPR Environment I/NET Vista Cause There are 2 Varieties of the Xenta 527 available: The Xenta 527 and the Xenta 527 NPR. While these devices share some similarities, there are some key differences. Resolution There are 2 Varieties of the Xenta 527 available. The Xenta 527 and the Xenta 527 NPR. The Xenta 527 is sometimes referred to as the Xenta 527 - Web Server.  This part can be used on I/NET systems, or I/NET systems that integrate with Vista.  The Xenta 527-NPR is use on I/NET systems.  It is a scaled down version of the standard Xenta 527 that will only provide the functions needed for I/NET.  This serves as a direct replacement for existing NPR devices. The Part numbers for these devices are as follows: Xenta 527 (Web Server) - 007308200 Xenta 527 (Web Server) Package of 3 - 007390130 Xenta 527-NPR - 007308210

Issue What hardware is necessary to integrate an I/NET security system with a Vista front end? Environment Vista 4.5.0 Vista 5.x.x Xenta Server 527 Cause To properly integrate an I/NET security system to Vista a Xbuilder project must be used to expose the I/NET controllers in the Vista tree structure. In addition the unit must not block AMT (Alarms, Messages, and Transactions) traffic from the I/NET controller LAN. Due to these requirements the Xenta Server 913 and the Xenta Server 527-NPR do not meet the requirements to integrate an I/NET security system into Vista. Resolution Use a TAC Xenta 527 (part number 007308200) for integration of an I/NET security system to Vista.

Issue Does ZBuilder require an additional license? Environment ZBuilder 4.5, ZBuilder 5.1.4, ZBuilder 5.1.5 tested Cause ZBuilder does not require any additional license. Resolution ZBuilder is installed with Vista Workstation.  No additional license is required in order to open ZBuilder.

Issue What is the supported DC voltage on Xenta controllers? Environment Xenta controllers Cause DC Voltage is available for power. Resolution The table below list the supported Voltage DC specifications for Xenta controllers For more information check Data sheets for Xenta controllers located on The Exchange.   Xenta Controller Volt DC Support 411 19-40Vdc 421 21.6-40Vdc 451 21.6-40Vdc 471 19-40Vdc 491 19-40Vdc 400 Series 19-40Vdc 300 Series 19-40Vdc 200 Series 19-40Vdc 500 Series 19-40Vdc 700 Series 19-40Vdc 900Series 19-40Vdc 101 No Vdc Support 102 No Vdc Support 103 No Vdc Support 104 No Vdc Support 120 series No Vdc Support

Issue A Xenta 5/7/9xx controller can either be implemented as A Xenta Server, where it doubles as the LonTalk adapter and a Xenta device A LON node, where it is a part of an LNS database below a different LonTalk adapter If the Xenta is a LON node, then it will be represented as a LON device in the network, but also utilizes Xenta Group Bindings to communicate to Xenta programmable controllers (280/300/401). If graphic pages in certain Xenta units aren't displaying data, or connection objects aren't passing data as expected, the online status of the Xenta units should be checked not from the Vista Server, but from inside the Xenta 5/7/9xx. This issue will display red x's on the graphics page. Product Line TAC Vista Environment Xenta 511, 527, 701, 711, 721, 731, 913 LNS Database Cause A Xenta 5/7/9xx LON node pulls "double duty" as both a LON device and a Xenta Lacnet device. It requires one Xenta Group Binding on message tag 0 to facilitate communication with Xenta programmable controllers. Resolution Log into the web interface for the 5/7/9xx. Navigate to Utilities > LacNet > LacNet List Xenta.  "LacNet" refers to proprietary Xenta communication. View the online status of each Xenta programmable controller in the network.  It is displayed as below: =============================================== Node: RTU7 Xenta group: XG_RTUS  GroupMaster:No FTP state alarmstack, app:finished OnOff:N/A Latest FTP : 05/13/2011 11:25:59 State: online (since 05/13/2011 11:23:05) Xenta???  Software version: 3.84-01 NID: 04:6B:84:9F:01:00  Subnet/Node:  253/122 Module: SUMMARY Module: CALIBRATE Module: CONFIGURE Module: ALARMS Module: SETPOINTS Module: ERRORS Module: $LOG Module: $SYSTEM Module: $SYS Number of alarm objects: 25 Number of public signals: 7 Number of handles allocated: 8, where 1 is with notification ===============================================

Issue Description of the file types and file extensions in Menta. Environment Menta Vista Lonmaker .AUT, .TLG, .MCB, .COD, .XLG, .ESP, .OPE, .OPC, .ESP, .BIN, .CHR, .COD, .XIF, .MTA, OPDOC.GOP, .SPT, .BIN, OPDOC.SPT, OPDOC.TMP, .BPR. Cause Description of the filetypes in Menta. Resolution The following data files are involved when creating a Menta application for a Xenta 280/300/401 device. .AUT Text file with application program source code and data including graphical block diagram. .TLG The trendlog definition. .MCB Macro block file (Group of blocks). .COD “Machine code” file in ASCII format for downloading to the TAC Xenta controller. .XLG The compiled trendlog definition. .ESP Specification file with public signals, their attributes etc. generated by TAC Menta. This file contains input data to the OP configuration tool. .OPE A file with an empty tree, i.e. an OP tree without a specification file. This is the kind of file that is created when the OP configuration tool is run from the program manager. .OPC A mix of an .OPE and an .ESP file. This file is created by the OP configuration tool when it has been invoked from TAC Menta. .BIN Binary file with OP menu tree data for downloading to the TAC Xenta controller together with the .COD file. .CHR National character set file for downloading to the TAC Xenta controller together with the .COD file. .XIF External interface file containing a standardized description of all network variables/ objects of the application program. The .XIF enables binding and communication with LonWorks nodes from other manufacturers. .MTA Menta project file, which can include all files (all types mentioned above except for .MCB and .OPE) related to a certain application. Once a file (for example .AUT or .OPC) has been inserted (saved) in the project file, it can be extracted (opened) anytime as an .MTA file. The .MTA file can be stored directly in the TAC Vista database. Note: The .MTA file can be stored in the TAC Vista database even though it can not be compiled. An .MTA file which is not compilable will not, of course, be possible to download into a TAC Xenta device. It must be correct and compilable before download is possible. In addition to the files listed above, the following data files are involved in the creation of the .BIN file. These files are placed in a specific directory for temporary files. OPDOC.GOP An ASCII file created by the OP configuration tool when the Generate command is executed. This file is converted to an .SPT file, which in turn is converted to a .BIN file OPDOC.SPT Intermediate ASCII file generated from the.GOP file. OPDOC.TMP Intermediate ASCII file generated from the.GOP file. BPR The Network Neighborhood file, describing the TAC Xenta device’s surrounding network nodes and groups. This information was taken from the TAC Menta Technical Manual.

Issue Can not view OGC graphics in Vista 4.5.0, only a white screen is shown when the graphic is opened. It is possible to edit the graphic and create new graphics but not view any OGC graphics. Environment Vista 4.5.0 Windows 2003 server Cause The folder C:\Documents and Settings\user\Local Settings\Temp\TemporaryGraphicsFiles is missing, this is where the cached OGC files should be saved. Resolution Create a new Windows user Log into Windows with that user Start Vista with that user The cache folder is created and it is now possible to see graphics again

Issue A loggbackup file is not copied from $bkp in the Vista database to the place specified in the backup object. Environment Vista 5.1.5 Windows XP SQL 2005 express Cause When the SQL server is finished with the backup it tells Vista, and Vista then copies the bkp file from $bkp in the Vista database to the place specified in the backup object in Vista. In this case the SQL server succeeds with the backup but fails to put it in the history log called dbo.backupfile in the MSDB database. So Vista never gets the message that SQL is finished and doesn't move it to the right location. Resolution The dbo.backupfile table in the msdb database was corrupt and needed repair. Contact PSS or have a SQL expert check the msdb database.