Issue When downloading a programmable controller with the Vista system plug-in, the process fails and reports the Error 80041195, Info: Communication port not connected. NOTE: Error 80041195 has also been reported when performing a commence communication command in the Vista system plug-in. Product Line TAC Vista Environment Vista Server 5.1.5 Vista System Plug-In 5.1.5 Cause Vista Server 5.1.5 is not communicating to the LNS server properly Resolution Vista Server hotfix 14 addresses this error within Vista Server 5.1.5. Download TAC Vista Server 5.1.5 Hotfix 14 from The Exchange Download Center. Run the TACVista515HotFix51514.exe file. Reboot the machine. This error has also been observed If the PC is running a a 64-bit operating system which is not supported for LonMaker or NL220. See Echelon LonMaker and Newron NL220 on 64-bit operating systems for more information.

Issue Using the EGL, EGRL, EGLL5 which are obsolete Environment Vista Cause temperature/resistance data of EGRL, EGRLL, EGRL5 temperature sensors, or customer needs data to calibrate the sensors. Resolution EGL is replaced by the STD100-250 EGRL - STR100 EGLL  (2 thermistors) was not really replaced, as the average temp calc nowadays is done in the controller. The room version was named EGRLL. All these are for the Vista series. For more information regarding sensors, please visit Exchange Extranet.    Click here for the temperature/resistance chart for the old EGL, EGRL, EGLL5 Click here for the original Product and Installation pdf.

Issue Downloading new NXE or APB files using Lonmaker for controller updates Product Line Other, TAC Vista Environment Lonmaker 3.2 Cause Updating of software in a controller for more features or fixes. Resolution To update a new NXE or APB in a Lonworks controller using lonmaker follow these steps. 1. Download the NXE or APB file you intend to use. If it is a 100 series controller the files are available on extranet. Here is the link to the Xenta 100 series NXE files.   2. Locate the device you wish to upgrade in you Lonmaker drawing and select the load option 3. The next option screen will indicate the existing template name. Retain this name if the SNVTs are not changing. You may want to create a new template name if the SNVTs are being amended. 4. Select the Next option and then in the image name area browse to the NXE or APB file you want to download to the controller. 5. Select the next option then select the state you would like the device to be in after the new NXE has been downloaded. Then select the finish button. The application will then be downloaded to the selected controller.

