Issue How to increase the number of Modbus registers the Xenta server polls in a single request? Product Line TAC Vista Environment XBuilder Xenta 511 Xenta 913 Xenta 701 Xenta 711 Xenta 721 Xenta 731 Cause This feature is not well documented in the Xenta 700 documentation, though it is mentioned in the TAC Xenta Server – Gateway, Technical Manual (Xenta 913). Resolution In XBuilder, selected the Modbus device in the network view. Under Link->Max Range Size you will see the current setting, the default is 20 which most devices support. Change the number to the desired value between 1-100. Note that the value must be supported by the device! Download the project to the device to commit changes.  

Issue Some sensors such as the SCR110-H CO2 produce a noisy signal even when wired according to the documented instructions. The following is a trend chart of the unfiltered raw signal from the sensor. Environment Automation Server Continuum controllers TAC Xenta Cause Noisy signal is typically caused by common ground wiring of AC power. Resolution SOLUTION #1 Signal noise can usually be eliminated by using an isolated transformer to power the sensor separately as opposed to using a common transformer that powers up several pieces of equipment. SOLUTION #2 For sensors that support  AC and DC input voltage, signal noise can usually be eliminated by using DC instead of AC power source to power the sensor. SOLUTION #3 Implement a Slew Rate to filter out the noise. As of version 1.7.1, StruxureWare Building Operation does not have a built-in slew rate functionality. Nevertheless, a custom slew rate can be implemented using Script programming. See HowToDebounceANoisySensorSignal.pdf SOLUTION #4 Add a filter (FILT) in a Function Block program after the signal input Description: The function block is a discrete time first order software filter. The filter time constant is specified in seconds with the Time Const parameter. The initial block output value is zero. The filter algorithm is y(k) = y(k-1) + 1 / 1+T/h (u(k)-y(k-1)) where y(k) and u(k) are the filtered and unfiltered values at time k, respectively,h is the sampling interval (i.e. the application program cycle time), and T is the filter time constant. If the time constant is less than or equal to zero, no filtering is done. To obtain a good filter function, the time constant should be set significantly greater than the application program cycle time. This filter algorithm is based on a straightforward backward difference approximation of the continuous time derivative operator. SOLUTION #5 Ensure you are not using older versions of the IO Firmware. As detailed in TPA-SBO-17-0006.00 the firmware should be at least V2.015 in the modules and is available on the Download Center.

