Lawo Ember+ Parameter Controllable Device

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: v1.3.0

Overview

hi connects to a Lawo^® or compatible Ember+ provider over persistent TCP. It traverses the published tree, subscribes to changes, and writes supported parameters. hi shows Ember+ functions, and it cannot invoke them.

Network Requirements

Connection Model: hi initiates a persistent TCP connection to the Ember+ provider.
Multicast / Unicast: Unicast only.
VLAN / IGMP: No multicast configuration is required.
Bandwidth: Control traffic only.
IP Version: IPv4.
Firewall: Allow outbound TCP from hi to the Ember+ provider, Port 9000 by default.

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: Inventory, Parameter Control, and Control Panel
Resources Controlled: Nodes and parameters published by the provider. Matrices need the Ember+ Compatible Router integration.
Device Administration: Use the provider's own tooling for engineering and firmware. Only controls and functions documented on this page are supported through hi.

Connection Details

Property	Value
Protocol	Ember+
Transport	TCP
Default Port	9000
Authentication	None - the Ember+ protocol does not define authentication access control must be managed at the network level
Encryption in Transit	None - Ember+ uses plaintext TCP no TLS defined
Connection Model	Persistent TCP
Required License	hiBase
Traffic Flow	Outbound connection with inbound responses and parameter updates

Required Configuration

Parameter	Description	Default
Host / IP Address	IP address or hostname of the Ember+ device	-
Port	Ember+ TCP Port	9000

Device-Side Setup

Follow Lawo Ember+ Parameter Controllable Device Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Feature	Access	Exposed Operation and Scope
Directory and Element Traversal	Read-only	Traverse the provider tree and read its parameter and Node elements. Matrices, functions, and other element types appear as placeholders.
Parameter Values	Per-parameter access	Read values and write only parameters whose Ember+ access metadata allows writing; parameters without write access are presented as read-only in hi.
Subscriptions	Write-only subscription management read-only updates	Subscribe to supported value changes, receive updates, and remove subscriptions. Updates report state; they do not make a parameter writable.

Device Coverage

Tested With identifies devices that have been tested with hi. Potentially Compatible (Not Yet Verified) identifies devices that use the same protocol or connection method but have not been tested with hi. Device-specific configuration, firmware, and feature support can affect results.

For device-specific workflows, use the dedicated integrations for Lawo Crystal Series, Sony MSU-3500, Sony RCP-3500, and Cyanview RCP. Those pages define the supported operations for each product.

Tested With

Arkona Technologies AT300 BLADE//runner
Lawo mc² Series
Lawo V__link4
Lawo V__pro8
Riedel MediorNet TDM
Solid State Logic System T S300

Potentially Compatible (Not Yet Verified)

Other Ember+ providers that expose a compatible parameter tree.

Use the dedicated references linked above for products with their own integration pages. A provider exposing Ember+ does not establish support for every parameter, function, or firmware version.

Known Limitations

Available controls depend on the tree published by the connected provider.
The Calrec Ember+ virtual GPIO provider, on TCP Port 62001 from MasterControl software v6.0, publishes its GPIO as matrices. This integration shows matrices as placeholders and cannot control them.
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.
When hi connects, it loads the top two levels of the provider tree. hi loads deeper levels when you open them in the Parameter Browser, and it subscribes to value updates of pinned parameters.
hi presents Boolean, Integer, Real, String, and Enum parameters. When a parameter carries an Ember+ factor, hi divides the value by the factor and shows a decimal value.
Ember+ matrices appear as placeholders with the message This is a Matrix. Please add an Ember+ compatible router from the Nodes screen to manage it.

What's Not Supported

Firmware updates, show-file editing, and DSP design.
Controls and functions that the connected provider does not publish in its Ember+ tree.
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.
Managing matrices. Use the Ember+ Compatible Router integration for matrices.
Ember+ Octets parameters. hi shows them with the message This parameter's data type can't currently be managed from hi.

Trademarks

Note

Lawo is a registered trademark of Lawo AG.

All product names, logos, and brands are property of their respective owners. Copyright in third-party software and materials remains with the respective owners. Use of these names does not imply endorsement.

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