Building Automation Knowledge Base

Issue When updating the Vista database in the TAC Vista System Pug-In an error message is displayed that says "Could not connect to Vista Server. Unable to request license." Product Line TAC Vista Environment TAC Vista System Plug-In Cause This error message is a result of not having the Vista Workstation license in the permanent license file. The licensing for the TAC Vista System Plug-In is included with the Workstation license. Resolution The license for Vista Workstation must be purchased in order for the system plug-in to work. For more information about the license packages see Vista 5.1 License Packages. 

Issue When trying to download a 5/7/9xx in XBuilder you get "Error code 401 - Unauthorized". Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 XBuilder Cause Password in XBuilder project does not match the password in the Xenta device. Resolution Select the 5/7/9xx in the Network panel The password is in the right hand panel of XBuilder under the TCP/IP Settings section. Change this to match the password in the 5/7/9xx. If the password is not known then refer to Receive a temporary session password for a Xenta 5/7/9xx if the password has been lost.

Issue How can the TAC Xenta OP be used with a TAC Xenta 100-series controller? How can the TAC Xenta OP know which TAC Xenta 100 controller it is communicating with? Which OP mode should be used? Product Line TAC Vista Environment Xenta OP Xenta 101 Xenta 102 Xenta 121 Xenta 122 Cause The TAC Xenta OP panel can be used to connect to a TAC Xenta 100-series controller to access input and output signals. Identifying the TAC Xenta 100 controller to configure is accomplished with a Service Pin message. If connecting directly to a TAC Xenta 100-series controller, or to a STR100-series device connected to the TAC Xenta 100-series controller, the controller sends out a Service Pin messages automatically, If this is not the case, or you connect on another location on the network, you could manually press Service Pin on the TAC Xenta 100-controller you want to connect to. For troubleshooting connectivity to a Xenta programmable controller, see "No Answer" on an OP when connecting to a Xenta 280/300/400. Resolution Configure the TAC Xenta OP Plug in the TAC Xenta OP Hold the Back and Enter button for 3 seconds to access the OP Service menu. Scroll down to option 10 for OP Mode. Change "Xenta 100" to ON with the + key. Press Enter. Change "Mode" to TAC with the + key. Press Enter twice to restart OP Connect TAC Xenta OP to a TAC Xenta 100-series device Plug TAC Xenta OP into OP jack on the TAC Xenta 100 controller, or to a STR100 device connected to the TAC Xenta 100. At prompt "Press <ENTER> to access Xenta 100", press Enter. At "Connecting to Xenta 100 ...", wait, or press the Service Pin of the Xenta 100-series  controller. Press Down. View Network Variables Select the network variable index number in the NV Index? prompt with the - and + buttons. Press Enter to view the signal. If the value is an input you can use + or - to provide a new value and press enter to accept it. If the signal is an application options set of bits then press enter to navigate between the bit number, + to change the value, and enter to accept the value.

Issue TAC Vista installations prior to TAC Vista 5.0.1 cannot be upgraded to TAC Vista 5.1.9  version directly. Product Line TAC Vista Environment TAC Vista Server TAC Vista Workstation Cause When upgrading Vista to 5.1.9, certain steps need to be followed to ensure that the process works properly. Resolution Note: If upgrading from an older version of Vista where the LNS port is at the root level of the system tree, instead of underneath the Vista Server, then you will need to follow the steps in Graphics binding were broken after a Vista upgrade to 4.5 from an earlier version to fix the binding paths of root level objects. TAC Vista installations between 4.3.0 and 5.0.0 must follow these upgrade steps in order: Upgrade to a version between 5.0.1 and 5.1.6 Upgrade to version 5.1.9   TAC Vista installations prior to 4.3.0 must follow these upgrade steps in order: Upgrade to a version between 4.3.0 and 5.0.0 Upgrade to a version between 5.0.1 and 5.1.6 Upgrade to version 5.1.9   Note: In a situation with multiple databases on a computer, make sure all are upgraded in this manner. After the upgrades have been carried out make sure the master server is started first followed by the slave servers.

