Building Automation Knowledge Base

Issue Managing the address table in a Lonworks device Product Line EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment I/A Series MNL TAC Xenta Third-party LON devices Building Operation Automation Server Cause A LonWorks device contains an Address Table which will hold a maximum of 15 addresses. Once this table is full, all bindings will only be able to use the broadcast setting which is not desirable. A Xenta 200,300 or 400 controller will have its first 2 address tables used with TAG 0 and TAG 1 binding. This leaves only 13 addresses for user bindings not the 15 addresses like other LonWorks devices. Resolution ​When you create a binding in LonWorks, you decide its behavior by selecting a binding profile. You either select a binding profile, or you use the default profile. There are basically three types of binding profiles: Acknowledged profiles Unacknowledged profiles Broadcast profiles Using an Acknowledged profile will consume one of the 15 available address table addresses on both the sending and the receiving device. The Unacknowledged profiles will only use one Address on the sending device's address table. Broadcast binds do not use an address but are not recommended. Use an acknowledged binding profile when the sending device should receive an acknowledgment from the receiving device indicating that the value of the bound variable was successfully sent. Binding profile Transmit timer Retry count Acknowledged Profile 96 ms 3 Acknowledged, Tx tmr 256, 3 retries 256 ms 3 Acknowledged, Tx tmr 256, 5 retries 256 ms 5 Acknowledged, Tx tmr 1024, 5 retries 1024 ms 5 Be careful of creating large, acknowledged fan-out bindings because they generate a lot of traffic, especially if the device of one of the recipients is offline.  Use an unacknowledged binding profile when the sending device should not receive an acknowledgment from the receiving device. Use this type when the value being sent is not critical and is of low importance to the control logic. Binding profile Repeat timer Repeat count Unacknowledged Profile   0 Unacknowledged Repeated Profile 48 ms 3 Unacknowledged Repeated, 5 repeats 48 ms 5 Use a broadcast profile when you do not want to use up an entry in the address table. The device address table has 15 available entries for bindings but the first entry is a reserved broadcast entry that all broadcast bindings can share. Binding profile Repeat timer Repeat count Broadcast Profile   0 Broadcast Profile, 5 repeats 48 ms 5 If no binding profile is selected, a default profile is used: Point-to-point bindings use the Acknowledged profile as default. Fan-out bindings use the Unacknowledged Repeated profile as default. Building Operation uses the broadcast profile as default when the device address table has run out of entries. If a point-to-point binding is changed to a fan-out binding, the binding profile is automatically updated to an Unacknowledged Repeated profile. If a fan-out binding is changed to a point-to-point binding, the binding profile is automatically updated to an Acknowledged profile.  This and other information about lon bindings is available on the online help guide Using a Lon Binding in StruxureWare Building Operation More information on the different tables used by each LON device

Issue An error occurred while installing DSS: MSDTC 2 Product Line TAC Vista Environment DSS Installation MSDTC Cause Users that get the following error message when installing Vista ‘Error occurred when installing DSS’ can be caused by the MSDTC (Distributed Transaction Coordinator) not being able to start. In the service list Distributed Transaction Coordinator (MSDTC) is not started and it fails when you try to start it. Resolution Check the windows event log. If you see the following error events logged in the Application log:  Event Type: Error Event Source: MSDTC Event Category: LOG Event ID: 4163 Description: MS DTC log file not found. After ensuring that all Resource Managers coordinated by MS DTC have no indoubt transactions, please run msdtc -resetlog to create the log file. Event Type: Error Event Source: MSDTC Event Category: TM Event ID: 4185 Description: MS DTC Transaction Manager start failed. LogInit returned error 0x5. Follow the steps in http://support.microsoft.com/kb/916926 to fix the problem. For other possible causes for this problem see: An error occurred while installing DSS: MSDTC An error occurred while installing DSS: The account already exists An error occurred while installing DSS:COM+ installation corrupt An error occurred while installing DSS: Cannot Start Service

