Building Automation Knowledge Base

Issue What are the Linking Rules within the Niagara R2 platform? Environment Niagara R2 platform Cause Additional information on linking rules to correctly linked objects. Resolution In most cases, in order for two properties to be linked, they must use the same data species. In a link, one object's output supplies the value (or trigger) used by the other object with the receiving input. The Link Editor in the JDE enforces this rule when selecting a property on one side of the window to link.  An exception to the need for matching data species occurs when linking Gx objects, which have only inputs. For example, the "binding" input of a GxText object can be linked to any internal (configuration property) of another object, in addition to most output properties.  When linked to an internal property, a GxText object displays text showing the value of that property.  Unlike "normal" links, Gx object links are considered user-interface ("ui") links, not part of "control logic." Instead, they provide the building blocks of a user interface. The Link Editor also enforces additional link rules. Many inputs can be linked to a single output as needed ("one-to-many").  For any input property that is already linked, no further link to it is permitted unless the property is a priorityArray type or trigger type (or certain types of Lon properties). Only then is a "many-to-one" link allowed. External links (between stations) have further restrictions. The following types of external links are not permitted (nor are they shown in the Link Editor): Links between prioritizedOutputs and priorityArray input properties. Links between properties using triggerType data species. Links from a GxText object to an internal property of another object (only inputs or outputs are available).

Issue What is the difference between the XIF and NXE files in any LON controller? Environment LNS LON Controllers NL220 LonMaker Cause There are different files related to a LON device. The XIF and NXE files have completely different purposes. Resolution The XIF is a text-based file that defines the device’s network image to a network management tool (e.g. Niagara, LonMaker, etc.). The XIF along with files termed device resource files (DRFs) are used by the management tools to work with the LON device. Device resource files provide definitions especially when the manufacturer has not used standard SNVT types. When requesting a shadow object from Tridium, the XIF file must be provided as a minimum. If the manufacturer has defined their own variable types, the associated set of device resource files must also be provided. The only other alternative would be to use a dynamic device and hope that the device’s manufacturer implemented the files within the device correctly. When a dynamic device is commissioned, Niagara will upload the XIF from the device and attempt to create an object from the file’s definitions. The NXE is an abbreviation for (Neuron Executable file). Some devices allow the user to download an NXE or new application image file that changes the operation and / or network interface of the target device. New or different application firmware can be downloaded to the Neuron. This is the way some manufacturers upgrade their devices and / or the network interface portion of the device. If the LON device can support an NXE, this would have to be provided by the device’s manufacturer.

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 How can it be determined what LonWorks Program IDs are supported by the Niagara R2 system? Environment Niagara R2 system LonWorks Cause To determine the LonWorks Program IDs, run the command "Command of Reports and Sub-command of programids" in Lon Utilities Manager. Resolution Create and install a test station on the localhost that includes the Lonworks service, Lonworks Network container, and the LocalLonDevice. Open the test station in WorkPlace Pro then right click on the Lonworks Service and open the Lon Utilities Manager. Select the LocalLonDevice then choose the Command of Reports and Sub-command of programids. Execute the command and a listing of all programIDs for the shadow objects found in the local tridiumx library (lonDevices container) will appear. Save this report to a text file and import into Excel where searches can be performed. Re-run the report anytime a new lon jar file is added or an existing lon jar file is replaced with a newer version.

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 can a Network 8000 GCM-84000 or GCM-86000 be connected to the Niagara R2 UNC-520 RS-232 port? Environment Network 8000 GCM-84000 GCM-86000 Niagara R2 Cause To use Network 8000 GCM-84000 or GCM-86000 with Niagara R2, connect using a pre-built adapters and silver satin cables. Resolution Pre-built adapters and silver satin cables for this type of connection are available for order.   The RJ-45 to DB-9 adaptor (UNCC-405) will interface to the GCM-86000. The RJ-45 to DB-25 adaptor (UNCC-430) will interface to a GCM-84000. A series of pre-terminated silver satin cables are available in three standard lengths: CBL-RJ45-4 Silver satin patch cable, 4 feet in length CBL-RJ45-10 Silver satin patch cable, 10 feet in length CBL-RJ45-25 Silver satin patch cable, 25 feet in length

Issue How can a DMS-35, DMS-350A or DMS-3500 be connected to a Niagara R2 UNC-520 RS-232 port? Environment Niagara R2 UNC-520 DMS-35 DMS-350A DMS-3500 Cause To use a DMS with Niagara R2, connect using a pre-built adapters and silver satin cables. Resolution Pre-built adapters and silver satin cables for this type of connection are available for order.   The RJ-45 to DB-9 adaptor (UNCC-405) will interface to the DMS-350A and DMS-3500 panels. The RJ-45 to DB-25 adaptor (UNCC-430) will interface to the DMS-35 panel. A series of pre-terminated silver satin cables are available in three standard lengths: CBL-RJ45-4 Silver satin patch cable, 4 feet in length CBL-RJ45-10 Silver satin patch cable, 10 feet in length CBL-RJ45-25 Silver satin patch cable, 25 feet in length

