Building Automation Knowledge Base

Issue "No license for LonWorks communication" - LonMaker Recovery Folder Product Line TAC Vista Environment Echelon LonMaker Cause Vista software detects the installation of commissioning tool for the LonWorks communication license. At times LonMaker will improperly shut down and store bad data in the Lm\Db\Database name\recovery folder. This invalid data will stop the LNS server from running properly. Resolution If using LonMaker and "No License for LonWorks Communication" error message appears: Shut down Vista software Open the drawing in LonMaker If it requests the contents of the recovery folder be removed, follow those instructions. Once the contents of the recovery folder are removed, open the drawing in LonMaker Launch Vista Server, and the license problem should be gone.  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" error message in Classic Network "No license for LonWorks communication" Error in Windows 2008 Server X64 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue Webpages were able to be viewed from controllers in the past but no longer work. The controller can be pinged which indicates that it is online. Product Line Andover Continuum Environment B4920 BCX 99xx Windows OS Cause If running the latest versions of Microsoft Office, there are a lot of extensions installed in the registry under accepted documents which create a very long string for a HTTP request. Resolution In a test environment, Microsoft Office suite 2007 was installed for testing. Webpages could be opened from the bcx and 9702 controllers but not from the b4920 or webpages on a 9900. The latest Microsoft Office packages added a few accepted document extensions that allow things like word docs and spreadsheets to be opened in Internet Explorer. If the extensions are removed, the docs and xls files can still be downloaded and can be opened locally instead of through the browser. The TCP streams below show the different http request. Request with latest extensions: GET / HTTP/1.1 Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, application/xaml+xml, application/vnd.ms-xpsdocument, application/x-ms-xbap, application/x-ms-application, */* Request with default extension: GET / HTTP/1.1 Accept: */* If running the latest versions of Microsoft Office, there are a lot of extensions installed in the registry under accepted documents which creates a very long string for a HTTP request. In order to work around this, you can edit the registry. Editing of the registry should be done with extreme caution. Be sure to export a copy of your registry. Look under the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Accepted Documents Then you can export all of the keys under the above location and delete all but the default key. Once this has been done, restart your browser and you should be able to open your controller's webpages.

Issue How to use a digital point card with a Network 8000 MicroZone II controller. Product Line TAC IA Series Environment Network 8000 MicroZone II controller Digital Point Card Cause To use the digital input cards (DPC-3-1 & DPC-3-2) with a MicroZone II controller, it requires a custom application file. Resolution The MicroZone II controller supports two digital input cards:  DPC-3-1 & DPC-3-2. A custom application file (1-DPC3.MZ2) is required to properly read the digital input card, review technical bulletin TB01-26 for more details. (Note: The DPC-5 series cards were designed for the MNL and MNB controllers.  They are compatible with the DUI Expander Object available for both controller lines.)

