Building Automation Knowledge Base

Issue   PARSER_CODE_ERROR Error in COD file - Error:15 When directly downloading a Menta file a Parser Code Error is displayed. This is a Parser Error that is alerting you to the fact that there is a problem with your Code. An error in the Menta file is stopping it from downloading successfully. Product Line TAC Vista Environment Menta Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause Direct downloading a Menta file (via the RS-232 port, a serial cable, and Online Simulation Mode) can bring to light Parsing Errors that are not reported by the System Plug-in. These errors will result in unsuccessful download attempts without any indication of the failure. To find them, direct download the Menta file. The download gets to where it is parsing the file before it fails:  There are three known reasons why the parsing of a Menta file will fail with Error Code 15. With some careful investigation of the error the cause can be determined, although checking all known causes is not prohibitively time consuming. Either the Menta application is too large, contains SmartStruxure Function Block following a cut-and-paste of code, or the file has corrupted public values indicated by the values being shown in scientific notation. Resolution First, determine the source of the error. Three known issues are discussed below: Corrupted public values show in scientific notation The Error:15 window attempts to show the user where in the Menta code the error is occurring. Without a fairly intimate knowledge of the inner workings of Menta, this can be less than helpful. However, if scientific notation in a PVR is causing the error, the error window will show this. The first line states: PVR     3,Z4 R1.0762e-042 This is showing that a PVR in the Menta program has a value of 1.0762e-042. It may take some searching, but you will need to locate the PVR in the Menta file that has this corrupted value and change it back to something valid. Also check public constants in the file to make sure they are not corrupted.   SmartStruxure Function Blocks in TAC Menta application This error also appears if there are any SmartStruxure specific Function blocks in the application. RO, BO, RI, BI, TSCHI, ERROR, II, IO, PI, PO Check the if any of the blocks are in the COD file (in the error window), find the blocks and replace/remove them.   Menta Application is too large The only other option is that the Menta application is too large. So if the Error:15 window comes up and does not indicate scientific notation in any of the values, it has to be that the file didn't fit inside the controller. Check the memory in Menta under Options > Memory Usage. You want to see free space in all categories. If there are any negative numbers then that portion of the application is too large. Bear in mind that this is a simple estimation by Menta as to the memory needed. Trend logs, OP tree, network description files and the Menta application all need to be stored in the controller, so sometimes a very low, albeit positive, number can indicate problems as well. Try cutting down on trend logs or OP trees to free up space if the application cannot be reduced.