Issue How to create a new database or purge a full SQL (i.e. it has hit the limit of 2G) Product Line TAC Vista Environment TAC Vista 4.X 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. Cause Log data has filled the 2GB limit of the SQL database. Resolution How to purge a full SQL (if you've hit the limit of 2G) Before deleting the database or creating a new one: Check the $queues/insertevents and $queues/insertlogvalues folders in the Vista database. This folder may contain "queued" files waiting to be written into the SQL database. If these queues have significant amount of data stored as a result of the SQL being full, you may delete these files if the data is not needed. If the data is needed, it will be written to the new SQL Database when Vista starts. In some cases, the $queue folders may be so large that even creating a new database won't allow the Vista Server to run. If this is the case and the $queued items are not needed, delete them from their directories. If you find that there is an abundant amount of queued files it may be easier to delete them using DOS. This can be done by navigating using the "cd" and "cd.." command prompts to c:\TAC\Vista\VistaDb\$queues. There you will find \insertevents and \insertlogvalues. You can clear both directories using the "del" command. It is recommended to stop the SQL Server and DSS Writer before attempting to delete any queued files. You can stop the SQL Server by double-clicking on the icon in the task bar and choosing to "Stop". You can locate the DSS Writer by right-clicking on My Computer and selecting "Manage". Navigate to "Services and Applications\Services" directory and look for "TAC DSS Writer Service". Right click on this service and select Stop. If the data is not needed: Simply go to ...Microsoft SQL Server/MSSQL$TACVISTA/Data and delete the old database. Before doing so, you may need to stop the SQL Server.  Then following steps in "If the data is needed" section below. If the data is needed: The simplest way to get a fresh DB is to create one. This is done using TAC Vista SQL Setup which can be downloaded from the Buildings Business Extranet: Global. Make sure that you download the SQL Setup for your Vista product version. In the Vista SQL Setup program, select your SQL Server - pcname\TACVISTA, Chose Windows Authentication if Vista is managing the Database (recommended in the Vista Install), "Login", enter the name of the database (perhaps "NEWtacdatalog" to be created, and select the login pcname\TACA_pcname, and "Create". This will create a new database to which you can now point the Vista Server. In Vista Server Setup, under the SQL Tab, change the database to this newly created database, click "OK". You can keep the old database to export for viewing or if you plan on upgrading to SQL Enterprise and merging the data in the future.   NOTE: Sometimes when this is done without first detaching or deleting the database from the SQL, the DSSwriter or TACA user stops working. Detach/Delete the database with SQL Management Studio Express and reinstall the system to solve this.  

Issue How to communicate with an Xenta 200/300/400 via an X911 in Vista Environment TAC Vista 5.1.X X911 5.1.X Xenta 200/300/400 device. Cause An X911 is to be used as an IP/Lon gateway. Resolution To add an X911 in Vista do the following: 1. In Vista workstation, right-click on the Server object and select New\Device\Communication Port - Xenta 911. 2. Give the device a suitable name. 3. Right-click on the device and select Properties. 4. Set the IP address for the device. 5. Right-click on the X911 and select New\Lonworks Network. 6. Give the network an appropriate name. 7. Right-click on the network and select New\TAC Xenta Group. 8. Give the group an appropriate name. The new Xenta devices can now be added by right-clicking and selecting New\Xenta 200\300\400. The device can then be configured via the properties menu. Once the device\s are configured the configuration can be downloaded to the devices. 1. Right-click on the lonworks network and select Commission and Download. 2. Click on the Start the selected operation  button and wait until the download has been completed. See TAC Xenta 500 700 911 913 Product Manual for full instructions on how to configure an X911.

Issue Remove the Routing tables from I/NET and Xenta 527 devices Host conflict or station conflict error messages displayed at the I/NET Host. Incorrect Links, Hosts and IP addresses that do not exist in your Network are shown when penetrating Network Configuration. Product Line Other, TAC INET, TAC Vista Environment I/NET IP Routers Xenta 527 Cause Host or station conflict errors can be caused by old information stored in a routing table. From time to time, it may be necessary to purge that information and allow the tables to be rebuilt automatically. The only way that routing tables can become corrupted is if a laptop was used to connect to the system from a different Network or from the Outside. Once connected, its IP table is broadcasted to the other devices like PCs and NPRs, thus populating the table with entries that does not belong or is non-existent for this location or system.  Resolution Managing I/NET Routing Tables   I/NET Host Workstation View the I/NET Routing Table See Viewing the routing tables on a PC using I/NET Seven for complete instructions. Delete a Single entry in the I/NET Routing Table Go to Start > Run Type Telnet and hit Enter Type open, hit the space bar, then enter the IP address of the PC Press Enter When the login comes up, type csi, hit enter Type LA  and hit enter to list all routing table entries Type ipdel xxx.xxx.xxx.xxx with xxx.xxx.xxx.xxx being the IP address of the device you wish to delete Press enter Clearing the I/NET Routing Table Shutdown the I/O Server Open Windows Explorer Browse to C:\INET Seven Data (or C:\Program Files\INET Seven) Delete the .dat files (you may want to save a backup to another location) Delete the routing table from any device listed as a Reference Host or the table will repopulate Start I/NET Other Method: See Bogus Links, Hosts and IP's in Netcon for instructions on using the delall command in Telnet     Xenta 527-NPR; Xenta 913; Xenta 527 Web Server (See Clear the IP routing tables of a Xenta 913)  Viewing the I/NET Routing Table View Connecting a serial cable to a Xenta 5/7/9xx controller to configure HyperTerminal to communicate to the Xenta Device. Log into the Xenta Device as the root user At the dsh/> type “inet ip” Press enter Deleting a Single entry in the I/NET Routing Table View Connecting a serial cable to a Xenta 5/7/9xx controller to configure HyperTerminal to communicate to the Xenta Device. Log into the Xenta Device as the root user At the dsh/> type “inet ipdel” then the IP address of the device you wish to delete Press enter Clearing the I/NET Routing Table View Connecting a serial cable to a Xenta 5/7/9xx controller to configure HyperTerminal to communicate to the Xenta Device. Log into the Xenta Device as the root user At the dsh/> type “inet delall” Press enter Type “inethost” and press enter Verify or set the Reference Hosts Clear the routing table from any referenced device to ensure old data is not repopulated Restart the Controller to re-populate the routing table   You can also realize this through the web page of Xenta device. Open the web page of Xenta controller, browse to Utilities-I/NET-I/NET Command Line, and type the command below or above. The result is the same as using HyperTerminal, which is also an easier way. Typing “inet help” or “inet” gives every I/NET option within the controller inet - I/NET Help ip - Display IP table list ls - Display Link/Station table list cp - Display Compressed table list gp - Display Global Point table list mm - Message masking all - Display all lists ipadd - Add an IP address to the tables ipdel - Delete a single ip record delall - Delete all ip records   NPR-2000 Viewing the I/NET Routing Table Go to Start>Run then type “Telnet” and hit Enter Type open hit the space bar then enter the IP address of the NPR Press Enter When the login comes up, type csi hit enter Type “LA”  and hit enter to list all routing table entries Deleting a Single entry in the I/NET Routing Table Go to Start>Run then type “Telnet” and hit Enter Type open hit the space bar then enter the IP address of the NPR Press Enter When the login comes up, type csi hit enter Type “LA”  and hit enter to list all routing table entries Type “ipdel xxx.xxx.xxx.xxx” with xxx.xxx.xxx.xxx being the IP address of the device you wish to delete Press enter Clearing the I/NET Routing Table (See Bogus Links, Hosts and IP's in Netcon)  Go to Start>Run then type “Telnet” and hit Enter Type open hit the space bar then enter the IP address of the PC Press Enter When the login comes up, type csi hit enter Type “LA”  and hit enter to list all routing table entries Type “delall” and hit enter to clear the table   Appendix A: I/NET Telnet Commands Glossary: Help – Displays all available commands in the NPR or I/O Server.  Note there are some differences between the NPR and I/O Server. ipadd a.b.c.d – Adds the IP to the routing tables. ipdel a.b.c.d – Deletes the IP from the routing tables. gpadd LLSSPPBBTT XX | a.b.c.d – Adds a global point link or global point IP to the routing tables. delall – Deletes “all” local routing table entries. setpass password – Change the telnet login password (6 characters max). +cpdel LLLL SS – Deletes the specified link/site address from the CP table. +debug gp on|off – Turns global point debugging on or off. +reboot – Reboots the NPR. +wdog – Reports watchdog errors. +wdogrst – Clears the watchdog errors. +Dx – Toggle debug output to COM3.  x=0/1; 0 = off, 1=on.   List Commands: +LR – IP Stack routing table. LI – IP routing table. LM – IP routing masks. LL – Link/Station routing table. LG – Global point routing table. +LC – Compressed routing table. +LS # - Compressed routing table: station to site maps for the specified link #. LA – All routing tables. LU – System metrics. *LD – Dial maps.  + = NPR only * = Host PC only   Appendix B: Method for Clearing Routing Tables at a Large Site See Possible solution to doing a Telnet session with a system wide firewall setup.   Appendix C: Suggested Reference Host Settings   Click here to be linked to the TAC INET Seven Getting Started. Click here to be linked to the TAC INET Seven Operator Guide.   A Reference Host is any TAC I/NET workstation, NPR, or Xenta 527/527-NPR that will serve as a source of IP addresses. Any of these devices attached to an Ethernet LAN can be used as a Reference Host. Each time I/O Server is started on a workstation, it provides the workstation’s IP address to each remote host designated as a Reference Host. I/O Server also requests and receives a list of all host IP addresses that are known to the remote host at that time. I/O Server must be running on the remote host for this address exchange to occur. I/O Server compiles and maintains a list of all the remote hosts that it learns about. Ultimately, all hosts in the network will know the IP addresses of all the other hosts. Ideally, you should determine 1 or at most 2 devices to serve as your Reference Host.  This device would ideally be a Xenta Server or an NPR, but a Host workstation that has I/O Server running 100% of the time will work as well.  All devices on the system will use this as a single Reference Host. No others are needed.  When the device comes online it will contact the Reference Host and get the site’s Routing Table.  The Reference Host can have an empty routing table.  Once the Routing Table is shared, Reference Hosts are no longer needed.  You can leave the single entry in place. This will allow a quick recover, in the event of a critical system failure. Here are a few reasons for using multiple Reference Hosts: Temporarily add a new device as a Reference Host on the Sites Reference Host or a workstation to aid in bringing it online A large site may desire to have 2 Reference Hosts in case one is offline when a device comes online. An I/NET site that spans multiple locations may wish to declare a local Reference Host for each building and a network Reference Host  

Issue How to transfer data from TAC Vista to EBO(EcoStruxure Building Operation) as a temporarily solution while a transition between TAC Vista and EBO is done?    Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista SmartStruxure Solution EcoStruxure Web Services TAC Vista SmartStruxure Interface 1.5 Cause If EBO need data from TAC Vista during a transition period the TAC Vista SmartStruxure interface can be used.   Resolution Please see the video or follow the instructions below:   On the Vista server(s) install the TAC Vista SmartStruxure Interface first. Refer to TAC Vista to SmartStruxure Interface will not connect when TAC Vista and SmartStruxure are installed on the same machine if there are any issues installing or getting the two programs to communicate when on the same PC. In StruxureWare Workstation, on the Enterprise server object or the Automation server object right click and create new interface, and select the EcoStruxure Web Service interface in Workstation. Click next. In the Server, enter the IP address of Vista server. If it is local, just use localhost. Enter the username and password of Vista Server. Pay attention that only the user in the default System user group can be used. Don't try to create other System group. And all the letters in the password field need to be in capital letters. This is a defect that will be addressed in the next release of TAC Vista to SmartStruxure interface. Please be selective with the port that you are using. If the Vista to SmartStruxure Interface program is on the same PC as the Enterprise server than a different port other than 80 or 443 will have to be used. Please refer to TAC Vista to SmartStruxure Interface will not connect when TAC Vista and SmartStruxure are installed on the same machine if the two softwares need to be on the same machine. Click Create. The next step is to Host TAC Vista objects into SmartStruxure. Refer to How to host TAC Vista objects using Web Services in StruxureWare Building Operation for the guide of how to host Vista objects into SmartStruxure. NOTE: There is a defect for Version 1.0 of TAC Vista to SmartStruxure interface under Non-English operation system. The EcoStruxure Web Services interface will not come online in SmartStruxure. Refer to TAC Vista to SmartStruxure Interface does not connect in non-English Operation System for solution.

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 LonWorks point count recommendation for the Xenta 5/7/9xx series controllers What is the device limitation on the FT-10 LonWorks channel installed on a Xenta Server Product Line TAC Vista Environment Xenta 500 Xenta 700 Xenta 900 Cause The load point table can be found in Vista version Release Notes on The Exchange Download Center. When Xenta 700 was released the Product Announcement had a table with the recommended number of LonWorks devices attached to Xenta 5/7/9xx. Below you can see a small revision of the recommendations. The list applies to devices which the applications in the Xenta 5/7/9xx are interchanging data with. Other devices that are completely handled by TAC Vista through the LTA port of Xenta 5/7/9xx are not included in this calculation. These devices will influence the LonWorks network performance in a similar way as if they were connected through a Xenta 911 and have to be considered. Not following the design recommendations and adding too many LonWorks devices to a single channel will cause poor Xenta Server performance. Resolution Each device uses "load points" according to the table. As a general guideline the total "load points" on the network shall stay under 100 to get a reasonable performance. In reality the e.g. intensity of the traffic also has an influence as well as, of course, the expectations on response time. Type of device Load points I/O module 5 Xenta group master 280/300/401      20 Additional Xenta 280/300/401      in the group 2 Standard LonWorks device, including Xenta 100, polled 2 Standard LonWorks device, including Xenta 100, bound 0.75 Refer to The Exchange Download Center for future releases of Vista / Xenta Release Notes containing software and updated load calculations This information is usually found in the Appendix B - Engineer Information, and look for section titled LonWorks recommendation for the Xenta 500 and 700 series

Issue How long does PSS support a product after it is released? Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series, TAC INET, TAC Vista Environment All Schneider Electric Buildings Business software platforms Cause After a few years, the majority of issues with a release product are documented in the Knowledge Base.  At this point, if the customer is having issues requiring Product Support, we ask that they upgrade to the current version. Resolution Please read the following Product Announcements: PA_00271 Software Support Policy - General Overview.pdf PA_00272 Software Support Policy - Supplementary info for_Andover_Continuum.pdf PA_00274 Software Support Policy - Supplementary info for TAC Vista.pdf PA_00279 Software Support Policy - Supplementary info for TAC INET.pdf PA_00280 Software Support Policy - Supplementary info for TAC IA Series.pdf

Issue Can I send live data over SNMP? How many trap pages can I define? Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731 Cause All Xenta Servers (except Xenta 913 and Xenta 527-NPR) have a built in SNMP agent. However, the SNMP protocol in them cannot handle sending live data over SNMP. It can only send alarms along with specific fields of those alarms.   Resolution The Xenta Server supports SNMP version 1 and SNMP Traps. It can only be used to send SNMP and not to receive. The first step to setting up SNMP is to create alarms in XBuilder and link the points to the alarms that are to be monitored. Then, the filters used by the SNMP traps should be defined. This is done using SNMP trap pages. SNMP Trap Page The SNMP trap page is where you define a set of rules in Xbuilder of when to send a trap to the SNMP manager. This includes severity of the alarm or a wildcard string based on the address of the point.  In XBuilder you can create up to 10 SNMP trap pages, which will give you possibilities to define 10 different alarm filters. An SNMP trap page is created by right-clicking a folder in the System pane of XBuilder and then selecting New > Page > SNMP Trap Page. (It is recommended that a separate folder be created for SNMP trap pages and that this folder be restricted to only system administrators.) Once the SNMP trap page has been created it is then configured by right-clicking on the SNMP trap page object and selecting SetupSNMP Trap Filter.   SNMP Field Configuration The SNMP field configuration is where you define what 8 pieces of data will be sent to the SNMP manager (due to the UDP limit of 8 fields). That data consists of things like date/time, type, address, priority, description, etc. The SNMP field configuration is accessed by clicking on the Tools menu and selecting SNMP Field Configuration.     For more information on SNMP in Xenta Servers please see the TAC Xenta Server - TAC Networks Technical Manual, section 16. Note: SNMP is only supported by Xenta Server devices and is not supported by TAC Vista.  

Issue Get error "Local TAC Vista server not started . Cannot reserve graphic object" when trying to edit a OGC graphic from TAC Vista Workstation. Can not start OGC editor from within TAC Vista Workstation Product Line TAC Vista Environment Windows Server 2008 Windows Server 2008R2 Windows 7 TAC Vista Server running as a Service Cause When using Windows 2008/7 the following legacy tools can not be used when TAC Vista Server runs as a service: TA Draw, TA Main, Database Generator, LIST.EXE, IPCL Editor, Test Client and UPGRFILE.EXE. For more restrictions for Windows 2008 and Windows 2007 see the release TPA-VSTA-11-0002.01 for TAC Vista 5.1.5. Resolution Run TAC Vista Server as an application.  Refer to Registering/Unregistering TAC Vista Server as a Windows service for registering/unregistering Vista Server as a service.

Issue A new feature is introduced in TAC Vista Workstation 5.1.7, enabling the user to identify broken and empty TGML bindings and TGML Links in TAC Vista Workstation. This feature can also list all bindings and links in TAC Vista Workstation, replacing the search function previously used to identify bindings and links in TAC Vista Workstation. Product Line TAC Vista Environment Vista 5.1.7 and above Cause Compiling a list of all bindings, or all empty or broken bindings, allows a user to quickly find and update any graphical problems cross an entire database at once. Resolution From Workstation, right click on a folder and choose "Find broken bindings." This replaces the previous method of searching for broken bindings within the Search window. Note the following object types are no longer available in the TAC Vista Workstation search function: TGML Bindings TGML Dynamics TGML Link TGML Links See TAC Vista Technical Manual Chapter 28.2 for additional information about this feature.

Issue When a Xenta 121-FC changes from heating to cooling the fan output  turns off for 5-10 seconds. Product Line TAC Vista Environment 121-FC controller Cause The firmware version has been enhanced and this was a enhancement that has been implemented. Resolution Upgrade your 121-FC to version 1.25 (or above). Download the upgrade files from The Exchange Download Center: Xenta 121-FC Firmware Files (NXE/APB/XIF) See Downloading new NXE or APB files using Lonmaker for instructions on how to download the application to the controller using LonMaker.

Issue What is extended lon talk? Is there no support for connection objects in TAC XBuilder 5.1.5 and 5.1.6? Environment TAC Vista 5.1.5, TAC Vista 5.1.6 XBuilder Xenta Server Cause In the release TPA-VSTA-11-0013.00 for Vista 5.1.6 it says: Extended LonTalk It is not possible to write to Extended LonTalk devices within XBuilder. Connections have to be engineered using NL220, Lonmaker or TAC Vista Workstation through object transfers. This can be misunderstood as connection objects are no longer supported. "Extended LON" means a newer type of neuron chip that has more address and domain tables (e.g. Loytec's LISA chip). The support for this was added in TAC Vista 5.1.5 but it is not added to the Xenta Servers. So support has not been removed for anything, just added support in TAC Vista. Resolution "Extended LON" refers to a newer type of neuron chip that has more address and domain tables (e.g. Loytec's LISA chip) There are no change in the use of connection objects in TAC Xbuilder 5.1.5 and 5.1.6

Issue When you view a Xenta Log through Vista you get estimated values in the Log. Product Line TAC Vista Environment Vista 4.x.x Vista 5.x.x Cause If the site has many Xenta logs in 200,300 or 400 controllers you maybe exceeding the limit for trend uploads to Vista. The maximum limit is 4 uploads of Xenta logs per minute to Vista. If you exceed this value estimated values may appear in the Xenta logs. Here is a link to a white paper description on this topic TAC Xenta Trend Logs Whitepaper Resolution Here are some steps to check if the estimated values are caused from excessive Xenta trend upload.   Calculate the amount of uploads that are occurring in the database. As an example if a Xenta log is set to store information in the controller for 1 hour and upload at 80% full. This equates to 0.8 uploads per hour or 0.013 uploads per minute. If you work out this rate for all the xenta logs in the database you can then calculate how many uploads are occurring per minute. To extract all the Xenta Logs in the Vista database follow these steps also shown in the video. From TAC Vista workstation select View and then Search from the toolbar. select the browse option for the field "Type of devices or objects" Expand the heading labeled Files. Expand the heading labeled Trend Logs under the Files heading. Expand the heading labeled Trend Log Vista under the Trend Log heading Check the Trend Log Xenta box Select OK In the Property value dropdown list select the" Log size byte " option. This is the Xenta Log duration in seconds. Select the search Button The search results now show all the Xenta Logs. You may need to uncheck the "interrupt search if more than 1000 results" to capture all Xenta trends In the Search output Pane right mouse click and select "Additional properties" Expand the list and select "Retrieve at % Full option" The Search results then show all Xenta trends with Xenta Log duration and retrieve % full. Copy this list in Excel and calculate the uploads per minute from this Database. Below is an image showing the data pasted into Excel, displaying the equation to calculate the upload per minute value per log:  If you find your total "uploads per minute" exceed 4 then reducing this may remove the estimated values. Some ways to do this are. Extend the Xenta log storage time in the Xenta device if memory permits. Change the upload percentage to a greater number if it has been decreased below 80%  Increase the Xenta sample rate which will allow for the Xenta storage to be extended as in point 1.

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

Issue Error "Not enough space in RTI device"   Product Line TAC Vista Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause Memory in PSU is corrupt. Resolution Run Dongleutil, a dongle reset utility software. This utility resets the memory in the PSU that is connected to the PC. You need to install the license file again after this operation. This problem is usually seen when Inhouse PSU is used. In TAC Vista version 4.10 and later, it’s no longer necessary to install the engineering file when Inhouse PSU is in use. Just connect the PSU to the PC, and everything should work fine.

Issue Error states: "Ensure that Vista Server is started" when trying to log into TAC Vista Workstation. The server is started. Product Line TAC Vista Environment TAC Vista Workstation 4.2.5, 4.3.0-4.5.0, 5.0.0 and higher Microsoft Windows XP Service Pack 2 Cause Microsoft Windows XP Service Pack 2 has security changes/upgrades from previous service packs.  This affects the DCOM permissions that Vista Server relies on. a variety of other reason could result in an error in DCOM parameters in later operating systems. Resolution Vista 4.2.5 Apply settings described in this TPI to get TAC Vista to work properly. Vista 4.3.0-4.5.0 Apply settings described in this TPI to get TAC Vista to work properly. Vista 5.0.0 and higher Apply settings described in TAC Software Installation Manual available on The Exchange Download Center. This can be done using the DCOM Utility in Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET. Error Message: Ensure that Vista Server is started lists manual steps to access DCOM.

Issue Error during installation of Vista:  "Unable to Locate Microsoft Excel" or may say "Could not find Microsoft Excel which is needed to use Vista Reports." Environment Windows 7, XP Microsoft Excel Vista Cause Vista may not be compatible with the version of Excel that you have installed on your computer or Excel may not be installed. Resolution Download document TAC Vista Compatibility Matrix Use the matrix to compare the version of Vista you are trying to install and the software installed on the machine Correct any discrepancies by either purchasing a different version of Excel for the computer or using a different version of Vista.

Issue Getting the error "The RPC server is unavailable" when attempting to write to a Vista Database.  This error can also be shown in the plug-ins output pain as "Error: Failed to access object xxxxxxxxxx." Product Line TAC Vista Environment TAC Vista System Plug-in Cause Incorrect DCOM or Firewall settings. This often occurs when installing a new system or restoring an existing Vista Database to a new PC. Computer is running out of memory. Resolution If it is cause due to computer memory shortage, please restart the TAC Vista Server. If the restart does not solve the issue, please follow the steps below. Install the DCOM utility located in Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET. or manually set the DCOM settings as instructed in the TAC Software Installation Unzip and execute the utility. If the problem persists and Vista Server is not on the local machine, ensure there is not a Firewall preventing a connection. If steps above does not resolve the issue, please reinstall TAC Vista software.