Issue During initial setup, the incorrect ethernet IP address or subnet mask was entered.  Now when rebooting the UNC, I cannot reconnect to it using the I/A Series R2 Admin Tool.  How can the incorrect information be changed? Environment UNC-520 or UNC-410 Cause Network connectivity cannot be established if the IP address or subnet mask was entered incorrectly.  Likewise, if an invalid subnet mask is entered, the UNC may not boot completely (or at all). Resolution The following information is provided in more detail in the section "Determining Network Settings", subsection "JACE-4/5" of chapter 3 of the Niagara Networking & Connectivity Guide.  This document is provided with and installed with the I/A Series (Niagara) R2 software. Required hardware: Serial Cable Terminal Emulator software on computer (such as "Hyperterminal" or "Putty") Procedure: Configure the Terminal Emulator to run at 9600 baud, 8 bits, one stop bit, no parity, hardware flow control Jumper the upper two pins of the Console "MODE" connector,  located in the upper right corner of the UNC-520 circuit board (See photo at right). Connect the terminal emulator via a UNCC-405 serial cable to port COM1 on the UNC and power-cycle the UNC. Wait for the UNC to complete its bootup process (do not break out of the boot process). Check the displayed information to determine what IP address and subnet mask was entered. Power cycle the UNC and when the console display shows "Press any key to stop auto-boot"., press the space bar. Follow the procedure in the section "Determining Network Settings", subsection "JACE-4/5" of Chapter 3 of the Niagara Networking and Connectivity Guide for the procedure to step through the settings changing them if necessary.  Please note that the figure 3-8 may not include all lines of information shown for your UNC. If the serial console is showing any errors after you have verified the IP address / Subnet mask entries, please provide product support with a text copy of the serial console output showing the error messages.

Issue A controller with only 2 available outputs is being used to control a 3 stage device. Environment Three stage device control where lower stages must remain active. Cause Hardware or space limitations may prevent there from being enough outputs to control a three stage device. Resolution Two controller outputs in conjunction with a DPDT (dual pole, dual throw) relay can be configured to control a three stage device. This will allow you to activate stage 1, stages 1 and 2 or all three stages by activating either one or both of the controller outputs. An example of when this might be used is to control three stages of heat or a three stage fan. A standard "ice cube" type relay can be used (IDEC RH2B or similar) and should be wired as shown in the diagram below.   The controller should be programmed to activate only output 1 for stage 1, activate only output 2 for stages 1 and 2 and finally to activate both outputs for stages 1, 2 and 3. Note that certain application specific controllers may not allow the outputs to be configured in the way described above and thus cannot take advantage of this setup.

Issue On an FTT-10 trunk  segment wired in a Loop Topology, where should the LON-TERM1 terminator be installed? The Loop Topology is a subset of the Free Topology. Environment LonWorks FTT-10 network including I/A Series MNL controllers wired in a Loop Topology. Cause Installation detail Resolution In a Free Topology segment, only one termination (LON-TERM1) is required, and may be placed anywhere on the free topology segment.

Issue Using the WPTech Flow Balance software and trying to generate the balance report in HTML format.  When doing this receive  the following warning: Environment MicroNet BACnet Flow Balance Software WorkPlace Flow Balance Tool MNB-V2 Cause Cause has not been determined. Resolution If this “Warning” appears check “My Report” folder”, the HTML may have been created even though the “Warning” was issue. The cause of this anomaly has not been determined at this time. This article will be updated when a solution is found.

Issue During an electrical storm, a component labeled MFC27 was damaged.  It is one of many similar components on the MNL-800 backplane or base circuit board.  What purpose does it serve and which circuit was it a part of? Environment MNL-800 Cause High voltage spikes from an electrical storm.  Sample of MFC damage in image below. Resolution All the MFC components on the backplane are Multi-Function Ceramic (MFC) protectors.  They are designed to absorb high voltage introduced into the circuit to which they are a part of.  In particular, MFC27 protects universal input six (UI 6).   See a sample image of MFC damage below. Although damaged, the backplane can still be used but that specific circuit won't have any further high-voltage protection.

