Building Automation Knowledge Base

Issue I get an Error message saying, "There is no folder for this object" when I try to create an object. Environment Vista Workstation Cause This error occurs if there is a dash or hyphen (–) in the name of the object being created. Vista uses the dash to define folder paths in the database, e.g. a graphic named RTU-1. Vista sees this as a graphic "1" in the folder "RTU." Resolution Do not use dashes or hyphens in the naming convention for Vista objects. Either eliminate it altogether, or use underscores (_) instead.

Issue Why Vista Workstation Remote is not supported for Internet Use Environment Vista Servers not in the same network Cause Technically Vista Workstation Remote can communicate to a Vista Server over the internet but this is not a supported practice due to the network requirements for the Vista Server. Resolution The Vista Server must be on a PC that is not behind a firewall which utilizes address translation. The IP address of the computer must be the same IP address that Vista Workstation Remote will use to communicate with it. Due to the nature of DCOM (Distributed Common Object Model) which is used by Vista Workstation Remote many ports would have to be left open on the PC and the network firewalls. Vista Workstation Remote connects to DCOM's Service Control Manager (SCM) on port 135 which will dynamically assign a port for the programs to communicate on. Since this requires ports 135 and the entire range of ports that the SCM utilizes to be open on the PC and the firewalls the risk to the network is significant. Most IT departments will not be willing to leave their network so open and exposed. Therefore, Vista Workstation Remote is not supported for Internet use. To use Vista over the internet please look into a web server (Xenta 511/527) or Vista Webstation.

Issue How do I build Vista graphics pages offline from the system running my Vista database? Environment Vista IV OGC Graphics Cause Engineering graphics on an offline database allows the work to be completed away from a customers site after the installation phase of the project has been completed. Resolution Make a backup of the Vista database so you will have the necessary points for the graphics pages. Restore backup on the PC that you want to build the graphics with. Build the graphics pages and save them as .ogc using file-save, not db save. When all pages are complete, copy the saved files to the system running the database. Create the necessary graphics objects in the Vista database. For each of these objects, right click and go to Properties and browse in the new files with the Source File button.

Issue Configuring Error Logging for Program Crashes Environment I/NET Seven Site Cause Dr. Watson is not the default debugging software then the following steps can be used to configure it to be used as the default debugger Resolution Dr. Watson is a debugging program that is installed with the Windows operating system that generates error reports when programs crash. These error reports are very useful in determining the cause and support personnel will typically request a Dr. Watson log file as the first step of troubleshooting the problem. If for some reason Dr. Watson is not the default debugging software then the following steps can be used to configure it to be used as the default debugger. In the Start menu Run command type "drwtsn32 -i" and select "Ok". You should receive notification that Dr. Watson has been installed as the default application debugger. In the Start menu Run command type "drwtsn32.exe" and select "Ok". You can configure the directory that log files will be placed in among other options. The default directory is "C:\Documents and Settings\All Users\Documents\DrWatson\". In the Start menu Run command type "regedit" and select "Ok". Browse to "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\AEDebug" and verify that the entry "Auto" is set to the value of 1. Dr. Watson log files should now be generated upon program crashes. The above steps should be valid for Windows 2000 operating system and newer

Issue Problems installing TAC Config. Environment Vista IV TAC Config Cause DDP1.1sp1 –KB867460-x86.exe The upgrade patch cannot be installed by the Windows installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Windows installer This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed. Resolution DDP1.1sp1 –KB867460-x86.exe The upgrade patch cannot be installed by the Windows installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch. Windows installer The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed. Contact your support personnel for assistance. You will have to repair your COM+ catalog before installing TAC Vista 4.3. You can do this by following the steps in described in Microsoft’s Knowledge Base article 301919 http://support.microsoft.com/kb/301919/ Note: To do this you will have to have an installation CD for your OS (or have the files copied to your hard drive).

