Ereca Stage Racer

Driver Maturity

Production

Recommended for normal production use.

Caution

Compatibility Note: This information is a general guide and may be incomplete, may not match a specific project implementation, and is subject to change as supported products and versions evolve. Confirm the exact implementation and requirements for each project with Riedel and the relevant equipment vendor, then validate the required functions end to end in the target environment before deployment.

Minimum hi Version: v2.7.3

Overview

The Ereca Stage Racer^™ integration uses Ember+ to discover routing matrices, monitor Crosspoints, and execute route commands.

Network Requirements

Allow outbound TCP from hi to the Stage Racer Ember+ provider on Port 9000 by default.
The Ember+ Port is configurable and may differ from the template default.
No callback or inbound connection to hi is used.
Keep the plaintext control connection on a trusted management network.

Standards Conformance

Standard	Conformance	Notes
Ember+ (Lawo)	Glow DTD parameter tree per Ember+ spec	Open community specification used as a de facto standard widely adopted

Operator Workflow

UI Surface in hi: Routing Matrix, Inventory, and Parameter Control
Layers Controlled: Matrices and parameters published by the Ember+ provider
Routing Semantics: hi exposes the Sources, Destinations, and Crosspoints published in the device tree.
Notes for Operators Familiar with the Vendor's Own Tooling: hi exposes only the matrices and parameters published in the device's Ember+ tree.

Connection Details

Property	Value
Protocol	Ember+ (S101 framing Glow DTD)
Transport	TCP
Default Port	9000
Authentication	No credentials are configured in hi for the Ember+ connection
Encryption in Transit	Not provided by Ember+
Connection Model	Persistent TCP with asynchronous subscription-based updates
Required License	hiBase
Traffic Flow	Outbound from hi

Required Configuration

Parameter	Description	Default
Host / IP Address	IP address of the Ereca Stage Racer	-
Port	TCP port configured for Ember+ access on the device	9000
Reinitialize Router	Operations button that disconnects the routing control connection and restarts initialization available at runtime	-

Device-Side Setup

Follow Ereca Stage Racer Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Feature	Access	Exposed Operation and Scope
Provider Tree and Values	Read-only	Discover exposed nodes, Parameters, and matrices, and read their published values.
Parameter Values	Per-parameter access	Write only Parameters whose Ember+ access metadata permits writes.
Crosspoint State and Subscriptions	Read-only updates	Subscribe to and receive exposed Crosspoint and parameter-value changes.
Crosspoint Routing	Read/write	Change only Crosspoints exposed for control on the discovered matrices.

Device Coverage

Tested With identifies devices that have been tested with hi. Device-specific configuration, firmware, and feature support can affect results.

This integration supports the Ereca Stage Racer range.

Tested With

Ereca Stage Racer

Supported Product Range

Ereca Stage Racer 2

Known Limitations

The Ember+ tree structure varies between Stage Racer firmware versions. Ereca reimplemented the Ember+ interface in release 3.12 and changed the Ember+ IO numbering in release 3.13.1. Recheck Sources, Destinations, and Crosspoints in hi after a firmware update.
Firmware releases before 3.13.1 can deadlock when Ember+ and TSL run at the same time.
From firmware release 3.23, the Stage Racer 2 publishes IO configuration Parameters, such as name, direction, standard, framebuffer, and gains, under the io_config node of each machine in the Ember+ tree. A write to one of these Parameters from Parameter Control changes the IO configuration of the device.
From firmware release 4.5.2, the Stage Racer 2 does not report the state of a forced pseudo-GPI through Ember+.
Ereca limits each Stage Racer 2 node to 10 Ember+ client connections from firmware release 3.18.6, and to 3 connections in earlier releases. The node rejects further clients. Count every Ember+ consumer against this limit. Each hi Node opens one connection for routing and one for Parameter Control.
The Stage Racer 2 node drops an inactive Ember+ client connection.
Large matrix sizes may result in longer initial synchronization times during the GetDirectory walk.
hi limits its initial matrix-discovery directory walk. Deeply nested matrices can be missed, and hi offers no setting to select a specific matrix path. Confirm that the required matrices appear during commissioning.
Validate the discovered matrices and the writable parameters with the installed firmware during commissioning.
hi sends an Ember+ keep-alive request every 5 seconds, and it disconnects when the provider does not answer within 10 seconds. hi requires the provider to answer keep-alive requests.

What's Not Supported

Engineering-level configuration that the Stage Racer does not publish as writable Ember+ Parameters, such as redundancy setup. Use the Ereca web interface.
Firmware updates - use the vendor's native update utility.
Hardware diagnostics and SFP-level health - surfaced by the device's own management plane, not this integration.
Ember+ Functions, including Qualified Functions, and function invocation. The Ember+ specification defines them from Glow 2.20, and hi never sends an Invoke command.
Ember+ Templates, including Qualified Templates, and template references. The specification defines them from Glow 2.40. hi requests all fields of each element, and it does not resolve template references.

Trademarks

Note

Ereca and Stage Racer are trademarks of Ereca S.A.S.

RIEDEL Communications is not affiliated with, endorsed by, or officially partnered with Ereca unless explicitly stated.