Notifications

Ask Me About Webinar: Data Center Assets - Modeling, Cooling, and CFD Simulation
Join our 30-minute expert session on July 10, 2025 (9:00 AM & 5:00 PM CET), to explore Digital Twins, cooling simulations, and IT infrastructure modeling. Learn how to boost resiliency and plan power capacity effectively. Register now to secure your spot!

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Label: "tac vista"

View in: "Building Automation Knowledge Base" | Community

2045 Posts | First Used: 2018-09-06

Building Automation Knowledge Base

Issue Renaming a Vista Server. Product Line TAC Vista Environment Vista Server Cause The Vista Server name will default to the PC name where the database is created. To rename the server to any desired name of fewer than 40 characters. This can be customer-appropriate or more generic than an individual's PC name; follow the steps below. Resolution Shut down Vista Server Open Vista Server setup and navigate to the Vista Database tab. Enter the desired server name in the text field "Rename Vista Server to" Click OK Restart Vista Server. Within a few seconds, the server's name shown at the top of the window will be updated to reflect the new name. It will also show up in the folder view of the Vista Workstation. Note: Changing the Vista Server name after graphics have been created and bound will break the binding path for all points. To fix up the binding paths for all graphics at once, use Change References, as shown in Change all bind paths for all bindings on a TGML or OGC graphic at once.

Issue Which licenses are required when TAC Vista is used in a virtual environment? Environment TAC Vista Cause Running a TAC Vista system in a virtual environment. Resolution No special end user licenses are necessary. License requirements are the same as if run in regular environment. Also, please see: Problems installing Vista on virtual PC and Running Vista software on an emulated environment for more details on the subject of running TAC Vista in a virtual environment.

Issue Regional settings might differ when TAC Vista server runs as a service. Product Line TAC Vista Environment TAC Vista Server set to run as a service Cause If TAC Vista Server is configured to run as Windows service it might have different regional settings. This is because the TAC Vista server service needs to be configured to use a specific user account (See Registering/Unregistering TAC Vista Server as a Windows service). One common symptom would be that the date and Time stamp might have another format. Resolution To make sure that TAC Vista server is using the correct regional settings: Log on to the system once using the credential that TAC Vista server is configured to use Check the regional settings for this account.

Issue Need help with programming Need help to make graphic Installation questions Forum Environment BMS Security Video Cause A great way of getting help with various application programming and graphic making is to spread knowledge between all the great technician out there. A forum exist for this and people worldwide that works with SE Solution share their knowledge here. Resolution Please enter the forum by the link below. http://community.se.com/welcome

Issue When installing the TAC Vista OPC server it doesn't show up as a Windows service like it should. Product Line TAC Vista Environment TAC Vista OPC Server Cause A valid license for the TAC Vista OPC server must be installed before installing The OPC server. Resolution Uninstall the OPC software Install a valid license for the TAC Vista OPC server. Reinstall the OPC software For more OPC Server issues please see Vista OPC Server Installation and Known Issues.

Issue Vista locks up randomly and displays application crashes. Investigating the Windows Event log shows the following errors pointing to tacldv32.dll. For more information on Windows Event Log, see Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes. Faulting application tacos.exe, version 0.1.0.0, faulting module tacldv32.dll, version 1.0.0.1, fault address 0x00007310 Product Line TAC Vista Environment Vista Server LNS Communication Port Large LNS network, or many smaller LNS networks Orion Stack Cause The DLL file, tacldv32.dll, is responsible for managing communications through an LNS communication port. If that is being overwhelmed with information from too many devices on the port, this DLL will crash. If the number of networks is only one and the database size is reasonable then the problem can be caused by a corrupted and non functioning LNS database.See Also Echelon LNS Utilities LNS Database Validator. Resolution If the number of networks is high then LNS communication must be managed by an Orion Stack, or NIC-852. This does not utilize tacldv32.dll and will stop the application crashes. If the number of networks is low, but the size of the networks is quite large, then it is also advisable to allow the Orion Stack to manage communication and will prevent the application crashes. If the number of networks is low and they are not very sizeable, then ensure that LNS database is working properly independently of Vista Server. If it has problems, investigate the LNS problems further, looking for any errors that can be searched on other articles. *Note that if you receive the tacldv32.dll error and are currently using an Orion Stack or NIC-852. There is a problem with the Orion Stack or NIC-852 installation or configuration. Hovering the mouse over the Communication Port objects in the TAC Vista Workstation should produce a pop-up window stating "Loytec Port". If it says "LNS Port", there will still be a need for using tacldv32.dll resource.