Issue WorkPlace Tech Tool menu functions and toolbar icons do not respond when selected even though they are visible (not grayed out) after changes are made to the Visio Menus or Toolbars. Product Line TAC IA Series Environment I/A Series WorkPlace Tech Tool software Cause Some COM add-ins are not compatible with the WorkPlace Tech Tool software. Resolution From the Visio menu, within WorkPlace Tech, select Tools / Customize then select the Toolbars tab. Select each checked toolbar in turn, clicking the reset button for each one. Next select the Options tab and click the "Reset menu & toolbar usage data" button. If this does not correct the issue, disable the COM add-ins and delete the Visio directory cache using the procedure listed below. The procedure depends on the version of Visio and the version of Windows being used. WorkPlace Tech with Visio 2007 Open Visio 2007 Open the Tools Pull down. Select the Options. Select the Trust Center Select Add-ins. Verify that the box "Disable all Application Add-ins" is NOT checked. At the bottom of the screen, COM Add-ins is the default selection. Press GO. In the COM Add-ins box displayed, un-check the box for the ",Send to Bluetooth", and any other third party add-ins. Click OK to apply. Close Visio 2007 Delete the Visio Directory Cache file, as follows, depending on the version of Windows. If running Windows Vista or Windows 7, delete the file c:\Users\< username> \AppData\Local\Microsoft\Visio\content12.dat If running Windows XP, delete the file c:\Documents and Settings\< username> \Local Settings\Application Data\Microsoft\Visio\content12.dat Open Visio 2007 and wait for the "Getting Started with Microsoft Visio" window to be displayed. Close Visio 2007. Open WorkPlace Tech, all menu items should be there. If some or all of the WorkPlace Tech Tool menu entries are still grayed out, repeat these steps, disabling all COM add-ins. Workplace Tech with Visio 2003 Open Visio 2003 Open the Tools menu. Select Options, then Security. Un-check the box for COM add-ins. Check the box for "Enable Microsoft Visual Basic for Applications". Check the box for "Enable Automation events" Click OK to apply. Close Visio 2003. Delete the Visio Directory Cache file, as follows, depending on the version of Windows. If running Windows Vista or Windows 7, delete the file c:\Users\< username> \AppData\Local\Microsoft\Visio\content.dat If running Windows XP, delete the file c:\Documents and Settings\< username> \Local Settings\Application Data\Microsoft\Visio\content.dat Open Visio 2003 and wait for the "Choose Drawing Type" window to be displayed. Close Visio 2003 Open WPT, all menu items should be there. Workplace Tech with Visio 2002 Open Visio 2002 Open the Tools menu. Select Options, then Advanced. Un-check the box for COM add-ins. Check the box for "Enable Microsoft Visual Basic for Applications". Check the box for "Enable Automation events" Click OK to apply. Close Visio 2002. Delete the Visio Directory Cache file, as follows, depending on the version of Windows. If running Windows Vista, delete the file c:\Users\< username> \AppData\Local\Microsoft\Visio\VISIO.BIN If running Windows XP, delete the file c:\Documents and Settings\< username> \Local Settings\Application Data\Microsoft\Visio\VISIO.BIN Open Visio 2002 and wait while Visio updates its directory cache. The process is complete when the "Choose Drawing Type" window is displayed. Close Visio 2002 Open WPT, all menu items should be there.

Issue When importing an application file created or previously edited with release 3.2sp1 of WorkPlace Tech, a "Workplace Tech Tool - Visio" error window is displayed:  "Cannot find the WorkPlace Tech add-ons for Visio.  WorkPlace Tech functions will be unavailable" Product Line TAC IA Series Environment WorkPlace Tech Tool software release 5.7.4 WorkPlace Tech application file created or edited with WorkPlace Tech Tool software release 3.2sp1. Cause The Visio stencil pages referenced in the application file cannot be found in the location specified in the application file. Resolution This is not a fatal error.  It occurs because WorkPlace Tech cannot locate the Visio object stencil files referenced in the existing application drawing file.   Click the [OK] button to ignore the error message and continue with the application file upgrade.  The error message is displayed because the default location for the stencils has been moved starting with WorkPlace Tech version 5.7.4.  During the application file upgrade, the proper stencils, as specified in the original application file, will be located and attached to the application. After clicking the [OK] button, WorkPlace Tech will display a Windows message box indicating that the application must be converted to WorkPlace Tech (WPT) 5.0 format before it can be modified or downloaded.  The message ends with a prompt asking the user if they would like the application converted.  Clicking [Yes] will allow WorkPlace Tech to process the application file and convert it to the current file format.  This is the required choice if the user intends to use the imported application in the current version of the WorkPlace Tech Tool software. Clicking [No] will bypass the conversion leaving the incompatible application open in WorkPlace Tech. Clicking [Cancel] will abort the import process.