Issue Alarm queue in the Vista Workstation states "No license for LonWorks communication" Product Line TAC Vista Environment Vista Workstation Cause The simplest cause of the issue, and the one that should probably be checked first, is that the license for LonWorks communication was not present at the time the server was started.  Oftentimes, this is due to starting server, realizing the engineering or end user dongle was not plugged in (or license server was not started) and then plugging it in.  The server will not actively poll for this license, it must be present at startup. Resolution Stop the Vista Server Ensure the license dongle is plugged in, or the license file is activated and installed on the license server. Restart the Vista Server Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" error when using a non LE dongle "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" error message in Classic Network "No license for LonWorks communication" Error in Windows 2008 Server X64 TACOS startup delay utility

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 How to order more LonMaker credits in order to commission more devices. Product Line TAC IA Series, TAC Vista Environment LonMaker LNS Cause There are two types of credits: Product specific credits like LonMaker and NL credits LNS credits   LNS LNS credits are assigned to the PC and when they reach zero, the LNS Server license goes into deficit mode. After 14 days the deficit mode will expire, at which time no LNS tools will be able to be used on that PC. To reverse the lockout, enough LNS credits must be ordered to cover the deficit and any additional nodes that need to be commissioned. Backing up, sharing, and restoring LNS databases can sometimes corrupt these LNS credits, which then prohibits you from launching any LNS plug-ins. For more help with corrupt LNS credits see Corrupted LNS Credits. LonMaker LonMaker credits are assigned to the PC. Both LNS and LonMaker credits are required, however when commissioning devices in LonMaker, LonMaker credits are consumed but LNS credits are not. Even though LNS credits are not consumed in LonMaker they are still necessary because certain LNS applications (i.e. TAC Vista System Plug-in) require them to operate. NL220 Each time a node is commissioned in NL220 it requires a NL credit and a LNS credit. NL credits are assigned to the NL220 dongle and can be used on other PCs in "MOVED" mode. LNS credits are also necessary in NL220 to operate certain LNS applications such as the TAC Vista System Plug-in.   To order more Echelon LNS credits see Ordering more LNS credits. To order more Newron NL220 credits see Ordering more Newron NL220 credits. Resolution To order more LonMaker credits: Echelon LonMaker v3.1 Open up a LonMaker database and go to LonMaker menu > LonMaker Credits Info... Here you can view how many LonMaker available credits that you have. Click on Add Credits... In the box named Credit Order, type in how many credits to order, then click Next. Following the instructions at the top of the window, click the Copy to Clipboard button to copy the PC key generated by LonMaker License Wizard. Click Cancel. Compose a new email and paste the PC key into the body of the email. Address the email to credits@echelon.com or your local Schneider Electric Buildings Business order department so they can place the order. Follow the instructions at the top of the email making sure to fill out all required fields. Once Echelon or the local Schneider Electric Buildings Business order department sends back an Application Key, open up the LonMaker License Wizard again. Click Next and paste the application key into the field titled "Application Key". Click Finish. Echelon LonMaker v3.2 Turbo Open up the LonMaker License Wizard by going to Start > All Programs > Echelon LonMaker > LonMaker License Wizard. Here you can view how many LonMaker credits that you have available. In the box named Credit Order, type in how many credits to order, then click Next. Following the instructions at the top of the window, click the Copy to Clipboard button to copy the PC key generated by LonMaker License Wizard. Click Cancel. Compose a new email and paste the PC key into the body of the email. Address the email to credits@echelon.com or your Schneider Electric Buildings Business Order Entry Department (888-444-1311) so they can place the order. Follow the instructions at the top of the email making sure to fill out all required fields. Once Echelon or the local Schneider Electric Buildings Business order department sends back an Application Key, open up the LonMaker License Wizard again. Click Next and paste the application key into the field titled "Application Key". Click Finish.