Issue "invalid data on _schedule address_" error when downloading application Environment Xenta Programmables Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause This error can occur when the time schedule data has become corrupted in the Xenta programmable controller. Resolution To fix the controller either: Clear the MTA file by using the clear application process (see Xenta Controller Will Not Download / How to Clear the Xenta Application for more information) Download the MOT file and empty the application memory (see Instructions on how to download an .MOT file into a Xenta Programmable controller for more information).

Issue System alarm message, Physical device not defined/configured, in the alarm window. Product Line TAC Vista Environment TAC Vista (all versions) TAC Xenta programmable controllers Cause This message is displayed when there is a TAC Xenta 401/30x/28x that is attached to the physical network, but the name is not in the TAC Vista database. It is there to alert that there are unconfigured controllers on the network. Resolution Download to the controller from TAC Vista Remove the controller if it is not needed. For an alternative cause and resolution for the message, see Physical device not defined/configured.

Issue CO2 sensors have been installed on the VAV boxes that have a 0-10 volt output, but the Xenta 102-AX is limited to reading 0-5 volt output using the Universal Inputs on the controller. If replacing the sensors would be too costly and time consuming, this is a viable option that will allow you to drop the voltage output on the CO2 sensor using 1000 ohm resistors. Product Line TAC Vista, EcoStruxure Building Operation Environment 102-AX Cause CO2 sensors have been installed on the VAV boxes that have a 0-10 volt output but the 102-AX is limited to reading 0-5 volt output using the Universal Inputs on the controller. Resolution NOTE: It is recommended that the incorrect sensors be removed and replaced with new sensors that have the proper specifications to match the 102-AX capabilities. If the sensor replacement is not an option please follow the instructions below. Please see the image below: You will need (2) 1000 ohm (1k) resistors to complete this conversion. Wire one resistor directly to the output wire of the CO2 sensor Land that resistor to U3 on the 102-AX Jump a second resistor from U3 over to M on the 102-AX Land the other output wire from your CO2 sensor on M with the jumped resistor Also see Using a 4-20mA CO2 sensor with a Xenta 102-AX to configure the Xenta 102-AX to accept a 4-20mA CO 2 sensor input on Universal Input 3.

Issue A Macro comes installed in the default directories with Menta. This macro will create a PWM signal that can be used for a variety of purposes in Menta. It will not, however, drive most industry-standard PWM hardwired actuators. For information on this, see Pulse Width Modulated (PWM) outputs in Menta. Product Line TAC Vista Environment Menta PWM actuator Cause Creating an a pulse width modulated output. Resolution Go to Program Files > TAC Menta > Library > Macro Block Library > Miscellaneous > Function > PWM.aut and PWM.doc These two files will give you a PWM function for Menta and an explanation. In simulation mode it will appear that the PWM increments at very crude levels but when the application is downloaded the processor actually runs at less than 1 second increments. Download this application to a controller and connect up a transducer and vary the control signal to be comfortable with the performance. Use a PVR block to generate a manually controlled signal.

