Building Automation Knowledge Base

Issue Encounter Queue Full Exception in context of "Error writing BACnet point" Product Line EcoStruxure Building Operation, TAC IA Series Environment I/A Series N4 Jace 8000 I/A Series N4 Jace 9000 Niagara Station running as SoftJace or 3rd Party Jace Cause If you notice queue overflow messages in the station dialog, it is essential to know which queue is overflowing. There are many different communications mechanisms in BACnet, and they use different queues. Resolution The canonical reference article is located on Niagara Community: BACnet Tuning Suggestions I have excerpted the following as a Rule of Thumb for the recommended starting configuration: Configure your tuning policies so that write-on-start is not enabled on some of the points - otherwise, the JACE may start with a to-do list that is larger than the queue can handle. The recommended configuration from Tridium is to set BACnet WriteWorker queues to 1.5 times the number of writable points. However, as initial configuration, Product Support has found these values to perform better than the defaults, so change the following values from 1000 to 3000. View the BacnetNetwork Property Sheet Expand Bacnet Comm Expand BACnet Comm -> Server -> Worker and Confirmed Worker Expand BACnet Comm -> Transport Change the various Queue Sizes from 1000 to 3000. Please consult PSS if a change to a value higher than 3000, as that has been found to adversely affect performance. 

Issue Installing and Configuring Email Service Accounts in Niagara G3 Environment Niagara G3 Cause The need for a quick reference guide Resolution The following document can be found at Niagara-Central.com as well.

Issue How to configure a LON router in Niagara R2. Environment Niagara R2 LON Cause Troubleshooting Resolution Review / download documentation here.

Issue Various changes to the PC operating system can alter the IA Series software host ID causing the license to be invalid. When this occurs the window below will be displayed providing the new Host ID read from the PC. Product Line TAC IA Series Environment I/A Series Enterprise Server I/A Series Workbench I/A Series SoftJace platforms    Cause Upgrading the Operating System (Windows, Linux, etc.) always changes the Host ID.  Making other changes to a Niagara host platform may also change the Host ID.  These are the types of changes that can alter the Host ID: upgrading from Windows 7 to Windows 8 upgrading from Windows 8.0 to Windows 8.1 upgrading from Windows 7 or 8 to Windows 10 installing the 2 August 2016 anniversary update to Windows 10 upgrading from RHEL5 to RHEL6 Upgrade from RHEL6 to RHEL7 will change your Host ID. Installing certain Microsoft Windows updates (patches/fixes) may also cause the Host ID to change. Resolution Email the hostID from the current license or a copy of the current license as well as the new hostID provided in the "Request License window" to Schneider Electric Customer Care (Email Information) and request a license replacement.

Issue Connection lines will not connect to some objects on the drawing, but will on other objects. The "Snap and Glue" feature was verified per Connecting lines in WorkPlace Tech stay red even when snapped to an object. Product Line TAC IA Series Environment WorkPlace Tech 5.x Windows XP SP3 Visio 2003 Visio 2007 Cause Objects are on the "back" layer. Resolution Select objects or complete drawing Right click Select Shape > "Bring to Front"

Issue The WorkPlace Tech and WorkPlace Editor add-in for the VisioRibbon is available in the toolbar of Visio but all or some of the functions are unavailable. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech 5.9.x, 5.10.4 Building Operation Workstation (WorkPlace Tech Editor) Microsoft Visio 2010, 2013, 2016, 2019 (WorkPlace Tech 5.10.4 only) Cause There may be one or several of these situations causing this behavior depending on a combination of products installed. The Visio installed is an unlicensed product or in its evaluation period and not registered  The Visio installed is not properly updated There is an error in the WPDispatcher.msi Resolution Review the proper area for the Visio you are using to assure the product is registered; Visio 2010 Visio 2013/2016/2019 If the Visio is part of a subscription-based product, it will be noted as such rather than saying the product is activated. Thoroughly read this Knowledge Base Article for the information required to assure your Visio is properly updated. Workplace Tech 5.9.3 / Workplace Tech Editor (EBO) Microsoft Security Updates required for Visio and Office  To correct any possible WorkPlace Tech or Editor (SBO/EBO) dispatcher problems, Follow the path C:\Program Files (x86)\WorkPlace Tech to the WPDispatcher.msi and "right click / Uninstall" Do this for each version of SBO or EBO installed that has Workstation with WorkPlace Tech Editor.  Here is the path C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation X.Y\WorkStation or C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation X.Y\WorkStation (X.Y will be the version installed i.e 3.1).  Perform the same Uninstall of the WPDispatcher.msi.  The picture below is what will appear if the dispatcher has been removed or was not previously installed.  This message is expected. Open the WorkPlace Tech or the WorkPlaceTech Editor.  The WPDispatcher.msi will run the correct version.

