Building Automation Knowledge Base

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.

Issue Echelon Node Utility with Loytec NIC-USB Network Interface Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment Microsoft Windows 7 32-bit Echelon Node Utility 2.04 Echelon OpenLDV 4.0 Loytec NIC-USB network interface Loytec NIC driver version 4.1.3 Cause There is a need to run Echelon Node Utility using Loytec network interfaces. Resolution The easiest way to accomplish this, is to use the NodeUtil Launcher. This program scans the registry for known interfaces. It was created by an active Community member. * Do take note Schneider Electric Product Support does not provide support for the NodeUtil Launcher - for support please write the developer of the tool. Below are two methods to manually achieve this if you don't want to use the tool. Here are 2 methods to run Node Utility using Loytec NIC-USB network interface. Method 1 involves accessing the Windows registry to check the path name of the Loytec network interface. We are not modifying any entries in the registry but as always, we should be careful when we access the Windows registry. Using Windows registry incorrectly can cause serious problems that may require you to reinstall Windows. Method 2 will configure the Loytec NIC-USB to use LON1. If you have used an Echelon LonWorks interface as LON1, you will need to detach it before you can use this method. Method 1 Run Loytec LConfig tool. With the Loytec NIC-USB network interface connected, go to the 'USB' tab and test the connectivity Run Windows registry editor (Start > Run > regedit). Navigate to the path HKEY_LOCAL_MACHINE\SOFTWARE\LonWorks\DeviceDrivers. The interfaces will be shown here. Look for the interface with '_LDV'. Run Windows Command Prompt and navigate to the Node Utility software directory (whichever directory you have put Node Utility) and run NodeUtil using the command nodeutil -D"". See example below. Method 2 Run Loytec LConfig tool. With the Loytec NIC-USB network interface connected, go to the 'USB' tab and test the connectivity. Click on the 'Advanced' button. Check the option 'LON1 Support for device' and select the appropriate device in the drop down list. You will need to reboot the computer for this to take effect. Once the computer has restarted, run Windows Command Prompt and navigate to the Node Utility software directory (whichever directory you have put Node Utility) and run NodeUtil. Node Utility should now run.

Issue Identify between the various dongles used by Vista 2k, Vista 4 and Vista 5 License systems. Product Line TAC Vista Environment Vista 3.3x (Vista 2000) Vista 4.x.x Vista 5.x.x Cause Licensing and dongle technology used by Schneider Electric Vista has changed as new revisions were released. The manufacturer of Vista dongles is Aladdin which causes the designs and colors to lead to confusion over which dongle works with which version of Vista. Resolution Visual inspection and some software tools can be used to differentiate between the various Vista dongles. The Dongle Reset Utility for Vista 4 can be used to determine whether the dongle is for End User or In House use. The getTACHLInfo.exe program which is installed with Vista 5 and the License Server can be used to determine whether a Vista 5 dongle is End User or In House. Vista 4 End User Dongle A Vista 4 End User dongle is only functional when an associated license file (PLF) is installed on a computer that was generated for the PSU ID of the dongle. This dongle can either be USB or LPT in size. If the dongle is LPT it is typically white in color. If the dongle is USB the color is typically blue. When viewing the dongle through the Dongle Reset Utility it will report the type of dongle as Enduser PSU and show the PSU ID. Vista 4 In House Dongle A Vista 4 In House dongle, commonly referred to as an Engineering Dongle, activates the Engineering license files which grants a branch or partner access to the majority of Vista licenses. This type of dongle is not intended for use on customer sites outside of commissioning and maintenance work. Custom licenses can be generated for In House dongles, but it is not common. This dongle can either be USB or LPT in size. If the dongle is LPT it is typically white in color. If the dongle is USB the color is typically blue. When viewing the dongle through the Dongle Reset Utility it will report the type of dongle as TAC Vista IV Inhouse PSU and show the PSU ID. Vista 5 End User Dongle part number 000857510 A Vista 5 End User dongle is only functional when an associated license file (LIC) is installed on a License Server that was generated for the Host ID of the dongle. Vista 5 End User dongles only come as USB dongles and are typically purple in color. When using the getTACHLInfo.exe command the dongle will indicate that it is Enduser and provide the dongle ID. Instructions can be found in Find a Vista 5 dongle ID. Vista 5 In House Dongle - Part Number - 000885000 A Vista 5 In House dongle, commonly referred to as Engineering or Maintenance dongle, grants a branch or partner access to the majority of Vista licenses. This type of dongle is not intended for use on customer sites outside of commissioning and maintenance work. Custom licenses can be generated for In House dongles, but it is not common. Vista 5 In House dongles only come as USB dongles and are typically black in color. When using the getTACHLInfo.exe command the dongle will indicate that it is Engineer and provide the dongle ID. Side by Side Comparison Dongles side by side for size comparison:

Issue In TAC Vista 5.1.9 when trying to lock a license file to an end user dongle, the taclic vendor daemon starts briefly, but then stops again and you see the error "Invalid license key (inconsistent authentication code)" in the taclic.log file. Usually you only see that message if the license file has been tampered with. 8:48:28 (taclic) Invalid license key (inconsistent authentication code) 8:48:28 (taclic) ==>INCREMENT Menta.View taclic 5.1 permanent 1 ISSUER=TAC \ ISSUED=30-may-2014 BORROW NOTICE=3424672 \ SN=FID__47eba299_146164ca427__7ec5 SIGN="13DC 795D AF25 E8ED \ D6EG 7BAA 8495 2ED7 B4B0 F6E4 EDD8 C3C1 6EAE 2BF0 598D 0759 \ AE4A 3C9E 391C A6ED B313 9971 369A 349C 8671 E194 2E42 E2DC \ 8A9A 7905" Product Line TAC Vista Environment TAC Vista 5.1.9 License Server Cause An issue has been detected in TAC Vista 5.1.9 when locking a license file to an end user dongle. You see the error "Invalid license key (inconsistent authentication code)" in the taclic.log file. The error is located in the taclic.exe file. Resolution Contact PSS for a permanent hotfix for this issue, or download it from Exchange Download Center.  Work around 1: Lock the license to the MAC address of the PC Follow Rehosting a Vista 5 License on the FlexNet License Server to rehost a license file to a MAC address.  Work around 2: Use a previous version of the taclic.exe file Access a PC having a previous version of the license server installed Locate the file "taclic.exe" and copy it - it's normally located in the TAC Vista installation folder under "License Server" Stop the license server on the PC having TAC Vista 5.1.9 installed Rename the original taclic.exe file to taclic_11.12.exe Paste the "taclic.exe" file you copied into the folder Start the license again  In general when working with the license system on TAC Vista versions from 5.1.8 and above, this utility can come in handy: TACLicenseServer Settings.

Issue The EcoStruxure Web Services Interface has been successfully setup in a Enterprise Server but cannot see the Vista objects / points in Workstation Product Line EcoStruxure Building Operation, TAC Vista Environment StruxureWare Building Operation 1.4.x TAC Vista SmartStruxure Interface TAC Vista 5 and above Cause The Web Services interface hosts the Vista objects in the System / Hardware / EcoStruxure Web Services / TAC Vista folder, these must be hosted to the Server to become visible within Workstation.  Resolution Once you have navigated to the System / Hardware / EcoStruxure Web Services / TAC Vista folder you will see the list of objects available associated with the TAC Vista user name setup in the TAC Vista SmartStruxure Interface. From the list of Vista objects select the required ones you wish to use within the Enterprise Server database. The right click on the selected folder and select the Host EWS Objects... option. The next option is to select the Vista EcoStruxure Web Service interface that will host these objects. The objects will now be visible within the Enterprise Server / Workstation.   For how to create Vista interface in SmartStruxure, refer to How to Create TAC Vista Interface to SmartStruxure. For additional details see Creating an EcoStruxure Web Service Object on the SBO WebHelp site. 

Issue How to use L-IP in Vista Classic network. Cannot service pin controllers under L-IP in Vista Classic network. Values in Classic network under multichannel L-IP are showing "Invalid Address" and "No such entity" Product Line TAC Vista Environment TAC Vista Workstation L-IP NIC852 Cause LOYTEC L-IP needs to be configured as a server and into the smart mode in order to be used in the Classic network. NIC852 needs to be used with LOYTEC L-IP in the Classic network. Resolution Configure L-IP as a web server (How to Configure Lonworks Network Interfaces to Communicate on the IP to a Loytec L-IP Router using the Echelon driver).   Configure L-IP into Smart mode. There are two ways to configure L-IP into smart mode.  Flip the DIP switch or using a serial cable (RS232). Flip the DIP switch to activate the smart mode. The dip switch is at the side of the L-IP next to the Ethernet port. L-IP DIP switch has seven switches.  By default, DIP switch 3 is down and the rest switches are up. Flip dip switch 2 down to activate the smart mode.   Use RS232 serial cable to activate the smart mode. Read more information in the LOYTEC L-IP User Manual Chapter 4.4.2.2   Configure NIC852 Open LConfig and go to NIC852 tab (Start/All Programs/LOYTEC Network Interface/LConfig). NOTE:  LOYTEC Network Interface package can be downloaded from LOYTEC website, called NIC-LOYTEC Network Interface Software X.X.X Make sure “Enable device” is checked Click on “CNIP Configuration”. Under “Device IP Address” use computer's address and use 1628 as Port number. Under “Conf. Server IP Addr.” Use L-IP’s IP  address and use 1629 as Port number.   Click “OK”. Click on “Test Device”, and should return the serial number   Add LIP as a LTA in Classic network. Right click on the Vista Server and choose “New->Device->Communication Port-LOYTEC” Name the LTA (for example: LIP).   Edit LIP in Classic network. Right Click on the LOYTEC L-IP (in this example the LIP LTA) just added and choose “Properties”. Under Communication Settings, click on the arrow and select the available NIC852.   Commission the LIP in Classic network. Right click on the LOYTEC L-IP just added (in this example the LIP LTA) and choose New > Device > LonWorks Network Name the network (for example: LNS Right click on the LonWorks Network just added (in this example the LNS network) and choose “Commission and Download” Select the LonWorks Network (in this example the LNS network) and click the “Start the Selected Operation” button (up-down arrow button on the top) Click “Continue” when asking for “Continue operation?” Operation successful message should be displayed.   Refresh (F5) the tree in the left panel in TAC Vista Workstation. The L-IP LTA (in this example the LIP LTA) and the LonWorks Network (in this example the LNS network) should turn green afterwards. Now the L-IP is ready to communicate in the TAC Classic network.

