Building Automation Knowledge Base

Issue Using STR-350 Bypass button as On/Off button in Classic Network Product Line TAC Vista Environment Vista STR-350 STR-351 Cause Sometimes on/off function is needed when using STR 350/351 to start or stop a device. Resolution Following the steps below to realize this function in Classic Network: Create a Menta file and Click "Add STR Module" in the Device Specification. In the Bits field of HVAC settings, change the value of the last 3 rd bits of the first line from "0" to "1". This bit is to switch the using Bypass button as on/off function on. Create an STRIN and STROUT module. Bind the STRIN to OccManCmd variable, while bind the STROUT to EffectOccup. Connect the STRIN to an real DO point to control the start/stop of device. But an calculation is needed because when the button is off, the value is 2 while the button is on, the value is 3 instead of simple 0/1. Also connect the STRIN to STROUT to make the output synchronize with the input, like the program below. You can also download the sample from here. For the application used in the LNS network, refer to the Using STR-350 Bypass button as On/Off button in LNS Network.

Issue TAC Vista SQL maintenance repeatedly fails. Not just once or twice, but on every attempt. Microsoft Management Studio View of error Vista Workstation view of error Environment TAC Vista 5.1.7 or newer. Cause The SQL maintenance feature was added to Vista in version 5.1.7, to regularly database defragment the database and prevent the follow-on effects of a fragmented database. This scheduled maintenance can fail for a number of reasons. Resolution Start by  taking a DSS writer server log using TACOS Tweak. Follow the steps below to do this. Goto the TAC Vista installation folder (C:\Program Files (x86)\Schneider Electric\TAC Vista 5.1.9 by default on 64-bit machines). Locate TacosTweak and double-click on it. Click on the "Category" drop-down box and select "DSS (Registry)". Locate the "DSS Server - Log Level" entry and increase the log level to "7" by entering the value in the value field and clicking the "Set" button. Locate the "DSS Server - Log file" entry and chose an appropriate path. Launch "TAC Vista Server Setup" and go to the SQL maintenance tab. Locate the "Run SQL Maintenance now" checkbox and check it. Click on "OK" or "Apply". Locate the DSS server log file and open it with a text viewer/editor. Search the log file for the following text "Maintenance Task - Starting" and check that the date time stamp is approximately when the "Run SQL Maintenance now" button was pressed. Examine the file carefully and follow the file line for line from this point until you reach "[ERROR] Fatal error : SQL Exception : Incorrect syntax near '('. NOTE: Contact Product Support Services if you are unable to interpret the log file or see another type of error than that described above. Once confirmed, launch Microsoft SQL Server Management Studio and follow the steps below: Locate the "taclogdata" database. Right-click on it and select "Properties"  Locate the "Options" tab and set the compatibilty level to SQL 2008 (or SQL 2005 if that is the installed version). Don't forget to set the DSS Server log level back to "5"!   A tool to simplify this process can be found here. Please note that this is not an official Schneider Electric utility.  

Issue How to place an order for more LNS credits to allow LNS plug-ins to work and to be able to commission more devices. Product Line TAC IA Series, TAC Vista Environment LonMaker NL220 LNS Cause There are two types of credits: Product specific credits like LonMaker and NL credits LNS credits   LNS LNS credits are assigned to the PC and when they reach zero, the LNS Server license goes into deficit mode. After 14 days the deficit mode will expire, at which time no LNS tools will be able to be used on that PC. To reverse the lockout, enough LNS credits must be ordered to cover the deficit and any additional nodes that need to be commissioned. Backing up, sharing, and restoring LNS databases can sometimes corrupt these LNS credits, which then prohibits you from launching any LNS plug-ins. For more help with corrupt LNS credits see Corrupted LNS Credits. LonMaker LonMaker credits are assigned to the PC. Both LNS and LonMaker credits are required, however when commissioning devices in LonMaker, LonMaker credits are consumed but LNS credits are not. Even though LNS credits are not consumed in LonMaker they are still necessary because certain LNS applications (i.e. TAC Vista System Plug-in) require them to operate. NL220 Each time a node is commissioned in NL220 it requires a NL credit and a LNS credit. NL credits are assigned to the NL220 dongle and can be used on other PCs in "MOVED" mode. LNS credits are also necessary in NL220 to operate certain LNS applications such as the TAC Vista System Plug-in.   To order more Echelon LonMaker credits see Ordering more Echelon LonMaker credits. To order more Newron NL220 credits see Ordering more Newron NL220 credits. Resolution To check the amount of LNS credits remaining on a PC go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard and look for Credits Available.   To order more LNS credits: Go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard In the box named Credit Order, type in how many credits to order, then click Next. Following the instructions at the top of the window, Click the Copy to Clipboard button to copy the PC key generated by LNS Server License Wizard. Click Cancel. Compose a new email and paste the PC key into the body of the email. Address the email to credits@echelon.com or your local Schneider Electric Buildings Business order department so they can place the order. Follow the instructions at the top of the email making sure to fill out all required fields. Once Echelon or the local Schneider Electric Buildings Business order department sends back an Application Key, go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard. Click next and paste the application key into the field titled "Application Key". Click Finish.

