Building Automation Knowledge Base

Issue Some Windows OS do not come with Hyperterminal installed. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Vista Windows 7 Cause Hyperterminal was not included in the Operating System software package. Resolution Installing Original XP HyperTerminal Download this .zip file which contains the necessary executable and dynamic link library for running hyperterminal Unzip to local hard drive. Double click the hypertrm.exe to launch hyperterminal See Connecting a serial cable to a Xenta 5/7/9xx controller for proper cable connection and hyperterminal settings if needed. Alternatively, extract the two files from any XP installation and copy them to the new Windows OS. hypertrm.exe default installation is in C:\Program Files\Windows NT hypertrm.dll default installation is in C:\Windows\System32. Alternatively, from a Windows XP CD, both files reside in the i386 directory.

Issue Configuring the Workplace Tech encrypted LON Tunnel Client  Product Line TAC IA Series Environment I/A Series WorkPlace Tech 5.10.4 Click for WorkPlace Tech 5.9.4 information I/A Series N4 Jace Cause How to handle the encrypted LON tunnel for single and multiple LON networks in the latest version of Workplace Tech, 5.10.4.  Understanding possible errors during tunneling. Resolution The following video will help us, Apply the Encrypted LON Tunnel in an N4 Jace Configure the Tunnel Client for use with multiple LON Networks on a single Jace Understand the change in workflow from Workplace Tech 5.9.4 and 5.10.4

Issue If an application hangs or crashes, Windows systems are sluggish or have problems, or new software fails to install properly one of the first places to look for information on what may be happening is the Windows Event Log. Product Support personnel may ask to see a copy of the Windows Event Log. Product Line TAC INET, TAC Vista, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, Field Devices, EcoStruxure Building Operation, Other, EcoStruxure Building Expert, Access Expert, Security Expert Environment Windows Operating System Cause If an application hangs or crashes, Windows systems are sluggish or have problems, or new software fails to install properly one of the first places to look for information on what may be happening is the Windows Event Log. Resolution   Open the Event viewer by one of the ways below: Start Event Viewer by pressing Windows key + R to open the Run dialog box and type eventvwr. Right-Click on "This PC" and select "Manage" then navigate to Computer Management (Local) > System Tools > Event Viewer. Select the type of logs the need to be exported. Application, Security, and System logs in the Windows Logs and Schneider Electric Security Expert logs under Applications and Services Logs (for Security Expert cases) are required.  For each log, view recent messages then click the "Action" menu and select "Save All Events As". Enter the log name, include the log type (Application, Security, or System) in the log name, and location the click "Save". For non-English Windows, make sure to select English (United States) in "Display information" then click OK. 

Issue The WorkPlace Tech application drawing contains a hardware tag that is outlined in red and displays this error message when viewing the right-click Display Errors option for the tag Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech Building Operation Workstation (WorkPlace Tech Editor) Microsoft Visio Cause The issue may be caused by incorrect copying and pasting of objects inside or between drawings.  An absolute cause has not been determined  Resolution Open the application in WorkPlace Tech or Editor.  Don't open the .vsd or .vsdx file in Visio alone. Enable the Developer in the Visio ribbon. File/Options/Customize Ribbon/check "Developer"  The Developer must be enabled to have the Show ShapeSheet option available  Right-click the Input object and select Show ShapeSheet In the ShapeSheet:  Step 1. Select the corrupted string for the Connection Points Step 2. Delete the string Step 3. Click the green check mark to save Unlink and Relink the connector between the previously corrupt object, UI01 in this case, and the Analog Input object.  Note, that this could be a Binary Input object as well.  This will add the correct string to the Connection Points.  

Issue When launching Workplace Tech or Workplace Tech Editor (EBO), the Workplace Tech ribbon does not appear or displays an error indicating it has not executed. Product Line TAC IA Series, EcoStruxure Building Operation Environment Building Operation Workstation (Workplace Tech Editor) I/A Series WorkPlace Tech Cause Smartware Studio 360 release 5.1.540 and later contains a 64-bit version of the Microsoft Access database.  It was modified to allow for installation with either Office 32-bit or 64-bit.  Workplace Tech and Editor requires a 32-bit version of Visio.  Microsoft normally does not allow 32-bit and 64-bit applications to be installed on the same OS.  Because of this, the COM Add-in for the Workplace Tech ribbon can fail. Resolution The Microsoft Access DataBase engine can be uninstalled in the Programs and Features of Windows.  For Studio 360 to function properly, it will need to be reinstalled.    

