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 New laptops do not support hardware for Echelon PCC-10 cards Product Line TAC Vista Environment Laptop Computers without PC Card slots or with ExpressCard Slots Cause Some new Laptops do not come with a PC Card slot or have an ExpressCard Slot that does not fit the PCC-10 card Resolution If the PC does not have a PC or express card slot then use NIC-709 USB Lon Talk adaptor. These are available from Loytec. See the procedure for changing from a PCC-10 LTA to a NIC-709 LTA. If the PC has a express card slot, see Can a LON PCC-10 PCMCIA card work in a laptop with an express card slot? for a solution.

Issue Xenta 102-AX version 2.14 and prior will not honor nviSpaceTemp unless it is bound with a true SNVT binding. This can be an issue in a Vista classic scenario using a Xenta Server to do the connection in XBuilder. Product Line TAC Vista Environment Xenta 102-AX version 2.14 or prior Vista Classic Network Cause The Xenta 102-AX version 2.14 and prior requires a true SNVT binding on nviSpaceTemp from an LNS Management software (LonMaker, NL220). The controller does a check to see if there is a true bound value on the nviSpaceTemp and if it does not exist, it reverts to the hard-wired room temperature sensor. When using the Xenta 700, Xenta 500, or Xenta 900 the controller simply connects the desired temp value to nviSpacetemp via a connection object. This is not a true LNS binding and the controller WILL NOT honor the connected value. Resolution Upgrade the firmware of the Xenta 102-AX to version 2.16 or later. Firmware 2.16 allows the use connection objects in XBuilder to send a value to the nviSpaceTemp SNVT of a 102-AX. Download the latest Xenta 102-AX firmware Instructions on upgrading the firmware are located here: Upgrading a Xenta 102-AX to version 2.16 or later.

Issue Error: "Event Receiver Failed - Could not retrieve any events from the event log" Product Line TAC Vista Environment Replacement PC running Vista 4.5 Vista IV Cause This is typical of a <4.5 Vista installation where the original PC running Vista Server has failed. The replacement PC name has not been changed to match the original PC name. It could occur from a name change of the PC or Vista Server after TAC Vista installation. This can be the result of a failed installation of the TAC Vista Config which creates communication issues between SQL and Vista. Resolution Reinstall Vista making sure the PC has the proper name and follows the correct naming convention before you start installing. This will create new users including the proper PC name on the PC and in the SQL server. If the installation continues to fail, send Product Support all error messages along with a copy of the Windows Event Log. Failed to Read Event From Event Log Database - Vista IV may also be of interest.

Issue In a web graphic hosted on a Xenta Server, clicking to change a value displays the dialog momentarily, then it immediately disappears. Product Line TAC Vista Environment Xenta server Cause The Java version is too new or too old. Resolution Make sure The java versions installed have been tested against the installed Xenta version. A Compatibility Matrix can be found on The Exchange Download Center. Or see Software and Firmware compatibility matrix for older versions of the traditional product lines. If the wrong versions are installed, download the correct version and install it.

Issue Error "Critical file not copied! c:\~\PLAiLANGEng.dll" during installation of Privilege License software. Product Line TAC Vista Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause This error occurs when 'PLApiLangEng.dll' already exists from previous installation. Resolution Uninstall both the Privilege and TAC software Find the existing 'PLApiLangEng.dll' file and delete it (It will be replaced during the installation process). Install Privilege and TAC software again. Please refer to How to uninstall Privilege Administrator 2.01 software for detailed instructions to uninstall Privilege software.

Issue The Vista Remote workstation cannot request the license fro the vista server with the firewall on. If all the ports are opened the license works fine. Product Line TAC Vista Environment Windows 7 32-bit Vista 5.1.6 Cause Even though ports 135 and 27000 to 27009 are open Vista license will not work. The Vendor Daemon (TACLIC.exe) port is by default not specified, and is chosen by the operating system at run time. However, it is possible to specify the TCP/IP port number the daemon use in the license file. Windows 7 on some installations does not assign a port for TACLIC.exe causing this error. Resolution The solution is to manually setup ports for the operation of the license system. This can be done by editing the Vista License file. Open the lic file in a text editor Here is a sample of a standard license header lines. Please Do not delete this comment line. SERVER this_host TAC_HL_ID=608806830 VENDOR taclic USE_SERVER Here are the changes to fix ports for the license system: #Please Do not delete this comment line. SERVER this_host TAC_HL_ID=608806830 27000 VENDOR taclic port=1700 USE_SERVER This will setup up the LMGRD to use port 27000 and TACLIC.exe will use port 1700. See Setting the firewall port 135 for a Vista Server running on Windows 7 for information on how to open ports in Windows 7. You will need to select the ports you have defined in your lic file.

