Building Automation Knowledge Base

Issue IIS is a Microsoft product that is included on your typical Microsoft OS software but is not active by default. Product Line TAC Vista Environment Webstation Windows 7 Windows Vista Cause Webstation requires for IIS to be active in your OS before you complete the installation of Webstation. Resolution Follow these steps to initiate your IIS service in Windows 7 or Windows Vista. How to Activate IIS 7: To open the Windows Features dialog box, click Start, and then click Control Panel. In the Control Panel, click Programs. Click Turn Windows features on or off. You may receive the Windows Security warning. Click Allow to continue. The Windows Features dialog box is displayed. Expand Internet Information Services. Additional categories of IIS features are displayed. Select Internet Information Services to choose the default features for installation. Expand the additional categories displayed, and select any additional features you want to install, such as Web Management Tools. Click OK to start installation. The progress indicator appears. When the installation completes, the Windows Features dialog box closes, and the Control Panel is displayed. IIS 7 is now installed with a default configuration on Windows Vista or Windows 7. To confirm that the installation succeeded, type the following URL into your browser, http://localhost Use Internet Information Services Manager to manage and configure IIS. To open IIS Manager, click Start, type inetmgr in the Search Programs and Files box, and then press ENTER. See Problems installing Vista Webstation 5.1.5 or newer for more information on configuring Webstation.

Issue When attempting to edit a graphic through WorkStation, the Graphic Editor crashes with the following message: "Font xxxxxx does not support style xxxxxx" Product Line EcoStruxure Building Operation Environment Building Operation Graphics Editor Font Cause When a Graphic object is edited, the editor does not open and an error message is presented, this error is caused because the font is missing. Resolution Dependant on the Windows operating system in use, the process for confirming that the "Tahoma  Regular" font is missing will vary. Windows XP Open the Control Panel and select "Fonts" and confirm that the font is missing. Windows 7 Select the Windows button and then search for "Font". Choose "View Installed Fonts" and review the fonts to see if Tahoma - Regular is available. If this font is missing, then copy it from another PC, download it, or visit http://support.microsoft.com/kb/314960 which deals with adding / removing fonts. If Workstation is crashing when you see this error, please see WorkStation crashes when opening some TGML graphic pages following a Windows update.

Issue Get error message "OPC communication error" when trying to view Vista OPC server objects in OPC tool. Product Line TAC Vista Environment TAC Vista 5.1.X TAC Vista OPC server 1.6.1 Cause Incorrect version installed or DCOM settings. Resolution Confirm which version of Vista OPC server is installed. Go to control panel\add remove programs and double check that it is version 1.6.1. that is installed. Confirm that OPC server setup account settings aren't being saved. Go to Start\Programs\Schneider Electric\TAC Vista OPC server\Tac OPC Server setup. Under Login to TAC Vista server, change to Login using the following TAC Vista account and fill in the appropriate user details. Click OK and close the dialogue. Re-open the TAC OPC server setup dialogue and see if the account details added in b are still there. If so then there is probably a problem with DCOM settings (see TAC Vista OPC Server Technical Manual). If the option Login using the windows account which is running the TAC Vista OPC server is re-selected TAC Vista OPC server 1.6.0 must first be installed according to OPC server for TAC Vista will not keep the login settings in the TAC Vista OPC Server setup.

Issue There is a beeper inside some of the card readers. In some cases when alarms happen, such as Door Forced or Door Open Too Long, the beeper can be activated with a sound to deliver alarms. Product Line TAC INET Environment I/NET Cause In some cases this application is needed. Resolution Open the Door parameter in I/NET. Set the relative alarm message. For example, set the Door Open Too Long or Door Forced to Alarm.   Click the "Sounder" button Change the polarity to "Low". Set the relative beeper type and condition. For example, when the Door Open Too Long or Door Forced happens, the beeper activates continuously. For more issues about beeper in I/NET, refer to Reader beeps continually when connected to the door controller.

