Issue Cannot get the Site license to run after downloading and installing it. Product Line TAC Vista Environment Vista 5.X LMTOOLS Cause TAC Vista 5 license needs to be recognized by the licensing server (FLEXnet License Server). Sometimes, license needs to be set up manually using the LMTOOLS software. Resolution Please follow the steps below to manually read the site license. Stop and close TAC Vista Server, Workstation, etc.   Generate the License file at schneider-electric.flexnetoperations.com and insert the .lic file into C:/Program Files/Schneider Electric/License Files folder (default path, for TAC Vista 5.1.3 and prior, the default path should be C:/Program Files/TAC/License Files) .   Open the LMTOOLS utility from the Start menu: All Programs/Schneider Electric/TAC Tools 5.x.x/LMTOOLS (for TAC Vista 5.1.3 and prior, use path: All Programs/TAC/TAC Tools 5xx/LMTOOLS).   Under "Service/License File" tab, make sure the "Configuration using Services" choice is selected and "TAC License Server" choice is highlighted.       Under "Config Services Tab", ensure the path to licenses file is correct (C:/Program Files/Schneider Electric/License Files, by default). Browse to the folder if necessary by using the "Browse" function. Make sure "Start Server at Power Up" and "Use Service" choices are checked.   Under "Start/Stop/Reread" tab, check "Force Server Shutdown" box. In order click, "Stop Server" (wait a few seconds, there will be no message when the server stops), "Start Server", "ReRead License File". You should receive a message stating the ReRead License File Completed.   Start any TAC application other than Vista Server (for example: TAC Menta). You will be prompted to "Specify the License Server System" or "Specify the License File". Select "Specify the License Server System" and enter the computer name preceded by an "@" symbol. If the License Server resides on the local machine, type "@localhost". Note: In more recent versions of License Server, the "@" symbol is optional. If in doubt, putting it in will work with all versions. If you are NOT prompted to "Specify a License Server" in Step 7, Please follow the instructions in Switching from the Demo license to the site License in Vista 5.1.7 or older. At this point the License should read correctly and the licensed Vista products should execute. If the license continues to fail, reboot the computer and try to open a Vista product again (for example: TAC Menta). If the license if still failing, please verify the above steps again before contacting Product Support. For additional information about the LMTOOLS software. Please go to What options are NOT supported by Signal XP?.

Issue Monitor the online status of a base unit's associated I/O modules Product Line TAC Vista Environment Menta Xenta programmables Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Xenta I/O Modules Cause Alert the end user to communication failures between a Xenta programmable base unit and its associated I/O modules. Resolution Add a DI block to the Menta program. Name the DI point Click the bind button and choose online device. Within the device address box, enter the I/O module number. For module 1, type 1. For module 2, type 2, etc. Also, attached is a Menta macro that contains code for 10 modules. If there are less than 10 modules, remove the unnecessary points / alarms. Note: Any I/O module defined in the Device Specification that has no hardware inputs or outputs assigned to it in the Menta application will always report an offline status.

Issue The time in TAC Xenta Server should be the same as the time on the TAC Vista Server PC. When Xenta Servers connect to the TAC Vista Server, they should synchronize their time with the Vista PC. Product Line TAC Vista Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 NTP Server Vista Server Cause There are different scenarios. Vista Server PC has no internet connection Vista Server PC has internet connection Resolution Corresponding to the causes above: Set the Xenta Server to synchronize with the Vista Server PC. You do that by adding this AuthoritativeNTPserver.zip reg file to the registry on the TAC Vista Server PC, and enter the IP address of the PC into the Xenta Server as described in Setting NTP in Xenta Server.pdf. Set the Xenta Server and the Vista Server PC to synchronize with a NTP server on the internet. Find servers here: http://support.ntp.org/bin/view/Servers/NTPPoolServers Area HostName Worldwide pool.ntp.org Asia asia.pool.ntp.org Europe europe.pool.ntp.org North America north-america.pool.ntp.org Oceania oceania.pool.ntp.org South America south-america.pool.ntp.org In general, make sure that firewall is not an issue. NTP uses port UDP 123

Issue SNVT_flow will not display correctly in Imperial units on a TGML graphic on a Xenta Server Product Line TAC Vista Environment Xenta Servers version 5.1.1 or earlier Xenta 511, 527, 711, 731 Cause SNVT_flow will only display on TGML graphics as liters per second regardless of what unit the signal in Xbuilder is configured for when sent to the graphic page. This is a bug and has been reported. Resolution This has been corrected in version 5.1.2. Upgrading to 5.1.2 or later will resolve this issue. If upgrading is not an option, the conversion can be done in a script element of the TGML graphic page. This LS to CFM Snippet can be used to modify a numeric or text presentation object.

