Issue When compiling a WorkPlace Tech application, the error message "Error-Failed to create nci file" appears. Environment WorkPlace Tech Cause NCIs value is out of bounds. Resolution Typically, this occurs when an out-of-range "NA" or "NaN" value is written to a NCI by a Niagara station, LonMaker, LNC or some other head-end device. If this issue occurs, check the values of all NCIs on the application drawing.  Any NCI displaying out-of-range values (i.e. 1.#QNaN, 1.#INF or etc.) should be reset to normal values or "NA".

Issue The following error message appears when adding a LON application to a project in WorkPlace Tech 5.x from the pre-engineered "WPT Applications" zip file: AppXMLAddon Error Code: -2032465751 Code meaning: Unknown error 0x86DB08A9s. Environment WorkPlace Tech 5.x WPT Applications.zip Cause Workplace Tech encountered one or more values in the application that contain invalid characters. Generally, the most common value that causes this issue is the nciLocation SNVT. The value that should be in this SNVT is "/0", but through a previous Microsoft Visio conversion, it was replaced with a "vertical bar" character. Resolution Locate the invalid characters Replace them with valid ones or delete them. Once this is done, select "Application - Rebuild Application" from the drop-down menu.

Issue A Niagara R2 Enterprise Server station is extremely slow in starting, and there are hundreds of alarms. Is there a way to delete all the alarms? Product Line TAC IA Series Environment Niagara R2 Enterprise Server Cause Storing unwanted various alarms can cause the station to boot slow. Resolution The alarms can be deleted in two ways. The first method is to delete the app folder under the station directory. The entire historical content of the station will be deleted. This includes archived trends, alarms, and events. Follow the steps below to delete the app folder. Deleting the app folder to clear the contents of the database only applies to a Cloudscape installation. Open windows explorer and navigate to Niagara\station\[station name]\app Delete or move the app folder Restart the station The second method, is to use the appdb/queryForm servlet to selectively remove data from each table including alarms. This is done by using a web browser. Depending on the size of the database this method may take a substantial amount of time. Follow the steps below to delete data from the database by using SQL queries. Open a web browser and navigate to http://[ipaddress]/appdb/queryForm In the form, enter the following query - delete from event.eventhistory This will delete all history data in this table. For further information refer to the SQL_Tutorial\QueryExamples_10_6_04.pdf

Issue Some older modems will successfully connect with the USRobotics 5686 series V.92 modems on the first call, but will fail to connect on subsequent attempts. Product Line TAC IA Series Environment USRobotics 5686 series V.92 modems Cause The V.92 protocol must be disabled when using these modems with older modems.  Resolution To disable the V.92 protocol on the USRobotics 5686 series modems, enter the following setup string in addition to the string specified in the referenced bulletin, before saving the settings: AT +PIG=1 +PMH=1 +PQC=3

Issue When should end-of-line (EoL) terminating resistors be installed on a BACnet/MSTP network? Product Line TAC IA Series Environment BACnet/MSTP network Cause Knowing where to implement the termination helps reduce signal reflections, which might cause issues in the system. Resolution Resistors of 120 ohm value must be installed at each end of a MSTP (or RS-485) trunk segment. They help reduce signal reflections and RF interference. Failure to install end-of-line resistors may result in intermittent communications.

Issue A Niagara R2/G3 UNC/JACE is rebooting every 15 minutes and the standard output window indicates AC Power status failed and a "Battery test failed" gets logged as well. Product Line TAC IA Series Environment I/A Series UNC, ENC or JACE chassis with Gel-cell backup battery Cause Marginal or failed battery or bad battery charging fuse Resolution The UNC automatically performs a battery load test every 15 minutes. If the voltage drops below a predefined value, the battery test indicates "battery test failed". If the voltage is higher than the predefined value, the battery test indicates "battery test passed". This message is only reported once unless the detected battery condition changes. A station alarm is generated only when the new outcome is different that the previous test. If a battery is marginal, the test may alternate between "passed" and "failed." Additionally, a bad or marginal battery has been known to cause random UNC reboots. Begin troubleshooting by checking the battery fuse (field replaceable only in the UNC-500/510 controllers), connections and voltage level.  If the battery voltage is low (less than 12 Vdc), disconnect the battery and monitor the UNC for errors or rebooting. If the errors or rebooting stops install a new battery.  After installing the new battery, measure the battery charging voltage.  The voltage reading should be between 13 and 14.5 volts DC if a good battery is connected.  If the installed battery is partially discharged, the charging voltage reading may be as low as 12.5 volts. In release 2.301.522, a change was made to how embedded controllers (UNC-410 / 500 / 510 / 520) perform the backup battery test.  Formerly, a "marginal" battery might result in continuous reboots. Now, the battery test is better coordinated with the AC power test. This prevents the scenario of repeated AC power fail shutdowns upon boot up if the battery is bad or weak.

Issue Is there a way to convert a Trane BCU (BMTW or BMTX) from BACnet/Ethernet to BACnet/IP for integrating to a Niagara R2 UNC? Product Line TAC IA Series Environment Trane BCU (BMTW or BMTX) Niagara R2 UNC Cause There are two components required to change over the BCU from BACnet/Ethernet to BACnet/IP. Resolution A special serial cable is required to download the BCU with the new configuration. Below are the pin outs to make the cable:     Access to the Tracer Summit software. Here are the steps for running the BCUconfig.exe program to change over the BCU from Ethernet to IP: Open Windows Explorer and navigate to C:\Program Files\Tracer Summit\Bin Double-click on BCUconfig.exe Enter the information and select download. Note - This is where you must have the Trane serial cable. The BCU will reset. Now change the Connection type in the Tracer Summit software to IP connection: Open the Tracer Summit software and select Connect. The Site connection Wizard will appear. Select the BACnet/IP radio button. From the Ethernet Configuration window, select the 'open on startup' check box. Select the 'Use BBMD connection' from the BACnet/IP configuration window. Specify the IP address of the BBMD BCU and the UDP port which is the BACnet port. Select Finish.

Issue MNL-800 LON SNVT Programming Standards Environment Workplace Tech Tool software (any version) MNL-800 controller application Cause Problems occasionally arise as a result of improper LON SNVT programming and configuration in the MN-800 device application.  These issues include problems with the re-commissioning of the updated controller and potential network variable mismatch situations. Resolution  The following standards will prevent these problems from occurring. Network variables MUST be manually indexed. This prevents issues with the network variables becoming renumbered when application programming changes are made. (See NOTE 1) Change the application "Program ID" any time network variables are added or removed from an application.  To change the "Program ID" use the WPT Hardware Wizard,  (See NOTE 2) Select Hardware Wizard from Application Menu Click [Next] in MicroNet Setup Wizard screen Change the displayed program ID by entering a different program ID or adding a suffix letter/number. Maximum length is 8 characters. Click [Finish] to save the changed program ID and exit the MicroNet Setup Wizard.  In addition, one method of minimizing the need to repeatedly change the "Program ID" as the application is developed and debugged is to add a few extra common SNVT input and output definitions when first creating the application, leaving them unconnected to the application program.  If one of these SVNTs is needed, it is available in the LON network image (XIF file) and it is not necessary to change the "Program ID". If the MNL-800 controller has firmware version 2.0 (or later) installed, the standard nci network variables do not have to be indexed as the highest numbered SNVTs in the application.  It is perfectly acceptable to number them as the first 17 indexed SNVTs. Note that there are 17 standard network variables (12 nci, 2 nvo & 1 nvi), not just ten nci SNVTs. SNVT variable names should be limited to 16 characters or less.  Longer names are accepted by the WorkPlace Tech programming tool but the names will automatically be truncated by the LON Network Management tool when commissioning the controller. In addition, when programming the MNL-800 applications with the WorkPlace Tech Tool version 5.0, or later, it is not necessary to put each MNL-800 application in a separate project. NOTE 1: If using the WorkPlace Tech Tool version 5.8 or above, you can use the "Object Indexer" to automatically number all the network variables for you.  This tool also includes functions for detecting duplicate SNVT index numbers and for detecting gaps in the assigned index numbers. NOTE 2: If using the WorkPlace Tech Tool version 5.8 or above, you can set an option in the Hardware Wizard to automatically generate a new ProgramID and reindex the network variables when compiling the application.  Please be aware that this automatic generation of the ProgramID will require the Echelon network image for this device to be updated in any Echelon compatible network management tool.  Please refer to the documentation for the network management tool to determine what actions will be required. For example, if Niagara was used to manage the LON network, then the old shadow will need to be deleted, a new one added, and the device points rediscovered and the device re-commissioned.  

Issue Input scaling issues with the use of 0 to 5 Vdc and 0 (or 4) to 20 Milliamp transducers on a MNB controller. Environment MNB Series Controller application program using Analog Input voltage or current inputs. Cause The resolution of the Analog Input object value is determined by the maximum value that can be processed. If the scaled input range is less than 163.84, the output resolution is 0.01 If the scaled input range is greater than 163.84, the output is an integer value. Resolution When programming the Analog Input object in the WorkPlace Tech Tool, it is important to properly configure the input range and scaled value range for this object. If configured for a 0 to 5 VDC input, the sensor properties must be configured as follows: Input Sensor Type (Type): 5 - Volts Input Low Value (LInput): 0 Scaled Low Value (LScale): 0 Input High Value (HInput): 5 Scaled High Value (HScale): (value, up to 16383, corresponding to 5 volt input) See note below. If configured for a 0 to 20 milliamp or 4 to 20 milliamp input, the sensor properties must be configured as follows: Input Sensor Type (Type): 4 - Milliamp Input Low Value (LInput): 0 or 4 (depending on transducer) Scaled Low Value (LScale): 0 (value corresponding to LInput sensed value) Input High Value (HInput): 20 Scaled High Value (HScale): (value, up to 16383, corresponding to 20 milliamp input) See note below. NOTE: The HScale value should be set to give an output value for the Analog Input object that corresponds to the maximum temperature, flow, cfm, etc. that the sensor is measuring. The resolution of the value processed by this object must be taken into account when setting the HScale value because the input to output scaling and precision depends on this scaling constant. If the HScale value is less than 163.83, the input resolution is two decimal places and if greater than 163.83, integer resolution. An example of where this scale range is critical would be the use of a 0 to 5 volt air pressure transducer measuring an air pressure of 0 to 2 InWC. If the HScale is set to 2, the output would only resolve to 0.01. If the HScale value were set to 2000, the output would be in thousandths of an InWC, giving you an effective resolution of 0.001. Since this value is one thousand times the actual measured pressure, this 1000x scale factor would also have to be taken into account in any use of that value within the application.

Issue What hardware is required to connect directly to a BACnet/MSTP trunk containing just MNB controllers? Product Line TAC IA Series Environment I/A Series WorkPlace Tech I/A Series WorkPlace Tech Commissioning Tool I/A Series WorkPlace Tech Balance Tool Cause Replacement for the previously recommended adaptor, the B&B Electronics model USOPTL4. Resolution Purchase the following part: MNB-ROAM-IA.  This is used in conjunction with WorkPlace Tech.

Issue Is the new PSI / XPSI rev 4.1 compatible with Windows XP and Vista? Environment PSI / XPSI rev 4.1 Windows XP and Vista Cause Install PSI / XPSI rev 4.1 in a Windows XP or Vista Operating System (OS) Resolution The new PSI / XPSI rev 4.1 is compatible with Windows XP and Vista. Download PSI rev 4.1 from The Exchange. The zip file includes an installer and a READ.ME file that includes Release Notes and Installation Instructions. Note that the Patton Electronics RS-232 / RS-485 converter that has been widely used with the earlier versions of PSI (3.13) will not work with the new PSI / XPSI rev 4.1.  The B&B Electronics model USOPTL4 USB converter has been successfully tested with PSI / XPSI rev 4.1. Other recommended converters are listed in the Release Notes.

Issue Too much LON communications traffic can cause LON communications errors. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series MNL 800 Building Operation Automation Server Premium LON Network  I/A Series R2, AX, N4 Jace LON Network Cause Sending output LON SNVT values too frequently or more often than reasonably needed. Resolution There are a series of NCI (configuration) objects that control the transmission and reception of these data values on the LON network. One of four NCI objects (nciSndHeartBeatA, B, C, or D) is assigned to each NVO object in the application program. This value regulates the periodic LON transmission queuing of the NVO object values for each binding. One of four NCI  objects (nciRcvHeartBeatA, B, C, or D) is assigned to each NVI object in the application program. This value regulates the fallback timeout for each NVI object value. If a value is not received via the binding in this time period, the NVI object value will revert to its application-defined default value. In an MNL-800 controller, there are two additional NCI objects that are used to regulate the flow of data onto the LON network. The nciMinOutTime object is used to throttle the transmission of all data values queued to be sent via bindings over the LON network. This NCI object sets the transmission time interval between each NVO value being sent on the network. The important fact here is that the product of the number of bound NVO values times this interval (nciMinOutTime) must be LESS than the shortest nciSndHeartBeatX (X=A, B, C or D) interval. For example, if the Send HeartBeat is set to the default of 120 seconds and there are 60 NVO SNVTs bound from this controller, the nciMinOutTime must be set to a value of fewer than 2 seconds.  The recommendation for setting this SNVT value one half the shortest nciSntHrtBr divided by the number of NVO SNVTs bound from the controller.   The nciMinPropTm object is used to regulate the transmission queuing of changing bound NVO object values. This timer acts as a time-based filter to prevent a rapidly changing NVO value, such as a constantly changing temperature, from overwhelming the communication capacity of the LON network. Typically this value is set to a value of 1 to 5 seconds. Additional information can be found in Chapter 6 of the WorkPlace Tech Tool 4.0 Engineering Guide (F-27254). BACKGROUND: This section is provided to give the reader a basic understanding of bound LON communications, as applied to LON controllers in general. Data communications across a LON network is accomplished by using a LON Network management tool to create a binding between a device with a data source (NVO object) and one or more devices with data receivers (NVI objects) in other LON controllers. The device containing the data source will send the bound data value at a periodic rate, as defined by the associated SendHeartBeat NCI object, and whenever the value of that object changes. If the NVI object does not receive a value from the sender (bound NVO object) within a specified time period, as defined by the associated ReceiveHeartBeat NCI object, the NVI object will use a local fallback value until such time as it receives a new value via the binding.

Issue How to program a limit block for use in Niagara G3. Environment Niagara G3 Cause Limit are configure using the Reset object in the kitControl palette in the Math folder. Resolution Use the Reset object found in the kitControl palette in the Math folder.  To use it set the "Input Low Limit" and the "Output Low Limit" to the lowest desired output.  Set the "Input High Limit" and "Output High Limit" to the highest desire value. kitControl-Reset This component performs a linear “reset” on the inA value. Reset is available in the Math folder of the kitControl palette. Reset operation is defined by the following four slots: Input Low Limit — must be less than the Input High Limit Input High Limit — must be greater than the Input Low Limit Output Low Limit — may (or may not) be greater than the Output High Limit Output High Limit — may (or may not) be greater than the Output Low Limit For example, a Reset object is used to establish a hot water control setpoint, based on the outside air temperature at inA. When the outside air temperature is 0°F, the hot water setpoint is 200°F. When the outside air temperature is 75°F, the hot water setpoint is 100°F. The Reset object is configured as: Input Low Limit = 0.0 Input High Limit = 75.0 Output Low Limit = 200.0 Output High Limit = 100.0 Whenever the inA value is beyond the input limits, the output is limited by the corresponding output limit (in this case, 200 at 0°F or below, 100 at 75°F or above). When the input is at an intermediate value, the output scales linearly. For example, when the outside air temperature is at 38.2°F, the Reset output is 149.1°F.

Issue Warning - Platform running low on RAM disk space (Niagara G3 Release 3.2.5 and higher) Environment I/A Series G3 (typically embedded ENC/JACE platforms) Cause Low disk warning for history RAM disk A station fault will be generated if the free disk space on the history / alarm RAM disk falls below the minimum percentage specified on the PlatformServices property sheet. Resolution During station startup,  /niagara/bin/ramdisk.sh is invoked to create the RAM disk partition.   The RAM disk is named /aram0 and symbolic links are created from /alarm -> /aram0/alarm /history -> /aram0/history.  After the RAM disk is created it is populated with the contents of the alarm.zip and history.zip files.  During a station save or shutdown, the alarm and history files on the RAM disk are zipped and stored under the station directory in alarm/alarm.zip and history/history.zip.  If this fault occurs, users should take one or more of the following actions to prevent history/alarm data from being lost: Reduce number of histories that you are collecting Reduce number of records in each history Increase history RAM disk system (requires reboot). Action 3, above, will reduce the available system memory and should only be taken if there is sufficient free system memory.  Rather than writing history and alarm records directly to persistent storage, a Niagara G3 station stores history and alarm records in a RAM disk. This approach reduces the number and frequency of writes to flash.  Be careful not to increase too much otherwise you risk consuming all the available JACE free RAM causing the niagarad to crash.  Review the free system memory and make sure to leave a buffer of at least 1 MB of free RAM.  The RAM disk size is stored in /niagara/lib/platform.bog and can be adjusted using Services -> Platform Services. After reducing the number of histories, etc. the RAM disk will still indicate a low warning message until the unused histories are removed from the history storage.  Delete the unused histories using the Database Maintenance view on the history component view within the station.

Issue How do I configure oBIX (Open Building Information Exchange) to integrate a Niagara R2 station and a Niagara G3 station? Product Line TAC IA Series Environment Niagara R2 version 5.22 and later Niagara G3 version 3.4 and later Cause This document provides an overview of the integration of an R2 UNC to a G3 Enterprise Server using oBIX (Open Building Information Exchange). Resolution The R2 UNC must be licensed for "obix" and the obix jar file must be in the remote library of the UNC. Add the "ObixService" to the Services container of the UNC. Re-boot the UNC. The G3 Enterprise Server must be licensed for obix. Double-click the Drivers Component in the G3 Enterprise Server to open the Driver Manager. Add an Obix Network. Double-click the new Obix Network to open the Obix Client Manager. Click the "New" button at the bottom. Add a new "R2 Obix Client." Double-click the new R2 Obix Client. Enter a name for the UNC. In the Lobby field, enter http://, followed by the IP Address of the UNC, followed by "/obix". Enter the UNC's station username and password. Click OK. After a few seconds the state of the client should be "Attached." Expand the UNC Device in the Nav Tree. Double-click the points component to open the Obix Point Manager. Click the "Discover" button. After the points are discovered, expand "Lobby" and then "Config." (The Lobby is the root of a Server's oBIX object tree.) You can now scroll to see the containers and objects in the UNC's station. You can add UNC points to the G3 Enterprise Server's database in the usual manner. If you wish to have "link control" of objects in the UNC from the G3 Enterprise Server, then add an "Obix Export" object in the R2 Logic. These Obix Export Objects (analog, binary or multistate) are found in the Obix jar file in the remote library of the R2 UNC. Link pOut of the Export Object to pIn (if available) of the object you wish to control. Then link sOut of the R2 object back to the feedbackInput (fIn) of the export object. If no Priority Input is available on the R2 object, simply link the sOut of the Export Object to the sIn of the R2 object. No link to the feedbackInput of the Export Object is required. Return to the G3 Enterprise Server and discover the points in the R2 UNC. When adding the Export Point to the obixNetwork, the Export Objects default to type "Numeric Writable" so they can be commanded from the G2 Enterprise Server.

Issue In a Niagara G3 station, what is the difference between a Station Save and Backup Station? Product Line TAC IA Series Environment Niagara G3 (AX) Jace/ENC Niagara G3 (AX) Enterprise Server (ENS)  Cause Help determine which feature (Station Save and Backup Station) meet the requirement. Resolution A Station Save only saves the config.bog file to the local device (if an ENC, it will save the file on the ENC; if an ENS, it will save it on the ENS computer).  The Backup Station function performs a complete backup of the connected ENC or ENS station, saved as a dist file on the Workbench computer. The backup dist contains the entire station folder plus the specific NRE config used by that ENC or ENS platform, including license(s) and certificate(s). The dist also contains pointers to the appropriate NRE core, Java VM, modules, and OS. If ever needed, you can restore a backup dist using the platform Distribution File Installer view. The backup dist file also contains the TCP/IP configuration of the host when it is backed up. When restoring the backup, the choice to restore these settings, or retain the TCP/IP settings currently in use by the target host is available.

Issue Unable to connect to a Niagara R2 UNC-520.  The IP address was incorrectly set.  How can the IP address be found and changed if there's no access via the Ethernet port? Environment UNC-520 or UNC-410 Cause Incorrect entry of the IP Address or subnet mask can cause the UNC appear unresponsive to the WorkPlace Pro software. Resolution There are two methods available to determine the IP and subnet mask entered into the UNC. The first method requires having access to the computer used to change the IP address.  Look at the file "ipchanges.txt" located in the "\Niagara\r2.301.522\nre\user" folder. It will contain the date, time, user name, original IP, new IP, and controller name (i.e. 9:54 16-Dec-2008 CST: tac 10.159.34.123 -> 10.1.146.128 on J404-29764). The second method requires the use of a terminal program, a UNCC-405 to adapt RS232 to RJ45, and a CBL-RJ45 cable (a standard ethernet cable no longer than seven feet will do).  The HyperTerminal program is used to directly connect to a UNC-520 to verify and to make changes to its IP address in order to make it accessible.  HyperTerminal makes it possible to view the UNC's configuration and execute commands. The steps needed to directly connect to a UNC-520 using HyperTerminal are listed in chapter 2 of the Niagara Networking & Connectivity Guide.  After connecting to the UNC, use the procedure "Determining an IP address of a JACE-4/5" in the section "Determining Network Settings" of Chapter 3 of the same manual to display or change the IP address or subnet mask.  Failure to enter the subnet mask properly can prevent the UNC from being seen by WorkPlace Pro.

Issue Are MNB controllers RoHS compliant? Environment MNB controllers Cause Restrict dangerous substances commonly used in electronic and electronic equipment. Resolution All controller final assemblies will be RoHS compliant by the end of the 1st quarter of 2010.

Issue How to display the degrees symbol (°) in WorkPlace Tech. Product Line TAC IA Series Environment WorkPlace Tech Cause Helpful to add a suffix for temperature engineering units. Instead of typing "degrees" or "deg". Resolution In the Constant Object properties (double click or right click - Set Value), click in the Suffix Text field.    Desktop PC: If you have a desktop PC with a full keyboard, press and hold the Alt key and type the number 248 on the numeric keypad. Note: The number keys above the keyboard will not work. Notebook PC: The numeric keypad on a notebook PC is overlaid on the letter keys (M, J, K, L, U, I, O, 7, 8, 9), and requires that the Fn key is held down while using this secondary purpose. The Fn key may be colored blue to match the number keypad keys. Press and hold both the Alt and Fn keys and type the number 248 (KU8). Release the Alt key (and Fn key on the laptop). A small circle ° (the symbol for degrees) should appear. Type an upper case F for Fahrenheit or C for Celsius. Click OK.   Other ASCII symbols are defined at asciitable.com or lookuptables.com.

Issue How can the Niagara G3 ENC platform be accessed if the user name and password have been forgotten? Environment Niagara G3 ENC Cause Forgot username and password for the Niagara G3 ENC. Resolution To connect via the serial port of the ENC you will need a UNCC-405, an Ethernet cable 7' or less, and Hyperterminal (or another terminal program). In the upper right corner of the ENC-520 is a block of four pins marked J4 Mode. Using one of the bias jumpers from the board, temporarily short the front two pins. Using the UNCC-405 and short Ethernet cable connect the laptop to serial port one of the ENC. Open HyperTerminal and configure a connection as 57600, 8, none, 1, no flow control. Reboot the ENC. When this appears: "Press ESC to restore factory default username and password...", go ahead and press the ESC key. Enter "y" when prompted to force the platform user name and password back to "tac" and "niagara". After using WorkBench to verify the user and password have been changed, remove the jumper and disconnect the serial connection.