Issue When opening LonMaker the LonMaker Menu list is not shown in Visio. Product Line TAC Vista Environment Echelon LonMaker 3.xx Microsoft Visio 2002, 2003, 2007, 2010 Microsoft Windows XP SP3 Cause Echelon LonMaker was not installed with Administrator rights or some of the default security settings have been changed. Resolution Older versions of Visio - Check the File Paths and Security Settings Open up Microsoft Visio on its own. Go to Start > Programs > Microsoft Office > Microsoft Visio. (Do not open up Visio by opening up the LonMaker project) Go to the Tools menu > Options and then select the Advanced tab. Click the File Paths button. (For LonMaker 3.1, go to Tools > Options > File Paths) In the Add-ons field make sure that the file path starts with DRIVE:\LONWORKS_PATH\LonMaker. The default path is C:\LonWorks\LonMaker. The path in the Templates and Stencils fields should DRIVE:\LONWORKS_PATH\LonMaker\Visio. The default is C:\LonWorks\LonMaker\Visio. The next setting to check is the Macro Security. Go to the Tools menu > Options > and then select the Security tab. Make sure that all of the below options are selected. Enable Microsoft Visual Basic for Applications Enable Microsoft Visual Basic for Applications project creation Load Microsoft Visual Basic for Applications projects from text Enable COM add-ins Enable Automation events   Newer versions of Visio - Check the File Paths and Security Settings Open up Microsoft Visio on its own. Go to Start > All Programs > Microsoft Office > Microsoft Visio. (Do not open up Visio by opening up the LonMaker project) Select "Options" on the left hand side of the window. Click on the "Advanced" section and scroll down to the bottom. Verify that the "Enable Automation events" box is checked. Click on "File Locations..." In the Add-ons field make sure that the file path starts with DRIVE:\LONWORKS_PATH\LonMaker. The default path is C:\LonWorks\LonMaker. The path in the Templates and Stencils fields should be DRIVE:\LONWORKS_PATH\LonMaker\Visio. The default is C:\LonWorks\LonMaker\Visio. Uninstall LonMaker and reinstall with the administrator account used to log into Windows. The following articles have information about another problem that can cause the same issue: Visio menu not displaying properly after installing Lonmaker 3.1 with Visio 2002  Visio will open but LonMaker menu is missing from the toolbar, the features are unavailable, or Error: "unable to launch visio with file lonworks.vst"  There are two other things you may try before uninstalling, that have solved the issue in some cases: Right-click any toolbar, Choose Customize > Toolbars tab, Choose the Menu Bar, Choose Reset Remove all registrations in the Tools menu, click Options, and then on the Advanced tab, click File Paths.

Issue When using TAC Vista 5 Demo License and Site License at the same time, Vista returns “Your application was not able to obtain a license because the FLEXnet license server manager could not determine where to find the licensing data it needs. Please choose one of the following: Specify the License Server System Specify the License File Product Line TAC Vista Environment Vista 5.X.X with Site License and Demo License Cause Using Vista 5 Demo License concurrently with Site Licenses, or having an expired Demo License in the License File folder with Site License may cause Vista ignore the Site License or not fully read the Site License. Resolution Remove Demo License from the License File folder. Restart the computer. If the issue still exists, follow Switching from the Demo license to the site License in Vista 5.1.7 or older.

