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 When commissioning I/A MNL800 controller in LonMaker LNS network management tool, an error will happen: One or more devices failed to update successfully, due to the following problem: "A device encountered an operational or messaging error while its configuration was being updated. (Subsystem: NS, #4031)" Product Line TAC IA Series, TAC Vista Environment Vista I/A MNL800 LonMaker Cause The issue is possibly due to more than one MNL800 controllers in the LonWorks network have the same Program ID defined in the WPT that causes the commissioning failed. Resolution Open the program of the MNL800 in WPT, right click in the blank place and choose Hardware Wizard. Click Next and modify the Program ID so that each MNL800 has unique program ID. Then it will be fine to commission them in LonMaker. There is also another method to deal with this issue. Please refer to Error: NS #4031 lcaErrNsUpdateFuncError A device encountered an operational or messaging error while its configuration was being updated (Subsystem: NS, #4031).

Issue After purchasing Webstation for a site, it still will not work even though the license is being read by LM Tools Product Line TAC Vista Environment Vista 5 Webstation Licensing LM Tools Cause When adding Webstation to an existing network it important to know if this was a Vista 5 "Stand-Alone" license or a "Full" version. Stand-Alone Vista will not allow any connectivity via IP. The needed license feature that comes in the Full version is "Vista.Server.Network". This can be verified by opening the site license in a text editor such as Notepad. Resolution Upgrade the site to a Full Vista license that contains the needed Vista.Server.Network feature. This will allow the Webstation to connect to Vista Server. A Demo license can be used in the interim until a Vista Upgrade License can be purchased, entitled and installed on the site. More information can be found in The Vista.Server.WebApps.Access license is missing.

Issue SNVTs that have been directly connected to a Menta application are not being updated. The value of the SNVT is not the same as the value in the corresponding Menta application. Product Line TAC Vista Environment Vista 5.1.7 Xenta 700 series Cause The Menta application is running too fast and sending to many requests out to the LonWorks network. You can see that the LonWorks network is running at very high levels if you use a LonWorks protocol analyzer. For example. 20 SNVTs are directly connected to RI in a Menta application running at Medium/Fast (500ms cycle) This would mean that every 500 ms 20 request would be processed to the LonWorks network. The 731 can only process around 15 request per second. The above example would be requesting 40 samples per second. Resolution The best solution for this problem is to use the connection object to connect SNVTs into Menta. Here is a link to User friendly way to make connections in Xbuilder for connection objects. The transfer rate can then be modified to slow down the LonWorks request through the 731. In the default setting for a connection object the transfer period is 10 seconds. To help with network request this time can be modified to prime numbers or realistic values for you application.

Issue When opening a Xenta Server (Xenta 5/7/913) trend log, it will display estimated value for a constant period of time. For example: A trend log trends room temperature every 30 minutes. An operator opens the trend log at 9AM, the trend log displays all the trend log values fine till 8AM. All values after 8AM before 9AM display as estimated value. Open the trend log again at 9:30AM, estimated values start at 8:30AM. Product Line TAC Vista Environment Xenta Server (Xenta 511, Xenta 527, Xenta 701, Xenta 711, Xenta 913) Cause Estimated value in trend log can have various causes. If it is always a constant period of time, it could be caused by the wrong time setting in Xenta Servers (most likely is the wrong day light saving minutes setting). Daylight saying time in a Xenta Server is set to 60 minutes by default. If Vista Server PC is set to not using daylight saying, then Xenta trend will not display the last hour trend since it believe the time is not reached yet. Resolution Please refer to Xenta Servers and Time Synchronization for step by step guide of manually setting up the Xenta Server's time. After the time setting change has been made, Xenta Server will reboot itself. When the reboot finishes, reopen the trend log and the issue should be solved.

Issue Privilege software version 2.01 crashes during installation on Windows XP. Product Line TAC Vista Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause Privilege Administrator Incompatibility with XP Resolution Uninstall any previous Privilege Administrator (Please see How to uninstall Privilege Administrator 2.01 software for details on uninstalling the software) Download "Privilege Windows XP crash hotfix" (PS202.zip) Install PS202 by running setup.bat. Install Privilege Administrator 2.01 again.