Issue   Invalid database version. (Subsystem: LNS, #81)[DB #-2038] Environment LonMaker 3.1 Cause A computer running LNS version 3.2 or higher (sometimes called LNS Turbo) can open any LNS database. If the database being opened is LNS version 3.1 or earlier, the database will be upgraded. This process is irreversible. Once the database is upgraded, earlier versions of LNS can no longer open it. The opposite is not true. If a computer running LNS version 3.1 attempts to open a 3.2 database, this error will appear. Resolution The LNS version must be at 3.2 or later to open a 3.2 database. Either upgrade the LNS version on the PC attempting to open the database, or revert to an earlier version of the database before it was upgraded (if possible). To upgrade your LNS version to 3.2: Navigate to http://echelon.com/support/downloads. You will need an Echelon ID and password. It is free to create a New User Account if you do not already have one. In the drop-down menu, select Search for software in the Network Tools category. Before you install LonMaker Integration Tool 3.1 Service Pack 3 Update 3, you must have already installed LonMaker Integration Tool 3.2 Service Pack 3 Update 1. Download both Update 1 and Update 3, or just Update 3 depending on the situation. Note: If you upgrade to LNS Turbo, you will no longer be able to restore databases from a non-Turbo LNS PC. There is backwards compatibility with old databases, but no "forward" compatibility for older PCs to open newer networks.

Issue During a Vista 5.x.x installation, failure can occur during the SQL installation portion of the install. This solution could encompass many different SQL installation errors; however, one that is known and verified is shown below: Failed to create or configure database on SQL Server! ([17] SQL Server does not exist or access denied.) Here is another common one:   Failed to create or configure database in SQL Server ([1802] CREATE DATABASE failed. Some file names listed could not be created. Check related errors.) If you have previously uninstalled Microsoft SQL Server, data files for the database may still exist in the SQL Server data directory. Remove the files manually and click Retry or click Cancel to abort installation. Product Line TAC Vista Environment TAC Vista Server 5.x.x Cause Uninstalling and reinstalling the software can leave pieces of SQL behind. Even if you try to uninstall everything in Add/Remove Programs, left over portions may cause the TAC Vista installation not to be successfully installed. The Program Files\SQL Server directory is flagged for compression or encryption. Installing Vista version below 5.1.5 on a Windows 7 64bit machine will cause this error. Resolution Please check the Windows Event log for the specific installation error. See Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes for information on viewing the Windows Event Log. Consult Log file of SQL installation when installing Vista Server for information on viewing the SQL Server installation log. If the Event log reveals Error 28001, the sa password must meet SQL Server password policy requirements, please refer to the solution provided in Error 28001 - sa password complexity error when installing TAC Vista 5. If not, then please proceed with the resolution below: If the SQL Server installation log file complains that the Program Files\SQL Server\ directory is flagged for encryption or compression then right click on the directory and select properties. The advanced option exposes the check boxes for compression and encryption. If the folder is flagged for compression the it will be visible in blue instead of black font. Remove the encryption or compression flags and apply then reinstall. If the PC operating system is Windows 7 64-bit, install Vista 5.1.5 or higher. Resolution below will not solve the issue. In most cases this is caused by MSXML 6.0 parser. This software is commonly installed by programs using SQL, and also during the TAC Vista installation. If this can't be removed using Add/Remove Programs, you can download a program from Microsoft that cleans up and removes this software (and others). It is called Windows Installer Cleanup. Link to download: msicuu2.exe. NOTE: Microsoft recently removed this utility from the downloads section of their support site. They have this to say about the utility: While the Windows Installer Cleanup utility resolved some installation problems, it sometimes damaged other components installed on the computer. Because of this, the tool has been removed from the Microsoft Download Center. Use this utility with care at your own risk.   In most cases TAC Vista will install successfully after removing MSXML 6.0 parser. For alternative solutions see SQL Express install fails on MSXML 6 and Error when installing SQL 2005 Express on a machine that had previously had MSDE installed .

Issue Power to devices are Full Wave or Half Wave. Device is connected to 24VAC and begins to smoke because the voltage power input from transformer is not wired correctly. Product Line TAC INET, TAC Vista Environment Devices such as a Xenta Router or a controller which is powered by an external 24VAC transformer. Cause Devices such as a Xenta Router or control board is connected to 24VAC and begins to smoke because the power input from transformer is not correct. Resolution Download Full Wave Half Wave.pdf which illustrates the transformer to device wiring configuration. PoE is not supported for any of the Ethernet ports on I/NET devices.  

Issue Modbus device is offline in Vista. Product Line TAC Vista Environment TAC Vista Xenta 511 Xenta 913 Xenta 700 Cause The Modbus device online check has to read at least one variable for the device to come online in Vista. If you only write values to the Modbus device, it will appear offline.  Resolution As a workaround, you may create a dummy variable that you read from in Xbuilder

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

Issue Error "Ensure that Vista Server is started" when the server is already running. Product Line TAC Vista Environment Vista Server Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause Refer to Chapter 3.5 of the TAC Software Installation Manual for the network security and permissions settings required to run Webstation (DCOM). test Resolution These are some utilities created by Benjamin Roswall at Schneider Electric Denmark. They are not official releases nor are they supported by Schneider Electric. While they have been tested and used successfully, they should be used at your own risk.   DCOM Config 1.0.3.0.exe: Configure DCOM for TAC Vista Network If you want to run TAC Vista Web Applications on Windows Server 2003 Standard Edition, both Internet Information Services (IIS) and ASP.NET 2.0 must be installed. ASP.NET 2.0 must be installed and activated before you start installing TAC Webstation. Refer to Chapter 4 of the TAC Software Installation Manual for more information. If you've made it this far, then it's time to refer to Chapter 3.5 of the TAC Software Installation Manual for the network security and permissions settings required to run Webstation (DCOM). Or just run this utility. Click the picture to download the utility.   Webstation installations will use Option 3. If Webstation doesn't come right up and start working after this, also download the next utility.   WEB.exe: Corrects common problems with Vista Webstation This utility will install and register the versions of ASP.NET required for running Webstation on the server PC. There are other articles on the command prompt commands to accomplish this, but this utility will take care of it for you. Click the picture to download the utility.   After this utility finishes running, restart the PC as instructed.

Issue Upgrading a Xenta 102-AX to v 2.16 Product Line TAC Vista Environment Xenta 102-AX LonMaker NL220 Cause Firmware upgrade Resolution The following instructions will describe the firmware upgrade process for three different LNS environments: LonMaker 3.1, LonMaker Turbo 3.2, and NL220. The NXE, APB, and XIF files for upgrading the 102-AX are now available on The Exchange Download Center. Preparation   Always remember to make backups before beginning this process. Record the Neuron IDs for all Xenta 102-AXs that will be receiving the upgrade. If you do not record the Neuron IDs ahead of time, you will have to press the service pin on every controller being upgraded. A list of all Neuron IDs can be obtained in one of the following ways: Through TAC Vista Server Open TAC Vista Server Click on Reports > LonWorks Networks, Survey   This process will open a .txt document which lists all controller names and Neuron IDs in the Vista database. Through Echelon LNS Utilities Navigate to Start > Programs > Echelon LNS Utilities > LNS Report Generator Select the LNS Network   Hit Generate   This will generate a .csv file in the designated location with controller names and Neuron IDs. This can be viewed using Microsoft Excel. Through NL220 Choose either Subsystem or Channel view Depending on the view, right click either on the Subsystem or the Channel Select Print > Print list of nodes Select Export   Choose desired file format Hit OK If changes have been made to the configurations of the 102-AXs through any means other than the LNS plug-in (I/STAT, M/STAT, Vista Workstation) these parameters will first need to be uploaded to the LNS database. If this step is skipped, then any configurations made this way will be erased during the upgrade. In LonMaker 3.1 Right click on a device Select Resynch CPs... Repeat for each 102-AX In LonMaker Turbo 3.2 Right click on a device Select Commissioning > Resynch CPs... Repeat for each 102-AX In NL220 Right click on a device Select Copy configuration values in memory Repeat for each 102-AX Download the NXE and XIF files for version 2.16 from The Exchange Download Center. Please note that during the upgrade process, the 102-AX will not function properly. In a multiple LIP or router database the dummy database can be created on a notebook PC. This allows for a local FT10 connection to the Lon network after the router. The existing network topology is not needed on the dummy database in this case.   Performing the Upgrade in LonMaker 3.1 It is not possible to upgrade a 102-AX in an existing database. To upgrade a 102-AX, a temporary "dummy" database must be created. Launch LonMaker Select New Network Set the new network to be Online and Network Attached. Do not register any plug-ins. Add a generic device *Note: The network has to represent the topology of the physical connection to the FT-10 channel Check Commission Device box, hit Next.   Load XIF. Browse to the downloaded v2.16 XIF file (not the standard XIF, but the v2.16 downloaded from Exchange Online). Hit Next.   Specify channel. Hit Next.   Default Properties selections are okay. Hit Next.   Set the Neuron ID. If you recorded them in a report previously, manually enter the data here. If you planned to service pin the controller, select Service Pin. You will be prompted at the end of the process to service pin the device.   Check the box for Load Application Image. Browse to the v2.16 NXE downloaded from Exchange Online. Hit Next.   Set the desired state to Online. Set the Source of Configuration Property Values to Current values in device. This is an important step. If you do not set to current values in device, your previous configuration parameters will be erased. Press Finish to begin the download.   Allow approximately 50 seconds for the application image to finish loading. While you wait you will see this window.   To upgrade the next 102-AX, right click on the device and select Replace. Repeat these steps for each 102-AX in the system. Performing the Upgrade in LonMaker Turbo 3.2 It is not possible to upgrade a 102-AX in an existing database. To upgrade a 102-AX, a temporary "dummy" database must be created. Launch LonMaker Select New Network Set the new network to be Online and Network Attached. Do not register any plug-ins. Add a generic device Check Commission Device box, specify channel, hit Next.   Load XIF. Browse to the downloaded v2.16 XIF file (not the standard XIF, but the v2.16 downloaded from Exchange Online). Hit Next.   Default Properties selections are okay. Hit Next.   Set the Neuron ID. If you recorded them in a report previously, manually enter the data here. If you planned to service pin the controller, select Service Pin. You will be prompted at the end of the process to service pin the device.   Check the boxes for "Load application image" and "Update firmware in device to match application image." Browse to the v2.16 NXE downloaded from Exchange Online. Hit Next.   Set the desired state to Online. Set the Source of Configuration Property (CP) Values to "Application image file." Set the Device Specific CPs to "Preserve device values." This is an important step. If you do not preserve device values, your previous configuration parameters will be erased. Press Finish to begin the download.   Allow approximately 50 seconds for the application image to finish loading. While you wait you will see this window.   To upgrade the next 102-AX, right click on the device and select Commissioning > Replace. Repeat these steps for each 102-AX in the system. Performing the Upgrade in NL220 It is not possible to upgrade a 102-AX in an existing database. To upgrade a 102-AX, a temporary "dummy" database must be created. Launch NL220 Log in and create a New project. Do not register any plug-ins. In SmartChannel, set the new network to be Attached. Under the Device Templates tab, right-click and select New Device Template. Create the New Device Template from interface file. Browse to the downloaded v2.16 XIF file (not the standard XIF, but the v2.16 downloaded from Exchange Online). Hit OK.   On the Channel tab, right-click and select New node on Name the device and choose Create node from a device template. Select the newly created 2.16 device template. Uncheck Set all configurations to manufacturer's default.   Right-click on the new device and select Install (network > commission in newer versions). Set the Neuron ID. If you recorded them in a report previously, manually enter the data here. If you are going to service pin the controller, do it now.   Right-click the device and select Download program. Choose Upgrade system version. You will receive a warning stating that upgrading the system image can leave the device in a bad state and break communication. You should only use this option if you are sure of what you are doing. Confirm, Yes, you want to continue. Configuration download should be set to Keep current configuration on node.     Allow approximately 50 seconds for the application image to finish loading. To upgrade the next 102-AX, right click on the device and select Network > Replace. Repeat these steps for each 102-AX in the system.

Issue Plug-in 'TACOSSysPin.Document' launch failure. Unspecified error Product Line TAC Vista Environment LonMaker 3.X TAC Vista System Plug-in Cause An unspecified error in the launching of the TAC Vista System Plug-in is either caused by a faulty installation or registration of the plug-in.   Resolution Check under Start > Settings > Control Panel > Add or Remove Programs. Look for TAC ToolPack 5.X.X. Make sure the version number 5.X.X matches the current Vista installation. If it does not, uninstall the current version of the ToolPack and install the correct version. If it is the correct version, proceed. Check the plug-in registration. In LonMaker go to LonMaker > Network Properties > Plug-in Registration. Look for TAC Vista System Plug-In (Version 5.X.X) Make sure the version number 5.X.X matches the current Vista installation. If it does not, unregister the current version of the Plug-in and register the correct version. If everything appears to be installed and registered correctly, but the error persists, uninstall and reinstall the correct ToolPack. Reboot the PC, reregister the plug-in, and try to launch it again.

Issue The new program interface does not match the previously defined program interface. (Subsystem: NS, #59) Product Line TAC Vista Environment LonMaker 3.1 LNS Version <3.2 Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Xenta 104-A Square D Altivar 61 Xenta 102-AX Cause The steps defined in this article only relate to the NS #59 error when it is received on an attempt to commission a controller in an LNS environment. It does not cover when this error is shown as a result of a download attempt in the TAC Vista System Plug-in. For information on the download error, see NS Errors #59, #64, #51 in a row on download attempt through System Plug-In. The new program interface does not match the previously defined program interface; i.e., the number of network variables, message tags, or the structure of self identification data is inconsistent even though the Program IDs match. This generally happens when a newer firmware of a controller is introduced that uses the same SNVT inputs and outputs as the old controller, and therefore shares a device template even though something below the surface may be different. Resolution The appropriate resolution to the NS, #59 error depends on the LNS version and type of controller that is failing to commission. Select from the categories below which best describes the situation. LNS Version <3.2 Check the existing Version of LNS. Open the Echelon® LonMaker™ Design Manager Right-click on the title bar of the Design Manager and select "About Echelon LonMaker..." In the About Echelon® LonMaker™ Design Manager Professional Edition window, look under Additional Information.   If the LNS Version is below 3.2, then upgrading the LNS to 3.2 or later (also referred to as LNS Turbo, not to be confused with LonMaker Turbo) may fix the error. The later LNS versions are less sensitive to program interfaces not matching. Navigate to Echelon Downloads. You will need an Echelon ID and password. It is free to create a New User Account if you do not already have one. In the drop-down menu, select Search for software in the Network Tools category. Before you install LonMaker Integration Tool 3.1 Service Pack 3 Update 3, you must have already installed LonMaker Integration Tool 3.2 Service Pack 3 Update 1. Download both Update 1 and Update 3, or just Update 3 depending on the situation. Note: If you upgrade to LNS Turbo, you will no longer be able to restore databases from a non-Turbo LNS PC. There is backwards compatibility with old databases, but no "forward" compatibility for older PCs to open newer networks. If you cannot install the LNS update, proceed to the following solutions organized by controller type. Xenta Programmables (follow steps below) Xenta 28X, 30X, 401(:B) You get this error when two controllers share a device template (XIF file) if one has a system program version (.MOT) below 3.5 and the other has a system program version above 3.5. Typically you will get this when you are replacing an older controller or adding a new controller to an older network. To fix the problem you have to make sure that the new controller you are adding (replacing) gets a new XIF file and its own template. Open the application from the System Plug-in by right clicking on the controller and selecting Configure>Edit. To give the application a new XIF, either add a dummy SNVT or go to Device Configuration and uncheck the box for "XIF header generated according to LonMark standard." Go to Options>Simulate (F12), select Commands>Generate. Options>Edit (F12) and save the application to the hard drive by selecting File>Save as. In the System Plug-in, browse in the application that you just saved on the hard drive. Update TAC Network and Vista Database. If you are asked to resynchronize, do so. Download Applications and Parameters. Commission in LonMaker. Another cause of the error for a Xenta programmable is if the system program version (.MOT) is newer than the version of Vista System Plug-In being used. For example, if visiting a 4.2.5 Vista site and attempting to add a much newer 3.8 firmware Xenta programmable. It will fail on attempts to commission. The firmware must be downgraded to a version that is compatible with the older Vista system. See Download an .MOT file into a Xenta Programmable controller for information on loading a different .MOT file. Xenta 104-A (follow steps below) If there are TAC Xenta 104-A v1.10 (or older) commissioned in an LNS database, it is not possible to add a TAC Xenta 104-A v1.20 or newer in the same database. Nor is it possible to do a replace. This is due to a change of size of the SNVT declaration area residing in the device memory. For the same Program ID, LNS requires this size to be identical as previously commissioned devices. Download NXE v1.20A from The Exchange Download Center. This is an NXE file which should be used to upgrade v1.20 to be able to coexist with v1.10. (It is not possible to upgrade 1.10 to 1.20/1.2A, due to memory configuration.) The download of v1.2A to the device is selected in the “New device wizard” in LonMaker. Check the “Load application image” and browse in the NXE as the image file. Note : The same process must be performed while dealing with the 104-A v1.21. In addition to the same issues above, v1.20A will not be compatible with v1.21. For more information on the Xenta 104-A firmware versions see Xenta 104-A firmware version compatibility. Square D Altivar 61 (choose an option below) Square D Altivar 61 drives have undergone a similar update of the firmware. Newer LON drives cannot reside concurrently on a network with older drives. A new NXE must be loaded into the newer drives so they can coexist with the older drives. This NXE file is on the Product Support SharePoint, or can be obtained by contacting Square D drive support directly at drive.products.support@schneider-electric.com. Xenta 102-AX Two Xenta 102-AXs, one that is hardware version 1, and one that is hardware version 2, cannot co-exist on the same LNS network. Whichever one is commissioned first will work fine, the second will result in an NS, #59 error.

Issue Program IDs do not match. There is an incorrect or out-of-date program version. (Subsystem: NS, #38) Product Line TAC Vista Environment LonMaker 3.X NS Error codes are not specific to any one LON environment, the display of the error may vary, but the steps to resolve should be the same. Cause A Program ID is a unique identifier assigned to each XIF (or device template) in an LNS database. Controllers with different XIFs cannot share the same Program ID. When a device is created in an LNS database, its Program ID is extracted from the XIF and stored in the database. When a controller is downloaded, the Program ID is transferred and stored in the controller. If the Program ID that resides in the controller differs from the one stored in the LNS management tool, the commission command will fail due to the Program ID mismatch. Resolution The appropriate resolution to the NS, #38 error depends on which controller is failing to commission. Select from the categories below which best describes the offending controller.  Xenta Programmables (follow steps below) Xenta 28X, 30X, 401(:B) Download the controller through the Vista System Plug-in before attempting to commission. If the error remains after a download, then the download did not go through, despite all indications that it did. Connect to the RS-232 serial port of the controller and attempt to download the Menta file directly. This will often bring to light parsing errors that are not detected by the System Plug-in. Find and correct the errors to allow the file to download properly. See Menta Parser Errors for more information on parser errors. The controller should then commission successfully. --- If the error persists, continue ---   Open the Menta file of the controller that will not commission. Under Options > Device Specification, uncheck the box for "XIF-Header generated according to LonMaker standard." (You may have to temporarily assign a System Version to activate this checkbox.) LonMark standard headings only use 255 combinations of IDs. It may be that two controllers just happened to be assigned the same Program ID. After unchecking this box, go to Options > Simulate, Commands > Generate to regenerate a new Program ID without using the LonMark standard header which opens up many more Program ID combinations and lessens the already low probability of two being the same. Download the new Menta file with the new XIF and new Program ID into the controller. It should now commission successfully.   Xenta 5/7/9XX Xenta 511, 527, 701, 711, 721, 731, 913 The XIF in the LNS database must be updated. See How to update a modified Xenta 5/7/9xx XIF file in LonMaker for detailed instructions.   ASCs/LON Devices (choose an option below) Xenta 100 series, third-party devices Replace the device using the correct XIF obtained from the manufacturers website. Replace the device using the correct XIF obtained from https://www.lonmark.org/. Replace the device with a generic device. Commission with the option of getting the XIF from the device.   Xenta 400 Series I/O Module (choose an option below) Xenta 42X(A), 45X(A), 47X, 49X Be sure the correct module is defined in Menta if adding I/O modules automatically. If adding I/O modules manually, be sure to use the correct stencil on the LonMaker drawing. You will get this error if you try to commission a 451A module with a 451 stencil.

Issue For further information, refer to the FLEXnet Licensing End User Guide, available on the Flexera website. Product Line TAC Vista Environment Vista 5 Workstation FLEXnet Licensing Cause If you get this error and attempt to find the End User Guide, you will discover that the company that produces the FLEXnet software has gone through several name changes: Macrovision to Acresso to Flexera. Resolution If you would like a copy of this document, you can find the FLEXnet License Administration Guide (previously called the End User Guide) here.

Issue   Plug-in 'TACXenta102AXPlugin.LNSPlugInAPI' launch failure. Can't show non-modal form when modal form is displayed Product Line TAC Vista Environment LonMaker 3.X TAC Xenta 102-AX Plug-In Cause This error appears when launching the TAC Xenta 102-AX Plug-in if there is another instance of the plug-in already running. The first instance of the plug-in was never fully launched (it is still stuck in modal form). This can happen by not acknowledging the Configuration Parameters Synchronization window, sending it to the back, getting tired of waiting for the plug-in to launch, and killing the application. Resolution Minimize every window on the screen. Find the errant Configuration Parameters Synchronization window as seen below:   Select Skip If the application was terminated through Task Manager, acknowledge the failure to connect. If the application is still waiting, the plug-in for the original VAV will launch. If you do not wish to view this plug-in, close it once it opens. Try to launch the plug-in again on the desired VAV. It should now launch.

Issue Not getting any alarms from Xenta 30x/40x/28x on the network. Have to perform alarm refresh to get alarms Product Line TAC Vista Environment TAC Vista XBuilder Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 400, 401, 401:B Cause Xenta will only send alarms if it gets a heart beat from TAC Vista. If it for some reason does not get it or get it from the wrong server no alarms will get in to the alarm list. Xenta Servers can also send out the heartbeat on the network if a "stand alone" Xenta server is doing this the alarms will be sent to it instead. Resolution Open properties of the Lonworks Network object and click on the  "Communication Timers" tab. Make sure that “Heartbeat Active” is checked. If there are any Xenta 5xx/7xx on the network open the XBuilder for it and make sure that the option Alarm Server is set to disabled.   Download the XBuilder project again

Issue Bind to more than 13 unique LON devices without running out of address table entries Product Line TAC Vista Environment LonMaker NL220 LNS Cause Using a broadcast SNVT binding type will save on address table slots by only consuming one slot per receiving subnet instead of one per receiving controller.  This will increase network bandwidth, but allows one-to-one bindings to many controllers in the same subnet.  Xenta programmable SNVT output limits would be the only limiting factor. Resolution Open the Network Variable Connection tool by right clicking on a function block in LonMaker and selecting Connect. Set the Connection Attribute to Repeated to use this as a starting point. Hit the Properties button.    On the Connection Details window, select New. Give the New Connection Description a name. "Broadcast" is a good description.    Hit the Advanced button for this connection type.    Set the Use Broadcast setting to Yes.   Try binding some outputs with this new connection type and it will reduce the number of address table slots consumed.

Issue Troubleshooting sending email alarms from a Xenta Server. Product Line TAC INET, TAC Vista Environment Xenta Server Xenta 511, 511:B, 527, 701, 711, 721 and 731 XBuilder SMTP Server Cause There are many reasons why an emailed alarm from a Xenta Server wouldn't reach the desired destination inbox. This document walks through the most common settings and networking issues and how to overcome them. Resolution Some Xenta Servers can be configured to send out alarms via email – 511, 511:B, 527, 701, 711, 721 and 731. Typically, following the instructions found in the TAC Vista Xenta Server – Web Server Technical Manual will result in successful delivery of email alarms. However, there are some factors that can hinder these email messages. This document is intended to address a few of the most common troubleshooting techniques to resolve these problems. The Basics The first step to getting Xenta alarms to email out is to properly configure the XBuilder project. Reference Chapter 5.2 Configuring the TAC Xenta Server for Email Forwarding in the TAC Vista Xenta Server – Web Server Technical Manual. Enter the address of the Simple Mail Transfer Protocol (SMTP) server as well as the authentication information (if any). If no SMTP server or login information has been provided, contact an IT professional at the customer's site to obtain this information. Alternately, for testing and demo purposes, Schneider Electric's SMTP server can be used – smtpservice.buildings.schneider-electric.com (port 25 or port 2525). If using Schneider Electric's SMTP server, set the Authentication to "TAC." Once the Xenta Server is correctly configured, set up Alarm Receivers in the XBuilder project. The steps for this can be found in Chapter 4.3 Configuring Receiver Groups in the TAC Vista Xenta Server – Web Server Technical Manual. Consider configuring the Alarm Receiver to email a distribution list as opposed to individual email addresses. Then the distribution list can be edited and maintained by the IT staff without ever having to access XBuilder projects or Xenta Servers. If everything is set up correctly, test the email capability by logging into the web interface of the Xenta Server and navigating to Utilities > Tools > Communication Tests. Enter a test email destination and hit "Test" as shown in Figure 1.  Figure 1. Test Send E-mail Message If the email arrives as expected, then the SMTP settings are all correct. A final test of the alarm receivers and alarm properties can be accomplished by forcing an alarm condition. If the email does not arrive as expected, check the following possible errors, or proceed directly to the next section of this document titled "Check SMTP Connectivity." Could not send the e-mail, error in mail configuration If this error results from sending a test email, then the settings in XBuilder need to be revisited and verified. Failed deliver e-mail, connection couldn't be established, check e-mail address If the test results in this error, proceed to the next section of this document titled "Check SMTP Server Connectivity." Check SMTP Server Connectivity In order to use an SMTP server, a connection must be established. In this example, the provided SMTP server is "smtp.ACME.com." Xenta Servers have a built in test function for determining the status of some of the defined devices. Log into the web interface and navigate to Utilities > Tools > Communication Tests.  Figure 2. Communication Tests From this screen, the connection between the Xenta Server and any of the defined gateways and servers can be verified. Select the radio button for Mail server 1 (SMTP) and hit test. Some possible results of the test are: ‘Mail server 1 (SMTP)’ is on-line If the mail server is online, but the test email still is not delivered, then the cause is most likely the authentication credentials of the Xenta Server. Check with an IT professional to verify the login account name and password that have been provided. Check that it has been correctly entered as described in the section of this document titled "Check SMTP Server Settings." If all of this is set up correctly and verified, proceed to the section of the document titled "Xenta Server Indicates No Errors." ‘Mail server 1 (SMTP)’ is off-line If the mail server is offline, then no communication exists. Make sure the SMTP server settings are correct. Refer to the section of this document titled "Check SMTP Server Settings." Also check the TCP/IP settings as described in the section of this document titled "Check TCP/IP Settings." If the SMTP server is outside the network, ensure that the default gateway is defined and test its availability with a communication test as shown in Figure 2. Lastly, connect to the network using a laptop and attempt to ping the SMTP server. If it is unavailable, contact an IT professional for assistance. C:\>ping smtp.ACME.com Pinging smtp.ACME.com [10.10.10.10] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 10.10.10.10: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Figure 3. Failed Ping Example C:\>ping smtp.ACME.com Pinging smtp.ACME.com [10.10.10.10] with 32 bytes of data: Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Ping statistics for 10.10.10.10: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms Figure 4. Successful Ping Example In Figure 4, the ping has returned four successful results. This will confirm that cables are connected properly, IP addresses are set, and any necessary gateway routers are communicating. It does not indicate ultimate success in connecting to the SMTP server. To check connectivity with the SMTP server, use a simple telnet command on port 25 (or the specified port) from a command prompt. C:\>telnet smtp.ACME.com 25 Connecting To smtp.ACME.com... Figure 5. Telnet command. If there is an error connecting, you will see this: C:\>telnet smtp.ACME.com 25 Connecting To smtp.ACME.com...Could not open connection to the host, on port 25: Connect failed Figure 6. Failed Telnet Command. If the connection succeeds, the command prompt will clear and show a new line beginning with 220. Type the word "helo" and press enter. The SMTP server should again respond but this time with a line starting with 250. Exit the telnet session by typing "quit" and pressing enter. 220 smtp.ACME.com ESMTP helo 250 smtp.ACME.com quit 221 smtp.ACME.com Connection to the host lost. C:\> Figure 7. Successful Telnet Session. If a connection can successfully be established through telnet, then the ports are open and SMTP messages should be successfully received from the Xenta Server. That does not guarantee they will be relayed by the SMTP server, so if emails are still not being delivered, continue troubleshooting with the next section titled "Xenta Server Indicates No Errors." Command not found If a telnet attempt results in the command prompt error "command not found" it is most likely because telnet is not enabled. In newer operating systems (Windows Vista/Windows 7) this feature is not enabled by default. To enable telnet: Go to Start > Control Panel > Programs and Features On the left side, select Turn Windows features on or off Scroll down to Telnet Client and check the box (see Figure 8 below)  Figure 8. Enable Telnet Client. Failed convert dns-name into ip-number If using DNS names for the SMTP server instead of IP addresses, a DNS server must be defined. A DNS server is responsible for resolving DNS names to IP addresses. Make sure the DNS server is online with a communication test as shown in Figure 2. To bypass any problems with DNS, enter the SMTP server IP address instead. This can be obtained by pinging the server as shown in Figure 3. Check SMTP Server Settings The SMTP settings can be viewed and changed either in the XBuilder project, or live via the server's web interface. If you are troubleshooting live on a site, it is probably faster and easier to use the web interface. If settings are changed live, be sure to update the XBuilder project at some point to avoid the settings being erased by a download. Navigate in the web interface to Configuration > Network > SMTP.  Figure 9. SMTP Settings The fields shown in Figure 9 for "Outgoing mail server port" are not available in XBuilder/System Program versions prior to 5.1.3. In versions 5.1.2 and below, it is not possible to alter the default SMTP port. It is hard-coded at 25. The Primary SMTP will be provided by the site's IT staff. If authentication is required, then an account name and password must be provided by the IT staff. If the SMTP server is available, but no emails are being sent out, the authentication parameters need to be checked. Any further investigation at that point will require contacting an IT professional for assistance. Refer to the section of this document titled "Xenta Server Indicates No Errors" for some troubleshooting questions to pose. Also refer to "Contacting an IT Professional" for documents to use to facilitate these conversations. If no SMTP server has been provided, then Schneider Electric's SMTP server can be used. To use Schneider Electric's SMTP server for testing or temporary purposes, enter "smtpservice.buildings.schneider-electric.com" into the outgoing mail server. Mail server ports 25 and 2525 are available. Authentication is set to "TAC." This does not require an account name or password. This method is only recommended for testing purposes. Schneider Electric makes no guarantees as to the availability of the SMTP server. To ensure the email alarms are being delivered as promised, use an SMTP server with some guarantee of up time. Even if an SMTP server has been provided, consider defining Schneider Electric's SMTP server as a secondary server. It is not always a viable solution due to some network security settings and availability, but may increase the overall success rate of your email delivery by providing some redundancy. Check TCP/IP Settings The TCP/IP settings can be viewed and changed either in the XBuilder project, or live via the server's web interface. If you are troubleshooting live on a site, it is probably faster and easier to use the web interface. If settings are changed live, be sure to update the XBuilder project at some point to avoid the settings being erased by a download. Navigate in the web interface to Configuration > Network > TCP/IP.  Figure 10. TCP/IP Settings The most important items to check on this screen are Default gateway and DNS server. If the default gateway is not properly defined, then external SMTP servers will be unavailable. If the DNS server is not properly defined, then SMTP servers defined by DNS names will be unresolved. Either enter a valid DNS server, or manually resolve the IP address by pinging the server as shown in Figure 3. If using Schneider Electric's SMTP server, DNS must be defined. Xenta Server Indicates No Errors If the test email was sent, but not received, and no errors were recorded, the focus should now shift to troubleshooting the SMTP server itself. Assistance from an IT professional will be helpful at this stage. Things to check include: Check the incoming/outgoing messages from the SMTP server. See if the messages from the Xenta Server are arriving but not being sent out. Many companies will set up an "allowed" list that will only pass emails from recognized IP addresses, and all else is filtered as spam. Make sure the Xenta Server's IP address is listed on the acceptable list. Ask what port the SMTP communication is using. Port 25 is typically used for SMTP communication, but some companies will change this for security purposes. Request that port 25 be opened for SMTP communication from the Vista Server. If this is not an option, the port can be changed in XBuilder/System Program versions 5.1.3 and later. See the section of this document titled "Changing the default SMTP Port" for instructions. Xenta Servers are hard-coded to use UTF-7 encoding. They require this encoding to support Swedish characters. UTF-8 is the most common encoding in America and Europe. Some networks may filter UTF-7 messages as spam. While this is not readily configurable, it can be manually changed by editing some files. Use an FTP program (Internet Explorer) to connect to the Xenta you are trying to change and download the \sys\langstring.cfg file. Edit the file and modify the following lines to replace all instances of 7 with an 8: ALARM_CODE_1= =?utf-7?Q? ALARM_CODE_3=charset=UNICODE-1-1-UTF-7 Upload the edited file back to the Xenta device and then cycle the power. The device will now use UTF-8 character encoding which is more commonly used in the United States. Remember that reloading the system program will erase these changes. Some companies will block all POP messages on the network. This will disable the ability to use external SMTP servers. Make sure POP messages are allowed or that the SMTP server is internal to the network. If you are trying to use an SMTP server of a different ISP than the one Vista Server is connected to, this will most likely be blocked by the SMTP server. This is known as mail relaying – something spammers can and will abuse. Changing the default SMTP Port Changing the default SMTP port is not available in XBuilder/System Program versions prior to 5.1.3. In versions 5.1.2 and before, the only options are to request for the IT department to allow use of port 25, or upgrade to version 5.1.3 or later. If you are using XBuilder/System Program version 5.1.3 or later, adjusting the default SMTP Port can be done through the web interface as shown in Figure 9. It can also be adjusted in XBuilder as shown in Figure 6.  Figure 11. Changing the SMTP Port in XBuilder Contacting an IT Professional If you need help contacting the customer's IT department to gather and share the correct data, use the document attached in Appendix A: IT Request for Information. A completed example is shown in Appendix B: Sample IT Request for Information. Disclaimer The information contained in this document is subject to change without notice. It is also subject to change with versions of TAC Xenta Servers. If further assistance is required, please Call or email Schneider Electric Product Support Appendix A: IT Request for Information The TAC building automation system installed on your site has the capability to email facilities personnel in certain situations. Typically, this is used to alert the proper channels of equipment failure or security breaches detected by the automation system. TAC Xenta Servers use standard Simple Mail Transfer Protocol (SMTP) for these messages. An SMTP server must be provided in order for these messages to be delivered. The following document was created to facilitate the sharing/gathering of necessary information between IT and the installation contractor. Information for the Installation Contractor from IT SMTP messages must be sent with the following details: SMTP server address (DNS or IP):   Authentication required (choose one): Yes No Account name (if applicable):   Password (if applicable):   To distribution list (if any):   Required UDP Port:   Information for IT from the Installation Contractor SMTP messages will be sent with the following details: To distribution list (or email addresses):   Unit e-mail address:   From IP address:   Desired UDP port:   Appendix B: Sample IT Request for Information The TAC building automation system installed on your site has the capability to email facilities personnel in certain situations. Typically, this is used to alert the proper channels of equipment failure or security breaches detected by the automation system. TAC Xenta Servers use standard Simple Mail Transfer Protocol (SMTP) for these messages. An SMTP server must be provided in order for these messages to be delivered. The following document was created to facilitate the sharing/gathering of necessary information between IT and the installation contractor. Information for the Installation Contractor from IT SMTP messages must be sent with the following details: SMTP server address (DNS or IP): smtp.ACME.com Authentication required (choose one): Yes No Account name (if applicable): emailuser Password (if applicable): password123 To distribution list (if any): facilities_staff@thebuilding.com Required UDP Port: 25 Information for IT from the Installation Contractor SMTP messages will be sent with the following details: To distribution list (or email addresses): facilities_staff@thebuilding.com Unit e-mail address: xenta@server.com From IP address: 10.10.10.20 Desired UDP port: 25

Issue Troubleshooting sending email alarms from a Vista Server Mail error 1 – MAIL client needs to be configured first Mail error 2 – Couldn’t connect to server. Error:0  Mail error 2 – Couldn’t connect to server. Error:10022 Mail error 2 – Couldn’t connect to server. Error:10061 Mail error 3 – Couldn’t send message. Response:550 Mail error 3 – Couldn’t send message. Response:503 Unable to relay Product Line TAC Vista Environment SMTP Server Vista Server Workstation Cause There are many reasons why an emailed alarm from a Vista Server wouldn't reach the desired destination inbox.  This document walks through the most common settings and networking issues and how to overcome them. Resolution Vista can be configured to send out alarms via email.  Typically, following the instructions found in the TAC Vista Technical Manual will result in successful delivery of email alarms.  However, there are some factors that can hinder these email messages.  This document is intended to address a few of the most common troubleshooting techniques to resolve these problems. The Basics The first step to getting Vista alarms to email out is to configure the Server Setup.  Reference Chapter 3.3 Setting Up TAC Vista Server in the TAC Vista Technical Manual.  Enter the address of the Simple Mail Transfer Protocol (SMTP) server as well as the authentication information (if any).  If no SMTP server or login information has been provided, contact an IT professional at the customer’s site to obtain this information. Once Vista Server Setup is correctly configured you must restart the Vista Server. After the Server has been stopped and restarted, set up an Alarm Control Object and an Alarm Receiver – Email.  The steps for this can be found in Chapter 18 Alarm Processing in the TAC Vista Technical Manual. Consider configuring the Alarm Receiver to email a distribution list as opposed to individual email addresses.  Then the distribution list can be edited and maintained by the IT staff without ever having to access Vista. If everything is set up correctly, test the email alarm receiver by forcing an alarm condition.  The alarm should show up in the Vista Alarm Queue as well as at the alarm receiver’s designated inbox.  If the email does not arrive as expected, proceed to the next section of this document titled “Check Vista for Alarms/Errors.” Check Vista for Alarms/Errors If emails are not showing up when expected, the first place to begin the investigation is in Vista Workstation’s Alarm Queue.  There are helpful messages that may appear based on some criteria.  The Alarms will all come from $EE_Mess object under the Vista Server.  Sort the Alarm Queue by Last Change if the alarm just happened, or by Object ID to find the $EE_Mess alarms. Server-$EE_Mess Mail error 1 – MAIL client needs to be configured first Server-$EE_Mess Mail error 2 – Couldn t connect to server. Error:10022 Server-$EE_Mess Mail error 2 – Couldn t connect to server. Error:10061 Figure 1.  Vista Alarm Queue Mail Errors There are three possible errors that can be seen in the Vista Alarm Queue.  They should occur within a few seconds of the alarm if there is an error connecting to the SMTP server.  If the alarms are acknowledged or disabled, they may not show up in the Vista Alarm Queue.  The other place to look for them is under the Vista database folder on the hard drive.  Inside the database structure there is a folder called $log.  Inside this folder should be a file called b0warlog.txt.  Open this file and scroll to the time/date where the alarm occurred.  If an error occurred, the same text that appears in the Alarm Queue will appear in the error log in a slightly different format.  An example: Mon Aug 17 08:16:26 2009 alrdisp >> Error from SMTPSendMail: Mail error 1 – Mail client needs to be configured first Three possible alarm conditions are discussed here: Mail error 1 – MAIL client needs to be configured first This error refers to the TAC Vista Server Setup.  Refer back to Chapter 3.3 Setting Up TAC Vista Server in the TAC Vista Technical Manual.  If the server is setup correctly, be sure that the server has been restarted since the last change.  Changes in Server Setup will not take effect until the next time server is run. Mail error 2 – Couldn’t connect to server.  Error:0 Unknown cause. Mail error 2 – Couldn’t connect to server.  Error:10022 This error means that the SMTP server is unreachable.  If using a DNS name for the SMTP server, double check the spelling.  If everything looks correct, move to section of this document titled “Check SMTP Server Connectivity” and follow the steps described there. Mail error 2 – Couldn’t connect to server.  Error:10061 This error means that the SMTP server has been reached, but Vista was not allowed access to the server.  Double check the authentication username and password.  Re-enter the password to ensure it is correct (only dots are shown for privacy).  There are three different authentication modes to choose from: CRAM MD5 – (Safest) Password is coded with Message Digest 5. AUTH LOGIN – (Standard) Password coded with base64 method. LOGIN PLAIN – Password is sent uncoded. If the correct authentication mode has not been provided, it may require trying all three until the mail error clears.  If all three result in an error, contact an IT professional to be provided with a valid username and password.  Use the section of this document titled “Contacting an IT Professional” for a template to request this information. Mail error 3 – Couldn’t send message.  Response:550 Unknown user Unknown cause. Mail error 3 – Couldn’t send message.  Response:503 Must have sender and recipient first. Unknown cause.  If no errors occur in the Vista Alarm Queue or in the Vista alarm log text document, refer to the section of this document titled “Vista Indicates No Errors” for more troubleshooting techniques. For troubleshooting unknown errors, read Troubleshooting sending emails using WireShark. Unable to relay If an error "Unable to relay" is returned, this is most likely because authentication is not sent to the SMTP server. Go to Vista Server settings At the email tab set proper authentication (Vista Technical Manual Chapter 3.3 explain this more in detail) You may need to consult with the IT department on site Check SMTP Server Connectivity In order to use an SMTP server, a connection must be established.  In this example, the provided SMTP server is “smtp.ACME.com.”  Pinging is the lowest level of internet communication.  A successful ping will not guarantee communication with an IP device, but a failed ping will guarantee no communication.  Open a new DOS command prompt (Start > Programs > Accessories > Command Prompt).  Ping the SMTP server. C:\>ping smtp.ACME.com Pinging smtp.ACME.com [10.10.10.10] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 10.10.10.10: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Figure 2.  Failed Ping Example In Figure 2, a request to ping the SMTP server has failed.  Check that the computer where Vista Server resides has internet connectivity (Start > Settings > Network Connections).  Make sure the connection status is Connected, navigate to an internet website, or ping a known IP address.  If those fail, check the computer’s IP settings.  Figure 3.  TCP/IP Properties - Obtain IP Automatically If the computer is set to obtain an IP address automatically make sure that an IP address has been assigned.  Figure 4.  Local Area Connection Status If no IP address has been defined, then the DHCP server is not available and the computer is not connected a network.  Check the physical connections and contact an IT professional to determine why the DHCP server is not assigning the PC an IP address. If the TCP/IP properties are configured to use a static IP address (which is common in applications where WebStation or ScreenMate are employed), then the DNS server address must also be defined if a DNS SMTP server is used.  Figure 5.  TCP/IP Properties - Static IP If DNS is causing problems, it is possible to bypass this by using the IP address for the SMTP server as opposed to the DNS name. Look back to Figure 2 to obtain the SMTP server’s resolved IP address.  In this example, the IP is 10.10.10.10.  Figure 6.  Using IP Address of SMTP Server When everything is set correctly, try to ping the SMTP server again.  This time, it should go through successfully, which is an indication that most of the basic settings are correct – but should not be viewed as indication that email messages will successfully be delivered by the SMTP server. C:\>ping smtp.ACME.com Pinging smtp.ACME.com [10.10.10.10] with 32 bytes of data: Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Ping statistics for 10.10.10.10: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms Figure 7.  Successful Ping Example In Figure 7, the ping has returned four successful results.  This will confirm that cables are connected properly, IP addresses are set, and any necessary gateway routers are communicating.  It does not indicate ultimate success in connecting to the SMTP server. To check connectivity with the SMTP server, use a simple telnet command on port 25 (or the specified port) from a command prompt. C:\>telnet smtp.ACME.com 25 Connecting To smtp.ACME.com... Figure 8.  Telnet command. If there is an error connecting, you will see this: C:\>telnet smtp.ACME.com 25 Connecting To smtp.ACME.com...Could not open connection to the host, on port 25: Connect failed Figure 9.  Failed Telnet Command. If the connection succeeds, the command prompt will clear and show a new line beginning with 220.  Type the word “helo” and press enter.  The SMTP server should again respond but this time with a line starting with 250.  Exit the telnet session by typing “quit” and pressing enter. 220 smtp.ACME.com ESMTP helo 250 smtp.ACME.com quit 221 smtp.ACME.com Connection to the host lost. C:\> Figure 10.  Successful Telnet Session. If a connection can successfully be established through telnet, then the ports are open and SMTP messages should be successfully received from the Vista Server.  That does not guarantee they will be relayed by the SMTP server, so if emails are still not being delivered, continue troubleshooting with the next section titled “Vista Indicates No Errors.” Command not found If a telnet attempt results in the command prompt error "command not found" it is most likely because telnet is not enabled. In newer operating systems (Windows Vista/Windows 7) this feature is not enabled by default. To enable telnet: Go to Start > Control Panel > Programs and Features On the left side, select Turn Windows features on or off Scroll down to Telnet Client and check the box (see Figure 8 below) Figure 11. Enable Telnet Client. Vista Indicates No Errors If no errors show up in either the Vista Alarm Queue or the $log folder, then Vista has successfully contacted a valid SMTP server.  Review Chapter 18 Alarm Processing in the TAC Vista Technical Manual.  Make sure that the alarm is using the correct Alarm Handler that is assigned the correct Alarm Receiver that has the correct valid email addresses defined. If the alarms are set up correctly, the focus should now shift to troubleshooting the SMTP server itself.  Assistance from an IT professional will be helpful at this stage.  Things to check include: Check the incoming/outgoing messages from the SMTP server.  See if the messages from Vista are arriving but not being sent out.  Many companies will set up an “allowed” list that will only pass emails from recognized IP addresses, and all else is filtered as spam.  Make sure the Vista Server’s IP address is listed on the acceptable list. Ask what port the SMTP communication is using.  Port 25 is typically used for SMTP communication, but some companies will change this for security purposes.  Request that port 25 be opened for SMTP communication from the Vista Server.  If this is not an option, the port can be changed manually using registry settings.  See the section of this document titled “Changing the default SMTP Port” for instructions. Look at the selected Text encoding in the Vista Server Setup.  Unicode (UTF-8) is the most common in America and Europe.  If encoding is set to UTF-7, some SMTP servers will filter the messages out as spam. Some companies will block all POP messages on the network.  This will disable the ability to use external SMTP servers.  Make sure POP messages are allowed or that the SMTP server is internal to the network. If you are trying to use an SMTP server of a different ISP than the one Vista Server is connected to, this will most likely be blocked by the SMTP server. This is known as mail relaying – something spammers can and will abuse. Changing the Default SMTP Port Vista defaults to using Port 25 for all SMTP communication.  This is the standard port for SMTP and is typically used by SMTP servers.  However, because it is so well known as the SMTP port, some companies prefer to change this as a security measure.  Request that port 25 be made available to the Vista Server.  Unfortunately, sometimes this is just not possible because of security procedures.  If a different port is required, it is possible to manually change the port by navigating through registry keys. Open up the Registry Editor on the Vista Server PC (Start > Run… > regedit).  Navigate to: My Computer > HKEY_LOCAL_MACHINE > SOFTWARE > TAC AB > TAC Vista > 5.1.2 > SMTP Depending on the version of Vista, the path may change slightly.  If a 64-bit operating system is being used, the path will be: My Computer > HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node > TAC AB > TAC Vista > 5.1.5 > SMTP Navigate until the SMTP folder is located.  Inside the SMTP folder, the SMTP settings that were set with Vista Server Setup can be viewed.  There is also an additional registry key defining the port.  Figure 12.  SMTP Registry Settings If there is no registry key for Port, create one.  Right click in the key view window, but not on an existing key.  Select New > DWORD Value.  Name the new value “Port.” Double-click the Port registry key to edit.  Radio buttons convert the value from hexadecimal to decimal.  Ports are typically described in decimal values.  Switch to decimal, enter the required port number, and click OK. Figure 13.  Editing Port Registry Key Verify that the value had changed in the registry.  Vista should now be sending out SMTP communication on the required port. Contacting an IT Professional If you need help contacting the customer’s IT department to gather and share the correct data, use the document attached in Appendix A:  IT Request for Information.  A completed example is shown in Appendix B:  Sample IT Request for Information. Disclaimer The information contained in this document is subject to change without notice.  It is also subject to change with versions of TAC Vista.  If further assistance is required, please Call or email Schneider Electric Product Support Appendix A: IT Request for Information The TAC Vista building automation system installed on your site has the capability to email facilities personnel in certain situations.  Typically, this is used to alert the proper channels of equipment failure or security breaches detected by the automation system.   TAC Vista uses standard Simple Mail Transfer Protocol (SMTP) for these messages.  An SMTP server must be provided in order for these messages to be delivered.  The following document was created to facilitate the sharing/gathering of necessary information between IT and the installation contractor. Information for the Installation Contractor from IT SMTP messages must be sent with the following details: SMTP server address (DNS or IP):   Authentication method (choose one): None CRAM MD5 AUTH LOGIN LOGIN PLAIN Username (if applicable):   Password (if applicable):   Text encoding (if filtered):   To distribution list (if any):   Required TCP Port:   Information for IT from the Installation Contractor SMTP messages will be sent with the following details: (This can be found in TAC Vista Server Setup): To distribution list (or email addresses):   From name:   From email address:   From IP address:   Desired TCP port: 25 Appendix B:  Sample IT Request for Information The TAC Vista building automation system installed on your site has the capability to email facilities personnel in certain situations.  Typically, this is used to alert the proper channels of equipment failure or security breaches detected by the automation system.   TAC Vista uses standard Simple Mail Transfer Protocol (SMTP) for these messages.  An SMTP server must be provided in order for these messages to be delivered.  The following document was created to facilitate the sharing/gathering of necessary information between IT and the installation contractor. Information for the Installation Contractor from IT SMTP messages must be sent with the following details: SMTP server address (DNS or IP): smtp.ACME.com Authentication method (choose one): None CRAM MD5 AUTH LOGIN LOGIN PLAIN Username (if applicable): emailuser Password (if applicable): password123 Text encoding (if filtered): UTF-8 To distribution list (if any): facilities_staff@thebuilding.com Required TCP Port: 25 Information for IT from the Installation Contractor SMTP messages will be sent with the following details: (This can be found in TAC Vista Server Setup): To distribution list (or email addresses): facilities_staff@thebuilding.com From name: Vista Server From email address: vista @server.com From IP address: 10.10.10.20 Desired TCP port: 25

Issue ADI FSCO Panel Integration Product Line TAC Vista Environment ADI FSCO Panel Xenta 913 Cause Integration to an ADI Fire/Smoke Control Panel. Resolution This document details the process for integrating an ADI FSCO Panel (www.adipanel.com) with a TAC Xenta 913 through the ModBus serial interface. Comm Settings In XBuilder, right click the "RS232-485 A" Serial Port, add a ModBus Slave interface. The comm settings necessary are shown below:   The ADI FSCO Panels speak RS232. The 913's baud rate is adjustable in XBuilder from 300 to 19200. The panel's baud rate is adjustable via DIP switches from 2400 to 19200. There is no right or wrong speed, they just need to match. Parity is even, 7 data bits, 1 stop bit, and ASCII framing mode. On the ModBus serial line slave, right click and add a device. If it has not been created yet, you will need to create a device template first. The device requires a ModBus address. With an ADI FSCO Panel, this address is always 1. Physical Connections The RS232 port is an RJ45 port on the left front of the 913 labeled “A.” If you are creating your own patch cable to tie into the ADI FSCO Panel, the pin-out is as follows:   1 - White Orange 2 - Orange 3 - White Green – TXD 4 - Blue – RXD 5 - White Blue – GROUND 6 - Green 7 - White Brown 8 - Brown     TXD ties to the ADI FSCO Panel on the terminal block labeled "IN." RXD ties to "OUT" and GROUND ties to "GND." Signal Connections When populating connection objects between an ADI FSCO Panel and a Vista database, the best option is to use a Multi-Connection Object. Right click on the root folder in the System pane of XBuilder and select New > Object > Multi-Connection Object. The Multi-Connection Object can be populated by dragging and dropping points from the ADI Device Template and Menta. The Send Option in the Connection Manager lets you select either Periodically, Write on change, or Write initially and on change. Choose to write initially and on change. Each point also has a designated Period. Just because a point is not set to update periodically does not mean the period ceases to have any effect. If too many points are on the same period, it can overwhelm the 913. So regardless of the Send Option, the Period (s) should be staggered. Set the first 20 points to 10 seconds, the next 20 points to 11 seconds (for example – in reality, just avoid having hundreds of points at the same period.) When finished populating all data fields of the Connection Manager, hit the Validate button on the bottom left corner and make sure there are no errors. Menta Programming Menta files that accept data from an ADI FSCO Panel do so through PVBs and PVRs. These come default with the "Backup" option selected. This is used to store the value in non-volatile memory on power loss. When using a PVR for a setpoint, this is a good thing. However, when something is constantly writing a value to this public variable, and it in turn is constantly writing values to flash memory, it can cause the controller to lock up and stop working. You must de-select the "Backup" option from any PVBs or PVRs in a Menta file that are accepting data from a connection object in a 913. Disclaimer This document is intended to address some of the most common (and most commonly overlooked) settings when integrating with an ADI FSCO Panel through a serial ModBus connection. Contact ADI for product information and to ensure that the correct FSCO Panel is ordered to facilitate this type of integration. No guarantee can be made that changes to the physical configuration, communication settings, or software format have not been made, so always check with your ADI sales representative first.

Issue Migrate from custom installed Microsoft SQL Server 2000 to custom installed Microsoft SQL Server 2005 Product Line TAC Vista Environment Microsoft SQL Server 2000 Microsoft SQL Server 2005 Cause When you upgrade from Vista 4.3.0 - 4.5.0 to Vista 5.x you can continue to use the SQL Server 2000, but as the security and performance is better in SQL Server 2005, you would want to upgrade. There are some things that are important before you upgrade. You should of course take a backup, but there are also some other things you should have in mind. If you want to have the same instance name on the SQL Server 2005 as you have on the SQL Server 2000, you must have two different PCs. The SQL Server 2000 should be SP4 The SQL Server 2005 should be SP2 The SQL Server 2005 should be minimum “Standard” version Resolution Always remember to update from TAC Vista 4.5.0 to TAC Vista 5. This means that you have to update to TAC Vista 4.5.0 if you are currently running eg. TAC Vista 4.4.1. Procedure Upgrade TAC Vista to 5.x, and have it connect to the existing database on SQL Server 2000. Check the existing SQL setup in TAC Vista Server Setup. Uninstall TAC Vista 4.5.0. Restart the PC. Install TAC Vista 5. In the installation procedure, type in the SQL credentials you checked earlier. Stop TAC Vista Server and DSS Writer. To view installed services go to Start > Run > services.msc. If TACOS is running as a service, stop it in the services and set it to disabled. Stop the “TAC DSS Writer service” and set it to disabled. Assure that the SQL Server Agent is started on both the SQL Server 2000 and the SQL Server 2005. This can be checked in Start > Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager. Start the “SQL Server Management” on the PC where SQL Server 2005 is installed. This is the management tool that comes with SQL Server 2005 Connect to both the SQL Server 2000 and SQL Server 2005. The connect button is located in the upper left corner. Login using either windows or SQL authentication. Right click the Vista log database on the SQL Server 2000, select all tasks and copy. Follow the instructions in the wizard, and copy the database to the SQL 2005 Server (VERY slow process). Configure TAC Vista to connect to the copied database on the SQL Server 2005 Go to the SQL setup in TAC Vista Server Setup and have it connect to the DB on the SQL 2005 Server in stead of the SQL 2000 Server. Start the DSS Writer Go to Start > Run > services.msc Set the “TAC DSS Writer service” to automatic and start it. Start TAC Vista If TACOS is installed as a service, set it to automatic and start it. Otherwise, just start the TACOS application.

Issue Failed to create or configure database on SQL Server! ([17] SQL Server does not exist or access denied.) Windows Event log reveals the following error:   Product: Microsoft SQL Server 2005 Express Edition -- Error 28001. The sa password must meet SQL Server password policy requirements. For strong password guidelines, see Authentication Mode, in SQL Server Books Online. Product Line TAC Vista Environment Vista Server Microsoft SQL Server 2005 Express Edition Windows Server 2003 Cause When installing TAC Vista 5 on a 2003 Server you can get an error if the group policy require a certain complexity on the sa password. Resolution One possibility is to edit the group policy Go to Start > Run and type gpedit.msc In the Local Group Policy Editor, navigate to Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Account Policies > Password Policy Set Password must meet complexity requirements to Disabled.     The other option is to install the SQL 2005 Express SP3 yourself. It is downloadable from Microsoft. Remove the checkmark in "Hide Advanced Configuration" Set the instance to TACVISTA. Use the "custom" option in TAC Vista Server setup, and select the local SQL server.