Issue SNVT_press_p will not display correctly in Imperial units on a TGML graphic on a Xenta Server Product Line TAC Vista Environment Xenta Servers Xenta 511, 527, 711, 731 Cause There is a bug with the TGML graphic editor that causes a SNVT_press_p to only display in the SI units of pascals. Resolution Until this issue is corrected you can manually convert the value on the graphic page using a JavaScript. This Pascal to H2O Snippet can be used to modify a numeric or text presentation object.  

Issue After upgrade of Xbuilder or opening a project built on another computer generating the project causes a "File not found:" error message.   Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment XBuilder Cause Find the alarm or event page that is causing this problem and view the reference field to identify the cause of the problem.   XBuilder was upgraded and the xmle files from the previous version are no longer present. XBuilder installation directory was on a different drive on the computer the project was last used on. Resolution In Xbuilder, right click on all the Alarm and Event pages, select Change reference, and browse in the new path to the referenced file.  

Issue Echelon now has an easier way to check the status of your LonMaker License. Determine the status of your credits in seconds. Product Line TAC Vista Environment LonMaker 3.1 LonMaker 3.2 (Turbo) LNS Cause Determine corrupted credits/licensing issues without the old method of using the command prompt. This will do the same thing with a click of a button. Resolution The tool will diagnose the license status and give you the solution you need to follow to fix the problem.   Download here: Echelon License Diagnostic Utility Save or run Choose LonMaker credits Copy to clipboard and email to Echelon if corrupted credits are shown. Screen shot of invalid LonMaker license:   This error occurs if the license file you specified is not located in the application directory. To resolve this, you will need to reboot your PC and log in as a user with Administrative privilege. Next, make sure the files listed below are located in the C:\Windows\LNS Licenses folder. Note that the "LNS Licenses" folder is a hidden one; therefore, in Windows Explorer, go to Tools - Folder Options..., and in the View tab, select "Show hidden files and folders." Now uncheck the "Hide protected operating system files (Recommended)" option.

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   Error message: "Failed to run DcuXml.exe" when importing I/NET .sav files into XBuilder Product Line TAC INET, TAC Vista Environment XBuilder 1.6.0 Cause When XBuilder imports I/NET save files, it does a simple batch of all of the save files for the import process. It creates a path for the import into XBuilder. A typical path might look like this: C:\TAC XBuilder Projects\MyProjectName\Files\INET\dcu0102,dcu0103,dcu0104 This example shows the import of 3 I/NET save files with a character length of 72 for the batch process. This process is limited to 2048 characters. Importing 15-20 save files will cause a crash.   Resolution To squeeze a few more save files into XBuilder, shrink that path as much as possible. For example: Rename the default "TAC XBuilder Projects" folder to something shorter. Rename the project to something shorter. Move .sav files to another location, even temporarily to the C:\ drive root to eliminate extra path data. Example:  C:\XBPrj\MyPrj\Files\INET\dcu0102.sav.  This path shrinks the directory at the front end to allow for more save files on the backend.