Issue Switching between LON communication methods within WorkPlace Tech may require a WorkPlace Tech and a LON tunnel client service restart. Product Line TAC IA Series Environment I/A Series WorkPlace Tech 5.9.3 and previous Cause When dynamically switching between LON communication methods within WorkPlace Tech (i.e. LON interface card to LON tunnel client), WorkPlace Tech communications may not initiate communications through the tunnel client properly. Resolution When this condition occurs, restart both WorkPlace Tech and the LON tunnel client as follows.   Save and close any open WorkPlace Tech applications and projects. Shut down the WorkPlace Tech tool. Restart the LON tunnel client service (Niagara LON Tunnel) within the Windows operating system services.  Verify the Niagara App Tunneling settings in Windows Control Panel. Please note, that any changes to the LON Port Name require a reboot of the computer. Start WorkPlace Tech and verify the WorkStation Communications Settings (i.e. network interface device driver and VLon device check box). Note: This does not apply to WorkPlace Tech 5.9.4 and newer encrypted tunneling in N4 Jaces.

Issue Proper handling and preparation of existing .vsd files help eliminate the crashing and lockup of the Visio application. Product Line EcoStruxure Building Operation, TAC IA Series Environment Workplace Tech Editor EcoStruxure 1.9.x - 3.2.3 Workplace Tech 5.9.1 - 5.9.4 Visio 2013, Visio 2016 Note: This does not apply to Workplace Tech Editor EBO 2022 (and newer) and Workplace Tech 5.10.x Cause The product is affected by the version of Visio in use as well as the file size and unused objects in the drawing. Resolution When using Workplace Tech 5.9.x with Visio 2013 or 2016, the file has to be opened in "Compatibility Mode." DO NOT CONVERT. Illustration 1 While the .vsd file is open in Visio, not in Workplace Tech, use the "Reduce File Size" option and select the boxes in Illustrations 1&2. Illustration 2 In Visio 2016, after opening the "Inspect Diagram," (Illustration 3), select the first 3 boxes in the "Reduce File Size" option (Illustration 4). Illustration 3 Illustration 4 Save the file for use in the Workplace Tech Project or to be imported into your AS-P as a .vsd. Add the "cleaned" file to your project or import it to Workplace Tech Editor. Make sure the Visio 2013 or 2016 is at the most recent version and build. You can find this under the file/account/About Visio. If Version 1802 is available in your Microsoft Office update Channel, use it. Version 1801 was used in testing. For Visio 2013 Build 15.0.4971.1000 MSO 15.0.5007.1000 was tested (Illustration 5) Illustration 5

Issue Procedures to purchase and unlock a permanent copy of WorkPlace Tech Tool (Asia Pacific customers) Product Line TAC IA Series Environment I/A Series WorkPlace Tech Tool software version 5.x. Cause WorkPlace Tech unlock code request should not be sent directly to Customer Care since orders in Asia Pacific are placed through Hub Asia.  Resolution 1. Install WorkPlace Tech. 2. After installation, generate the codes required to request an unlock code. 3. Complete the Unlock Code Request Form or output it to the file (InVueOrder.txt). Submit the form or the file together with the purchase order to your local orders processing team.  The procedure to generate the order codes can be found in the WorkPlace Tech Tool Installation Instructions. 