Issue Xenta Controllers can report "offline" status if they encounter bandwidth limitations Completion Event Failure warnings CRC Errors showing in controller properties Loytec Multi-port router/switch channel LED blinking fast red (traffic overload) Product Line TAC Vista Environment Lon Networks Vista Xenta LPA Loytec Protocol Analyzer Cause HMI Vista on-line/off-line presentation is based upon receipt of the heartbeat messages. Every TAC Xenta 280/300/401 controller is periodically sending a message to the other members of its TAC Xenta reporting (including the group master) that it is on-line. Proprietary "LACNet-IAm" and "LACNet-GroupIs" are sent every 15 seconds to HMI Vista. Without the HMI receiving these heartbeats, Vista will display the controller or group in an offline state. The TAC Xenta group is specified by the tag_0 and the TAC Group is specified by tag_1 bindings in LonMaker or NL220. Resolution Actions for reducing Bandwidth: TAC Xenta 100s Slow down the SendHeartBeat Check sensors etc that are affecting all bound nvo's Decrease traffic of SNVT group bindings. For large groups of bound controllers, use UNACKD/RPT instead of ACK service type. 3rd Party LonWorks devices Change update rates for nvo's. If possible, the product manual should show how. Decrease traffic of SNVT group bindings. For large groups of bound controllers, use UNACKD/RPT instead of ACK service type. TAC Xenta 280/300/401 TACNV and SNVTs Verify delta and period values make sense for the particular signal and application. Decrease traffic of SNVT group bindings. For large groups of bound controllers, use UNACKD/RPT instead of ACK service type. Increase the trend log time span (the total log time) if possible. Of course, this will increase the memory usage in the Xenta, but this will make TAC Vista to do the fetch more seldom and result in reduced traffic. TAC Xenta 280/300/401 + TAC Xenta I/O Modules If sensitive sensors (i.e. pressure sensors) are connected to I/O Modules, a high load of communication will be generated. Bandwidth issues may arise when 401s with many I/O Modules are each reading multiple sensitive sensors. Increase the Min Send Time for every I/O Module. Min Send Time is how often the I/O module is allowed to communicate with the TAC Xenta. This setting is located in Device Specification in Menta. Reduce Trend Log definitions in the controllers. If possible, try to have all your "high speed sensors" connected to one, or a few I/O modules, so it's only a few I/O modules sending a lot to the Xenta. LonWorks routers Implement L-Switch routers to reduce traffic on high bandwidth segments. Set router to Configured Mode, not Repeater Mode. Vista Server Trend Log Stagger Vista server Trend Log start times so that they do not all attempt to get fetched at once. See also Troubleshooting LON Network Communication More information can be found in Tool for LON / LPA Capture Traffic Analysis (login required) which discusses the LPA Analyzer Tool. This may be useful for interpreting the LP file data.