Issue In the event of a hardware failure on a Xenta controller you may need to perform a proper replacement procedure in the TAC Plug-In to install the new device. Product Line TAC Vista Environment Vista Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause Hardware failure in an LNS network Resolution In the event you have a piece of hardware fail on your LNS network you will want to follow the steps below to properly replace the device. Remove the bad controller and Install the new controller in its place Open your LNS network in LonMaker or NL220 Select to open the TAC System Plug-In in your network management tool In the Plug-In, locate the bad controller in the tree under the LNS Network pane and right click Select Replace... (the Replace TAC Xenta Device Wizard will open) Click Next Select the service pin button and press the service pin on the new controller Then click Next In the next window, click Next to update your Vista Database (NOTE: If you receive a warning during this process, see Warning about application file replacing a programmable controller in Vista System Plug-In) Once this process of updating your Vista Database is complete you will see the screen below confirming that the update was completed successfully Close the TAC Vista Load window Return to the Replace TAC Device Wizard and click Finish. This will complete the replacement process for your new device In some rare cases not all I/O modules will come online after this procedure. If this occurs a power cycle of the Xenta 400/300 will solve this issue.

Issue TAC ToolPack plug-ins (eg. STR 350 plug-in) do not show up Product Line TAC Vista Environment TAC Vista 5.1.4, 5.1.5, 5.1.6 Windows 7, Windows Server 2008, Visio 2010 TAC System Plug-in TAC Device Plug-in TAC Zbuilder TAC Xenta 100 Plug-in TAC Xenta 102-AX Plug-in STR 350 Plug-in Cause Not all plug-ins in the TAC ToolPack can run on Windows 7, Windows 2008 or Visio 2010. Resolution When installing TAC ToolPack on these operating systems only the supported plug-ins will be installed: TAC System Plug-in TAC Device Plug-in TAC Zbuilder TAC Xenta 100 Plug-in TAC Xenta 102-AX Plug-in If the desired plug-in is missing, configuration of your controller will need to be done manually in NL220, Lonmaker, or Vista. Read details about manually setup STR 350/351 in STR 350/351 manually setup without plug-in (nciOption1 and nciOption2).

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Time synchronisation is often an issue on large BMS installations. A central time signal is normally required to make sure all controllers, terminals or workstations have the correct time. If there is no internet connection available then the time has to be synchronised from a central source. Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Sigma Continuum Vista SmartStruxure Windows XP Windows 7 Server 2003 Server 2008 R2 Cause No internet connection available to synchronise the system time. Resolution Important The methods below contain steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. If using Windows XP, please use the following link - http://support.microsoft.com/kb/314054 If using Server or Windows 7 OS, please use the following link - http://support.microsoft.com/kb/816042 This has been tested for Time updates to an AS by simply using the PC IP address as the primary NTP Time Server. If the firewall is turned on you also need to make sure UDP 123 is open. Please note that Windows will add a dispersion to the time that may cause issues with time synchronization, please see Automation Servers ignore time sync message sent from Windows NTP server that uses local internal clock for details.

Issue Is it possible to run TAC Vista 5.X.X in Windows XP compatibility mode (When TAC Vista Installed on Windows Vista, Windows 7, Server 2003/2008) Product Line TAC Vista Environment TAC Vista 5.X.X Windows XP Windows Vista Windows 7 Windows Server 2003/2008 Cause If TAC Vista 5.x.x is Installed on Windows 7, Windows Vista, or Windows Server 2003/2008, is it possible to run the Vista Workstation on Windows XP using Compatibility mode. Resolution TAC Vista has several other applications that work together with Vista. These applications do not support compatibility mode. Upgrade to Vista 5.1.4 or later which support Windows 7. If the operating system is a 64-bit version, upgrade to Vista 5.1.5 or later. For the compatibility matrix see Software and Firmware compatibility matrix for older versions of the traditional product lines.