Issue When using the UI-8-10V for 0-10V analog input, the ElecValue of the input shows the half of the actually applied voltage. Product Line Andover Continuum Environment NetController: CX9900 , CX9940 , CX9680 IOU: UI8-10V (UI-8-10V) Cause UI8's 10V dip switch functions as the voltage divider. Resolution As the UI8's 10V dip switch functions as the voltage divider, it halves the 10V input voltage into 5V and uses it as the measured input. So, the ElecValue of the input shows the half of the actual input voltage. Note: When the input is configured for 10V operation, the input impedance is 4.4kΩs. Therefore, the sensor used would have to be able to source as much as 2.3mA. If input impedance is an issue for the sensor, then select the 5V input switch setting and use external resistors as detailed in How to use a 0-10V Sensor on a controller with 5V inputs.

Issue When executing a Find New BACnet Device a third party controller (Trane) would not come into the system.  Product Line Andover Continuum Environment Continuum BACnet Trane Cause BACnet Network ID was assigned to 1 in the third party device. Both the CyberStation Device node ID and the third party device Node Id can not be set to 1.  Resolution Have the vendor change the device node ID from 1 to a unique value on the network. See Could not learn in a new 3rd Party BACnet device.  

Issue Missing "restore" option when right-clicking on my Enterprise Server even though logged in as admin user. Product Line EcoStruxure Building Operation Environment SmartStruxure 1.3 and above Cause The admin user is member of multiple groups. The software permissions within that group have deny access set to Server Restore as well as other commands. Resolution Move the 'admin' (or Administrator) user to only be a member of the Administrator group and not any other groups otherwise you need to ensure that the correct permissions are set to each group and the correct users are assigned to those groups. For further detail of User Permissions in SmartStruxure Solution refer to following How software permissions work in SmartStruxure.

Issue WorkStation crashes when opening some TGML graphic pages following a windows update Product Line EcoStruxure Building Operation Environment Windows 7 64 bit SBO v1.6.1.5000 with KB3045171 windows update Cause Windows Security update KB3045171 can cause WorkStation to crash if some fonts have been used within the TGML graphic The example seen was using font "Dotum" Security Update for Windows 7 for x64-based Systems (KB3045171) http://support.microsoft.com/kb/3045171 If this does not resolve your issue see Graphics Editor will not open and causes a font related error. Resolution Microsoft have produced a fix for this problem (KB3065979) see https://support.microsoft.com/en-us/kb/3065979 The PC must be rebooted following this update before the problem is corrected.

Issue What is the Part Number for the optional battery for the JACE-NXT (TRD-NXT-R2)? Product Line TAC IA Series Environment I/A Series R2 JACE-NXT (TRD-NXT-R2) Cause An optional battery is required for the JACE-NXT (TRD-NXT-R2). Resolution The part number for the optional battery is TRD-NPB-BATT, per the Spec Data sheet for the JACE-NXT, F-27769. There is also an optional UPS that includes a battery, TRD-NXT-UPS, per Hardware platforms to replace the I/A Series R2 UNC-600 or UNC-610. See Product Announcement PA-00223 for further information on the JACE-NXT.   *Update - The NXT platform has been withdrawn. Refer to PA-00373 for details. 

