Building Automation Knowledge Base

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 How to uninstall and completely remove TAC Vista 4.3 to TAC Vista 4.5 Product Line TAC Vista Environment Microsoft Windows OS Vista 4.3 to Vista 4.5 Cause Occasionally it is beneficial to be able to remove a TAC Vista installation completely, removing any indication it was ever installed. Resolution When using SQL 2000 or enterprise version not administered by TAC Vista: Backup SQL database named "taclogdata." Use the backup function in SQL Server manager. Save the database outside of the Microsoft SQL Server and TAC root directory (usually C:\Program Files\TAC and> C:\Program Files\Microsoft SQL Server). When using SQL MSDE administered by TAC Vista: Backup TAC Vista log and event database using backup function in TAC Vista. Backup TAC Vista database using backup function in TAC Vista. Stop SQL manager, Task manager/processes – stop sqlserv.exe and sqlagent.exe if running. Remove TAC Vista Config1.x using the uninstall program in Control panel Add/Remove programs. Remove all TAC Vista hotfixes. Remove TAC Vista Server 4.x.x using the uninstall program in Control panel Add/Remove programs. If additional TAC programs like TAC ToolPack, TAC XBuilder etc. are installed remove them as mentioned before. Remove SQL (Microsoft SQL server desktop engine) using the uninstall program in Control panel Add/Remove programs. Save off a customer's license (.lic) file to another location.  Delete remaining uninstalled TAC folders (usually C:\Program Files\TAC). Delete remaining files in C:\Program Files\Common Files\TAC Shared. Delete remaining uninstalled SQL (Microsoft SQL server) folders (usually C:\Program Files\Microsoft SQL Server) Check to see if TAC needs to be removed from the registry – Start, Run, REGEDIT. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls Remove all keys containing "TAC Shared," e.g. C:\Program Files\Common Files\TAC Shared\TACADDON01_ENG.dll. If applicable - Remove SQL from registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL server Go to user profiles delete the profile Computername\TACA_Computername (Versions of Vista <5.0) Go to My computer, right click manage, local users and groups, users, and delete user account TACA_Computername and TACM_Computername. Reboot. Reinstall desired version. See How to uninstall and completely remove TAC Vista 5 for steps on removing TAC Vista 5.

Issue "No license for LonWorks communication" with TAC Vista Server LE Product Line TAC Vista Environment TAC Vista Server LE (LE= Limited Edition which has no Webstation or multiserver functionality) Cause If TAC Vista Webstation is installed on a TAC Vista Server LE machine, Lon communications will not work correctly. It will work for 10 minutes then an alarm message appears, "No license for LonWorks communication," and all communication with the Lon network will stop. Resolution Uninstall Webstation Related Articles: "No license for LonWorks communication" error when using a non LE dongle. "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" error message in Classic Network. "No license for LonWorks communication" Error in Windows 2008 Server X64 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue How to order more NL credits in order to commission more devices. If the following message displays when opening a NL220 database, then more credits will need to be purchased soon. " BEWARE: less than 20 credits are available on this machine. If you need to install more than 20 device please order the amount of needed credits as soon as possible. Do you want to ask for new credits?" Product Line TAC IA Series, TAC Vista Environment NL220 LNS Cause There are two types of credits: Product specific credits like LonMaker and NL credits LNS credits   Echelon LNS LNS credits are assigned to the PC and when they reach zero, the LNS Server license goes into deficit mode. After 14 days the deficit mode will expire, at which time no LNS tools will be able to be used on that PC. To reverse the lockout, enough LNS credits must be ordered to cover the deficit and any additional nodes that need to be commissioned. Backing up, sharing, and restoring LNS databases can sometimes corrupt these LNS credits, which then prohibits you from launching any LNS plug-ins. For more help with corrupt LNS credits see Corrupted LNS Credits. Echelon LonMaker LonMaker credits are assigned to the PC. Both LNS and LonMaker credits are required, however when commissioning devices in LonMaker, LonMaker credits are consumed but LNS credits are not. Even though LNS credits are not consumed in LonMaker they are still necessary because certain LNS applications (i.e. TAC Vista System Plug-in) require them to operate. Newron NL220 Each time a node is commissioned in NL220 it requires a NL credit and a LNS credit. NL credits are assigned to the NL220 dongle and can be used on other PCs in "MOVED" mode. LNS credits are also necessary in NL220 to operate certain LNS applications such as the TAC Vista System Plug-in.   To order more Echelon LNS credits see Ordering more LNS credits. To order more Echelon LonMaker credits see Ordering more Echelon LonMaker credits. Resolution When working in NL220, it is wise to maintain a higher level of LNS credits than NL credits to help avoid locking out the LNS server license. To check the amount of NL credits remaining go to Start > All Programs > NL Suite > NLCreditsGenerator and look for Remaining NLCredits. The number of NL credits remaining can also be found at the bottom of the NL220 LonWorks Manager window with a project open. To check the amount of LNS credits remaining on a PC go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard and look for Credits Available. The number of LNS credits remaining can also be found at the bottom of the NL220 LonWorks Manager window with a project open.   To order more NL220 credits: Open the NLCreditsGenerator Utility that is installed with NL220. Go to Start > All Programs > NL Suite > NLCreditsGenerator > NLCreditsGenerator Utility. Enter the number of NL220 credits to be added  in the request area. Click Next. Click "Yes, this PC will be used for commissioning" Enter your name and contact details. Select "Copy to clipboard". Then either paste the information into notepad or in an email. Send the NL credit request to your local Schneider Electric Buildings Business order department  (NLCredits@buildings.schneider-electric.com). When you order has been processed by the local Schneider Electric Buildings Business order department you will receive an upgrade key. Open the NLCreditsGenerator Utility again. Go to Start > All Programs > NL Suite > NLCreditsGenerator > NLCreditsGenerator Utility. Click the Next button. Enter the key into the "Upgrade key" field of the credits generator. A message indicating you credits were added is then displayed.   Note: Once the request key has been generated, DO NOT commission or decommission any devices with the dongle until the upgrade key has been applied to the dongle. If devices are commissioned before then, the upgrade key will no longer be valid.

