Building Automation Knowledge Base

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 IDWorks 6.x (on a Remote Client) does not connect to the SQL with Windows 7 64 Bit. Product Line TAC INET Environment Datacard IDWorks 6.x Windows 7 64-bit I/NET 2.43 and above Cause You have to manually install a 32 Bit ODBC connection for this to work correctly. Resolution To resolve this issue, start the EXE file located at: C:\Windows\SYSWOW64\odbcad32.Exe. NOTE: This is NOT the ODBC that is in the Control Panel on the PC. Once you start the EXE file, set this new ODBC Connection up by following the steps that are listed in Setting up ID Works on a Remote Client PC.

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 Difference in Triggered time and Timestamp Product Line EcoStruxure Building Operation Environment SBO Alarm view Cause In alarm view there, there are two timefields: "triggered time" and "time stamp." Resolution The Timestamp is the time at which the most recent state change occurred to the alarm. It is when the AS or ES received/detected the state and logged the alarm. The Triggered time is the first occurrence of this alarm. It could be when the alarm was originally detected, before possibly going in/ out of alarm several times. It could also be the time stamp when detected by a field controller. Triggered Time Stamp behavior also clarifies a few things on when they are updated.

Issue There appears to be a low battery on the control board. How can the NiCAD Battery be tested on the controller to see if it needs to be changed? Product Line TAC INET Environment I/NET Seven Cause Possible low battery on control board. Resolution There are some checks you can make regarding the battery condition. The battery has a design life of 7 years and sometimes lasts much longer. With power applied to a controller for at least 72 hours, take a DMM and measure the DC voltage across the battery. It should be in the neighborhood of 4.2-4.3 vDC. Remove power from the controller board and take the same measurement again. The beginning voltage should still be between 4.1-4.3 vDC and should start slowly tapering off (a tenth of a volt over a period of minutes would be normal). When the battery voltage reaches 3.6 vDC this is the threshold at which the battery can sustain the RAM memory. Any voltage below this value will subject the RAM memory to loss of data (+ - a tenth or two). If the initial voltage with power applied to the controller is less than 4.0 vDC after 72 hours, the battery may need replacing. If the battery voltage drops rapidly after power is removed from the controller, the battery needs replacing. If the controller memory inexplicably gets lost (not counting power surges, brownouts, etc.) and a station restore is needed, the battery may need replacing. Normally the above-mentioned tests will show that the battery has lost its storage capacity. The TAC part number for the White NiCAD battery that is on most of the I/Net Controllers is 01-2100-545. These batteries can no longer be ordered through the Customer Care department. For further battery info please reference Replacement I/NET Controller NICAD Battery info.  

Issue BACnet bCX MSTP network loses communication when a b-Link is added or removed Product Line Andover Continuum Environment MSTP b3 bCX4040  b-Link Cause The bCX MSTP circuitry is slightly different to the b-Link  MSTP circuitry , thus under some circumstances, other faults on the MSTP network can cause communication to change, when the network is connected via a b-Link Resolution If an MSTP network is installed correctly, then it will operate correctly at all speeds up to 76.8k (assuming all devices operated up to this speed) If the MSTP network is not stable up to 76.8k, or adding or removing a b-Link causing a loss of communication, then it is likely there is some fault on the network. (adding or removing the end of line termination resistors, is also a useful fault finding option) The bCX MSTP components are slightly different to the b-Link MSTP components, thus under some circumstances, other faults on the MSTP network can cause communication to be lost, when the network is connected via a b-Link Example This has been seen when third party variable speed drives (VSDs) were connected to a bCX MSTP network (these unit had switchable termination resistors that by default were in circuit) The communication was ok at a low speed (19200) connected directly to a bCX, but when the network was put on the secondary side of a b-Link, the communication failed. Once the termination resistors were switched out of circuit, the communication via the b-Link was fine. In the example above the VSDs were by ABB Related: How to change the Baud Rate of a field bus (Infinet or Bacnet MSTP) when there is an Infilink or B-link on the network