Issue Modbus (or other 3rd party communications protocol) not displaying correct value even though coefficients (gain and offset) have been defined Product Line TAC Vista Environment XBuilder Device Template Cause The Xenta 913/731 uses an abnormal equation when applying the coefficient in device templates for 3rd party interfaces: y=m(x+b) Traditionally, the slope-intercept form is used when applying a coefficient: y =mx+b This means that the gain in the coefficient is applied after the offset rather than before it. Resolution If you have the information that fits a traditional slope-intercept form and need to apply a coefficient in a XBuilder device template then use the following as your variables where m and b are from the slope-intercept form equation: Gain: m Offset: b/m The following is an example of one manufacturer's specifications for its Modbus values and how to correctly enter them into the device template: For a temperature sensor reading that is being sent as a Modbus point a certain manufacturer specifies that to correct the raw value the following should be used: Gain = 0.1 Offset = -40   However, the manufacturer assumes the standard slope-intercept form will be used, so entering the data without any adjustments would cause the value to be converted incorrectly in the Xenta Server. For example, if the temperature was 80 °F then the raw Modbus value would be 1200 and the Xenta Server would apply the coefficient as y=0.1(1200+(-40)), simplified as y=120-4. This means the Xenta Server would return a value of 116 °F instead of 80 °F.   In order to fix this the offset should be multiplied by the gain in order to compensate for the difference in how the Xenta Server utilizes the coefficient compared to how the 3 rd party manufacturer intended it to be used. So the following would be used: Gain = 0.1 Offset = (-40)*0.1 or -400   Now, with a temperature of 80 °F the raw Modbus value will still be 1200 and the Xenta Server will apply the coefficient as y=0.1(1200+(-400)), simplified as y=120-40. The Xenta Server now returns the correct value of 80 °F.  

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 Downloading new NXE or APB files using NL220 Product Line TAC Vista Environment NL220 Cause Downloading new or old firmware versions into application specific controllers. Resolution Before performing this update, make a backup of the NL220 project. In case something happens and the configuration parameters are lost, there will be something to reference. Go to extranet and download the latest NXE and APB files. In NL220, right click on the controller to be upgraded and go to Network > Upload configurations. This will update the database with the current configuration in the controller.   Next, right click on the controller again and go to Network > Replace. A box will open that is titled Commissioning a node. The option "Upload configuration from old node if present" should be checked. This will insure that the values in database are current with the controller. Under Configuration download, "Download all known database values" needs to be selected. This will download the configuration parameters back into the controller once the update is complete. Finally under Template, "Download a program to the node" should be checked. The file that was downloaded off of extranet earlier can now be browsed in. Note: The option ‘Keep current configuration on node’ is misleading. By selecting this option it will not download parameters to the node. So when you download the new APB file, the controller will retain the configuration parameters found in the APB file not what was originally on the node.   Click Continue

Issue TAC Vista Error Codes in Plain Text Product Line TAC Vista Environment TAC Vista Server TAC Vista Workstation Cause Vista will sometimes give an error code. This list decodes the Vista Family Error Codes. Resolution For a list of TAC Vista Error Codes in plain text click here.

Issue ZBuilder allows for configuration of heating and cooling setpoints as well as PI gain and terminal load deadbands. However, sometimes these parameters can mask the actual activation and deactivation temperature points for heating and cooling outputs. Product Line TAC Vista Environment Xenta 121 ZBuilder Cause Figuring out where a Xenta 121 will turn on stages of heating or cooling can be a bit confusing, especially in °F. If you're not careful, you could have the heat operating until the space temp crosses the cooling setpoint at which point, the unit will switch to cooling and turn on the cooling stage(s). Resolution Click here to open a spreadsheet that will calculate the proportional bands and the activation points of the heating and cooling stages. Select the tab that describes the cooling/heating application set in ZBuilder Enter the temperature setpoints, gain and hysteresis settings and the value of nviSetpoint if it is being used. Ensure that cooling/heating bands are not inverted or overlapping to ensure proper operation of the Xenta 121.  

Issue TGML Graphic does not display. Shows only a red X Xenta Server TGML Graphics not updating following XBuilder download Miscellaneous Java error messages Product Line TAC Vista Environment Xenta 511, 527, 711, 731 TGML graphics XBuilder Cause Dynamic TGML graphics are rendered in the web browser using a Java applet. Java on the PC will store applets and graphics in its cache for faster load times. This can sometimes be problematic as changes are being made -- either to the graphic source files or the firmware version of the Xenta Server. Resolution Clear the Java cache before loading the page again: Open the Java Control Panel If viewing a Java page, the icon for the control panel will be in the task bar of the PC. Double click it. Otherwise, go to Start > Control Panel > Java. On the first tab, General, see the third box item, Temporary Internet Files. Click Settings...   Click Delete Files...   Select both "Applications and Applets" and "Trace and Log Files". Click OK, and exit the Java Control Panel   Reload the graphic.