Issue Is it possible to see how many users are logged in to Webstation? Product Line TAC Vista Environment TAC Vista Webstation 5.1.X Cause The number of users logged into Webstation at one time is limited by the number of available licenses.  Need to have a way to monitor this resource. Resolution There is no built-in function in TAC Vista Webstation to see how many users are logged in at a certain time. The only way to see how many users are logged in at the same time is to use the License Server Webpage. There it is possible to see how many Webstation licenses are in use. To access the License Server webpage: Open a browser and type in localhost:8888 Open the "Dashboard" and click on "Concurrent" See also Using Lmtools in Windows Vista/7/Server 2008 for Windows Vista/7/Server 2008 OS.

Issue When downloading a programmable controller with the Vista system plug-in, the process fails and reports the Error 80041195, Info: Communication port not connected. NOTE: Error 80041195 has also been reported when performing a commence communication command in the Vista system plug-in. Product Line TAC Vista Environment Vista Server 5.1.5 Vista System Plug-In 5.1.5 Cause Vista Server 5.1.5 is not communicating to the LNS server properly Resolution Vista Server hotfix 14 addresses this error within Vista Server 5.1.5. Download TAC Vista Server 5.1.5 Hotfix 14 from The Exchange Download Center. Run the TACVista515HotFix51514.exe file. Reboot the machine. This error has also been observed If the PC is running a a 64-bit operating system which is not supported for LonMaker or NL220. See Echelon LonMaker and Newron NL220 on 64-bit operating systems for more information.

Issue Commission and download command on a controller beneath a Xenta Server in a Vista classic network fails. Error: Completion event-failure, Info: $Address Product Line TAC Vista Environment Vista Workstation Vista classic network Xenta Server Cause This error does not indicate an error with the addressing of the controller.  What it refers to is the reading of parameters from the controller in an attempt to commission and download.  The first parameter it tries to read is the address, and if that fails, the $Address indicates which portion it failed on.  Since $Address is first, this indicates a complete lack of communication with the controller. If this issue occurs with a freely programmable controller (Xenta 280/300/401) under a Xenta Server (Xenta 5/7/913) it may be due to the Xenta Server firmware version not matching the Vista Server version. Resolution Go to the controller and look at it.  The green LED on the front should be solid green. Physically inspect the wiring of the controller.  A shorted LON, for example, would cause this error.  Make sure all wires are terminated firmly. For DDCs under Xenta Servers: Please refer to Xenta Server firmware versus Vista Server versions for the Xenta Server compatibility matrix with Vista Server. If a Xenta Server's firmware version does not match the Vista Server version then either uninstall Vista Server and reinstall the correct version of Vista Server or reload the correct firmware version to the Xenta Server.

Issue The order of installation is dependent upon the SQL versions installed with Vista and I/NET. I/NET DBCreate does not open after installation is complete.  DBCreate application is not shown even though under Task Manager processes the application is active. Product Line TAC INET, TAC Vista Environment SQL MSDE Express Vista and I/NET Installed on the same PC Cause Vista and I/NET both use SQL databases for purposes of event and trend logging.  They must be installed in the correct order to coexist within the shared SQL installation. It can be confusing to know which software should be installed first on a certain installation because it is completely dependent upon both the I/NET versions and Vista versions.  Later versions are compliant with SQL 2005 Express while earlier versions must use SQL MSDE. Resolution If a previous installation has failed, it is best to start "fresh" before attempting a re-install. Removal of Vista instructions located here: How to uninstall and completely remove TAC Vista 4.3 to TAC Vista 4.5 Removal of I/NET instructions located here: Procedure for uninstalling I/NET Seven on a stand-alone host Empty Recycle Bin to remove evidence of previous installations.    Use the following guidelines to determine in which order to install I/NET and Vista: If the I/NET version is prior to 2.2.1, then I/NET must be installed before Vista, regardless of the Vista version. When prompted during the Vista installation, allow a new SQL instance on the existing SQL MSDE that was installed with I/NET.   If the Vista version is 4.3.0 through 5.0.0, and the I/NET version is 2.2.1 or higher, then Vista must be installed before I/NET. These versions of Vista use TAC Config and SQL MSDE. When prompted during the Vista installation, allow a new SQL instance on the existing SQL MSDE that was installed with I/NET.   If the Vista version is 5.0.1 through to 5.1.6, and the I/NET version is 2.2.1 or higher, it is recommended to install Vista before I/NET. These versions of Vista use SQL 2005 Express.  I/NET versions 2.2.1 and higher have an option to install SQL 2005 Express. When prompted during the I/NET installation, allow a new SQL instance on the existing SQL 2005 Express that was installed with Vista.   If the Vista version is 5.1.7 and above, and the I/NET version is 2.2.1 or higher, it is recommended to install Vista before I/NET The default installation of this version of Vista uses SQL 2008 R2 Express.  When prompted during the I/NET installation, select Default Instance of either MSDE or SQL 2005. (Note that if installing on Windows7 operating system, MSDE option is grayed out and cannot be selected, as it is not supported on Windows7)..   If the Vista version is 5.1.7, and the I/NET version is 2.4.0 or higher, you can choose either one to be installed first. If Vista is installed first, by default Vista will install SQL 2008 R2 Express SP1. But I/NET 2.4x fails to recognize the instance installed by Vista, while also fails to create a default instance. So after installed Vista, manually create a default instance for I/NET, and then install I/NET. Refer to Item 1 in How to Troubleshoot on DBCreate on how to create it; If I/NET is installed first, you can choose Custom Installation for SQL during the installation of Vista. You need to manually enter the SQL instance name, SQL username and password when installing I/NET SQL. If you don't know the instance name, there is a quicker way to identify it: Open DBCreate of I/NET, and you can see the SQL server name for I/NET. Just copy and paste it here. Then you can finish the installation. For Vista IV installation, the correct procedure can be found here: TAC Vista IV and Peripheral Software Installation Outline