Issue Download a Menta application file to a Xenta controller using the Menta software tool and a directly connected serial RS-232 cable. Product Line TAC Vista Environment Menta Programming Tool Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cableguide Kableguide Programming Serial Kit 0-073-0920-0 Note: The Online command is not available for the Xenta Server 700 devices so the following procedures do not apply to these devices. Cause Throughout the engineering, installation and commissioning phases of a project it may be necessary to download directly to a Xenta programmable controller. Also, performing a directly connected Menta download may be necessary in order to fix certain issues. See the following: The device is applicationless, or is not associated with a program record. (Subsystem: NS, #5) Resolution Use Menta Setup program (this is found in the TAC Tools menu) to select the Com port that is being used. Do not change any other setting before clicking Close. Connect the RS-232 cable and Programming Adapter between the PC and the RS232 port on the TAC Xenta. (these are part of the TAC Xenta: Programming Serial Kit, part no. 0-073-0920-0 For more information about the cable and adaptor see Xenta Cable Guide , Adaptor A1 and Cable L1 or Schematic for the RS-232 cable used to direct download Menta applications and system files.)  Open the Menta file to be downloaded. Change to simulation mode in Menta by clicking Options menu and selecting Simulate. In the simulation mode click Online. In the Connecting to Device dialog click Download. In the Tam32 dialog choose whether or not to generate files for an OP menu. For more information regarding Menta direct downloads see the TAC Menta Technical Manual  Section 16.4.1. Notes: Network information containing network addresses and other properties for the Xenta device and it's I/O modules is included in the download. For more info about this network info see the TAC Menta Technical Manual listed above or for problems with downloading the network information see No blueprint in TAC Xenta! Don't forget to download the network configuration if the TAC Xenta is to function in a network!. If Menta returns Parser Errors during download see Menta Parser Errors. If Menta returns Unsupported I/O Warning during download see Reference to unsupported I/O Error in COD file - Error:13. If a serial connection is not available on the PC a USB adapter can be used. The appropriate version of the TAC Menta Engineering Tool can be downloaded from the Exchange

Issue When downloading a controller in the Vista System Plug-in, messages are received saying the System Plug-in is waiting for the controller to restart, but this never completes successfully. This message may be shown many times. Environment Vista System Plug-in LonMaker Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause There may be several different causes including communications errors or a corrupted application. However, by taking the controller offline in LonMaker, any extraneous interaction with the controller is temporarily ignored during the download. Resolution First, please double check the Vista ToolPack version that is installed, and make sure the version matches TAC Vista Server version. If not, please uninstall the Vista ToolPack and install the correct version of ToolPack. TAC Vista ToolPack can be download from Extranet (Software and Firmware > Engineering Tools). In LonMaker force the controller's neuron chip into a configured, bypass mode: Right-click the controller and select "Manage" In the LonMaker Device Manager window click "Offline" Download the controller in the Vista System Plug-in. In LonMaker set the controller's neuron chip back to configured, online mode: Click "Online" in the LonMaker Device Manager window then close window

Issue Instructions on how to download an .MOT file into a Xenta Programmable controller Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Download Wizard Cause To reinstall or upgrade the firmware of a Xenta programmable controller, a .MOT file must be loaded using the Download Wizard. Resolution Get the latest (or desired) .MOT version onto the PC's hard drive. Download the appropriate .MOT for the controller requiring new firmware. To find the version of firmware in a controller, see How to view the current firmware version on a Xenta controller using the RS-232 cable. Go to the The Exchange Download Center and view the MOT files Locate the proper version and controller combination in the asset title. Download the desired .MOT version   Download the .MOT file into the controller Start the Download Wizard. Note: The download wizard is installed when Menta or EcoStruxure Building Operation Workstation is installed on the machine. Start > Programs > Schneider Electric > TAC Tools X.X.X > Download Wizard (For versions prior to 5.1.4, the path will be "TAC" instead of "Schneider Electric.") Follow instructions on the Download Wizard. System Choose to Retain Current .MOT or Download new.  Typically the choice will be to download a new .MOT. Ensure the device type is correct and matches the controller and .MOT file. Browse to the .MOT file downloaded from the Buildings Business Extranet. Application Choose to Retain Current, Clear memory, or Download New.  Typically the choice will be to clear memory. This is referring to the Menta application inside the controller.  If the application is cleared, the controller will be "applicationless" and cannot be downloaded through the Vista System Plug-in.  Some Menta application will need to be loaded through a Menta direct download before the controller can function again in a network. If you choose to load a Menta application through the Download Wizard, browse to the desired .MTA file.  Configuration If the application is set to clear memory, the configuration section will be grayed out.  No selections are necessary. This refers to the network description files.  The typical selection if the option is available is to retain current. Press Apply Download status is shown in % finished.  Do not interrupt this process! When the dialog states that the download has completed, close Download Wizard.  Load a Menta application if necessary through Menta direct download. For more information on Menta Cable needed to download, see Schematic for the RS-232 cable used to direct download Menta applications and system files.

Issue Where to find the documents for KNX System Integration with TAC Vista Product Line TAC Vista Environment KNX Protocol (LON) TAC Vista 5.x.x Cause When KNX Lighting system (LON) want to Integrate with TAC Vista system, It requires a Gateway to connect from KNX Protocols to TAC Vista. Resolution Download the KNX documents from the below link: Product Announcement - Field Devices Europe New 3rd Party Gateway between LON and KNX Learn more about LON-KNX Gateway

Issue Where to find information on how to set up SSL for webstation Environment TAC Vista Webstation Cause Can not find the documentation on how to set up SSL in Webstation Resolution This is documented in chapter 4.3 of the TAC Vista Software Installation Manual.

Issue Dell Optiplex GX 620 and GX 520: When logging into Vista the PC reboots. Environment Dell Optiplex GX 520 Dell Optiplex GX 620 Cause On some Dell computers, there is a problem with the graphics hardware acceleration. Resolution Adjust these setting with the following instructions: Right click on the desktop Select Properties Click on the Settings Tab Click the Advanced Button Select the Troubleshoot Tab Adjust the slide bar of the Hardware Acceleration down from Full two or three bars Click OK Click OK Again Now you should be able to open Vista without the PC Rebooting. This problem is experienced on Dell Optiplex GX 620 (TPI C-88-1-F-97) and Dell Optiplex GX 520 (TPI C-88-1-F-95)

Issue Where are the CE certificates available for the products in the Xenta family portfolio? Environment Xenta family Cause In some applications, CE certificates are required by the end customer or consultant as Declaration of Conformity .  Resolution In general, the CE certificates are available for download on The Exchange Download Center. Download Xenta CE Declarations certificates

Issue Database schema upgrade failed Environment Vista 5.1.X taclogdata database SQL 2005/2008 Cause The error message in the b0warlog suggests this is caused by the automatic database schema upgrade failing. Resolution See TAC Vista installation manual section 5.3

Issue Description of the file types and file extensions in Menta. Environment Menta Vista Lonmaker .AUT, .TLG, .MCB, .COD, .XLG, .ESP, .OPE, .OPC, .ESP, .BIN, .CHR, .COD, .XIF, .MTA, OPDOC.GOP, .SPT, .BIN, OPDOC.SPT, OPDOC.TMP, .BPR. Cause Description of the filetypes in Menta. Resolution The following data files are involved when creating a Menta application for a Xenta 280/300/401 device. .AUT Text file with application program source code and data including graphical block diagram. .TLG The trendlog definition. .MCB Macro block file (Group of blocks). .COD “Machine code” file in ASCII format for downloading to the TAC Xenta controller. .XLG The compiled trendlog definition. .ESP Specification file with public signals, their attributes etc. generated by TAC Menta. This file contains input data to the OP configuration tool. .OPE A file with an empty tree, i.e. an OP tree without a specification file. This is the kind of file that is created when the OP configuration tool is run from the program manager. .OPC A mix of an .OPE and an .ESP file. This file is created by the OP configuration tool when it has been invoked from TAC Menta. .BIN Binary file with OP menu tree data for downloading to the TAC Xenta controller together with the .COD file. .CHR National character set file for downloading to the TAC Xenta controller together with the .COD file. .XIF External interface file containing a standardized description of all network variables/ objects of the application program. The .XIF enables binding and communication with LonWorks nodes from other manufacturers. .MTA Menta project file, which can include all files (all types mentioned above except for .MCB and .OPE) related to a certain application. Once a file (for example .AUT or .OPC) has been inserted (saved) in the project file, it can be extracted (opened) anytime as an .MTA file. The .MTA file can be stored directly in the TAC Vista database. Note: The .MTA file can be stored in the TAC Vista database even though it can not be compiled. An .MTA file which is not compilable will not, of course, be possible to download into a TAC Xenta device. It must be correct and compilable before download is possible. In addition to the files listed above, the following data files are involved in the creation of the .BIN file. These files are placed in a specific directory for temporary files. OPDOC.GOP An ASCII file created by the OP configuration tool when the Generate command is executed. This file is converted to an .SPT file, which in turn is converted to a .BIN file OPDOC.SPT Intermediate ASCII file generated from the.GOP file. OPDOC.TMP Intermediate ASCII file generated from the.GOP file. BPR The Network Neighborhood file, describing the TAC Xenta device’s surrounding network nodes and groups. This information was taken from the TAC Menta Technical Manual.

Issue What kind of controller can be used to get values from a Modbus device into TAC Vista? For example, getting data from a Modbus meter into a BMS system running Vista. Product Line TAC Vista Environment TAC Vista TAC Xbuilder TAC Xenta server 731/913 Cause TAC Vista can not talk Modbus directly so you need to use a gateway controller. Resolution Xenta firmware version 5.1.4 and earlier only two controllers had Modbus communication capabilities: Xenta Server 731  For details see TAC Xenta 711/731 Web Server and Controller Xenta Server 913 For details see TAC Xenta 913 LonWorks Gateway Starting with Xenta firmware version 5.1.5, all Xenta Servers are now capable of communicating on a Modbus network both via TCP/IP and RS-485.  This includes Xenta 511, 527, 701, 711, 721, 731, 913. Note: Older Xenta Server devices built before firmware 5.1.5 have the capability of using Modbus over RS-485 once they have been upgraded even though the terminals are not labeled on the device. For information on how to wire these devices to reference a newer Xenta Server that does have the RS-485 A terminals labeled or see Xenta Server wiring and pinouts.

Issue Using the Xenta 421A, 422A, 451A or 452A I/O modules as a stand alone Lonworks node and all values are reading the default 0. Product Line EcoStruxure Building Operation, Field Devices, TAC Vista Environment Xenta I/O Modules Xenta 400, 421A, 422A, 451A, 452A as stand alone LON nodes Cause The Xenta 421A and Xenta 451A as stand alone Lonworks node require the UCPTConfiguration to be set to the necessary integer value for the required input. Resolution Please see the supporting documentation for the TAC Xenta 421A/422A and TAC Xenta 451A/452A that gives each nci value for the needed input type. To configure each input to the correct type please follow these steps: Navigate to the node in your Lonworks network management software (Lonmaker, NL220, Tridium, Etc.) Browse / Edit the controller to view all of the inputs, outputs, and configuration properties. Find the Universal Input module for the input you need to configure, and locate the UCPTConfigInput variable within that module Set this UCPTConfigInput variable to one of the following: 1 = 1.8 kohm thermistor 2 = DI with green indication 3 = 0-10 vdc 4 = 0-20 mA 5 = 10 kohm thermistor 6 = DI with red indication 7 = DI with green inverted indication 8 = DI with red inverted indication NOTE: This is normally done in Menta when you are using these controllers as I/O modules to a Xenta 401, Xenta 301, Xenta 302 base unit.  The scan time of all inputs is (200ms * number of inputs used).  So if there are 3 inputs, the complete module will have been scanned every 600ms.

Issue If steps used in creating a LNS network are performed in an incorrect order, you can get many errors which can be easily avoided. While this should not replace the Engineering LNS Networks manual  it can be used as a quick reference. Follow this link to access the complete Manual Environment LonMaker 3.X Vista System Plug-in Cause There are several steps to perform in order to create and update an LNS Network using LonMaker. Resolution LonMaker Cheat Sheet Create new LNS Network in LonMaker Set path to Vista DB in Server Setup Start TAC Server Open TAC System Plug-In Drag and drop Devices from Stencils Assign .MTA to Xenta Devices You will be prompted to Resynchronize, say no. Assign I/O Modules Set Neuron IDs Update Vista DB Create Group Bindings Resynchronize drawing (fix up) Download Application and Parameters Commission Base Units and Modules Commence Communication

Issue It may be useful to have logic in Menta programs trigger an event in Vista so that it can be recorded and stored in the event log. Environment Vista Workstation Menta Cause Alarms that have the Priority parameter set to 0 are used for info purposes only and only show in the event viewer and not the alarm viewer (queue). Resolution Events can be triggered by a Menta program by creating an Alarm block in Menta and setting the Priority parameter to zero. This causes the alarm to only function as an event and keeps it from showing up in the alarm queue. The following is taken from the Menta Technical Manual: The alarm priority is specified with the Priority parameter. There are 10 levels, 1 to 9 and 0, where 1 is the highest. Events with priority 0 (Information messages) have the lowest priority. They are not placed in the alarm database of TAC Vista and do not appear in the alarm overview. An example where using a priority zero alarm might be useful is to record as an event whenever an air handler enables and disables its economizer. This would be done as follows: 1. An ALARM block is created and named EVENTS\ECONOMIZER_ENBL. The Priority parameter is set to 0. Alarm Control is set to the standard alarm control object which is $Alr_Cntrl. The Tripped Alarm text is set as "ECONOMIZER ENABLED" and the Reset Alarm text is set as "ECONOMIZER DISABLED". 2. The ALARM block is then connected to the Economizer function. Now an event will be generated each time the economizer is enabled and disabled but an alarm will never pop up in the alarm viewer. An Events Viewer object could now be created to make it easier to view just economizer events without everything else. This is done as follows: In Vista Workstation right click the Root object and select New > Object > Viewer - Events. Type in a description and enter the Object ID of the economizer event that has been created. This can be found by locating an instance of the economizer event in the standard event viewer and copying the Object ID from there. The event viewer could be set up to display all priority 0 alarms instead of one specific event type by entering a 0 in Priorities in the Alarms section under the Event Specifics tab. The amount of time displayed in the event viewer can be filtered under the Date and Time tab. It may be useful to remove unneeded columns from the new event viewer so that only the relevant information will be displayed. In this example everything is unselected except Time, Object ID and Text under the Select Column(s) tab. The event viewer will automatically update and could be used for real-time monitoring of whatever event(s) it has been configured to display.

Issue In an old TAC Menta file, STATE members of SNVT_Switch inputs and outputs are assigned to DI/DO blocks. When editing existing SNVT_Switch I/O blocks, or adding a new one, it is not possible to select the STATE member from the drop-down list because the list is empty. Environment TAC Menta version 4.20 or higher Cause An application made in a version of Menta earlier than 4.20 would have had the STATE member of a SNVT-Switch declared as a digital input/output. From TAC Menta version 4.20, both the STATE and VALUE members of the SNVT_Switch are declared as analog input/output. Resolution Applications made with earlier versions of TAC Menta can still be downloaded with the latest TAC Menta version and will work correctly, provided you do not open the DI/DO block containing the SNVT_Switch member STATE and then exit the block dialog with the OK button. If this occurs: Delete this DI/DO block Recreate the SNVT_Switch STATE using a AI/AO block instead See TPI C-89-1-F5 for full details of this issue

Issue Cannot attach the Network interface to Lonmaker database when the Vista Server (Tacos) is started as a service. The error message is that the 'NIC interface is not connected'. Product Line TAC Vista Environment Echelon Lonmaker 3.1 Echelon Lonmaker 3.2 TAC Vista (all versions) Cause When updating Lonmaker and Vista databases as applications, it is important that Lonmaker be started first. Failure to do so can result in issues like this when Vista is reconfigured to start as a service. Resolution To get Vista and Lonmaker running together: Stop the Vista service and unregister it. If using a Loytec interface, set the Loytec Legacy Driver to run as a service (click the Advanced tab in LConfig). Start Lonmaker and attach the correct network interface. Ensure that Lonmaker is online. Start Vista Server as an application. From Lonmaker open the System Plugin. In the TAC Network properties, check that the correct network interface is selected. Update the Vista database. Start Vista Workstation and check that everything is online. Stop Vista and Lonmaker. Reregister Vista as a service. For details of these operations see Registering/Unregistering TAC Vista Server as a Windows service. Also see section 16.3 of the TAC Vista Technical Manual.

Issue Now the newest firmware version of Xenta server is 5.1.8, and the hardware version is 3. If a new Xenta server in an old project is needed to replace an old Xenta server with old version, it is not compatible with the old TAC Vista or I/NET software version of the project. So downgrade of the firmware is needed. Environment TAC Xenta 500/700/900 TAC Vista Cause Controller with new firmware is not compatible with the old TAC Vista or I/NET software. Resolution The controller with hardware 3 can be downgraded, but with only three versions: 5.1.6 SP1, 5.1.7 SP2 (or SP3 for X700) and 5.1.8 SP1. If any firmware other than these three versions is downloaded to the Xenta server, there will be no warning and it will be "bricked". Refer to TPA-VSTA-12-0029.00.

Issue What is the supported DC voltage on Xenta controllers? Environment Xenta controllers Cause DC Voltage is available for power. Resolution The table below list the supported Voltage DC specifications for Xenta controllers For more information check Data sheets for Xenta controllers located on The Exchange.   Xenta Controller Volt DC Support 411 19-40Vdc 421 21.6-40Vdc 451 21.6-40Vdc 471 19-40Vdc 491 19-40Vdc 400 Series 19-40Vdc 300 Series 19-40Vdc 200 Series 19-40Vdc 500 Series 19-40Vdc 700 Series 19-40Vdc 900Series 19-40Vdc 101 No Vdc Support 102 No Vdc Support 103 No Vdc Support 104 No Vdc Support 120 series No Vdc Support