Issue Removing Trend Log before Upgrading to Vista 4.3 Environment Vista upgrade Cause During the addition of digital signatures to the log values, as required when upgrading to Vista 4.3, the PC may experience excessive demand of the processor and take a significant amount of time. Resolution If you do not require these trend log values you can follow these steps to avoid this potentially lengthy process. In the version of Vista that you are upgrading from create a full Vista backup by accessing the $Backup_FVB object found in you Operator Unit. Make sure that the "Include trend log files" selection is not checked before you start the backup. Upgrade to Vista 4.3 and specify a different database path then the one your old Vista database resides in. Start Vista Server and manually log in. Select "Restore Database" from the File menu in Vista Server. Browse to the backup file and specify the path you want to restore this database to. (The path to restored database must be different from the current Vista database path being used by Vista Server) Shutdown Vista Server and using Vista Server Setup change the database path to the directory you restored the backup into. Start Vista Server and the database will be upgraded without having to wait for the trend logs to get digital signatures. Once you have verified the upgrade completed made another backup of your database.  

Issue Using TOAD with Vista 4.3 Environment Vista 4.3 TOAD Cause The release notice for Vista 4.3 recommended the use of TOAD which is a free program that allows users to view and query SQL databases. This can be a very powerful tool to assist in database verification, exploration of the database for creating Crystal Reports, and running scripts. Resolution Warning: Care should be taken before making any changes to the SQL database since damage could break Vista To setup TOAD to work with the Vista database: Run Vista Server Setup and check the "SQL Server" tab and write down what is filled into the Instance and Database fields. Run TOAD_SS.exe. At the Server Login screen select "Add". Give your connection a name. Select "Use Connection String" and click "Build". Select "Microsoft OLE DB for SQL Server". Click "Next". In section "1" use the dropdown menu to select the Instance name found in Vista Server Setup. Typically the PC name or PC Name\TACVISTA. Select "Use Windows NT Integrated Security". In section "3" verify that "Select the database on the server" is selected and with the drop down menu choose the database name found in Vista Server Setup. Typically "taclogdata". Click "Test Connection" to verify it is working and click "Ok". Click "Ok" in the Data Link Properties window. Click "Ok" in the Add Registration window. Select the line your server was added to and click "Connect". You should now be connected to the server and you can use the Data Browser window to view the tables, views, procedures, and users of the database among other things. The SQL Editor window will allow you to run queries as well as other administrative tasks. Remember that all changes should be carefully considered before made to avoid breaking the database.  

Issue After using the STR-350/351 as an I/O module to a Xenta programmable controller and then using STR-350/351 LonMaker Plug-In the changes made in the Plug-in default back to previous settings Environment Vista LonMaker, NL-220 STR-350 Plugin Cause If the STR was added to the Menta application then the controller will continually update the STR with the settings programmed. Any changes made with the STR LonMaker Plug-In will then be overwritten. Resolution In order to use the STR 350/351 LonMaker Plug-In, the STR must not be set up in classic mode by adding it in the Menta application of the controller communicating with it. If the STR-350 has already been added to a Menta application it must be configured using the Menta application. Otherwise, the STR-350 should be removed from the Menta application before attempting to configure the STR-350 as a Lon node using the Plug-in.

Issue When attempting to create OP Trees for Xenta controllers, some public signals in the application do not appear in the OP/32 Configuration Tool. Environment Xenta OP OP/32 Configuration Tool Cause While Menta allows you to use both uppercase and lowercase module names, the OP/32 Configuration Tool is case sensitive and can only use one version of a particular module name. For example, if you refer to Air Handler 1 as both "AH1" and "ah1" modules in an application, the OP Tool will only list the points from either the capitalized module or the lowercase module; never both. Resolution To correct this issue and make the missing points visible in the OP Tool: Close the OP Tool Standardize the module names to the same case format To change module names: Select one or more blocks with the mouse When they are highlighted in green, right click and click on "Module" Type in the new module name and then click "OK". Save the application Re-open the OP Tool