Issue These errors are internal to Echelon LonMaker and require the assistance of Echelon Technical Support. Environment LNS LonMaker Vista NL220 LonSupport@Echelon.com 1-800-258-4LON or 1-800-258-4566 Cause NS #9 lcaErrNsBadClient NS #11 lcaErrNsNoClient NS #14 lcaErrNsClientBlocked NS #16 lcaErrNsNotImplemented NS #18 lcaErrNsServiceFailure NS #20 lcaErrNsPrematureRelease NS #21 lcaErrNsRootBus NS #22 lcaErrNsRootDoesNotExist NS #23 lcaErrNsNoFreeRootTransactions NS #30 lcaErrNsEventFailure NS #32 lcaErrNsSubscriptionDblimit NS #34 lcaErrNsSegmentation NS #41 lcaErrNsDbError NS #42 lcaErrNsOutOfJournal NS #46 lcaErrNsNetworkHasInstalledNodes NS #49 lcaErrNsIntegrityError NS #55 lcaErrNsProgramDblimit NS #57 lcaErrNsNvmtDbLimit NS #61 lcaErrNsMsgError NS #62 lcaErrNsCancelError NS #71 lcaErrNsTimerRange NS #83 lcaErrNsObjectLocked NS #84 lcaErrNsInvalidContext NS #85 lcaErrNsServerNotFound NS #109 lcaErrNsStaleFileHandle NS #115 lcaErrNsManagerNotAllowed NS #126 lcaErrNsUnimplementedCategory NS #127 lcaErrNsUnimplementedProperty NS #128 lcaErrNsDisallowedInMipMode NS #129 lcaErrNsDisallowedInTxHandler NS #130 lcaErrNsNssNotInitialized NS #146 lcaErrNsInvalidErrorContext NS #151 lcaErrNsBatchOptionNotImplemented NS #152 lcaErrNsBatchNoResult NS #172 lcaErrNsEngineNotInitialized NS #189 lcaErrNs16BitUserErrorCode NS #190 lcaErrNs16BitWarningCode NS #191 lcaErrNs16BitErrorCode NS #289 lcaErrNsEngineIsSuspended NS #290 lcaErrNsNotSupportedFromRemoteClient NS #4031 lcaErrNsUpdateFuncError NI #24 lcaErrNiObsolete NI #27 lcaErrNiUnimplemented LNS #5 lcaErrUninitializedDb LNS #35 lcaErrGeneric LNS #36 lcaErrDbServer LNS #39 lcaErrWrongWriteDataSize LNS #40 lcaErrInvalidFormat LNS #54 lcaErrCantCopyLNSDirectory LNS #70 lcaErrCantRecoverReadOnlyFile LNS #71 lcaErrStringIsEmpty LNS #73 lcaErrInvalidProgramType LNS #97 lcaErrInvalidRmcObject LNS #98 lcaErrInvalidRmcServer LNS #99 lcaErrInvalidRmcClient LNS #101 lcaErrInvalidRmcMethod LNS #123 lcaErrInvalidPropChangeEvent LNS #133 lcaErrInternalErrBadExceptionCode LNS #134 lcaErrInternalErrBadHresultExceptionCode LNS #135 lcaErrInternalErrBadVNIDataServer LNS #136 lcaErrInternalErrBadNsdHandle LNS #137 lcaErrInternalErrStartTransaction DS #365 lcaErrLnsDsUnexpected DS #366 lcaErrLnsDsFailed Resolution These are internal errors and should be reported to Echelon's customer support. Contact Echelon at 1-800-258-4LON (258-4566) or LonSupport@Echelon.com.