Issue Configuring the Xenta 102-AX to accept a 4-20mA CO₂ sensor input on Universal Input 3. A negative value is required on the CO₂ offset value, but it is not possible to enter a negative value. Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta 102-AX 4-20mA output CO₂ sensor Cause The Xenta 102-AX universal inputs are designed to work with a 0-5V input. The best option is to always buy a CO₂ sensor that is compatible. However, if 4-20mA CO₂ sensors have already been purchased and installed, they can be made to work. Resolution In this example, a 4-20mA CO₂ sensor with a 0-2000ppm range is assumed. In the Xenta 102-AX Plug-In > Hardware Configuration Tab, set Input 3 Selection to CO₂ Sensor Wire a 250Ω resistor across U3 and M. This converts the 4-20mA signal to 1-5V. In Vista Workstation, navigate to the 102-AX > UnivIn3_Sense. Open SCPToffsetCO2. This value needs to be -500, but negative values cannot be entered. To get around this: Change Value to 0 Change Scaling > Offset to 500. This alters the display of the offset value. Click OK. Open SCPToffsetCO2 a second time. The value is still 0, but it is being displayed as 500, due to the scaling offset. Change the value to 0 (because of the offset, 0 represents -500). Click OK Open SCPTgain. Set multiplier to 2444 Set divisor to 1000 Click OK. This value comes from 2000 (range of sensor) + 500 (offset) / 1023 Note: An input of 0V (a sensor that has not been wired yet) will result in an nvoCO2sensor value of 65535 (invalid). Also see Using a 0-10 volt CO2 sensor with a Xenta 102-AX to configure the Xenta 102-AX to accept a 0-10 volt CO₂ sensor input on Universal Input 3.

Issue A multi-port router can be represented in a LonMaker drawing using several LonMaker Basic Shapes routers if the internal structure of the L-IP is understood. Alternatively, Loytec provides a stencil library of their routers that can be used. Product Line TAC Vista Environment LonMaker Visio Loytec L-IP routers L-IP-3ECT, L-IP-1ECT, L-IP-33, L-IP-3333, LS-13333, LS-11333, LS-13300 LS-33300, LS-33, LS-13, LS-11 Cause The LonMaker Basic Shapes router only represents a single port router (near side/far side). To represent the 2, 3, or 4 port L-IP routers requires multiple basic routers with different channel types, or one of the device templates from the Loytec Shapes stencil library. Resolution Download the latest Loytec Shapes 5.0 stencil library here. Extract the contents of the .zip file Move the LoytecShapes.vss files to C:\LonWorks\LonMaker\Visio Note: This is assuming that LonMaker is installed at the default location on the C: drive Start LonMaker Go to File > Stencils > LoytecShapes Select the router part number that matches the physical device. The appropriate channels for the router will be added along with the shape. Each port can now be commissioned separately. See also How to Configure Lonworks Network Interfaces to Communicate on the IP to a Loytec L-IP Router using the Echelon driver for more information.

Issue Stand-alone Vista 5 applications and Licensing Product Line TAC Vista Environment LMGRD Menta Save Menta View Demo Vista 5.x Cause No license found lc_checkout Failed: Network connect to THIS_HOST failed. The license file indicates THIS_HOST, and the server is not running on this host. Resolution Running Menta, Xbuilder or any of the Vista Applications as a "stand-alone" application i.e. no Vista Server/Workstation, requires a download of the License Server from Exchange Online. Navigate to Product Zone > TAC Vista > Vista Software > TAC Vista 5.0.X > Downloads. Ensure the version matches (5.0X) the version of Vista installed. For instruction set for licensing a Vista Software Entitlement: See How to Host a Vista Site License. Ensure the license is placed in C:\Program Files\TAC(Schneider Electric)\License Files folder. Launch the licensed Vista software of your choice, typically Menta or Xbuilder. When prompted, select "Use a License Server" option. Specify the Computer name that the server exists on, typically the Local Computer Name, or "localhost". To assist in troubleshooting additional Licensing problems: See [Video] Vista 5 Macrovision/Flexnet Licensing: Lmtools diagnostic utility overview See License troubleshooting in Vista 5.1.8 or greater See TAC Vista 5.0 to 5.1.7 license does not work after installation

Issue IIS is a Microsoft product that is included on your typical Microsoft OS software but is not active by default. Product Line TAC Vista Environment Webstation Windows 7 Windows Vista Cause Webstation requires for IIS to be active in your OS before you complete the installation of Webstation. Resolution Follow these steps to initiate your IIS service in Windows 7 or Windows Vista. How to Activate IIS 7: To open the Windows Features dialog box, click Start, and then click Control Panel. In the Control Panel, click Programs. Click Turn Windows features on or off. You may receive the Windows Security warning. Click Allow to continue. The Windows Features dialog box is displayed. Expand Internet Information Services. Additional categories of IIS features are displayed. Select Internet Information Services to choose the default features for installation. Expand the additional categories displayed, and select any additional features you want to install, such as Web Management Tools. Click OK to start installation. The progress indicator appears. When the installation completes, the Windows Features dialog box closes, and the Control Panel is displayed. IIS 7 is now installed with a default configuration on Windows Vista or Windows 7. To confirm that the installation succeeded, type the following URL into your browser, http://localhost Use Internet Information Services Manager to manage and configure IIS. To open IIS Manager, click Start, type inetmgr in the Search Programs and Files box, and then press ENTER. See Problems installing Vista Webstation 5.1.5 or newer for more information on configuring Webstation.