Issue Does Niagara R2, G3 (AX), and N4 support IPv6?  Product Line TAC IA Series Environment I/A Series R2 I/A Series G3 (AX) I/A Series N4 Cause Network planning questions from an end customer's IT department Resolution Niagara R2 does not support IPv6 (by design). Niagara G3 version 3.5 supports IPv6 but only on Windows-based platforms like an Enterprise Network Server or a soft Jace. Niagara G3 version 3.6 added support for IPv6 in embedded platforms like the ENC-520-2 and ENC-410-1.  Hotspot JVM required.  It is not supported by the J9 platform. Niagara N4 supports IPv6

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 WorkPlace Tech application was created with constant tags for writing test values to the application.  After uploading a previously downloaded application that contains constant tags with a [NA] value, none of those constant tags are drawn on the regenerated application drawing. Product Line TAC IA Series Environment I/A Series WorkPlace Tech Tool version 4.x (any release) I/A Series WorkPlace Tech Tool version 5.x.x (any release) Cause The default input value for any unused control object input is a value of [NA].  Since all unused inputs have the implied [NA] constant, they are not drawn on a regenerated WorkPlace Tech application drawing. Resolution This action is by design.  By design, a constant tag can be added to any previously unused control object input and a value written to the controller via that constant tag using the Write to Ram function.  When adding constant tags to inputs, it is not necessary to recompile and download the application unless you desire that the new "Non-NA" value be saved in the application hex file.  With this in mind, remember that constant values are written to an installed application using the "Write to Ram" function will be lost when the controller is rebooted.

Issue The file linked below details a model of the MicroNet sensors with carbon dioxide sensing.  Are these available for purchase? MN-Sxxx CO2 sensors Product Line TAC IA Series Environment I/A Series MN-Sx sensors Cause Sales literature with reference to Schneider-Electric Resolution The MicroNet sensor models with carbon dioxide are a product of another company - Barcol-Air. The standard MicroNet sensors from Schneider-Electric were modified by Barcol-Air to include carbon dioxide sensing. Visit http://www.barcol-air.nl for more information. In the United States, contact Alpha Controls and Services to order these sensor models. Alpha Controls & Services 4104 Charles Street Rockford, IL 61108 Office:  815-227-4000 www.alphaacs.com  

Issue Using BQL query to extract data from a G3 station How to display data from the BMS system on their custom / third party application. Environment I/A Series G3 Cause A requirement to display data from the BMS system on their custom application. Resolution You can query for data using a BQL (Baja Query Language) query. The Baja Query Language (BQL) is an SQL-like query language that provides a mechanism for identifying various sets of data. It provides an ad hoc way to search for data based on some criteria. 3rd party applications which is capable of running a web query can be used to query data from a G3 station. One such application is Microsoft Excel. The Niagara BQL Query Examples PDF provides several examples of BQL queries as well as an example of using Excel web query. Most data in a station can be queried including point values etc. For detailed description of BQL usage, refer to the Niagara Help in Workbench ( as shown below).

Issue When trying to embed a website in an N4 Px view, the site renders in Workbench but not in most browsers displaying this error in the browser's developer console; Product Line TAC IA Series Environment I/A Series N4 Workbench Web Browsers, Chrome, Firefox, Edge, Internet Explorer Cause Most major browsers no longer support NPAPI/Java plugins.  Oracle has stated they would remove it in JDK 9  and from Java entirely.  The N4 WebBrowser object under the workbench pallet requires Java to work correctly.  That is why it only works in the Workbench environment, Internet Explorer, and older Oracle Java platforms. Resolution When using the WebBrowser object in Niagara N4. Viewing in the Browser Preview Mode or in an actual browser that doesn't support the Java plugin, the embedded site will not render. The only solution is to use Internet Explorer or the Web Launcher application detailed in the attached document to view the Px. For more information, refer to the Niagara Web Launcher - Niagara Java-based Web Clients Guide PDF