Issue "No license for LonWorks communication" Error when starting Workstation. Product Line TAC Vista Environment Windows 2008 Server X64 TAC Vista 5.1.5 Cause Windows Server is member of a domain. Configure the TAC Vista Server to run as a service, with a local user set as administrator to logon. Results in "No license for LonWorks communication" when starting Workstation. If starting the service with a domain user or local system, it works.  Resolution Windows Security Policy This may have something to do with UAC (User Account Control) in Windows. The user that launches TAC Vista was already as a local administrator, but it seems that a log out with the user, log in with a local user, and log back in with a domain user is necessary for some policies to be set. Licensing Registry The Vista licensing requires registry information on where to find a license file. This registry key is found in the following location: HKEY_CURRENT_USER\Software\FLEXlm License Manager\TACLIC_LICENSE_FILE If the user has not been logged in and configured to run Vista software, this key might be missing or misconfigured. Ensure that it has a proper value by launching Vista Workstation or running the TAC License Setup. Log in with the user that will run the TACOS service and run the License Server Setup application to ensure the correct file path is defined in the Registry.   Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" error when using a non LE dongle "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" error message in Classic Network "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue Is there any way to get the Xenta Server trend log data without TAC Vista? How to get the Xenta Server trend log values from the web interface How to e-mail the Xenta Server trend log values Product Line Satchwell MicroNet, TAC Vista Environment TAC Xenta Server TAC Xenta 511, 527, 555 TAC Xenta 711, 731 Cause The TAC Xenta Server is installed standalone and TAC Vista can not be used to view or save the trend logs. However if you want to collect and store data from multiple trend logs on a regular basis we do strongly recommend using TAC Vista. Resolution There are two ways to get the trend log data from a Xenta Server (except for TAC Vista): 1. Manually copy the trend log values from the Xenta Server web interface In XBuilder, create a trend log page and drag the trend log to it Log in to the web interface and go to the trend log page Right click the trend log signal name and choose "view values" Copy/paste the values to for example Excel.   2. Forwarding the trend log data as an e-mail First make sure that the SMTP settings in XBuilder are correct. For troubleshooting on this, see Troubleshooting sending emails from a Xenta Server Create a receiver group and define one or more e-mail addresses to receive the trend log data. Highlight the trend log.  Under Log Data Transfer Settings, click the Receiver Group box, and select the Receiver Group list. In the Subject box, type a suitable subject. If desired, also type a suitable text in the Body box. In the Log Events Included box, click Yes to attach log events to the e-mail message. You must also specify when the log data is forwarded. For this, create a time object which you drag to the "send data" signal on the trend log. When the trend log data is forwarded, the receiver group e-mail addresses will receive the trendlog data as an attached .log file. For more information, see chapter 8.2.2. in the TAC Xenta Server – Web Server, Technical Manual

Issue AMT message stop coming through after re-installation of I/NET Product Line TAC INET Environment I/NET Seven all revisions. Cause If you re-install I/NET from a clean install.  That is you have uninstalled I/NET initially, AMT masking is cleared from the Host PC. Resolution Go to AMT Configuration (Edit > Configuration) Select the correct distribution group and mask settings for the site They must match the source points so that you receive the correct alarms and messages for that Host PC. For further information refer to TCON 299 - Chapter 6 "Message / Alarm and Printer Masks" If this still does not resolve your issue then refer to article AMT not receiving Data for additional items to check.

Issue When restoring I/NET database backup from another server in DBcreate, it shows an error: Error dropping PRIMARY KEY 'PK_DvrServers': Could not allocate space for object 'sys.sysserefs'.'clust' in database 'InetDb' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET SQL Server Cause Each SQL express version has its own database size limit. Refer to SQL and version compatibility for Filemaster, Equalized Client, Remote Client, Limitations of SQL. If the database size limit is reached, I/NET database will fail to update. The backup of the database will be fine, but when trying to restore onto another computer, it will also fail. Resolution 1. If the original I/NET server is still running, try to enable archive function to shrink the database in I/NET. And also follow Archiving and SQL database size keeps growing to set the database cap. 2. If the original I/NET server can't run, or the original database has been deleted, try to use SQL server version with higher size limit or full version SQL server which hasn't physical size limit. Like try to restore the backup from SQL 2005 Express (4GB limit) to SQL 2008 R2 Express (10 GB limit) or Full version of SQL 2005/2008. Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.

Issue Which stem heater should be used with V222 and V292? Product Line Field Devices Environment 8800112000 8800113000 Cause In some applications, a stem heater is required. Resolution For V222/V292, DN65-100, stem heater 8800112000 should be used. For V222/V292, DN125-150, stem heater 8800113000 should be used. For more information on stem heaters, see Stem heater for Forta actuator.

