Niagara PRO TIPS: Web Charts Relative Ord's

Niagara PRO TIPS: Web Charts Relative Ord's

Video Tutorial: Niagara PRO TIPS: Web Charts Relative Ord's

Overview

This guide covers how to embed web charts into PX views using relative ORDs (Object Reference Descriptors) in the most robust and easy way. Learn three different methods for creating reusable, flexible chart views that work across multiple devices.

What are Relative ORDs?

ORD (Object Reference Descriptor) is Niagara's way of referencing objects in the station hierarchy.

Relative ORDs use special syntax like slot: to reference objects relative to the current context (e.g., the device the PX view is assigned to), rather than using absolute paths.

Benefits of Relative ORDs:

• Reusability - Same PX view works for multiple similar devices

• Flexibility - No need to create separate views for each device

• Maintainability - Update one view, applies to all devices

• Scalability - Easy to deploy across large systems

Example Setup

Station Structure

JACE-8000 Station
└── BACnet Driver
    └── Air Handler Devices
        ├── Air Handler 1
        │   └── Points
        │       ├── Room Temp (with history extension)
        │       ├── Room CO2 (with history extension)
        │       └── Room Humidity (with history extension)
        ├── Air Handler 2
        └── Air Handler 3

PX Views Assigned to Air Handler

• Graphic - Visual representation

• Responsive - Responsive layout

• Chart View - The focus of this tutorial

Creating the Base Chart View

Step 1: Create Empty Chart View PX

1. Create a new PX view

2. Add header and frame elements

3. Position elements as desired for your UI layout

4. Do not add web chart yet

Method 1: Using slot: (Simplest Method)

Best For:

• Quick setup

• When you want to display all available histories

• Simple chart requirements

Step 1: Add Web Chart to PX View

Option A - Drag from Point:

1. Drag one of the points with history into the PX view

2. Choose Workbench View

3. Select Web Chart

Option B - Drag from Palette:

1. Open the Web Chart Palette

2. Drag a chart widget into the PX view

3. Position it where desired

Step 2: Configure WB View Binding with slot:

1. Select the web chart widget

2. Find the WB View Binding property

3. In the ORD field, enter: slot:

Syntax:

slot:

How It Works

Automatic Resolution:
When you specify slot: as the relative ORD:

1. The workbench/UI resolves the device the PX view is assigned to

2. Looks underneath that device for any points with:

   • History extensions

   • end:history tags

   • Historical data (imported from Ion network, etc.)

3. Automatically displays the first 10 histories it finds

Advantages of slot:

✅ Easiest method - just one setting
✅ Automatic history detection
✅ No need to specify individual points
✅ Works immediately with any device that has histories

Limitations of slot:

❌ Shows ALL available histories (up to 10)
❌ No control over which specific histories display
❌ If more than 10 histories exist, only shows first 10 found
❌ Cannot control the order of histories

Method 2: Multiple WB View Bindings (Recommended)

Best For:

• Specific history selection

• Controlling which histories display

• When you have more than 10 histories but only want specific ones

• Working with on-demand PX views

• Virtual ORDs in supervisor

Step 1: Add Web Chart to PX View

Same as Method 1 - add a web chart widget to your PX view.

Step 2: Configure First WB View Binding

Instead of just slot:, specify a specific point:

Syntax:

slot:points/[PointName]

Example:

slot:points/RoomTemp

What This Does:

• Resolves to the current device (slot:)

• Navigates to the points folder

• Finds the specific point (RoomTemp)

• Displays ONLY that history

Step 3: Add Additional WB View Bindings

Web charts can display up to 10 histories at a time.

Add Second Binding:

1. In the web chart properties, find Bindings

2. Click Add Binding

3. Select Workbench WB View Binding

4. Configure the ORD:

slot:points/RoomCO2

Add Third Binding:

1. Click Add Binding again

2. Select Workbench WB View Binding

3. Configure the ORD:

slot:points/RoomHumidity

Step 4: Continue Adding Bindings (Up to 10)

Repeat the process to add up to 10 total bindings:

Binding 1: slot:points/RoomTemp
Binding 2: slot:points/RoomCO2
Binding 3: slot:points/RoomHumidity
Binding 4: slot:points/SupplyTemp
Binding 5: slot:points/SupplyFan
... (up to 10 total)

Result