Issue The platform daemon for the localhost displays this error: ERROR   [09:21:09 28-Jun-2011] [tid=712] app registry: app svr_station NOT created, maximum app limit reached All of these stations were part of a migration from one version of G3 to another.  All the station folders were copied and pasted prior to starting Workbench. Environment Niagara G3 version 3.5 and older Cause More than 32 stations are not supported on any G3 platform (3.5 and older).  This is not a license restriction. The 32 station limit applies to the number of station folders on the hard drive under the release directory.  This is only a constraint for engineering the stations.  In Release 3.6, 3.7 & 3.8, the limit is  in excess of 150 "station" folders. Resolution If one computer (running Workbench) is being used to engineer more than 32 stations, then some of the station folders will have to be cut / pasted back and forth with some other temporary folder on the hard drive. Example: A job will have 35 total stations when complete.  In order to engineer them from one computer, 3 station folders will have to be cut out from beneath the parent "stations" folder and put in a temporary folder elsewhere on the hard drive. When there is a need to engineer one of the three cut stations, use Windows Explorer to move it back into the Niagara "stations" folder and remove some other station folder.  Always maintain 32 sub-folders under the "stations" folder. In Release 3.6, 3.7 & 3.8, the limit is  in excess of 150 "station" folders.

Issue When starting communications, a failure occurs generating the errors illustrated below:   Windows cannot find 'CDECHICO.EXE'.  make sure you typed the name correctly, and then try again.  To search for a file, click the Start button, and then click Search.     Environment Tree Tech 3.1 Cause The "Connection Type" for a network in the E: EQUIPMENT DATABASE was assigned as "ARTIC ECHELON". This connection type was used for a communication interface card that was obsoleted many years ago.  It was used with IBM's motherboards using MicroChannel expansion sockets. Resolution Click on the down-arrow and select a different connection type.  The two most-common are:  Ethernet and Serial.

Issue In G3, how to NOT have the AUTO function invoke in a Boolean Writable when the station is restarted?  Environment I/A Series (Niagara) G3 ENCs (all revisions). Cause Default setting of Fallback is check for NULL Resolution In the property sheet of the Boolean Writable object, at Fallback uncheck NULL.

Issue What's the easiest way get a TIP license for Tree Tech 3.1 for legacy panel database maintenance? Environment Tree Tech 3.0 (included with WIBS 1.1) Tree Tech 3.1 Network 8000 DMS Cause Up to four unlock codes are required for Tree Tech: - one for Tree Tech itself - one for the serial driver - one for the Network 8000 ethernet driver - one for the DMS ethernet driver  Resolution In the Purchase program, select the part number in the package list called IV-DEMO-CDE (scroll down to the bottom of the list). Ordering and unlocking this part number will include Tree Tech and the three communication drivers. This is a permanent license and does not expire.

Issue To enable BACnet communications in an I/A Series (Niagara) UNC station, enter a valid instance number. Environment I/A Series  R2 (Niagara) UNC, all versions Cause The BACnet Service in the UNC defaults to instance number = -1, which prevents the BACnet service from communicating. Resolution Assign a valid Instance Number on the General, Config tab of the BACnet service. The valid range is from 0 to 4194302. See the Niagara BACnet Integration Reference, Chapter 1, "Configuring Essential Station Properties", Procedure 1-2, Step 2. Note: In addition to setting the Instance Number, the appropriate Link-Layer must be enabled, eg, "ipEnable = True".

Issue ERROR [Current Date] [AsdNetwork_COM3] Unlicensed: /Drivers/AsdNetwork Javax.baja.license.FeatureNotLicensedException: tac_llc:tacasd Environment I/A Series G3 (Niagara) Asd Driver Cause The issue is caused by a missing certificate. Each license installed needs to have a matching certificate. Resolution Obtain TAC_LLC Certificate Install under License Manager Reboot ENC If issue persists verify the license file name is correct, i.e. TAC_LLC.license.   If it doesn't match this name exactly obtain new license file.