Issue The STR-150 Installation Instructions state that the stat wires into D1, X1, and M of the Xenta 100 series controller. However, this is not applicable to the Xenta 121, which does not have a D1 input. Product Line TAC Vista Environment Xenta 121 STR-150 Cause The correct terminal for the mode input from the STR-121 is labeled differently on the Xenta 121 versus all other Xenta 100 series controllers. Resolution Wire the stat as follows: STR-150 Xenta 121 Label Terminal Label Terminal Mode 11 Y1 5 Data 12 X1 7 M 13 M 6   The Purpose of output Y1 The only function that the STR-150 uses Y1 for is to get an effective occupancy signal from the Xenta 121. When the Xenta 121 is occupied, the man symbol will be displayed on the STR-150. If Y1 is already in use then the Status LED can be moved to a K output as explained inIs it possible to use an analog valve on the TAC Xenta 121-FC/HP and still have the effective occupancy active on the STR-150?. In order to activate this feature, the Hardwired status LED option must be selected. This can be found under the Configuration tab > Connected devices > Room unit in ZBuilder. If this feature is not desired then unselect Hardwired status LED and only wire up X1 and M. The STR-150 will still be able to send the controller the temperature, setpoint, bypass signal, and fan speed.

Issue When having issues with a specific NCI (SCPT or UCPT) in a XIF file it can be hard to understand the FILE definition in the XIF file in order to troubleshoot a given issue For information regarding NCI's that are not part of a FILE definition, refer to Understanding the NVVAL part of a XIF file Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment LonWorks XIF Cause The FILE definition can be somewhat cryptic - here is an example   FILE template 0 2 "1.1;" "2,23.24.25.26.27.28.29.30.31.32.33.34.35.36.37.41.42.43.45.46,0\x80,49,2;" "1,1,0\x80,60,12;" "1,1,0\x80,52,2;" "2,0.2.3.5.6.7.8.9.10.16.17.18.19.20.21,0\x80,48,2;" "1,0,0\x80,17,31;" "1,1,0\x80,34,2;" "1,1,0\x80,23,2;" "1,1,0\xA4,169,1;" "1,1,4\x80,3,8;" "1,1,4\x80,5,17;" "1,1,3\x80,1,2;" "1,1,4\x80,4,9;" "1,1,4\xA4,13,1;" "1,1,4\xA4,14,1;" "1,1,4\xA4,15,1;" "1,1,4\xA4,16,1;" "1,1,4\xA4,17,1;" "1,1,4\x80,18,1;" "1,1,0\x80,42,2;" "1,1,0\x80,36,2;" "1,1,0\x80,193,2;" "1,1,4\x80,8,2;" "1,0,3\x80,2,2;" "1,0,0\x84,165,1;" "1,0,0\xA4,166,1;" "1,1,6\xA4,2,8;" FILE value 1 1 116 0x0B, 0xB8, 0x09, 0x1D, 0x09, 0xFB, 0x0B, 0x80, 0x08, 0x77, 0x07, 0x98, 0x06, 0x13, 0x00, 0x02, 0x23, 0x28, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x78, 0x7F, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x80, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0xFF, 0x7F, 0xFF, 0x7F, 0xFF, 0x13, 0x88, 0x00, 0x00, 0x02, 0x0B, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 Resolution The FILE section describes the configuration variables (or SCPT's and UCPT's) for a device. Here is an explanation of the various parts of the FILE section.

Issue Xenta Server is offline in Vista and can not be reached via web interface. Product Line TAC Vista Environment Vista 5.1.9 Windows 7 Cause The PC has proxies configured. Resolution Open Internet Explorer Go to Tools > Internet options > Connections > LAN settings Disable "use a proxy server" Related Article: Xenta Servers are offline in Vista, although they can be reached via the web interface

