Building Automation Knowledge Base

Issue Using an MNB-ROAM-IA, cannot connect WorkPlace Tech Commissioning Tool to a controller; receive error message  “ Cannot open communication port: Error code 5” Environment MNB-ROAM-IA adapter, either Bluetooth or serial cable connection WorkPlace Tech Suite software ( WorkPlace Tech Tool, Commissioning Tool, Flow Balance Tool), revision 5.7.1 and newer I/A Series MNB controller (MNB-70, MNB-300, MNB-V1, MNB-V2, MNB-1000) S-Link Sensor (MN-S1, MN-S1HT, MN-S2, MN-S2HT, MN-S3, MN-S3HT, MN-S4, MN-S4HT, MN-S4-FCS, MN-S4HT-FCS, MN-S5,   MN-S5HT) Cause A poor mechanical connection between the plug (on the cable connected to the MNB-ROAM-IA) and the MS/TP jack on the MNB- controller or on the MN-Sx can prevent the software from connecting to the controller. Resolution Make sure the mechanical connection between the plug and the MS/TP jack is secure. The plug should connect at a right-angle to the jack, and be completely inserted.  When connecting via the MN-Sx sensor, make sure that the back portion of the plug does not hang up on the sensor cover, preventing full insertion.

Issue I/A Series R2 (Niagara) Unable to Install Vykon Alarm Service (VAS) Client in Windows 2000 Environment Environment I/A Series R2 (Niagara) Windows 2000 Vykon Alarm Service 3.90 Cause Windows 2000 installer is not compatible with Vykon Alarm Service 3.90 Resolution As a work-around: Unzip VAS 3.90 file Create a new folder named VAS Client 3.90 under Program Files\Tridium Copy Overlay folder with all contents to VAS Client 3.90 folder Right Click Vykon Alarm Service.exe select Send to / Desktop (create Shortcut) Run by clicking new shortcut created in Step 4 

Issue Using Lon Tunnel with Lon Flow Balance Tool Environment Lon Flow Balance (MNL-FLOW-BAL) all versions R2 Niagara Lon Tunnel Client G3 Niagara Lon Tunnel Client Cause Not applicable Resolution No, the Lon Tunnel Application (Niagara Application Tunneling) is not compatible with the Lon Flow Balance Tool.  A direct connection (PCMCIA card or USB Lon Adaptor) must be present between the Lon VAV controller and the Lon Flow Balance Application.  Also, LON1 is the only adapter address supported.  

Issue The factory uses the number of field failure returns to evaluate product quality.  The analysis of returned product has the potential to produce extensive information about how the product is performing and also reveal areas for improvement. Environment All controllers in following product lines:  MNB, MNL, Niagara, Network 8000, Micronet 2000. Cause Lately, many of the returned controllers, after factory-testing, have resulted in "no fault found", and a high percentage of these controllers have little to no explanation of the failure witnessed in the field. This makes it difficult to investigate the returned product further. Resolution Include the following information with all controller returns: A detailed description of the reason for return The name of the site from where the controller was removed The name and contact information of the field technician who determined the unit was defective The field technician will only be contacted if absolutely necessary. Write the above information on a "returned goods" identification tag (part number F-24802) and attach a tag to each returned controller.  The tags are available via the Publication Zone through iPortal at no charge. For more information on returning product to the factory, review the following technical product advisories: TPA-PSSG-09-0003.00  Return Process Improvement TPA-RKFD-10-0005.00  Return Process Improvements

Issue The I/A Series R2 (Niagara) build 529 programLib jar file is missing 5 objects that were available in previous build programLib-2.301.527c.v1.jar. The missing objects include: ConfigurableBinaryOutputNode.class FlexLimitEnableBits.class FlexString.class Bpa2Str.class Fs2Fp.class Environment I/A Series R2 (Niagara) build programLib-2.301.529.v1.jar Cause Objects listed were not included in programLib-2.301.529.v1.jar Resolution The missing objects were restored in the programLib-2.301.532d.jar. Use it instead of the programLib-2.301.529.v1.jar. In Windows Explorer, rename programLib-2.301.529.v1.jar. to programLib-2.301.529.v1.jar.old in the emb, nre/modules, and nt directories. Download programLib-2.301.532d.jar Copy into all three 2.301.529.v1 directories (emb, nre/modules, and nt ).

