Building Automation Knowledge Base

Issue Installation cable requirements Product Line Andover Continuum Environment Continuum Cause Need to specify a cable type for a site Resolution Installation cables have to be chosen taking in to account the local regulations and legislation, the installation environment and the electrical requirements. The Continuum specifications give the electrical requirements. For this reason actual cable types, makes or Belden numbers can not be stated, only as helpful guidance as a cable that may meet the electrical requirements only. BACNET MSTP - See What cable type should be used for BACnet MS/TP communications?. INFINET - See What cable type should be used for Continuum Infinet bus communications. CARD READER - See the manufacturers requirements for the cables, also Maximum Cable Length Between ACX and Card reader. ANALOGUE and DIGITAL INPUTS - See the relevant Continuum specification eg. I/O Modules. See Andover Continuum IO System Reference (especially note screening and grounding requirements) I/O MODULE (RS-485 & LON) - See the relevant Continuum specification eg. I/O Modules See Andover Continuum IO System Reference For ETHERNET, LON, MODBUS RTU, OTHER THIRD PARTY BUS/NETWORK - See the relevant external documents

Issue The status of a Forced BACnet value is not reflected in a Graphic or the Watch Window. Product Line EcoStruxure Building Operation Environment Enterprise Server (ES) Automation Server (AS) Cause This is functioning as designed. It was designed so that the "Forced" status for BACnet values would not be displayed in graphics or the watch window. Resolution It was designed so that the "Forced" status for BACnet values would not be displayed in graphics or the watch window. For a workaround using a PE Script program to show the forced icon for a BACnet value see How to show the forced icon for a BACnet value in a Graphic. In EBO version 3.0.1 and later this issue only occurs on internal BACnet points, points which are located in the Application folder under the BACnet interface for the SmartX server.

Issue In WorkPlace Commissioning Tool, the following error message appears when browsing a BACnet/IP network: "A critical error occurred in the communication server rtmonitor.exe. Please shutdown this application and the communication server then try again." Product Line TAC IA Series Environment WorkPlace Commissioning Tool Cause There could be a Niagara R2 station running on the computer configured for BACnet/IP. Since the Niagara station also uses UDP port 47808 by default, the Niagara service prevented WorkPlace Commissioning Tool from "binding" to the UDP port. Resolution There are two ways to resolve this issue: Disable the Niagara service when using the WorkPlace Commissioning Tool In Workplace Pro, stop the station that has the BACnet/IP service enabled, and configure it so that it does not auto-start. NOTE: If this procedure does not correct the issue and the WorkPlace Tech Tool software is being run on the Windows 7 operating system, refer to WorkPlace Commissioning Tool Windows 7: "A critical error occurred in the communication server rtmonitor.exe" for information on how to correct what may be a program security settings issue.

Issue "No license for LonWorks communication" error when using a non LE dongle. Product Line TAC Vista Environment Non LE dongle (LE= Limited Edition which has no Webstation or multiserver functionality) Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause One would normally expect this error message when trying to run Webstation server with a Vista LE license. If the system is not using a Vista LE dongle/license, but the error "No license for LonWorks communication" appears, then the problem may be in the Privilege Server service.   Resolution Shut down Vista Server and Workstation. Right click on My Computer and select Manage. Expand Services and Applications. Click on Services. Find the service Privilege Win32 Server. Right click on the service and select Stop. Right click on the service once more and select Start. Restart Vista Server and Workstation and verify that the error went away. Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" - LonMaker Recovery Folder "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 When using the I/A Series R2 (Niagara) WorkPlace Pro to commission LON controllers under an existing LNC-100, configure the Local LON device to match the Domain Length, Domain ID, and Subnet ID programmed in the LNC. Product Line TAC IA Series Environment I/A Series R2 (Niagara) WorkPlace Pro I/A Series Network 8000 LNC-100 Cause When a third-party network management tool is used to define and commission a LON network, the commissioning tool frequently uses specified domain address instead of the default "zero-length" domain address.  When using the I/A Series (Niagara) R2 WorkPlace Pro to learn a previously commissioned network, Workplace Pro will not be able to discover the LON devices until it has been configured to match the domain address of the network. Resolution Click here to see this procedure including screen captures. If the LNC-100 is already communicating to existing controllers on the LON trunk, document the Domain0, Subnet0, and Node0 addressing in either the SYS:SIM or SYS:SIM2 blocks. You don't need to change the existing address in order to add new LON controllers. If you will be using Niagara to commission the new LON controllers, set up the LonWorks Service so that the Local LON device is on the same Domain and Subnet as the LNC-100. Set the Domain length and Domain ID; go to the Properties of the LonWorksService, Netmgmt tab, Engineering tab, domainId, length, domainId. For example, if the SYS:SIM block in the LNC-100 has "DOMAIN0=0D, SUBNET0=01,NODE0=120,..." then in the UNC, it should be domain length = 1 (byte), and domainId = 0D. Apply the changes. Set the Niagara subnetNodeId properties: subnetId = 01, nodeId = 127. The subnet matches SUBNET0 in the SYS:SIM block. Leave the Node ID set to 127 Apply the changes Recommission the Local Lon Device. (Remember to disconnect the LNC-100 from the trunk before commissioning!) With the new controllers connected to the LON trunk, go to the Lonworks service, Lon Device Manager, and run the “find” command; the new controllers should be added to the list of nodes. You can use the Lonworks Utilities, command = identify, SubCommand = service pin to be sure you have the correct node. Then commission the new nodes. Note: Should the LNC-100 be accidentally commissioned, refer to Network 8000 LNC-100 cannot communicate to LON devices under it but can be accessed with WorkPlace Tech or a LON commissioning tool.

