Issue "Couldn't parse: Illegal type:1 cannot be enum" Java error when opening a values page in an Xenta Server Environment Xenta 511 Xenta 527 Xenta 555 Xenta 913 Xenta 711 Xenta 731 Cause Underscores ( _ ) are not permitted characters in the enumeration names within the Xbuilder project. Resolution Remove the _ (underscores) from the enumeration names and redownload the project.

Issue When you attempt to create SNVT binding you the following error. The message output pane shows the following text. Environment NL220 Cause The SNVTs setup in Menta has not had the correct send or poll option set. Resolution Select the send option on the Digital/Analog output setup as a NVO SNVT from the Menta application   This will allow the change of value connection which will assist with network traffic bandwidth. If you set poll in the option on the Digital/Analog input the NVI will poll the output at the specified time set in the input regardless of a change in value. When you generate the modified Menta file the program ID will be changed so an update of NL220 and the Xenta controller is required. To do this save the modified Menta file to the hard drive, browse the updated Menta file from the configure option on the Xenta controller in the system plugin. Then update Vista and download the controller.

Issue Is it possible to see a list of all the signals in the vista system that are overridden manually? Environment Vista 5.1.X Cause It is important for the customer to know which signals are manually overridden to be able to make appropriate decisions about a plants' status. Resolution There are 2 main options available: 1. Use Vista's search tool -the screen shot below shows which criteria to use. You can of course include other points in the filter. 2. Create a report and link to the signal's 'manual control' property. This option would have the advantage of being able to trigger the report via a button in TGML and that the layout can be configured according to the customer's specifications. However, it will take a bit longer to configure the report initially. -Open the report and via the Vista reports addin configure a vista link to a value as shown below.  

Issue Clarification regarding Vista's OPC server and OPC client functionality. Incorrect configuration can cause unexpected results and crash the system. Product Line TAC Vista Environment Vista Server Vista OPC Server Cause There is some confusion as to the usage of the OPC server object in TAC Vista workstation. Resolution TAC Vista OPC Server TAC Vista OPC Server is an add-on module to TAC Vista Server, which enables third party OPC-compliant presentation systems to interface with TAC products. All objects and signals in the TAC Vista Server database can be read and changed via the OPC Data Access interface. Vista OPC Server is implemented as a Windows service and can be started from the Computer Management console.  A license is required, but no configuration is necessary in workstation TAC Vista OPC Client The TAC Vista database has to be programmed and configured as an OPC client, using the TAC Vista OPCTool. Simply browse the available OPC servers, select the objects to be added to TAC Vista and then from the tools menu select "Create/update TAC Vista objects...". When the dialogue opens up, browse to the appropriate location and select the OPC server object to be updated. If this is a new OPC client, right-click in the dialogue and select New->Device-OPC server. The object's properties will then be set by OPC tool after clicking on the select button. !!Do not create an OPC server object in Vista and set the program ID to TACOS.OPCServices.DA.1 and the Class ID to {7EA83597-0B54-4BAF-9EE5-D30AA9EB4D6D}. This will create a loop in the system and cause unexpected behaviour. There should be no OPC server objects in Workstation if TAC Vista is the OPC server!! read and changed via the OPC Data Access interface. to interface with TAC products.

Issue It is possible to create a receiver group in XBuilder that can be edited by the customer through the web browser.  This will allow the customer to make changes without downloading a new project to the controller. Environment Xenta Server Xenta 511, 511:B, 527, 701, 711, 721 and 731 XBuilder Cause Edit receiver groups using your web browser Resolution It is possible to create a page that will allow your customer to view and edit the receiver group from the web page without using XBuilder.  Create the receiver group in the system pane of XBuilder Create a new Edit Alarm Page in the system pane of XBuilder Drag and drop the receiver group onto the new Edit Alarm Page Once this connection is made, the receiver group will be displayed on the Edit Alarm Page when the customer logs onto the controllers' website.

