Issue In MNB-1000 with firmware Revision 1.50E, the Router Table can be viewed and /or reset without resetting the Plant Controller. This allows users to clear table entries that could cause router problems, without needing to reset the MNB-1000. Product Line TAC IA Series Environment I/A Series MNB-1000 (Plant Controller) with firmware Revision 1.50E, or later. WorkPlace Tech Tool, Commissioning Tool (WPT CT) version 5.7.7 and later Cause Product enhancement. Resolution To view or reset the Router Table, choose from the following procedures, depending on the version of firmware: For MNB-1000 with Revision 1.50E, use a web browser to access the Plant Controller to view or clear its Routing Table. Click here to see the Release Notes for Revision 1.50E, for more details. For MNB-1000 with Revision 1.510, use the WorkPlace Tech Tool Commissioning Tool, version 5.7.7.  Go to the Device Properties, Diagnostics Tab, and Router Table Information button. Click here to see the Release Notes for WPT 5.7.7, for further details.

Issue A Niagara G3 server station was running well for a long time.  Then in a matter of a couple of days, the station began failing to run.  The error listed in the Application Director Output is:   ERROR [java.lang.OutOfMemoryError: GC overhead limit exceeded 13:46:17 20-Mar-14 EDTjava.lang.OutOfMemoryError: GC overhead limit exceeded][sys.leasejava.lang.OutOfMemoryError: GC overhead limit exceeded] Error in run Product Line TAC IA Series Environment I/A Series G3 Enterprise Server Cause There is not enough memory allocated to the Java Virtual Machine (JVM). The email service is keeping a very large outbox because the network email server's IP address was changed. Resolution Increase the Java Virtual Machine (JVM) memory allocation Using a text editor, open the nre.properties file (located in the niagara 'lib' subfolder on the server hard drive). Locate the line: java.options=-Xmx256M. Change it to java.options=-Xmx512M. Empty the outbox file (i.e. delete it) and/or update the email server's IP address.

Issue WPT and WPTE require certain Microsoft Security updates for Visio and for Office running on the host machines. Issues currently observed: Different and various functions in the fluent ribbon do not work or the ribbon does not appear. The following error "Application compile failure during save operation" is seen when saving/compiling an application in WorkPlace Tech Editor Product Line EcoStruxure Building Operation, TAC IA Series Environment Visio 2010, 2013, 2016, 2019, 2021(.msi install)  Visio 2013, 2016, 2019, 2021 (subscription "Click to Run", Plan 2) Office 2010, 2013, 2016 (.msi install) Office 2013, 2016, 365 (subscription "Click to Run", Plan 2) Support for Workplace Tech 5.10 / previous and Workplace Tech Editor Note: Visio 2019 and Visio 2021 are not supported in 5.9.4 or EBO versions before EBO 2022.  Visio 2019 and Visio 2021 are supported when using Workplace Tech 5.10.x and EBO 2022. Cause Interoperability of Visio and Office can cause problems with Workplace Tech and Workplace Tech Editor if these MS16-70 updates are not applied.  If the Office / Visio product is "Click to Run" the software has not been updated to the latest version. Resolution Install the updates from Microsoft Update Catalog To use the catalog, copy and paste the KB number into the "search".  Always select the 32-bit version of the update. Visio 2010 32 bit KB3114872                Office 2010  KB3115198 select 32 bit  Visio 2013 32 bit KB3115020                Office 2013  KB3115173 select 32 bit  Visio 2016/2019 32 bit KB3115041       Office 2016  KB3115144 select 32 bit Visio 2016/2019 32 bit KB4484333 NOTE:  If the Visio or Office is "Click to Run" (subscription such as Office 365, Plan 2) rather than from a Microsoft Office .msi, the product should be upgraded by using the Update Options feature If you try and install the KB/.msi install patches, you will get this message