Issue Receive error stating that a Menta "File object is locked by another application" when trying to open it for editing. Product Line TAC Vista Environment TAC Vista Menta Cause There are several potential causes of this error: The Menta (.mta) file is already open locally or on a remote machine. The current user does not have the appropriate authority to edit the file. Menta crashes while editing a file opened directly from the Server. Each subsequent attempt to launch the Menta editor from Workstation will result in this error. When a "standard" Menta file is being used and the user attempts to edit the Menta file locally. For more information about this scenario, please see "Read-only because object refers to a standard file" when editing Menta from Workstation. Resolution The following resolutions correspond to the causes listed above: If an instance of Menta already has the file open, whether on the local computer or on a remotely connected computer, then it must be closed before trying to open and edit that particular Menta file again. If the current Vista user has only "User" privileges or is otherwise limited from editing Menta then a user with the appropriate authority should log in to open the Menta file for editing. Shut down then restart Vista Server and Workstation if the error was caused by Menta crashing. See the link in Cause D above.

Issue Alarms stops coming into Vista from Xenta 280/300/401 in the Lonworks network under a Xenta 913 or a Xenta 701. Xenta 280/300/401 controller goes offline/online in Vista. Unable to disable an alarm from a Xenta 280/300/401 that are under a Xenta 913 running as Xenta Server in Vista. Product Line TAC Vista Environment TAC Vista TAC Xenta 913 TAC Xenta 701 TAC Xenta 401 TAC Xenta 301 TAC Xenta 302 TAC Xenta 281 TAC Xenta 282 TAC Xenta 283 Cause There is no support for adding Xenta 280/300/401 to the Lonworks network under a Xenta 913/Xenta 701 running as Xenta Servers in Vista (even though if it is possible to do it in the software). Resolution Use a different Xenta Server that supports adding programmable Xenta controllers in the Lonworks network. Please see the table in chapter 1.1 of the TAC Xenta Server - Networks Technical Manual or Xenta Server version 5.1.5 and after Major Features.

