Issue Is there a limit to the number of read/writes available for a BACnet Setpoint object? Environment WorkPlace Tech versions 5.1 and later Cause Not applicable Resolution The BACnet Setpoint object (analog or binary) is used for writing setpoint values to a controller, where it is stored in EEPROM. Observe normal precautions to avoid frequent writes to EEPROM. Excessive writes (typically greater than 100,000) can greatly shorten the life of the EEPROM and adversely affect its reliability. The BACnet Setpoint Priority object (analog or binary) represents a Value BACnet object type, of which the data is read-write accessible. This object can be used to write data to the controller. The Setpoint Priority object provides access to temporarily stored application values, usually setpoints or setup values, that are stored in RAM.  These setpoint values can be monitored and changed via BACnet communications, using the BACnet priority array.  When written from WP Tech, the default value is written to the priority array “relinquish default” location. Only this default value is stored in EEPROM. For more information, refer to the WorkPlace Tech Tool Engineering Guide Supplement (F-27356)

Issue Controllers that will operate in a  Master / Slave configuration, where values such as the setpoint, temperature etc can be shared. Environment MNL controllers LonMaker WorkPlace Tech Cause Configuration issue. Resolution The MNL 20RF controllers will not directly act in a Master / Slave configuration. If there is a requirement to share values between controllers, such as the setpoint, temperature etc. then these values need to be assigned to SNVT's in each controller, and the controllers bound together using LonMaker or similar.

Issue A version of the WorkPlace Tech Tool software prior to version 5.7 had previously been installed on the computer and licensed with an expiring license.  The WPT software was updated to version 5.7.x.  When the previous expiring license was about to expire, the next expiring license renewal was requested.  However, when the previous expiring license did expire, the new one also expired. Environment Initial WIBS/WPT license on computer created by installation of any version Wonderware for Intelligent Buildings Software (WIBs) or any version prior to 5.7 of the WorkPlace Tech Tool software (WPT). New version (5.7.x or later) of the WorkPlace Tech Tool software installed on same computer. Cause New license request was incorrectly generated using the WIBSPurchase ("Purchase WIB Software" icon) program instead of using the "Purchase WorkPlace Tech Software" icon on the computer desktop. Resolution Use the "Purchase WorkPlace Tech Software" icon on the computer desktop to request any license updates for version 5.7.x and newer of the WorkPlace Tech Tool software.

Issue When attempting to use Serial Tunneling through an I/A Series (Niagara) G3 system ENC, the following error message is displayed in the Application Director window: ERROR [....][Serial Helper] Denied Opening comm port 'COM1' javax.baja.serial.PortDeniedException: COM1 is already owned by dbgjmpr Environment I/A Series (Niagara) G3 ENC-520, ENC-410. Cause This error is reported when the operating system console enable jumper is installed on the front two pins of the MODE connector in the upper right corner of the ENC circuit board.  NOTE: This jumper is installed only when using a serial terminal running at 57600 baud and connected to serial port COM1 to troubleshoot ENC operating system startup / IP address issues. Resolution Remove the jumper and reboot the ENC.

Issue The station’s database indicates a “successful” start, however, the error message “Service Unavailable – Service disabled in remote station” is seen when attempting to tunnel with XPSI.  See I/A Series Enhanced ASD Driver - Release Notes for more information on this issue. Environment I/A Series (Niagara) R2 station, with VSerial service and ibsAsd service installed. XPSI 4.1 or newer. Cause The vserial and IbsAsd services use common tunnel software components, and having both services enabled at the same time causes conflicts in registering the services. Resolution The resolution to this issue requires that the I/A Series (Niagara) R2 station be running the ibsAsd 2.302.516b.v1 jar file, or later. In a station where communications with ASD controllers, and the ability to tunnel into the ASD bus with XPSI are both required, delete the vserial service and reboot the UNC.   In stations where both the ibsAsd service and the vserial service are required (not simultaneously), see the TAC I/A Series Enhanced ASD Driver Engineering Guide, F-27429-3, Appendix B, “Tunneling Example”, pp 123 – 130 for an application that will allow only one or the other service to run at a time, and prevent the conflict between them. This document and the I/A Series Enhanced ASD Driver - Release Notes are included with the I/A Series (Niagara) R2 software release R2.301.522 and newer documentation.

