Building Automation Knowledge Base

Issue Errors occur when trying to open up graphics in Vista Workstation similar to these: Microsoft .NET Framework Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue. A generic error occurred in GDI+. TAC Vista Workstation Encountered an improper argument. Environment Windows 7 Windows XP Vista TGML Cause Installing Windows XP on a machine that came pre-installed with Windows 7 has been observed to cause this problem. Resolution Computers that are sold with Windows 7 pre-installed typically have hardware that is optimized for Windows 7 and often experience a variety of problems when they are re-imaged to Windows XP. The best solution is to re-install Windows 7. TAC Vista 5.1.4 and newer is compatible with Windows 7 as well as some third-party LNS network tools (check manufacturer's websites for more information). Windows 7 Professional, Ultimate and Enterprise can run programs using "XP Mode". XP Mode is a separate download available for free from Microsoft's website.

Issue Adding a device through the System Plug-in results in missing SNVTs, SCPTs, or Module/Functional Block Names in the Vista database. Environment Vista 5.x.x Cause The XIF file is either incorrect or parsed improperly. Resolution Right click on the device and select properties. Click on the XIF file tab. View the XIF file name (this can be found in the $thisfil directory of the Vista database) and either browse in a renamed copy of the existing file or an independent copy of the file by clicking the ... button. Click Ok Log out of Workstation Log into Workstation to see the changes. Note: For a change to be detected the filename or location of the file must be different.

Issue How to register LonTalk Protocol Analyzer Software Product Line EcoStruxure Building Operation, TAC Vista Environment Vista LPA Cause The LonTalk Protocol Analyzer software is a tool for LonWorks network troubleshooting. There are two kinds of LPA license. Some customers may be confused about it. Resolution To use the LPA, you need to purchase the software license. There are 4 kinds of LPA license. Refer to this page for further explanation. LPA-SW: This license is bound to NIC709-USB.  Need to use specific NIC709-USB to be the network interface of the software. LPA-IP-SW: This license is bound to NIC852. Need to use specific NIC852 to be the network interface of the software. LPA-IP: Same as the above, but includes a dongle.   The steps of registration for the current version of LPA using the current NIC driver is the following: Install the drive for the LOYTEC Network Interface. Refer to Loytec's Website. Open the LPA program Click on "Help->Register Product"   Enter the Registration Code in the product package, and click Add.   The steps of registration for previous versions of LPA using the previous NIC driver is the following: Install the drive for the LOYTEC Network Interface. Refer to Loytec Website. Open the LConfig program.   Click Register / Activate to open the registration window. Enter the Registration Code in the product package, and click Add. Then the registration is finished. Open the LPA software to test whether the license works fine.

Issue When downloading an XBuilder project (Send to Target) a window pops up with three send options: Send all project and language files Send all project files Send modified project files What is the difference between each of these and when is it appropriate to use each one? Environment XBuilder Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Cause Knowing what each option does and when it's best to use each one can save a lot of time in troubleshooting integrations and general operations of a Xenta Server. Resolution Send all project and language files This option is very rarely used. The only time it is necessary to send language files is when the display language inside the Xenta Server is being changed (e.g. from English to Polish).   Send all project files If there was a default operation to always use, it would be send all project files. It will always perform the desired operation. However, it always prompts a reboot of the Xenta Server. Communication with the Xenta unit will be interrupted for ~2 minutes while the reboot occurs. If a lot of quick changes are being tested, this can add unnecessary time to the task. However, the reboot is sometimes desired. Especially when making small changes to integration device templates, a reboot will ensure the changes take immediate effect. In general, if a change has been made to the Network pane in XBuilder, all project files should be sent.   Send modified project files Send modified project files when minor changes to the System pane have been made. Adding a values page, editing a time object, deleting a graphic page. These are all changes that can be sent with only modified project files. This will not reboot the unit and will allow for faster editing of the project.

Issue Step by step instructions for installing and configuring a Loytec NIC852 dongle, also known as an Orion Stack. Environment Vista LNS Network Echelon LonMaker Cause A single Vista server can handle communications to about four "average" sized LNS Networks. Very large networks or many LNS ports in a single server may result in a degradation of communication reliability. An Orion Stack changes the way Vista communicates with the LNS Server and allows up to 28 LNS Ports to be added. Resolution NOTE: If LonWorks Interfaces was previously configured as your Network Interface you must delete the computers IP address from the IP-852 tab before you continue. Insert NIC852 Dongle into USB slot on Front-End computer.  This dongle must be plugged in at all times for the Orion Stack to work. Use the Loytec CD to install the necessary software to use the dongle such as hardware drivers and the LConfig interface Make sure that the latest drivers are installed for the NIC Interface.  The latest drivers can be found at:  http://www.loytec.com/index.php?option=com_docman&task=cat_view&gid=116&Itemid=25 When properly installed, the Loytec symbol should appear on the bottom right corner of the Windows Toolbar.   Right-clicking on the symbol will allow you to easily access the LConfig interface.  Click on LConfig to configure the NIC852 (Orion Stack) Using the LConfig interface, navigate to the NIC852 tab and check the box next to enable the device.  The transceiver should most likely be set to IP-10L and the number of LNS Applications should be selected (aka, the number of LNS databases) Click CNIP configuration to set up the IP addresses for the Device (aka..The Front-End Computer IP address) and the Config. Server’s IP address.  * Don’t forget to enter the Device Name (aka Computer Name).  Click “Ok” twice and the device should be configured.  Test it before closing out. With the NIC852 configured, open Lonmaker and open the first drawing directory with “Show all network options dialogs” checked. When the Network opens, click ‘Next’ to configure the Network Interface.  Check the box next to ‘Network Attached’ and select the first NIC_852 entry.  Click next to let the network configure.  Go through the rest of the windows by clicking ‘Next”, save the drawing, and exit. The network interface for each LNS can also be chosen by going to Lonmaker > Network Properties in the Visio drawing and utilizing the Network Interface tab. Next, set the Communication Port for the TAC Network to look for a Loytec device.  To do, this open ‘TAC Vista System Plug-In’ which can be found at Lonmaker > System Plug-in > TAC Vista System Plug-In.  In this window, right-click the Network (top of the controller tree under the TAC Network) and click “Settings.” When the ‘TAC Network Settings’ window opens, under the Network tab select “Communication Port-Loytec” and click OK.  The TAC Network will have to be updated after this.  Repeat Steps 6-10 for each LNS database.  Remember to select a different Network Interface each time. After configuring the NIC for each LNS Database.  The Orion Stack should be properly setup.  * Note:  It is a good idea to note that an Orion Stack is installed on the main graphics page for the site to keep other potential users informed, like remote support engineers.

Issue Opening an MTA file in Menta causes an "The device type is not supported" error message. Environment Menta 5.x.x XBuilder 5.x.x Cause The Menta file is for a Xenta 700 controller and cannot be opened in stand alone Menta which only supports the Xenta 280, 300, and 400 series of programmable controllers. Resolution Import the MTA file into an Xbuilder project's Menta Library in order to edit or view the MTA file.

Issue Receive PARSER IO ERROR 13 when direct serial downloading a Xenta 401 controller. Environment Menta Xenta Cause Physical IO points in a Xenta 280 or Xenta 300 menta application are assigned to M0-X1, M0-U2, etc, and when these physical IO points are copied to a Xenta 401 or Xenta 401:B menta application M0 does not exist. Because these points were copied into the menta application and not created within that application or imported as a library file, simulation mode will not check this IO terminal error. This situation will show itself by failed downloads in the system plug-in, and PARSER IO ERROR 13 when direct serial downloading. Resolution In Menta select Options>IO Configuration Table. Click the "bound to" column to sort by physical IO within the menta file. Look for points with the M0 reference similar to the screen shot below. Set these points to the proper physical IO terminal for the application.  

Issue After Vista system commissioning finished. Site engineers need to move Vista database from engineer laptops to site PC. Sometimes Vista database export & import needed. Engineers found some time schedule or setpoint (PVI / PVR / PVB) returned to initial value, not the value they changed during the commissioning progress or customer defined later. Environment Vista Menta Cause Vista may not save customer changes to the Menta file sometimes. Therefore, when exporting the menta file, those forced by operator values may not be carried along with. Resolution To save the latest setting of time schedule object or setpoint object in Vista database before export the database, make sure following steps have done. Right click on the Xenta controller and select "Edit" Input "username" and "password" after the Menta application window comes up. In the Menta application, click "Vista Database", select "Save", Make sure following window is displayed. If not, try making some modification in Menta, such as move a wire or block. Then click "Vista Database >Save" Repeat step 1 to 4 for those Xenta controllers which need export. In Vista Workstation, click "File > Database > Export" to export the desired networks / Xenta Servers / Devices. Copy the ZIP file to target PC, and Import the contents to the final system.

Issue After creating a Vista user and modifying its password in Vista Workstation, can not login into Vista Workstation by using this user and its password. Or, modify TAC Vista user’s password and the password automatically changes into unidentifiable characters. Environment Vista Workstation Chinese Windows operating system or using Chinese language package. (NOTE: may also apply to some other Eastern Asia language package). Tested on Windows XP Professional Cause When the “Languages at Regional Options” and "Location" settings are set to Chinese/China or two settings are different, the user password may be changed to some unidentifiable characters  or even digits password changes to odd digits password (For example, 5 digits password changes to 4 digits password). Resolution Log in as an system manager Vista user, and change the desired user's password to an even digits password. If the issue still exists, carry out according to the following processes: Close TAC Vista Workstation and TAC Vista Server. Click “start” >“Control Panel” to open control panel. Double click “Regional and Language Options”. Check the selection of standards and formats at “Regional Options” is the same with the selection of language for non-Unicode programs at “Advanced”. If not, set them to be the same. Start TAC Vista Server and Workstation, the issue should be solved.

Issue Get "Invalid Data" error message when trying to change an Xenta Trendlog's setting from Man-On to Auto in Vista workstation. Environment Windows 2003 & XP (confirmed - possibly other operating systems). TAC Vista Workstation/Server 5.1.4. Cause Unknown. Resolution Upgrade to TAC Vista 5.1.6. This issue has been resolved in this version.

Issue "Out of memory" warning dialogue window pops up when trying to access objects in Vista. How to create a performance log to monitor Vista's memory usage Environment All Operating Systems TAC Vista 5.1.X - server and workstation Cause Memory usages exceeds the allocated memory on the PC. Resolution Check the memory usage. The first step is to simply check the memory usage of all the processes that are running. Open task manager (right-click on the task bar and select from the context menu). Select the tab Processes and check that there are no processes using a large amount of memory. Especially interesting are TACOS.exe (Vista server) and TACVistaExplorer.exe (Vista Workstation). If everything looks OK here monitor Vista's memory usage. Click on Start->Run and type in perfmon. Click on OK. Select System Monitor in the menu-tree to the left. Click on the + (plus) symbol in the graph pane to the right. Use the following settings:   Click add and then do the same adding TACVistaExplorer. In the same way add Memory - Available bytes Monitor the memory usage and check to see if anything unusual happens - if TACOS's memory usage is near the available bytes or if TACOS's memory usage keeps growing etc. If it's possible to establish that TACOS and TACVistaExplorer are using a large percentage of the PC's memory, upgrade to Vista 5.1.6. and/or increase the physical RAM of the PC (if possible). A lot of improvements have been made to TAC Vista that have optimized memory usage. A significant reduction in memory usage should occur after upgrade.

Issue It may be useful to have logic in Menta programs trigger an event in Vista so that it can be recorded and stored in the event log. Environment Vista Workstation Menta Cause Alarms that have the Priority parameter set to 0 are used for info purposes only and only show in the event viewer and not the alarm viewer (queue). Resolution Events can be triggered by a Menta program by creating an Alarm block in Menta and setting the Priority parameter to zero. This causes the alarm to only function as an event and keeps it from showing up in the alarm queue. The following is taken from the Menta Technical Manual: The alarm priority is specified with the Priority parameter. There are 10 levels, 1 to 9 and 0, where 1 is the highest. Events with priority 0 (Information messages) have the lowest priority. They are not placed in the alarm database of TAC Vista and do not appear in the alarm overview. An example where using a priority zero alarm might be useful is to record as an event whenever an air handler enables and disables its economizer. This would be done as follows: 1. An ALARM block is created and named EVENTS\ECONOMIZER_ENBL. The Priority parameter is set to 0. Alarm Control is set to the standard alarm control object which is $Alr_Cntrl. The Tripped Alarm text is set as "ECONOMIZER ENABLED" and the Reset Alarm text is set as "ECONOMIZER DISABLED". 2. The ALARM block is then connected to the Economizer function. Now an event will be generated each time the economizer is enabled and disabled but an alarm will never pop up in the alarm viewer. An Events Viewer object could now be created to make it easier to view just economizer events without everything else. This is done as follows: In Vista Workstation right click the Root object and select New > Object > Viewer - Events. Type in a description and enter the Object ID of the economizer event that has been created. This can be found by locating an instance of the economizer event in the standard event viewer and copying the Object ID from there. The event viewer could be set up to display all priority 0 alarms instead of one specific event type by entering a 0 in Priorities in the Alarms section under the Event Specifics tab. The amount of time displayed in the event viewer can be filtered under the Date and Time tab. It may be useful to remove unneeded columns from the new event viewer so that only the relevant information will be displayed. In this example everything is unselected except Time, Object ID and Text under the Select Column(s) tab. The event viewer will automatically update and could be used for real-time monitoring of whatever event(s) it has been configured to display.

Issue If the result of a divide by zero is sent to a physical AO, Vista Workstation will display this value as -2. The physical output, however, will be sending out the maximum specified voltage (default 10V). In Menta simulation mode, if a divide by zero scenario is simulated, the following error will pop up: tam32 Division by zero Connected to a controller viewing live Menta, a divide by zero equation will result in a displayed value of 1.#QNAN. All subsequent equations using this value will also output 1.#QNAN. Environment Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause Division by zero results in an invalid value that is interpreted differently by the controller's physical outputs, the Menta application, and the Vista Workstation. The application will continue to run, but any output affected by the invalid value will not act as expected. Division by zero is not usually intentional (there's no equation that says "A/0"). Instead, it is usually the result of an unforeseen sequence of events where complex equations result in a 0 in the denominator of an equation, and simulations did not ever produce this unique situation. Resolution To troubleshoot whether a divide by zero is occurring: The best solution is to connect live to the controller with a serial cable and watch the live Menta. Look for any values that read 1.#QNAN and trace it back to the source. If live Menta is no available, the simulation mode can be helpful. Recreate the scenario as best as possible with all inputs set to the real life instance. To prevent a divide by zero error: Never allow an equation to write to the denominator of a division equation without programming divide by zero prevention. Add an expression block prior to the division equation that says "if the value is zero, then output a safe value" Add a max block to the input that compares the value with 0.0001, so that a zero will never pass through.

Issue A stand alone Xbuilder project was already started and now needs to be converted to a Xenta Server in the Vista database. Environment Vista Server 4.5.0/5.x.x Xbuilder 4.5.0/5.x.x Cause The Xbuilder project can be saved to the Vista database, but if there is a LON network in the Xbuilder project it will be replaced by the LON network defined in the Vista database. This is necessary to ensure that the devices are commissioned and addressed to be compatible with the Xenta Server. If this network has not been created yet in the Vista database then create the network, groups, and controllers first. Try to match as much of the names as possible to allow existing references in the Xbuilder project to be preserved. Any changes in the paths will require relinking your graphics, alarms, trends, etc. Resolution Open the stand alone Xbuilder project Select the Vista Database\ Save as option Select an existing Xenta Server object or create a new one in the Select window and click Select. Click "OK" and the network will be replaced by the one in the Vista database.

Issue Not allowed to add a new event to a Xenta Time Schedule through Vista Workstation. One of the following errors results: The maximum number of total events is exceeded.   The maximum number of week events is exceeded. Only alternative events can be added.   The maximum number of alternative events is exceeded. Only week events can be added. Environment Vista Workstation Xenta Time Schedules Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause The adjustable setting for the maximum amount of events allowed in a single Time Schedule object has been exceeded. Resolution Verify how many weekly and how many alternative events are allowed. This is available on the time schedule editing dialog in the lower right hand corner. Click the "All Events" button to display all previously defined events. Weekly events are displayed with a dash "-" in the From Date, To Date columns Alternative events will have a date in the From Date, To Date columns. The year may or may not be **** if this is a yearly recurring event.   Count how many weekly and how many alternative events are defined. If possible, delete unneeded events to clear space for new events. If a holiday is not set to occur yearly, then old events from years past may still be defined and can be deleted. If all of the events are required, then the capacity for the time schedule must be increased in Menta. Edit the Menta file Double click the TSCH block Increase the max for Week Charts, Holiday Charts, or both as needed.   Download the Menta changes to the controller and more events can be added.

Issue Public values, inputs and outputs of a Menta object defined in a Xenta 700 XBuilder project are displaying their values in Workstation as [Invalid Address]. When the value is double- clicked, the following error appears: Error in property Value. Read operation failed. Product Line TAC Vista Environment Vista Workstation Xenta Servers Xenta 701, 711, 721, 731 XBuilder Menta Cause The Menta object is not connected to a task. Therefore the Menta application is not being executed. Resolution In XBuilder, generate the project. Check the output window Generate tab for a warning that states "This Menta Object is not connected to a task" Double click the warning. The offending Menta object is highlighted. Drag and drop the Menta object into a Control Task folder in the Network Pane > TAC_Xenta_7xx > Control Tasks Regenerate and send the project to target. Menta object values should now report valid values.

Issue When an alternative holiday schedule is set up for "ON all day" or "OFF all day" the representation in the time schedule dialog and the operation is quite clear. However, when defining set hours of operation, it may not be clear when the unit is actually going to run. Environment Vista Workstation Xenta Time Schedule Cause An alternative or holiday schedule (represented in gray on the time schedule dialog) will override the operation for the entire day, not just when the alternative time is scheduled. Resolution An example alternative event: The unit is scheduled to run every day of the week from 8am to 5pm. On Tuesday, a special meeting requires that the unit run for an additional hour in the evening. The operator schedules the alternative event for 5pm to 6pm and the schedule dialog looks like this:   In reality, an alternative event will override operation for the entire day in which it is scheduled. Even though the time schedule display appears as though the unit will run any time the schedule is shown in white or gray, in reality, the operation will be as if the schedule was configured like this:   In order to properly schedule additional time to an existing time schedule, the original occupied hours must be accounted for in the definition of the alternative event. A correctly schedule additional hour is shown below:

Issue What effect do Central Time Charts have on a Xenta time schedule object? Can the Central Time Chart be selectively overridden at individual units? Making changes to a Xenta time schedule results in the following Information message: A central week chart and a central alternative chart are defined. any changes made in the chart will be overridden by the central charts. Xenta time schedule events are shown with an asterisk (*) next to the start time. Environment Vista Workstation Time Chart - TAC Xenta Time Chart - Global Time Chart - Local Cause If a central time chart has been defined for a Xenta time schedule object, the central time chart will override the operation completely (both for scheduled on and scheduled off times). Resolution Double click a Time Chart - TAC Xenta object in Vista Workstation. The edit dialog is shown. Click on the third tab, Central Time Charts Select either a Time Chart - Global or a Time Chart - Local object to override the Xenta time schedule object. This can be done selectively for just Weekly recurring events, just Holiday alternative events, or both. Once selected, all events defined in the Xenta time chart will be shown with asterisks (*) indicating that they are being overwritten by a Central Time Chart. Exceptions cannot be made to the Central Time Chart for individual units. Refer to the TAC Vista Technical Manual Chapter 19.1 Time Charts for additional information.

Issue When creating a device template in NL220 from network, receive an error message widow: Error creating the new device template.   In NL220 traces window, an error message is also being displayed: LCA: an attempt was made to register or add a device without a channel handle specified, but the system was not able to automatically determine the channel on which the device resides. (Subsystem: NS,#79) Environment NL220 Multi-channel routers (such as a Loytec L-IP-33ECTB) Cause This issue happens when using a multi-channel router (for example: L-IP-33ECTB). When using such a router under "Template view", NL220 will not be able to identify which channel the device is under. Resolution Sometimes it is necessary to create a device template from network (also called upload XIF file from device). In this situation, it is recommended to create the device template while creating the node in a specified channel. Steps as listed below: Switch to "Channel view".   Right click on the proper channel and select “New node on ” or go to "Edit->New->New node".   In the "New node(s)" window , name the node and choose “Create node from network”.   Service pin the device which is going to be the device template or manually enter its Neuron ID. Then click "Continue" to create the node.   Once NL220 finishes node configuration, it should automatically create the device template under the template view for further use. The alternative way is to replace the multi-channel router to a single channel router. Once the LNS database is imported into TAC Vista, a copy of the XIF file can be found in the database $thisfil folder.

Issue Xenta Server Error: "Sequences number in unit was reset. Fetching from first event." Environment Xenta Server Xenta 511, 511:B, 527, 701, 711, 721 and 731 Xenta Error Log Cause When Vista asks the Xenta Server for log data,it is returned unexpected data Resolution Reinstalling or upgrading to a System Program version >5.14 SP1 should correct this issue.