Issue Getting DCOM errors when trying to access WebClient and need to determine which of the various permissions have not been set properly. Product Line Andover Continuum Environment WebClient IIS Cause DCOM permissions have not been set properly. Resolution Open EventViewer, go to System Events, and note the DistributedCOM error. Open the error and find the CLSID that it is referring to. In the DCOM Config, look through all of the DCOM objects and find the one with the matching CLSID. Make sure that it has the correct permissions according the WebClient installation document. If this does not resolve the problem, you can also consult WebClient most common installation problems for further troubleshooting steps.

Issue Key information necessary to operate and install Vista OPC Server Product Line TAC Vista Environment Vista Server 5.1.x Vista OPC Server 1.6.1 Cause Following these guidelines and work arounds the proper installation and configuration of TAC Vista OPC Server can be achieved. Resolution Please reference the articles below depending on the situation.  After installing TAC Vista OPC server it does not show up as a Windows service: Proper license is required before installation OPC server for TAC Vista will not keep the login settings in the TAC Vista OPC Server setup: Login Settings require additional steps Installing and configuring Vista OPC Server: Step by Step installation and configuration steps Unable to access data on a Vista OPC Server that reside on Xenta Server (I/NET or 3rd Party protocols): Server address limitations

Issue Error states: "Ensure that Vista Server is started" when trying to log into TAC Vista Workstation. The server is started. Product Line TAC Vista Environment TAC Vista Workstation 4.2.5, 4.3.0-4.5.0, 5.0.0 and higher Microsoft Windows XP Service Pack 2 Cause Microsoft Windows XP Service Pack 2 has security changes/upgrades from previous service packs.  This affects the DCOM permissions that Vista Server relies on. a variety of other reason could result in an error in DCOM parameters in later operating systems. Resolution Vista 4.2.5 Apply settings described in this TPI to get TAC Vista to work properly. Vista 4.3.0-4.5.0 Apply settings described in this TPI to get TAC Vista to work properly. Vista 5.0.0 and higher Apply settings described in TAC Software Installation Manual available on The Exchange Download Center. This can be done using the DCOM Utility in Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET. Error Message: Ensure that Vista Server is started lists manual steps to access DCOM.

Issue After successfully downloading a Menta application directly through the serial connection, the pop-up window below is displayed:  tam32 No blueprint in TAC Xenta! Don't forget to download the network configuration if the TAC Xenta is to function in a network! Product Line TAC Vista Environment Directly connected Menta Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause The blueprint is also called an .NDB (network database) file.  It contains network information that allows the controller to communicate to other controllers or I/O modules.  When downloading a Menta application directly, this warning is displayed as a reminder that that necessary network information has not been included in the application-only download. Resolution If the controller is running stand-alone and no networked communication is required, then no further action is required.  The message is only a warning alerting the user to the fact that the NDB file has not been included in the download. If the controller needs network variables and I/O module communication, follow the direct download (most often done only for troubleshooting purposes) with a download from the front end Vista Workstation for classic networks Vista System Plug-In for LNS networks If no front end exists, but network communication is still required (most often for I/O modules), lonTool32 is a suitable work around for those rare instances.  See Using lontool32 to download a stand-alone controller.