Issue Use the block DI to monitor an IO module, and generate an alarm when it is offline. But the above-mentioned function cannot be realized. Product Line TAC Vista Environment Menta Xenta 301, 302, 401 Xenta I/O Modules Cause If there is a configuration error in block DI, the right alarm cannot be generated. It is necessary to check and correct the configuration error. Resolution Create and configure the block DI and Alarm block according to the following procedure, then the IO module status can be monitored. When it is offline, an alarm will occur in the alarm window in TAC Workstation.   1. Create a block DI. (See the Figure 1) Figure 1 2. Edit the block DI and input DI identifier such as the monitored module name, Status_411 in instance. (See the Figure 2)           Figure 2 3. Click BIND in Edit window, select the Online Device in BIND TO column, and input the IO module number in DEVICE ADDRESS. (See the Figure 3)               Figure 3 4. The module number can be found in IO Expansion and Wall Module Table of DEVICE SPECIFICATION in Menta Options toolbar. In the under instance picture, the M1 module, TAC Xenta 411, its device address is 1; the M2 module, TAC Xenta 421A, its device address is 2; and so on, the M5’s device address is 5. (See the Figure 4)       Figure 4 5. After creating and configuring the block DI, the block Alarm should be created. (See the Figure 5)                Figure 5 6. Then connect the block DI and Alarm. When the IO module is online, the DI value is generally 1. So the block NOT must be used. (See the Figure 6)         Figure 6   You can also reference Monitor the online status of a base unit's associated I/O modules.

Issue There are 31 different Parser Errors that can result from a Menta direct download to a programmable controller. Product Line TAC Vista Environment Xenta programmables Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause Causes vary by error code.  See details below and any links to additional information. Resolution No. Name Comment 0 PARSER_OK   1 PARSER_CREATE_OBJ_ERROR Seen immediately on an attempt to download directly.  Subsequent attempts result in "Download Failed."  Resetting the device caused the error to come back.  See in the error in COD window that its showing 0,0 coordinate pairs and underlying information.  The error's not in the Menta code itself.  No spaces allowed in the Program Specification -- a change from earlier versions.  May render your device unusable after attempting to download -- correct files won't download either. 2 PARSER_ALLOCATE_FLASH_ERROR   3 PARSER_IOMOD_SAVE_ERROR   4 PARSER_VERSION_ERROR   5 PARSER_APPNAME_ERROR   6 PARSER_ABBREV_ERROR   7 PARSER_TYPE_ERROR   8 PARSER_SOURCEFILE_ERROR   9 PARSER_SIGNAL_ERROR Error 9 has to do with the signal list (ESP-file) there all the public signals are transferred from Menta into the GraphOP tool by a sort of a long list. Normally, if you just make the application in Menta, this should not be any problem, however search and replace on signal names could give you headache. 10 PARSER_ALARMTEXT_ERROR Seems to download and fails on resetting device.  Had a case where this occurred when the application was too large due to generation of an OP tree where there wasn't one before.  Check memory. 11 PARSER_TIMESCHEDULE_ERROR   12 PARSER_IOMOD_ERROR   13 PARSER_IO_ERROR The terminal may not exist in this unit type.  Could also include situations where the same terminal reference is used in multiple references (this could be on the Xenta or the IO module). Typically caused by copy/paste. Reference to unsupported I/O Error in COD file - Error:13 for more information. 14 PARSER_CYCLETIME_ERROR   15 PARSER_CODE_ERROR Constants table has scientific notation, PVR blocks have scientific notation, Expression block attempting to use scientific notation, application size too large PARSER_CODE_ERROR Error in COD file - Error:15 for more information. 16 PARSER_DST_ERROR   17 PARSER_CHECKSUM_ERROR   18 PARSER_EOF_ERROR   19 PARSER_SNVT_ERROR   20 PARSER_SNVT_CRC_ERROR   21 PARSER_AUTHOR_ERROR   22 PARSER_BLUEPRINT_ERROR   23 PARSER_NO_BPR_FILE   24 PARSER_TLOG_RAM_ERROR   25 PARSER_TLOG_FLASH_ERROR   26 PARSER_TLOG_TO_MANY   27 PARSER_TLOG_ERROR_IN_DEF   28 PARSER_TOLG_PARSE_ERROR   29 PARSER_IMAGE_TOO_BIG   30 PARSER_RESET_BEFORE_PARSED   31 PARSER_SELF_DESTRUCTION_PERFORMED  

