hi human interface®
hi human interface®
English
Breadcrumbs

Ereca Stage Racer Integration Configuration

Ereca Stage Racer Integration Configuration

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.

Configuration Overview

The Stage Racer integration has one configuration. hi discovers the matrices in the Ember+ tree of the device, so only the address and the Port must match.

Configuration

What hi Sees

Use When

Stage Racer Ember+

The matrices found by hi's initial discovery and the Parameters available when you browse the device tree in Parameter Control.

hi must route or monitor a Stage Racer.

Before You Begin

  • Use Node admin and open Inventory > Nodes. See Manage Nodes.

  • Confirm the license and minimum hi version in Required Configuration.

  • Obtain the Ember+ address and Port of the Stage Racer from the device commissioning record or from Ereca.

  • Confirm the network access in Network Requirements.

  • Ember+ has no authentication. Anyone who can reach the Port can route. Keep the device on a routing-control network.

Configure Stage Racer Ember+

Device Configuration

  1. Read the device IP address on the front panel with the navigation buttons next to the LCD INFO screen, and open the web interface through the dedicated admin Ethernet port. Ereca recommends Firefox for the web interface.

  2. Confirm that the device runs firmware release 3.12 or later. Ereca reimplemented the Ember+ interface in release 3.12 and changed the Ember+ IO numbering in release 3.13.1.

  3. Confirm with Ereca how to enable the Ember+ provider and which TCP Port it uses. Ember+ is the third-party control path for the Stage Racer 2.

  4. Confirm that the hi server can reach the Ember+ Port of the device.

hi Configuration

  1. Add the Stage Racer integration (manufacturer Ereca) in Inventory.

  2. Enter the Ember+ address of the device. The template default Port is 9000. Enter the Port that the device uses when it differs.

  3. Create the Node. No additional matrix-selection settings are required when creating this Node. hi discovers the published matrices and creates their Sources and Destinations. Confirm that the required matrices appear; initial matrix discovery uses a limited directory walk.

  4. After the Node is created, the Operations group shows Reinitialize Router, Reinitialize Parameters, and Clear Parameter Cache. Reinitialize Router disconnects the routing control connection and restarts initialization.

Settings Summary

Setting

Device Side

hi Side

Address

Ember+ provider address

Device address

Port

Ember+ provider Port

Port
default 9000

Common Checks

Symptom

Check

The Node does not connect, or it disconnects every few seconds.

Confirm the Port, and confirm that the provider answers Ember+ keep-alive requests. hi disconnects when no answer arrives within 10 seconds.

Discovery does not start.

Confirm that the Ember+ provider is enabled on the Stage Racer, then check the network path from the hi server to the device.

No matrix appears.

Confirm that the device publishes the required matrix and that hi discovers it after Reinitialize Router. Deeply nested matrices can be missed.

Sources or Destinations are out of date after a device change.

Select Reinitialize Router in the Operations group.

Verify the Configuration

Wait for hi to discover the Ember+ provider tree. Compare the discovered Sources, Destinations, and several Crosspoints with the Stage Racer. Route a noncritical Destination from hi and confirm the change on the device. Then change a Crosspoint on the device and confirm that hi shows it without a restart, because hi subscribes to Crosspoint changes.