Issue There is a problem after upgrading the SystemDB to N4.10. Product Line TAC IA Series Environment I/A Jace 8000 N4.10 I/A Enterprise Server N4.10 Cause In Niagara 4.10, we upgraded SystemDB from Orient v2 to v3, and as a result of that change, any customers that are utilizing SystemDB on their Supervisor stations will need to re-index accordingly upon upgrading to 4.10. Resolution In Niagara 4.10, the SystemDB has been upgraded from Orient v2 to v3.  Because of this change, customers that are utilizing SystemDB on their Supervisor stations will need to re-index upon upgrade to 4.10.  Please note, re-indexing can take a considerable time upon upgrade, and the DB will not have accurate information when queried until the index upgrade is complete. After upgrading to 4.10, invoke the actions that force system indexing.  Be aware that re-indexing can take some time, and that the DB won’t have accurate information when queried until the index is complete. The following image shows how to invoke execute on the Local System Indexer: If the Station has a DB configured to contain information about points on other stations, the Niagara Network System Indexer should be used, rather than the Local System Indexer.  Additional details regarding indexer actions can be found in the Niagara System Database and System Indexing Guide.

Issue What should be considered when prepairing for upgrading to Niagara 4.10? What known issues should I be aware of when upgrading to Niagara 4.10 and how can I prepair for them? Product Line TAC IA Series Environment I/A Series N4 Enterprise Server I/A Series N4 Jace 8000 Cause Define potential issues with an N4.10 upgrade Resolution The following details a set of upgrade considerations and known issues and their workarounds regarding Niagara 4.10. Please review prior to upgrading to Niagara 4.10. Niagara 4.10 and Default NRE Memory Changes: The increased size of some core libraries in Niagara 4.10 required changes to the default NRE Memory Pool settings for use on a JACE-8000. MetaSpace memory needed to be increased to allow applications to run without issue.   Note: any previous custom memory configuration applied to the JACE-8000 will be reset upon upgrade to 4.10. Prior to upgrading your JACE-8000, please review Default NRE Memory Pool Configuration Changes In 4.10.     Niagara 4.10 System DB Upgrade: In Niagara 4.10, we upgraded SystemDB from Orient v2 to v3, and as a result of that change, any customers that are utilizing SystemDB on their Supervisor stations will need to re-index accordingly upon upgrading to 4.10.   Please note, re-indexing can take a considerable time upon upgrade, and the DB will not have accurate information when queried until the index is complete accordingly. Prior to upgrading your Supervisor, please review System DB Must Be Re-indexed for Upgrades to Niagara 4.10+ from Earlier Niagara.     Niagara 4.10 and Third-Party Modules Keeping your Niagara installations safe and secure is our highest priority. In Niagara 4.10, 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.10, unsigned modules will not execute.   For more information, please review the Niagara documentation on Third Party Module Signing   Niagara 4.10 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.10.   OS, Browser, Database Version Red Hat Enterprise Linux 8.1 (64 bit), 7.7 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.10 Web Launcher 20.4.2 was recently revamped for Niagara 4.10 to include essential software dependencies updates along with critical defect fixes. This version of Web Launcher has Java version 8 update 275 and certificate management has been updated to work with Niagara 4.10 along with any legacy or prospective release.   Prior to using Web Launcher with Niagara 4.10, the customer should update Web Launcher accordingly (see steps below). Updating WebLauncher 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.

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 for assistance. Issue Both the STAT LED and the BEAT LED is off on the Jace controller and cannot successfully ping the JACE 8000 IP address Product Line TAC IA Series Environment I/A Series JACE 8000 Cause The STAT and BEAT LED remaining in an off state is an indication that no SD card is installed in the JACE card carrier.  When the Micro SD card is installed the STAT LED is solid Green, and BEAT LED is blinking Amber. Resolution Make sure to insert the SD card prior to startup commissioning of the JACE 8000. See JACE-8000 Install and Startup Guide