Issue What diagnostic information is available within Niagara that can be sent to Product Support or acted on locally? Product Line TAC IA Series Environment I/A Series Enterprise Server I/A Series Jace Cause Jace or Enterprise Server operating slow or specific problems are causing the need for debugging a station or platform Resolution There are several diagnostic tools available: Check the station Resource Manager Right-click on the station and select "Views - Station Summary" This will open up a resource monitor page where you can check CPU and memory usage.  The CPU should not be consistently above 80%.  Spiking is common as the process is executing and completing tasks.  There are other things easily referenced here also. Heap memory will vary as well.  It can slowly increase until a garbage collection cycle releases unused heap back to the pool.  You should never use more than 75% of the total available heap memory. Heap Memory is primarily used by station modules and java program objects, so if the memory usage is high, these 2 might be the main reasons Engine Hogs   Right-click on the station, and select "Spy". From the main view, click on "sysManagers". Click "engineManager" and then scroll down to find "Engine Hogs". Clicking Engine Hogs will open a list of the main components of the station and a column on the right-hand side will display the average execution time of the component. Review the top 10 or so and see if any are taking an extraordinary amount of time.  This can help to locate improperly executing objects. Driver Poll Rates Drivers that are based on polling data, like BACnet when COV is not enabled, or Modbus constantly run commands to read data based on the fast, normal, and slow configured rates.  Open the Poll Service under the network the points are being polled on. Looking at the property sheet of the driver, it is important to verify that the cycle time (1) for each rate (fast/normal/slow) is always equal to, or below the actual time configured (2) for that rate. The defaults are 1 second for Fast Cycle Time, 5 seconds for the Normal Cycle Time and 30 seconds for the Slow Cycle Time. Seeing a longer cycle time is usually an indication that the network is saturated with commands and may cause the Jace/Niagara controller to be slow with heavy use of controller resources.  There are several ways to correct this: changing the polling rate spreading the number of objects being polled at each rate, etc. In this example, all points (3) are in the "normal" bucket. Application Director console The "Application Director" (under "Platform") shows a live console output.  Open it by clicking the option under the platform Copy the content of the Application Director, or "stream to file" to send the content to support. It will be essential to help the support engineer to understand the problems in the station.  Add more debug information to the Application Director console You can add more granularity to the messages in the Application Director for a deeper look into possible issues. This can be accomplished in 2 different ways: Right-click on the station, and select "Spy". Then, select "logSetup" on the main view From the list that appears, you can scroll and find appropriate topics to log and you can select at what level you want the information to appear.  This will add traffic to the application Director window so be careful how "fine" and how many logs you enable.  It might be good to consult with support before enabling these logs. example; bacnet.debug/finest if you select this box. Debug Service   Select the "DebugService" from the station "Services" In the Log Category, type a few letters of the topic and scroll to find what you are interested in logging From the pulldown menu, determine the granularity of the log Click the plus Click "Save" Setting this logging and streaming the output to a file will allow information to be sent to support for better diagnostics if required.  Remember to set this logging back to "Default" when done so the Application Director is not overwhelmed with information when you are only trying to view normal station activity.

Issue LON card indicates fault (unique name required) when multiple LON cards are installed in the JACE-6E, JACE-7 or Jace 8000 Product Line TAC IA Series Environment I/A Series G3, JACE-600, JACE-600E, JACE-700 I/A Series N4 JACE 8000 Cause The default name when adding a LON network to the G3/N4 station is LON1.  Both networks will attempt to use the same LON card (LON1) causing a fault condition. Resolution Under each LonNetwork within the Lon Comm Config, specify a unique device name for each card or network (LON1 and LON2).  In the case of the JACE 8000, a total of (4) LON modules is acceptable but would not be advised.  Continue with LON3, and LON4 if required.  

Issue Niagara 4.9 (or later) sometimes has a new Host ID that differs from the Host IDs of other versions of Niagara that were installed on the same host PC Product Line TAC IA Series Environment I/A Series N4 Enterprise Server Cause Niagara 4.9 and later, are only available in a 64-bit version. The older Niagara versions installed on the host PC are probably 32-bit versions, which will always have Host IDs different from 64-bit versions. Resolution If the older versions are Niagara 4.3 or lower, you may need to update the older versions, as per the following document… I/A Series G3 and N4 Eliminating multiple HostID on a single PC  Niagara 4.9 (or later) is only available in a 64-bit version.  The other Niagara versions installed on the host PC are probably 32-bit versions, which will always have Host IDs different from 64-bit versions.  In this case, the host PC will require one of the following Un-installing the 32-bit versions and re-installing 64-bit equivalents One license, to be "transferred" to a different Host ID when necessary Multiple licenses, one for each unique Host ID.

Issue N4 software installation stops because; azul-zre-compact3-qnx7-arm tridium-qnx7-n4-titan-am335x software is missing Product Line TAC IA Series Environment I/A Series N4 Jace 8000 Cause A valid license including the features that meet the dependencies is not installed. Resolution Install a valid license containing the jre8J8000Azul, jre8Qnz7Zulu and qnx7, jreQnx7Zulu features before attempting to commission the Jace 8000

Issue Can report generation be scheduled in a Niagara G3 (AX) station? Product Line TAC IA Series Environment Niagara G3 (AX) station Cause Set the report schedule in the Export Source Object. Resolution Reports can be generated at scheduled times: Add an Export Source object (from the Report Palette) to the Report Service. Double-click the Export Source Object and set the built-in schedule to the desired time and frequency (e.g. 6:00 AM Daily) Click the chevron near “Source” and browse to the ReportPx file. Click “Next” and choose PxView to Pdf in the Exporter field. Then click “Finish.” Drag an Email or File Recipient to the Report Service and link the Export Source to the Recipient. Set up the Email Recipient with email addresses. Set up the File Recipient with a folder for the file. Force an export by right-clicking the Export Source object and choosing “Actions – Generate”.

Issue In a Niagara G3 station, what is the difference between a Station Save and Backup Station? Product Line TAC IA Series Environment Niagara G3 (AX) Jace/ENC Niagara G3 (AX) Enterprise Server (ENS)  Cause Help determine which feature (Station Save and Backup Station) meet the requirement. Resolution A Station Save only saves the config.bog file to the local device (if an ENC, it will save the file on the ENC; if an ENS, it will save it on the ENS computer).  The Backup Station function performs a complete backup of the connected ENC or ENS station, saved as a dist file on the Workbench computer. The backup dist contains the entire station folder plus the specific NRE config used by that ENC or ENS platform, including license(s) and certificate(s). The dist also contains pointers to the appropriate NRE core, Java VM, modules, and OS. If ever needed, you can restore a backup dist using the platform Distribution File Installer view. The backup dist file also contains the TCP/IP configuration of the host when it is backed up. When restoring the backup, the choice to restore these settings, or retain the TCP/IP settings currently in use by the target host is available.

Issue MSTP controllers go offline when changing the MaxMaster value in the Automation Server from it's default of 127 Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server MSTP Master Controllers Cause The MaxMaster value is being set lower than some or all of the MSTP controllers on the network Resolution EcoStruxure Building Operation supports MSTP Master controllers in the address range 0-127 (often refered to as the node id). The MSTP network is a token passing network where the token is passed around the network, until a controller has the token it cannot 'talk' to other devices.   The MaxMaster value is defaulted to 127 to allow all devices on the network to receive the token and reply to online status requests, send values etc. If the MaxMaster value is less than any of the MSTP Master controller addresses then those controllers never receive the token and cannot respond to online status requests.   The value for the MaxMaster needs to be equal to or greater than the highest addressed MSTP controller node id.  For example, if the highest node id=54 then the MaxMaster will need to be set to 54 or higher. For maximum efficiency the MaxMaster should be set 1 or 2 greater than the highest controller address, this allows for adding future devices without needlessly polling for many non-existent devices.    Please refer to BACnet MS/TP Network Properties – Basic Tab or Configuring the MS/TP Network for b3 Communication 