Issue Managing the address table in a Lonworks device Product Line EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment I/A Series MNL TAC Xenta Third-party LON devices Building Operation Automation Server Cause A LonWorks device contains an Address Table which will hold a maximum of 15 addresses. Once this table is full, all bindings will only be able to use the broadcast setting which is not desirable. A Xenta 200,300 or 400 controller will have its first 2 address tables used with TAG 0 and TAG 1 binding. This leaves only 13 addresses for user bindings not the 15 addresses like other LonWorks devices. Resolution ​When you create a binding in LonWorks, you decide its behavior by selecting a binding profile. You either select a binding profile, or you use the default profile. There are basically three types of binding profiles: Acknowledged profiles Unacknowledged profiles Broadcast profiles Using an Acknowledged profile will consume one of the 15 available address table addresses on both the sending and the receiving device. The Unacknowledged profiles will only use one Address on the sending device's address table. Broadcast binds do not use an address but are not recommended. Use an acknowledged binding profile when the sending device should receive an acknowledgment from the receiving device indicating that the value of the bound variable was successfully sent. Binding profile Transmit timer Retry count Acknowledged Profile 96 ms 3 Acknowledged, Tx tmr 256, 3 retries 256 ms 3 Acknowledged, Tx tmr 256, 5 retries 256 ms 5 Acknowledged, Tx tmr 1024, 5 retries 1024 ms 5 Be careful of creating large, acknowledged fan-out bindings because they generate a lot of traffic, especially if the device of one of the recipients is offline.  Use an unacknowledged binding profile when the sending device should not receive an acknowledgment from the receiving device. Use this type when the value being sent is not critical and is of low importance to the control logic. Binding profile Repeat timer Repeat count Unacknowledged Profile   0 Unacknowledged Repeated Profile 48 ms 3 Unacknowledged Repeated, 5 repeats 48 ms 5 Use a broadcast profile when you do not want to use up an entry in the address table. The device address table has 15 available entries for bindings but the first entry is a reserved broadcast entry that all broadcast bindings can share. Binding profile Repeat timer Repeat count Broadcast Profile   0 Broadcast Profile, 5 repeats 48 ms 5 If no binding profile is selected, a default profile is used: Point-to-point bindings use the Acknowledged profile as default. Fan-out bindings use the Unacknowledged Repeated profile as default. Building Operation uses the broadcast profile as default when the device address table has run out of entries. If a point-to-point binding is changed to a fan-out binding, the binding profile is automatically updated to an Unacknowledged Repeated profile. If a fan-out binding is changed to a point-to-point binding, the binding profile is automatically updated to an Acknowledged profile.  This and other information about lon bindings is available on the online help guide Using a Lon Binding in StruxureWare Building Operation More information on the different tables used by each LON device

Issue An error occurred while installing DSS: MSDTC 2 Product Line TAC Vista Environment DSS Installation MSDTC Cause Users that get the following error message when installing Vista ‘Error occurred when installing DSS’ can be caused by the MSDTC (Distributed Transaction Coordinator) not being able to start. In the service list Distributed Transaction Coordinator (MSDTC) is not started and it fails when you try to start it. Resolution Check the windows event log. If you see the following error events logged in the Application log:  Event Type: Error Event Source: MSDTC Event Category: LOG Event ID: 4163 Description: MS DTC log file not found. After ensuring that all Resource Managers coordinated by MS DTC have no indoubt transactions, please run msdtc -resetlog to create the log file. Event Type: Error Event Source: MSDTC Event Category: TM Event ID: 4185 Description: MS DTC Transaction Manager start failed. LogInit returned error 0x5. Follow the steps in http://support.microsoft.com/kb/916926 to fix the problem. For other possible causes for this problem see: An error occurred while installing DSS: MSDTC An error occurred while installing DSS: The account already exists An error occurred while installing DSS:COM+ installation corrupt An error occurred while installing DSS: Cannot Start Service

Issue "No license for LonWorks communication" - LonMaker Recovery Folder Product Line TAC Vista Environment Echelon LonMaker Cause Vista software detects the installation of commissioning tool for the LonWorks communication license. At times LonMaker will improperly shut down and store bad data in the Lm\Db\Database name\recovery folder. This invalid data will stop the LNS server from running properly. Resolution If using LonMaker and "No License for LonWorks Communication" error message appears: Shut down Vista software Open the drawing in LonMaker If it requests the contents of the recovery folder be removed, follow those instructions. Once the contents of the recovery folder are removed, open the drawing in LonMaker Launch Vista Server, and the license problem should be gone.  Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" error when using a non LE dongle "No license for LonWorks communication" error message in Classic Network "No license for LonWorks communication" Error in Windows 2008 Server X64 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue After the TAC Menta file has been downloaded all other IO modules operated normally but one IO module will not come online Product Line TAC Vista Environment Xenta401 XENTA301 XENTA281 Cause If the IO module that will not come online has IO points set up in it, then chances are one of the points is set up incorrectly. For example, it may be referencing a Universal Input, but in an Analog Output only IO controller. This is typically caused by changing the IO module from its original type. The TAC Menta was not updated correctly after the change and an analog input was left referencing an analog output in the new controller. Resolution Check all the points in the affected controller for correct and valid references. Once corrected download the controller. TAC Xenta I/O modules do not come online after a download from System Plug-In is a related article.

