Building Automation Knowledge Base

Notifications

Community

Notifications

Categories
Forums
Knowledge Center
Blogs
Ideas
Events & Webinars

Share Your Feedback – Help Us Improve Search on Community!
Please take a few minutes to participate in our Search Feedback Survey. Your insights will help us deliver the results you need faster and more accurately.
Click here to take the survey

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…

Search in

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

2029 Posts | First Used: 2018-09-06

Building Automation Knowledge Base

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 "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 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.

Issue Animations, gifs, updating values, hover overs or mouse event scripts work in Workstation but do not work in Webstation. Product Line TAC Vista Environment Vista Webstation TGML graphics Dynamic values Cause Various reasons can cause TGML graphics to not function the same in TAC Vista Webstation as in Workstation. Typical reasons can be: Using "Static TGML viewer" vs. "Dynamic TGML viewer". Under Static view, all animations are prohibited. Using unsupported script functions can cause animation to not work in Webstation. Sizes and the number of animated .GIF images used on a single TGML graphic page. Resolution Check if the Webstation is running under Dynamics view. Go to Start->All Programs->Schneider Electric->TAC Vista Web Applications -> Vista Web Setting. (For Vista 5.1.3 or prior, go to Start->All Programs->TAC->TAC Vista Web Applications -> Vista Web Setting instead.) Click on "Graphics/TGML Views" in the left panel. Make sure the TGML View is either “AutoDetect” or “Dynamics” in the right panel. If it is “Static”, click on the drop down manual and choose a different display viewer. Check if using any unsupported Java script. Please reference Vista Webstation unsupported TGML functions for more information. If a TGML graphic page contains many animated GIF images, it can cause the animation on that graphic page to run slow, discontinuously, or not run at all. The amount of animated GIF images that can be put on one single TGML graphic page various case by case. Therefore, the best way to test it is deleting all animated GIF images and add them back on one by one.

Issue The reason for TAC dummy nodes and the logic behind the number of dummy nodes created. Product Line TAC Vista Environment Vista NL220 LonMaker TAC Vista System Plug-In Cause TAC dummy nodes are added to Xenta groups automatically in the LNS network. The dummies are made after group bindings have been created. Resolution The TAC dummy nodes are created when group bindings are made. For more information about group bindings see Verifying Xenta Group Bindings in an LNS system. Vista requires that the TAC Group and the TAC Xenta group differ in the number of devices. If you only have one Xenta group in your system, TAC Vista System Plug-In will create a dummy device and use its tag_0 (also first row of the address table) in the group binding for the TAC Group. This will allow Vista to differentiate between the TAC and Xenta groups. Notice that in both LonMaker and NL220, this dummy node that is created to represent a second Xenta group appears to be located in the same Xenta Group as the rest of the controllers. This is fine, the system plug-in is not going to create a new group to put it in, just realize why the dummy node is there. Modules do not count in the group bindings therefore the example below only has three devices in Xenta group 1. Xenta Groups must consist of at least three Xenta devices. If you only have two Xentas in a Xenta group, TAC Vista System Plug-In will also use a dummy device, since a binding between just two devices is not considered a group binding. To create a group binding, a third device is needed. Consequently, you will need two dummy devices if you only have one Xenta in your Xenta group. Thus, if just one Xenta device exists in a single Xenta group, three dummy devices will be needed: one to separate the TAC group binding from the Xenta group binding and two more to form a Xenta group.

Issue Error messages appear in graphics that have worked in previous versions. Environment TAC Vista TGML graphics editor/ workstation graphics 5.1.8 and newer Cause There are a number of changes made in TGML in version 5.1.8, but one of the changes in the way we handle scripts being run when in a graphic when a link is invoked may cause errors. Resolution One of the commonly used menu-components invokes a link via a script within a script. Previously the scripts remained in the cache memory and all running functions were completed, but in 5.1.8 the cache is emptied as soon as a new graphic is invoked. In this case evt.stopPropagation() should be used to terminate any scripts that could potentially run after invoking a link, for example when using nested scripts. A fix has been posted on the Graphics Exchange that addresses this issue. This is not an official Schneider Electric fix and Schneider Electric takes no responsibility for issues arising from it's use (Go to Community Post).

Issue The Vista administrator user account (system manager) is created; however, that account does not have administrator rights such as add/edit/delete any user, cannot change time schedules, graphics, etc. Product Line TAC Vista Environment TAC Vista Workstation 5 Cause When adding a system manager account in Vista, that account also needs to be added into the administrator group ($Administrators). If the system manager account is not listed under the administrator group, it will not be able to behave as the administrator. Resolution Maker sure the user account is set as a “System manager” Log into Workstation as an administrator and click on the root project folder in the left panel, right click on the user account in the right panel, and then select property. Under “General/Authority level”, it should say “System manager”. If not, change to “System manager”. NOTE: If the textbox is grayed out, it means the current logged in account does not have the permission to make changes to that user account. Please read Cannot edit or delete a user account in TAC Workstation to add the control rights. If this articele fails also, please go to step 2. Click on the root project folder in the left panel, and right click on the “$Administrators” in the right panel, then select “Properties”. Under “Users”, all administrators should be listed here. Make sure the desired user account name is listed. If not, use “Add” function to add the user account. If the text box is grayed out, log in as one of the system manager account listed under “Users” to process this step. NOTE: If all system managers listed under “Users” are no longer available. Please contact product support to unlock the database.

Issue Unless the correct format is used when defining a dongle as locking property in https://schneider-electric.flexnetoperations.com web site when activating license, the license will not work. Product Line TAC Vista Environment Vista 5.x Cause Defining a dongle as locking property in schneider-electric.flexnetoperations.com web site when activating license. Resolution It is important that the format is entered in the following format: TAC_HL_ID=1234567890. If the "TAC_HL_ID=" part is not entered, it will not work, and you will need to rehost the licenses again, this time using the correct format as stated above. Complete instructions can be found in Rehosting a Vista 5 License on the FlexNet License Server.

Issue Necessary Accounts for DCOM and Firewall Security Settings. Product Line TAC Vista Environment TAC Vista Webstation TAC Vista Remote Workstation DCOM Configuration Cause DCOM Parameters must be set to allow for remote connectivity to the Vista Server. Resolution You will notice in the "Security Settings for MS Windows XP SP2 and MS Windows Server 2003 SP1" instructions that several changes are needed for the accounts "ANONYMOUS LOGON" and "Everyone". If these accounts do not exist, they must be created and set to allow local launch and remote activation permissions. See also Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET for an automatic DCOM utility.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

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

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

"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

Animations or other functionality work in Vista Workstation but not in Webstation

Purpose behind TAC dummy nodes

Difference in script handling since Vista 5.1.8

Vista administrator user account has no admin rights

Specifying Dongle ID when locking license to dongle in Vista 5

Necessary Accounts for DCOM and Firewall Security Settings

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!