Issue 5.1.5 is now packaged into two different spanned archives because of how large the installer files have become. At this point there is a 300 MB file limit on exchange online and the 5.1.5 installer package is now 336 MB, hence the reason the installation package had to be split into two archives. Because the installation package is a spanned archive it will need to be opened with WinZip or a compatible archive program. In these instructions we will be downloading and installing WinRar to open the installation archives. Note 1: WinRar is technically not free software, but it does allow its demo license to extend on past the demo period. It is at the customer’s discretion on what legal and compatible archiving software they chose to use. Note 2: The built in zip archive program in Windows 7 will open this spanned archives without fail. Product Line TAC Vista Environment Vista 5.1.5 software download on any operating system older than Windows 7 Cause File limit set on exchange online and the built in .Zip extractors in older operating systems do not have the capabilities to open these spanned archives. Resolution Create a folder on your local C: drive and name it 5.1.5 To download and install WinRar please visit http://www.rarlabs.com/download.htm and find the appropriate version. If you would like to use Winzip instead, please visit http://www.winzip.com/win/en/downwz.htm to download and install the appropriate version Navigate to exchange online at Download Center login, and click the links Product > TAC Vista > Vista Software > TAC Vista 5.1.5 > Downloads Click the file named TAC Vista Server 5.1.5 with Workstation (File 1 of 2) and save. Save the file to the 5.1.5 folder created in step 1. Click the file named TAC Vista Server 5.1.5 with Workstation (File 2 of 2) and save. Save the file to the 5.1.5 folder created in step 1. Allow the downloads to finish and navigate to the location of the 5.1.5 folder. Right click on the file named TACVistaServer515.zip and select Open With > WinRar archiver WinRar should open the archive file and you can now double click and run the TACVistaServer515.exe file within it. This exe file will access the other file (TACVistaServer515.z01) within the 5.1.5 folder automatically during the install process.

Issue ARCNET Cable Requirements. Product Line Satchwell Sigma Environment Sigma 4.05 and earlier versions V53 and ARM7 Processor Boards Cause Sigma ARCNET Network cabling advice. Resolution The following Sigma Cabling Guide should be followed when installing an ARCNET network for Sigma:  Sigma Cabling Guide 2.2 Network biasing and earthing arrangements will be required and further information about cabling can be found in the following guides: For V53 Processor Boards (UNC496, 596, UNC532, DNN and IC integration controllers): Sigma Configuration Guide - Chapter 26a For ARM7 Processor Boards (UNC696, 796 & UNC632): Sigma Configuration Guide - Chapter 32; Sigma Configuration Guide - Chapter 31 For ARM7 Processor Boards (DNN3 Decentralised Network Node): Sigma Configuration Guide - Chapter 33 For ARM7 Processor Boards (IC3 Integration Controller): Sigma Configuration Guide - Chapter 34

Issue 1. What is the specification (spec) for a Sigma PC?  2. Do I need to use Windows XP SP3 with Sigma? Product Line Satchwell Sigma Environment Sigma Software Cause Minimum requirements for a Sigma PC. Resolution The highest PC specification should always be sought.   See the Download Center for the release note appertaining to the Sigma version in use. The release note will detail the minimum PC required and Windows version no. that can be used. For EBO transitions and Windows 10 compatibility, see the KB article Sigma and Windows 10 compatibility.

Issue The text on the prog object does change but the graphic does not show the same change. Environment Sigma all versions BAS all versions Cause Controller only update server graphics when the object changes state or exceeds the set tolerance.  If prog objects are written with the same condition but different texts in the return statements then the correct text may not be displayed until the whole graphic is updated.  For example 10 If P0|1 on then return true "Object 1 on" 20 if P0|2 on then return true "Object 2 on" 30 if p0|3 on then return true "Object 3 On" Resolution Write the programmable object to that will change state to update the graphic.  This may well have to be a dedicated object for the graphic.  For example using a time statement to check for a change; 10 if not time left then goto 50 20 If P0|1 on then return true "Object 1 on" 30 if P0|2 on then return true "Object 2 on" 40 if p0|3 on then return true "Object 3 on" 50 set timer 10 60 If P0|1 on then return false "Object 1 on" 70 if P0|2 on then return false "Object 2 on" 80 if p0|3 on then return false "Object 3 on"

Issue There are a number of object tabs that support the functionality of exporting to a CSV file. Can this CSV file then be used as a template and imported into another site? Product Line EcoStruxure Security Expert Environment Security Expert Cause Not sure how to import objects from CSV as a database creation tool. Resolution The export options are so you can export the required records to a file as part of site documentation, administration etc. There is no way to import anything other than users using a CSV file. A database backup that is already configured can be restored to a new system to be used as a site template. Another option for using the same configuration is the Copy Controller Feature. If you want to have multiple sites within a single Security Expert Server, take a bank for example where each branch is a separate site in the one server but configured pretty much the same, you could utilize the Copy Controller feature to copy all the programming from the template controller to a new one. Please note that although this feature currently exists within Security Expert it is currently being worked on by our engineers to improve its functionality.

