Building Automation Knowledge Base

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.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue StruxureWare Building Operation Extended trend logs have an incorrect unit associated with the measured value. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.3.x Cause It is possible to create extended trend logs by selecting multiple trend logs and using the right click option to create extended trend logs. The software incorrectly associates all of the created trend logs with the first trend log object's associated unit even if the other trend logs in the selection use different units. Resolution The cause of the problem is resolved in a forthcoming release (1.4.0) however if the system is in the state currently additional steps must be taken. The method to resolve this problem depends on the need to maintain the existing extended trend log data or not. 1. Accept loss of data Delete the extended trend logs that have incorrect units and create each extended trend log individually and avoid multiple selections. 2. Avoid loss of data Export the trend logs in StruxureWare Workstation. Modify the export file and edit the unit value for the Extended trend log The unit will need to be validated with another export that contains an object of the correct unit type. Example of Units % - 0x200001 F - 0x280003 no unit - 0x10001 inH20 - 0x230005 ppm - 0x200002 kW - 0x3210001 Import the modified file and when it detects a naming conflict allow it to rename the Trend log with a "2" notification. Stop the data collection on the original trend logs and once the retention levels of the new trend logs meets your site requirements delete the old trend logs with the incorrect data. Please be aware this issue could impact meter reports from WebReports detailed in Energy Reports not working in 1.3 and earlier

Issue Animations, gifs, updating values, hover overs or mouse event scripts work in Workstation but do not work in Webstation. Product Line TAC Vista Environment Vista Webstation TGML graphics   Dynamic values       Cause Various reasons can cause TGML graphics to not function the same in TAC Vista Webstation as in Workstation. Typical reasons can be: Using "Static TGML viewer" vs. "Dynamic TGML viewer". Under Static view, all animations are prohibited. Using unsupported script functions can cause animation to not work in Webstation. Sizes and the number of animated .GIF images used on a single TGML graphic page. Resolution Check if the Webstation is running under Dynamics view. Go to Start->All Programs->Schneider Electric->TAC Vista Web Applications -> Vista Web Setting. (For Vista 5.1.3 or prior, go to Start->All Programs->TAC->TAC Vista Web Applications -> Vista Web Setting instead.) Click on "Graphics/TGML Views" in the left panel. Make sure the TGML View is either “AutoDetect” or “Dynamics” in the right panel.  If it is “Static”, click on the drop down manual and choose a different display viewer.   Check if using any unsupported Java script. Please reference Vista Webstation unsupported TGML functions for more information.   If a TGML graphic page contains many animated GIF images, it can cause the animation on that graphic page to run slow, discontinuously, or not run at all.  The amount of animated GIF images that can be put on one single TGML graphic page various case by case. Therefore, the best way to test it is deleting all animated GIF images and add them back on one by one.

Issue Upgrading from older Continuum version using parallel dongle. Product Line Andover Continuum Environment CyberStation Cause The old style hardware key cannot be attached to newer machine that do not have a parallel port. Resolution It is not necessary to have a hardware key plugged into Continuum workstation pc when the c2v file is created.   If you are able to read the key information and/or identify the serial number for the existing key, contact the EcoBuilding upgrade department at Upgrades.Continuum@schneider-electric.com and provide them with the serial number of the hardware key and a c2v file that was generated on the Continuum workstation. If you are unable to read the key information or identify the S/N from the old dongle, contact the EcoBuilding upgrade department at Upgrades.Continuum@schneider-electric.com. It may become necessary to sent the hardware key to the EcoBuilding Upgrade Dept to so that they can extract the serial number and key information themselves.   See also Software Licensing for Continuum 2.0 and StruxureWare Solution.

Issue When deploying Automation Server or Enterprise Server from Workstation for Projects under PCS, it will fail. The error shown in the Progress view window is "The live server is not empty." Product Line EcoStruxure Building Operation Environment SmartStruxure Project Configuration Server Workstation for Projects Enterprise Server (ES) Automation Server (AS) Cause A project can only be deployed to a server when the server has an empty database and not has been part of a multi-server system. A server is considered empty when it does not contain any user-created objects, such as programs and graphics. Resolution The server database can be emptied in different ways depending on if it is an Automation Server or an Enterprise Server: Reinstall the Enterprise Server. Upgrade the Automation Server with a new database. For more detail about how to deploy AS or ES, refer to Offline Engineering with Project Configuration Server (PCS).

