Issue The Exchange Download Center contains all of the assets you once accessed through the Buildings Extranet are now available on a brand new platform. It's easy to search and fast to download. Stay tuned for more great features as we roll this into the all-new extranet solution for Buildings. We ask that you register for a new account on The Exchange.   Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Other, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Exchange Download Center Cause You can utilize the new Buildings web experience from The Exchange. Resolution Navigate to https://ecoxpert.se.com/ * Use a modern browser for the best experience: Google Chrome, Mozilla Firefox, Microsoft Edge, and Microsoft Internet Explorer version 8 or later. If you receive the following error in Internet Explorer despite using version 8 or later, the browser displays the page in Compatibility View. Click here for more information on Compatibility View and how to disable it. The Download Center will not function properly in Compatibility View.   On the header bar, you will see the option in the top right corner for “Login / Register.” Click it.   If you are already registered, enter your email address and password. If this is your first time registering, click the link for “New to the Download Center? Register here!”   Answer whether or not you are a Schneider Electric employee using the radio buttons. If you are a Schneider Electric employee, enter your SESA ID and your desired password for The Exchange. Click to accept Schneider Electric’s Terms and Conditions and hit “Create Account.” * The first time you register, you must be connected to the Schneider Electric network or connected via VPN. This is only required at registration. All future logins can be done externally. If you are not a Schneider Electric employee, enter your first name, last name, company name, location, business email address, and desired password for The Exchange. * It is important to use your business email address if you are a licensed partner. Your email address is used to automatically validate your Partner status and assign the correct permissions to your user profile.   An email is sent to your designated inbox with a link to click through and validate your email address. Once this is done, your login is created, and you are ready to start using the Download Center. * If an error is displayed when trying to validate your authentication code, please try to log in. This happens when an email address has already been verified and oftentimes does not indicate an error with the registration.   Once logged in, you can search and download assets available to your user profile. If you attempt to download a file that you do not have access to, you will be given a chance to report if this is in error. Your username, email, and the asset you are trying to access are recorded. Please enter a message if any further description is required and hit “Submit.” A member of our team will get back to you promptly with a resolution. Web Site Support For any issue regarding The Exchange Download Center, please contact us at exchangesupport@schneider-electric.com.

Issue The License Server is not working and may show Vendor Daemon Down errors. The LMadmin log shows the error. LicenseEngine (taclic) exited with status 28 Product Line TAC Vista Environment Vista License server Cause DEP is activated. Antivirus or other software can scan/use the port used by the vendor daemon. If the time drifts over two minutes and a time synch occurred, the vendor daemon can stop. https://support.citrix.com/article/CTX137111 Resolution First, check so DEP is not activated. Make sure that there is no antivirus program that has portscan activated Make sure there is no other software that uses the same port as the vendor daemon Make sure that the time does not drift too much, if the time drift two or more minutes and then resynch the vendor daemon can stop This is more true on VMware that can make time synch from either the domain or VMware tool. Check Windows event log (Security) for time synch messages. NOTE: It can also appear just by stopping the server manually.

Issue Error message "The Parameter is incorrect" when clicking OK in TAC Vista Server Setup Emailing alarms from TAC Vista is not working Product Line TAC Vista Environment TAC Vista Server Setup Cause The text encoding method has not been selected. Resolution Open TAC Vista Server Setup Click on the Mail Tab Check if the Text encoding Field is empty. If it is, select an encoding from the dropdown. Unicode (UTF-8) is suggested in the US with an Exchange Mail server.

Issue Getting error message when selecting Character set file for the TAC  Xenta Operator Panel (OP).     Product Line EcoStruxure Building Operation, TAC Vista, Xenta OP Environment TAC Xenta OP EcoStruxure Building Operation Microsoft Windows 10 Cause Microsoft Windows 10 does no longer allows the software to change files in all directories. Resolution Manually open up the directory C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 3.2\WorkStation\CharSet.lib Select the Charset you want to use, depending on the language, and copy the file. Remove the extension, so that the file is named Charset, without any extension. Manually open up the directory C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\WorkStation\Function Block Editor Paste the copied file here.

Issue TAC Xenta 300 devices without /N/P (networking and presentation) could be upgraded by ordering an upgrade from the factory. Example of a 302/N/P label. Example of a non-/N/P 302 label. Product Line TAC Vista Environment TAC Xenta 301, TAC Xenta 302 Cause TAC Xenta 300 controllers without the /N/P do not have functions for networking or to be connected to a presentation system, like TAC Vista. Resolution TAC Xenta 300 controllers without the /N/P could be upgraded to /N/P by following the process described in the attached datasheet.