Issue When a Binary Input object is configured as a pulse counter, what happens when the time between pulses is longer than the interval specified in the “Pulse Input, Minimum Rate”? For example, the MNB-1000’s Fast Pulse Input, Minimum Rate  = 1 pulse per 4 minutes; what if 20 minutes pass between pulses? Environment MNL- controllers (MNL-5Rxxx, MNL-10Rxxx, MNL-15Rxxx, MNL-20Rxxx, MNL-800) MNB - controllers (MNB-70, MNB-300, MNB-1000, MNB-V1, MNB-V2) Cause Some meters transmit output pulses at a rate slower than the specified Minimum Rate of the controller. Resolution In the Binary Input object, the input is integrated over the time period, and the resulting calculated value is the object’s Output. If there is no pulse to count, the Output = 0 (no pulses, no measured output calculated over that time period), but the Count output will still be correct. Refer to the current Specifications Data Sheet for the controller for details on the Minimum Pulse Rate.

Issue Unable to override points in a MicroZone II from an I/A Series (Niagara) G3 station. Get error " javax.baja.sys.ActionInvokeException   at com.tridium.fox.sys.broker.BFoxComponentSpace$FoxTrapCallbacks.invoke(BFoxComponentSpace.java:355)...  ... at java.awt.Component.dispatchEventImpl(Unknown Source)  com.tridium.fox.session.ServerException: java.lang.RuntimeException: Invalid response during override.  Check username and password" Environment I/A Series (Niagara) G3 station with the tacAsd driver I/A Series Network 8000 ASD controller (MicroZone II, PEM-1, LIM) Cause The "User Name" and "User Password"  in the Property Sheet of the ASD device object (under the AsdNetwork object) in the ENC's station, and the USRn and PASn stored in the MicroZone II, PEM or LIM database do not match exactly. The USRn and PASn are case sensitive, accepting ONLY capitalized characters. The AsdZone2 device property sheet in the G3 station allows entry of lower case characters, which can cause a mismatch in the User Name or User Password, or both. Resolution Be sure to enter the correct User Name and User Password in the Property Sheet of the AsdZone2 device, and remember to use ONLY capital letters.

Issue When using the I/A Series WorkPlace Tech Tool software to engineer an application for the I/A Series LON or BACnet controllers, the Visio Shape Sheets (stencils) containing the application drawing objects may be accidentally or intentionally closed.  Due to the names of the Visio Shape Sheet files containing the WPT stencils, it is very difficult to reopen the proper series of shape sheets without repeated trial-and-error.   When upgrading an application drawing from WPT 4.0 to WPT 5.7 or WPT 5.8, this same issue may occur.  Use this procedure to reattach the proper stencils to the upgraded application file. Environment I/A Series WorkPlace Tech Tool software version 4.0.0 or newer. Cause The names of the Visio Shape Sheet (Stencil) files for the WorkPlace Tech Tool are not self-explanatory, making it nearly impossible to manually select and reattach the correct stencils to the current application file.   Resolution Open the WPT Hardware Wizard, either from the Application Menu or by Right-Clicking on the drawing, and then click the Hardware Wizard [Finish] button.  The WPT Hardware Wizard will use the information pertaining to the selected controller type, model and version to insure that the application is configured properly and the necessary drawing stencils are available, redisplaying them on the left edge of the drawing

Issue In Tree Tech Revision 3.1,  received  "Error in FCSINIT - Use the TaskBar to find its window and check the error". Environment TAC I/A Series Tree Tech, Revision 3.1 Cause TreeTech 3.1 will only function with communication ports 1 through 9.  Ports above 9 result in "Error in FCSINIT - Use the TaskBar to find its window and check the error".   Resolution Select a communications port in the valid range from 1 through 9.

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 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 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 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 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.