The chart will display only the specific histories you've configured, in the order you added them.

Advantages of Multiple WB View Bindings

✅ Precise control over which histories display
✅ Control the order histories appear
✅ Works with on-demand PX views
✅ Compatible with virtual ORDs in supervisor
✅ No unnecessary histories displayed
✅ Still fully relative - works across devices

Why This is James Johnson's Preferred Method

"I personally like the multiple WB view bindings because it works with on-demand PX views, virtual ORDs and stuff in the supervisor."

Key Benefits:

• Most flexible for complex deployments

• Works in all scenarios (standard views, on-demand views, supervisor)

• Maintains reusability while providing precise control

Method 3: Saved Chart Files

Best For:

• Customizing default chart appearance

• Creating chart templates

• Standardizing chart configurations

• Sharing chart configurations across projects

Understanding Absolute vs. Relative ORDs

Absolute ORDs:

station:|slot:/Drivers/BacnetNetwork/AHU_1/points/RoomTemp

• Full path from station root

• Device-specific

• Not reusable across devices

Relative ORDs:

slot:points/RoomTemp

• Relative to current context

• Device-agnostic

• Reusable across similar devices

Step 1: Build Chart with Absolute or Relative ORDs

When building your chart by dragging and dropping:

• The system may assign absolute ORDs by default

• This is okay - we'll convert them during export

Example Absolute ORD Configuration:

Binding 1: station:|slot:/Drivers/BacnetNetwork/AHU_1/points/RoomTemp
Binding 2: station:|slot:/Drivers/BacnetNetwork/AHU_1/points/RoomCO2
Binding 3: station:|slot:/Drivers/BacnetNetwork/AHU_1/points/RoomHumidity

Step 2: Export Chart File

1. With the web chart selected, locate the Export option

2. Click Export Chart File

3. Choose export options:

   • ORD Type: Select Relative (not Absolute)

   • Chart File Name: Enter desired name or keep default

4. Click OK

What Happens:
A chart file is saved in your Charts directory in the station.

Step 3: Verify Relative ORDs in Chart File

You can verify the ORDs were saved as relative:

1. Locate the saved chart file in the Charts directory

2. Right-click → Open with Text Editor

3. Search for slot:

4. Confirm ORDs are relative (e.g., slot:points/RoomTemp)

Example Chart File Content:

<WbViewBinding ord="slot:points/RoomTemp"/>
<WbViewBinding ord="slot:points/RoomCO2"/>
<WbViewBinding ord="slot:points/RoomHumidity"/>

Step 4: Embed Saved Chart File in PX View

Now you can reuse this chart file across multiple PX views:

1. Open your Chart View PX (or create new one)

2. Drag the saved chart file from Charts directory into the PX view

3. Choose Workbench View

4. Select Chart

Result:
The saved chart file is embedded in your PX view with all relative ORDs intact.

How Saved Chart Files Resolve

When the PX view is assigned to a device:

1. The chart file's relative ORDs resolve to that specific device

2. slot:points/RoomTemp resolves to the RoomTemp point on the current device

3. Works automatically across all similar devices

Advantages of Saved Chart Files

✅ Reusable templates - Create once, use many times
✅ Customizable defaults - Preset chart appearance/settings
✅ Flexibility - Can modify chart settings before saving
✅ Centralized updates - Update chart file, affects all PX views using it
✅ Standardization - Consistent look across project

Additional Benefits

Chart Customization:
Saved chart files allow you to customize:

• Default time ranges

• Chart colors and styles

• Axis settings

• Sampling preferences

• And more...

"The saved chart file can give you some flexibility maybe about making some changes to how the chart's going to render by default."

Method Comparison

Best Practices

When to Use Each Method

Use Method 1 (slot:) when:

• Quick setup is priority

• You want all available histories displayed

• Device has 10 or fewer histories

• No specific history selection needed

• Building simple monitoring views

Use Method 2 (Multiple Bindings) when:

• Need precise control over which histories display

• Working with on-demand PX views

• Using virtual ORDs in supervisor

• Want to control history order

• Device has more than 10 histories

• Building production systems

Use Method 3 (Saved Chart Files) when:

• Creating standardized chart templates

• Need to customize default chart appearance

• Want to share configurations across projects

• Building multiple similar charts

• Need centralized chart management

Complete Workflow Example

Scenario: Create reusable chart view for multiple air handlers