Issue LMTOOLS was not installed on the computer that Vista 5.1.8 was installed on. Product Line TAC Vista Environment Vista LMTOOLS LMAdmin Cause The TAC Vista license administrator tool has been upgraded to LMAdmin, a web based license administration tool accessible using a web browser. Existing license files are compatible with the new LMAdmin tool that is included in the TAC Vista Server and TAC License installers. Resolution If the license server is not running as a service, Vista is unable to locate the license, or you need general troubleshooting help then see License troubleshooting in Vista 5.1.8 or greater. Flexnet License Admin   The default license file folder has changed with the new LMAdmin license tool. The new default license file folder is "C:\Program Files\Schneider Electric\License Server\taclic\licenses\". For 64-bit OS the default license path is "C:\Program Files (x86)\Schneider Electric\License Server\taclic\licenses\". The license server administration, LMAdmin, is installed as a web server and is accessible at http://localhost:8080 after the installation; a shortcut will also be placed in the start menu. The location of this shortcut can be found by going to Start > All Programs > Schneider Electric > TAC Tools 5.X.X > FlexNet License Admin. To check what your license file contains, how many seats are available for each program, and how many are in use click on the Concurrent icon.   To log into LMAdmin, click on Administration in the top right corner. The default login and password is admin/admin and it is recommended that this is changed after the installation is finished. User accounts can be managed in the Administration area, under the User Configuration tab. Click the New icon at the top of the window to add users. The edit button at the end of the row of each user will allow the user name and password to be changed. There is also a delete button to remove unwanted users. If the computer running the TAC Vista License server enters a power save mode, the license server may have to be restarted manually in Computer Management > Services and Applications > Services.   TAC License Setup It is recommended to use the "License Setup tool" in the start menu instead of the license popup dialog when specifying a license server name or license file location. The License Setup tool can be found here; Start > All Programs > Schneider Electric > TAC Vista Server 5.X.X. Note: When upgrading Vista from a version 5.1.7 or older to a newer version, the old license file path may still exist in the registry. This will not impact the license server in any way. The old path can be removed if you desire through the TAC License Setup. During the installation of TAC Vista Server and TAC License, any license files located in the old license file folder are automatically copied to the new license file location; the original files are not removed.

Issue What are the typical steps to install and configure Vista OPC Server? Product Line TAC Vista Environment Vista 5.1.x Vista OPC Server 1.6.1 Cause OPC Server can be used in many integration situations to provide data to other parties or bring third party data into the Vista front end. Resolution  Install TAC Vista OPC Server 1.6.1 installation package Add a Windows Account for Vista OPC Server Start Computer Management In System Tools\Local Users and Groups\Users click New User Name the user OPC_Communication Provide a password Uncheck the User must change password at next logon checkbox Check User cannot change password checkbox Check Password never expires checkbox Click Create and Close. Add user to the Administrators group Configure Service In Services right click on TAC Vista OPC Server and click properties Ensure Startup type is Manual On Log On tab select This Account Browse to the local account OPC_Communication Provide the password in the Password and Confirm password fields Click OK Configuring DCOM Start Component Services Double click Component Services\Computers\My Computer\DCOM Config Locate the COM Server TAC Object Server OPC DA Services and select properties Click the Identity tab Select This User Select the local account OPC_Communication Provide the password in the Password and Confirm password fields Click OK Locate the COM Server TAC Object Server OPC AE Services and select properties Click the Identity tab Select This User Select the local account OPC_Communication Provide the password in the Password and Confirm password fields. Click OK Create a Vista User Account Start Vista Server Start Vista Workstation and Log In In the root TAC Vista folder create a new account (User - Vista or User - Windows Domain Group) Name the user TACOPC Modify the properties of the account Set the password Set an authority level that OPC Clients should use when accessing the OPC Server Set the Logout time to zero(0) Configure the Vista OPC Server Login Open TAC Vista OPC Server Setup (Program Files\Schneider Electric\TAC Vista OPC Server\Vista OPC Server Setup) Ensure the Retry connect period is 360 seconds. In the logon to TAC Vista Server click Login using the following Vista Account In the Username type TACOPC Type the password Click OK Confirm the change took place, if it is not refer to OPC server for TAC Vista will not keep the login settings in the TAC Vista OPC Server setup. Configuring Windows Firewall If Vista Server and OPC Server are on the same computer then no firewall exceptions are required. Consult the OPC Server manual (Chapter 4) for the firewall exceptions if using a separated OPC Server and Vista Server setup. Configuring OPC Client DCOM Settings If the OPC Client is on another computer then create a user account to match the one used by Vista OPC Server. Start Computer Management In System Tools\Local Users and Groups\Users click New User Name the user OPC_Communication Provide a password Uncheck the User must change password at next logon checkbox Check User cannot change password checkbox Check Password never expires checkbox Check Create and Close Configure Access Permissions Start Component Services on the Vista OPC Server computer under Administrative Tools In the Tree Structure right click on Component Services\Computers\My Computer and click properties Click the COM Security tab In Access Permissions click Edit Limits Click Add Select the local account OPC_Communication (EXAMPLE: W7USCNU1342VXXX\OPC_Communication) In the allow column select Local Access and Remote Access Click OK In Access Permissions click Edit Default Click Add Select the local account OPC_Communication In the allow column select Local Access and Remote Access Click OK In Launch and Activation Permissions click Edit Limits Click Add Select the local account OPC_Communication In the allow column select Local Launch, Remote Launch, Local Activation, and Remote Activation Click OK In Launch and Activation Permissions click Edit Default Click Add Select the local account OPC_Communication In the allow column select Local Launch, Remote Launch, Local Activation, and Remote Activation Click OK Configure Local Security Policy Select the Local Policies\Security Options\Network Access: Sharing and security model for local accounts policy Set the policy to Classic - local user authenticate as themselves Click OK Repeat these steps for the OPC Client computer Configuring OPCEnum Start Component Services on the Vista OPC Server computer In the tree structure Component Services\Computers\My Computer\DCOM Config right click on OPCEnum and click properties On the general tab change Authentication Level to Default Ensure Run Application on this computer is checked on location tab Click the Identity tab Select This User Browse to the local account OPC_Communication Provide the password in the Password and Confirm password field Click OK Repeat these steps on the OPC Client computer Start the TAC Vista OPC Server In Services right click on TAC Vista OPC Server and click start For more OPC Server issues please see Vista OPC Server Installation and Known Issues. A good overview of  OPC integration and the necessary COM and DCOM settings is located here.