Issue How to get the XIF file of Xenta free programmable controllers? Product Line TAC Vista Environment Xenta Free programmable controllers (Xenta 281, Xenta 282, Xenta 283, Xenta 301, Xenta 302,  Xenta 301C, Xenta 302C, Xenta 401, Xenta 401B, Xenta 401C) TAC Menta editor Cause If Xenta free programmable controllers need to play as a third party device in another system, a XIF file is needed. Resolution Open the preprogrammed Menta file in the Menta Editor.  Note: If you are opening the file directly from the Vista database, it will first need to be saved to the local harddrive before generating an XIF. Go to Options > Simulate (or press F12) Go to Commands > Generate An XIF file with the same name as the .MTA file will be generated in the same location on the harddrive as the. MTA.   Alternatively, if you are connected live to the controller, you can also generate an XIF by connecting live: Open the preprogrammed Menta file in the Menta Editor. Connect the Xenta free programmable controller to the computer with a RS232 to USB cable. For details please refer to Downloading a Xenta Device Using Direct Connection to Menta Programming Tool. Go to Options->Simulate (F12), and select connect. A XIF file will automatically generated under the same folder that the Menta file is saved. NOTE: in order for third party system to be able to view points in Menta, those points need to be set as SNVTs.

Issue Xenta programmable controllers can communicate to each other using TAC Network Variables (TANV). These are defined in the Menta programming and travel on Xenta Group Bindings in the LNS environment. If data is failing to update in the receiving controller, there are a few troubleshooting techniques that can help. Product Line TAC Vista Environment Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta LonMaker/NL220 Cause TAC Network Variable communication can be compromised for four reasons: Network path not defined correctly in the Menta file Network path name is too long Group Bindings not done correctly in LonMaker/NL220 Controller's network output capacity has been exceeded Resolution Verify the Network Path If the network variable has been populated by browsing Menta files on the hard drive, or was entered manually, it can be the cause of the problem. Even visual inspection of the network path is not 100% reliable -- a lowercase "l" and an uppercase "I" appear the same, for example. The only way to be certain the path is correct is to browse it in through the Vista database. Open the Menta file from the Vista database. Right-click on the receiving controller and select Edit. Editing a Menta file directly from the hard drive of a computer does not give you the same network browsing options and can lead to incorrectly mapped network variables. Double click the network variable AI block and go to the Bind dialogue. Next to the Network Address text field is a browse button ("..."). Click it to open the network browse window. This tree structure should be the same as the folder view in Vista Workstation. Navigate to the sending controller's public signal and click okay. Download the application to the controller. Verify that the Network Path Name is not too long If the network variable path name, or the Network Address, is too long then this will cause a problem.The network variable path name, if the point is in a module, looks like ControllerName\ModuleName\PointName. If it is not in a module then it will have the Program Specification name instead of a module name. So it would look like ControllerName\ProgramSpecificationName\PointName.  If the ModuleName\PointName or ProgramSpecificationName\PointName part of the path is longer than 33 characters, counting the "\", then it will not work. Verify Group Bindings are correct Refer to Verifying Xenta Group Bindings in an LNS system for the procedure on verifying group bindings. If the group bindings are not correct, redo group bindings and download the sending and receiving controllers. Calculate the total output of the controller Depending on the controller type, there are different limits on the network variable outputs.  This includes both SNVTs and TANVs.  If together, they exceed the capacity, there will be spotty updates and random signals that don't make it to the receiving controller.  Unfortunately, there is no easy way to count the TANVs. In the Menta file of the sending controller, go to Options > Memory Usage... > Advanced... Make note of the TACNV/SNVT Out Free number.  Each SNVT output defined in the Menta file consumes one of these outputs and decreases the number of Free signals available for use with a TANV. The only way to count the number of network variable outputs is to know each receiving controller that is pointing back to the sending controller with a TANV.  Unlike with SNVTs, EACH signal in EACH receiving controller consumes one of these available outputs.  If the output limit has been exceeded, the communication will suffer. Reduce the number of network variables coming from one controller by "cascading" signals.