Issue Get error message "OPC communication error" when trying to view Vista OPC server objects in OPC tool. Product Line TAC Vista Environment TAC Vista 5.1.X TAC Vista OPC server 1.6.1 Cause Incorrect version installed or DCOM settings. Resolution Confirm which version of Vista OPC server is installed. Go to control panel\add remove programs and double check that it is version 1.6.1. that is installed. Confirm that OPC server setup account settings aren't being saved. Go to Start\Programs\Schneider Electric\TAC Vista OPC server\Tac OPC Server setup. Under Login to TAC Vista server, change to Login using the following TAC Vista account and fill in the appropriate user details. Click OK and close the dialogue. Re-open the TAC OPC server setup dialogue and see if the account details added in b are still there. If so then there is probably a problem with DCOM settings (see TAC Vista OPC Server Technical Manual). If the option Login using the windows account which is running the TAC Vista OPC server is re-selected TAC Vista OPC server 1.6.0 must first be installed according to OPC server for TAC Vista will not keep the login settings in the TAC Vista OPC Server setup.

Issue "No license for LonWorks communication" Error when starting Workstation. Product Line TAC Vista Environment Windows 2008 Server X64 TAC Vista 5.1.5 Cause Windows Server is member of a domain. Configure the TAC Vista Server to run as a service, with a local user set as administrator to logon. Results in "No license for LonWorks communication" when starting Workstation. If starting the service with a domain user or local system, it works. Resolution Windows Security Policy This may have something to do with UAC (User Account Control) in Windows. The user that launches TAC Vista was already as a local administrator, but it seems that a log out with the user, log in with a local user, and log back in with a domain user is necessary for some policies to be set. Licensing Registry The Vista licensing requires registry information on where to find a license file. This registry key is found in the following location: HKEY_CURRENT_USER\Software\FLEXlm License Manager\TACLIC_LICENSE_FILE If the user has not been logged in and configured to run Vista software, this key might be missing or misconfigured. Ensure that it has a proper value by launching Vista Workstation or running the TAC License Setup. Log in with the user that will run the TACOS service and run the License Server Setup application to ensure the correct file path is defined in the Registry. 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" - LonMaker Recovery Folder "No license for LonWorks communication" error message in Classic Network "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue Is there any way to get the Xenta Server trend log data without TAC Vista? How to get the Xenta Server trend log values from the web interface How to e-mail the Xenta Server trend log values Product Line Satchwell MicroNet, TAC Vista Environment TAC Xenta Server TAC Xenta 511, 527, 555 TAC Xenta 711, 731 Cause The TAC Xenta Server is installed standalone and TAC Vista can not be used to view or save the trend logs. However if you want to collect and store data from multiple trend logs on a regular basis we do strongly recommend using TAC Vista. Resolution There are two ways to get the trend log data from a Xenta Server (except for TAC Vista): 1. Manually copy the trend log values from the Xenta Server web interface In XBuilder, create a trend log page and drag the trend log to it Log in to the web interface and go to the trend log page Right click the trend log signal name and choose "view values" Copy/paste the values to for example Excel. 2. Forwarding the trend log data as an e-mail First make sure that the SMTP settings in XBuilder are correct. For troubleshooting on this, see Troubleshooting sending emails from a Xenta Server Create a receiver group and define one or more e-mail addresses to receive the trend log data. Highlight the trend log. Under Log Data Transfer Settings, click the Receiver Group box, and select the Receiver Group list. In the Subject box, type a suitable subject. If desired, also type a suitable text in the Body box. In the Log Events Included box, click Yes to attach log events to the e-mail message. You must also specify when the log data is forwarded. For this, create a time object which you drag to the "send data" signal on the trend log. When the trend log data is forwarded, the receiver group e-mail addresses will receive the trendlog data as an attached .log file. For more information, see chapter 8.2.2. in the TAC Xenta Server – Web Server, Technical Manual