Issue Communication to LON controllers is lost.  After a re-start of the station, the following errors appear in the standard output window: ---------- Station Starting:   MON MAY 02 14:53:10 2011 ---------- Tridium Niagara Station, r2.301.529.v1 [test] MESSAGE: ErrorLogService installed [/test/services/ErrorLogService] Start service: ControlEngineService [3] ControlEngineService Start service: UiEngineService [7] UiEngineService Start service: NotificationService [6] NotificationService Start service: LogService [5] LogService Start service: AuditLogService [2] AuditLogService Start service: ErrorLogService [4] ErrorLogService Start service: LonWorksService [9] LonWorksService Error opening driver LON1 java.lang.Exception: Unable to open lonworks driver *************************************************************** ERROR: Cannot startService [Sys: LonWorksService [9] LonWorksService] java.lang.IllegalStateException: Unable to open lonworks driver at tridiumx.lonworks.services.LonLinkLayer.start (bytecode 143) at tridiumx.lonworks.services.LonWorksService.startService (bytecode 12) at tridium.foundation.Sys.startServices (bytecode 49) at tridium.foundation.Station.startStation (bytecode 63) at tridium.foundation.Sys.boot (bytecode 27) at tridium.foundation.Sys.bootLocalSns (bytecode 17)    at tridium.tools.StationMain.bootSns (bytecode 0)    at tridium.tools.StationMain.doIt (bytecode 352)    at tridium.tools.StationMain.main (bytecode 10)    at java.lang.reflect.Method.invoke (Native Method)    at tridium.nre.Nre.mainImpl (bytecode 271)    at tridium.nre.Nre.main (bytecode 1) tridiumx.lonworks.LonException E_LON_COMM_SERVICE_NOT_STARTED    at tridiumx.lonworks.services.LonCommService.doLonCommSendRequest (bytecode 19)    at tridiumx.lonworks.services.LonCommService.lonCommSendRequest (bytecode 3)    at tridiumx.lonworks.services.LonCommService.lonCommSendRequest (bytecode 68)    at tridiumx.lonworks.util.Neuron.readMemory (bytecode 29)    at tridiumx.lonworks.util.Neuron.readMemory (bytecode 9)    at tridiumx.lonworks.util.Neuron.isNMAuthSet (bytecode 32)    at tridiumx.lonworks.util.Neuron.isNMAuthSet (bytecode 16)    at tridiumx.lonworks.devices.LocalLonAppDevice.verifyDevice (bytecode 2)    at tridiumx.lonworks.services.LonWorksService.stationReady (bytecode 28)    at tridium.foundation.Sys.stationReady (bytecode 23)    at tridium.foundation.Station.startStation (bytecode 87)    at tridium.foundation.Sys.boot (bytecode 27)    at tridium.foundation.Sys.bootLocalSns (bytecode 17)    at tridium.tools.StationMain.bootSns (bytecode 0)    at tridium.tools.StationMain.doIt (bytecode 352)    at tridium.tools.StationMain.main (bytecode 10)    at java.lang.reflect.Method.invoke (Native Method)    at tridium.nre.Nre.mainImpl (bytecode 271)    at tridium.nre.Nre.main (bytecode 1) MESSAGE: Station started successfully. (HTTP port=80) [test] These errors follow a short time later: Freeing transaction from transmit driver, tag is 4 The LonException code is java.lang.Exception: ldvWrite() failed - rc = 6, in transmit driver Freeing transaction from transmit driver, tag is 5 The LonException code is java.lang.Exception: ldvWrite() failed - rc = 6, in transmit driver  ... repeated Environment Niagara R2 UNC-520-2 Niagara R2 UNC-410-1 (including the -N international versions) Also applies to obsolete models:  UNC-500, UNC-510, UNC-600, UNC-610 Cause These errors indicate the Niagara operating system is not communicating to the (on-board) Echelon MIP chip.  To confirm, run the following test: Open the running station in Tree View Go to the Properties of the localLonDevice, specifically the Engineering tab Blank out the "neuronId" and click Apply Reboot the UNC When the station has started successfully, return to the neuronId field and observe the value in the box If the neuronId field is all zeros, then there is a hardware problem with the Echelon MIP chip. Resolution This issue is not field-repairable. Contact Product Support Services for a return authorization number.

