Issue MicroNet Heat Pump / Fan Coil Controller Diagnostic Table Environment MicroNet 2000 MN-HPFC Cause Quick reference table with corrective action Resolution This table is an excerpt from the MicroNet Heat Pump / Fan Coil Controller Reference Manual (F-26174):

Issue When adding MNL controller in Workstation for Projects, it will show up an error: Object type is not supported. Environment SmartStruxure 1.5 Workstation for Project PCS MNL controller Cause When using the Project Configuration Server, you cannot create MNL LonWorks devices and applications. Accordingly, the WorkPlace Tech Editor option does not display in the Control Panel. Resolution MNL LonWorks devices can be added in an Enterprise Server or Automation Server after deploying a project to one of these servers.

Issue The property list for an Analog Input / Output or Binary Input / Output object in the WorkPlaceTech application shows a "Process Time" parameter: OR instead of a "COV Increment" parameter" Note that for Binary I/O objects, the COV increment is implied as any change of binary value and is not displayed. Environment MNB series controller WPT application file MNB series controller with firmware release 1.4 or newer WorkPlace Tech Tool software, release 5.5 or newer Cause Prior to firmware version 1.4, the MNB family of controllers did not support COV Subscription functionality. Resolution The existing I/O object must be deleted and recreated, using the WorkPlace Tech Tool software release 5.5 or newer, to allow the use of the COV Increment parameter.

Issue Can additional mounting clips for the MNL-VxRVx or MNB-Vx controllers be purchased? Product Line TAC IA Series Environment MNL-VxRVx or MNB-Vx controllers Cause Each MNL-VxRVx and MNB-Vx controller includes one mounting clip that can be moved from the factory shipped location (bottom) to the side of the controller base.  The mounting clip is also known as the mounting foot or pivot bracket. Resolution Replacement or additional mounting clips can be purchased using part number DVAV-242.

Issue Application Director output window and LON proxy point indicates fault: java.lang.ClassCastException: javax.baja.sys.BDouble ERROR [14:56:22 20-Aug-14 EDT][lon1] Could not decode nv update data Misc9:nvoSpaceTemp java.lang.ClassCastException: javax.baja.sys.BDouble    at javax.baja.lonworks.londata.LonFacetsUtil.makeLonQualifiers(LonFacetsUtil.java)    at javax.baja.lonworks.londata.LonFacetsUtil.getQualifiers(LonFacetsUtil.java)    at javax.baja.lonworks.londata.BLonData.primitiveFromInputStream(BLonData.java)    at javax.baja.lonworks.londata.BLonData.fromInputStream(BLonData.java)    at javax.baja.lonworks.londata.BLonData.fromNetBytes(BLonData.java)    at javax.baja.lonworks.BNetworkVariable.receiveUpdate(BNetworkVariable.java)    at com.tridium.lonworks.NvManager.receiveLonMessage(NvManager.java)    at com.tridium.lonworks.loncomm.NLonComm.routeToNvListener(NLonComm.java)    at com.tridium.lonworks.loncomm.NLonComm.receiveLonMessage(NLonComm.java)    at com.tridium.lonworks.loncomm.NLonLinkLayer$AppBufferReceive.run(NLonLinkLayer.java)    at java.lang.Thread.run(Unknown Source) Environment I/A Series G3 (all versions) Cause This error is related to a mismatch between the lonworks module running on the ENC/JACE versus the version being used within the Workbench modules folder.  A different version of Workbench and/or lonworks module is being used to engineer the ENC/JACE. Resolution Review the versions between the Workbench and ENC/JACE and match the versions.

Issue After troubleshooting a communications issue, the DCM daughterboard (or piggyback board) was deemed defective.  Can it be removed and replaced with another in the field? Environment DMS MicroSmart controller (revision 9) -- Model numbers affected are DCM-UC, DCM-IOC, DCM-GPC Cause Internal board failure Resolution Yes, the DCM board can be swapped out.  Care must be taken not to damage the pins and clips (identified below in yellow).

Issue A GCM has been removed in the field and replaced with a newer product (i.e. a Niagara Jace or a SmartStruxure AS).  How can the GCM be disabled from communicating in TreeTech without actually deleting it?  Environment TreeTech (all revisions) Cause The GCM's programming logic will be used for a short period of time as a reference.  Then, the entire GCM will be deleted from TreeTech. Resolution Right-click on the GCM and go to Properties. Click the Offline Status tab. Select Offline from the drop-down menu. Close the window. Offline mode disconnects the GCM database in TreeTech from the field.  

Issue I/A Series R2 OPC integration to Gallagher OPC Data 3.0 Server: R2 is unable to discover the OPC objects. Product Line TAC IA Series Environment I/A Series R2 version r2.301.529 and higher Cause I/A Series R2 OPC client supports integration to OPC data access server versions 1.x and 2.x. It has not been tested for DA server 3.x.  Resolution I/A Series R2 OPC Client does not support integration to OPC DA Server version 3.x. However, in this particular case, the OPC objects can be added manually and the integration works.  The OPC Server and group have been successfully discovered and added to the R2 station. However, the OPC Items are not shown when we run the ItemListManager. In the example below, the OpcClientStringInput objects have been manually added. To manually add the OPC Items: Go to the Group's WorkPlace Editor. In WorkPlace Pro, in the local library, go to 'tridiumx' > 'opcClient' > 'objects' Select the objects you need, copy and paste it to the OPC Group folder WorkPlaceEditor. Go to the properties of the OPC objects and configure the OPCItemFullName.

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