Issue "No license for LonWorks communication" - LonMaker Recovery Folder Product Line TAC Vista Environment Echelon LonMaker Cause Vista software detects the installation of commissioning tool for the LonWorks communication license. At times LonMaker will improperly shut down and store bad data in the Lm\Db\Database name\recovery folder. This invalid data will stop the LNS server from running properly. Resolution If using LonMaker and "No License for LonWorks Communication" error message appears: Shut down Vista software Open the drawing in LonMaker If it requests the contents of the recovery folder be removed, follow those instructions. Once the contents of the recovery folder are removed, open the drawing in LonMaker Launch Vista Server, and the license problem should be gone.  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" error message in Classic Network "No license for LonWorks communication" Error in Windows 2008 Server X64 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue After the TAC Menta file has been downloaded all other IO modules operated normally but one IO module will not come online Product Line TAC Vista Environment Xenta401 XENTA301 XENTA281 Cause If the IO module that will not come online has IO points set up in it, then chances are one of the points is set up incorrectly. For example, it may be referencing a Universal Input, but in an Analog Output only IO controller. This is typically caused by changing the IO module from its original type. The TAC Menta was not updated correctly after the change and an analog input was left referencing an analog output in the new controller. Resolution Check all the points in the affected controller for correct and valid references. Once corrected download the controller. TAC Xenta I/O modules do not come online after a download from System Plug-In is a related article.

Issue "No license for LonWorks communication" error when using a non LE dongle. Product Line TAC Vista Environment Non LE dongle (LE= Limited Edition which has no Webstation or multiserver functionality) Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause One would normally expect this error message when trying to run Webstation server with a Vista LE license. If the system is not using a Vista LE dongle/license, but the error "No license for LonWorks communication" appears, then the problem may be in the Privilege Server service.   Resolution Shut down Vista Server and Workstation. Right click on My Computer and select Manage. Expand Services and Applications. Click on Services. Find the service Privilege Win32 Server. Right click on the service and select Stop. Right click on the service once more and select Start. Restart Vista Server and Workstation and verify that the error went away. Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "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 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue Key information necessary to operate and install Vista OPC Server Product Line TAC Vista Environment Vista Server 5.1.x Vista OPC Server 1.6.1 Cause Following these guidelines and work arounds the proper installation and configuration of TAC Vista OPC Server can be achieved. Resolution Please reference the articles below depending on the situation.  After installing TAC Vista OPC server it does not show up as a Windows service: Proper license is required before installation OPC server for TAC Vista will not keep the login settings in the TAC Vista OPC Server setup: Login Settings require additional steps Installing and configuring Vista OPC Server: Step by Step installation and configuration steps Unable to access data on a Vista OPC Server that reside on Xenta Server (I/NET or 3rd Party protocols): Server address limitations

Issue Error states: "Ensure that Vista Server is started" when trying to log into TAC Vista Workstation. The server is started. Product Line TAC Vista Environment TAC Vista Workstation 4.2.5, 4.3.0-4.5.0, 5.0.0 and higher Microsoft Windows XP Service Pack 2 Cause Microsoft Windows XP Service Pack 2 has security changes/upgrades from previous service packs.  This affects the DCOM permissions that Vista Server relies on. a variety of other reason could result in an error in DCOM parameters in later operating systems. Resolution Vista 4.2.5 Apply settings described in this TPI to get TAC Vista to work properly. Vista 4.3.0-4.5.0 Apply settings described in this TPI to get TAC Vista to work properly. Vista 5.0.0 and higher Apply settings described in TAC Software Installation Manual available on The Exchange Download Center. This can be done using the DCOM Utility in Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET. Error Message: Ensure that Vista Server is started lists manual steps to access DCOM.

Issue After successfully downloading a Menta application directly through the serial connection, the pop-up window below is displayed:  tam32 No blueprint in TAC Xenta! Don't forget to download the network configuration if the TAC Xenta is to function in a network! Product Line TAC Vista Environment Directly connected Menta Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause The blueprint is also called an .NDB (network database) file.  It contains network information that allows the controller to communicate to other controllers or I/O modules.  When downloading a Menta application directly, this warning is displayed as a reminder that that necessary network information has not been included in the application-only download. Resolution If the controller is running stand-alone and no networked communication is required, then no further action is required.  The message is only a warning alerting the user to the fact that the NDB file has not been included in the download. If the controller needs network variables and I/O module communication, follow the direct download (most often done only for troubleshooting purposes) with a download from the front end Vista Workstation for classic networks Vista System Plug-In for LNS networks If no front end exists, but network communication is still required (most often for I/O modules), lonTool32 is a suitable work around for those rare instances.  See Using lontool32 to download a stand-alone controller.

Issue "No license for LonWorks communication" with TAC Vista Server LE Product Line TAC Vista Environment TAC Vista Server LE (LE= Limited Edition which has no Webstation or multiserver functionality) Cause If TAC Vista Webstation is installed on a TAC Vista Server LE machine, Lon communications will not work correctly. It will work for 10 minutes then an alarm message appears, "No license for LonWorks communication," and all communication with the Lon network will stop. Resolution Uninstall Webstation Related Articles: "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 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue How to order more NL credits in order to commission more devices. If the following message displays when opening a NL220 database, then more credits will need to be purchased soon. " BEWARE: less than 20 credits are available on this machine. If you need to install more than 20 device please order the amount of needed credits as soon as possible. Do you want to ask for new credits?" Product Line TAC IA Series, TAC Vista Environment NL220 LNS Cause There are two types of credits: Product specific credits like LonMaker and NL credits LNS credits   Echelon 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. Echelon 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. Newron 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 Echelon LonMaker credits see Ordering more Echelon LonMaker credits. Resolution When working in NL220, it is wise to maintain a higher level of LNS credits than NL credits to help avoid locking out the LNS server license. To check the amount of NL credits remaining go to Start > All Programs > NL Suite > NLCreditsGenerator and look for Remaining NLCredits. The number of NL credits remaining can also be found at the bottom of the NL220 LonWorks Manager window with a project open. To check the amount of LNS credits remaining on a PC go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard and look for Credits Available. The number of LNS credits remaining can also be found at the bottom of the NL220 LonWorks Manager window with a project open.   To order more NL220 credits: Open the NLCreditsGenerator Utility that is installed with NL220. Go to Start > All Programs > NL Suite > NLCreditsGenerator > NLCreditsGenerator Utility. Enter the number of NL220 credits to be added  in the request area. Click Next. Click "Yes, this PC will be used for commissioning" Enter your name and contact details. Select "Copy to clipboard". Then either paste the information into notepad or in an email. Send the NL credit request to your local Schneider Electric Buildings Business order department  (NLCredits@buildings.schneider-electric.com). When you order has been processed by the local Schneider Electric Buildings Business order department you will receive an upgrade key. Open the NLCreditsGenerator Utility again. Go to Start > All Programs > NL Suite > NLCreditsGenerator > NLCreditsGenerator Utility. Click the Next button. Enter the key into the "Upgrade key" field of the credits generator. A message indicating you credits were added is then displayed.   Note: Once the request key has been generated, DO NOT commission or decommission any devices with the dongle until the upgrade key has been applied to the dongle. If devices are commissioned before then, the upgrade key will no longer be valid.

Issue How to get the XIF file of Xenta free programmable controllers? Product Line TAC Vista Environment Xenta Free programmable controllers (Xenta 281, Xenta 282, Xenta 283, Xenta 301, Xenta 302,  Xenta 301C, Xenta 302C, Xenta 401, Xenta 401B, Xenta 401C) TAC Menta editor Cause If Xenta free programmable controllers need to play as a third party device in another system, a XIF file is needed. Resolution Open the preprogrammed Menta file in the Menta Editor.  Note: If you are opening the file directly from the Vista database, it will first need to be saved to the local harddrive before generating an XIF. Go to Options > Simulate (or press F12) Go to Commands > Generate An XIF file with the same name as the .MTA file will be generated in the same location on the harddrive as the. MTA.   Alternatively, if you are connected live to the controller, you can also generate an XIF by connecting live: Open the preprogrammed Menta file in the Menta Editor. Connect the Xenta free programmable controller to the computer with a RS232 to USB cable. For details please refer to Downloading a Xenta Device Using Direct Connection to Menta Programming Tool. Go to Options->Simulate (F12), and select connect. A XIF file will automatically generated under the same folder that the Menta file is saved. NOTE: in order for third party system to be able to view points in Menta, those points need to be set as SNVTs.