Issue The Optimum Stop feature of the OPT function block in Menta / Building Operation Function Block Editor does not auto-adjust, even when the auto-adjust parameter is enabled. Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 281 Xenta 301 Xenta 401 Menta FBD Cause This behavior is by design, although it is not made clear in the Menta documentation.  The auto-adjust feature only works with Optimum Start, not Optimum Stop.  The optimum stop time is calculated from a fixed Outside Air Temperature vs time curve.  As some compensation, both end points of the curve are manually adjustable for both time and temperature.  For the optimum start, only the time parameters of the curve end points are manually adjustable. Resolution The optimum stop curve must be manually adjusted over succeeding days until an acceptable stop time is achieved.

Issue Can not get my TAC Xenta 300 controller, which does not have the /N/P, online in TAC Vista. How can I download the application to a TAC Xenta 300 device that does not have /N/P? Product Line TAC Vista Environment Vista Server Vista Workstation Xenta 301 Cause TAC Xenta 300 devices that are not marked with /N/P could not come online in TAC Vista. Resolution Even if the TAC Xenta 300 devices that are not marked with /N/P (does not have Network or Presentation system functionality) could not come online in TAC Vista, it is still possible to download the address and application to it, by the use of TAC Vista. Just add the devices as normal, and select download to the device. The device will however not come online in TAC Vista, but you could still download the application. Please do not forget to store a backup of your project.

Issue The status of a TAC Xenta 301 or 302 does not go 'online' in TAC Vista, although the Neuron Status property of the controller is 'online' and 'Commission and Download' from TAC Vista is apparently successful. Values read "Failed to Read Signal" in a values page of a classic network. Values read "Invalid Address" in a values page of an LNS network (also see [Invalid Address]) Controllers without /N/P (networking and presentation) designation cannot communicate in a Network. Product Line TAC Vista Environment Vista Workstation Vista Server Xenta 301 Cause Attempt to commission a standalone (non-/N/P) TAC Xenta 301 or TAC Xenta 302 in a TAC Vista Classic LON network.  Non-/N/P controllers are designed to run stand-alone and be configured/interact only with a Xenta OP. Resolution Check the sticker on the side of the controller where the controller type, hardware version, and neuron ID are found. Example of a 302/N/P label. Example of a non-/N/P 302 label.    If the sticker does not have /N/P following the controller type, this is not a network presentation controller.  It will never communicate on a network Replace the non-/N/P controller with an /N/P enabled version.

Issue Online Device shows "0" for one scan, but the device is still online from TAC Vista. This is enough for the unit to stop and close dampers. Product Line TAC Vista Environment Vista Server Xenta 281 Xenta 301 Xenta 401 Cause The Online Device function depends on your network.  If two controllers are within the same TAC Xenta group, there should be no extra traffic the asking device could just check in the online table if the other device has sent out its poll lately. If it is outside the actual TAC Xenta group, it will be like a TACNV connection, within the limits for TACNV. However, there are no re-sends. A single missed message will result in an Offline status. If there is a lot of traffic, there could be a collision on the network traffic and this could result in an Offline status. The next scan time, the messages might work correctly again, and resulting in online status. Resolution The best solution is to have a Delay block in the TAC Menta code, to get a delay-off (when the value goes from Online (1) to Offline (0)). Make sure the device is offline for at least a few program cycles before taking any action in the application program logic.  

Issue What is "Verbose" within Vista Server Setup? Documentation refers to "certain dialogs and messages." What are these certain dialogs? Product Line TAC Vista Environment TAC Vista Server Setup TAC Vista Workstation Cause The documentation states that this setting: "Enables or disables the display of certain dialogs and messages for operator communication."  Resolution Verbose turns on questions that ask if you really want to do something. An example, "Do you really want to quit?" when closing Vista server.