Issue BACnet bCX schedules cannot be edited without an error. Product Line Andover Continuum Environment Continuun bCX4040 Schedule Firmare v4.500082 Cause Following an upgrade to firmware v4.500082 the  Schedule end date year 2038 now enforced and schedule cannot be modified if the end (effective) date is beyond this Resolution For all schedules newly created or otherwise, the end (effective) date needs to be set to 2038 or earlier see Script Programs in Continuum compared to StruxureWare Building Operation and using floats (32 bits) and 64 bit numbers If the date is set after 2038 then an error is seen when trying to edit the schedule "An error code was returned from a BACnet operation, but the reason could not be determined."   Creating a new schedule with a date > 2038 can also give the error: " Error setting attribute 'DeviceID' An error code was returned from s BACnet operation , but the reason could not be determined " Defect was corrected in v4.500083

Issue Use of the Building Operation Script editor and general Script programming is covered in the Training courses and technical reference guide, what other techniques can be used to debug a program? Product Line EcoStruxure Building Operation Environment  Building Operation Script editor. Cause Often additional techniques are required to debug Script programs, especially when attempting to analyze, modify or fault find other people's code. Resolution Some techniques you can use for debugging your program and isolating problems are: Add in additional line labels to the program to isolate where the program is disabling or failing, if it disables you will be able to see the "CurrentLine" it has failed on and therefore know which line of code is causing the problem. Use the Trace feature to step through a program and monitor the binding variables, stepping through each line of code to ensure the values are all set as expected. Even if a program does not disable you can use the "Stop" keyword in the program, it will act as a break in the code and you can look at the values of the various variables, this may be a useful alternative to the Trace feature. Use the Watch window and the Binding Variables window to show the values of the various objects, when used with the above two techniques it allows you to accurately trace a program flow. Ensure all of the code used is compatible with the Script programming rules and that Continuum Plain English programs are not just used without conversion. Check the Plain English and Script Difference Guide. For programs in an i2 or b3 controller, ensure none of the Program size limitations are exceeded, see Plain English program limitations on number of characters in program and line labels.  

Issue Cannot open a file from TAC Vista Webstation from a TGML graphic Environment Vista IV TGML Webstation graphics Workstation graphics File access Cause  The "OpenFile" command doesn't work in a web browser. Resolution For an alternative way of viewing the reports and other files, refer to this document on the Community: DOC-7604 Guideline on how to open the same file in both TAC Vista Workstation and TAC Vista Webstation. To achieve opening a PDF or DOC file from a TGML graphic both in TAC Vista Workstation and TAC Vista Webstation, typically in workstation there's no problem. Use the "OpenFile" button, and the file should open. "OpenFile" button function in Webstation is not the same.  The "OpenFile" command to open the document from a button in a TGML graphic doesn't work in a web browser.  To open a file from a dynamic TGML graphic in Webstation Define a "Hyperlink" in TAC Vista. Direct the hyperlink to a document located in the "C:\Inetpub\wwwroot" folder on the server. Call the hyperlink with http://ip_address/docName.   Typical graphic behavior Opening a PDF document: Can be viewed in Workstation. Can be viewed in Webstation, but will not open in a new window even defining target as _blank. Opening a DOC document: Can be viewed in Workstation, but opens an "extra" window which must be closed after viewing the document. Can be viewed in Webstation.

Issue Without knowing the Device ID / Device Instance these devices cannot add to the MSTP network in the AS or ES. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment Automation Server Enterprise Server BACnet SE7000 Cause Only the MAC ID / Com Address is shown in the display but not the Device ID / Device Instance. Resolution SE7200x Models Default Device ID is set to: 72000 + MAC Where MAC is the current MAC address of the device. The device ID will also be upgraded as soon as there is a change to the device’s MAC. For example, when a SE7200F5045B controller with a MAC address of 41 is connected to a network, its default Device Name will be SE7200F5x45B-41 and its default Device ID will be 72041. SE73xxx Models Default Device ID is set to: 73000 + MAC Where MAC is the current MAC address of the device. The device ID will also be upgraded as soon as there is a change to the device’s MAC. For example, when a SE7300C5045B controller with a MAC address of 63 is connected to a network, its default Device Name will be SE7300C5x45B-63 and its default Device ID will be 73063. Click here for the Integration Manual. Please refer to the SE7300 series BACnet controller does not come online in StruxureWare Building Operation if SE7300 controller does not come online.