Issue "No Answer" when plugging in an operator panel (OP) to a Xenta 300/400/280. Product Line TAC Vista Environment Xenta OP Xenta Programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause There are several adjustable parameters on the Xenta OP that put it into different modes of communication/user preferences. This is a comprehensive list of all of those that might affect connectivity in different situations. If the controller is NOT commissioned, the red LED is blinking. The controller will not talk to the OP until commissioned. The OP will only talk to controllers on its same Domain ID. For troubleshooting connectivity to a Xenta 100 series ASC, see Use a Xenta OP with a Xenta 100 controller. Resolution Is the TAC Xenta controller commissioned? If the controller is NOT commissioned, the red LED is blinking. The controller will not talk to the OP until commissioned. Commission the controller from Lonmaker if using an LNS network (to download to the controller from the system plug-in first) Download and commission from TAC Vista if using a classic network. What mode is the OP in? Press the "escape" and "enter" buttons at the same time to get to the "OP service menu," scroll down to "OP-mode." Usually the OP should be in MAN mode (unless installing it in Lonmaker). Is the OP talking on the same Domain as the controllers? Check what domain being used in Lonmaker or TAC Vista. Go to the OP service menu, OP LON address (dom0), change the domain to match the setting in Lonmaker/TAC Vista.

Issue A stand-alone Xenta programmable controller can have an application downloaded into it using a serial cable and Menta. However, if that base unit has additional Xenta 400 I/O modules associated with it, they will never recognize and associate with their base controller. Product Line TAC Vista Environment Stand-Alone Xenta Programmables Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Xenta 400 I/O Modules Menta Cause A direct download of a Menta application does not download any network description information along with it (.ndb file) -- it is application only.  The controller can be downloaded via System Plug-in, which places the .ndb file into the controllers, but this requires the creation of a "dummy" network.  lontool32 offers a quick work around for truly stand-alone controllers. Resolution It is best to use the most current system program for this method as older versions may not work. Note: While Menta allows for configuration of the communications port from COM1 to COM9, lontool32 can only communicate on COM1. Follow the instructions in Reassigning a USB Serial Adaptor to a desired COM port to force the hardware to COM1. Then launch the Menta Setup tool from the Start Menu (Start >All Programs > Schneider Electric > TAC Tools X.X.X > Menta Setup) and set the Com Port to 1. Using Menta, create and download your .MTA file to the Xenta programmable using the direct connect method. This connection will also be used for lontool32 downloads. After Downloading, ensure Menta is "offline" to allow lontool32 an active connection on COM1. Open the lontool32 program which is located in your Menta program folder (e.g. C:\Program Files\Schneider Electric\TAC Menta 5.X.X\lontool32.exe) In lontool32, select the add button to add group, then select add node to add Base Unit. Double click on the Base unit to edit the node in the Network Configuration window. Select the Upload button to retrieve the Device and associated  I/O information. You will see this information populate the "database" column and associated I/O will populate the "I/O Modules" window below. *If the upload button remains grayed out, Ensure the Menta connection is "Offline" or follow the instructions here Reassigning a USB Serial Adaptor to a desired COM port to force the hardware to COM1. Also, check in the TAC Menta Setup program to verify that the Com Port is set to 1. Edit each I/O module by right clicking and selecting "Edit I/O". Use the "Service Pin" button to set the Neuron ID .  Enter the Subnet and a unique Node address in the appropriate text boxes. Repeat this procedure for every base unit in the network. If the network will contain more than one Base Unit, one must be designated as master by selecting the "master" check box in the Network Configuration window. When all the I/O has been updated, Select the "Download" button to generate and send the .NDB file to the base unit. Your I/O Modules should now be online which can be verified by the status light now oscillating every second vs. flashing quickly. If the Subnet Node information populates to a 0, you must type a subnet address and unique Node address for each unit on the network.  