Issue How to connect 2-10 Vdc position output signal of an actuator to an analog input of LON or BACnet controllers. Controller’s Analog Inputs are limited to 0-5 Vdc input. Environment WorkPlace Tech I/A Series Lon (MNL) controllers I/A Series BACnet (MNB) controllers Cause Controller’s Analog Inputs are limited to 0-5 Vdc input. Resolution See the WorkPlace Tech Tool Engineering Guide (F-27254-3) Analog Input object discussion (page 129) for reference. Setting up a 2 to 10 VDC feedback voltage divider, use a 120 K (120,000) Ohm in series with a 100 K (100,000) Ohm resistor; connect the UI across the 100K Ohm resistor. As long as the signal never exceed 10 VDC, the voltage across the 100 K Ohm will never exceed 5.0 VDC. Based on the above test results, 10Vdc [actuator output] = 4.545 Vdc [after voltage divider] 2 Vdc [actuator output] = .909 Vdc [after voltage divider] Set-up the Analog Input Object Linput= 0.909 Vdc LScale= 0 Hinput= 4.545 Vdc HScale= 100 Your values maybe different based on the resistor accuracy.

Issue The TAC I/A Series G3 ASD Driver Installation and Configuration Guide, F-27522, does not describe the Send Group object. Environment I/A Series G3 (Niagara) station containing the ASD driver I/A Series Network 8000 ASD controllers ; MicroZone II, MicroFlo II, LIM, or PEM1 PSI / XPSI to edit database in the ASD controller. Cause Setup not documented. Resolution Basic setup procedure: Verify the configuration of the ASD controller, using PSI: ASD device, Edit, device, Setup, Group # RGRP:n block, where n matches the Group Number in step 1 Edit the G3 station using the Workbench, as follows: In the ENC station, AsdNetwork, Groups (AsdGroup Device); verify Enabled = True verify status = OK  SendGroup object under the Groups. Verify Device Type matches the controller type ( Mz2, Mf2, Lim, or Pem) Verify Group Number is the same as in Steps #1 & #2 above. Set Mbx Input = true;  by either setting Mbx Input Default = true, or by connecting a Boolean Writeable to the Mbx Input

Issue Pinout configuration for a RJ-45 to DB-9 Null Modem Adapter (part number UNCC-405) used for serial integrations to a Niagara R2 UNC or Niagara G3 ENC. Product Line TAC IA Series Environment Niagara R2 UNC-520 Niagara G3 ENC-520 Cause Pinout diagram for wiring Resolution This image details two pinout configurations:  Null Modem and Straight-through.  The Null Modem version is available for purchase using part number UNCC-405.  The Straight-through version is not available for purchase. This image is also part of the UNC-520 Installation Instructions (F-27391)

Issue Installed the I/A Series(Niagara) R2 software on a new Windows computer but cannot get it to connect to an existing UNC that has the same release of the I/A Series R2 software.  One possible error, "Java.io.EOF Exception", that might be displayed is shown below: Another possible error message is an HTTP 401 error. This issue may also prevent the I/A Series R2 tunnel client from connecting to UNC. Environment Computer with any supported version of Windows software including the usual assortment of utility and security / anti-virus software. I/A Series (Niagara) R2 software (any version) installed on the computer. Cause The Windows Firewall and/or Anti-Virus/Internet Security software has been installed and configured such that it is blocking Ethernet communications into or out of the computer on certain Ethernet ports. According to the I/A Series Networking & Connectivity Guide, provided with the I/A Series (Niagara) R2 software, specific user definable Ethernet ports, must be open for two-way communications between the WorkPlace Pro software and a UNC.  If communications is blocked on these ports, the WorkPlace Pro software will not be able to communicate across the Ethernet network. Similar issues are caused by the firewall built into many of the Internet Security software packages.  The following programs have been known to cause port blocking issues: Trend Micro Internet Security - Workstation Edition Trend Micro Office Scan - Workstation Edition Symantec Internet Security Suite version 9 Avast 7 (Free) Antivirus with 30 day demo of Avast Internet Security Bitdefender Antivirus Software Kaspersky PURE 3.0Total Security Kaspersky Endpoint for Business Resolution Verify that the Windows Firewall has been configured to pass bidirectional Ethernet communications over the two required Ethernet ports (default ports are 80 and 3011 - for both the TCP and UDP protocols).  Refer to the online Windows Help for configuration information.  Note that  computers that are members of a Windows Domain may have firewall configuration restrictions enforced by domain policies.  In these situations, it will be necessary to contact the Domain Administrator or facility PC-Help Desk for assistance. Verify that any installed Internet Security software does not block the required Ethernet communications ports.  Some specific Internet Security software packages are known to permanently block the use of some Ethernet ports, for specific uses.  Any Internet Security software of this type must be totally removed from the computer before the required communications can be established.  Three known software packages of this type are the "Symantec Internet Security Suite, version 9", "Bitdefender Antivirus Software" and "Trend Micro Internet Security software".