Issue An unexpected database error occurred. "There can only be one LCA Object Server ActiveX control per process. Please make sure that you only have a single Object Server control in this process." "Could not listen on _poet/tcp: The address is already in use or another server already running. (-2532)" Environment LonMaker NL220 Vista LNS Cause Microsoft Exchange 2003 Server and other OEM software sometimes use TCP ports 6001 or 6002. This causes a conflict since the POET server (FastObjects DB) defaults to TCP ports 6001 and 6002. Resolution For an automated solution, refer to: https://community.exchange.se.com/t5/TAC-Vista-Forum/LonMaker-POET-Port-Changer/td-p/271427   For a full explanation from Dialog Semiconductor, refer to: https://edgesupport.diasemi.com/hc/en-us/articles/206494283   Further details   Check that the ports used by LNS are not being blocked (firewalled) or used by another application. To verify this, type in the following command from a DOS prompt: netstat -bn You should now get a list of in-use TCP ports. Look for an entry saying {your computer name}:6001 or 6002. If you find one, you have located a conflict and you will need to change the POET Port numbers. Check if you run a firewall on this PC. If yes, you need to find the list of Programs with their Internet Access level and make sure you have given access to the appropriate files. To run LonMaker/LNS , you need to give access to ptserv32.exe, LonMaker.exe, lonpoint.exe, visio.exe, lmwbrw32.exe and lsass.exe. You can modify the ports used by the POET server and clients by modifying the "Services" file (%WINDIR%\System32\Drivers\Etc\Services) using a text editor like Wordpad.exe or Notepad.exe. For example, to change the POET port numbers to 7001 and 7002, add/modify the following lines in the "Services" file. The  '#' in the example indicates that the following text is a comment. For Win XP: use "Windows\System32\Drivers\Etc\Services". If you see the "poet" and "_poet" entries, go ahead and change the port numbers from 6001 and 6002 to 7001 and 7002. If you don't see these entries, simply add the lines below. poet          7001/tcp    #FastObjects services _poet        7002/tcp    #FastObjects services https://echelon.force.com/support/s/search/All/Home/562?tabset-95728=2

Issue Double click on a point in Vista. The Edit Properties window should pop up allowing you to view the value, set the Forced-By-Operator setting, and set the forced value. Sometimes double clicking it does not open any window. Product Line TAC Vista Environment Vista Workstation Double or dual monitor Cause The Edit Properties window is popping up off of the screen. Either it was dragged off of the screen accidentally or a second monitor was removed or is not accessible through remote connections. Resolution To display the dialog on the main screen: Double click a point in Vista. Do not click on anything else. The invisible Edit Properties window should be the current window. Press three keystrokes in this order: Alt + Space + X.  This is the Windows hotkey combination to the File menu, and will maximize the current window on the monitor. Possibly try hitting the Alt key twice. This brings the current window to the front. Alt + Space bar, then select Move with the mouse, after a tap of any arrow key, the mouse should lock onto the window allowing you to move it To prevent this from happening in the future: Download the TAC Vista Dialog Position Reset utility. Unzip and double click the executable file to run. Hit the Reset button.

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