Issue Continuum / Vista / I/NET / StruxureWare etc will not connect to any of the controllers on the LAN when using a Windows 7 and above PC. Product Line Andover Continuum, EcoStruxure Building Operation, TAC INET, TAC Vista Environment I/NET 2.4x Continuum Vista StruxureWare Windows 7 8 8.1 10 Cause This is due to Microsoft improving their security in Windows 7 and above that will now block many types of connections across a network. Resolution To enable communications across the network; Disable all firewalls and any Anti-Virus software on the PC. (SE laptops, right click on McAfee shield, Quick settings and un-tick everything, this will temporarily disable the AV and firewall) Disable User Administrator Control (UAC) (As per Disabling administrator rights messages in Windows 7 OS and above) Re-install I/NET Seven / Continuum / Vista etc

Issue Vista licensing dongle has been lost or stolen from the site. Vista will not run without a valid license. Product Line TAC Vista Environment Vista Licensing Dongle Cause The user dongle has been lost, stolen, or is missing. Resolution You must contact Order Entry for a replacement dongle PN=000857510. Order Entry, Phone: 888-444-1311, E-mail: ccc.service@buildings.schneider-electric.com. See Vista Dongle Guide to get the old Dongle number. Call or email PSS when you receive the new Dongle with both Dongle numbers. PSS will then rehost the license to the new Dongle number. Note: Order Entry/Product Support will be able to assist in verifying which licenses were previously purchased for the site if you do not know.

Issue Unable to get a Dual FT Channel L-IP-33ECTBB to communicate after installing in LonMaker. Product Line TAC Vista Environment LonMaker Loytec L-IP Cause Using a "generic" router stencil in the LonMaker drawing as you would when installing a single FT channel L-IP will not work with the Dual FT Channel device. This is because of a virtual 1250 backbone internal to the Dual channel L-IP that the two FT channels hang on. Resolution To properly install a L-IP-33ECTB, use the stencil provided by Loytec. This can be downloaded via the following link: Loytec website Search for "shapes" and download the "LOYTEC Shapes Version 5.0.0" file. Also see How to Configure Lonworks Network Interfaces to Communicate on the IP to a Loytec L-IP Router using the Echelon driver.

Issue The LNS credits and the NL220 credits quantities do not match Product Line TAC Vista Environment NL-220 Cause Some LNS credits have been consumed while another NL220 dongle was used on the system. When you commission a device, both a NL credit and a LNS credit are consumed. When using another dongle on a given computer, (likely in “move” mode) it will consume a NL credits from it and a LNS credit from the computer. This can bee seen from the NL220 information bar. Resolution If the LNS credits are inferior, this means you are running in deficit. To fix this, you should order additional LNS credits to level up their quantity. When we deliver you credits, we send at the same time NL and LNS. This is why the dongle has to be confirmed on the computer when ordering credits and also why we highly recommend to commission devices only when the dongle is confirmed. Ordering more LNS credits is a link on how to order LNS credits.

Issue How Many Remote Workstations can be connected to TAC Vista Server using a DEMO LICENSE Product Line TAC Vista Environment TAC Vista 5.x.x Demo License Cause Need to know how many remote users can access a single TAC Vista server using a Demo License. Resolution There is no limitation number announced by the Schneider. Practically, if too many Remote Workstations connects to the TAC Vista Server, It will slow down the speed of the Server and for sure will get some un-expected errors will occur. And if the TAC Vista Server have many graphics and too many Remote Workstations trying to access the same graphics page all at a time, it should affect the performance. But it will not be a problem with 15-to-20 remote connections when the Server PC have a very good configuration. Note: If the Server PC having a high configuration and using the Windows XP the speed differ with the PC using Windows server 2003 or 2008 or Higher. Use "Demo TS_OK_" demo license, if the Vista Server accessing with Windows Remote Desktop Connection. Remote Workstations need to use individual "Demo TS_OK_" demo license file in each machine. Remember that when using the "Demo License" files, Vista does not work on "License Server". Related Articles: How many Remote Workstations can connect to a single TAC Vista Server? Monthly temporary (demo/evaluation) license files for Vista 5 'Unable to request license' message when using Demo license with Remote Workstation Windows Remote Desktop (RDP) is not supported by the TAC Vista Licensing system Remote Desktop Connection issues When Starting Vista Server