Issue Commissioning i.LON 600 Routers Environment i.LON 600 LonMaker 3 Cause i.LON 600 routers require backwards compatibility and a configured IP port. Resolution To commission an i.LON 600 in LonMaker 3 the user needs to make sure that the following are done. When creating the channel in the Echelon LONWORKS/IP Configuration server the channel mode selected should be "Backward Compatible" so that it can communicate with computer hosting the LNS Server. A device needs to be added to the channel that represents the computer hosting the LNS Server. It will share the same IP address as the channel, but utilize port 1628 rather then 1629.  

Issue How can I avoid getting an asterisk  (*) on all my devices when adding a controller to an existing TAC Xenta group in the system plug-in. Environment Vista System Plugin Cause When you do the "Update TAC network" after adding a new controller a group is created and when a new group is created all devices have to be downloaded. Resolution If you use the "Update TAC Network" command (or button) the controller is added to a new group. You can move the controller to the group you want it to be in, download to the controllers in that group and it will work, but now all your other controllers will have * next to them telling you that they need to be downloaded. To avoid this drag and drop the new controller directly into the group you want it to be in. Now only the controllers in that group have the * and needs to be downloaded.

Issue Using Time Schedules in the Xenta 527 Environment Xenta 527 I/NET system I2V integration Cause Users should exercise caution when creating time schedule objects and pages in the Xenta 527. If a time schedule is created and directed at an I/NET point that already has a time schedule on the controller, the point value will be incorrect until the schedules synchronize. Due to the risk of improper results, possible harm to equipment in an HVAC environment, possible security breaches in a security environment, and the risk that if Ethernet communications fail the point will not operate according to the schedule it is recommended that time schedules in the 527 not be used with I/NET points. Resolution The I/NET time schedule object, which is created during the save file conversion in XBuilder, should be used . This object will direct you to a page that modifies the I/NET time schedule on the controller.  

Issue How can I give other users and SYSTEM the right to filter events in the Event viewer? Environment Vista Workstation Cause For a user to be able to filter events in the Event viewer it has to have at least authority level change (RWXD) on the $EVENTVIEW object. Resolution For more information on how to change authority on an object see Chapter 3 - Authority Levels for TAC Vista Workstation in the Administrating TAC Vista Workstation Manual.

Issue When adding a third-party controller to a Vista database, some SNVT values are not present in Vista. The unit commissions and functions properly in Lonmaker, but certain valid SNVTs are left out of the Vista database, such as nvoSpaceTemp on the Trane device. Environment Trane LCI-R rooftop unit Smart Controls SmartStat ST-35F LonMaker Vista Workstation Cause Some information in the XIF did not transfer properly to the Vista database. Resolution Locate the correct .xif file for the device Browse to the device in Vista Right click and select Properties. On the XIF information tab, select the button next to the xif file name and browse in the original .xif file. Refreshing your page values should now reveal all the valid SNVTs in the device.

Issue Using Lonmaker to replicate settings in a specific function block from one Lonworks unit to others of the same type Environment LonMaker LON Devices Cause It is very time-consuming to configure VAV controllers and other Lonworks units in large systems. Fortunately, it is possible to configure the settings in one controller and then replicate those settings to all of the other controllers. This can be accomplished by using "ResynchCPs" but that applies to all settings in a controller. Using this function can replicate the settings in only one function block. For example, maybe you want to change all of the temperature setpoints and heating configuration but not the duct area and other airflow settings. Resolution First, make sure that each controller in the Lonmaker drawing has a functional block of the same type, e.g. "VAV Controller." To quickly create multiple functional blocks, drop a functional block onto the drawing; in the dialog box, give the FB a name, and where it says "Number of FBs to Create," enter the number of VAV controllers in the subsystem. Use the plug-in or browser to configure the parameters in one of the controllers. Make sure the parameters get downloaded to the controller. Next, right-click on the functional block for that controller and select "Replicate Settings." Select the parameters that you want to copy and then click Next. Under "Target Subsystems," select the subsystems that contain the same type of controllers. Under "Target FB Selection" select "Matching FB Type", then click Next. It will show you a list of qualifying targets, including the current value and new value of the parameters. Highlight any settings you don't want to be changed and select remove. Click Finish to replicate the settings