Issue When trying to view values in a Classic Network, "[No license for LonWorks communication]" message shows up in the Value tab and the alarm window. Product Line TAC Vista Environment Vista Classic Network Cause Though you are using Classic network, it's still using LON standards. You still need the license for TAC Vista Server. If the Server license is missing or invalid, you will get this kind of message. Resolution Check your license file and make sure you have the server license included. The server license should look something like listed below:  INCREMENT Vista.Server taclic 5.1 permanent 1 ISSUER=TAC \ If you do not have the line above, it means you do not have the proper license for TAC Vista server. Thus, you get the error message saying "No license for LonWorks communication."  The solution is to purchase the TAC Vista Server license, or use the demo license or an engineering dongle. Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" error when using a non LE dongle "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" Error in Windows 2008 Server X64 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue Site inquiring as to know the limit to how many workstations can be connected to a Continuum LAN system. Product Line Andover Continuum Environment Windows Server SQL Cause Site planning and architecture requires information on the limit of how many workstations can be connected to a Continuum LAN system. Resolution The Continuum LAN system itself has no real limit to how many workstations you can connect, but there are some limits to take into consideration. You can have up to 64 Workstations with ACC NET ID's between 191 - 254 which you will be able to setup to receive Continuum alarms. If the requirement is to have more than the 64 workstations allowed, you can add workstations after this limit but you will not be able to receive alarms and will need to set their ACC NET ID set to 0 If you add extra workstations you may also need to purchase additional Microsoft CAL (Client Access Licensing) licences for the Server and SQL which the database will reside on. For more information please see Microsoft Volume Licensing.  Also see Client Access License (CAL) for more detail about CAL. 

Issue Save time in the field by using the different functions Newron NL220 has to offer. This article contains some tips, tricks, suggestions and ideas. Product Line TAC IA Series, TAC Vista Environment NL220 Cause By not using all of the different tools within NL220 it can take much longer to complete a checkout of a database or resolve a problem. There are a number of shortcuts and hotkeys that can save a substantial amount of time. Some examples include database searches, browser window functions, filters, attaching documents, and meanings behind network menu options. Any addition questions or information can be found by contacting Newron here. Resolution Other Helpful NL220 Articles and PDFs NL220 Manual - Click here Starting a NL220 database - Click here Echelon LonMaker and Newron NL220 on 64-bit operating systems Ordering more LNS credits Ordering more Newron NL220 credits The difference between NL220I and NL220M dongles How to Rehost an NL220 Dongle to another PC LOYTEC NIC-USB in NL220 Creating LNS database in NL220 and transferring it into TAC Vista procedures outline Adding a Xenta Programmable Controller to an NL220 System Downloading new NXE or APB files using NL220   Searching the Database There are multiple ways to perform a search in the NL220 database depending on what is trying to be found. At the top of the NL220 window there is a search bar as seen above. The buttons found on this toolbar are defined below. When performing a search there are four different ways that a name can be searched. Using an asterisk after the name means that NL220 will search for anything that begins with those characters. Example: Name*   Using an asterisk before the name means that NL220 will search for anything that ends with those characters. Example: *Name   Using an asterisk before and after the name means that NL220 will search anything with those characters somewhere in the name. Example: *Name*   If no asterisks are used then NL220 will search for an exact match of those characters. Example: Name   General Toolbar The general toolbar at the top of the NL220 window has many useful shortcuts and features. Descriptions of some of these tools can be found below.    To use the automatic browser feature , the desired network variables must first be selected in the device templates. Select the template tab at the bottom of the database tree window.   Double click on the template that is desired for automatic browse. This example is using the 102-AX template.   Select the NVs tab in the device template settings window. Check the box in the browse column next to all network variables to include in automatic browse.   Click on the Subsystem tab  at the bottom of the database tree window.   Select the automatic browse button and click on a controller that is using the template that was modified. It will automatically open up the browse window with only those network variables.   Filter Toolbar The filter toolbar seen above is found at the top of the tree window. This toolbar contains the ability to look at nodes in a specific state like commissioned or uncommissioned, only display specific types of network variables, or even filter nodes and variables by name.    Network Functions Right clicking on objects in the tree window gives the pop up menu that contains the Network menu.  The functions of these icons are defined in the chart below.       Network Variables If changes have been made to the XIF file of a controller, the change needs to be applied to the network variables of the application devices that use the template. Click on the Templates tab at the bottom of the tree window. Right click on the template that needs to updated and select "Rename variables of all application devices" A prompt will open that says "Do you want to rename all network variables of the application devices with the template name?". By clicking yes, this will rename all of the network variables of the devices that reference this template to match the names found in the template. Note: Once this has been completed double check the SNVT connections that have been created already. After the rename, it may change the SNVT order if a SNVT was renamed or removed  from the programming. This will cause connections to be binding the wrong variables together.   Creating a New Device Template If adding a new device to the database, a new device template may need to be created. See Adding a Xenta Programmable Controller to an NL220 System for instruction on how to add a Xenta programmable controller to a NL220 system. Click on the Templates tab at the bottom of the tree window. Right click anywhere in the Templates pane and click on "New device template..." In the New device template box, enter the name of the new template and browse the XIF file into the "Description file" box.    