Issue Unable to view rooms with Screenmate. After logging in and typing a room number, Screenmate takes a long time searching for the room and eventually times out. Product Line TAC Vista Environment TAC Vista 5.1.X Screenmate 5.1.X Cause This may be caused by slow network communication if Vista is running on a number of networks on a node. Vista will check all nodes for the given Screenmate ID and this can take a long time if there are a lot of objects and/or nodes. Resolution To resolve this issue it is possible to activate a caching function that collects the names of all the available Screenmate objects on all the nodes and stores them in a cache file. This means that the next time a user tries to view a room Screenmate will check in the cached file instead of asking all nodes for their Screenmate objects. To activate this function do the following: Locate the web.config file for TAC Vista web By default this is in c:\inetpub\wwwroot\TACVistaWeb51X\ Open the file (with notepad) and locate the key TAC.WebStation.ScreenMate.CacheEnabled Change the value of this key to "True" and save the changes to the file. Create the cache file Open a web browser and type in Localhost/ScreenMate Try to browse to a room once logged into Screenmate. This will create the cache file. Check under C:\Windows\Temp and see that a file named ScreenMateCache.dat has been created. If the file isn't created: Temporarily delete the other Vista nodes in Vista workstation so that only the master is left. Rerun the steps above - this will create a file containing the local screenmate objects and speed the process up. Add the other TAC Vista nodes again and repeat the steps above shown under "Create the Cache File". The next time the process should be much quicker, once this file is created. If problems persist check the authority settings described in The ScreenMateCache.dat file is not created on a Windows 2008 server.

Issue Creating a backup file to download into the controller so it can be extracted at a later date if needed. Extracting and restoring a backup file from a Xenta Server. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment XBuilder 5.x.x Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause If the XBuilder project is not set up to send project backup file to target device, you will not be able to extract a backup in the future. On site technicians will be unable to service the XBuilder project if they do not have the original project stored on their PC. Resolution To create a backup to store in the Xenta Server When creating an XBuilder project, check the box titled “Send Project backup file to target device”. If space requirements are an issue, then this option may cause storage overruns. See The size of the generated project is xxxx KB, which exceeds the maximum size of 8192 KB. For an existing XBuilder project, on the menu bar go to Project > Settings… to access this feature. To extract a backed up project from a Xenta Server Connect to the Xenta Server on the 10Base-T port Verify ethernet communications (ping) Open XBuilder Go to Project > Get from Target...

