Building Automation Knowledge Base

Issue TAC 200 OTP Controller replacement battery information Product Line Field Devices, TAC Vista Environment Site with TAC 200 OTP Controller  Cause On-board battery is in need of replacement, Part number - 200-1005-000. Here is additional information: TAC 200 OTP compensator and optimiser TAC 200 OTP is a compensator and an optimiser. It controls the heating via a boiler output and a mixing valve or via two stages of gas boilers. TAC 200 OTP can be operated with or without a room sensor. The controller has an easy-to-use operator's panel and needs virtually no maintenance. TAC 200 OTP is also described in the following documents, all available in English: Data sheet TAC 200 OTP C-10-31 The data sheet contains a comprehensive specification of the controller and should be read together with the handbook (part number 0-003-1148). A brief instruction A small leaflet normally placed in a slot in the operator's panel (part number 0FL-3564). User's manual TAC 200 OTP The user's manual (part number 0FL-3563) is a description for installation and start-up, packed together with the unit. The contents are a condensed version of chapter 2 in this manual and a mounting instruction. Manuals are available in TAC 200 OTP User Guide, TAC 239W DHW User Guide. Resolution Replacement battery is 342200360 CAP, .22 F 5.5V RM5 

Issue TGML Graphic Alert: ReferenceError: "test" is not defined. (cmd#16) Product Line TAC Vista Environment Vista 5 TGML Graphic Cause A Javascript tag in the TGML has used a variable that has not been defined. Resolution Determine which script tag is generating the error. When did the error occur? When the page loaded?  When a value changed?  When the user clicked?  Did it happen once or multiple times?  These questions can help you narrow down which script has thrown the error. Save the graphic under a different name.  Delete portions of the graphic until the error clears.  The component that was removed holds the offending script. The cmd# syntax is indicating which line of the script has the error.  Launch the script editor by clicking the "..." button next to the script Content attribute.  In this example, go to line 16 of the code. The variable name is in quotes.  In this example, find where a variable named "test" was used. Verify that the variable has been declared and defined prior to being used. Also check out the JavaScript Essentials - Programs and Statements Quick-Help video on the Exchange.

Issue It is not possible to extract a Menta file directly from a Xenta programmable. If a backup of the Menta file, or a backup of the Vista database is not available, there is no way to extract the program from the controller. "File object contain no actual MTA file" when trying to open a Menta file. Product Line TAC Vista Environment Xenta Programmable Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause Going out to a job site without a database backup, or a backup of the Menta applications (.MTA), leaves no way to view the Menta that is running in a Xenta programmable controller. Resolution Options are: Find a backup of the .MTA Menta application that has been downloaded previously into the controller. Find a backup of the Vista database.  Menta files are stored in the Vista database for each programmable controller. To extract a Menta file from a Vista database, the preferred method is described in Get all MTA files saved from a Vista Database. To extract the files one at a time, right-click on the controller and select Edit. Connecting to a live controller, it is possible to view all public values inside the controller and to extract a .COD code file.  Unfortunately, these cannot be used to create a .MTA to view the logic.

Issue OP is plugged into Xenta base unit, or wired up using terminal strip on the back, but the screen is still blank. Product Line TAC Vista Environment Xenta OP Xenta programmable controller Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Xenta 100 series ASC Cause Either power is not properly being applied to the OP, or the contrast on the LCD has been adjusted all the way down making the menu invisible. For troubleshooting connectivity issues please see the following articles: Xenta programmable controllers: "No Answer" on an OP when connecting to a Xenta 280/300/400 Xenta 100 series ASCs: Use a Xenta OP with a Xenta 100 controller Resolution Check OP port connection Check power connections on terminals 3 and 4 Make sure the contrast hasn't been adjusted all the way down

Issue On larger databases it is time intensive to resynchronize the drawing by creating group binding from the System Plug-in. Is it possible to manually set the TAC group binding on a Xenta Server controller to enable LACnet communication? Product Line TAC Vista Environment LonMaker Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Cause The TAC group binding can be created manually by editing the group binding properties. Resolution First identify what group ID is the TAC group bindings. Use Verifying Xenta Group Bindings in an LNS system as a guide to identify the group number of the TAC group binding. Follow these steps to manually create the TAC group binding in a Xenta Server: Create the Xenta Server in LonMaker and commission it. Drop a Virtual Function Block for the Xenta Server Drop a msg_out shape on to the Virtual Function Block of the Xenta Server and select tag_0. Find a Virtual Function Block for one of the Xenta programmable controllers.   a. Right click on the tag_0 reference shape and select properties.   b. Expand the connection details and then highlight the source signal in the Hub window. c. Click the Target pane. d. Click the "Add FB/SNs.." and add the Xenta Server Virtual Function Block. e. Select the tag_0 under the Xenta Server Virtual Function Block. f. Click the "Add" button. g. Click the "OK" button. The Xenta Server now has the TAC group binding created.

Issue How to display humidity level or CO2 level on a STR350/STR351? What type of sensor can display humidity or CO2 level? Product Line TAC Vista Environment STR 350 SHR 100 Cause All Schneider Electric made humidity sensors and CO2 sensors do not have display. In order to display the value locally, need to wire the sensor to a STR 350, and configure the STR 350 for display. Resolution Wire humidity sensor or CO2 sensor to STR 351 or STR 351's AUX. input channels. Following STR 350/351 manually setup without plug-in (nciOption1 and nciOption2) to add the STR 350 or STR351 into the network. Change nciOption2 bit 6-8 according to the sensor type. Note: If using a plug in or adding the STR 35X in XBuilder, can simply follow the configuration guide. Set nciOption2 bit 9 to a value of 1. This allows the humidity or CO2 to be displayed on the STR.

Issue A Xenta 121-FC controller setup as a 2 pipe system will not heat or cool even though the terminal load is showing a demand. Product Line TAC Vista Environment Xenta 121-FC Cause The Xenta 121-FC does not have a water temperature sensor wired into the device Resolution For this functionality to work automatically, a water temperature sensor must be wired into the U1 terminal on the FC-121. The other alternative is to set the supply temperature via the SNVT nviSourceTemp. This can be done from a supervisory system that is feeding the water to the 121-FC. To use the SNVT nviSourceTemp as a solution the correct heartbeat will be require to be set in the 121-FC. Values sent from a Xenta 121 FC/HP via SNVT bindings are not making it to the receiving controller is a link on how to set that up. 

Issue The Lon comms card that can be installed in the pciExpress slot on HP Laptops can sometimes generate a "Buffers Full" error. The identical fault details can be found in another Knowledge Base article relating to Dell E6400 laptops. Product Line Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Sigma using IC-3 Lon with Lonmaker for Windows Vista Micronet when using Lon interface Using the Lon PCC-10 Card in a laptop that has an express card slot and not a PCMCIA card slot. Cause There is an issue with some HP 6560D Probook laptop that is provided by the UK IS department to commissioning and service engineers. If they need to use the Echelon Lontalk PCC-10 PCMCIA card then when trying to configure it via the Control Panel applet it will fail giving an error message "Driver Buffers Full" or it will simply fail when running diagnostic tests. Resolution See Can a LON PCC-10 PCMCIA card work in a laptop with an express card slot? for details of the Express card configuration for laptops.

Issue When the quantity of Xenta Server reaches a certain figure, for example 20, the following Xenta Servers begin to become offline in Vista 5.1.2. Product Line TAC Vista Environment Vista 5.1.2 Cause There are issues when more than 20 Xenta Servers are added in Vista 5.1.2. After 20 Xenta servers have been added, the following Xenta Servers begin to become offline in Workstation. Resolution Upgrade to Vista 5.1.5 or greater. The Xbuilder and Xenta Server firmware can stay 5.1.2 without change. For information on how to install Vista 5.1.5, refer to Instructions for downloading and installing Vista 5.1.5 on an operating system older than Windows 7.

Issue Values are coming into Vista without issue but do not update on the graphics in the Xenta 7XX. Product Line TAC Vista Environment Workstation Graphics Xenta Server 701, 711, 721, 731 Cause If there is a Xenta Server in the database, when connection objects are not used to bind values between a controller and a Menta program in the Xenta Server, this graphic update can occur. It can also be because of the XIF for a device being formatted incorrectly. If the procedure below doesn't solve the issue, refer to LON device can communicate in Vista, but fails in a Xenta Server / XBuilder Resolution There are two options to correct this issue: Re-engineer the XBuilder project to use connection objects between the controller and the Menta program in the Xenta controller. The control task speed of the Menta program in the XBuilder project can be changed to a lower speed setting.

Issue The panes in Webstation are empty and login happens without specifying a user or password. When specifying the URL to Webstation the user is automatically logged in to Webstation but there are no objects in the panes. Product Line TAC Vista Environment TAC Vista Webstation 5.1.6/7 Cause This is caused by using the wrong application pool in Internet Information Services (IIS) manager. Resolution Ensure that the application pool SE ASP.NET v4.0 Classic is used. More information on how to set this and check other settings for Webstation can be found in Problems installing Vista Webstation 5.1.5 or newer.

Issue Error when trying to register plug-ins within an LNS environment. Two known examples: Plug-in 'TACOSSysPin.Document' launch failure. Unknown error 0X8007002    Plug-in 'TACOSSysPin.Document' launch failure. Exception occurred Product Line TAC Vista Environment LonMaker 3.X TAC Vista System Plug-in Cause There are two types of credits: Product specific credits like LonMaker or NL credits and then there are LNS credits. LonMaker/NL credits are used by LonMaker/NL220 to commission devices. LNS credits are not consumed by commissioning devices in LonMaker, but are consumed when commissioning devices in NL220. LNS credits are used by other LNS applications – like the TAC Vista System Plug-in. While LNS credits may not be consumed by LonMaker, they must be present in order for the plug-ins to launch. 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 information regarding NL220 and LNS credits see Ordering more LNS credits. Resolution Echelon released a Licensing Update in January of 2006 to improve the reliability of the Echelon licensing software, which was compromised due to newer security and self-protection features of Windows. This will not fix your already corrupted license files; however, this will help prevent the license from becoming corrupted in the future. It is highly recommended that this update be installed on all applicable products.  If you do not already have the LNS Licensing Update 2006 software (LnsLicensingUpdate2006.exe), download it from http://www.echelon.com/support/downloads/detail.asp?partNum=153-0155-01A. If you do not already have one, you will need to create a user account with Echelon. It is free. Shut down all LNS applications, including LNS enabled Windows services. LNS enabled Windows services are LNS applications that are being run under the Windows Service Manager as background processes. Examples from Echelon include the LNS Server application and the LNS DDE Server. Third party examples are typically HMI drivers for HMI workstation software products. Log on with Administrator privilege. For version 3 LNS Server installations that are not already at LNS version 3.08 or higher, LNS 3 Service Pack 8 or higher must be installed before applying this update. Service packs are available from www.echelon.com/downloads. Run LnsLicensingUpdate2006.exe. Reboot if requested by the installer. To resolve the issue of corrupted LNS credits:       Run the LNS Server License Wizard by navigating to Start > Programs > Echelon LNS Utilities > LNS Server License Wizard. It can also be found at C:\LonWorks\bin\LnsLic.exe. If the Max Credits, Credits Available, Max Deficits, Deficits Remaining, or Days Remaining are displaying zero values, then your LNS credits have become corrupted. To order free LNS replacement credits, hit Next. Hit Copy to Clipboard and paste into a blank email. After entering your specific contact information, you will want to check the "No Charge" box and the "Replacement Use" box. Before you send the form via fax or email, you also need to provide evidence that your LNS credits have been corrupted. Select Start > Run > and type "cmd" to reach a command prompt. This command will check the status of the LNS credits: checklic nsseng.exe An example of a working license is show below:   The output of this command should either be printed and sent with the fax or included in the email. Send the completed form to credits@echelon.com or print the forms and fax them to 1-408-790-3833. Note: If you are accustomed to ordering credits through another entity, do not send them this form. Only Echelon can issue replacement LNS credits. Echelon will reply with an application key that can be entered in this same window. When the LNS credits are restored, the System Plug-in should launch.

Issue See Check Xenta programmable online status from a Xenta 5/7/9xx LON node to determine if the Xenta 5/7/9xx controller is communicating with Xenta programmable controllers on the network. If it's not, graphic pages in certain Xenta units won't display data, or connection objects won't pass data as expected, etc. Product Line TAC Vista Environment Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 LNS Database XBuilder Cause A Xenta 5/7/9xx LON node pulls "double duty" as both a LON device and a Xenta device. It requires one Xenta Group Binding on message tag 0 to facilitate communication with Xenta programmable controllers. Resolution Check LacNet status (see Check Xenta programmable online status from a Xenta 5/7/9xx LON node).  If controllers are showing an offline status, proceed with the following steps. In LonMaker, right-click on the device and go to Properties. View the address table. The Xenta 5/7/9xx controller's address table should have the first entry (message tag 0) populated with an index that matches all the Xenta programmable controllers on the network (see Verifying Xenta Group Bindings in an LNS system for more information about checking address table group bindings). If the group binding for LacNet communication doesn't exist or is wrong, redo group bindings. Ensure the Xenta group masters of the network have not been manually removed from the network pane of the XBuilder project. Download the XBuilder project to the device. Recommission the device in LonMaker. If it is still not communicating, download each of the Xenta units that it is trying to communicate with and recommission them in LonMaker.

Issue How and when does a Xenta 121 resynchronize floating control outputs? Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta 121 - All versions Cause Documented reasons for floating control resynchronization on a Xenta 121 controller. Resolution There are 3 events that cause a Xenta 121 to resynchronize its floating control output logic. These reasons are: After a restart of the controller from a power cycle or reset command. The resynchronization is randomly initiated within the first 42 minutes after this restart. Testing shows an average of 20 minutes. After the controller is powered up and has done it's initial resynchronization, it will resynchronize every 18 hours there after. Commanding the snvt_switch input nviDOResync value member to  >0, and the state member to =1 Please see Programming SNVT_Switch in Menta for instructions on how to program snvt_switch in Menta.

Issue Display the Text Value for a multistate point (e.g. enumerated SNVT) instead of the numerical value in a TAC Vista Graphic page. Product Line TAC Vista Environment Vista IV OGC Graphics Editor Cause A digital presentation will display the integer value of the enumerated SNVT by default (1, 2, 3...). Many structured SNVT types use default enumerations (e.g. HVAC_HEAT, HVAC_COOL, HVAC_OFF). Rather than setting up a customer dynamic text value each time, the standard enumerations can be displayed. Resolution Add a digital presentation to the Graphic page Browse in multistate point. Check the check box "Presentation format." Now the text will be displayed instead on the numerical value. To define custom texts for use with multiple points, see Creating custom Multi-state Text definitions.

Issue Error message window appears when installing TAC Vista 5.1.6 as below. It says that "XXX.dll file is an invalid Win32 application". But the installation could be finished without any other error messages. However if trying to run TACOS.exe after installation. Another error message window appears as below. It said, "MSVCR100.dll is an invalid Windows image, please check your installation disk". If you try to uninstall TAC Vista 5.1.6 which you just installed. You would get another error message window appears as below. It says "XXX.dll file is an invalid Win32 application". User can not run TAC Vista 5.1.6 in your computer finally. Product Line TAC Vista Environment Windows XP SP3 TAC Vista 5.1.6 Cause It may cause by the msvcr100.dll file is damaged.  Resolution Uninstall TAC Vista 5.1.6. Refer to How to uninstall and completely remove TAC Vista 5 for detail In the %system root%\WINDOWS\system32, copy "msvcr100.dll" file from someone who has installed TAC Vista 5.1.6 Rename the msvcr100.dll file which existed in the folder in your computer, user can rename the file such as msvcr100.dllx Copy the file from other computer and paste it into your computer folder Run TAC Vista 5.1.6 installation file again

Issue Unable to Run WebStation on Windows Server 2008 Product Line TAC Vista Environment Vista Webstation 5.1.6 IIS ASP.net Cause IIS 7 and ASP.net must be installed before Vista Server in order for Webstation to function Resolution Uninstall Vista Server as outlined in How to uninstall and completely remove TAC Vista 5 Install IIS 7 and ASP.net Start the Server Manager Right-click Roles Click Add roles Select Web Server (IIS) In the following dialog click Add Required Features Click Next (twice) Select ASP.net In the following dialog click Add Required Role Services Click Next Click Install Install TAC Vista Server Install TAC Vista Webstation As administrator, Run the ASP.NET IIS Registration Tool (Aspnet_regiis.exe) for ASP.NET version 4.0 %SystemRoot%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i -enable 64-bit OS: %SystemRoot%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i -enable

Issue When you make a change to the Menta file and save that file back into Vista the changes are not available in Vista. An alarm appears stating ("Object does already exist " when expanding file in database) Product Line TAC Vista Environment Vista 5.1.7 Cause In some earlier versions of Vista, illegal characters were allowed to be entered in the Menta program specification name. Illegal characters in the program specification of a Menta file describes more on that problem. Resolution Rename the Menta program specification name. No more than 12 character and no spaces or illegal characters. Refer to Menta Warning: Syntax error for illegal characters which can not be used. Then generate the OP tree for the Menta application and save into the Vista database.

Issue Is it recommended to modify TGML Graphics from Remote Workstation? Product Line TAC Vista Environment TAC Remote Workstation TAC Graphics Editor Cause Remote Workstation should not be used as an engineering tool. It is used only to access the system. Resolution Remote Workstation's recommended use is to access the system.  Its function is not meant to be used as an engineering tool. It is possible to access the TGML Graphic pages from remote workstation to monitor and modify the objects not for editing Graphic Pages. You can prevent the access for TGML Graphics from Remote Workstation. For settings, please refer to Prevent a graphic page from being edited.

Issue Version incompatibility of Vista and Xbuilder generates an error. TAC XBuilder The installed TAC Vista version is not compatible with XBuilder 5.1.8 The XBuilder projects created will not be possible to use with the installed TAC Vista. Do you want to start XBuilder? Product Line TAC Vista Environment XBuilder versions compatible with Vista 5 Xenta 913 Xenta 527 Xenta 511 Cause Incompatibility of versions when XBuilder checks installed version of Vista 5. Resolution This error message is generated when launching XBuilder. XBuilder checks the installed version of Vista against its version and will generate an error if it is not the same. However, this is only an issue when the XBuilder is to be loaded into a Xenta Server. When using a NON-Xenta server i.e. a stand alone device that is simple passing values, this message can be ignored. Please refer to Xenta Server firmware versus Vista Server versions for the Xenta Server compatibility matrix with Vista Server.