Requirements:

• Display 3 specific histories: Room Temp, Room CO2, Room Humidity

• Same view should work for AHU-1, AHU-2, AHU-3, etc.

• Want consistent appearance across all charts

Solution Using Multiple Bindings (Recommended):

Step 1: Create Chart View PX

1. Create new PX file: ChartView.px

2. Add header, frame, and layout elements

Step 2: Add Web Chart

1. Drag web chart from palette

2. Position in layout

Step 3: Configure Bindings

Binding 1:
  Type: Workbench WB View Binding
  ORD: slot:points/RoomTemp

Binding 2:
  Type: Workbench WB View Binding
  ORD: slot:points/RoomCO2

Binding 3:
  Type: Workbench WB View Binding
  ORD: slot:points/RoomHumidity

Step 4: Assign to Devices

1. Assign ChartView.px to AHU-1

2. Assign ChartView.px to AHU-2

3. Assign ChartView.px to AHU-3

Result:

• Same PX view works for all air handlers

• Each displays data from its own Room Temp, CO2, and Humidity points

• Fully maintainable - update one PX, affects all devices

Understanding Relative ORD Syntax

Basic Syntax Elements

slot:                          → Current device (where PX is assigned)
slot:points/                   → Points folder under current device
slot:points/RoomTemp          → Specific point under current device
slot:points/RoomTemp/history  → History extension of that point

Path Navigation

slot:                  → Current level
slot:../               → Parent level
slot:../../            → Grandparent level
slot:/Drivers/         → Absolute path from station root

History Detection

Niagara automatically detects histories by looking for:

• History extensions on points

• end:history tags

• Historical data (local or imported)

Key Reminders

Web Chart Limitations

⚠️ Web charts can display a maximum of 10 histories at one time

If you need more than 10 histories:

• Create multiple charts

• Use separate chart views

• Or filter to most important 10 histories

Relative ORDs Work With:

✅ Standard PX views
✅ On-demand PX views
✅ Virtual ORDs in supervisor
✅ Multiple device instances
✅ Templated deployments

Troubleshooting

Chart Shows No Data

Possible Causes:

1. ORD path is incorrect

2. Point doesn't have history extension

3. Point missing end:history tag

4. No historical data collected yet

Solution:

• Verify ORD syntax

• Check point has history extension

• Confirm data collection is active

Chart Shows Wrong Histories

Possible Causes:

1. Using slot: showing all histories automatically

2. ORD pointing to wrong point name

3. Point name mismatch between devices

Solution:

• Use specific bindings (Method 2)

• Verify point names match across devices

• Check for typos in ORD paths

Chart Not Reusable Across Devices

Possible Causes:

1. Using absolute ORDs instead of relative

2. Chart file exported with absolute ORDs

3. Point names differ between devices

Solution:

• Use relative ORD syntax (slot:)

• Export chart files with relative ORDs

• Standardize point naming across devices

Coming Up

In future videos, we'll cover:

• Customizing web chart default settings

• Advanced chart configuration options

• Creating chart templates with preset styles

• Width options and responsive layouts

Quick Reference

Method 1: Simple slot: Binding

WB View Binding ORD: slot:
Result: Shows first 10 histories found under device

Method 2: Multiple Specific Bindings

Binding 1 ORD: slot:points/RoomTemp
Binding 2 ORD: slot:points/RoomCO2
Binding 3 ORD: slot:points/RoomHumidity
Result: Shows only specified histories

Method 3: Saved Chart File

1. Build chart with bindings
2. Export → Choose Relative ORDs
3. Save to Charts directory
4. Drag into PX views as needed
Result: Reusable chart template

Key Takeaways

✅ Relative ORDs enable reusable, flexible chart views across multiple devices
✅ Three methods available, each with specific use cases and benefits
✅ Multiple WB view bindings (Method 2) recommended for production systems
✅ slot: syntax provides device-relative referencing
✅ Web charts support up to 10 histories simultaneously
✅ Saved chart files enable templating and standardization
✅ Export with relative ORDs to maintain reusability
✅ Works with on-demand PX views and virtual ORDs

Presenter: James Johnson
Series:Niagara PRO TIPS
Topic:Web Charts Relative Ords
Key Concept:Creating reusable, maintainable chart views using relative ORD syntax

YouTube: http://www.youtube.com/@TridiumInc