Issue When trying to view values in a Classic Network, "[No license for LonWorks communication]" message shows up in the Value tab and the alarm window. Product Line TAC Vista Environment Vista Classic Network Cause Though you are using Classic network, it's still using LON standards. You still need the license for TAC Vista Server. If the Server license is missing or invalid, you will get this kind of message. Resolution Check your license file and make sure you have the server license included. The server license should look something like listed below: INCREMENT Vista.Server taclic 5.1 permanent 1 ISSUER=TAC \ If you do not have the line above, it means you do not have the proper license for TAC Vista server. Thus, you get the error message saying "No license for LonWorks communication." The solution is to purchase the TAC Vista Server license, or use the demo license or an engineering dongle. 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" - LonMaker Recovery Folder "No license for LonWorks communication" Error in Windows 2008 Server X64 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue When attempting to update Vista Database in Vista System Plug-In, there is a failure producing the error "Update Vista database failed". Product Line TAC Vista Environment NL220 LonMaker Vista System Plug-In Cause There are multiple causes for this error including LonWorks Network name not matching, signal names in Menta have too many characters, the use of an invalid alarm controller object in a Menta alarm block, and orphaned/unnecessary constants left in the Menta constants table. Resolution LonWorks Network name does not match If the LonWorks Network name in vista does not match the name in the system plug-in then the update will fail. In Workstation, right click on the LNS Network object Rename the LonWorks Network to match the name in the LNS side of the Vista System Plug-In. *If this occurs during the addition of a LNS port into a Vista database with an existing LNS port, ensure each LNS port is using a unique name. Insufficient Vista user account privilege An update to the Vista database cannot be performed if not logged in with an administrator level user account. Too many characters in a Menta point name If there is a signal name that is longer than 20 characters it can cause the Menta file to fail to update to the Vista server. Invalid alarm controller object If there is a Menta alarm block that is referencing an alarm controller object using a $ (other than the default $Alr_Cntrl) it can cause the update to fail. TAC Vista will try to add the object even though objects with $ can not be added. Orphaned or Unnecessary constants For more information on this cause and how to correct it, see Updating the Vista Database fails when trying to transfer a specific MTA object.

Issue Is it possible to get a XIF from Lonmaker when you have commissioned it by "upload" from device? Product Line TAC Vista Environment TAC Vista Toolpack TAC Vista Server LonMaker Cause If you don't have the XIF you can upload from the device in Lonmaker. Resolution There is no way to get the XIF from LonMaker but the system plug-in will create a new XIF when you add the device to the TAC Vista db. Refer to SNVTs, SCPTs, or Module Names are missing from Vista after device is added to database from System Plug-in. Compare XIF stored in Vista for instructions on how to locate the XIF generated by the system plugin.

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

Rename a Vista Server

TAC Vista end user licenses in virtual environment.

Regional settings might differ when TAC Vista server runs as a service

BMS Application assistance

After installing TAC Vista OPC server it does not show up as a Windows service

Vista lock-up caused by tacldv32.dll crash

"invalid data on _schedule address_" error when downloading application

System alarm message, Physical device not defined/configured

Using a 0-10 volt CO2 sensor with a Xenta 102-AX

Create an internal Pulse Width Modulated (PWM) signal in Menta

Using a 4-20mA CO2 sensor with a Xenta 102-AX

Representing a Loytec L-IP multi-port router in LonMaker

Stand-alone Licensing for Vista 5 Applications

How to activate IIS on Windows Vista and Windows 7

Error "OPC communication error" when trying to view Vista OPC server objects in OPC tool

"No license for LonWorks communication" Error in Windows 2008 Server X64

Receiving Xenta Server trend log data without TAC Vista

"No license for LonWorks communication" error message in Classic Network

"Update Vista database failed" Error in Vista System Plug-In

Is it possible to get a XIF from Lonmaker

Building Automation Knowledge Base

Related Forums

Welcome!