Issue Every time the computer reboots, LMGRD errors are shown at startup.   LMGRD encountered a problem and needed to close. lmgrd.exe - Application Error The instruction at "0x0012e854" referenced memory at "0xffffff91". The memory could not be "written". Product Line Other, Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Vista Server 5.0 FlexNet Licensing Remote Alarm Manager Sigma BAS2800+ Micronet Errors Cause There is a known issue with the new license server from Flexnet. The LMGRD.exe is actually crashing during shut down of the PC. Resolution This is nothing dangerous. What happens is that when you turn off the PC, something is happening with the license server during the shutdown phase. Since LMGRD runs as service, it can not display this error message during this shut down. The error message is shown the next time the PC is started. It will not affect anything since the error messages is queued from the last shutdown sequence, NOT during the startup. We think it has something to do with having a license server installed and not using only an entitlement license. In some situations, placing a customer license file from any project into the license folder along with the monthly demo license stops the LMGRD error. The license server may read the customer license, note that it is invalid, then use the monthly license. Flexnet is looking into this issue. Look for a fix in upcoming versions. On Sigma, BAS2800+, and Micronet systems where Remote Alarm Manager is installed, the TAC license server can be uninstalled as it is not used.

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 for assistance. Issue Error: "Could not create remote directory" or "Failed to establish connection with the target device" when trying to upgrade/downgrade a Xenta 5/7/9xx controller     Product Line TAC INET, TAC Vista, Satchwell MicroNet Environment Xenta Servers Xenta 511, 527, 527-NPR, 555, 701, 711, 721, 731, 913 XBuilder Cause This error can be caused by any of the following reasons: Trying to downgrade a Hardware version 2.x Xenta Server device to System Program version 2.10 or older Internet Options are configured to use a proxy server IP communication is not properly established due to incorrect IP settings, a bad cable or a faulty device The controller is 5.1.8 or lower and Microsoft KB 2661254 or KB 2661254-V2 is installed on the PC. In this upgrade Microsoft has changed the criteria for the certificate Key. Service packs are available on the extranet to correct this issue. Download blocked because of other Windows updates SSL 2 and 3 is not activated Resolution First, establish that the System Program that you are attempting to load is compatible with hardware version of the device. The older HW 1 versions can be upgraded to System Program 5.1.2 or older. Only system program versions 2.2.0 and newer can be loaded into devices that are hardware version 2.X. Hardware Version System Program 1.0 5.1.2 or older 2.X 2.2.0 or newer 3.X 5.1.6 SP1 or newer Note: Hardware version 1 devices are not labeled as HW 1 since only one version of hardware existed at the time. Hardware devices can be identified by the lack of any hardware version printed on the Neuron ID sticker. Note: If running the firmware update software, ensure you are running as an administrator. Next, check to verify that IP communications are configured properly and are functional: Check the IP address defined in XBuilder Verify a good connection to the IP port of the controller (10Base-T port on the far right) with a crossover cable. If that is all good, then a reformat of the controller may be necessary. Connect via Hyperterminal to the unit and at the dsh> prompt type format and press enter command . This will recreate the directory structure of the controller and allow you to attempt the upgrade/downgrade again. Finally, verify that the Internet Options are not configured to use a proxy server or, if they are, temporarily change them as follows: To temporarily change this setting follow these steps: In Internet Explorer select the Tools Menu and select Internet Options. Or select Internet Options from your Control Panel. Go to the Connections tab. Click the LAN settings button. Uncheck the Use a proxy server for your LAN box. Click Ok in the LAN settings window and the Internet Options window. Complete the System Program download. Return to the Internet Options window and re-check the Use a proxy server for your LAN box in the LAN Settings found in the Connections tab. Another Matrix explaining the compatibility of each with Vista versions can be found in Xenta-Server-firmware-versus-Vista-Server-versions If you have the Xenta FW 5.1.8 or lower and KB 2661254 or KB 2661254-V2 were installed during a Windows Update you will need install the service packs. These new service pack builds have been released and are available on the extranet. See TPA-VSTA-12-0028.00 - TAC Xenta Servers, Not Possible to Download Firmware for more info. Another issue has been reported to support relating to the bit length of the Xenta server boot certificate. The Xenta server installer uses a 512 bit key length of the boot certificate, and Windows in some instances can be configured for a 1024 bit length certificate. If the issue still exists after removing the above mentioned Windows Updates, or if you are getting this error and the Windows Updates are not on your machine. Download the attached tool, Allow Weak Certificates.zip, and execute the file, chose "Allow Weak Certificates", and "Update".   Here is what the tool set: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\OID\EncodingType 0\CertDllCreateCertificateChainEngine\Config] "EnableWeakSignatureFlags"=dword:00000002 "minRSAPubKeyBitLength"=dword:00000200 If taking the preceding steps fails to resolve the issue then see the following articles for additional steps that can be taken: Xenta Server "Run" light is solid red, with no communication via Ethernet,  Fail to upgrade the TAC Xenta Server system software (firmware)  An unexpected error occurred while downloading using a Xenta Server