Issue How do I set the LonWorks send and receive heartbeats settings for localLonDevice in an I/A Series R2 UNC station? Environment I/A Series R2 UNC LonWorks Integration Cause There may be a need to change the settings for the LonWorks send and receive heartbeats settings in an I/A Series UNC station (for faster or slower updates).  Resolution To change the send heartbeat of the localLonDevice: Go to the UNC station's lonLonDevice properties Config tab. The maxSendTime and minSendTime is the send heartbeat settings for the localLonDevice (LLD). As per the Niagara LonWorks Integration Reference page 9-4 to 9-6 (which is installed together with the installation of I/A Series WorkPlace Pro software), maxSendTime and minSendTime are defined as follows. maxSendTime: Specifies the maximum amount of time (in seconds) that the LLD waits to write an output value—if the value has not changed in this amount of time, the LLD will send it anyway. Maximum send time ensures that network variable updates are received by destination nodes (whether they change or not) within the limits set by that node's receive heartbeat limit. minSendTime: Restricts the number of network variable updates placed on the wire. Regardless of the rate at which the network variable is updating, it will only be sent at this rate. This property prevents the network from being congested by values that are oscillating at an abnormal rate. To change the receive heartbeat of the localLonDevice: Go to the UNC station's lonLonDevice properties Config tab and expand the nvoStatusProps property. The Receive Heartbeat is used to ensure timely network variable updates are transmitted and received. If this property is set to zero, the local LON device does not expect periodic updates of its linked inputs - it simply waits until the value changes.

Issue Attempting to run a station with BacnetNetwork already added will result in the station not being able to start successfully. The station status in Application Director will continuously be shown as 'Starting'. The following error messages can be seen in the station's output messages. # A fatal error has been detected by the Java Runtime Environment: # #  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0e953cc4, pid=2912, tid=3104 # # JRE version: 6.0_16-b01 # Java VM: Java HotSpot(TM) Client VM (14.2-b01 mixed mode windows-x86 ) # Problematic frame: # C  [platform.dll+0x33cc4] # # An error report file with more information is saved as: # c:\niagara\niagara-3.5.34\daemon\hs_err_pid2912.log # # If you would like to submit a bug report, please visit: #   http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug.   When you try to add the BacnetNetwork to a running station, the station will disconnect. The BacnetNetwork is not added after you re-connect to the station. Environment I/A Series G3 versions 3.5.25.4 and later Windows XP Chinese (Taiwan) Edition Cause The BACnet module is unable to correctly process the unicode character set of the computer's Ethernet adapter name. This this case, the Ethernet adapter name contains traditional Chinese characters. Although it has not been tested or verified, the same problem may occur on computers installed with other unicode languages versions of Windows (Japanese, Korean, Thai etc.). Resolution Current workaround is to rename the computer's Ethernet adapter name to 8-bit characters (English etc.). In Application Director, 'Kill' the station that is 'Starting'. Rename the Ethernet adapter. Start the station in Application Director.