Issue Using the keypad on the stat to set the comm address may result in duplicate Device Instance IDs on a BACnet network. Product Line Andover Continuum, EcoStruxure Building Operation Environment Viconics Cause Find New BACnet Device does not result in new Viconics stat added to the system. This is due to the default assignment ID scheme used by Viconics. It is resulting in a duplicate Device ID on the BACnet network. Resolution By default, the Device Instance ID (called the Device Node ID in Continuum) is generated using the first two digits of the model of the thermostat + the comm (MAC) address assigned to the stat. Example: For a VT7200C5000 thermostats with MAC address 115, the default Device Instance would be 72115. The problem is that when installing the same model stats on multiple MSTP networks on the same BACnet system, this scheme can easily result in duplicate Device Instance IDs. The resolution is to change the duplicates or use a scheme to assign unique IDs manually to all the stats on a system. Any number between 1 and 4194303 (between 1 and 3FFFFF in Hex) is accepted by the thermostat. One scheme would be to use the BACnet Network ID and append the MAC address to it. Since each BACnet Network ID must be unique across the entire system, and the MAC address on each BACnet Network must be unique, this assures the combination is unique across the system. For example, if you have a bCX with an MSTP bus on comm2 that has a BACnet Network ID - Comm2 of 2765 and a stat with a MAC address of 9, assign it the Device Instance ID 2765009. A BACnet Explorer that provides write access to the Device Instance ID is required to change the default Device Instance ID. See Changing the BACnet device instance of the SE7000 series room controllers for a link to the Viconics VT7000 BACnet Configurator utility. For additional support on the above utility contact Viconics Support at 1-800-563-5660.

Issue The discontinuation of the SVT controller due to component obsolescence. Product Line Field Devices Environment SVT Optimiser 4201 4251 Cause What replacements are available for the SVT 4201 / 4251 controllers? Resolution Important Note - The replacement controller mentioned in this article is no longer available, and therefore a replacement for the SVT 4201 / 4251 is not available. The SVT controller range has been discontinued due to component obsolescence. The SVT controller was a basic optimiser that performed the start calculation using only an internal temperature sensor. There are no exact replacements for this controller available. What is available? The Schneider Electric DC1400 Optimiser / Compensator is the recommended replacement, but this is not a direct replacement. Differences in the controllers. The SVT controller provides only an optimum start, the DC1400 provides optimum start and stop. The SVT controller uses only a room temperature sensor for the start calculation, the DC1400 uses only a room temperature sensor and an outside temperature sensor for the start/stop calculations. The SVT controller has a dedicated "Boost" relay, which allows overriding of a CSC compensator, and control valve. This is an internal function with the DC1400 optimiser/compensator. The DC1400 has many other built in functions.   Controller wiring - Modifications will be required. SVT general wiring connections. Relay R1 is the main plant relay and relay R2 is the boost relay. To see the full controller details, please click SVT Optimiser DS2001 0210.pdf DC1400 general wiring details.   To see the full controller details, please click DC1400 DS2044A.pdf Controller Sensors As already indicated, the SVT controller uses only a space temperature detector, and this sensor is NOT suitable to use with the DC1400. The DC1400 controller will, as a minimum, require a room temperature sensor and an outside temperature sensor, meaning that extra wiring for the outside temperature sensor, and the sensor itself, will need to be installed. For details on suitable sensors, please refer to What sensors does the DC1400 optimiser/compensator require?

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 Right clicking the controller and selecting "Distribute Personnel" results in NO distribution There is no error Product Line Andover Continuum Environment CyberStation Cause Corrupted Personnel Distribution table in SQL ContinuumDB Resolution Truncate table PersonnelDistribution and re-populate it, then distribute personnel once again. WARNING: Unless knowing exactly what you are doing, deleting entries from your database can cause irreversible harm to your database and can potential cause corruption. Make sure to perform a full SQL Database backup before attempting to make any changes to the database. (See Move / Backup / Restore a database on a Single User SQL2005 Express system for details on how to backup your database and if not already installed, where to get Management Studio from) Make a backup of the Continuum database as a precaution. Close ALL CyberStation workstations. In SQL Management Studio execute the following query. truncate table PersonnelDistribution Once the table is truncated it must be re-populated by one of the following methods... If the total number of personnel objects is reasonably small (in the hundreds) launch Continuum and bring a list view of all the personnel objects, select all then right click and perform a 'Send to controller' OR In SQL Management Studio Invoke the stored SQL procedure that initializes the PersonnelDistribution table using the query dt_DIST_Init_Personnel_Dist_Table IMPORTANT: Truncating the PersonnelDistribution table will remove all pending personnel distribution including personnel deletions; controllers could potentially continue to allow access to doors for the deleted personnel until reloaded. Conversely, removing a pending personnel distribution could potentially cause a person to be denied access at a door until a distribution is performed to the controller.

Issue What are the bCX and b3 COV subscription limits? Product Line Andover Continuum Environment CyberStation bCX4040 bCX4920 b3 devices Cause Confusion on the limits for COV subscription in the Continuum BACnet devices. Resolution The b3 controllers are restricted to 32 devices, which means they can simultaneously establish  COV CLIENTsubscriptions with up to 32 different devices (Andover Continuum or third-party). The bCX1 and the b4920 permit COV CLIENT relationships with up to 255 devices. These limits are device limits and NOT point limits, so if a bCX has established COV subscriptions with 500 points on device X, it can still set up multiple COV subscriptions with up to 254 other BACnet devices. IMPORTANT- See Limit of how many devices a Bacnet controller can know about (Known devices). This limit does not apply to the number of other controllers which a COV exporter can deliver COV data to as a COV SERVER. For instance if a particular controller had a global point like OAT that 50 other controllers wanted and subscribed to this particular controller for that COV, this is allowed because each COV subscription has within it the target controller's address information and does not use the known device limit. There are two cautions that must be stated regarding this example however. Refer to What are the differences between Standard Continuum Import/Export and Continuum BACnet COV?. Each COV subscription in an exporting controller takes away user memory. Each subscription uses approximately 56 Bytes of user memory. So the limit of how many other devices can subscribe COV's in an individual controller is limited by free memory in the exporting controller.

Issue Need to bring Continuum system into SmartStruxure. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation v1.3, Continuum v1.94 system with BACnet bCX and b3 devices Cause b3 devices under the bCX become BACnet devices as if they were 3rd party BACnet devices. Resolution Test Environment: Cyberstation 1.94, SmartStruxure 1.3 Released, (1) AS-B, (2) bCX4040, one bCX hosting (2) B3 devices. Do BACnet discovery from SmartStruxure. Both bCX's and the b3 devices can be seen From the Hardware\BACnet devices folder, multi-select both bCXs and drag them into the BACnet Interface\IP Network. Upload their BACnet objects to SmartStruxure. From the Hardware\BACnet devices folder, multi-select both B3 controllers and copy/paste them into the BACnet Interface\IP Network. The B3 devices are hosted as, and look like, generic BACnet devices. Once the two B3s have been copied to the IP Network, an upload to SmartStruxure can be done. BACnet Digital Values and BACnet Analog Values on the b3 devices can be seen updating on a SmartStruxure listview. Note: Currently in SmartStruxure v1.3 there is no method to multi-select and host B3 Devices, within an MS/TP network. This functionality is part of the Continuum Migration project (a future version). Also check out the b3 VAV Quick Start Video on the Exchange.

Issue Does Port Based Network Access Control Ethernet 802.1x apply to Continuum controllers? Product Line Andover Continuum Environment Continuum Ethernet Controllers Cyberstation Cause A question that may be asked by Customers IT Departments Resolution No, the 802.1x protocol is not applicable to controllers, it is a Port based Network Access Control (PBNAC) that is used by Routers and computers. It is related to the Operating system user accounts and policies so is above and outside the scope of Continuum. Not all devices support 802.1X authentication. Examples include some network printers, Ethernet-based electronics like environmental sensors, cameras, and wireless phones. For those devices to be used in a protected network environment, alternative mechanisms must be provided to authenticate them. One option would be to disable 802.1X on that port, but that leaves that port unprotected and open for abuse. Another, slightly more reliable option is to use the MAB option. When MAB is configured on a port, that port will first try to check if the connected device is 802.1X compliant, and if no reaction is received from the connected device, it will try to authenticate with the AAA server using the connected device's MAC address as username and password. The network administrator then must make provisions on the RADIUS server to authenticate those MAC-addresses, either by adding them as regular users, or implementing additional logic to resolve them in a network inventory database. Many managed Ethernet switches offer options for this. Network Security is an available option add on for IP level controllers. Please refer to IPSEC and Network Security on Controllers for more information. Another potential option would be to secure the controllers on a separate VLAN.

Issue Muster Report triggered to generate and print Product Line Andover Continuum Environment Muster Reports on a Continuum site Cause With Muster Report loaded, can you trigger from a input (example: fire alarm) for a report to be generated and automatically print? Resolution With some workstation PE programming, you can launch the Muster Report to automatically print. You will need to install and configure the "Plain English Alarm Function" available from Can Plain English interact with the Continuum Alarm Engine? This will trigger a workstation Function each time an alarm is received. You will write PE code to detect the specific alarm and/or point, then "Shell" to launch the Muster Report. Please find the attached Muster Report User Guide and .dmp file which is renamed as .txt file which should be useful.

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.