Issue After installing the Niagara AX Serial Tunnel client, the service fails to start and Windows displays the following error: Could not start the NiagaraAX Serial Tunnel service on the Local Computer. Error 1068: The dependency service or group failed to start. Product Line TAC IA Series Environment I/A Series G3 ENC I/A Series G3 Enterprise Server Microsoft Windows operating systems (any) Cause The selected, virtual COM port is in use by another application or is in conflict with another service running on the Windows host computer. Resolution Modify the COM port used by the Serial Tunnel Client. On the Windows host, go to Control Panel and double-click Niagara AX Serial Tunneling. Change the Serial Port to another selection that is not being used by other applications or services and click OK (see below). Reboot the computer

Issue Satchwell ALM series Linear Actuator requires replacement. Environment Satchwell ALM series Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF Series Plug and Seat Valve Body.    Satchwell ALM series Linear Actuators. Cause Obsolescence of Satchwell ALM series Linear Actuator. Resolution Replace Satchwell ALM series Linear Actuator with MV15B-230 Linear Actuator and Linkage Kit and wire as follows :- ALM = MV15B-230 + L7SV (880-0126-000) Linkage Kit. Actuator wiring :- ALM Terminal Number 1  =  MV15B-230 Terminal Number Y2  ALM Terminal Number 2  =  MV15B-230 Terminal Number Y1  ALM Terminal Number 3  =  MV15B-230 Terminal Number N N.B. ALM power consumption  =  4.5 VA          MV15B-230 power consumption  =  12 VA operating and 15 VA Transformer sizing Should the Satchwell ALM series Actuator include a wired Auxiliary Switch (ALA1211) then the following Accessory should also be installed on the MV15B-230 Actuator as appropriate and should be wired as follows :- S2 - MV15B = Two independent 250 volt 10 amp / 3 amp rated SPDT Auxiliary End Point Switches. Auxiliary Switch wiring :- ALA1211 Terminal S1  =  S2 - MV15B Switch 1 Terminal C ALA1211 Terminal S2  =  S2 - MV15B Switch 1 Terminal B ALA1211 Terminal S3  =  S2 - MV15B Switch 1 Terminal A ALA1211 Terminal S4  =  S2 - MV15B Switch 2 Terminal C ALA1211 Terminal S5  =  S2 - MV15B Switch 2 Terminal B ALA1211 Terminal S6  =  S2 - MV15B Switch 2 Terminal A   Please check the latest catalog for current equipment.  

Issue Configuring and monitoring the Xenta 102-AX is traditionally done through the LNS Xenta 102-AX Plug-In, but how can it be done in a Vista Classic Network where no LNS plug-ins are available? Environment Vista 5 Classic Network TGML Xenta 102-AX Vista Workstation ONLY -- This plug-in is not compatible with Webstation or XBuilder graphics at this time. Cause LNS Plug-ins are not available in a Vista Classic Network. Resolution All of the values that are written to by the LNS Plug-In are public and available through the Vista front end. So if only one or two signals need to be set for each box, this can be accomplished by locating them in the Vista network and writing the desired values to them.  This does require some fairly intimate knowledge of the Xenta 102-AX and Plug-In. The alternative is: Download the Xenta 102-AX TGML Plug-in by clicking the image below.  Unzip the contents to the hard drive. Open the TGML file. Select File > Save As > Vista Database Object Navigate to the first Xenta 102-AX in the network. Drill down into the 102-AX on the same level with Node_Object and VAV_Controller modules. Give the plug-in graphic a name and save. Right click on the Graphic object in Vista Workstation and select Copy Navigate to the next Xenta 102-AX and select Paste Shortcut. Since all bindings are automatically populated with relative bindings, copying and pasting shortcuts will automatically display data for the associated Xenta 102-AX. Repeat Step 8 for all Xenta 102-AXs in the network.