Issue How to configure a G3 station as a BACnet BBMD Product Line TAC IA Series Environment I/A Series G3 version 3.3.22 and later Cause Documentation Resolution In the G3 Station, expand the BacnetNetwork, expand Bacnet Comm, expand Network, and then double-click IP Port.  The IP Port Property Sheet opens (see below)   In the IP Device Type drop-down, select Bbmd.  Click Save The station is now configured as a BACnet BBMD

Issue Too much LON communications traffic can cause LON communications errors. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series MNL 800 Building Operation Automation Server Premium LON Network  I/A Series R2, AX, N4 Jace LON Network Cause Sending output LON SNVT values too frequently or more often than reasonably needed. Resolution There are a series of NCI (configuration) objects that control the transmission and reception of these data values on the LON network. One of four NCI objects (nciSndHeartBeatA, B, C, or D) is assigned to each NVO object in the application program. This value regulates the periodic LON transmission queuing of the NVO object values for each binding. One of four NCI  objects (nciRcvHeartBeatA, B, C, or D) is assigned to each NVI object in the application program. This value regulates the fallback timeout for each NVI object value. If a value is not received via the binding in this time period, the NVI object value will revert to its application-defined default value. In an MNL-800 controller, there are two additional NCI objects that are used to regulate the flow of data onto the LON network. The nciMinOutTime object is used to throttle the transmission of all data values queued to be sent via bindings over the LON network. This NCI object sets the transmission time interval between each NVO value being sent on the network. The important fact here is that the product of the number of bound NVO values times this interval (nciMinOutTime) must be LESS than the shortest nciSndHeartBeatX (X=A, B, C or D) interval. For example, if the Send HeartBeat is set to the default of 120 seconds and there are 60 NVO SNVTs bound from this controller, the nciMinOutTime must be set to a value of fewer than 2 seconds.  The recommendation for setting this SNVT value one half the shortest nciSntHrtBr divided by the number of NVO SNVTs bound from the controller.   The nciMinPropTm object is used to regulate the transmission queuing of changing bound NVO object values. This timer acts as a time-based filter to prevent a rapidly changing NVO value, such as a constantly changing temperature, from overwhelming the communication capacity of the LON network. Typically this value is set to a value of 1 to 5 seconds. Additional information can be found in Chapter 6 of the WorkPlace Tech Tool 4.0 Engineering Guide (F-27254). BACKGROUND: This section is provided to give the reader a basic understanding of bound LON communications, as applied to LON controllers in general. Data communications across a LON network is accomplished by using a LON Network management tool to create a binding between a device with a data source (NVO object) and one or more devices with data receivers (NVI objects) in other LON controllers. The device containing the data source will send the bound data value at a periodic rate, as defined by the associated SendHeartBeat NCI object, and whenever the value of that object changes. If the NVI object does not receive a value from the sender (bound NVO object) within a specified time period, as defined by the associated ReceiveHeartBeat NCI object, the NVI object will use a local fallback value until such time as it receives a new value via the binding.

Issue The Universal Input real-time values on a MNL-800 (or Microzone II) are fluctuating unrealistically.  They rise, peak, drop, valley and then start over again very quickly.  It is similar to an AC wave pattern. It is happening with all the inputs no matter their configuration. Product Line TAC IA Series Environment MNL-800 Microzone II (Network 8000) Cause When an actuator is interfaced with a MNL-800 (or MicroZone II), and the UI cable shields are connected to earth ground (the SHLD terminal), the shield has a common mode AC potential that couples to the UI input. Only a very small signal (UI shield to signal common) is needed to result in objectionable UI signal fluctuation. Resolution Connect all drain shields on UI inputs to UI common (C terminal). Read additional solutions and a more descriptive cause in Technical Bulletin 01-36.

Issue How can a BACnet system be customized to maximize data throughput?  The site has a Niagara R2 Enterprise Server and a UNC with a variety of MSTP controllers connected to the UNC. Environment Niagara R2 Enterprise UNC MSTP controllers Cause Improper configurations won't achieve optimum performance. Resolution This can be a relatively complicated question, however, there are a number of basic steps that can be taken in terms of best practices to enhance performance. Within the UNC station, any BACnet objects that are not needed are to be deleted. During the learn of a BACnet controller, many objects are learned that are not used. All BACnet objects when learned into a station are placed in Poll-Always containers. All but the most critical objects, schedules and trended objects are to be moved to Poll-on-Demand containers. All controllers on the MSTP bus should be consecutively addressed.  Gaps in addressing add delay in communications. The MaxMaster setting in all controllers, including the UNC, is to be set to a numeric value two greater than the highest MSTP controller address on the network. To leave MaxMaster at 127 but only have 20 controllers on the network will also add delays in communications looking for the other non-existent 107 controllers. The MaxInfoFrames setting in the UNC or MNB-1000 is to be set to a number higher than 5 but no more than 20. This setting determines how many pieces of information can be requested each time the UNC or MNB-1000 receives the token on the MSTP bus. The default value is 1 and if left at this value the system will be sluggish with updating values on graphic screens. The range of 5 to 20 is given as a starting point for experimenting and each system will be different depending on the number of controllers and what data is being requested.  Lab tests have shown there is a performance curve with an optimum point.  Starting at a value of 5, performance increases as the value increases.  Performance will then peak and any further increase to the setting will result in a performance reduction.  As a result, stay above 5 but less than 20. Refer to the document titled "I/A Series MicroNet BACnet Wiring, Networking, and Best Practices Guide" (F-27360) for additional information.

Issue What is Domain Name Service (DNS)? Product Line Andover Continuum,EcoStruxure Access Expert,EcoStruxure Building Expert,EcoStruxure Building Operation,EcoStruxure Security Expert,Satchwell BAS & Sigma,Satchwell MicroNet,TAC IA Series,TAC INET,TAC Vista Environment TCP/IP Networks Cause DNS is a distributed hierarchical system for resolving host names into IP address. Under DNS, there is no central database with all of the Internet host information. The information is distributed among thousands of name servers organized into a hierarchy similar to the UNIX file system. DNS has a root domain at the top of the domain hierarchy that is served by a group of name servers called the root servers. Source: TCP/IP Network Administration by Craig Hunt, O’Reilly & Associates, Inc. Resolution Short for Domain Name System (or Service or Server), an Internet service that translates domain names into IP addresses. Because domain names are alphabetic, they're easier to remember. The Internet however, is really based on IP addresses. Every time you use a domain name, therefore, a DNS service must translate the name into the corresponding IP address. For example, the domain name www.example.com might translate to 198.105.232.4. The DNS system is, in fact, its own network. If one DNS server doesn't know how to translate a particular domain name, it asks another one, and so on, until the correct IP address is returned.  

Issue When using CIDR (Classless Inter Domain Routing) or Supernetting it is not always obvious what range of IP addresses can be used. Product Line EcoStruxure Building Operation Environment Device Administrator Building Commissioning Tool Cause When subnet masks with values other than 255 are used it is not always obvious what is the range of valid IP addresses allowed.  There is a need for an easy way to determine the range of valid IP addresses for the Subnet Mask being used. Resolution The IP address range can be calculated mathematically but the simplest method is to use a subnet calculator.  The website links below are both examples that will calculate the range of valid addresses for any specified subnet value.   http://www.subnet-calculator.com/cidr.php https://www.calculator.net/ip-subnet-calculator.html   Visit either of the websites for a CIDR / Supernet calculator, enter an IP addresses in the network along with a subnet mask and the calculator will provide the range of addresses that can be used within the subnet.   In addition to online calculators, a number of different subnet-calculator programs are available for Android, Apple and Windows Smartphones.  