Issue The upgrade fails, and you may get the following error message: Warning Error: Could not create remote directory. Product Line TAC Vista Environment TAC Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause To upgrade the Xenta Server system software to version 5.1.3 and later, Xenta Server HW 2.0 or later is required (otherwise the upgrade will fail). All Xenta 700 have HW 2.0 or later. In some cases the file system of the Xenta Server can be corrupt, which prevents the upgrade software to connect to the device.   Resolution First of all, try to do the upgrade a second time. If the upgrade still fails, please do the following: Check if you can ping the device and that port 80 or 443 aren't blocked. If the above is ok, format the device from the console by typing "format". (Warning: All data will be lost!) Install the system software again. If it still fails, replace the Xenta Server. Please note that If the Xenta Server is HW 1.1 or earlier you can only upgrade to version 5.1.2 or earlier. If you have to upgrade to 5.1.3 or above you need to replace the Xenta Server to a unit that has HW 2.X. (See also Error: "Could not create remote directory" or "Failed to establish connection with the target device" when trying to upgrade/downgrade a Xenta 5/7/9xx controller)

Issue After updating the computers Java version to Java 7 update 51, graphics are not displayed when using Webstation. Then a security warning is displayed. Missing required Permissions manifest attribute in main jar: http://xxx.xxx.xxx.xxx:/com.SE.webstation.Main/applet/applet-1.4.1.68.jar If you don't see the error above, but just get a blank window, please refer to Webstation graphics not working after updating to Java 7 Update 65. Product Line EcoStruxure Building Operation, Satchwell MicroNet, TAC Vista Environment Webstation Cause From Java 7 Update 51 and onwards, Java has enhanced the security model to make user system less vulnerable to the external exploits. The new version of Java does not allow users to run the applications that are not signed (Unsigned), Self signed (not signed by trusted authority) and the applications that are missing permission attributes. Risks involved in running each kind of applications: Unsigned applications An application without a certificate (i.e. unsigned apps), or missing application Name and Publisher information are blocked by default. Running this kind of application is potentially unsafe and present higher level of risk. Self signed application (Certificate not from trusted authority) An application with self-signed certificate is blocked by default. Applications of this type present the highest level of risk because publisher is not identified and the application may be granted access to personal data on your computer. Jar file missing Permission Attribute Permissions Attribute verifies that the application requests the permission level that developer specified. If this attribute is not present, it might be possible for an attacker to exploit a user by re-deploying an application that is signed with original certificate and running the application at a different privilege level. Resolution As a workaround, the user can use Exception Site list feature to run the applications blocked by security settings. By adding the URL of the blocked application to the Exception Site list allows it to run with some warnings. Steps to Add URL to the Exception Site list: In control panel go to the Java Control Panel Click on the Security tab Click on the Edit Site List button Enter your site details (This example http://www.SBO-Site.com) Click the Add in the Exception Site List window. Select continue Repeat the process until all the sites AS/ES have been added. Then select OK to complete and OK on the next window to exit the Java control panel. Next time you use Webstation to access the AS/ES you will be asked if you want to run the application. Tick the box so this is not displayed again. Then select Run. The graphics should now be displayed. You will need to repeat this process on any computer you which to use Webstation on.