Issue Unable to utilize auxiliary contact on SE7000 Product Line EcoStruxure Building Expert Environment   SE7000 Cause Misunderstanding of wiring and configuration steps for the auxiliary output Resolution SE7600 The Aux contact will provide 24 Vac to end devices such as; exhaust fans, valves, economizers, pumps…The contact will operate in conjunction with occupancy command of the thermostat. SE7200 | SE7300 The auxiliary output on terminal BO5 terminal 6 and BO5 terminal 7 is a dry contact that require 24 Vac loop to operate. The output will operate accordingly to configuration and control end devices. Auxiliary contact function and configuration

Issue Would like to change the default Event Description displayed under Monitoring | Status Page View.  Product Line EcoStruxure Security Expert Environment Security Expert Server Cause Would like to customize Event messages by adding or removing text from the Description field for specific Events. Resolution Unfortunately we are unable to modify any Event Description. Changing, or adding to, the event text is not an option. A couple of alternatives could be: Add a descriptive Instruction to an Alarm that you are filtering (with an Alarm Filter) for raw data events and then monitoring the Alarms feed, instead of the Events feed, for those messages. Setup an "Action" to single out and email those specific Events that you want to see.

Issue Xenta 700 System Report shows "Menta: IO error (Error#:62464) Environment Xenta 700, 701, 711, 721, 731 Cause Some of the causes could be following: Might be configured to use wrong I/O Modules Wrong Neuron ID configured Menta program issues Resolution To resolve this error, check the following: Upgrade Xenta Firmware with Latest Version from the Exchange Extranet. Ensure correct I/O modules are configured. Ensure all the controllers and I/O modules are online.

Issue How to generate an invalid attempt alarm. Product Line Security Expert Environment Security Expert Cause It is not clear how an alarm for an invalid attempt at a Door is configured. Resolution The easiest way to setup an alarm to trigger when an invalid attempt is made at a reader is to trigger an Alarm off of the required Event. An example would be: Under Events create a new Event Filter, go to Event Types tab, un-tick "Include all event types" and add the events you want to monitor. In this case "User Door Group Not Valid At Door Using Access Level" should suffice as a start. To ensure you have the correct events you can create the event condition and confirm exactly what the event recorded is. Under Events create a new Alarm and set the Event Filter to the Event filter you created in step 1. Under Monitoring setup a Status Page that includes All Alarms (or alternatively is filtered for the specific alarms you want to see).

Issue This utility, TAC Vista Check References, will check references (every binding and every link) on every graphic at once and provide a summary of any empty or invalid database paths. It will also allow you to correct these broken or missing links and bindings. Environment TGML Graphics Vista Workstation Links/Bindings Cause Viewing the bindings or links of a TGML graphic can traditionally only be done on individual graphics one at a time. In addition, to see if a network path is invalid, it must be clicked on and will turn red if there is a problem. Resolution This utility was created by Benjamin Roswall at Schneider Electric Denmark. It is not an official release, nor is it supported by Schneider Electric. While it has been tested and used successfully, it should be used at your own risk. Download the TAC Vista Check References Utility by clicking here. Unzip the file onto the harddrive, view extracted files Double click TAC Vista Check References.exe Make sure Vista Server is running, click Login and log in to the database Choose whether to check for empty paths, and whether to validate .[OBJECT] bindings Click Check A summary of the network can be viewed and saved by switching between tabs.

Issue A door configured with entry and exit readers using AC1/AC1A will report door switch trouble after controller is reloaded. Environment CyberStation CX9900 CX9680 AC1 AC1A NOTE: There is no problem if AC1Plus modules are used. Cause Configuration issue Resolution Attach resistors to exit side AC1's door switch, the resistor configuration on the exit AC1 must match the resistor configuration on the entry AC1. DO NOT wire the inputs on the exit AC1 to anything. Only the door switch has this requirement, the REX input does not require adding resistors to the exit AC1. See IO System Reference Guide  connecting a dual reader door for wiring information.