Issue What is throttling range? Product Line TAC I/A Series Environment I/A Series controllers Cause Setting a proper throttling range will allow for more accurate control of external actuators and devices. Resolution Throttling range is the amount of change in the process variable that is necessary to cause the controller output to change from 0 to 100%. The controller output may be 4-20mA, a voltage range, or pressure range.

Issue BACnet MSTP Capture Application Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment Any Bacnet MSTP Network Cause The BACnet MSTP capture application provides the ability to analyze data communications between devices anytime issues are suspected on the network. Resolution Download the latest version. Browse to Steve Karg's  BACnet Protocol Stack - Browse /bacnet-tools at SourceForge.net Select the version folder Select bacnet-tools-[n.n.n].zip file to download it From the zip file, extract mstpcap.exe Now you can use it via command prompt as described below or install it in C:\Program Files\Wireshark\extcap if want to use with modern Wireshark version.   To capture data follow these steps: Unzip file Open command prompt with window pointing at location of mstpcap.exe file.  For example:  c:\MSTP Tool> Daisy chain RS-485 adapter to trunk or connect Roam I/A to jack on MNB device. Command syntax is as follows:  mstpcap comx baudrate# do not type baudrate just speed. Control C to stop Example: If Using Roam I/A it requires highest baudrate available on the interface. ROAM I/A Serial port mstpcap comx 115200 If using Roam I/A Bluetooth mstpcap comx 76800 If using an RS-485 adapter it will not support 76,800. This is a PC hardware limitation not a software limitation for further information or instructions on how to use baudrate 76,800 consult text file titled mstpcap.txt or Steve Karg's website: http://steve.kargs.net/bacnet/wireshark-and-bacnet-mstp .  Example: mstpcap comx baudrate speed The capture file can be analyzed with WireShark Protocol Analyzer.  WireShark software is available at: http://www.wireshark.org

Issue A Niagara G3 station (version 3.5.25) reports the following error in the Application Director Output (full text version of error): ERROR [10:41:43 09-Mar-12 CST][sys.engine] Cannot start component: false {ok} javax.baja.sys.IllegalNameException: Illegal name "booleanSwitch.invalidInSwitch".    at javax.baja.naming.SlotPath.verifyValidName(SlotPath.java)    at javax.baja.sys.BFacets.make(BFacets.java)    at javax.baja.status.BStatus.make(BStatus.java)    at javax.baja.status.BStatus.make(BStatus.java)    at com.tridium.kitControl.util.BBooleanSwitch.onExecute(BBooleanSwitch.java)    at javax.baja.control.BControlPoint.doExecute(BControlPoint.java)    at javax.baja.control.BControlPoint.fw(BControlPoint.java)    at com.tridium.sys.engine.EngineUtil.descendantsStarted(EngineUtil.java)    at com.tridium.sys.engine.EngineManager.start(EngineManager.java)    at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)    at javax.baja.sys.BComponent.start(BComponent.java)    at com.tridium.sys.engine.EngineManager.start(EngineManager.java)    at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)    at javax.baja.sys.BComponent.start(BComponent.java)    at com.tridium.sys.engine.EngineManager.start(EngineManager.java)    at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)    at javax.baja.sys.BComponent.start(BComponent.java)    at com.tridium.sys.engine.EngineManager.start(EngineManager.java)    at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java) Product Line TAC IA Series Environment Niagara G3 Cause There is a known issue with version 3.5.34.2 of the kitControl module:  An error occurs when "null" is used as the value for "inSwitch" Resolution Upgrade to version 3.5.39 of the kitControl module.  Click here to download a copy or visit niagara-central.com (downloads).

Issue In an I/A Series G3 station, is there a way to relocate a history from one parent history container to another without losing history data? In addition, can the associated history ID be modified to allow new data to log and append into the relocated history? Product Line TAC IA Series Environment I/A Series G3 (Niagara) station Cause Sometimes a user will want to move a history to a different folder. Resolution See the procedure illustrated with screen captures.