Issue "No license for LonWorks communication" error when using a non LE dongle. Product Line TAC Vista Environment Non LE dongle (LE= Limited Edition which has no Webstation or multiserver functionality) Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause One would normally expect this error message when trying to run Webstation server with a Vista LE license. If the system is not using a Vista LE dongle/license, but the error "No license for LonWorks communication" appears, then the problem may be in the Privilege Server service.   Resolution Shut down Vista Server and Workstation. Right click on My Computer and select Manage. Expand Services and Applications. Click on Services. Find the service Privilege Win32 Server. Right click on the service and select Stop. Right click on the service once more and select Start. Restart Vista Server and Workstation and verify that the error went away. Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" error message in Classic Network "No license for LonWorks communication" Error in Windows 2008 Server X64 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue Key information necessary to operate and install Vista OPC Server Product Line TAC Vista Environment Vista Server 5.1.x Vista OPC Server 1.6.1 Cause Following these guidelines and work arounds the proper installation and configuration of TAC Vista OPC Server can be achieved. Resolution Please reference the articles below depending on the situation.  After installing TAC Vista OPC server it does not show up as a Windows service: Proper license is required before installation OPC server for TAC Vista will not keep the login settings in the TAC Vista OPC Server setup: Login Settings require additional steps Installing and configuring Vista OPC Server: Step by Step installation and configuration steps Unable to access data on a Vista OPC Server that reside on Xenta Server (I/NET or 3rd Party protocols): Server address limitations

Issue Error states: "Ensure that Vista Server is started" when trying to log into TAC Vista Workstation. The server is started. Product Line TAC Vista Environment TAC Vista Workstation 4.2.5, 4.3.0-4.5.0, 5.0.0 and higher Microsoft Windows XP Service Pack 2 Cause Microsoft Windows XP Service Pack 2 has security changes/upgrades from previous service packs.  This affects the DCOM permissions that Vista Server relies on. a variety of other reason could result in an error in DCOM parameters in later operating systems. Resolution Vista 4.2.5 Apply settings described in this TPI to get TAC Vista to work properly. Vista 4.3.0-4.5.0 Apply settings described in this TPI to get TAC Vista to work properly. Vista 5.0.0 and higher Apply settings described in TAC Software Installation Manual available on The Exchange Download Center. This can be done using the DCOM Utility in Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET. Error Message: Ensure that Vista Server is started lists manual steps to access DCOM.

Issue After successfully downloading a Menta application directly through the serial connection, the pop-up window below is displayed:  tam32 No blueprint in TAC Xenta! Don't forget to download the network configuration if the TAC Xenta is to function in a network! Product Line TAC Vista Environment Directly connected Menta Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause The blueprint is also called an .NDB (network database) file.  It contains network information that allows the controller to communicate to other controllers or I/O modules.  When downloading a Menta application directly, this warning is displayed as a reminder that that necessary network information has not been included in the application-only download. Resolution If the controller is running stand-alone and no networked communication is required, then no further action is required.  The message is only a warning alerting the user to the fact that the NDB file has not been included in the download. If the controller needs network variables and I/O module communication, follow the direct download (most often done only for troubleshooting purposes) with a download from the front end Vista Workstation for classic networks Vista System Plug-In for LNS networks If no front end exists, but network communication is still required (most often for I/O modules), lonTool32 is a suitable work around for those rare instances.  See Using lontool32 to download a stand-alone controller.

Issue Cannot open a file from TAC Vista Webstation from a TGML graphic Environment Vista IV TGML Webstation graphics Workstation graphics File access Cause  The "OpenFile" command doesn't work in a web browser. Resolution For an alternative way of viewing the reports and other files, refer to this document on the Community: DOC-7604 Guideline on how to open the same file in both TAC Vista Workstation and TAC Vista Webstation. To achieve opening a PDF or DOC file from a TGML graphic both in TAC Vista Workstation and TAC Vista Webstation, typically in workstation there's no problem. Use the "OpenFile" button, and the file should open. "OpenFile" button function in Webstation is not the same.  The "OpenFile" command to open the document from a button in a TGML graphic doesn't work in a web browser.  To open a file from a dynamic TGML graphic in Webstation Define a "Hyperlink" in TAC Vista. Direct the hyperlink to a document located in the "C:\Inetpub\wwwroot" folder on the server. Call the hyperlink with http://ip_address/docName.   Typical graphic behavior Opening a PDF document: Can be viewed in Workstation. Can be viewed in Webstation, but will not open in a new window even defining target as _blank. Opening a DOC document: Can be viewed in Workstation, but opens an "extra" window which must be closed after viewing the document. Can be viewed in Webstation.