Issue NRE default configuration and RAM disk removal Product Line TAC IA Series Environment I/A Series N4.11 Jace 8000 Cause In Niagara 4.10u1 and earlier, the RAM disk was used to temporarily store alarm and history data. During station save, this data was copied from the RAM disk and zipped up, and stored on Flash. In Niagara 4.11, the RAM disk has been removed entirely. This data is now written directly to the Flash. Resolution A change to the JACE-8000 file system has been introduced with the release of Niagara 4.11. The RAM disk was used to store alarm and history data. During station save, this data was copied from the RAM disk and zipped up into a single file that was stored on flash. In Niagara 4.11, the RAM disk has been removed entirely. This data is now written directly to the flash memory. This change has enabled ~384MB of RAM to be freed up to improve performance. Some of the space has been reallocated to code cache, metaspace, and heap space in the 4.11 NRE default settings. Any additional memory space is now available as general free memory. JACE-8000 NRE Memory Default for (older) Niagara 4.10 - sizes in MB: System Reserve Size:          0 Heap Space Size:              360 Meta Space Size:              56 Code Cache Size:              16 RAM Disk Size:                384 Free Memory:                  ~16 JACE-8000 NRE Memory Default for (newer) Niagara 4.11 - sizes in MB: System Reserve Size:          0 Heap Space Size:              384 Meta Space Size:              64 Code Cache Size:              32 RAM Disk Size:                Not present (cannot be created) Free Memory:                  ~352   These changes should be transparent to most users and will provide moderate performance improvements on the JACE-8000.

Issue Tridium N4.11 Upgrade Considerations  Product Line TAC IA Series Environment I/A Series N4.11 Enterprise Server I/A Series N4.11 Jace 8000 Cause Detailed information about N4.11 upgrade prerequisites and best practices  Resolution The following details a set of upgrade considerations and known issues and their workarounds regarding Niagara 4.11. Please review prior to upgrading to Niagara 4.11. Niagara 4.11 and Default NRE Memory Changes: A change to the JACE-8000 file system has been introduced with the release of Niagara 4.11. The RAM disk was used to store alarm and history data. During station save, this data was copied from the RAM disk and zipped up into a single file that was stored on flash. In Niagara 4.11, the RAM disk has been removed entirely. This data is now written directly to the flash memory. This change has enabled ~384MB of RAM to be freed up to improve performance. Some of the space has been reallocated to code cache, metaspace, and heap space in the 4.11 NRE default settings. Any additional memory space is now available as general free memory. These changes should be transparent to most users and will provide moderate performance improvements on the JACE-8000. Prior to upgrading your JACE-8000, please review NRE default configuration changes and RAM disk removal In 4.11. Niagara 4.11 and Third-Party Modules Keeping your Niagara installations safe and secure is our highest priority. In Niagara 4.11, ALL third-party modules must be signed with either a trusted valid certificate or a self-signed certificate to successfully run on a station. This new policy greatly increases the security posture of Niagara installations by making administrators aware of any modules that may have been tampered with, compromised, or derived from untrustworthy sources. Niagara's new signature enforcement feature is being rolled out over multiple Niagara releases. The first iteration was built into release 4.8 to give developers adequate time to make the transition to always signing any third-party modules. Niagara 4.8 produced console and Security Dashboard warnings about unsigned modules but allowed them to run on a station. As of Niagara 4.11, unsigned modules will not execute. For more information, please review the Niagara documentation on Third-Party Module Signing Niagara 4.11 Updated Operating Systems, Browsers, and Databases For the latest information on supported operating systems, please refer to Supported OS and other software in the Niagara 4 Framework Installation Guide. Tridium remains focused on keeping pace with advancing IT infrastructure to enable more efficient, long-term support of each release version. This policy enhances the security posture of a Niagara installation by ensuring that only the most robust, secure operating systems and enterprise applications are compatible with the framework. The list below provides information on what we will be supporting with Niagara 4.11.   OS, Browser, Database Version Red Hat Enterprise Linux 8.1 (64 bit), 7.7 Ubuntu Linux 20.04 LTS – Desktop & Server Windows Server 2019 (64 bit), Server 2016 (64 bit), Windows 10 (64 bit) VMWare ESXi 6.7 Oracle Database 19.3, 18.3, ... 12.2/12.1 MySQL Database 8 MS SQL Database 2019, 2017, 2016 Browsers Chrome, FireFox, Microsoft Edge Mobile Browsers Safari (iOS 12, 13), Chrome (Android 8, 9, 10) As with all software products, we must also deprecate support for some operating systems and enterprise applications.  Nevertheless, you can be confident that the above list will handle your needs moving forward. Using Web Launcher with Niagara 4.11 Web Launcher 21.4.1 was recently revamped for Niagara 4.11 to include essential software dependencies updates along with critical defect fixes. This version of Web Launcher has Java version 8 update 311 and certificate management has been updated to work with Niagara 4.11 along with any legacy or prospective release. Prior to using Web Launcher with Niagara 4.11, customers should update Web Launcher accordingly (see steps below). How to update Web Launcher? Web Launcher has a feature to check for updates over the internet and prompts the user when a new version is available in the cloud. However, the existing version of Web Launcher has a bug that prevents a smooth update. Users will be required to perform a fresh install by downloading the latest version from the cloud via the station web Login page. Click on the Niagara Web Launcher Installer link on the station's Web Launcher Web Page, which can be reached via the link on the Login page itself. Once the download is successful, click on the msi file and follow the installation wizard. You do not have to uninstall the older version. The new installation will automatically update to the latest version. Niagara 4.11 Release Notes: The release notes for Niagara 4.11 are located here.