Issue Errors in Vista Workstation alarm window: "Failed to execute report XXXXX-YYYY, Error in "DDE Execute" command[27]" "Warning logged in B0WARLOG.TXT on node XXXXXX" Contents of B0WARLOG.TXT: "Could not open report XXXXX-YYYY, hRes=[-2147467261]Invalid pointer" Product Line TAC Vista Environment Vista Server Microsoft Windows 7 Microsoft Windows Server 2008 Cause Vista Server does not support running as a service under the local system or interactive user account. A PC account that has local administrator rights must be used to run Vista Server. Resolution Follow the registration instructions for Vista Server in Registering/Unregistering TAC Vista Server as a Windows service when registering TACOS.exe as a service.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue When Vista Server is started the startup process just hangs. Product Line TAC Vista Environment Vista Server 5.x Cause There can be several causes for this issue. A common issue with this situation is the Vista database has been restored from site without the Lonworks NL220 or LonMaker database. When the Vista server is opened it is unable to contact the Lonworks database and repeated attempts cause the server to hang. Resolution It is possible to prevent the Vista server communications as well as other parts of the Vista server communication. Reference TAC Vista dll Manager to download a tool from the Community that will allow you to disable DLL files and find the cause of the issue. If you are seeing the scenario as stated in the above cause, you would disable Option "10: Network communication" and "11: Field bus communication" in this tool then select the Update button You must remember to enable the options once you have finished with the site database. If you forget to do this the Vista server will not function correctly when you want to run a live database.

Issue Launching Menta by opening an MTA file causes a Buffer Overrun Error The error message: "Buffer overrun detected ... A buffer overrun has been detected which has corrupted the program's internal state. The program cannot safely continue execution and must now be terminated." Product Line TAC Vista Environment Menta Cause Menta's buffer for opening files is limited; if the file you are trying to open by double-clicking has a very long path (of 142+ characters), you will receive the Microsoft Visual C++ Runtime Library Buffer Overrun error message. Resolution Work arounds: Shorten the path to the Menta file. If it is possible to decrease the number of subdirectories or the length of the directory names to make the total path length less than 142 characters, this will correct the problem. Note: Never modify a Menta file name within Windows; only change Menta file names using the Menta application by using "Save As..." from the File menu. (See "Cannot open file" error when opening a Menta file for resolution if this occurs.) If it is not possible or practical to change the path to the file, files with long paths can still be opened by launching Menta using the Start Menu or a desktop icon. Select File > Open and browse to the Menta file, then click "Open". Opening the file via this method will expand the path length limitation to over 200 characters.

Issue Cannot attach the Network interface to Lonmaker database when the Vista Server (Tacos) is started as a service. The error message is that the 'NIC interface is not connected'. Product Line TAC Vista Environment Echelon Lonmaker 3.1 Echelon Lonmaker 3.2 TAC Vista (all versions) Cause When updating Lonmaker and Vista databases as applications, it is important that Lonmaker be started first. Failure to do so can result in issues like this when Vista is reconfigured to start as a service. Resolution To get Vista and Lonmaker running together: Stop the Vista service and unregister it. If using a Loytec interface, set the Loytec Legacy Driver to run as a service (click the Advanced tab in LConfig). Start Lonmaker and attach the correct network interface. Ensure that Lonmaker is online. Start Vista Server as an application. From Lonmaker open the System Plugin. In the TAC Network properties, check that the correct network interface is selected. Update the Vista database. Start Vista Workstation and check that everything is online. Stop Vista and Lonmaker. Reregister Vista as a service. For details of these operations see Registering/Unregistering TAC Vista Server as a Windows service. Also see section 16.3 of the TAC Vista Technical Manual.

Issue Installing I/NET and Vista on the Same PC Using I/NET with MSDE for File Equalization Product Line TAC INET, TAC Vista Environment I/NET 2.31 with MSDE Vista 5.1.4 with SQL2005 Express Windows XP Cause When Installing I/NET and Vista on the same PC and MSDE is desired for use with I/NET, I/NET must be installed first. If you are not using MSDE, please see Installation guidelines for installing I/NET and Vista on the same PC. Resolution Completely Remove I/NET, Vista and all versions of SQL and MSDE from the system. See Verify in Windows Registry all items are deleted after uninstall of I/NET Seven and MS SQL and How to uninstall and completely remove TAC Vista 5 for more details. Begin the I/NET Installation Select MSDE for the database installation. Complete I/NET and MSDE installation Install Vista Start Vista Server Start I/NET Configure I/NET as a Filemaster Build Database or restore from a backup.

Issue Does Vista support virtualization? Will Vista run on a virtual PC, VMware, virtual environment? Product Line TAC Vista Environment TAC Vista all versions VMWare, Player, Workstation and Server Microsoft Virtual PC Cause For many companies, the largest benefit of server virtualization is in reducing the amount of hardware that is required to run all the software needed by the business. Consolidating servers using a virtualization process not only provides savings in terms of how many physical machines must be bought and maintained, but also potentially reduces the amount of physical space that a company needs for its servers or data centre. Resolution Virtualization is a term that allows software in emulating environments, such as VMware / Virtual PC. These software packages emulate a PC environment so that many computers appear to be running on one single machine, thus “virtualization”. The general impression is that the emulation packages work very well. The user must be familiar with the emulating product in order to be able to do the correct settings. No matter if it runs on PC hardware or in an emulating environment, the specific product is supported given the problems are related to the Software itself, but not for problems related to the environment it runs on. Particular note and understanding is required when dealing with multiple applications trying to access a single piece of hardware, such as serial ports, USB and the like. Please see the following TPA-MALI-09-0013.00 for additional information. Also note that Vista Licensing system is NOT supported when using Remote Desktop. Refer to the following article for further details: Windows Remote Desktop (RDP) is not supported by the TAC Vista Licensing system.