Issue The standard graphic object does not exist in Vista 5 the same way it did in previous versions so an alternative method for creating a standardized graphic is necessary. Product Line TAC Vista Environment Vista Workstation TGML Graphics Cause The standard graphic object does not exist in Vista 5 as it did in earlier versions. Relative bindings and shortcuts replicate the functionality of having one graphic source file represent data from several different pieces of equipment. Resolution There are a couple of alternative methods to creating a standardized graphic that will work where many identical or similar devices exist. Below is an example of the first method. The scenario is a site where multiple Xenta 121 devices exist and each need individual graphics. In Vista Workstation locate the first Xenta 121 device in the folders pane on the left and right click and select New > Object > Graphic - TGML to create a new graphic that resides in the controller object.   Create a standardized graphic that uses naming conventions that are common to all of the devices that will use the graphic. In the example the actual SNVT names from the Xenta 121 are used for the point names. When the graphic is complete, save it and create the graphic bindings to the controller where the graphic resides.   From the bindings pane select all of the bindings then right click and select Apply Relative Address.   The addresses on the bindings will now only contain references to the points within the controller but will not have any reference to the controller name as shown below.   Close the bindings window and right click the graphic object and select copy.   Right click on the next device and select Paste Shortcut. Repeat this step for all of the relevant devices.   Now, clicking on the shortcut to the graphic from any of the devices will open up a copy of the graphic that is bound to the device in which the shortcut resides. The other is similar but places all of the shortcuts to the graphics in individual folders rather than down in the devices. It also requires that shortcuts be made in the folders to each of the devices. Create a graphic (use this graphic as a standard graphic) with relative bindings. Create folders for e.g. every room. In this folder, add shortcuts to the controllers, also add a shortcut to the graphic (with the relative bindings). By doing this you can have the function of "TGML standard Graphics" as in earlier OGC graphics.

Issue Problem changing values in Echelon LonMaker Product Line EcoStruxure Building Operation, TAC Vista Environment Echelon LonMaker Echelon Browser Plugins Cause When using Echelon Lonmaker, verify the PC's regional settings have the decimal sign set as a dot (period) and not a comma. Resolution Go to Start > Control Panel > Region and Language Click the Additional settings... button Under Decimal symbol, make sure this is a period and not a comma.

Issue Create smooth rotation for an object in a Vista TGML graphic Product Line TAC Vista, EcoStruxure Building Operation Environment TGML Graphics Editor Cause If the "CalcMode" is set to "Discrete" the object will rotate the full specified range instead of taking the duration time to slowly move around it.  Resolution Add a <rotate> tag to the object that will be rotating. Add an <animate> tag to the rotation. Set the properties for the animation: Animation = default state (Start/Stop), if a binding is ultimately used to control when the animation occurs, bind to this attribute. AutoReverse = should the animation continue in one direction or get to the end of the animation and then come back to the beginning? (True/False) CalcMode = determines whether the animation is smooth or jumps from end point to end point of the animation. For rotation, choose Linear. (Linear/Discrete) Duration = the amount of time in seconds that the animation should take. Higher numbers result in slower animation. Freeze = if true, the animation will pause at the last position when Animation is set to False. Otherwise it will revert back to the starting position. (True/False) Repeat = how many times should the animation occur. Default value is "Forever" but this value can also be set to any integer number (1, 2, 3, 4...) From, To = depend on the desired animation and target attribute. For rotation 0 to 360 is typical. Attribute = for rotation, the Angle property of the <rotate> tag is animated from 0 to 360 degrees. For more information on CalcMode see ‘Animation Overview’ in the Help.

Issue Xenta 102-ES Flow Calibration Plug-In Error An error message is generated that reads: Balancing Error Errors occurred during balancing and values for nciBoxScale, nciNomFlow and nciBoxOffset and values have been reset. This can be caused by air flow not being stable during the balancing process, or due to incorrectly measured values. Returned values were: nciBoxScale = XXX, nciNomFlow = XXX, nciBoxOffset = XXX. You should try doing the balancing process again.   Product Line TAC Vista Environment Xenta 102-ES Plug-In Cause If the Lonmaker plug-in for the Xenta 102-ES gets a negative result on nciBoxOffset during calibration, the "Apply" button can be hit and all works fine. However if the plug-in is closed and then re-opened, the flow page will show values that do not match what was calibrated to. Resolution Do not make any adjustments or changes after the device has been calibrated.   You should hit cancel if you go to the flow page after a box has been calibrated and not Apply. If you do hit the "Apply" button, it corrupts the data in the device and you will need to re-calibrate. Also if you want to check flow values on a box after a calibration has been done, do so in Vista or in the LonMaker Browser, not through the plug in flow page.