Issue S-E L2SV Linkage Kit and S-E L7SV Linkage Kit compatibility with Satchwell Plug and Seat Valve Bodies. Environment Satchwell 1 series Plug and Seat 2-port and 3-port Valve Bodies. Satchwell 2 series Plug and Seat 2-port and 3-port Valve Bodies. Satchwell 3 series Plug and Seat 2-port and 3-port Valve Bodies. Satchwell 7 series Plug and Seat 2-port and 3-port Valve Bodies. Cause Use the correct S-E Linkage Kit with Satchwell Plug and Seat Valve bodies. Resolution 1.  Observe specification number of Satchwell Plug and Seat Valve Body Generally where a Satchwell AL series Linear Actuator is fitted to a Satchwell plug and seat Valve Body, the Actuator may be replaced by an equivalent S-E Forta or MV15B series Linear Actuator and appropriate S-E Linkage Kit. It should be noted however that neither the S-E L2SV Linkage Kit nor the S-E L7SV Linkage Kit will enable an S-E Forta or MV15B series Linear Actuator to be mounted on a Satchwell 7 series MZ/MZF or a Satchwell 7 series VZ/VZF plug and seat Valve Body. The internal screw threads of the Neck Adaptors included in the S-E L2SV Linkage Kit (880 – 0124 – 000) and S-E L7SV (880 – 0126 - 000) Linkage Kit are compatible with the external screw threads on Satchwell 1, 2 & 3 series Valve Body necks only. The external screw threads on Satchwell 7 series Valve Body necks however differ to those on Satchwell 1, 2 & 3 series Valve Body necks. Consequently neither the S-E L2SV Linkage Kit nor the S-E L7SV Linkage Kit will enable an S-E Forta or MV15B series Linear Actuator to be mounted on a Satchwell 7 series Valve Body. A S-E Forta series Linear Actuator may be mounted on a Satchwell 7 series Valve Body however using Linkage Kit 880 – 0135 – 000.  No equivalent Linkage Kit is currently available for use with the MV15B series Linear Actuator. The Satchwell Valve Body series may be determined from the Valve Body specification number stamped on the Valve Body Identification Collar, where the single middle digit of the specification number denotes the series. In the case of a Satchwell 7 series Valve Body for instance the single middle digit of the specification number will be the number 7 (e.g. 626 – 7 – 402)

Issue How to remove, from a Niagara R2 Enterprise Server station, data for all logs prior to a specific date with one command. Product Line TAC IA Series Environment I/A Series R2 Enterprise Server Cause Cloudscape database management Resolution There is a utility that will allow deleting of records before a certain date of all or specific tables in the cloudscape database. The space from deleted records can also be recovered after deleted. This utility is called CloudscapeAdmin and is downloadable from The Exchange Download Center. Download cloudscapeAdmin.jar and place in the x:\niagara\[NiagaraRevision]\nre\lib directory (for Builds 431 and higher). To run this utility the station will need to be stopped. Once the station is stopped, open the console from either the created short cut or x:\niagara\[NiagaraRevision]\nre\bin\console.exe. From here type ‘nre CloudscapeAdmin’ and hit enter to view the commands to use it.  There are two functions that cloudscapeAdmin can do: Delete; The delete command deletes records before a certain date but does not reduce the size used on the disk. The empty area of the database will be filled with new archived data. Compact; The compact command deletes records before a certain date and recovers the space from the disk. This process is slower. Command: nre CloudscapeAdmin x:\niagara\[Niagara Revision]\stations\[Station Name] [User Name] [Password] [delete or compact] [tablename or all] [date] Sample Delete commands: nre CloudscapeAdmin c:\niagara\r2.301.522a\stations\StationName admin admin delete all 2007-07-01 Sample Compact commands: nre CloudscapeAdmin c:\niagara\r2.301.522a\stations\StationName admin admin compact all 2007-07-01

Issue Writing directly to a SR (set-reset) simple block in a Xenta 700 Menta application where that SR output is sent to a Delay block, the Delay block may not delay. The output on the Delay block will be set immediately, without any delays. Environment Xenta Servers version 5.1.1 and lower Xenta 701, 711, 721, 731 Menta Cause This was a bug in version 5.1.1 and lower. Resolution Upgrading the Xenta Server to version 5.1.2 or later will resolve the issue. If upgrading is not an option, this can be worked around by not writing to the SR block itself, but to a block in the logic before the SR block.

Issue Writing directly to DELB (delay binary) simple block in a Xenta 700 Menta application where that DELB output is sent to a TRIG block, the TRIG block may not work. Environment Xenta Servers version 5.1.1 and lower Xenta 701, 711, 721, 731 Menta Cause This was a bug in version 5.1.1 and lower. Resolution Upgrading the Xenta Server to version 5.1.2 or later will resolve the issue. If upgrading is not an option, this can be worked around with one of these options: Write to a block prior to the DELB block, not the DELB block itself Put a second DELB block at the end before the TRIG block

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 Can't  Override/force an I/O point on an I/O-Module connected to a Xenta 7xx Environment Vista Xenta 7xx Cause Xenta 7xx way of override value has been changed from the way Xenta 4xx did Resolution There are no way of forcing the RI/BI or RO/BO signals like you can do with the AI/AO DI/DO in Xenta 300/400/280. In the 700 you can only force the real physical point. You find the points under the Xenta Server object $IO.