Issue Xenta 102-AX temperature sensors reading in the range of 130°F (54.4°C) when they should be closer to room temperature. Wiring has been checked and everything appears correct. What kind of temp sensor do I use for a 102-AX? Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX ETD-1xx duct temperature sensors ETR-1xx room temperature sensors STR-1xx room thermostats Cause Every other Xenta controller uses a 1.8k-ohm thermistor as a standard. Because the Xenta 102-AX is a modified version of the I/NET MR-VAV-AX, it still uses the 10k-ohm thermistors native to the I/NET product line. Resolution The Xenta 102-AX uses 10k-ohm thermistors. See 10k Thermistor compatibility with Xenta controllers for detailed information on the thermistor curve that is acceptable. Approved sensors are: ETD-2xx duct temperature sensors ETR-2xx room temperature sensors STR-2xx room thermostats STD-2xx duct temperature sensors

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Not possible to see live values in a Xenta 700 Menta program from web interface or TAC Vista Can't see Menta online values in Xenta Server Control Applications graphical view The Menta application displays fine, but it's not possible to see the live values (true/false et c) Product Line TAC Vista Environment Xenta 731 Xenta 711 Xenta 721 Xenta 701 Xbuilder Menta Cause This is an uncommon error and the cause is not known, however it may occur when copying a HFB block within or between X700 Menta applications. Resolution In the Xbuilder projects folder, find the file [project name]\TargetImage\configdb\menta\mentablocks.xml and open it in Internet Explorer. Search for Menta blocks that have CodIndex='0' and note (copy) the GUID of those (for example 3C02F735-E375-45d0-99A8-6CFC402DE5D0). Now open the file [project name].xbp518 (in the project's root folder) with notepad or similar and search for these GUID(s). Note the Menta block(s) name (before the GUID) and the menta block type (just after the GUID), for example HFDI. Close all previously opened files (no save). Open the Xbuilder project normally, and open/edit the troublesome MTA. Search for the menta block(s) name and check that it also is the same block type (most likely a HFB block), then delete it. Create the block again with the same name (no copying from similar blocks!). Save and download the project to the X700. Now it should work fine viewing the live values in Control Applications. If still same issue, redo step 1-7, there may be other blocks with CodIndex='0'. Note: If you can't see the Menta application at all it's likely a different error, see Can't see the Xenta Server Menta program online in the browser.

Issue "Read-only because object refers to a standard file" when trying to change Menta application (.mta file) from TAC workstation. "File object is locked by another application" when trying to edit a Menta application (.mta file) (file is not marked as reserved) Product Line TAC Vista Environment Menta Workstation Cause If a standard file is used, it is not possible to edit the "local" Menta file. Other causes are explained in "File object is locked by another application" error when trying to edit Menta file. Resolution If the referenced file is supposed to be a standard file, locate and edit the file referenced. If the referenced file is not supposed to be a standard file: Click on the more button under the MTA tab in the properties for the device. Uncheck "Reference standard file object.

Issue A service that requires the system to be open has been accessed prior to successfully opening the System object. TAC Vista System Plug-In The system is not open. (Subsystem: LNS, #67) Error: LNS #67 lcaErrSystemNotOpen Product Line TAC Vista Environment LonMaker Vista LNS Cause There are many circumstances that could cause this. For example, if you call the Validate method to validate a network database before opening the system, or if you call the Backup method to copy a network database before opening the system, this exception will be thrown. Resolution If registering or launching the TAC System Plug-in results in the error "System is not open, LNS #67" followed by "TACOSSysPin.Document launch failure Exception occurred," and "lnsplugin.api launch failure," then your LNS credits may be corrupted despite indications that they are not. First reboot and try again. If still fails, replacement credits have to be reordered from Echelon. See description of LNS #147 in Error message in Vista System Plug-in: LNS System access failure, (Subsystem: NS,#147). It is also possible to get LNS #67 without having corrupted credits. This has been seen a couple of times on databases that are upgraded from LNS 3.1 to LNS Turbo. It seems to be hit or miss whether the upgrade will cause this issue or not. The Licensing Upgrade 2006 discussed in LNS #147 should be installed. Defragmenting the computer can also cause this corrupted credits with no indication and a TACOSSysPin error. Replacement credits will fix the issue even though there is no indication that they are corrupted.

Issue Does TAC Vista Support MySQL Server? Product Line TAC Vista Environment TAC Vista MySQL Cause User may wish to integrate TAC Vista with a MySQL installation for access to data or reporting. Resolution TAC Vista can not support MySQL Server. It only supports various types of Microsoft SQL Servers. For details, please refer to the compatibility matrix which is available on Exchange Extranet, or refer to Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation.

Issue Adding a Xenta Programmable Controller to an NL220 System Product Line TAC Vista Environment NL220 Cause Commissioning a Xenta programmable controller in NL220 needs to follow a certain procedure in order to prevent various issues from occurring, such as controllers not showing online in Vista Workstation, etc. Resolution Adding a Xenta Programmable Controller to an NL220 LNS system. Preparation: Create the Menta File Install the Controller Adding the Device to the LNS database NL220:Create a Template for the device type. See NL220 Useful Functions and Shortcuts on how to create a template. NL220:Add a node using the correct device Template System plug-in: Assign Neuron ID and Menta file Add and match I/Os if applicable Bring the Device to the Vista Database System plug-in: Update TAC Network Drag controller to an existing group if desired, and delete the now empty group Create group bindings Assign Neuron ID for the I/O modules Update the TAC Network again Check TAC Network Update Vista Database Check that your network is attached and OnNet Download Application and Parameters Bring Vista Db online NL220: Commission and download the device (ignore I/O modules.) System plug-in: Commence Communication (if needed) NOTE: It is very important that you Download Application and Parameters in the Vista system plug in THEN Commission the device in NL220.

Issue There are two sets of terminals on the Xenta Repeater that are labeled identically. Product Line TAC Vista Environment Vista Lon Network Cause The duplicate power supply and communications terminals are internally connected. Resolution The power supply and communication connections can be made either to the upper or the lower terminals as they are internally connected. The extra set of terminals is strictly for convenience purposes. One segment of the Lon network should be connected to the COM1 terminals and the other segment should be connected to the COM2 terminals. The only other wiring required is to connect the Xenta Repeater to a 24V power supply. Wiring Example #1 This is the most traditional wiring schematic used with a Xenta repeater. Segment #1 comes into COM1 and is the end-of-line for a bus topology. A terminator is placed at the repeater. Segment #2 continues on out of COM2, and represents the beginning-of-line for the next segment, thus is also terminated at the repeater. Wiring Example #2 This example is actually the same as Example #1, but is showing that the upper or lower terminals can be used for convenience, as they have electrical connectivity from top to bottom. Wiring Example #3 Example #3 shows Segment 1 coming into COM1 on top and carrying on out of COM1 on bottom. This segment does not get terminated at the repeater because it is not the end of line for this segment. However, COM2 does represent the beginning-of-line for the second segment, and is therefore terminated at the repeater. For more information on how the Xenta Repeater works see the following article: The Xenta Repeater provides signal restoration and conditioning on LON networks.

Issue Xenta 102-ES configuration and wiring for 2 position (on / off) heating actuators or other digital heating control Product Line TAC Vista Environment Vista Xenta 102-ES Cause Wiring for 2 position heating control on the Xenta 102-ES is different than increase / decrease type actuators. Resolution The Xenta 102-ES documentation refers to two position heating control as thermal actuators, thermo or TAO and can be somewhat confusing. The same info applies whether using a two position hot water valve, any on / off type electrical heat (such as baseboard heaters or electric heating strips. Here's what you need to know: If using only one stage of heat: Select Thermo for Primary Heating in the Xenta 102-ES plugin or if configuring from Vista Workstation or the OP set nciAppOptions bit 5 to 1 and leave bit 6 as 0. From the Xenta 102-ES plugin choose either Normally Closed (NC) or Normally Open (NO) from the box in between the Primary and Secondary Heating fields. Additionally, this can be configured from Vista Workstation or the OP by setting nciAppOptions bit 11 to 0 for normally closed (NC) operation or set bit 11 to 1 for normally open (NO) operation. Both terminals V3 and V4 will be switched when the first stage of heat is activated. These terminals operate in parallel in this configuration and either one can be used. If using two stages of heat: Select Thermo for Primary Heating in the Xenta 102-ES plugin and select Enable for Secondary Heating. If configuring the device from Vista Workstation or the OP set nciAppOptions bit 5 and bit 6 to 1. From the Xenta 102-ES plugin choose either Normally Closed (NC) or Normally Open (NO) from the box in between the Primary and Secondary Heating fields. Additionally, this can be configured from Vista Workstation or the OP by setting nciAppOptions bit 11 to 0 for normally closed (NC) operation or set bit 11 to 1 for normally open (NO) operation. Both terminals V3 and V4 will be switched when the first stage of heat is activated. These terminals operate in parallel in this configuration and either one can be used. Only terminal V6 will be switched for second stage of heat. Note: The triac outputs of the Xenta 102-ES are ground sourcing and should be wired accordingly. See Digital outputs (V) on most Xenta 100 series controllers are ground sourcing (voltage sinking) for additional information.

Issue "PSU device driver failed, It may be missing or disabled!” error or “An External installation failed : Hasp" error error when attempting to install Privilege Administrator. Product Line TAC Vista Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause Incompatibility with Windows Server 2003 Resolution Uninstall any previous installation attempts (Please see How to uninstall Privilege Administrator 2.01 software for instructions on uninstalling the software) Download HDD32.zip from Exchange Online located at Previous Vista Software \ TAC Vista IV License System Unzip and run HDD32.exe Install Privilege Administrator again. Only Vista version 4.20 and later is supported for use in Windows 2003 Server. Please observe that HDD32 may also solve some problems when installing Privilege License on Windows XP Note: Beginning 2012, PSS will no longer support the Privilege License System. The Tamfs26 Server will be retired along with TAC License Server software. It would be wise to inform the customer of this important information to plan for future upgrade in the event that their site license has issues.

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

Error when commissioning I/A MNL800 controller in LonMaker

Adding Webstation to an Existing Network

SNVT not updating Menta inputs in a 731

Xenta Server Trend log has estimated values for a constant period of time

Privilege software version 2.01 crashes during installation on Windows XP

Periodic report will not run when Vista Server is running as a service

Vista Server hangs on startup

Launching Menta by opening an MTA file causes a Buffer Overrun Error

Cannot attach the Network interface to Lonmaker when Tacos is started as a service

Installing I/NET and Vista on the Same PC Using I/NET with MSDE for File Equalization

Running Vista software on an emulated environment

Xenta 102-AX temperature sensors reading incorrectly, very high

Not possible to see live values in a Xenta 700 Menta program

"Read-only because object refers to a standard file" when editing Menta from Workstation

The system is not open. (Subsystem: LNS, #67)

TAC Vista does not support MySQL Server

Adding a Xenta Programmable Controller to an NL220 System

How To Wire a Xenta Repeater

Xenta 102-ES configuration and wiring for 2 position (on/off) heating control

"PSU device driver failed, It may be missing or disabled!" or "An External installation failed : Hasp"

Building Automation Knowledge Base

Related Forums

This is a heading