Issue Are all four RS-485 ports licensed for use with BACnet/MSTP on a Niagara G3 ENC-520? Environment Niagara G3 ENC-520 Cause Licensing information about the Niagara G3 will help during installation. Resolution Yes.  At any time, any of the four RS-485 ports can be used without the need for re-licensing.

Issue Sending a Service Pin message (Neuron id) thru a Micronet S-Link sensor. Environment MN-S2xx, S3xx, S4xx and S5xx MN-S4-FCS sensors MN-S4HT-FCS sensors Cause The Service PIN message is used to identify the device. There is not a visible service pin button located on the device. Resolution A service pin message (Neuron id) can be sent by pressing the override key (button) for more than 8 seconds (on models MN-S2xx, S3xx, S4xx and S5xx). For the MN-S4-FCS and MN-S4HT-FCS sensors, press the fan on/off key for more than 8 seconds(to send a service pin message). The system override/on-off LED will flash one time indicating the message was sent. Additional information is in the WorkPlace Tech Tool 4.0 User's Guide (F-27255) under the compiling and downloading application (and the uploading) section.

Issue What if any voltage can be measured on a Micronet 2000 U-Bus? Environment MicroNet 2000 U-Bus communication Cause Information about voltage helps implement multiple MicroNet 2000 controllers in U-Bus communications interface. Resolution The U-Bus is a Wired-OR open collector communication bus talking at 2400 baud. The MN-ASDI has the U-Bus current source.  It supplies the current for the U-Bus communications. It should supply about 45 ma. with short circuit protection. Under normal communications, the U-Bus voltage will be around 15 volts +/- 2 volts when measured with a voltmeter.

Issue The Niagara R2 version 522 Workplace Pro 'new station' wizard lists four vlon services. Environment Niagara R2 Cause The four vlon services is part of the new station wizard; Schneider Electric currently using vlon0. Resolution The new station wizard now lists services vlon0, vlon1, vlon2, and vlon3. Previous builds only listed a vlon service. These new vlons relate to the lonworks multiple services that have not been used by Schneider-Electric.   For tunneling to operate, select the vlon0 service for use with the lonworks service.

Issue In Niagara R2, can WebUI be set to auto-logoff web users? Environment Niagara R2 Cause Unfortunately, the browser sessions use "HTTP Basic Authentication" a protocol that has no provisions for de-authentication or automatic logoff. Resolution The only logoff feature applies to JDE sessions in WorkPlace Pro. Tridium does not plan to add this mechanism to Niagara R2.   Niagara G3 software provides a web profile (cookie authentication) for each user that includes a feature for automatic logoff via the browser.

Issue When using a Niagara R2 Master Enterprise Server, do the projects require the same Project ID? Environment Niagara R2 Master Enterprise Server Cause Project ID is required for license information. Resolution Example: Two projects will eventually have a Master Enterprise Server (MES) over both of them.  One of the projects is in progress and the second phase will follow.   In order to use a MES and allow both projects to communicate with it, do both projects need to have the same Project ID? Or can each separate Enterprise Server maintain its own Project ID?   Requirement: The MES is licensed to support multiple Enterprise Servers (with different project IDs). Purchase the IA-MES-1 which supports an Enterprise Server for one site.  Additionally, each IA-MES-N would add another Enterprise Server (additional site). The project IDs for each Enterprise Server site would have to be provided in the license request form. The license will then list multiple project IDs and add the multisite feature.

Issue How can Modbus address xxxx, function 16 be written? Environment Modbus driver Cause To use function code 16 instead of 06, configure the properties usePresetMultipleRegister and usePresetMultipleCoil Resolution By default, the Modbus driver uses function codes 05 (Force Single Coil) and 06 (Force Single Register) and can be set up to support the Force Multiple function codes. Navigate to the Modbus Service properties -> General – Config tab. Set the properties usePresetMultipleRegister and usePresetMultipleCoil both to true. The driver will now write using function code 16 instead of 06 for both the ModbusGenericAO and ModbusPresetRegister objects.

Issue What is the Analog to Digital Output resolution of the MNL controllers? Environment MNL Controllers Cause Analog/Digital conversion resolution Resolution The MNL controllers (with the exception of the MNL-800) have a 10-bit equivalent UI resolution and an 8-bit output resolution. The MNL-800 has a 12-bit equivalent UI resolution and an 8 bit output resolution.

Issue What is the Analog to Digital Output resolution of the MNB controllers? Environment MNB Controllers Cause Analog to Digital conversion resolution. Resolution The MNB BACnet controllers have 12-bit resolution on the inputs and 8-bit resolution on the analog outputs.

Issue Can the MNL controllers be powered by DC voltage? Environment MNL controllers DC voltage input Cause Using DC voltage is not recommended or supported. Resolution The MNL controllers are not specified for DC operation and all agency approvals were submitted using a power source of 24 VAC 50/60 Hz.

Issue Can the MNB controllers be powered by DC voltage? Environment MNB controllers DC voltage input Cause Using DC voltage is not recommended or supported. Resolution The MNB controllers are not specified for DC operation and all agency approvals were submitted using a power source of 24 VAC 50/60 Hz.

Issue How to configure serial tunneling for MicroSmart networks in Niagara G3. Product Line TAC IA Series Environment Niagara G3 OPRIF 11.x Cause Documented procedure with figures don't identify all steps clearly Resolution This video will help you set up and use serial tunneling with MicroSmart networks in Niagara G3.

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 Configuring the LON Router (LPR-10) within a Niagara R2 System Environment Niagara R2 system LPR-10 Cause Procedure to configure LON Router (LPR-10) in Niagara R2. Resolution Since most LonWorks networks are unmanaged (that is, managed only by the Niagara station's Lon Device Manager), use the procedure beginning on page A-9, of the Niagara LonWorks Integration Guide, to define the LonWorks network.  Before beginning this process, cut the existing LonRouter and Channel1 from the station. Set the status of all of the Lon devices to "Unknown". The most important part of this process is defining the router and associated channels before beginning any of the automated processes using the LonDeviceManager. Ensure four LON-TERM-2 devices (LON BUS Topology Terminators) are installed. One at each end of the trunk and one at the near end of the router and one at the far end of the router.

Issue Is Niagara R2 compatible with Windows Server 2003? Environment Niagara R2 Windows Server 2003 Cause Compatibility Resolution Niagara version 514 and higher was officially certified to operate with Windows NT, Windows XP, and Windows Server 2003. As a side note, if using Windows Server 2003, there are two issues to be aware: Windows Server will use IIS services causing a conflict with TCP port 80. This will have to be addressed when engineering the station database. There is an issue with Niagara and Windows Server 2003. Tridium released a Tech Tip as follows: R2 Web Supervisor on Windows 2003 Service Pack JDE will not start. If fui.exe is run from within the Windows command prompt, the following error is displayed: Error occurred during initialization of VM Could not reserve enough space for object heap. The problem is limited to instances where the user is accessing the computer with a Remote Desktop connection. On 8/8/2006, Microsoft issued an update KB921883 which unintentionally causes problems with applications that use large amounts of contiguous memory on a Windows Server 2003 Service Pack 1-based computer. There is a Hotfix now available to resolve the issues generated by this update. Hotfix KB924054.

Issue How can two stations run concurrently on a Niagara R2 computer? Product Line TAC IA Series Environment Niagara R2 Cause Operate two stations by running each station on different port. Resolution In order to run two stations simultaneously, set up one of the stations to run on a different port. By default, the station database is set up to run on port 80. Attempting to start a second station will fail if it finds the port unavailable. Open the second station offline; right click on the station root, and select properties. On the configuration tab, set the httpPort to another value (e.g. 8080). Save and close the station database. The station should now start without conflict. Remember to open the station with the IP address followed by the port (e.g. 10.1.146.25:8080). Also, for live external links to work, the address books would have to match (adding the port number).

Issue Lifecycle margin versus actual station database resource count in Niagara R2. Environment Niagara R2 Cause When pasting objects that are over the maximum allowance size, it will not paste the object because the copy or cut maximum size is depend on the Lifecycle margin. Resolution The UNC-410, UNC-510, and UNC-520 platforms all have a resource count limitation of 600,000.  The TRD-NXT has a resource count limit of 2,500,000. The total number of available resources is the same regardless of support for Web services. The (Search > Resource Count) function under the WorkPlace Pro Search menu item will count the number of resources used. The count is performed from the object currently selected on the JDE tree and includes all child objects. By selecting the station's root name, the resource value for the entire station database will be provided. The dialog box with the information provides the calculated actual Resource count and also will indicate the Lifecycle margin: 20,000. The Lifecycle margin is a JDE term that specifies the maximum size (in resource count) of any “cut” or “copy” permitted in a running station. A cut or copy effectively creates a temporary new tree of objects within the memory of the host. This mechanism is used to support the JDE's “undo” operation (Edit > Undo). As an example, try to cut & paste something and it won't be allowed because of resources.  After checking, for instance, that there is a 43,000 resource count with a lifecycle margin of 20,000, what is happening is that the cut and paste has a total resource count higher than 20,000 which is the max. Perform the cut and paste in smaller portions.

Issue What do the network mismatch errors in WorkPlace Commissioning Tool mean? Environment  WorkPlace Commissioning Tool Cause Information to troubleshoot network mismatch errors in WorkPlace Commissioning Tool. Resolution These errors are described in the WorkPlace Commissioning Tool and Flow Balance Tool Users Guide (F-27358) page 175.

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.