Lawo Crystal Series Audio Console 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

A crystal console connects to hi as one Node through its Ember+ provider. The Node has two capabilities on the same address and Port: Crosspoint Management for the matrices that the console publishes, and Parameter Control for its Ember+ tree. hi finds the matrices automatically, so the published Ember+ tree decides what hi can route.

Configuration	What hi Sees	Use When
crystal Routing and Parameters	The matrices in the top three levels of the Ember+ tree as Sources, Destinations, and Crosspoints, and the parameters that you pin on the Node.	hi must route crystal signals or monitor and change crystal parameters.

Caution

A matrix deeper than the top three levels of the Ember+ tree does not appear in hi.

Before You Begin

Use Node admin and open Inventory > Nodes. See Manage Nodes.
Confirm the license and minimum hi version in Required Configuration.
Define an Ember+ provider on the crystal console and record its Local Port Number. The provider Port is set in the Lawo configuration, so it can differ from the hi default.
Confirm the network access in Network Requirements.

Configure Crystal Routing and Parameters

Device Configuration

In the Lawo configuration tool, open System > Definition in the Tree Definition window, select the Ember+ tab, and define a provider under Local Providers with a Local Port Number.
Select Enable Subscript Reports for that provider so that it announces value changes to hi.
Set Internal Matrix to the provider number to publish the console matrix. Set Ember+ Local Provider Nr on each Source element whose parameters hi controls.
If a Power Core Providers Client Whitelist is active, add the address of the hi server.
Record the address of the console ETHERNET port and the provider Port. Ensure that the hi server can reach the provider.

hi Configuration

Add the crystal Series Audio Console integration (manufacturer Lawo) in Inventory.
Enter the console address and the provider Port for the Crosspoint Management capability and for the Parameter Control capability. hi defaults both to 9000.
Create the Node and wait for hi to read the matrices.
Browse the parameter tree of the Node and pin the parameters that your workflow needs. See Parameter Control Nodes.
After the Node is created, use Reinitialize Router in the Operations group when hi must read the matrices again.

Settings Summary

Setting	Device Side	hi Side
Control Port	Ember+ provider Port	Port of both capabilities default `9000`

Common Checks

Symptom	Check
The Node does not connect.	Confirm that the Ember+ provider is enabled, that its Port is reachable, and that it answers keep-alive requests within 10 seconds.
A matrix is missing in hi.	Confirm that the matrix is in the top three levels of the Ember+ tree.
A parameter value does not update in hi.	Confirm that the parameter is pinned on the Node.

Verify the Configuration

Confirm that the expected matrix, parameters, and labels appear in hi. Route a noncritical Destination from hi and confirm that the Crosspoint returns to hi. Change a pinned, noncritical parameter from hi and from the console, and confirm that each new value appears on the other side.