Issue There is no designated configuration setting to monitor fan run indication with a TAC Xenta 102-AX controller. Environment TAC Xenta 102-AX Plug-in Workstation Cause The Xenta 102-AX controller does not have a configuration option to monitor fan run indication. This can be achieved by using a universal input and converting the raw value to run indication. Resolution These configuration steps can also be done through Vista Workstation, just make note of the configuration point names and locations in parenthesis.   Setting Up Fan Run Indication on a Xenta 102-AX   Open up the TAC Xenta 102-AX Plug-in of the controller that will be monitoring fan run indication. Click on the Hardware Configuration tab. Any one of the universal inputs may be used to monitor fan run indication but Input 1 will be used in this example. Change Input 1 Selection to Universal Input (UnivIn1_Sense > UCPTselectUI). Click on the Status tab. Notice that the percent value of Universal Input #1 (nvoUnvInput1) is at 99.90%. This value may vary but when the fan is not running it will be near 100%. Override the space temperature so that the fan powered VAV box goes into heating (if using a parallel fan) or make sure the series fan is running. Notice that the value of Universal Input #1 dropped to 0.00%. Again this value may vary but it will be near 0.00%. This percent value is sent out of the Xenta 102-AX controller on nvoUnvInput1. In order to display this value in a binary state it will need to be converted using Menta or in a graphic page.  

Issue How to configure a TAC Xenta server in Lonmaker when also being used as the communication port in TAC Vista Environment TAC Vista Lonmaker TAC Xbuilder TAC System plug-in Cause Needs to use the Xenta Server as a lonworks device and the Network Interface in TAC Vista. Resolution Using Xenta Server 7xx and LonMaker   Create the Xbuilder project using “stand alone Xbuilder” Add the IO modules that the Xenta Server is using and assign neuron Ids Create the SNVTs for the Xenta Server. Send the project to target.   Create LonMaker and TAC Vista database Create you LonMaker database, register the necessary plug- ins. TAC System plug- in and TAC Device plug- in are used for the Xenta Server. Add the nodes on you Network including the Xenta Server but not the IO modules. You can use a generic template for the Xenta Server and browse in the XIF file. Open system plug-in. Right click on The Xenta server and select “Configure…”. Browse in the Xbuilder project. Click on the “add and mach IO”. Click ok. Go to TAC Network – Settings, Set the Vista communication port to the correct Xenta server type. Also select if you want the IO modules to be commissioned in LNS. Click Ok   Still in the system plug in right click on the Xenta Server and select “set as network interface”. Update TAC Network. Start the server and update TAC Vista Database form the system plug in. Create group bindings if you have any Xenta 401, 30x, 28x controllers. Close the system plug in. Resynchronize the drawing to database. Commission devices. Create bindings. Open TAC Vista workstation, right click and edit the Xenta server (This can also be done form the system plug in configure command). Send the project to target.

Issue How to transfer data from one device to another in Xbuilder? If it is possible to bind SNVT values in through Xenta Servers? Environment Xenta Servers (Xenta 511, Xenta 527, Xenta 701, Xenta 711, Xenta 721, Xenta 731, Xenta 913) Cause For some reason, if a user need to transfer data from one device to another under a Xenta Server (mostly, from third party devices to third party devices without using NL220 or LonMaker), “Connection Object” feature can be used to achieve this request. Resolution This example is showing how to transfer a room temperature value from an IO module under a Xenta 721 to a programmed SNVT input in a Xenta 301under the same Xenta 721. Other applications should be in a similar manner. Under “System” panel, right click on the folder site. (Default name is “The site name”) Expand the connection object by clicking on the “+” button on the top left. A “From” signal and a “To” signal will be displayed as shown below. Drag and drop the value from the IO module in the “Network” Panel (in this case, it is the U1 Value) on to the “From” signal as shown below. Find the SNVT variable created in the Xenta 301. In this example, go to LON->LWNetwork->XG->DDC->SNVT->LonMarkObjects->Node_Object_1->NetworkVariables->nvi_SpaceTemp. Then drag and drop this signal onto the “To” signal as shown below. NOTE: Do not choose the signals under “Public Signals” folder. Those signals are NOT writable. Download the project into Xenta server, the biding should start working by this point. NOTE: It is strongly recommended to use NL220 or LonMaker to do SNVT bindings for better and more stable performances. Large amount of connection object communications may cause Xenta servers to go offline frequently.