Issue Installing StruxureWare Building Operation Workstation fails The following error message is displayed when installing Workstation:     Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Workstation Earlier versions Cause This issue occurs if the PC has a newer version of Microsoft Visual Studio 2010 Tools for Office Runtime Language Pack previously installed than the one in the Workstation installer, which will abort the installation. Resolution Uninstall the Microsoft Visual Studio 2010 Tools for Office Runtime Language Pack from "Add or remove programs" in Windows. Run the Workstation installer again. It should now complete successfully. Before step 1 (uninstalling) you may first check which version of Microsoft Visual Studio 2010 Tools for Office Runtime Language Pack you have installed, this is also found in "Add or remove programs".  After finishing step 2 you may download the latest  Runtime Language Pack separately from Microsoft, or even the complete Runtime.  Note: This resolution only applies if you specifically get error 1603. There is a similar issue but with error 3010, please see Getting the error "Failed to install XXXX redist, error: 3010" during installation.     StruxureWare Building Operation

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 How to uninstall and completely remove TAC Vista 4.3 to TAC Vista 4.5 Product Line TAC Vista Environment Microsoft Windows OS Vista 4.3 to Vista 4.5 Cause Occasionally it is beneficial to be able to remove a TAC Vista installation completely, removing any indication it was ever installed. Resolution When using SQL 2000 or enterprise version not administered by TAC Vista: Backup SQL database named "taclogdata." Use the backup function in SQL Server manager. Save the database outside of the Microsoft SQL Server and TAC root directory (usually C:\Program Files\TAC and> C:\Program Files\Microsoft SQL Server). When using SQL MSDE administered by TAC Vista: Backup TAC Vista log and event database using backup function in TAC Vista. Backup TAC Vista database using backup function in TAC Vista. Stop SQL manager, Task manager/processes – stop sqlserv.exe and sqlagent.exe if running. Remove TAC Vista Config1.x using the uninstall program in Control panel Add/Remove programs. Remove all TAC Vista hotfixes. Remove TAC Vista Server 4.x.x using the uninstall program in Control panel Add/Remove programs. If additional TAC programs like TAC ToolPack, TAC XBuilder etc. are installed remove them as mentioned before. Remove SQL (Microsoft SQL server desktop engine) using the uninstall program in Control panel Add/Remove programs. Save off a customer's license (.lic) file to another location.  Delete remaining uninstalled TAC folders (usually C:\Program Files\TAC). Delete remaining files in C:\Program Files\Common Files\TAC Shared. Delete remaining uninstalled SQL (Microsoft SQL server) folders (usually C:\Program Files\Microsoft SQL Server) Check to see if TAC needs to be removed from the registry – Start, Run, REGEDIT. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls Remove all keys containing "TAC Shared," e.g. C:\Program Files\Common Files\TAC Shared\TACADDON01_ENG.dll. If applicable - Remove SQL from registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL server Go to user profiles delete the profile Computername\TACA_Computername (Versions of Vista <5.0) Go to My computer, right click manage, local users and groups, users, and delete user account TACA_Computername and TACM_Computername. Reboot. Reinstall desired version. See How to uninstall and completely remove TAC Vista 5 for steps on removing TAC Vista 5.

Issue How to update a demo Security Expert License once it expires. Product Line Security Expert Environment Workstation Cause Not sure how to re-active the demo license after it has expired. Resolution To extend the demo license, contact your local country product support group. Product support can have the license expiration date extended and then it can be updated/download again.  Go to About -> License, go to License Update tab and click on Download License and then OK to update. From v4.2.243 you will now be able to perform manual license activation's that can be used for installations that do not have Internet access. For more information see Performing a manual license registration.

