Issue What are the three serial tunnel clients included with the latest release of Niagara G3? Environment 3.6.47 and higher Cause How to choose which serial tunnel client is required. Resolution For Windows XP SP3 32-bit, use Install_Serial_Tunnel.exe   For Windows 7 32-bit, use InstallVserialAx2.exe   For Windows 7 64-bit, use InstallVserialAx2_64bit.exe  

Issue Unable to import and install an ENC/JACE license using I/A Series G3 Workbench 3.8.37 by requesting through the license server. The result is a dialog box with information on where to email host ID information to obtain a license. Environment I/A Series G3 Workbench 3.8.37 only Cause A parameter within the brand.properties file has been inadvertently set to bypass the online request. Resolution Modify the parameter within the brand.properties file as follows: Use the Windows Explorer and navigate the \niagara-3.8.37\lib directory Open and edit the brand.properties file with a text editor Modify the following line: license.onlineRequest=false to license.onlineRequest=true Save and close the file Close and open Workbench

Issue On a old MNL project, a MNL-MI device was found. Is it required to integrate into SmartStruxure? Environment SmartStruxure with MNL Cause Outdated LON product Resolution The MNL-MI provided network-level management functions for a network of MNL controllers.  An RS-232 port on the MNL-MI provided for a connection to a computer running the MicroNet Tech Tool or MicroNet View software (both obsolete).  It is not required for a SmartStruxure integration and can be removed from the LON trunk.

Issue An existing Niagara R2 Enterprise Server was upgraded to 535 but the Vykon Alarm Client (version 2.5) cannot connect to the server. Environment Niagara R2 Cause The Server Name in the Vykon Configuration Utility must be the server's IP address and NOT the station name nor the Windows' Computer Name. Resolution See the VAS_InstallationConfiguration Guide for more details.

Issue The first time a WB-profile user connects a web browser to an I/A Series G3 station, the user is prompted to download software from Oracle. Product Line TAC IA Series Environment I/A Series G3 (AX), version 3.8.xxx Cause An earlier version of I/A Series G3 used an open-source library for 128 or 256-bit encryption.  I/A Series G3 version 3.8.xxx migrated to the Java Cryptography Extension (JCE) that requires the installation of add-on files from Oracle. Resolution Download the required files from Oracle. Depending on your version of Java, download either ... JRE8 ... http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html JRE7 ... http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html Otherwise, navigate to the Oracle download website and search for the links to "Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files" for your Java version ... http://www.oracle.com/technetwork/java/javase/downloads/index.html Accept license and download. This may require registration or sign in to Oracles website. Locate the Correct Java Folder on Your PC Where the Software Must Be Installed. Launch... Windows > Control Panel > Java In the Java Control Panel, navigate to the "Java" tab, and then click "View" to see the installed Java version. The name of the folder where Java is installed precedes the "bin\javaw.exe" in the text. "JavaHome" is what this document will call that folder, no matter what the full name is. In the example below, the folder name appears as "C:\Program Files\Java\jre?" -- the obscured last character will be 7, or 8, or some other number, depending on the installed Java version. Install the Files on Your PC Use Windows (File) Explorer to navigate to the Java jre folder path as shown in the step above. From the jre folder, navigate to the lib\security\ folder. Copy the local_policy.jar and US_export_policy.jarfiles contained in the Oracle download and replace the older version files. Clear the web browser's cache Delete the contents of the C:\Users\username\niagara folder. Clear the java cache (Control Panel => Java => Temporary Internet File "Settings" => Delete Files => check installed apps and applets => OK Re-start the web browser NOTE: This procedure will need to be performed on each computer accessing the I/A Series G3 station via a web browser.

Issue Is there a way to determine which version of Operator Interface is installed without actually running the program? Environment DMS Operator Interface Cause Determine the version without running the program Resolution Open the file LANGUAGE.TXT in the DMS folder using Notepad and line 12 will indicate the version installed:

Issue The Niagara Tunnel service in Windows 7 indicates that it is started; however the tunnel window will not pop-up Environment Niagara R2 version 5.35, Windows 7 32-bit. Cause The Interactive Services Detection service is disabled. This service must be enabled for the tunnel client to work.  Resolution Verify that Interactive Services Detection is started.  Set the service to automatic, start it, and re-boot the computer.   