Issue Remove the Routing tables from I/NET and Xenta 527 devices Host conflict or station conflict error messages displayed at the I/NET Host. Incorrect Links, Hosts and IP addresses that do not exist in your Network are shown when penetrating Network Configuration. Product Line Other, TAC INET, TAC Vista Environment I/NET IP Routers Xenta 527 Cause Host or station conflict errors can be caused by old information stored in a routing table. From time to time, it may be necessary to purge that information and allow the tables to be rebuilt automatically. The only way that routing tables can become corrupted is if a laptop was used to connect to the system from a different Network or from the Outside. Once connected, its IP table is broadcasted to the other devices like PCs and NPRs, thus populating the table with entries that does not belong or is non-existent for this location or system.  Resolution Managing I/NET Routing Tables   I/NET Host Workstation View the I/NET Routing Table See Viewing the routing tables on a PC using I/NET Seven for complete instructions. Delete a Single entry in the I/NET Routing Table Go to Start > Run Type Telnet and hit Enter Type open, hit the space bar, then enter the IP address of the PC Press Enter When the login comes up, type csi, hit enter Type LA  and hit enter to list all routing table entries Type ipdel xxx.xxx.xxx.xxx with xxx.xxx.xxx.xxx being the IP address of the device you wish to delete Press enter Clearing the I/NET Routing Table Shutdown the I/O Server Open Windows Explorer Browse to C:\INET Seven Data (or C:\Program Files\INET Seven) Delete the .dat files (you may want to save a backup to another location) Delete the routing table from any device listed as a Reference Host or the table will repopulate Start I/NET Other Method: See Bogus Links, Hosts and IP's in Netcon for instructions on using the delall command in Telnet     Xenta 527-NPR; Xenta 913; Xenta 527 Web Server (See Clear the IP routing tables of a Xenta 913)  Viewing the I/NET Routing Table View Connecting a serial cable to a Xenta 5/7/9xx controller to configure HyperTerminal to communicate to the Xenta Device. Log into the Xenta Device as the root user At the dsh/> type “inet ip” Press enter Deleting a Single entry in the I/NET Routing Table View Connecting a serial cable to a Xenta 5/7/9xx controller to configure HyperTerminal to communicate to the Xenta Device. Log into the Xenta Device as the root user At the dsh/> type “inet ipdel” then the IP address of the device you wish to delete Press enter Clearing the I/NET Routing Table View Connecting a serial cable to a Xenta 5/7/9xx controller to configure HyperTerminal to communicate to the Xenta Device. Log into the Xenta Device as the root user At the dsh/> type “inet delall” Press enter Type “inethost” and press enter Verify or set the Reference Hosts Clear the routing table from any referenced device to ensure old data is not repopulated Restart the Controller to re-populate the routing table   You can also realize this through the web page of Xenta device. Open the web page of Xenta controller, browse to Utilities-I/NET-I/NET Command Line, and type the command below or above. The result is the same as using HyperTerminal, which is also an easier way. Typing “inet help” or “inet” gives every I/NET option within the controller inet - I/NET Help ip - Display IP table list ls - Display Link/Station table list cp - Display Compressed table list gp - Display Global Point table list mm - Message masking all - Display all lists ipadd - Add an IP address to the tables ipdel - Delete a single ip record delall - Delete all ip records   NPR-2000 Viewing the I/NET Routing Table Go to Start>Run then type “Telnet” and hit Enter Type open hit the space bar then enter the IP address of the NPR Press Enter When the login comes up, type csi hit enter Type “LA”  and hit enter to list all routing table entries Deleting a Single entry in the I/NET Routing Table Go to Start>Run then type “Telnet” and hit Enter Type open hit the space bar then enter the IP address of the NPR Press Enter When the login comes up, type csi hit enter Type “LA”  and hit enter to list all routing table entries Type “ipdel xxx.xxx.xxx.xxx” with xxx.xxx.xxx.xxx being the IP address of the device you wish to delete Press enter Clearing the I/NET Routing Table (See Bogus Links, Hosts and IP's in Netcon)  Go to Start>Run then type “Telnet” and hit Enter Type open hit the space bar then enter the IP address of the PC Press Enter When the login comes up, type csi hit enter Type “LA”  and hit enter to list all routing table entries Type “delall” and hit enter to clear the table   Appendix A: I/NET Telnet Commands Glossary: Help – Displays all available commands in the NPR or I/O Server.  Note there are some differences between the NPR and I/O Server. ipadd a.b.c.d – Adds the IP to the routing tables. ipdel a.b.c.d – Deletes the IP from the routing tables. gpadd LLSSPPBBTT XX | a.b.c.d – Adds a global point link or global point IP to the routing tables. delall – Deletes “all” local routing table entries. setpass password – Change the telnet login password (6 characters max). +cpdel LLLL SS – Deletes the specified link/site address from the CP table. +debug gp on|off – Turns global point debugging on or off. +reboot – Reboots the NPR. +wdog – Reports watchdog errors. +wdogrst – Clears the watchdog errors. +Dx – Toggle debug output to COM3.  x=0/1; 0 = off, 1=on.   List Commands: +LR – IP Stack routing table. LI – IP routing table. LM – IP routing masks. LL – Link/Station routing table. LG – Global point routing table. +LC – Compressed routing table. +LS # - Compressed routing table: station to site maps for the specified link #. LA – All routing tables. LU – System metrics. *LD – Dial maps.  + = NPR only * = Host PC only   Appendix B: Method for Clearing Routing Tables at a Large Site See Possible solution to doing a Telnet session with a system wide firewall setup.   Appendix C: Suggested Reference Host Settings   Click here to be linked to the TAC INET Seven Getting Started. Click here to be linked to the TAC INET Seven Operator Guide.   A Reference Host is any TAC I/NET workstation, NPR, or Xenta 527/527-NPR that will serve as a source of IP addresses. Any of these devices attached to an Ethernet LAN can be used as a Reference Host. Each time I/O Server is started on a workstation, it provides the workstation’s IP address to each remote host designated as a Reference Host. I/O Server also requests and receives a list of all host IP addresses that are known to the remote host at that time. I/O Server must be running on the remote host for this address exchange to occur. I/O Server compiles and maintains a list of all the remote hosts that it learns about. Ultimately, all hosts in the network will know the IP addresses of all the other hosts. Ideally, you should determine 1 or at most 2 devices to serve as your Reference Host.  This device would ideally be a Xenta Server or an NPR, but a Host workstation that has I/O Server running 100% of the time will work as well.  All devices on the system will use this as a single Reference Host. No others are needed.  When the device comes online it will contact the Reference Host and get the site’s Routing Table.  The Reference Host can have an empty routing table.  Once the Routing Table is shared, Reference Hosts are no longer needed.  You can leave the single entry in place. This will allow a quick recover, in the event of a critical system failure. Here are a few reasons for using multiple Reference Hosts: Temporarily add a new device as a Reference Host on the Sites Reference Host or a workstation to aid in bringing it online A large site may desire to have 2 Reference Hosts in case one is offline when a device comes online. An I/NET site that spans multiple locations may wish to declare a local Reference Host for each building and a network Reference Host  