Issue Can not open LonMaker database Error window pops up saying "Invalid parameters - LNS error #44" When you click on OK it pops up another window asking you to either attach or detach the network. Once this is done, it comes up with an NSS assigned error. Environment Windows 2003 server, with SP1 installed. Cause If you have Windows Terminal Server installed (used for remote desktop connections to the server) then LonMaker does not work. Resolution Fully uninstall Windows Terminal Server (you don't need the CD for this operation) and reboot. You can not just turn the service off in Windows, this has no effect at all.

Issue Access specific variables in the Xenta 511/527 via HTML. Product Line TAC Vista Environment Xenta 511 Xenta 527 HTML Cause View certain values inside the 511 without accessing a graphic page within the device. Resolution Individual variables can be accessed using HTML addresses in a 511/527 if you use the following address: https://x.x.x.x/sys/varaccess?Variable&UID=root,PW=root Where: x.x.x.x = IP address of the unit Variable = name of the variable being referenced UID = User Id PW = Password If you are already logged into the 511/527 or wish to use the address in a link page then leave off the &UID=x,PW=y part. In order to identify the name of the variables available, consult the SB_ProjectTree.gz which is a compressed XML file containing the project. It is located in the TargetImage\ConfigDb subdirectory of your project directory. Use the value field in the XML section for the signal you wish to reference. NOTE: This can not be done with a 527-NPR since it does not contain any of this information

Issue Will the type of SNVT binding affect the controller address table? Environment Vista LNS Network LonMaker NL-220 Cause Different types of SNVT bindings affect the entries made in the address tables of the sending and / or receiving devices. Resolution One to One Bindings The binding type (Acknowledged, Unacknowledged, or Repeated) has no effect on the address table entries. Instead the determining factor are the send and poll flags. The sending state on SNVT outputs causes the SNVT to update the signal it is bound to. The polling state on a SNVT input causes the SNVT to poll for values on a regular basis. The effect these signal flags have on the address tables are detailed below: Any one to one binding Sender Receiver   Poll No Poll Send Both Sender Only No Send Receiver Only Unbindable Group Bindings When creating group bindings the type of binding (Acknowledged, Unacknowledged, or Repeated) and the signal flags (Poll/Send) complicate the table greatly. However in situations where direct control of these signal flags is possible the effects on the address table is very simple. A group binding where the output is a Send signal and the inputs are Not Poll then one address table slot will be consumed by all members of the group (Both sender and receiver). This scenario is the default settings for inputs and outputs for SNVTs created by Menta. If the equipment being used is not configurable then the address table entries can become full very fast. Care should be taken if group bindings are used and it does not match the Send & No Poll defaults.

Issue How to service pin a Loytec L-IP. Environment Loytec L-IP Cause Commission a Loytec L-IP into a LNS network. Resolution The Loytec L-IP can be service pinned in one of two ways: If you have direct access to the router, press the status button to initiate a service pin. If you do not have direct access to the router, connect to the router via Ethernet to initiate a service pin. By entering the IP address of the router in a web browser you will reach the L-IP Device Info which has a button to send a service pin message.

Issue Re-using symbols library in Vista Environment TAC Vista IV OGC Graphics Editor Cause You can re-use your symbol library that you created in a Vista data base to avoid having to recreate symbols every time you start a new Vista db. After adding or editing symbols in the graphic editor, your changes are stored in the $tmp folder in your db as $symbol.sym. You can use this file or use the database generator to export the $Symbol file to your $wrk folder. Resolution To use a saved .SYM file Find the $symbol object in you database (in workstation) Right click and select properties. Click on the last line, a browse button should appear. Click on the browse button and browse in the saved .SYM file