Issue How to completely uninstall and remove TAC Vista 5.X.X Product Line TAC Vista Environment TAC Vista 5.1 and later versions Windows OS (Windows XP, Windows 7 tested) Cause Occasionally it is beneficial to be able to remove a TAC Vista installation completely, removing any indication it was ever installed. Resolution When using the full SQL version not administered by TAC Vista: Backup SQL database named “taclogdata”. Use the backup function in SQL Server manager. Save the database outside of the Microsoft SQL folder Server and TAC root directory (usually C:\Program Files\Schneider Electric (note: TAC Vista 5.1.3 and prior will have path C:\Program Files\TAC instead) and C:\Program Files\Microsoft SQL Server). Backup TAC Vista database using backup function in TAC Vista. Stop SQL manager, Task manager/processes – stop sqlserv.exe and sqlagent.exe if running. Remove all TAC Vista hotfixes using the uninstall program in Control panel Add/Remove programs. Remove TAC Vista Server 5.x.x using the uninstall program in Control panel Add/Remove programs. If additional TAC programs like TAC toolpack, TAC Xbuilder etc. are installed remove them as mentioned before. Remove SQL (Microsoft SQL Server 2005) using the uninstall program in Control panel Add/Remove programs. Delete remaining uninstalled TAC folders (usually C:\Program Files\Schneider Electric, TAC Vista 5.1.3 and prior will have path C:\Program Files\TAC instead). Delete remaining files in C:\Program Files\Common Files\TAC Shared. Delete remaining uninstalled SQL (Microsoft SQL server) folders (usually C:\Program Files\Microsoft SQL Server). Check to see if TAC needs to be removed from the registry – Start, Run, REGEDIT. Find the registry key folder HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDll Remove all keys containing “TAC Shared”, e.g. C:\Program Files\Common Files\TAC Shared\TACADDON01_ENG.dll. If applicable - Remove SQL from registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft \Microsoft SQL server. Reboot. If SQL Server (TACVISTA) still listed under Services, please follow steps in SQL server service cannot be started during Vista 5.X.X installation to solve the issue. See How to uninstall and completely remove TAC Vista 4.3 to TAC Vista 4.5 for steps to completely remove TAC Vista IV.

Issue Laptops are now being supplied with an express card slot instead of a PCMCIA card slot. The LON PCC-10 cards are PCMCIA cards and will not fit in an express card slot. Product Line Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment Using the Lon PCC-10 Card in a laptop that has an express card slot and not a PCMCIA card slot. Cause The latest laptops are being supplied with express card slots. The option of a PCMCIA card slot is becoming harder to specify. Resolution Although the slot in the laptop appears to be the same as a PCMCIA card, the Express card slot differs in many ways to the PCMCIA slot the PCC-10 card requires. Express card slot to PCMCIA card converters are available but not all support the PCC-10 card. Some express card to PCMCIA card converters only support 32 bit PCMCIA cards. The PCC-10 is a 16 bit card. Basic testing has been carried out on an express card to PCMCIA card converter with a LON PCC10 card from Roalan Ltd. You can purchase the EC1632 converter direct from Roalan Ltd. website by credit card through the Sagepay secure web server. Alternatively, you can phone your order to +44 (0)1202 861512 or fax it to +44 (0)1202 891454. The product is plug and play on Windows Vista and Windows 7 with a downloadable utility for Windows XP. (Only required on some computers. It was not required on the Dell E6420 when testing the card.) You can download the utility here: EC1632.zip, or from Roalan's website. Further information on the converter is available on Roalan's website. You may also download the EC1632 Installation Guide. The card should be plug and play. If your PCC-10 card does not work when using the express card converter, check the PCC-10 card installation using under the control panel. If the card is not working correctly review The Echelon LonTalk PCC-10 PCMCIA Network Adapter will not work with a Dell E6410 laptop. If you need to order a LON PCC10,PCMCIA card, they are available through Schneider Electric specification number WPA-LON-2.