Issue History Extensions in History Service show a “Fault” Status.  The Fault cause displays: "Duplicate history id:" followed by the name of the object. Environment I/A Series G3, version 3.3.22 and later Cause  By default, history extensions inherit the name of the objects they’re attached to (e.g. CFM).  If CFM is to be trended on multiple VAV units (VAV1, VAV2, etc.), this can cause issues when enabling history collection in the History Service; one or more histories will be in a “Fault” state, with the error message: “Duplicate history id:” for the Fault Cause. Resolution To resolve the issue, the history names can be configured to include the parent folder names:     1.  Open the Program Service in the station’s Services container, and click on the “Find Objects” button at the bottom of the Batch Editor view 2.  In the Bql Query Builder window, select (Custom Type) in the “Of type:” drop-down menu.  Two more drop-down menus will appear.  In the middle drop-down, select “history”.  In the last drop-down, select the appropriate history extension (e.g. NumericIntervalHistoryExt).  Then, click OK.  The Batch Editor view will populate with all of the history extensions in the station for the extension type selected     3.  In the Batch Editor view, highlight all of the history objects, then click the “Edit Slot” button at the bottom of the view 4.  In the Edit Slot window, select “historyName” in the Property drop-down menu.  In the New Value field, type the following:      %parent.parent.name%_%parent.name%     NOTE:  Depending on the tree structure, the filter may need to be modified in order to create a unique history name.  For example, if the network is structured in the following format:   In this example, the object nviSatSwitch1_value is a child of the Points container, which is a child of the device MnlRs3_10. In order to create a unique name for the history extension, the correct filter would need to be:         %parent.parent.parent.name%_%parent.name%.   5.  Click OK.  After a few seconds, the BatchEditor Results window will appear, displaying the objects that were changed.  The history extensions now have unique names, and can be enabled in the History Service

Issue Network scanning software causes a loss of Jace network communication. Product Line TAC IA Series Environment I/A Series Jace 8000 N4.9 and later Cause As network security awareness continues to expand, software-based scanners, such as industry-standard Qualys and Nessus, intended to detect and report on vulnerabilities within internal networks will likely continue to gain popularity.  Today, Tridium is seeing these scanners being deployed and run against Niagara-based platforms like the JACE-8000 and Edge 10.  In some cases, these scans are causing Niagara platforms to become unresponsive or reboot via an Engine Watchdog Timeout, all of which are not acceptable for the critical applications that Niagara facilitates. Resolution While Tridium has no control over how these scanners behave, or how and when they are executed within an organization, Niagara 4.9 introduces a number of changes intended to allow a Niagara-based hardware platform to appropriately respond to the scanning utilities, and also maintain operation.  Below is a brief explanation of how Niagara will function under the different known circumstances currently employed by these scanners, and how to interpret the results.   Recognition of non-Niagara Traffic on the platform In the event a scanner is interrogating a Niagara 4.9+ platform connection, the Niagara Daemon has been modified to recognize non-Niagara traffic over a period of time, shut down the connection if necessary, and wait for a pre-determined amount of time before re-enabling connectivity.  Under these conditions, a scanning utility may report that the Niagara instance has encountered denial of service, when in fact, Niagara has simply disabled the communication mechanism by which the scanner was attempting its interrogation. During this time, normal platform communication will also be affected; however, the Niagara platform and station will continue to run.   Prioritization of Internal vs. External Communication on the Niagara station In the event, a scanner is interrogating a Niagara 4.9+ station (external communication) and Niagara detects that this interrogation may cause an Engine Watchdog Timeout, the station’s web server will be stopped and restarted. Under these conditions, a scanning utility may report that the Niagara instance abruptly stopped communicating, and may have encountered denial of service.  During this time period, normal/expected client web connections to the station will also be affected; however, the Niagara platform and station will continue to run. As mentioned, these scanners are outside the control of Tridium, and likely always evolving to meet the needs of the various threats they are intended to protect against. As a best practice, Tridium recommends not scanning in production if possible, as any findings would be just as legitimate during scheduled downtime. Additionally, it may be prudent to work with the scanning tools to configure the appropriate priority of a scan, as the intensity of which you scan a production multicore, failover redundant web server host, is likely not the best choice for scanning a single-core JACE. Should you encounter an issue with a network scanning utility and Niagara 4.9 and above, please contact your support organization.