Issue When TAC Vista and the SmartStruxure Enterprise server are installed on the same machine the EcoStruxure web service object will not connect to the Vista Server. Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista SmartStruxure Solution EcoStruxure Web Services TAC Vista SmartStruxure Interface 1.0 Cause The default ports used by the SmartStruxure Enterprise server are HTTP 80 and HTTPS 443. These are the exact same ports used for the communication between the TAC Vista SmartStruxure Interface and EcoStruxure Web Services Resolution TAC Vista SmartStruxure Interface settings change the HTTP and HTTPS ports to something that is available and not in use on the machine. In the example below HTTP 8181 and HTTPS 8191 are used. After these ports are changed click apply and stop and restart the TAC Vista SmartStruxure Interface service. After these port changes are made login to the Enterprise server and select properties on the TAC Vista web services object. Change the service URL to the localhost address and the proper port that was chosen in the TAC Vista SmartStruxure Interface settings. In the example below http://localhost:8181/EcoStruxure/DataExchange was used. The local IP address could also be used in place of the localhost if needed. Another point needs to be kept in mind is that only the user in the default System user group can be used. Don't try to create other System group. And all the letters in the password need to be in capital in the password field of the window above. This is a defect that will be addressed in the next release of TAC Vista to SmartStruxure interface. For how to create Vista interface in SmartStruxure, refer to How to Create TAC Vista Interface to SmartStruxure.

Issue TAC Xenta Server webpage does not work smoothly. A typical example is when you try to change a value. The small dialog that should pop up to change a value might pop up and immediately disappear. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment TAC Xenta Severs Xenta 511, 527, 701, 711, 721, 731, 913 TAC Vista 5 Webstation Cause Using unsupported version of Java may cause various issues. For example, Xenta server webpage does not display smoothly, time schedule does not show up or can not be edited, etc. Resolution Below is the Java compatibility matrix of TAC Vista 5.   5.1.9 5.1.8 5.1.7 5.1.6 5.1.5 5.1.4 5.1.3 5.1.2 5.1.1 5.1.0 5.0.3 5.0.2 5.0.1 5.0.0 Java 1.5 update 06               X X X X X X X Java 1.6 update 11           X X               Java 1.6 update 17            X 1                 Java 1.6 update 20 X X X X X                   Java 1.7 update 51 X                           1  TAC Xenta Server 5XX/7XX/913 SP1. Log into The Exchange and then click here to download the full Vista Compatibility Matrix. To uninstall an unsupported version of Java and install the supported version, refer to Xenta Server webpage automatically logs out while waiting for Java to load.

Issue If the STR 350 plug-in is missing, then the STR 350/351 setup needs to be performed manually in NL220, LonMaker, TAC Vista Workstation, or TAC Menta. Product Line TAC Vista Environment TAC Vista 5.1.4, TAC Vista 5.1.5 Windows 7, Server 2008 Cause Not all plug-ins in the TAC ToolPack can run on Windows 7 or Windows 2008. Read details in TAC ToolPack plug-ins are not showing up. Resolution If the STR 350 plug-in is missing, then the STR 350/351 setup needs to be performed manually in NL220, LonMaker, TAC Vista Workstation, or TAC Menta. NL220 STR 350/351 setup steps are shown below: Use the STR 350 device template to create a new node on the channel. Note: the device template is located at C:\LonWorks\import\TAC\IO Modules (Default location) Double click on the STR 350/351 device and make necessary changes to any signal under “NVs” tab. TAC Workstation STR 350/351 setup steps are shown below: Expand the tree structure in the left panel. Select the desired signal to change in the right panel. If a STR 350/351 is connected to a programmable controller (Xenta 280/300/400), then the STR 350/351 can be added in the Menta file similar to an IO module. Setup steps are shown below: Under “Options/Device Specification” select “Add STR Module…" Under “Type” Select “STR350/351” and Under “Bit(s)”, choose the desired bit(s). Note: hover over each bit, there is a short description about the selected bit. If a STR 350/351 is connected to a Xenta Server (Xenta 7XX), then the STR 350/351 can be added in the Xbuilder project similar to an IO module. Setup steps are shown below: In Network panel,  under “LON", right click and select “Add IO Module->STR35X". Right click on the STR35X model just added, and select "Configure". A configuration pop up window will be displayed.  Make any desired changes. Note: Neuron ID can be manually typed in the Xbuilder or get from service pin in the Workstation. If choose to service pin, need to create and commission a LNS network in Workstation. Save and download the project. Below is a table of each bit in nciOption1 and nciOption2 and its brief description. nciOption1: Bit 0, 1: Fan type 00: No fan (Default) 10: On/Off fan 01: 2 speed fan 11: 3 speed fan Bit 2: Fan auto state 0: Not allowed (Default) 1: Allowed Bit 3: Fan off state 0: Not allowed (Default) 1: Allowed Bit 4: Fan speed 1 0: Not allowed (Default) 1: Allowed (On/Off fan type needs to be activated) Bit 5: Fan speed 2 0: Not allowed (Default) 1: Allowed (2 speed fan type needs to be activated) Bit 6: Fan speed 3 0: Not allowed (Default) 1: Allowed (3 speed fan type needs to be activated) Bit 7, 8 ,9: Not used   Bit 10: Temperature presentation 0: °C (Default) 1: °F Bit 11: Temp. normally displayed 0: Setpoint temperature (Default) 1: Room temperature Bit 12: Setpoint temp. presentation 0: Absolute temperature (Default) 1: Offset temperature Bit 13: Bypass button usage 0: Bypass (Default) 1: On/Off Bit 14: Not used   Bit 15: Supported protocols 0: Standard LonTalk protocol only 1: Standard LonTalk protocol and TAC proprietary protocol (Default) nciOption2: Bit 0, 1: Sunblind - Switch 1 00: On/Off (Default) 10: Up/Down 01: On/Off/Up/Down 11: Not used Bit 2, 3: Sunblind - Switch 2 00: On/Off (Default) 10: Up/Down 01: On/Off/Up/Down 11: Not used Bit 4: Light - Switch 1 0: Disable (Default) 1: Enable Bit 5: Light - Switch 2 0: Disable (Default) 1: Enable Bit 6, 7, 8: Local sensor 000: None (Default) 100: CO 2 010: RH 001: Occupancy Bit 9: CO 2 /RH value 0: Hidden (Default) 1: Display Bit 10-15: Not used  

Issue Can the red crosses (that indicate that a signal is offline) in Vista or SmartStruxure Workstation/Webstation be disabled? Product Line EcoStruxure Building Operation, TAC Vista Environment SmartStruxure TGML Graphics (Workstation, Webstation) Vista TGML Graphics (Workstation 5.X, Webstation 5.X) Cause When a signal which is bound to an object in a TGML graphic is offline, this is indicated by a red cross when viewing the graphic in Vista or SmartStruxure Workstation or Webstation. Resolution This can easily be disabled in TGML by adding a script to the OnSignalChange event: function signal(evt){   evt.preventDefault(); }  Note, this script will only disable the red X when a point is offline. This does not address any issue that might cause points to be offline. A short video is available on this process, to review, please see SmartStruxure - Graphics - Removing Red Crosses.mp4.