Issue Xenta programmable controllers can communicate to each other using TAC Network Variables (TANV). These are defined in the Menta programming and travel on Xenta Group Bindings in the LNS environment. If data is failing to update in the receiving controller, there are a few troubleshooting techniques that can help. Product Line TAC Vista Environment Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta LonMaker/NL220 Cause TAC Network Variable communication can be compromised for four reasons: Network path not defined correctly in the Menta file Network path name is too long Group Bindings not done correctly in LonMaker/NL220 Controller's network output capacity has been exceeded Resolution Verify the Network Path If the network variable has been populated by browsing Menta files on the hard drive, or was entered manually, it can be the cause of the problem. Even visual inspection of the network path is not 100% reliable -- a lowercase "l" and an uppercase "I" appear the same, for example. The only way to be certain the path is correct is to browse it in through the Vista database. Open the Menta file from the Vista database. Right-click on the receiving controller and select Edit. Editing a Menta file directly from the hard drive of a computer does not give you the same network browsing options and can lead to incorrectly mapped network variables. Double click the network variable AI block and go to the Bind dialogue. Next to the Network Address text field is a browse button ("..."). Click it to open the network browse window. This tree structure should be the same as the folder view in Vista Workstation. Navigate to the sending controller's public signal and click okay. Download the application to the controller. Verify that the Network Path Name is not too long If the network variable path name, or the Network Address, is too long then this will cause a problem.The network variable path name, if the point is in a module, looks like ControllerName\ModuleName\PointName. If it is not in a module then it will have the Program Specification name instead of a module name. So it would look like ControllerName\ProgramSpecificationName\PointName.  If the ModuleName\PointName or ProgramSpecificationName\PointName part of the path is longer than 33 characters, counting the "\", then it will not work. Verify Group Bindings are correct Refer to Verifying Xenta Group Bindings in an LNS system for the procedure on verifying group bindings. If the group bindings are not correct, redo group bindings and download the sending and receiving controllers. Calculate the total output of the controller Depending on the controller type, there are different limits on the network variable outputs.  This includes both SNVTs and TANVs.  If together, they exceed the capacity, there will be spotty updates and random signals that don't make it to the receiving controller.  Unfortunately, there is no easy way to count the TANVs. In the Menta file of the sending controller, go to Options > Memory Usage... > Advanced... Make note of the TACNV/SNVT Out Free number.  Each SNVT output defined in the Menta file consumes one of these outputs and decreases the number of Free signals available for use with a TANV. The only way to count the number of network variable outputs is to know each receiving controller that is pointing back to the sending controller with a TANV.  Unlike with SNVTs, EACH signal in EACH receiving controller consumes one of these available outputs.  If the output limit has been exceeded, the communication will suffer. Reduce the number of network variables coming from one controller by "cascading" signals.

Issue Using STR-350 Bypass button as On/Off button in LNS Network Product Line TAC Vista Environment Vista STR-350 STR-351 Cause The Bypass button will only toggle the output of the nvoOccManCmd if the input nviEffectOccup matches the current button value. Resolution The STR-350/351 Sensors allow you to configure the Bypass button as an ON/OFF button but if it is not setup correctly it can get stuck in a single position. If using an application specific controller, the effective occupancy of the controller should be routed back to the STR-350 and bound to the nviEffectOccup. If using a 3rd party controller that does not have a SNVT for the effective occupancy, follow the step below. If using a programmable Xenta controller the nvoOccManCmd coming from the STR-350 should be bound to the programmable controller that with some logic programmed to follow the toggle of the button. Then that signal should be sent back to the nviEffectOccup of the STR-350. For the application used in the Classic network, refer to the Using STR-350 Bypass button as On/Off button in Classic Network.

Issue After updating Java, webstation doesn't show graphics. The window is blank/white. If the error you get is "Error. Click for details" and not a blank window, please refer to Webstation graphics not working after Java updated to Java 7 update 51. Product Line EcoStruxure Building Operation, TAC Vista Environment Java Webstation Cause There's an issue with Java and Webstation in SmartStruxure 1.5 when using panels. There's a hotfix available (1.5.0.2307) correcting this issue. Either Contact Product Support for this hotfix or download it on The Exchange Download Center. If panels are not used or the SmartStruxure version is lower than 1.5 or you are working with another product line such as TAC Vista, this article might help. This issue is usually only seen when updating an existing Java installation. If no version of Java has been installed previously, the issues doesn't seem to appear. According to Sun, there's an issue with the deployment.properties file. Read this article for further information. Resolution First try to install the newest version of Java. Version 1.7u67 has just been released, and is supposed to solve the issue. If you are using a x64 operating system, make sure you install both the x86 and the x64 version of Java in order to support both 32 bit and 64 bit browsers installed. If that doesn't work, try the procedure below. 1: Make sure all browsers are closed 2: Uninstall all Java versions 3: Make a copy of the file C:\Users\%username%\AppData\LocalLow\Sun\Java\Deployment\security\exception.sites (replace user_name with the profile name of the user logged into Windows) 4: Delete the folder C:\Users\%username%\AppData\LocalLow\Sun (replace user_name with the profile name of the user logged into Windows) 5: Install the latest version of Java (https://java.com/en/download/manual.jsp) - if you are using a x64 operating system, make sure you install both the x86 and the x64 version 6: Verify that you have the latest Java version and that you don't have older versions using the Java uninstall applet: https://java.com/en/download/uninstallapplet.jsp 7: Move the exception.sites file back into C:\Users\user_name\AppData\LocalLow\Sun\Java\Deployment\security (replace user_name with the profile name of the user logged into Windows) - if the directory doesn't exist, make the directories missing to complete the path 8: Try viewing TGML graphics again

Issue When a XIF file contains NCI's (SCPT's and UCPT's) default values (NVVAL) must be described in the XIF file. In some cases if NCI's are present, but some or all NVVAL initializers are missing commissioning the device will fail. For information regarding NCI's that are part of a FILE definition, please refer to Understanding the FILE part of a XIF file. Product Line EcoStruxure Building Operation, TAC Vista Environment LonWorks XIF Cause When commissioning a device default values to configuration variables must be assigned. If the tool (TAC Vista, SmartStruxure, LonMaker, NL220) does not know what default value to assign, it can cause an error. Resolution Make sure all NCI's have proper initializers defined. Read XIF file - NVVAL initializers.pdf guide as reference. Here is an example of a NVVAL section: VAR nciHrtBtRcv 2 0 0 0 0 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,0\x80,48; 107 * 1 4 0 2 0 0 VAR nciHrtBtSnd 3 0 0 0 0 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,0\x80,49; 107 * 1 4 0 2 0 0 VAR nciLocation 4 0 0 0 1 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,0\x80,17; 36 * 1 4 0 31 0 0 VAR nciDeviceName 5 0 0 0 0 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,6\x80,3; 36 * 1 4 0 31 0 0 NVVAL #VAR nciHrtBtRcv \x00,\x00 #VAR nciHrtBtSnd \x00,\x00 #VAR nciLocation = empty string \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00, \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00 #VAR nciDeviceName = empty string \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00, \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00

Issue After successfully logged into Xenta Server web pages, java loading icon will be displayed as shown below. However, after a while it will automatically log the user out as shown below. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers 5.1.6 (Xenta 511, Xenta 515, Xenta 527, Xenta 701, Xenta 711, Xenta 721, Xenta 731, Xenta 913) Java 1.6 update 29 Note: This behavior may happen on other Xenta Server versions with different Java versions. Please refer to the Cause section for the reason. Cause Vista may not support the newest Java versions. For Vista 5.1.6, the recommended Java version is Java 1.6 update 20. Please refer to Recommended Java version for TAC Vista 5 for recommended Java version details. Resolution Go to Start > Settings > Control Panel > Add or Remove Programs. Find Java application (in this example is Java(TM) 6 Update 29), and select “Remove”. Reload the Xenta Server webpage, will find the Java icon will not be displayed this time. Instead, “Download Java” request link will be displayed. Click on the link and download the supported version of Java. The issue should be solved after the recommended version of Java is installed.

Issue What version of Microsoft.Net Framework and ASP.NET is used by Webstation 5.1.9? Product Line TAC Vista Environment Vista Webstation 5.1.9 Cause ASP.NET is a web application framework developed and marketed by Microsoft to allow programmers to build dynamic web sites, web applications and web services. TAC Vista Webstation is developed using ASP.NET, which is a part of the Microsoft.Net Framework. Resolution TAC Vista Webstation uses Microsoft.Net Framework 4 and ASP.NET 4. For details on additional Vista versions and the .NET framework and ASP.NET versions required please consult the compatibility matrix in the Supported version of .NET framework and ASP.NET for Vista software.

Issue Verifying the Com Port on a PC is working properly by using "Loopback" test in Terminal Emulator. Product Line Andover Continuum, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Hyperterminal RS-232 serial port Cause The following test writes to the serial port and reads from the same port. This will verify the Full duplex operation of the RS-232 communication. Resolution Short the TX and RX pins of the cable (pins 2 and 3) following the pinouts below. Gender is determined by pin type.                Male DB9 (Left) and Female DB9 (right)   Launch Hyperterminal by selecting Start>>Programs>>Accessories>>Hyperterminal. If you do not have Hyperterminal, please read Hyperterminal on Microsoft Windows Operating Systems. If you are asked if you would like to install a modem, select No. Choose any icon and name the session, select "OK". In the next Pop-Up menu, choose direct to COMx (where x is the number of the COM Port you are testing.) Set the flow control setting to None. Leave the other settings to default settings, select "OK" Select File » Properties from the menu bar, select the Settings tab, and then push the ASCII Setup button. Check the option for Echo typed characters locally. Type something. If you see double characters the serial port is setup correctly and is functional. The display is showing characters that are sent out and what is read in. The Emulator will send and display the TX and immediately read and display  RX. If you see exactly what you are typing, you have a communication issue. which could be: Bad Com Port Bad cables Pins not shorted correctly If you are out of physical ports to try, use a USB Serial Port converter. If you are using a USB, use Reassigning a USB Serial Adaptor to a desired COM port for instructions of assigning Com to another port.

Issue Knowing the procedure to follow when hosting a site license for the first time with Vista. Product Line TAC Vista Environment Vista Licensing Cause The TAC licensing website is divided up into different areas depending on the task to be performed. An account must be created the first time using the site before creating a license file from the entitlement ID. Resolution Note: In order to rehost an existing Vista license file, see Rehosting a Vista 5 License on the FlexNet License Server. Log onto https://schneider-electric.flexnetoperations.com/flexnet/. Click on the link that says "New User?".   Fill out the entire page with your information. Insert the Entitlement ID that was purchased in the space titled "Activation ID". Once everything has been filled out, click Complete.   This will log you into the Start Page of the licensing site. A temporary password will be emailed to the address you provided on the New User page. This temporary password is required to set your new password which can be done by clicking on Profile in the top right corner of the screen.   Enter the temporary password into the "Old Password" field. Then enter your new password into the "New Password" and "Confirm Password" fields. Click Save.   On the left side of the Start Page, click "Activate" underneath Manage Entitlements.   Check the entitlement ID that you want to use and click Activate.  Fill out all of the information on this page. Click Next.   Click on "Add New Host" at the top of the Server Hosts panel. Select MAC address or Hardware dongle as the Server Hosts. Type in the MAC address of the computer or the dongle ID of the hardware dongle that the license file will be associated too and click OK. In order to find out the MAC address of your computer, reference How to locate a computer's MAC address.   Check the box next to the host name that was just added. Click Next.   Enter the number of licenses you would like to activate in the "Fulfill Count" box and click Verify. The file should verify successfully. Click Next.   Review all of the information. Click Generate.   Select the box next to the newly created license file. Either select to "Save to File" (save a copy of the license file to the local PC) or "Email License" (email the license file to a desired address). Click Complete.  

Issue The TAC Xenta group master is online but not the other Xenta devices in the group. Product Line TAC Vista Environment TAC Vista 5.1.x Classic network Menta 5.1.x Cause The TAC Xenta Group Master is a TAC Xenta 301/302/401/901 (in the TAC Xenta Group) that monitors the on-line and off-line status of the TAC Group and its members. The Group Master forwards the on-line and off-line information to TAC Vista. If devices have been added it's possible that  the current group isn't updated. Resolution The entire Xenta group must know it has a new device for proper communication to occur. To accomplish this download the applications and parameters to the entire group.  If the Group master goes offline, the whole group will be considered off-line by TAC Vista. The separate on-line group members, however, can send alarms and other information directly to TAC Vista as usual. Information about resolving this issue with an LNS network can be found in Xenta Programmable Device is Offline in Vista but Online in LonMaker.