Issue When having issues with a specific NCI (SCPT or UCPT) in a XIF file it can be hard to understand the FILE definition in the XIF file in order to troubleshoot a given issue For information regarding NCI's that are not part of a FILE definition, refer to Understanding the NVVAL part of a XIF file Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment LonWorks XIF Cause The FILE definition can be somewhat cryptic - here is an example   FILE template 0 2 "1.1;" "2,23.24.25.26.27.28.29.30.31.32.33.34.35.36.37.41.42.43.45.46,0\x80,49,2;" "1,1,0\x80,60,12;" "1,1,0\x80,52,2;" "2,0.2.3.5.6.7.8.9.10.16.17.18.19.20.21,0\x80,48,2;" "1,0,0\x80,17,31;" "1,1,0\x80,34,2;" "1,1,0\x80,23,2;" "1,1,0\xA4,169,1;" "1,1,4\x80,3,8;" "1,1,4\x80,5,17;" "1,1,3\x80,1,2;" "1,1,4\x80,4,9;" "1,1,4\xA4,13,1;" "1,1,4\xA4,14,1;" "1,1,4\xA4,15,1;" "1,1,4\xA4,16,1;" "1,1,4\xA4,17,1;" "1,1,4\x80,18,1;" "1,1,0\x80,42,2;" "1,1,0\x80,36,2;" "1,1,0\x80,193,2;" "1,1,4\x80,8,2;" "1,0,3\x80,2,2;" "1,0,0\x84,165,1;" "1,0,0\xA4,166,1;" "1,1,6\xA4,2,8;" FILE value 1 1 116 0x0B, 0xB8, 0x09, 0x1D, 0x09, 0xFB, 0x0B, 0x80, 0x08, 0x77, 0x07, 0x98, 0x06, 0x13, 0x00, 0x02, 0x23, 0x28, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x78, 0x7F, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x80, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0xFF, 0x7F, 0xFF, 0x7F, 0xFF, 0x13, 0x88, 0x00, 0x00, 0x02, 0x0B, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 Resolution The FILE section describes the configuration variables (or SCPT's and UCPT's) for a device. Here is an explanation of the various parts of the FILE section.

Issue Is there a way to get damper position out of a MNL VAV controller? Product Line TAC IA Series Environment WorkPlace Tech Tool Cause The hardware does not provide for direct damper feedback position. Resolution Click on the link below for objects can be added to an existing application to provide a calculated damper position. V2-23012-PosInd for Visio2002.zip

Issue Recommended USB to Serial RS-232 adapter Environment I/A Series R2 UNC’s, G3 ENC’s, MicroNet 2000 MN-CIM, and MicroSmart MSC-LIM. (NOTE: MN-CIM is obsolete as of December, 2011. See Product Announcement PA-000164. There is no functional replacement available) Cause PC or Laptop without RS-232 Serial Port (DB-9 male) connector. Resolution IOGEAR (p/n: GUC232A) has been validated to work in the following applications: 1. HyperTerminal  with a direct connection to the ENC/UNC’s serial port (COM1) using RS-232 adapter and Schneider Electric p/n: UNCC-405 (RJ-45 socket to DB-9 socket adapter, null modem) and CBL-RJ45-** (flat silver satin cable). 2. MN-CIM interface module for use with the TAC MicroNet 2000 series controller interface and Air Balance software. 3. MSC-LIM interface module for use with the DMS MicroSmart Controller Interface (equipment with a handheld port). Click here for product data sheet on the IOGEAR adapter

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 General use of the Wireshark program. Product Line Access Expert, Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Ethernet Networks Cause General Information on using WireShark. Resolution Wireshark is an Ethernet packet analysis programme, Which can be downloaded from: Latest version available from Wireshark Locally stored version 1.0.9 Installing Wireshark If necessary, unzip the WireShark executable file to a suitable location on the PC/Laptop you wish the programme to be installed on. Run the executable file and follow the on-screen instructions. Rules for capturing LAN traffic using Wireshark: Do not use a switch or router to connect the LAN capture PC to the network as these will filter important network activity that you will need to see. You will want to capture everything that is passing over the network at the point of concern. Usually, this means tapping into the ethernet at the Controller or controllers, that is having an issue. midBit-Technologies-LLC-10-100 is an example of a device that can be used to easily tap into the network to take the capture. The monitoring PC must see all traffic from the controller's point of view. The monitoring PC can be connected in either two ways: Connected to the network at the controller The customers IT department can mirror all the network traffic from the controllers port to another port the PC can be connected to. If connected to the network at the controllers, the connection must be made through a true ethernet hub. A hub will not selectively filter important network traffic as a switch or a router will do. More information on what a "true ethernet hub" can be found at http://wiki.wireshark.org/HubReference There are however some switches that feature port mirroring, please see How to Configure a NETGEAR Prosafe Plus Switch for Mirroring. If connected to a mirrored port, the port must mirror 100% of the network traffic to and from the controller. No filtering should be done. Once a complete capture file has been obtained it can be filtered after the fact using WireShark or EtherReal. Using Wireshark Run WireShark Start a trace by choosing the "Capture" menu and then select "Interfaces" Choose the appropriate interface. Generally, this can be identified by its IP Address, but if not, then the packets increasing are an indication. Press the "Start" button. The trace will start and will be similar to the following screenshot. After an appropriate time, the trace can be stopped by selecting "Capture" menu and "Stop" To save the capture file, choose "File" menu and "Save As".