Issue Various webstation or TGML issues Environment StruxureWare Web Station Vista Web Station Cause Java script may be causing problems with Webstation.  Resolution   How to turn on Java Debugging: Open Control Panel Select Java Chose the advanced tab Expand Debugging and check all boxes Expand Java console and select Show console When future errors occur you can capture the errors from the java console If you do not wish to have the console pop up, you can change the Java console back to Hide console and access the logs at this location:  C:\Users\CURRENTUSER\AppData\LocalLow\Sun\Java\Deployment\log

Issue After an OGC graphic is upgraded to TGML, some images or components are no longer in the desired location on the page. Some images may shift location on the page depending on how TGML performs certain tasks during the conversion. Product Line TAC Vista Environment TGML Graphics Editor OGC Graphics Editor Vista Cause When an OGC graphic is converted to TGML, it is possible for the position of an image to be converted incorrectly. The x,y axis of an image in OGC is relative to the origin on the page (The uppermost top, left corner on the page being 0,0). However, if you have used the Symbols feature in OGC, TGML may group this symbol as a during the conversion. This places the 0,0 axis position at the uppermost top, left corner of the component and not the page. This creates unwanted separation as the x.y position relative to the component moves the image to an undesired location on the graphics page. Resolution Open the new TGML file in the graphics editor Locate the component that has been moved in the object tree Change the top and left position to 0,0 on all s associated with that component. TGML may have created several groups for one OGC symbol and the image under each group will need to change. NOTE: It may be possible to use the find/replace function in the source code to replace all of the unwanted positions at once. You will need to be careful that this number is not being used anywhere else in your code before you save these changes. You may remove necessary code if this number has multiple functions.

Issue Values sent from a Xenta 121 FC/HP controller via SNVT bindings are not making it to the receiving controller. Viewing the outbound SNVT on the Xenta 121 shows a value, but the inbound SNVT on the receiving controller is invalid or a default value. Product Line TAC Vista Environment  Vista NL220 LonMaker ZBuilder Cause The Node Configuration parameters are set with a send heartbeat of 0 seconds, which tells the controller to never send an update on the output SNVT.  All Xenta 121 controllers come with a default send heartbeat of 0 seconds, so for them to function in an LNS network where they must send data to another controller, the send heartbeat must be set to something greater than 0 seconds. Resolution In order to adjust the send or receive heartbeat of a Xenta 121 controller, follow these steps: Right click on the controller and go to PlugIns > TAC ZBuilder Plug-In. In ZBuilder, click on the Configuration tab and go to LON > Node. Here the Send heartbeat and Receive heartbeat can be changed. The following nvo values will require the Send heartbeat be set to a value greater than zero in order to communicate with another controller using a SNVT binding. nvoSpaceTemp nvoUnitStatus nvoHeatPrimary nvoHeatSecondary nvoCoolPrimary nvoEffectOccup nvoTerminalLoad nvoEffectSetpt nvoFanSpeed nvoEnergyHoldOff nvoOccSensor nvoRawDOStatus   The following nvi values will default to invalid if they do not receive an update within a specified period of time. For most applications this should be left at zero. If the application must actively poll a SNVT then the receive heartbeat can be set to a value greater than zero. nviApplicMode nviSetPtOffset nviEnergyHoldOff nviFanProof nviOccSensor nviSpaceRH nviOutdoorRH nviSpaceIAQ nviOutdoorTemp nviSourceTemp nviAuxHeatEnable nviSourceFlow nviComprEnable

Issue All of the nodes are yellow and when they are clicked on the error below is displayed even though the database is attached to the network (OnNet), the network interface is on the correct channel, and the network interface passed all applicable tests. Environment NL220 Cause When the nodes appear yellow, this means that the LNS database has been corrupted. Resolution It can be attempted to repair the database using the Echelon LNS Database Validator. Follow these steps. If NL220 is still running, shut it down. Go to the Start menu > All Programs > Echelon LNS Utilities > LNS Database Validator. Select the corrupt database in the "Network to Validate" drop down box. Check the box next to Repair Database. Now click on the button called Validate.   If these steps do not repair the database, send the LNS database backup to Echelon support to see if they can correct the problem.

Issue When right clicking on the Xenta 100 device in Lonmaker or NL220 the Xenta 100 plug-in is not shown. Environment Lonmaker NL220 Xenta 104-A Xenta 101 Xenta 102 Xenta 103 Xenta 110 Cause The Xenta 100 plug-in is not accessible when launched from the physical device in Lonmaker or NL220 Resolution The plug-ins for all Xenta 100 controllers are only accessible when launched from the controller function block. They are not accessible when launched from the physical device. To launch the Xenta 104-A plug-in in Lonmaker, right click on the function block and choose plug-in:   To launch the Xenta 104-A plug-in in NL220, right click on the function block and choose plug-in:

Issue When you open LonMaker 3.13 the LonMaker Menu list is not shown in Visio. Environment Lonmaker Cause The Visio macro security settings sometimes become corrupted Resolution  To restore the link to the LonMaker software, follow these steps: Open the Windows Start menu, point to Program Folders, and then click Microsoft Visio. Visio starts Open the Tools menu, point to Options, and then click Security. If any of the check boxes under Macro Security are not selected, select them, click OK, and then exit and restart the LonMaker tool. If you restart the LonMaker tool and you see the LonMaker menu, skip the rest of this procedure. In LonMaker  open the Tools menu, point to Options and then click File Paths tab. Write down the LonMaker path shown in the Add-ons box, and then delete it. By default, the LonMaker path is C:\LonWorks\LonMaker\Visio. *This should be C:\LonWorks\LonMaker. The path may be followed by a semicolon if there are any additional paths in the list. Exit and restart Visio. Open the Tools menu, point to Options, point to Advanced, and then click File Paths. Enter the LonMaker path you wrote down in step 5 in the Add-ons box. Include the semicolon if there are additional paths after the LonMaker path. Exit Visio and then start the LonMaker tool.

Issue All the correct $LAN objects are setup in the Vista Master and Slave but neither will communicate with each other. If you check the nodes, the connection status shows connected but the Servers will not be online. Environment Vista 5 Cause The server has had the DMZ zone settings Unchecked. This will prevent Server to Server communications. Resolution Recheck the Server DMZ setting back to the standard install defaults.

Issue Unable to view a graphic in Xenta Server web interface. The graphic is not displayed and a Java error message is shown. The message is as follows: Environment TAC Xenta Server TGML graphics 5.1.X Cause The exact cause is unknown but this is somehow related to localisation - in other words a conflict between the language setting on the PC and the Xenta Server web interface. Resolution Set the PC's (on which the browser is located) language to English to eliminate the problem.

Issue The Lonworks Network has been moved under the LNS Port and no longer resides directly under the Vista Server in the tree structure as it was in previous versions.  This will add a level in the binding path and the old paths are no longer valid. This will impact any binding paths to objects on the root level of the System Tree.  Product Line TAC Vista Environment Upgrade Vista from versions older than 4.5 to newer versions OGC Graphic bindings Trend Log bindings Cause Versions of Vista < 4.5 had the Lonworks Network connected directly to the Vista Server in the workstation tree structure. A revision to this tree structure was made in all versions of vista > or = 4.5. After an upgrade from an earlier version to 4.5 the Lonworks Network is under the LNS port and is no longer connected directly under the Vista Server. This will add a step to the path in your graphic bindings that must be corrected in the OGC Graphic Editor. Example: OLD Binding Path: VistaServer_LonWorksGroup_ControllerName_Point NEW Binding Path: VistaServer_LNSPort_LonWorksGroup_ControllerName_Point Resolution You will need to edit the binding path of graphics at the root level of the System Tree. Follow the steps below to repair the bindings: Right click on the folder that contains the graphics that need to be altered in Vista Workstation (This same procedure can be performed on individual graphics as well instead of an entire folder). Select "Change References". Click Search in the Change references window. This will display all references that are contained in this folder. Select all references (Alt A) in the window and click Replace. Type the OLD path into the "Find what" field (example:VistaServer_LonWorksGroup). Type the NEW path into the "Replace with" (example:VistaServer_LNSPort_LonWorksGroup). Click OK. Verify that the reference path in the New column is correct and then click Save. This will repair all of the bindings in this folder.  You will need to repeat these steps for all folders containing items that reference points below the LNSPort . Note: Correcting this path will fix the graphics bindings in all future releases of Vista.

Issue When using a STR-150 room stat with the TAC Xenta 121-FC/HP, the effective occupancy signal output defaults to the Y1 output in ZBuilder. Y1 is the only analog output on the Xenta 121-FC/HP so this creates a conflict if an analog valve is being controlled Product Line TAC Vista Environment TAC Xenta 121-FC/HP STR-150 ZBuilder Cause In order to activate the effective occupancy signal to the STR-150 room stat, the Hardwired status LED option must be selected. This can be found under the Configuration tab > Connected devices > Room unit in ZBuilder. When this is selected, it places the output on Y1 by default. Resolution In ZBuilder, it is possible to move the effective occupancy signal named "Status LED" from the default location on Y1 to K1 through K4. If a K output is used then a 5 Volt DC external power supply will be required. Place the 5 Volts DC on KC and land the mode wire from the STR-150 on one of the K outputs. It is recommended that K4 be used because it does not share a common with the other K outputs. This way K1, K2, and K3 are free to be used for other things.

Issue Various errors during installation of I/NET 2.42 and Vista 5.1.7 on a 64-bit Operating system Product Line TAC INET, TAC Vista Environment Windows 7 64-Bit Cause Windows 7 64-Bit Resolution Overview: Install SQL according the instructions found in the SQLExpress folder on the I/NET CD Run the SQL Server 2005 backwards compatibility tool located on the I/NET installation CD Install Vista 5.1.7 Install I/NET 2.42. Step-by-Step Process: Installing SQL Download SQL2008 Express 64 (SQLEXPR_x64_ENU.exe) bit from this location http://www.microsoft.com/en-us/download/details.aspx?id=1695 Run SQLEXPR_x64_ENU.exe In the left hand section, select Installation In the Right and section, select New SQL Server stand-alone installation of add features to an existing installation. At the "Setup Support Rules" screen select OK At the "Product Key" screen, select Next At the "License Terms" screen, check accept and select "Next" At the "Setup Support Files" screen, select Install At the "Setup Support Rules" screen, select Next At the "Feature Selection" screen select: Database Engine Services, SQL Server Replication, Management Tools - Basic (If Present) and SQL Client Connectivity SDK. Leave the Shared feature directory as default. At the "Instance Configuration" screen, select the Default instance option, accept the default Instance ID, accept the Instance root directory default settings and select next. At the "Disk Space Requirements" screen, select Next At the "Server Configuration" screen, under SQL Server Database Engine set the Account name to NT AUTHORITY/SYSTEM, leave the password field blanks, and set the startup type to automatic. Under SQL Server Browser Service, set the Startup Type to Automatic At the Database Engine Configuration screen, set the Authentication Mode to "Mixed Mode", Define a strong password (example: @sql2008), in the Specify SQL Server administrators section click "Add Current User". Select Next. At the "Error and Usage Reporting" screen, select Next At the "Installation Rules" screen, select Next At the "Ready to Install" screen, select Install At the Installation Progress screen, when the setup process is complete, select Next At the "Complete" screen, select Close. SQL Configuration: In the Windows Start Menu, launch the SQL Server Configuration Manager In the Left hand section of the window, highlight SQL Server Services Verify that SQL Server Browser and SQL Server are Running In the left hand section of the window, expand SQL Server Network Configuration and highlight Protocols for MSSQLSERVER Enable Named pipes and TCP/IP Close the SQL Server Configuration Manager Restart the PC Installing SQL Server 2005 Backward Compatibility On the I/NET 2.42 installation CD, look in Support\SQLBCM_64Bit and launch the SQLServer2005_BC_x64.msi file Follow all the prompts on each screen and accept all defaults. Install Vista 5.1.7 Download and Run the TAC Vista Server 5.1.7 installation package. Accept all default settings Do not start the Vista Server at this time Install I/NET Seven 2.42 Install I/NET Seven 2.42 using the installation CD Follow prompts and use defaults When prompted for the SQL password, select "Windows Authentication" Restart the PC Open I/NET Configuration through the start menu. Modify the default Config profile or create a new profile. Close I/NET Configuration Start I/NET Activate any Vista Licensing Start Vista Server Start Vista Workstation

Issue Is there a way to see what someone has done on a particular Xenta controller and what they have changed Environment Vista Cause Yes you can select the controller and retrieve the events for that controller. Resolution First locate the controller in the network. The right click on the controller and select View events The event viewer will then display all the events from that controller. this will include the old vale and new value is a value has been changed. The user that made these changes is also logged in the event viewer. You can use the filter option     then to narrow down on the date range if required.