Issue During the menu configuration process, the ProView for LON configuration wizard will provide a list of LON devices commissioned into the G3 station database.  The MNL-800 controller appears in the list, however,  the MNL-800 device object cannot be expanded to display the nvi, nvo, and nci objects for selection. Environment I/A Series G3 (all versions), MNL-800, ProView for LON, MNL-PROV-WAL Cause None Resolution The MNL-800 will not display network variable nvi, nvo, and nci objects unless the device's self documentation is modified to provide what the wizard considers a valid LonMark and function block reference. Open the properties for the MNL-800 (Dynamic Device) and expand the Device Data. Locate the Self Doc property and configure the value as follows: 3.3@8000; Launch the Ec Dis Wizard and the MNL-800 will now expand to display the nvi, nvo, and nci objects for selection.

Issue I have an obsolete floating / proportional / two-position actuator connected to my controller.  Need to replace the obsolete actuator, preferably without modifying the controller or valve. How do I locate a replacement? Environment Obsolete electronic actuator Cause Find replacement parts for obsolete actuators. Resolution Use the Schneider Electric Cross Reference Tool

Issue Downloaded the Tree Tech 3.1 software. How do I get a serial number so that I can complete the licensing form displayed with the "Tree Tech software" program? Environment TreeTech_3.1.exe Cause The Purchase Wibs license generator program requires a "WIBS serial number" so that the license request can be generated. If the field is left blank, the program will not allow the license request to be generated. Resolution The serial number is provided on purchased CDs so as to provide a method of tracing the manufactured CDs. To license the downloaded version of the Tree Tech, enter an 8 digit serial number. It is suggested, although not required, that you enter the current date as the serial number. When using the date as the serial number, enter the four digit year followed by the two digit month followed by the two digit day, i.e., in the format YYYYMMDD. For example, 20110520.

Issue Unable to open a G3 station from the web browser when the error "Java. lang. Out of memory error: Java Heap Space" is seen in the station output. The error appears to clear itself after some time and the station will become accessible again. Environment I/A Series G3 ENS 3.0.101 and above Cause The station is running out of Java heap space. Resolution To resolve this issue, you can adjust the Java heap settings in the nre.properties file. It is important that you only make the changes as detailed below. Make a backup copy of this file before proceeding. Locate the file nre.properties in \niagara\<niagara version>\lib Open the nre.properties file using a text editor program (Notepad). Modify the java.options=-Xmx120M to java.options=-Xmx1024M leaving other parameters in the file unchanged. Save, close the file and restart the station.

Issue ABB drives connected to UNC-520 on BACnet MS/TP network do not update automatically; an upload needs to be performed in order for the points to be updated. Environment I/A Series R2 BACnet, all versions Cause By default, R2 sets the readPropertySupported flag to True.  ABB drives do not support the Read Property Multiple feature. Resolution In R2, in the Properties of the BACnet device, set the readPropertySupported flag to False.

Issue The following error message is seen when attempting to launch the I/A Series R2 WorkPlace Pro or Enterprise Server : "This product requires a valid license. Missing license file: /nre/lib/license.properties." Environment I/A Series R2 (all versions), Enterprise Server, WorkPlace Pro Cause The computer has file extensions hidden, causing the license.properties file to actually be named license.properties.properties. Resolution Use the Windows Explorer to navigate to the directory that contains the license.properties file (typically \niagara\r2.301.xxx\nre\lib). If running Windows 7,  select Organize then Layout and check "Menu Bar" to enable the Windows Explorer menu bar.  This menu bar is the same as the Windows Explorer menu bar found in earlier versions of Windows. Select menu item Tools - Folder Options ...  Select the View tab and locate the checkbox for "Hide extensions for known file types." Uncheck the checkbox and select OK. Rename the file to license.properties and save.

Issue Vykon Tenant Billing invoice and report end dates are limited to year 2010 Environment I/A Series R2 (all versions), VTBS, Vykon Tenant Billing Cause None Resolution vtbs-2.301.532d.v1 resolves the year limitation. The year is now selectable beyond 2010. Caution: Always backup station database before performing any upgrade.

Issue Vykon Tenant Billing fails to reliably generate invoices for overrides that operate through midnight. Environment I/A Series R2 (all versions), VTBS, Vykon Tenant Billing Cause None Resolution vtbs-2.301.532d.v1 resolves the year limitation. The year is now selectable beyond 2010.   Caution: Always backup station database before performing any upgrade.