Issue On a fresh install of LonMaker Turbo, inactivated, the first time trying to open a drawing you may get the error:  The object was not found (Subsystem: LNS, #6) Extensions ‘Echelon_LMW_Demo’ Environment LonMaker Vista LNS Cause If you specify a network name with trailing spaces, the LonMaker tool will report an LNS #6 error (object not found), and report an unexpected error. An object has been requested by name or index that could not be found in the databases.  Typically, this would be a request from a LNS collection object with a bad name or index. It should be noted that this error can also occur in some implicit assignments. For example, if the network interface to be used has not been explicitly assigned to the appropriate property, LNS will continue using the network interface previously assigned to the ActiveRemoteNI or NetworkInterface property, respectively. In such a scenario, this exception could occur even though no explicit assignment has been made, indicating that an implicit assignment maps to an unavailable object. A monitor set may be created while offnet (System.MgmtMode is set to lcaOffNet); however, a monitor set cannot be opened while offnet. Furthermore, attempts to query the MonitorSet.IsOpen property will get the error "The object is not found (Subsystem: LNS, #6)" when offnet Resolution Getting the activation code and activating the install should clear the error.

Issue NSS program ID changed. Requires upgrade or revert back to old interface. (Subsystem: NS, #171)  Environment LonMaker NL220 Vista LNS Cause If you open the Network Properties dialog, change the network interface from an LNS legacy Network Interface (also called NSI) to an LNS Fast Network Interface (also called VNI), or vice versa, and at the same time change from Offnet to Onnet, the LonMaker tool will report an NS #171 error (NSS upgrade required).  Resolution Change the network interface only -- remain offnet Click OK. Re-enter the Network Properties dialog and then change from Offnet to Onnet

Issue Attempting to commission a controller in an LNS environment results in the following error: Cannot communicate with the device. (Subsystem:  NS, #26) Environment LonMaker, NL220 Cause An NS, #26 error indicates a complete failure to communicate.  Most often this will be the result of physical layer problems.  In some situations it maybe due to a failed controller. Resolution Check the obvious physical layer connections: Is the cable plugged into the laptop to connect to FT-10?  Is the router between the computer and device being commissioned online and communicating?  Are the wires terminated properly at the controller?  Is the controller powered? Are there end of line terminators fitted? Inspect the controller: Are the LEDs blinking as designed? Are you able to receive a service pin from the device? Does an MOT or NXE need to be reloaded to the device? Typical troubleshooting techniques will usually resolve an NS, #26 error once it is understood to be a complete lack of communication at the physical layer.

Issue Integration to the Powerlogic PM800 power meter with the Xenta 500 \ Xenta 700 \ Xenta 900 and Modbus RTU Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Powerlogic PM800 Power Meter Cause Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support Services-Dallas has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template. Please report any problems to PSS Dallas at product.support@buildings.schneider-electric.com Resolution Please us the following .dev file as a starting point and a guide to the integration. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes.     To use these files in Xbuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on your harddrive. In Xbuilder, right click on the Modbus Master device and chose Add Device Browse to the needed .dev file and choose Open. Rename the newly added device to a unique name within the Modbus Master network.

Issue Error number :      17040 Error description: Invalid format. (Subsystem: LNS, #40) Any tab except "Status" has some strange values. Trying to view or edit some values results in this error. Environment Xenta 102-AX Plug-in Xenta 104 Plug-in LonMaker NL220 Cause A value inside the device has been set with an invalid value.  It could be through an LNS browser, through an M/STAT or just through some glitch when setting a parameter. Resolution The device will need to be recommissioned using default values. CAUTION:  Recommissioning a device with default values will erase any user defined configuration parameters.  Record all important data for the box:  duct area, airflow setpoints, operating parameters, etc. Right-click on the device in the LNS Management tool.  In LonMaker, select Recommission. In NL220, select Repair. Choose "Manufacturer Defaults" for the initial values.  Click OK. Launch the plug-in again.  The values should now be able to be changed to the desired value.

Issue Get Authentication Mask The entire Disk RTI subsystem is damaged. Please consult the software provider. Product Line TAC Vista Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause Unspecified, but a PSU-specific fix file is the only way to correct the situation. Resolution Note: Beginning 2012, PSS will no longer support the Privilege License System. The Tamfs26 Server will be retired along with TAC License Server software. The following is for informational and archival purposes only. PSS does not have the ability to provide this file to our customers. Contact Product Support and provide the PSU ID. A PSU-specific fix file will be generated and sent back via email. Install the fix file Install the original .plf file again. Exception: If the fix file cannot be installed, make sure that the PSU ID printed on the sticker matches the PSU ID that it presents itself when running Dongleutil. If they do not match, see Error "License run-time information is damaged. Contact software vendor. PSU ID: XXXXXXXX PSU Type: Unknown subfamily: 255".

Issue Menta Parser Error when attempting to direct download a Menta application. Warning Reference to unsupported I/O Error in COD file - Error:13 (Y=___ X=___) Product Line TAC Vista Environment Xenta Programmable Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause The application may contain an I/O terminal that does not exist in the device type to which the application is being downloaded.  This error could also occur in situations where the same I/O terminal reference is used more than once in the application (this could be on the Xenta or the I/O module). Typically caused by copy/paste. Resolution It is possible to have a Menta application that looks to be error free during simulation or the generation of the XIF file, but when the application is downloaded to the controller and it is being parsed by the device it reports a warning about unsupported I/O and leaves the controller without an application. The error window that pops up when trying to perform the download directly from Menta is attempting to show where in the Menta file the error is occurring.  If you can read the point names that are highlighted it can help direct toward the invalid I/O termination.  The other option is to look in Options > I/O configuration and make sure there are no duplicates or invalid I/O terminations.  For example, a 401 doesn't have any onboard I/O so a termination of M0-K1 wouldn't be valid. Note: I t is recommended that all macro libraries have non-connected outputs and constant value inputs to force the user to edit these fields.