Issue The following error occurs on startup following upgrading of Niagara Station to  4.10.   SEVERE [20:42:01 23-Oct-20 UTC][nreconfig] invalid nre memory configuration values, 832 > 816   Product Line TAC IA Series Environment I/A Jace 8000 N4.10 Cause The default NRE memory pool settings are incorrect after an N4.10 upgrade and need configuration to function correctly. Resolution Niagara 4.10 and Default NRE Memory Pool 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. The overall size of the pool of memory available to the NRE installation has decreased.  T As the overall size of the pool has decreased, customizations based on the old total pool size are invalid and cannot be maintained.   If a custom memory configuration is required, the user will need to manually adjust the platform administration menu after a device is upgraded. A longer-term approach to address this issue is in development and should be available with the Niagara 4.11 release.   NRE Memory pool default settings for Niagara 4.9: Changes to the default configuration: Heap Space size 4.9 value: 384 MB 4.10 value: 360 MB Meta Space size 4.9 value: 48 MB 4.10 value: 56 MB System reserve 4.10: allocated additional 16MB NRE Memory pool default settings for Niagara 4.10:

Issue Some helpful basic IP commands. Product Line Other Environment Computer with IP NIC or Network Cause Need for basic IP configuration or IP address Resolution Go to start, click run and type in "cmd". This takes you to the command prompt. Type in: "ping xxx.xxx.xxx.xxx" to see if your device is online and its response time. Make sure you put the space between "ping" and "xxx". "ipconfig" and hit enter to get the info of the computer you are currently using. You'll get the IP address, subnet mask and the gateway. "ipconfig/all" and hit enter to get more info on the machine your using. It will give you all the above and then some including the DNS server addresses. "tracert xxx.xxx.xxx.xxx" and hit enter and you can see the servers that you are going through to get to your destination. This can be used when connecting to a Loytec or a iLon and the IP address is being presented to the L-IP or iLon is unknown. Connecting through a firewall/gateway/NAT server, you are not presenting the PC's address - when you do the tracert you will go through your gateway and the next address will be the IP you are presenting- Use this in the iLon as the LNS server address.

Issue What is the contact information for Barber Colman Dyna group? What is the contact information for Barber Colman Aerospace division? What is the contact information for Barber Colman Industrial Instruments division? Environment Barber Colman Cause The old Barber Colman Dyna group is now a part of Woodward Governor. The old Barber Colman Aerospace division is now a part of the GE Aerospace. The old Barber Colman Industrial Instruments is now part of Eurotherm, an Invensys company. Resolution Barber Colman Dyna group is now Woodward Governor. They can be reached at 800-543-5811 Barber Colman Aerospace division is now GE Aerospace. They can be reached at 815-637-3500 Barber Colman Industrial Instruments is Eurotherm, an Invensys company. They can be reached at 815-637-3222 or 815-637-3404 for tech support.