Issue LDAP (Lightweight Directory Access Protocol) Integration of G3 (Niagara) Users with Active Directory Environment I/A Series G3 (Niagara) LDAP Cause None Resolution The Enterprise server or ENC must be part of the site domain before setting up LDAP.  If DNS has been configured proceed to LDAP Configuration Steps.  For further information consult docLdap_3_1.pdf

Issue Information on the MicroSmart Laptop Interface Module (MSC-LIM) Environment DMS MicroSmart Cause Information Resolution Installation / Connection sheet

Issue How to convert earlier versions of Microzone II PSI files to 3.3 revision or later Environment Network 8000 Microzone II, PSI/XPSI Revision(S) 3.13 and 4.1 Cause Error Not a valid application file!  File is not compatible with existing XPSI revision.  It must be upgraded with Zconvert.exe Resolution Procedure on how to convert Microzone II files to revision 3.3 or later and read me file.

Issue How to open an external document (e.g. Word, Excel, PDF) from a G3 graphics page Environment I/A Series G3 (Niagara AX), revisions 3.3 and later Cause N/A Resolution The attached document provides detailed instructions on how to launch an external documents from a G3 graphic.  Click Here to open the document.

Issue Unable to ping the MNB-1000 (Plant Controller) using firmware Revision 1.50E until 1.532  Product Line TAC IA Series Environment I/A Series MNB-1000 (Plant Controller), firmware Revision 1.50E, until 1.532. Cause Common IP (Internet Protocol) ports echo (7), daytime (13) and time (37) are open. Having any of these IP ports open may be a cause of concern for customers that are sensitive to network security issues; these customers include defense installations, financial institutions, and government buildings. Resolution The services using the echo, daytime, and time protocols have been disabled which prevents IP ports 7, 13, and 37 from being open. These services and protocols have no purpose during the normal operation of the MNB-1000. Disabling the echo protocol and closing of port (7) has the side effect that the MNB-1000 cannot be “pinged”. Using the command line program Ping will not detect an MNB-1000 that has firmware v1.50E installed. Use WPCT instead of Ping to verify communications with the MNB-1000. Click here to see the Release Notes for firmware Revision 1.50E. Update; In firmware 1.532, the ping function was re-initiated as the default.  Please see the TPA-IA-19-0004.00 Firmware 1.532 Release Notes.  It is always recommended the highest firmware version available for the MNB-1000 be used.  Many issues have been addressed for better functionality.

Issue Attempting to commission and bind to a Trane lon controller (object name:  Lcir & programID 80:00:CF:07:00:0A:04:05, 80:00:2A:55:00:03:04:0C, and Lcir-DAC 80:00:2A:56:0A:03:04:04. Both processes fail.  An xif file was created directly from the controller using Nodeutil. Click here to view the xif file. Environment Niagara G3 version 3.5.25 Cause The commissioning process concludes with a change of state to the controller ('config/online' to 'offline' to 'online'). The issue is that this particular Trane controller responds to the first requests ('config/online' to 'offline') but fails to respond to the 'online' request (original message plus three retries as defined by the LonWorks protocol) or approximately 400 mSec. In addition, the binding process also utilizes an 'online' to 'offline' to 'online' change of state and has some similar delays within the controller response. Resolution Modifying the Retry Count within the Lon Comm Config settings (from 3 to 6) allows up to 6 retries in the event of a no response for this type of  message. The actual Trane node appears to take a long period of time (over 500 mSec) to respond to the change of state message. This change to the retry count will not affect the bus unless there are bus issues that generate multiple retries. Basically, the change will be not be noticeable on a solid operating bus.