Issue When attempting to update Vista Database in Vista System Plug-In, there is a failure producing the error  "Update Vista database failed". Product Line TAC Vista Environment NL220 LonMaker Vista System Plug-In Cause There are multiple causes for this error including LonWorks Network name not matching, signal names in Menta have too many characters, the use of an invalid alarm controller object in a Menta alarm block, and orphaned/unnecessary constants left in the Menta constants table. Resolution LonWorks Network name does not match If the LonWorks Network name in vista does not match the name in the system plug-in then the update will fail. In Workstation, right click on the LNS Network object Rename the LonWorks Network to match the name in the LNS side of the Vista System Plug-In. *If this occurs during the addition of a LNS port into a Vista database with an existing LNS port, ensure each LNS port is using a unique name. Insufficient Vista user account privilege An update to the Vista database cannot be performed if not logged in with an administrator level user account. Too many characters in a Menta point name If there is a signal name that is longer than 20 characters it can cause the Menta file to fail to update to the Vista server. Invalid alarm controller object If there is a Menta alarm block that is referencing an alarm controller object using a $ (other than the default $Alr_Cntrl) it can cause the update to fail. TAC Vista will try to add the object even though objects with $ can not be added. Orphaned or Unnecessary constants For more information on this cause and how to correct it, see Updating the Vista Database fails when trying to transfer a specific MTA object.

Issue Transitioning from Continuum to Struxureware Building Operation and replacing bCX's with Automation Servers.   Product Line Andover Continuum, EcoStruxure Building Operation Environment b3865 Struxureware Building Operation Cause Unsure if the older belimo style VAV controllers are compatible with StruxureWare Building Operation. Resolution All of the b3xxx controllers (including both the -V and non -V) will work with the Automation Server under it's MSTP network. Also check out the b3 VAV Quick Start Video on the Community.

Issue Is it possible to get a XIF from Lonmaker when you have commissioned it by "upload" from device? Product Line TAC Vista Environment TAC Vista Toolpack TAC Vista Server LonMaker Cause If you don't have the XIF you can upload from the device in Lonmaker. Resolution There is no way to get the XIF from LonMaker but the system plug-in will create a new XIF when you add the device to the TAC Vista db. Refer to SNVTs, SCPTs, or Module Names are missing from Vista after device is added to database from System Plug-in. Compare XIF stored in Vista for instructions on how to locate the XIF generated by the system plugin.