Issue What does it mean on an MNL-800 if both the top green LED (Transmit) and the Amber LED (Receive) are on continuously? Product Line TAC IA Series Environment MNL-50 MNL-100 MNL-200 MNL-800 MNL-V1R MNL-V2R MNL-V3R Cause LEDs indicate LON traffic on the trunk Resolution For an explanation of the Transmit (Green LED) and Receive (Red LED) see F-26724, MNL-800 Installation Instructions, Table 1 LED Indications: LED Operation Status Green ON Normally ON indicating controller is powered and not actively transmitting data on the LON. Flashes OFF Flashes OFF while actively transmitting data on the LON. Amber OFF Normally OFF unless actively receiving data from the LON. Flashes ON Flashes ON while actively receiving data from the LON. Red OFF  (Neuron - normal communications) indicates the Neuron is operating properly allowing normal communications to and from the HVAC application. OFF  (Neuron - Offline) Neuron responds to network management messages only. In this state, communication to and from the HVAC application is not possible. To correct, place the Neuron online by downloading an application using WP Tech or configure using a third party management tool. Blinking The service LED blinks at 0.5 Hz rate (1 second ON, 1 second OFF) to indicate that the Neuron is unconfigured (i.e. communications parameters not loaded). Corrective action: Configure the Neuron by downloading an application using the Work Place Technician's Tool or configure the neuron using a third party management tool. ON Indicates Neuron is not operating properly. Replace controller.  Heartbeat (Green LED) Blinking (Normal Operation) The heartbeat LED blinks at 0.5 second ON, 0.5 second OFF to indicate controller is operating properly. Wink Mode Wink mode provides a visual means for identifying the controller using WP Tech or third party management tool. During wink, the heartbeat LED blinks as follows: With revision 1.x firmware: 2 seconds ON, 0.5 seconds OFF; cycles five times for a total of 12.5 seconds of wink time. With revision 2.x (or later) firmware: 3 seconds ON, 1 second OFF; cycles three times for a total of 12 seconds wink time. Diagnostic Blink (RAM/ROM Failure) The heartbeat LED repeats a pattern of 2 quick flashes followed by pause. To correct, turn power OFF then ON. Replace controller if necessary. Diagnostic Blink (ROM Failure) The heartbeat LED repeats a pattern of three quick flashes followed by a pause. To correct, turn power OFF then ON. Replace controller if necessary. Diagnostic Blink  (RAM Failure) The heartbeat LED repeats a pattern of four quick flashes followed by a pause. To correct, turn power OFF then ON. Replace controller if necessary. OFF Indicates controller is not operating properly. Check power. Replace controller if necessary.      If the amber LED is blinking fast enough, it appears to be ON continuously, so it is receiving data at a high frequency. The other MNL devices on the same LON should all be behaving the same way, indicating a lot of LON traffic. Confirm with a LON protocol analyzer. If excessive LON communications traffic is suspected, see How can LON communications be throttled in MNL-800 controllers? for a method of throttling LON traffic.

Issue The reason for TAC dummy nodes and the logic behind the number of dummy nodes created. Product Line TAC Vista Environment Vista NL220 LonMaker TAC Vista System Plug-In Cause TAC dummy nodes are added to Xenta groups automatically in the LNS network. The dummies are made after group bindings have been created. Resolution The TAC dummy nodes are created when group bindings are made. For more information about group bindings see Verifying Xenta Group Bindings in an LNS system. Vista requires that the TAC Group and the TAC Xenta group differ in the number of devices. If you only have one Xenta group in your system, TAC Vista System Plug-In will create a dummy device and use its tag_0 (also first row of the address table) in the group binding for the TAC Group. This will allow Vista to differentiate between the TAC and Xenta groups. Notice that in both LonMaker and NL220, this dummy node that is created to represent a second Xenta group appears to be located in the same Xenta Group as the rest of the controllers. This is fine, the system plug-in is not going to create a new group to put it in, just realize why the dummy node is there. Modules do not count in the group bindings therefore the example below only has three devices in Xenta group 1.   Xenta Groups must consist of at least three Xenta devices. If you only have two Xentas in a Xenta group, TAC Vista System Plug-In will also use a dummy device, since a binding between just two devices is not considered a group binding. To create a group binding, a third device is needed. Consequently, you will need two dummy devices if you only have one Xenta in your Xenta group. Thus, if just one Xenta device exists in a single Xenta group, three dummy devices will be needed: one to separate the TAC group binding from the Xenta group binding and two more to form a Xenta group.

Issue Satchwell “AL..S” series Spring Return Linear Actuator requires replacement Product Line Field Devices Environment Satchwell “AL..S” series Spring Return Linear Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body. Actuator type :- AL..S series. Cause Obsolescence of Satchwell AL..S series Spring Return Linear Actuator. Resolution Replace Satchwell AL..S series Spring Return Linear Actuator with S-E M700 Spring Return Linear Actuator and Linkage Kit : AL..S = M700 + L7SV (880-0126-000) Linkage Kit. N.B. M700 is available with two different spring return actions M700 - SRSU (880-0430-000) = Spring Return Spring Up          ( M700 - SRSU will CLOSE a Satchwell Valve.) M700 - SRSD (880-0440-000) = Spring Return Spring Down     ( M700 - SRSD will OPEN a Satchwell Valve.) Should the Satchwell AL..S series Actuator include a wired Auxiliary Switch then the following S-E M700 Actuator specifications which include 2 independent 24 volt 4 amp AC-1 rated SPDT Auxiliary End Point Switches should be considered as appropriate: M700 - S2 - SRSU (880-0431-000) M700 - S2 - SRSD (880-0441-000) Alternatively Auxiliary Switch Pack S2 (880-0104-000) - Two independent 24 volt 4 amp AC-1 rated SPDT Auxiliary End Point Switches may be purchased separately permitting local installation.  Particular care should be taken when selecting a TAC Forta M700 Spring Return Actuator to replace an existing Satchwell ALMS, ALXS or ALES Spring Return Actuator.  Please refer to Replacement of Satchwell "AL..S" series Spring Return Linear Actuator by S-E M700 Spring Return Linear Actuator due to obsolescence.(Actuator Wiring). Please check the latest catalog for current equipment.

Issue A 7791 is used specifically for what? Product Line TAC INET Environment I/NET Site Cause A 7791 is used on security/access control installations. Resolution It is the interface for Door Processing Units (DPUs). (TCON209, 1-20) TCON Number and Title Cross Reference (with links) is TCON information. Explain and define I/NET Ethernet, C-LAN, and Sub-LAN communication is a chart to explain further.