Issue What if you need to send unique SNVTs to more than 13 controllers or groups from a Xenta base unit? Product Line TAC Vista Environment LNS System LON Devices LonMaker/NL220 Cause All devices with Neuron chips in them use an address table. This table holds the neuron addresses or group addresses of each device or group that receives a SNVT from it. That table only holds 15 entries and 2 of them are used in the base units for the TAC group and the Xenta group leaving only 13. Resolution If the signals are sent to a group that only occupies one entry in the address table of the sender and one in each receiver. If the binding is unacknowledged, one entry is taken in the sender for each node or group but not in the receivers. So what if you need a unique occupancy signal for 50 controllers? Or a unique temperature setpoint for them? A group binding will not do because that is one single value to the entire group. The Loytec L-Proxy communicates on Lon networks and is commissioned like other Lonworks devices but uses a proprietary chip set instead of a neuron. This allows its address table to contain 384 entries. It can also have up to 5 ports which can all be commissioned in the same network. So if you send all of your SNVTs from the base units to the L-Proxy (up to 125 of them from a 401), you can let the L-Proxy distribute them to the rest of the devices. Another benefit of that chipset is that the throughput is much greater than the neuron so it can handle such a load. Related Articles: Bind to more than 13 unique LON devices without running out of address table entries No more address table slots for a device involved in the attempted connection. (Subsystem: NS Connections, #15)

Issue Several Xenta 102-AX controllers need to have the CO 2 sensor shared among them in a LNS environment. Product Line TAC Vista Environment CO 2 (Carbon Dioxide) Xenta 102-AX nviCO2 nvoCO2sensor Cause Properly binding a CO 2 sensor output to multiple Xenta 102-AX VAVs. Resolution From the Xenta 102-AX VAV that is connected to the CO 2 sensor, create a binding from the UnivIn3Sense function block/nvoCO2sensor, to VAV_Controller function block/nviCO2 in the receiving Xenta 102-AX VAVs. It will also be necessary to set the send heart beats by following Values sent from a 102-AX via SNVT bindings are not making it to the receiving controller.

Issue When integrating a Integral DVR system Vista crashes Video does not work in Vista CCTV video loss in Vista Product Line Pelco, TAC Vista Environment Vista 5.1.3 Vista Integral DVR SDK v6.6.1.57 Integral DVR SDK v7.0.8 Cause Vista uses the same SDK as Controlpoint uses for an Integral DVR system, this mainly means that Vista SDK needs to be at the same versions as Controlpoint's SDK. A good example of this would be that Vista 5.1.3 use SDK v6.6.1.57 and Integral Digital sentry 7 use a newer version of SDK that is not compatible with SDK v6.6.1.57, a integration of this system then causes Vista to crash. An integration with Vista 5.1.3 would need Integral Digital Sentry 4.1/4.2. Please reference Vista Video Compatibility for more information. Vista 5.1.5 has SDK 7.0.8.0 and it appears that HD support was not included prior to SDK7.0.24.0 Resolution Make sure you have the correct version of Integral Digital version versus Vista version. 5.1.5 5.1.4 5.1.3 5.1.2 5.1.1 5.1.0 5.0.3 5.0.2 5.0.1 5.0.0 Integral Digital Sentry 4.1/4.2 X X X X X X Integral Digital Sentry 7 X X

Issue Unable to view a report in webstation. When trying to open the report object in webstation the message "This report is dynamic and cannot be opened from webstation". Environment TAC Vista 5.1.X TAC Vista Webstation 5.1.X Cause As the message implies, reports are dynamic objects that cannot be viewed in webstation. Workstation is considered an engineering environment where objects are created and manipulated, whereas Webstation is primarily a viewing interface. Resolution For an alternative way of viewing the reports after carrying out the steps below, refer to this document on the Community: DOC-7604 Follow the steps below to be able to view a report in webstation: 1. Create a report - in this example named "Report1". 2. Create a time Event object and set the appropriate interval eg. daily, weekly, monthly etc. 3. Create a Report Periodical in Vista. Link to your "Report1". 4. Link the Report periodical to your time event object (created in step 2). 5. Lastly, create a hyperlink to the location where you have saved the copy of the report.

Issue When importing an old database into a new version of Vista, right click on a Xenta Server and select "Edit" to open the Xbuilder project. (Change the version information in the property of Xenta Server. Refer to "Edit" is not available in the right-click menu for a Xenta Server in Vista Workstation.) The old XBuilder project will automatically be upgraded to match the new version of XBuilder. However, the content of the project sometimes will be incorrect after this conversion. Product Line TAC Vista Environment Vista Workstation XBuilder Cause The XBuilder version of old the database does not match the one of the new database. Resolution Install the old version of XBuilder. One PC can install several different versions of XBuilder. The standalone XBuilder installation file can be found on the Schneider Electric Exchange Extranet under "Engineering Tools" Keep the Vista Server and Workstation etc. at the newer version.

Issue When you select the option to view the properties of a Object nothing appears. Environment Vista 5.1.7 Cause A Remote Desktop session is connected at the same time as a local user. Resolution To allow the properties option to be displayed, log the Remote Desktop user off. The preferred option is to set the Remote desktop session to a single user session. Remote Desktop Protocol (RDP) / Remote Desktop Connection (RDC) and I/NET has more information on how to configure a single user setup.

Issue The space temperature (nvoSpaceTemp) is displaying an invalid or default value (either 621.81 degrees Fahrenheit or 327.67 degrees Celsius). In newer versions of Vista the value will display "Invalid Value". Product Line TAC Vista Environment Vista Workstation Xenta 104-A STR-150 LonMaker NL220 Cause The option to use the STR-150 wall module with display has not been selected. Resolution If using a Xenta controller with software older than version 1.2 see STR-150 Not Compatible With Software Version 1.1 Xenta 100 Series Controllers. Otherwise, there are two ways to correct the problem: Using the Xenta 104-A Plug-In Open the 104-A plug-in. Select the General tab. Verify that the "Enable wall module with display" box has been checked. Click Apply or OK. Using Vista Workstation In the tree menu find and open the Xenta 104-A. Open the "8030" object. Locate and double-click nciAppOptions. Verify that Bit 14 has been checked and click OK.

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

Echelon PCC-10 card does not fit in new Laptop PC Card slots

Xenta 102-AX version 2.14 and prior will not honor nviSpaceTemp unless it is bound with a true SNVT binding

Event Receiver Failed - Could not retrieve any events from the event log

Xenta graphic - Change setpoint popup disappears within a second

Error "Critical file not copied! c:\~\PLAiLANGEng.dll" during installation of Privilege License software

Vista Remote workstation cannot get license in Windows 7 with firewall on

Problem communicating across the LAN on Windows 7 and above PCs

Missing/Lost Vista 5 Licensing Dongle

Dual FT-10 Channel L-IP will not communicate in LonMaker

NL220 credit mismatch

How Many Remote Workstations can be connected to TAC Vista Server using a DEMO LICENSE

Unable to view rooms with Screenmate

XBuilder project backups stored in the Xenta Server controller

Send unique SNVTs to more than 13 controllers or groups

Sharing a CO2 sensor between Xenta 102-AX controllers

Vista crashes when integrating with an Integral DVR

Unable to view a report in webstation.

The content of XBuilder is not correct due to mismatch of the XBuilder version

Vista properties window not displaying on points when the properties option is selected

Reading Invalid or Default Space Temperature from Xenta 104-A When Using STR-150

Building Automation Knowledge Base

Related Forums

This is a heading