Virtual Px Issues with Alarm Console in Niagara

Virtual Px Issues with Alarm Console in Niagara

This article addresses compatibility issues when using virtual Px pages from JACE controllers in a Niagara Supervisor, particularly with alarm console components.

Understanding Virtual Px

Virtual Px pages are graphics that reference the station's points rather than hardcoded paths. They're designed to be reusable across multiple instances of similar equipment.

Virtual Px Concept

The Multi-Site Problem

Architecture

When virtual Px pages are brought from JACEs to a Supervisor via station copying or navigation, certain components may not function correctly.

Affected Components

Alarm Console

The alarm console widget relies on:

• Alarm service references
• User permissions context
• Station-specific alarm classes

When moved to Supervisor: References may break because alarm service paths differ between JACE and Supervisor.

Other Affected Components

• History trend charts (history references)
• Schedule widgets (scheduler service paths)
• User management displays (auth service)
• Device status components (driver-specific)

Root Causes

1. Hardcoded Service Paths

Some components reference services with absolute paths:

station:|slot:/Services/AlarmService  ← JACE path
station:|slot:/Drivers/NiagaraNetwork/Site1/Services/AlarmService  ← Supervisor path

2. Missing Services on Supervisor

JACEs have local services (alarm, history) that may not exist at the same path on Supervisor.

3. Permission Context Changes

JACE may run in different security context than Supervisor graphics.

Solutions

Solution 1: Use Server-Specific Graphics

Create separate graphics for Supervisor vs JACE viewing:

JACE Version:

• References local alarm service
• Optimized for JACE context

Supervisor Version:

• References proxied alarm service
• Uses Supervisor-compatible paths

Solution 2: Virtual Service Bindings

Instead of hardcoding alarm service path:

Bad:  station:|slot:/Services/AlarmService
Good: $(station)/Services/AlarmService

Or use relativized ORDs:

slot:../../../Services/AlarmService

Solution 3: Alarm Console Configuration

For alarm console widgets specifically:

1. Check Alarm Service binding - Ensure it uses relative or virtual path
2. Configure Alarm Class Filter - May need adjustment for Supervisor context
3. Set appropriate time range - Supervisor may have different history depth

Solution 4: Network Alarm Aggregation

On Supervisor, use network alarm console that aggregates from multiple stations:

1. Add Network Alarm Console widget
2. Configure to pull from NiagaraNetwork driver
3. Filter by station/device as needed

Step-by-Step Fix

For Existing Virtual Px Pages

1. Open page in Px Editor on Supervisor
2. Select alarm console widget
3. Check Alarm Service property:
   • If absolute path → change to relative
   • If missing → rebind to Supervisor alarm service
4. Test navigation from different entry points
5. Verify alarms display correctly

For New Implementations

1. Use relative bindings from the start
2. Test on both JACE and Supervisor during development
3. Document which graphics are station-specific vs portable
4. Consider network-level alarm views for Supervisor

Prevention Best Practices

When Creating Virtual Px Pages

Do	Don't
Use relative ORDs	Hardcode absolute paths
Test on target platform	Assume JACE = Supervisor
Document service dependencies	Leave bindings unconfigured
Use virtual path variables	Reference specific device names

Multi-Contractor Environments

1. Establish graphics standards before development
2. Define service path conventions across contractors
3. Require testing on Supervisor before deployment
4. Create graphics templates for common components

Troubleshooting

Alarm Console Shows "No Alarms" (but alarms exist)

1. Check alarm service binding path
2. Verify user has permission to view alarms
3. Check alarm class filter settings
4. Verify time range includes recent alarms

Alarm Console Shows Error

1. Open browser developer tools
2. Look for 404 errors (path not found)
3. Check Workbench fault viewer for binding errors
4. Verify service exists at expected path

Alarms Work on JACE, Not Supervisor

1. Confirm graphics are accessing correct station
2. Check if alarm service is proxied to Supervisor
3. Verify network routing is correct
4. Test with network alarm console instead