Issue Station down station up alarms are constantly generated even though the Enterprise Server and UNCs are not actually down. A station up alarm for the same station was generated within a short period of time (seconds).  Environment I/A Series R2 Enterprise Server and Universal Network Controllers Cause A station down alarm will be generated if the station does not respond within the timeout configured for the station.  Resolution In a station's AddressBook, the entry for a station has a 'Monitor' checkbox. A station down alarm is generated if the station does not respond within the timeout configured for the station in the AddressBook entry. The timeout by default is 1 minute. This can be increased if false station down alarms are being generated. You can also disable the station monitor if required. 

Issue After installing the Niagara AX Lon Tunnel Client, the service fails to start and Windows displays the following error: Could not start the NiagaraAX Serial Tunnel service on Local Computer. Error 1068: The dependency service or group failed to start. Environment I/A Series AX Lon Tunnel Client Cause There are two possible causes of this issue. The LON port specified is already in use and assigned to a physical LON adapter.  The LON adapter assigned to this port may not necessarily be currently installed into the computer. One of the underlying Windows functions or services required by the AX Lon Tunnel is not installed or is corrupted. Resolution To verify that the LON port you have selected is not already installed in the computer, perform the following steps: Open the "LonWorks Interfaces" applet from the Windows Control Panel (Procedure describes operation with OpenLDV 4.00 installed.  The procedure for OpenLDV 3.20 or OpenLDV 3.40 is similar to what is shown in the following steps. Under the "View" menu, insure that "Show detached interfaces" is checked. Select a LON port that is not already shown in the list and enter it in the "Lon Port" field of the "Niagara AX Lon Tunneling" Windows control panel applet. If the LON port name is valid and the NiagaraAX Lon Tunnel service still displays the 1068 error message, an issue could be occurring with another Windows service or DLL file.  Microsoft provides a method of diagnosing and possibly correcting this type of issue. Open the Windows Start Menu and in the "Search Programs and files" box enter the command:       cmd In the Command Prompt window, type in the following command:       sfc /SCANNOW This command "scans integrity of all protected system files and repairs files with problems when possible". In the event that this process finds an uncorrectable issue, the program will stop, displaying an appropriate diagnostic message.

Issue Niagara G3 Serial Tunnel to Microsmart > correction in the Installation and Configuration Guide (F-27523). Product Line TAC IA Series Environment Niagara G3 MicroSmart Driver Cause A documentation error Resolution A serial tunnel is included with the MicroSmart Network (see below): There is no need to add a SerialTunnel to the station as illustrated in the manual on page 22: The TunnelService is still required in the Services folder.

Issue The I/A Series G3 Modbus TCP slave device is unable to establish communications with a Modbus client requesting a unit identifier of 255.  The ENC/JACE rejects the message because the Modbus TCP slave device address can only be configured with a value between 1 to 247. Environment I/A Series G3 (all versions) Cause The Modbus TCP slave device address can only be configured with a value between 1 to 247 and Workbench will generate an exception if a value outside this range is entered and saved. Per the Modbus TCP standard, the Modbus TCP/IP Application Data Unit (ADU) takes the form of a 7 byte header (transaction identifier, protocol identifier, length field, and unit identifier) plus the protocol data unit (function code + data). The 7 byte MBAP header includes the following fields: Transaction/invocation Identifier (2 Bytes): This identification field is used for transaction pairing when multiple messages are sent along the same TCP connection by a client without waiting for a prior response. Protocol Identifier (2 bytes): This field is always 0 for Modbus services and other values are reserved for future extensions. Length (2 bytes): This field is a byte count of the remaining fields and includes the unit identifier byte, function code byte, and the data fields. Unit Identifier (1 byte): This field is used to identify a remote server located on a non TCP/IP network (for serial bridging). In a typical Modbus TCP/IP server application, the unit ID is set to 0 or 0xFF (255), ignored by the server, and simply echoed back in the response. Resolution The I/A Series G3 Modbus TCP slave device address can only be configured with a value between 1 to 247 and Workbench will generate an exception if a value outside this range is entered and saved.  The workaround is to configure the value as follows. Right click on the ModbusTcpSlaveNetwork and view the ModbusTcpSlaveDevice objects. Right click on the ModbusTcpSlaveDevice object and select Pin Slots. Select the Device Address slot to pin ... select OK, Create a NumericWritable and set the value to 255. Link the output of the NumericWritable to the Device Address.

Issue When attempting to open the WorkPlace Tech Tool software, a Windows fatal error box is displayed: WptEd has encountered a problem and needs to close. We are sorry for the inconvenience. If you were in the middle of something, the information you were working on might be lost. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve WptEd. We will treat this report as confidential and anonymous. Product Line EcoStruxure Building Operation, TAC IA Series Environment WorkPlace Tech Tool software WorkPlace Tech Editor Cause This problem can occur when you use an unsupported version of Visio, such as Visio 2000, prior to starting WorkPlace Tech Editor. Only Visio 2010 SP1, Visio 2007 SP2, and Visio 2003 SP3 can be used with the WorkPlace Tech Tool or WorkPlace Tech Editor. Resolution In the warning message, click [Don't send]. Close Visio. Open Visio 2010 SP1, Visio 2007 SP2 or Visio 2003 SP3.  This causes Windows to initialize and configure that specific version of Visio. When Visio opens, confirm that the selected version opens.  If the wrong version opens, you may need to repair the installation of the selected version. Close Visio. Restart WorkPlace Tech

Issue Alarm email is not sent out and is discarded. The Last Discard Cause is 'BOutgoingAccount could not dequeue in-memory email: 501 Syntax error in parameters or arguments'.  Environment I/A Series G3 Cause 'Reply To' field in the Outgoing Account properties was left empty. This field specifies the contents of the 'From' field in the email that is sent. Resolution Configure the Outgoing Account 'Reply To' field with a valid email account. In the example below (G3 version 3.7), the valid account being used is my.account@gmx.com. 

Issue In SmartStruxure, how can Network 8000 objects be linked with non-Network 8000 objects?  For example, sharing an outside air temperature value from a LON integration on the same Automation Server with a Network 8000 integration Environment Network 8000 StruxureWare Building Operations Cause No outside air temperature reference is available in a Network 8000 integration.  Resolution Use APT (A=analog), DPT (D=digital), RnetAv, or RnetDv objects to bring non-Network 8000 data into the Network 8000 integration. These objects behave similar to a 'middle man'.  Each of these objects has a global reference on the 'Inputs' tab. Using the APT object as an example, the Inputs tab has an Analog Global Reference section with two settings: Analog global value & Analog global reference. Bind the output of a Function Block Program (for example) to the Analog global reference. Watch the Analog global value as it will display the value once the binding is done. The output of the APT object can now be linked to as many Network 8000 objects as required. Note: The Global Reference takes highest priority. Therefore, the order of input priority is as follows: 1st = global reference, 2nd = input constant, 3rd = input reference. The input constant and input reference are carry-overs from Network 8000 GCM blocks. The global reference was added for SmartStruxure integrations and took over 'top spot'. In order to use the input constant or input reference, the value of the global reference must equal NULL. This is only for inputs. Any output of a Network 8000 object can be bound directly to any non-Network 8000 object.  

Issue During the startup of an ENC-520 station, the following warning message appears in the application director output: Platform Service Access Platform Service Qnx will not be added, feature 'accessControl' is not licensed. How can this warning be corrected? Environment Niagara G3 Cause This service is for a product line, offered by Tridium, that is no longer available. Resolution Remove the platAccess module from the ENC and reboot.

Issue After upgrading systems to the latest I/A Series G3 Niagara maintenance builds 3.5.406, 3.6.406 or 3.7.106 some customers have noticed spikes in Heap and CPU usage. This behavior has been traced to the excessive creation of NiagaraNetwork worker threads. Customers may see spikes in CPU usage that randomly occur and persist until system appears to halt or in some cases triggers Engine Watchdog Timeout and restart of station.  Customers may also experience the Java Virtual Machine exit with the following exception in the standard output: java.lang.OutOfMemoryError: unable to create new native thread Environment I/A Series G3 versions 3.5.406, 3.6.406, and 3.7.106 Cause It is believed that excessive NiagaraNetwork workers are being spawned due to additional overhead required to encrypt and decrypt passwords from the new password store utilized in 3.5.406, 3.6.406 and 3.7.106. Excessive usage of CPU and creation of worker threads may be seen on both Enterprise Network Server and ENC/JACE platforms. Typically OutOfMemoryError will be seen on ENC/JACE platforms and not on PC based solutions due to the limited resources of the embedded platforms. The issue has only been observed on stations with five or more station devices in the NiagaraNetwork. Resolution Limit the number of NiagaraNetwork/workers that can be created by setting the property "Max Threads" on the NiagaraNetwork/workers property sheet. A good rule of thumb for the number of workers is six times the number of Niagara Network stations monitored by the station.

Issue Equipment lead lag rotation based on runtime Environment I/A Series G3 Cause Rotation of equipment using runtime.  Resolution A LeadLagRuntime object is available in the kitControl palette (HVAC folder). The LeadLagRuntime object can be configured to rotate 2 to 10 loads. An explanation of the usage can be found in the Niagara Ax kitControl Guide or the online help in Workbench. 

Issue I/A Series G3 BACnet Server (Export) Operation Environment I/A Series G3 Cause Integration to I/A Series G3 from a 3rd party BACnet system Resolution If the I/A Series host (ENS or ENC) is licensed as a BACnet server, you can export any number of selected types of objects in the station (regardless of location) to appear as BACnet objects. As such, these objects can service client requests from any networked BACnet devices. Exporting of Niagara schedules and calendars is included. Histories can be exported also, where they appear externally as BACnet Trend Log objects.  The following I/A Series G3 objects can be exported as BACnet objects (extracted from the Niagara Ax BACnet Guide).    You use the Bacnet Export Manager to export Niagara objects for BACnet. To access the Bacnet Export Manager, go to 'BacnetNetwork' > 'Local Device' and double click on the 'Export Table' under the Local Device.  You can find details on using the Bacnet Export Manager on pages 4-57 to 4-71 of the Niagara Ax BACnet Guide. The Niagara Ax BACnet Guide is installed with G3 and can be found in \niagara\niagara-3.x.xx\docs.   can be exported also, where they appear externally as BACnet Trend Log objects. from any networked BACnet devices. Exporting of Niagara schedules and calendars is included. Histories can be exported also, where they appear externally as BACnet Trend Log objects. (regardless of location) to appear as BACnet objects. As such, these objects can service client requests from any networked BACnet devices. Exporting of Niagara schedules and calendars is included. Histories can be exported also, where they appear externally as BACnet Trend Log objects.

Issue I/A Series R2 BACnet IP Device addressing Environment I/A Series R2 BACnet integration Cause When you manually add a BACnet IP shadow device object to a station, you will need to enter the BACnet IP addressing information for communications to work.  Resolution Right click on the BACnet IP device and go to its properties. Go to the 'Config' tab and set the following.  - The objectIdentifier > Instance Number. This is the BACnet instance number of the device (1 - 4194302).  - The address > Network Number. This is the BACnet network number of the device (1 - 65534). - The address > MAC Address. This is the IP address and BACnet UDP port of the BACnet IP device in HEX format.  Example: C0:A8:01:23:BA:C0 corresponds to 192.168.1.35:47808. 

Issue Although the current time is correctly displayed in a UNC, the Enterprise Server, and WorkPlace Pro, it is incorrect in the R2 Schedule Editor. The error in time is a multiple of one hour. Environment I/A Series R2 (Niagara), all versions. Cause The correct Time Zone is not synchronized in the Schedule Editor, which defaults to timezone=America/New_York. Resolution 1. Close WPPro 2. in Windows, go to Niagara / build / nre / lib /time.properties, open with a text editor 3. If it reads timezone=America/New_York, change it to timezone= (timezone corresponding to your location. Copy from Niagara / build / nre / lib /timezones.txt) 4. Save the change 5. Start WPPro, check the time in the Schedule Editor, should be correct.