Issue You get an error, "Unable to load the .Net control for this page." when trying to open a schedule in WebClient. Product Line Andover Continuum Environment webClient Cause The problem is that the .Net zone permissions are not set on the browser machines. Resolution Depending on the revision of the WebClient the procedure for correcting this on the browsing machines is different. If you are running WebClient version 1.73 or below then refer to the WebClient installation guide on setting the .Net zone permissions. If you are running WebClient version 1.74 or higher, which uses .Net 2.0, the procedure is different. Below is the procedure that will need to be performed on the browser machines at the command prompt to set the .Net Zone Permissions for .Net 2.0. The following command will add FullTrust to the Internet_Zone in DotNet 2.0: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Internet_Zone -zone InterNet FullTrust -name FullTrust The following command will add FullTrust to the Trusted_Zone in DotNet 2.0 C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Trusted_Zone -zone Trusted FullTrust -name FullTrust This will result in output like: The operation you are performing will alter security policy. Are you sure you want to perform this operation? (yes/no) Then select Y and you should see: Added union code group with "-zone" membership condition to the Machine level. Success You should then be able to open the .Net 2.0 editors on your web.client browser machine. In some cases adding the webclient IIS PC to the trusted sites in the browser is needed Internet Explorer> Internet Options> Security> Click Trusted Sites> Click Sites Type in http://your server name/webclient and click Add (i.e your server name is specific to your install) Deselect the checkbox for 'Require server verification (https:) for all sites in this zone Click Ok, Ok Close explorer and access webclient schedules Note: Every browser PC that will be accessing schedules needs to have the caspol commands run on it. Download a batch file that can be run on each PC (Rename the .txt file to .bat and run at a DOS prompt  C:\> caspolwebclient.bat)   Note: When using 1.94 SP1 check the application pools .net version selected Name .Net Version ASP NET v4.0 4.0 ASP NET v4.0 Classic 4.0 Classic .NET AppPool 2.0 Default AppPool  2.0 WebClient  4.0 Note: If .net framework 4.5.x has recently been installed on browser PCs, see Webclient Cannot open .net editor with .NET Framework - 'There was an error trying to create the .NET control for this page'.

Issue Unit Conversion Exceptions Unit selection of 'bar' defaults to N/m 2 unit Units are not displaying unit as selected in the properties Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.2 and above Cause Building Operation supports both the SI metric system and the US Customary System for units of measurement. The operating system regional settings on which WorkStation is installed determine whether SI units or US Imperial units are displayed. The conversion between the two measurement systems is managed automatically. For example, the temperature 42,82 °C is stored in Building Operation. A WorkStation on an operating system with the US Customary System converts the temperature and displays it as 109.08 °F. To display the original unit of a value in WorkStation, open the Properties pane for the value and go to the Unit selection dialog box. As part of this process some units selected, default to a default display unit, and not what was originally selected.  For example, selecting the pressure unit 'bar' when configured in a SI regional setting will display by default the unit 'N/m 2 ' and not 'bar' as selected.  This functionality is as per design but can be altered by using the Unit Conversion Exceptions feature. Resolution First reference Adding a Unit Conversion Exception on the Building Management WebHelp site.    In the release version 1.2 and above there is a feature that allows the operator to create unit exceptions, called Unit Conversion Exceptions.  This is located under the Domain folder and allows various conversions for different domains.  The steps below indicate how this is achieved. Locate the Unit Conversion Exceptions under the required Domain The Unit Conversion exceptions are now displayed in the Workspace.  The Add remove buttons are located at the bottom of this workspace Add the Configured unit, which is the selected unit for the variable you wish to be converted Then change the SI Display Unit and / or US Display Unit to the desired unit you wish the configured unit to be displayed / converted too Save these changes and confirm that it is now displayed in the desired unit.  In some cases you may need to log out and then back in for the changes to be applied. Online Web Help is also available here: If your system is based in US region then you can default you measurement system to US as per Metric vs. English (Imperial) Operating System.

Issue Unable to successfully install Continuum keyless license software. Product Line Andover Continuum Environment Continuum Keyless Soft License Hasp Key Utility Sentinal HASP License Manager Cause Various causes. Resolution The following articles address issues with the Continuum Keyless license software. Hasp Key Utility will not activate keyless license Version Error Getting Id. - HASP License Manager service has stopped Web based email should not be used to deliver Keyless Licensing information files (c2v) or activation files (v2c) How to determine the Continuum version, features and the Hasp license ID on a Keyless Continuum License Hasp Key Utility will not activate keyless license Version Error Getting Id. -- Key Id Not Found Hasp Key Utility will not activate keyless license Version Error Getting Id. - HASP License Manager service has stopped

Issue "No license for LonWorks communication" with TAC Vista Server LE Product Line TAC Vista Environment TAC Vista Server LE (LE= Limited Edition which has no Webstation or multiserver functionality) Cause If TAC Vista Webstation is installed on a TAC Vista Server LE machine, Lon communications will not work correctly. It will work for 10 minutes then an alarm message appears, "No license for LonWorks communication," and all communication with the Lon network will stop. Resolution Uninstall Webstation Related Articles: "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" Error in Windows 2008 Server X64 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility