Building Automation Knowledge Base

Issue Vista 5.1 license is not working.  Trying to launch Vista components results in error:  lc_checkout failed: Cannot checkout an uncounted license within a Windows Terminal Services guest session. Environment Vista 5 Terminal Services Virtual Machine VM Cause There is a special feature needed in the license which allows the use of Terminal Services. Resolution You must download the 14 day Demo TS Evaluation License on The Exchange Download Center. *note that Terminal Services are only supported in Vista 5

Issue  System Plug-In returns "Error: 80010105" when downloading a programmable controller. Environment Vista Server NL220 / Lonmaker System Plug-In Cause The cause is unknown at this time.  When downloading a controller through System Plug-in this error will stop the download from proceeding.  It seems to be system-wide once it happens, not controller related. Resolution Go to Start > Settings > Control Panel > Add or Remove Programs Uninstall the TAC Toolpack Re-Install TAC Toolpack (make sure it matches the Vista Server version).

Issue LOYTEC NIC-USB card shows offline in NL220 Cannot communicate to NIC-USB card when opening NL220 Product Line TAC Vista Environment NL220 NIC-USB Loytec Cause Proper setup of a NIC-USB in NL220 is required in order for the NIC-USB card to be able to communicate with NL220 or TAC Vista Server.  Resolution A tool called LConfig need to be installed on the computer before the configuration. Click here to download and install  the configuration tool (NIC - LOYTEC Network Interface Software 4.1.4). Connect the NIC-USB to the computer Use LConfig (Start/All Programs/LOYTEC Network Interface/Lconfig) to configure the NIC-USB Choose the USB tab Check "Enable USB Network Interfaces" Click "Test Device/Serial Number" Go to NL220. In the project open window, select the correct NIC-USB in the "Network interface" box. Click "OK"

Issue How to make a graphic page pop up in Vista Workstation when an alarm occurs. Environment Vista Workstation Cause Steps of making a graphic page pop up in Vista Workstation when an alarm occurs may not be very obvious to many users. Resolution Locate the alarm object in Workstation. Right click on that alarm object and select "Properties" In the "Properties" window, select "Video/Graphic" tab. In the "Linked graphic" text box, browse to your graphic object and click "OK" to save it. Check "Show graphic automatically". This is also discussed in the TAC Administering Manual in Chapter 7.

Issue Device driver open failure Echelon LonMaker Failed to open network interface device. (Subsystem: NI, #39) Environment LNS LonMaker Vista Cause NI error #39 is a network interface error. It indicates that the network interface driver failed to open the network interface. For the i.LON 10 or i.LON 100, this error occurs when the LonWorks Interfaces driver configuration on your computer does not match the network interface settings in your i.LON 10 or i.LON 100. Improperly seated PCMCIA PCC-10 LON Adapter. Can happen with some regularity when using a NIC852 and going onnet through LNS Server.  Subsequent attempts are usually successful Resolution If the LON Adapter is not properly inserted, you should try removing it and plugging it back in, or by using a second card temporarily and then switching back to the original card. If unsuccessful... To correct the error, open the LonWorks Interfaces Control Panel program and verify that the port setting, authentication key, hostname, and DNS suffix match the settings in your i.LON 10 or i.LON 100. To open LonWorks Interfaces, click Start, click Control Panel, double-click LonWorks Interfaces, and then click the RNI tab. Please reference the i.LON 10 or i.LON 100 user guides or online help for instructions in modifying the configuration of an RNI. When opening your network, make sure you select the correct network interface. For an i.LON 10 or i.LON 100 RNI, the name that you select in the LonMaker tool must match the name that you see on the LonWorks Interfaces RNI tab. Echelon Support KB515 .

Issue How to set up a periodic report in Vista Workstation.  Troubleshooting techniques to solve a periodic report that will not run. Environment Vista Workstation 5 Cause There are three objects required to work together.  They are: Time Event - Object Report Report - Periodical Resolution Verify settings in each of the three Vista objects Time Event - Object Create a Time Event - Object.  Right-click and go to Properties. View the Time Event Settings Tab Choose the interval type and frequency. Ensure a start time is checked and occurs prior to when the report should run. Check a stop time.  If a stop time is needed, leave it checked.  If not, uncheck it. Click OK Right-click again and go to Properties. View the General Tab Description is optional Next Event: should be populated with a date and time. Report Create a Report object.  Right-click and go to Properties. Go to the Report Tab If the report is to be printed, define a printer. If the report is to be saved to the hard drive, define a destination folder. Define a report file name.  This will be the name of the saved folder. If multiple copies are to be saved, uncheck overwrite existing file.  Files will be saved with a datetime extension on the file name. To insert a trend log or value into the report, navigate to the report in Vista Workstation, right click, and go to edit. Select a cell in excel towards the top left of the page where the trend or value will be inserted. In excel menus, navigate to Vista Links > Insert > Trend Log or Value. Browse in the value or trend log out of the vista database, adjust settings to the project preference and click okay. Finally make sure that the report is saved to the Vista database by navigating to Vista Reports > Save.   Report - Periodical Create a Report - Periodical.  Right-click and go to Properties.  This is the object that will tie together the Time Event - Object with the Report. General Report:  Browse to the Report object in the Vista database Settings Active: must be checked. If the report is to be printed, check Print report. If the report is to be saved to the hard drive, check Save copy Event Settings Event:  Browse to the Time Event - Object in the Vista database If the report is to run when the event begins, check Tripped If the report is to run when the event ends, check Reset.  At least one of these should be checked.

Issue Downloading the .chm help file from a Xenta 5/7/9xx controller help button results in the following error: Navigation to the webpage was canceled What you can try: Retype the address. Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause Content of the compiled HTML file is blocked for security reasons. Windows blocks the content because it assumes it has come from another PC and could be harmful.  Resolution Right click on the .chm help file and go to Properties Click the Unblock button under security Click apply and then OK Re-open the file

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 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 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 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 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 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 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: It is recommended that all macro libraries have non-connected outputs and constant value inputs to force the user to edit these fields.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue When doing a LonMaker resynchronization, the operation fails on a certain subsystem or when doing a commission on a controller in Lonmaker an error is displayed: Attempt to assign a neuron ID that is already in use by another device. (Subsystem: LNS, #102) Environment LonMaker 3.X Cause If re-commissioning or downloading and commissioning a controller in LonMaker fails or times out, this issue may crop up. LonMaker assigns the desired neuron ID to a temporary device while performing either of these commands, and if the operation fails, that temporary device will get stuck in the database with the same neuron ID as the controller the user was working on. A successful resynchronization will bring this "phantom device" to light where it can be deleted, but if it is the resynch that is failing, the steps below detail how to remove a neuron ID from a device in the LNS database so it can be deleted. Resolution Try to do a resynch command in LonMaker to get the temporary device to show itself on the Visio drawing. If this works, then the temporary device will show up with a randomly generated alpha numeric name on the same page as the controller you were trying the commission or download. After the resynch completes, delete the device from the page and repeat the commission or download. If the resynch operation fails with: Attempt to assign a neuron ID that is already in use by another device. (Subsystem: LNS, #102), continue. Because the temporary device is in the LNS database, but not on the LonMaker Visio drawing, manual manipulation of the LNS database is required to remove this object. This is done with the LNS Object Browser. First, shut down LonMaker, then click START and chose RUN in Windows and type lnsobjectbrowser and click ok. The Startup Preferences are shown. Set the Client/Server Communication to Don’t change and the Local Network Access to Engineering Mode and then click Ok. After choosing settings in the Startup Preferences menu, the LNS Object Browser is displayed. Press F8 to take the object browser out of read only mode. Browse to the following: ObjectServer/Networks/Your_Network_Name/Systems/ Your_Network_Name/Subsystems/All/AppDevices. Note: Double-click to open each object. Within the APPDevices menu you will see the temporary device with the large alpha-numeric name. Double-click this device to get its properties in the right hand window. Double-click on the NeuronId line in the properties pane of this device and manually set the Neuron Id to 000000000000 (12 zeros) and click Ok. Exit out of the LNS Object Browser and re-open the LonMaker database. Perform another resynchronization of the database, and the suspect temporary device should now show up on the LonMaker drawing. Then, delete that device and re-attempt your work on the original controller.