Notifications

We Value Your Feedback!
Could you please spare a few minutes to share your thoughts on Cloud Connected vs On-Premise Services. Your feedback can help us shape the future of services.
Learn more about the survey or Click here to Launch the survey
Schneider Electric Services Innovation Team!

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 How can multiple licenses work simultaneously in Vista 5? Product Line TAC Vista Environment Vista 5 Licensing LMTools Cause Licenses may have been purchased separately and either contain different features, or additional seats. The license server can read multiple licenses and serve them up appropriately. Resolution Option 1 - Use multiple .lic files Since the filenames are the same for all .lic files sent via schneider-electric.flexnetoperations.com, you must first rename the files Put them in the License Files folder Make sure the license server is pointing to that folder (not an individual file) Reboot or Stop/Start/Reread license server using the LMTools utility. Option 2 - Merge into one .lic file Complete instructions in Manually Consolidating License Files Open each license file using a text editor. Cut and paste the "Features" into one of the files (Do not copy the file "header") Place this file in the License Files folder Reboot or Stop/Start/Reread license server using the LMTools utility.

Issue If a customer's Vista PC crashes, how is the software recovered, and is it necessary purchase all software again? Product Line TAC Vista Environment TAC Vista Cause If a PC with Vista software installed crashes, all software needs to be reinstalled, and if necessary a rehost of licenses is required. The rehost procedure is covered in Rehosting a Vista 5 License on the FlexNet License Server. Resolution The TAC Vista 5.x software itself is free and available for download from The Exchange Download Center. If the software licenses are purchased once, they are still available and no repurchase is necessary. If licenses were locked to a hardware dongle, just reinstall the license file(s) again when installation is completed. If licenses were locked to a Host ID and Host ID is changed due to configuration changes on PC, you need to login to https://schneider-electric.flexnetoperations.com and rehost the licenses to the new Host ID.

Issue Is it possible to limit the number of Vista workstation instances that can be opened on a PC? Product Line TAC Vista Environment TAC Vista 5.1.X Cause On a site with a number of workstation and workstation remote it is possible that all licenses will be checked out by one user on one PC, if multiple instances are running, leaving no licenses available for other users in the network. Resolution It is possible to use a license options file to reserve licenses for specific users. In this way it is possible to guarantee that a license will be available for each user. There is also an option to set the maximum number of licenses a user can use. Click on the following link to open Controlling distribution of license modules in Vista 5which contains a link to the FlexNet Licensing User Guide.

Issue Steps to setup a NIC-IP for Vista Product Line TAC Vista Environment NIC-IP Cause Setting UP a NIC-IP Resolution 1. Download and install the latest NIC software. Here is a link to this site 2. Start the LConfig application. This is located in the LOYTEC Network Interfaces menu. 3. Select the NIC-IP/RNI tab. 4. Select the Assignment & Configure button. 5. The next popup screen will search for the NIC-IP. If your NIC-IP is powered up and plugged in to the network it should appear in this list. 6. Select the NIC-IP and then select the Configure button. 7. Setup the IP address, IP Netmask, IP Gateway and DNS servers if required. Select the OK and the device will write the new configuration to the NIC-IP 8. Take note of the Assignment and change if required. Press OK and the Assignment & Configure screen will close. 9 In the LConfig application select the Device from drop down list that matches the notes assignment from step 8. 10. Press the Test Device/Serial Number button to check for the correct setup of the NIC-IP. The return screen should look like this. 11.Close the LConfig application by selecting the OK button. 12. Start the Vista server and log into Vista workstation 13. Under the Vista server object add a new Device-communications Port - Loytec 14. Select the properties of the new Communication port and select the Network interface from the dropdown list. this should be the same interface noted in step 8. 15. You can the add Lonworks networks under the NIC-IP device. If your NIC-IP does not appear in the dropdown list, Configuring Loytec NIC in Vista discusses this related issue.

Issue How to check the amount of used memory in a TAC Menta/TAC Xenta application. Product Line TAC Vista Environment TAC Menta Xenta 281 Xenta 301 Xenta 401 Cause When programming applications for TAC Xenta, you may want to be able to check the size of your application, to verify that it can be downloaded to the device. Resolution To be able to check how much memory an application is using, the application needs to generated. In TAC Menta, edit mode: Select Option, Simulate to enter Simulate mode. In Simulate Mode, select Commands, Generate, to generate the application. To be able to check the Memory usage, you have to return to Edit mode, Select Options, Edit. Now you can check the Memory usage by selecting Options, Memory Usage... As this calculation is done on your PC, and not in the device, and that the memory in the TAC Xenta device is dynamic allocated, it is a recommendation to have at least 10% free memory in each category to avoid future problems. For more information about the Advanced button, please see TAC Menta Advanced Memory Usage: BPR Size Calculator.

Issue It is not possible to make any configurations or calibrations within a Xenta controller that will reflect on the STR-150. Product Line TAC Vista Environment STR-150 Vista Xenta 121 Xenta 104-A Cause Communication between any Xenta controller and STR-150 is only one-way. The STR-150 can communicate to the controller but the controller cannot communicate back to the STR-150. Resolution Any parameters that can be changed on the STR-150 must be changed at the stat itself. Complete information on the various available parameters can be found in STR-150 Manual Configuration. It is not possible to perform a calibration on the STR-150 stat in a way that will affect the readout of the STR-150 in a version prior to 1.4. The Xenta 104-A can have the space temperature calibrated within the application by changing nciTempOffset. However, when a version prior to 1.4 of the STR-150 is used with the Xenta 121 the space temperature cannot be calibrated. For more information see STR-150 Calibration Feature.

Issue From time to time TAC Vista Server stops communicating with LonWorks devices and needs to be restarted. Product Line TAC Vista Environment TAC Vista Server LonWorks Cause There can be various reasons for this. One of the reasons can be, that one or more devices is flooding TAC Vista Server with communication, and the communication finally stops. Among other things, this can be due to one or more TAC Xenta's suffering from the rare memory fault issue described in TAC Xenta 401 - Rare Memory Fault Issue - TPA-MALI-09-0011.01, or that the system program in the TAC Xenta device has become corrupt. To identify the issue, make a communications log as described in Start TAC Vista Communications Log, and open the log with the "TAC Vista Comm. Log Decoder". Filter on "C1" messages, and check if there's extensive communication from one or more devices. If that's the case, you have identified that file transfer loop is the issue. Resolution The first thing to try, is to update the system program in the Xenta. Follow article Download an .MOT file into a Xenta Programmable controller for instructions on how to do that. If that doesn't work, replace the Xenta device(s) causing the massive file transfer.

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

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

Use multiple license files simultaneously for Vista 5

How restore software after a Vista PC crashes

Limit the number of Vista workstation instances that can be opened on a PC

Configuring a NIC-IP to be used in Vista

Memory Usage in TAC Menta/TAC Xenta

STR-150 does not support full duplex communication with base unit

TAC Vista Server stops communicating with LonWorks devices

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

Building Automation Knowledge Base

Related Forums

This is a heading