Issue Need to re-license I/A Workplace Tech, have already used 3 of the 365 day licenses. Is there a way to add another one?   Environment I/A Series WorkPlace Tech Tool Software  Cause Renewal license limitation. Resolution Use the file WPTLExtractor.exe. This exe file allows for up to (15) - 365 days license renewals. Review TPA-RKFD-09-0025 for additional information.

Issue The GCMA-135-2 circuit board for the ASD repeater needs to be replaced but the item is not available for purchase. Environment RPTR-WIRE product, GCMA-152-2 circuit board Cause Unit needs to be replaced. Resolution The GCMA-135-2 circuit board used in the RPTR-WIRE ASD repeater is not available as a field replaceable part.  Purchase as an assembled unit using part number RPTR-WIRE.

Issue BACnet MS/TP Bus Communication Troubleshooting Checklist Product Line TAC IA Series Environment I/A Series BACnet controllers (MNB-70, MNB-V1, MNB-V2, MNB-300, MNB-1000) on an MS/TP bus. Cause BACnet MS/TP Bus Communication Troubleshooting Checklist Resolution This checklist provides several settings/configurations to review when faced with a communication problem at the controller level. The content was compiled from different resources, summarized, and laid out in an easy-to-use manner so as to provide a quick-reference document. Power Each controller requires 24 VAC from a Class 2 transformer. See the Installation Instructions for each controller, and the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “Power Supply Wiring”. Read-Only Flag Use the WorkPlace Tech Commissioning Tool (WPTCT) to check “Device Properties” of the controller. If the status is “Operational, Read-Only”, the input voltage to the controller may be too low. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “Power Supply Wiring”. Due to the short duration of the low-voltage condition required to set the flag, it is unlikely that you will see it when measuring the input voltage with a digital meter, so check the “Device Properties”, and correct the problem as noted on page 28 of the guide, (reduce transformer loading, reduce wire length between transformer and controller, and /or use wire with higher current rating). Diagnostic LEDs The MNB controllers have onboard diagnostic LEDs that are useful in troubleshooting. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 3, “Communications Hardware Checkout”, Table: “LED Indications”, for a detailed description of the behavior of the LEDs and their diagnostic uses. Topology It is very helpful to draw the topology of the bus when you start troubleshooting. If there are no repeaters on the bus, the topology must be a daisy-chain, with no tees or stars. MS/TP network wiring to MN-Sx sensors must be run to the sensor, then to the next controller on the bus, in a daisy-chain; no tees or spurs are allowed. Maximum length of a wire segment is 4000 feet. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “MicroNet MS/TP Network Wiring”, for details on Communications wiring. Repeaters B-LINK-AC-S, Andover Controls MS/TP Repeater B-LINK-AC-F-S, Andover Controls MS/TP Repeater Fiber See the MicroNet BACnet Smoke Control Systems Manual, F-27419, for details on the use of these wire and fiber repeaters with MNB controllers. See F-27419, Chapter 5, “Approved MS/TP Repeaters”, including the wiring example. Maximum Number of Devices The maximum number of MNB controllers depends on the cable used, and the Baud Rate. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7,Chapter 1, Table, “Approved Cable Types”. The MNB controllers are quarter-load devices, so a maximum of 128 or less are allowed on an MS/TP trunk, depending on the cable used. Addressing Avoid duplicate addresses. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “Required Configuration”, CAUTION: “Duplicate addresses on an MS/TP network trunk will result in erratic behavior, lost tokens, and disrupted communication. There is no software tool that will identify duplicate addresses on an MS/TP network trunk. Typically, if two controllers are set to the same address, one of the controllers will appear to be missing from the list, and the address shared by the two controllers will intermittently come and go from the list.” Biasing As a requirement of EIA-485 (formerly RS-485) bus topology, an MS/TP network must have a minimum of one set, and a maximum of two sets, of bias resistors in place. The MNB-300, MNB-1000, UNC-520, and ENC-520 have jumpers to enable or disable the bias resistors. See bulletin TB06-09, “RS-485 Bias Resistors and the UNC-520-2 / ENC-520-2”, page 3, for a photo of the bias jumpers on a UNC-520-2. Terminators A 120-Ohm End-of -Line (EOL) resistor is required across the “MS/TP +” and “MS/TP -” terminals at each controller at the end of a wire segment. The MNB-1000 and MNB-300 are equipped with a jumper-selectable end-of-line (EOL) termination resistor. The default position for the EOL jumper is “EOL termination not present.” See the MicroNet BACnet Smoke Control Systems Manual, F-27419, Chapter 5, “Approved MS/TP Repeaters”, Figure titled “UL 864 Listed MS/TP Repeater and Isolation”, Note 4, for an important exception, requiring external EOL for the MNB-300 and MNB-1000, when used on a bus with an approved repeater. If a UNC-520-2, ENC-520, MNB-V1 or MNB-V2 is installed at the end of the trunk, install a discrete 120 Ohm EOL resistor, part number EMSC-546, or equivalent. Cable Use of the proper cable is critical to the communications performance of the networked controllers. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7,Chapter 1, Table, “Approved Cable Types” for a list of recommended cable types. As shown in the table, cable selection affects both the maximum number of controllers allowed on the trunk, and the maximum baud rate. WorkPlace Tech Interface The MNB-ROAM-IA is the recommended communications converter for connecting WorkPlaceTech, including the WPT Commissioning and Flow Balance Tools, to an MS/TP trunk. It is supported in versions 5.7.1 and later. A converter that had been recommended earlier, the B & B Electronics model USOPTL4, was found not to operate reliably at speeds above 38.4 K baud. (See Direct MS-TP Connection with B & B Electronics Converters (Revised) - TB08-02-02 for details). The MNB-ROAM-IA supports Bluetooth wireless connection between WorkPlace Tech suite and the MS/TP network, for distances up to about 40 feet. One external Bluetooth adapter has been tested and approved - the Belkin USB adapter. (See Supported models of Bluetooth adapters with WorkPlace Tech for details). A problem we have seen with some MNB-ROAM-IAs is when trying to add Bluetooth device, the Bluetooth Wizard identifies it as "Serial Port Device, Unknown: Major(0), Minor(0)" instead of "tac-RoamIA:xxxxxxxx" where xxxxxxx is the serial number. There is no way for WPT to use the ROAM-IA if the computer can’t pair with it. Currently, there is no known solution, other than replacing the device. Divide and Conquer This is a strategy for dividing a bus into smaller sections in order to isolate a controller or section of bus that might be causing communication problems. The general idea is to divide the bus in half, and see if communications are possible from one end to the other end. If not, divide each half again, and continue until the problem(s) are found. Reference Documents F-27360 TAC I/A Series MicroNet BACnet Wiring, Networking, and Best Practices Guide F-27358 TAC I/A Series MicroNet BACnet Workplace Commissioning Tool and Flow Balance Tool User’s Guide F-27456 TAC I/A Series MicroNet BACnet MNB-70 Zone Controller Installation Instructions F-27345 TAC I/A Series MicroNet BACnet MNB-300 Unitary Controller Installation Instructions F-27346 TAC I/A Series MicroNet BACnet MNB-V1, MNB-V2 VAV Controller Installation Instructions F-27347 TAC I/A Series MicroNet BACnet MNB-1000 Controller Installation Instructions F-27419 TAC I/A Series MicroNet BACnet Smoke Control Systems Manual

Issue When ordering an MNL-10Rxx, MNL-15Rxx, or MNL-20Rxx controller, is the controller base included? Environment MNL controllers; MNL-10Rxx, MNL-15Rxx, or MNL-20Rxx Cause The web pages on iPortal do not described whether or not the base is included. Resolution The base is included when ordering any of these MNL controllers.