Issue Java is no longer available or supported in most web browsers so accessing Niagara using the Java Applet is no longer possible Product Line TAC IA Series Environment I/A Series G3 Enterprise Server/Jace 3.8U4 I/A Series N4 Enterprise Server/Jace 4.4U3 and subsequent Cause Oracle announced the end-of-life of Java SE 8 (Standard Edition). As of January 2019, free public updates for commercial users are no longer available. Customers accessing Niagara with the Java Applet/Web Start are impacted by this change. Those who have upgraded to full HTML5 versions for your browser front-end will not be affected. For customers who use the Java VM and Java Web Start for their legacy systems, Tridium has developed a suitable alternative, the Niagara Web Launcher. Resolution The Niagara Web Launcher application is now available. You can download Niagara Web Launcher using the following link: 64-bit systems: Web Launcher for 64 bit, 32 bit OS 32-bit (-x86) systems: Web Launcher for 64 bit, 32 bit OS Niagara Web Launcher download links are also available from the Niagara station login page. Niagara Web Launcher support is included in Niagara versions: 4.4U3 –Included in (4.4.94.14). 4.7U1 - Included in (4.7.110.32) Subsequent releases of Niagara 4 will include Niagara Web Launcher support. A patch for Niagara 3.8 U4 can be downloaded from here.  Copy web.jar module version 3.8.403.1 into the modules folder of your Niagara AX 3.8 U4 workbench or supervisor station.  This module may also be installed on JACE platforms.  To use Niagara Web Launcher, Web Start must be enabled in the Web Service of the station.

Issue Troubleshooting guide for ASD bus communications. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series Legacy Controllers ( GCM, MicroZone II, MicroFlo II, LIM, PEM, MN-ASDI) I/A Series R2 UNC I/A Series G3 ENC Building Operation Automation Server Premium ( Pre EBO 2022 ) I/A Series N4 Jace 8000 Cause Troubleshooting guide for ASD bus communications. Resolution This checklist provides several settings/configurations to review when faced with a communication problem at the controller level. The content was compiled from different resources, summarized, and laid out in an easy-to-use manner so as to provide a quick-reference document. NOTE:  The ASD protocol is not supported in EBO 2022 or subsequent versions

Issue WorkPlace Tech Tool reports Database Error when attempting to link to the output of a copied custom object. The displayed error message shows the name and attribute of the object being connected along with the error "Exception error occurred during WriteProperty [0xE0330020]". Product Line TAC IA Series Environment WorkPlace Tech Tool Software Version 5.7.x or newer Workplace Tech application file containing a custom object copied from another WPT application. Cause Unknown, believed to be an internal Visio error. Resolution Open the application file in the WorkPlace Tech Tool software and select the page for the Custom Object that is reporting the error. Break the connection (disconnect the link) between the Custom Object output tag and the corresponding source object. When breaking the link, it is suggested that the wire link be dropped onto the drawing page before being re-linked. Select the link and reconnect it to the proper object. It may be necessary to perform this unlink and relink operation for all output tags within the Custom Object that had been copied from another WPT application file.