Issue Using STR-350 Bypass button as On/Off button in LNS Network Product Line TAC Vista Environment Vista STR-350 STR-351 Cause The Bypass button will only toggle the output of the nvoOccManCmd if the input nviEffectOccup matches the current button value. Resolution The STR-350/351 Sensors allow you to configure the Bypass button as an ON/OFF button but if it is not setup correctly it can get stuck in a single position. If using an application specific controller, the effective occupancy of the controller should be routed back to the STR-350 and bound to the nviEffectOccup. If using a 3rd party controller that does not have a SNVT for the effective occupancy, follow the step below. If using a programmable Xenta controller the nvoOccManCmd coming from the STR-350 should be bound to the programmable controller that with some logic programmed to follow the toggle of the button. Then that signal should be sent back to the nviEffectOccup of the STR-350. For the application used in the Classic network, refer to the Using STR-350 Bypass button as On/Off button in Classic Network.

Issue After updating Java, webstation doesn't show graphics. The window is blank/white. If the error you get is "Error. Click for details" and not a blank window, please refer to Webstation graphics not working after Java updated to Java 7 update 51. Product Line EcoStruxure Building Operation, TAC Vista Environment Java Webstation Cause There's an issue with Java and Webstation in SmartStruxure 1.5 when using panels. There's a hotfix available (1.5.0.2307) correcting this issue. Either Contact Product Support for this hotfix or download it on The Exchange Download Center. If panels are not used or the SmartStruxure version is lower than 1.5 or you are working with another product line such as TAC Vista, this article might help. This issue is usually only seen when updating an existing Java installation. If no version of Java has been installed previously, the issues doesn't seem to appear. According to Sun, there's an issue with the deployment.properties file. Read this article for further information. Resolution First try to install the newest version of Java. Version 1.7u67 has just been released, and is supposed to solve the issue. If you are using a x64 operating system, make sure you install both the x86 and the x64 version of Java in order to support both 32 bit and 64 bit browsers installed. If that doesn't work, try the procedure below. 1: Make sure all browsers are closed 2: Uninstall all Java versions 3: Make a copy of the file C:\Users\%username%\AppData\LocalLow\Sun\Java\Deployment\security\exception.sites (replace user_name with the profile name of the user logged into Windows) 4: Delete the folder C:\Users\%username%\AppData\LocalLow\Sun (replace user_name with the profile name of the user logged into Windows) 5: Install the latest version of Java (https://java.com/en/download/manual.jsp) - if you are using a x64 operating system, make sure you install both the x86 and the x64 version 6: Verify that you have the latest Java version and that you don't have older versions using the Java uninstall applet: https://java.com/en/download/uninstallapplet.jsp 7: Move the exception.sites file back into C:\Users\user_name\AppData\LocalLow\Sun\Java\Deployment\security (replace user_name with the profile name of the user logged into Windows) - if the directory doesn't exist, make the directories missing to complete the path 8: Try viewing TGML graphics again

Issue When a XIF file contains NCI's (SCPT's and UCPT's) default values (NVVAL) must be described in the XIF file. In some cases if NCI's are present, but some or all NVVAL initializers are missing commissioning the device will fail. For information regarding NCI's that are part of a FILE definition, please refer to Understanding the FILE part of a XIF file. Product Line EcoStruxure Building Operation, TAC Vista Environment LonWorks XIF Cause When commissioning a device default values to configuration variables must be assigned. If the tool (TAC Vista, SmartStruxure, LonMaker, NL220) does not know what default value to assign, it can cause an error. Resolution Make sure all NCI's have proper initializers defined. Read XIF file - NVVAL initializers.pdf guide as reference. Here is an example of a NVVAL section: VAR nciHrtBtRcv 2 0 0 0 0 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,0\x80,48; 107 * 1 4 0 2 0 0 VAR nciHrtBtSnd 3 0 0 0 0 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,0\x80,49; 107 * 1 4 0 2 0 0 VAR nciLocation 4 0 0 0 1 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,0\x80,17; 36 * 1 4 0 31 0 0 VAR nciDeviceName 5 0 0 0 0 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,6\x80,3; 36 * 1 4 0 31 0 0 NVVAL #VAR nciHrtBtRcv \x00,\x00 #VAR nciHrtBtSnd \x00,\x00 #VAR nciLocation = empty string \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00, \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00 #VAR nciDeviceName = empty string \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00, \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00

Issue After successfully logged into Xenta Server web pages, java loading icon will be displayed as shown below. However, after a while it will automatically log the user out as shown below. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers 5.1.6 (Xenta 511, Xenta 515, Xenta 527, Xenta 701, Xenta 711, Xenta 721, Xenta 731, Xenta 913) Java 1.6 update 29 Note: This behavior may happen on other Xenta Server versions with different Java versions. Please refer to the Cause section for the reason. Cause Vista may not support the newest Java versions. For Vista 5.1.6, the recommended Java version is Java 1.6 update 20. Please refer to Recommended Java version for TAC Vista 5 for recommended Java version details. Resolution Go to Start > Settings > Control Panel > Add or Remove Programs. Find Java application (in this example is Java(TM) 6 Update 29), and select “Remove”. Reload the Xenta Server webpage, will find the Java icon will not be displayed this time. Instead, “Download Java” request link will be displayed. Click on the link and download the supported version of Java. The issue should be solved after the recommended version of Java is installed.

Issue What version of Microsoft.Net Framework and ASP.NET is used by Webstation 5.1.9? Product Line TAC Vista Environment Vista Webstation 5.1.9 Cause ASP.NET is a web application framework developed and marketed by Microsoft to allow programmers to build dynamic web sites, web applications and web services. TAC Vista Webstation is developed using ASP.NET, which is a part of the Microsoft.Net Framework. Resolution TAC Vista Webstation uses Microsoft.Net Framework 4 and ASP.NET 4. For details on additional Vista versions and the .NET framework and ASP.NET versions required please consult the compatibility matrix in the Supported version of .NET framework and ASP.NET for Vista software.

Issue Verifying the Com Port on a PC is working properly by using "Loopback" test in Terminal Emulator. Product Line Andover Continuum, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Hyperterminal RS-232 serial port Cause The following test writes to the serial port and reads from the same port. This will verify the Full duplex operation of the RS-232 communication. Resolution Short the TX and RX pins of the cable (pins 2 and 3) following the pinouts below. Gender is determined by pin type.                Male DB9 (Left) and Female DB9 (right)   Launch Hyperterminal by selecting Start>>Programs>>Accessories>>Hyperterminal. If you do not have Hyperterminal, please read Hyperterminal on Microsoft Windows Operating Systems. If you are asked if you would like to install a modem, select No. Choose any icon and name the session, select "OK". In the next Pop-Up menu, choose direct to COMx (where x is the number of the COM Port you are testing.) Set the flow control setting to None. Leave the other settings to default settings, select "OK" Select File » Properties from the menu bar, select the Settings tab, and then push the ASCII Setup button. Check the option for Echo typed characters locally. Type something. If you see double characters the serial port is setup correctly and is functional. The display is showing characters that are sent out and what is read in. The Emulator will send and display the TX and immediately read and display  RX. If you see exactly what you are typing, you have a communication issue. which could be: Bad Com Port Bad cables Pins not shorted correctly If you are out of physical ports to try, use a USB Serial Port converter. If you are using a USB, use Reassigning a USB Serial Adaptor to a desired COM port for instructions of assigning Com to another port.

Issue Knowing the procedure to follow when hosting a site license for the first time with Vista. Product Line TAC Vista Environment Vista Licensing Cause The TAC licensing website is divided up into different areas depending on the task to be performed. An account must be created the first time using the site before creating a license file from the entitlement ID. Resolution Note: In order to rehost an existing Vista license file, see Rehosting a Vista 5 License on the FlexNet License Server. Log onto https://schneider-electric.flexnetoperations.com/flexnet/. Click on the link that says "New User?".   Fill out the entire page with your information. Insert the Entitlement ID that was purchased in the space titled "Activation ID". Once everything has been filled out, click Complete.   This will log you into the Start Page of the licensing site. A temporary password will be emailed to the address you provided on the New User page. This temporary password is required to set your new password which can be done by clicking on Profile in the top right corner of the screen.   Enter the temporary password into the "Old Password" field. Then enter your new password into the "New Password" and "Confirm Password" fields. Click Save.   On the left side of the Start Page, click "Activate" underneath Manage Entitlements.   Check the entitlement ID that you want to use and click Activate.  Fill out all of the information on this page. Click Next.   Click on "Add New Host" at the top of the Server Hosts panel. Select MAC address or Hardware dongle as the Server Hosts. Type in the MAC address of the computer or the dongle ID of the hardware dongle that the license file will be associated too and click OK. In order to find out the MAC address of your computer, reference How to locate a computer's MAC address.   Check the box next to the host name that was just added. Click Next.   Enter the number of licenses you would like to activate in the "Fulfill Count" box and click Verify. The file should verify successfully. Click Next.   Review all of the information. Click Generate.   Select the box next to the newly created license file. Either select to "Save to File" (save a copy of the license file to the local PC) or "Email License" (email the license file to a desired address). Click Complete.  

Issue The TAC Xenta group master is online but not the other Xenta devices in the group. Product Line TAC Vista Environment TAC Vista 5.1.x Classic network Menta 5.1.x Cause The TAC Xenta Group Master is a TAC Xenta 301/302/401/901 (in the TAC Xenta Group) that monitors the on-line and off-line status of the TAC Group and its members. The Group Master forwards the on-line and off-line information to TAC Vista. If devices have been added it's possible that  the current group isn't updated. Resolution The entire Xenta group must know it has a new device for proper communication to occur. To accomplish this download the applications and parameters to the entire group.  If the Group master goes offline, the whole group will be considered off-line by TAC Vista. The separate on-line group members, however, can send alarms and other information directly to TAC Vista as usual. Information about resolving this issue with an LNS network can be found in Xenta Programmable Device is Offline in Vista but Online in LonMaker.

Issue Many customers still have a requirement to run Lonmaker 3.13, but have project specific issues related to software fixes in newer version of LNS Server, and an LNS Server upgrade is required. Product Line TAC Vista Environment Echelon Lonmaker LNS Cause Older versions of Lonmaker 3.1 and LNS server had multiple defects that were addressed in later version of Lonmaker Turbo and LNS Server Turbo. However, it is possibly to run Lonmaker 3.1 and only upgrade the LNS server engine to take advantage of software fixes over time. Resolution NOTE: Any LNS Server version older than 3.10 needs to first be upgraded to 3.2x before 3.2x service packs can be installed. Also, please take into consideration that after upgrading the LNS Server on a system that any other system that needs to open that same database will have to be at the same version or higher. For example: a database upgraded to 3.27 can not be opened on the machine running 3.08.   Please follow these steps for upgrading LNS server to 3.22 and finally up to 3.27: Identify what version of Lonmaker and LNS server are currently running on the system. Please see How to determine what version of LonMaker and LNS Server on a computer for instructions on how to find the current version of Lonmaker and LNS Server currently running. As seen in the screen shot below the system is running Lonmaker 3.13.10 with LNS Server version 3.08. Download LNS Server 3.22. Once this file is downloaded please unzip all of the contents to the desktop of the local machine. Run setup.exe from the extracted files in the LNS Server 3.22.zip, and step through the installation process. Once the installation of 3.22 is complete please reboot the machine. After the machine has rebooted please verify that the system is now running LNS Server 3.22. Using How to determine what version of LonMaker and LNS Server on a computer for instructions on how to find the current version of Lonmaker and LNS server the system should now show LNS Server version 3.22 like below: Now that the system is upgraded from LNS Server 3.08 to 3.22, service pack 7 should be installed to upgrade the system to LNS Server 3.27. Please download LNS Server/Turbo edition Service Pack 7 file to your local machine. Unzip the contents of the LNSServerTurboSp7.zip to the desktop of the local machine, and run the LNSturboServerSp7.exe file. Step through the installation process. When the installation is completed please reboot the machine. After the machine has rebooted please verify that the system is now running LNS Server 3.27. Using How to determine what version of LonMaker and LNS Server on a computer for instructions on how to find the current version of Lonmaker and LNS server the system should now show LNS Server version 3.27 like below:

Issue When trying to add a Xenta 421A, 422A, 451A or 452A I/O module in Menta to a Xenta 300/401, the following warning is displayed. Tam32 Warning, IO modules of type TAC Xenta 421A, 422A, 451A and 452A requires at least system program version 3.6. Environment Menta Vista Xenta 301, 302, 401 Cause To utilize the full functionality of the "A" series I/O modules, the version of Menta and firmware in the associated programmable controller must be compatible. Resolution Use the Xenta 4XXA modules as old 4XX modules The I/O modules with an "A" in the name can be used with programmable controllers earlier than 3.61 as well as Menta earlier than 4.2.2 but the functionality will be limited. The functionality is limited to that of the modules' predecessors, modules without the letter "A" in the name (Xenta 421, 422, 451, 452). The TAC Xenta 421A/422A modules can only have digital inputs and the TAC Xenta 451A/452A modules can only have four 1.8k ohm thermistor and four limited universal inputs (digital input, 1.8k ohm thermistor or 0-10 V). In any running system with TAC Xenta 300/401 version 3.X, TAC Xenta 421, 422, 451, and 452 can be replaced with an "A" module the same way as an old module. The "A" module will detect that it is sitting in an old environment and behave as an old module. Use the full functionality of the Xenta 4XXA modules In order to gain full functionality of the "A" modules, the firmware in the Xenta 300/401 controller must be upgraded to a version 3.61 or higher and Menta must be version 4.2.2 or higher. Instructions on how to download a .MOT file can be found in Download an .MOT file into a Xenta Programmable controller. The additional features of these controllers include all inputs are universal inputs (0-10 V, 0-20 mA, 1.8k ohm and 10k ohm thermistor), universal inputs set as digital inputs can act as a pulse counter, and all configurations, inputs, and outputs can be accessed by means of the SNVT interface. Note: If updating the firmware in a Xenta 300/401 and the following conditions apply than see the Xenta Programmables section of The new program interface does not match the previously defined program interface. (Subsystem: NS, #59). Working on a database with multiple Xenta programmable controllers that reference the same device template A firmware version earlier than 3.52 is installed

Issue When installing the TAC Vista remote workstation, an error message is displayed. Details listed below: TAC Vista Workstation Remote Error 1935. An error occurred during the installation of assembly 'Integral.Common.SystemInfo, Version="7.0.70.0",Culture="neutral", FileVersion="7.0.70.0", ProcessorArchitecture="MSIL", PublicKeyToken="6853E3D8122788A2";. Please refer to Help and Support for more information. Product Line TAC Vista Environment TAC Vista 5.1.7 Workstation Remote (may happens to other version of TAC Vista Workstation Remote). Another version of Vista has been installed Cause When installing Workstation Remote the first time, it will automatically remove the other version of TAC Vista Workstation (ONLY) which has been installed earlier on the same computer. However, it will not remove other parts of TAC Vista (Vista Server, Menta, XBuilder, etc.) and causing the installation of Workstation Remote later crashes. Resolution Follow the instructions in How to uninstall and completely remove TAC Vista 5 to completely remove other parts of TAC Vista. NOTE: if you want to keep the SQL database, you can skip the SQL part.  Restart the computer.  Run the Workstation Remote installation file again. Now the issue should be solved. Corrupt Windows file system transaction log In some cases this error has been the result of the Windows file system transaction log becoming corrupt. Follow the steps found on the Microsoft support website forum to correct this issue.

Issue The following errors occurred in succession when trying to run LonMaker. Could not listen on poet/tcp: the address specified is already in use (-2532) Database error. (Subsystems: LNS, #25) [DB #-2506] The global database is not open. (Subsystem: LNS, #64) The following errors have also been seen to be caused by the same issue. Problem connecting with the database server process. (Subsystem:LNS, #36)[DB#-2523] Error opening LCA Global database. Problem connecting with the database server process. (Subsystem:LNS, #36)[DB#-2523] Environment LonMaker for Windows 3.1 and 3.2 Sentinel Protection Installer 7.6.1 Cause Sentinel Protection Installer 7.6.1 was recently installed on the computer. This is the driver for the Satchwell Sigma dongle key. The Sentinel Protection Server is installed together with the driver. The Sentinel Protection Server is use to manage the Sentinel SuperPro and UltraPro keys attached / installed on the system. This is causing a conflict with the POET Server as it uses the same port(s). Refer to Error: LNS #25 lcaErrDatabase for details. Resolution Stop the Sentinel Protection Server in Windows Services. In Windows, go to 'Start' > 'Run' and type in 'services.msc' to bring up the Services windows. Find Sentinel Protection Server and stop the service. This is not required for the dongle driver to work. You can also disable the service

Issue After TAC Vista Server is started, logging into TAC Vista Workstation, an error "Ensure that Vista Server is started" occurs. Product Line TAC Vista Environment TAC Vista Server TAC Vista Workstation TAC Vista Webstation Cause This issue is due to the DCOM permissions that Vista Server relies on and they must be manually changed. Resolution Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET contains a DCOM Utility that can automatically set the proper permissions to clear the issue. To manually alter DCOM parameters: Locate the DCOM config in Component Service > Computers > My Computer Right-click TACOS and selected Properties Select Security tab Click the Edit in Launch and Activation Permissions. Add the appropriate groups or user names of computer and Allow them permissions. After finishing the above procedures, the issue should be solved. Error: "Ensure that Vista Server is started" when trying to log into TAC Vista Workstation. The server is started. also discusses this issue.

Issue Switching from the Demo license to the Entitled License in Vista 5 Product Line TAC Vista Environment TAC Vista 5.X.X Cause In most cases the license will begin to work just fine after starting Vista and selecting "Use License Server" upon startup. For unknown reasons, Vista may need to be forced to ask you for a License File Or License Server option when Vista is first started after the license is switched. Resolution Unlike the Demo license, the site license must be placed in C:\Program Files\TAC\License Files (or C:\Program Files\Schneider Electric\License Files for TAC Vista 5.1.4 and above) and accessed via the License Server. It is imperative that the license file retains the .lic file extension, which importing to certain Windows environments may append a .txt extension to the filename The easiest way to force TAC software to use a License server versus pointing directly to the Demo License is to modify a registry setting of the Flexnet Licensing Software.   Start the Registry Editor from the Command prompt (type "regedit" in the start menu run box) and navigate to HKEY_LOCAL_MACHINE>SOFTWARE>FLEXlm License Manager.  Modify the TACLIC_LICENSE_FILE string and delete the Value data. By leaving this key empty, the next time you start any TAC software you will be prompted to "Specify the License Server System" or "Specify the License File".  Start a TAC Software package that requires a license.  Select "Specify the License Server System" and enter the computer name preceded by an "@" symbol. If the License Server resides on the local machine, "@localhost" can also be used. Note: In more recent versions of License Server, the "@" symbol is optional. If in doubt, putting it in will work with all versions. If the changes were successful, the registry entries should appear as follows (in a typical installation). If registry settings are different that the ones below, please contact Product Support Services.   If the above changes were performed but the License fails to read,  in some cases the License Server system will not work properly until rebooting the PC. If unable to read the license use LMtools utility located in the TAC Tools to troubleshoot the issue. If additional assistance is needed for using LMtools, watch the video overview published in Vista 5 Macrovision/Flexnet Licensing: Lmtools diagnostic utility overview. For help with Vista versions >5.1.7, see License troubleshooting in Vista 5.1.8 or greater

Issue View the current firmware version on a Xenta controller using the RS-232 cable Product Line TAC Vista Environment Vista 5.1.X Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B, 901 Cause While it is the best practice to match all of the firmware versions in your controllers, this is a quick and easy way to view the current version installed on your hardware.  Resolution Connect the RS-232 programming cable to your controller and your PC Open TAC Tools 5.1.X Open Download Wizard Click next Click the information button located directly above the help button For more information on how to update the firmware (.MOT file) on a Xenta controller, see Download an .MOT file into a Xenta Programmable controller. For more information on Menta Cable needed to download, see Schematic for the RS-232 cable used to direct download Menta applications and system files.