hi human interface®
hi human interface®
English
Breadcrumbs

Riedel MediorNet TDM

Riedel MediorNet TDM

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.1.0

Overview

The Riedel® MediorNet® TDM integration uses Ember+ to discover routing matrices, subscribe to Crosspoint state, and set routes.

Network Requirements

  • Allow outbound TCP from hi to each MediorNet Ember+ provider on Port 9000 by 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 MediorNet Ember+ providers

  • Routing Semantics: hi exposes the Sources, Destinations, and Crosspoints published in the selected matrix.

  • Notes for Operators Familiar with the Vendor's Own Tooling: Use vendor tooling for engineering setup and firmware management. Use hi for the matrices and Crosspoints exposed by Ember+.

Connection Details

Property

Value

Protocol

Ember+

Transport

TCP

Default Port

9000

Authentication

No credentials are configured in hi for this Ember+ connection

Encryption in Transit

Not provided by Ember+

Connection Model

Persistent TCP with asynchronous updates

Required License

hiBase

Traffic Flow

Outbound from hi

Required Configuration

Parameter

Description

Default

Host / IP Address

IP addresses of the primary and secondary MediorNet system controllers. For one controller, enter the same address in both entries.

-

Ember+ Port

TCP port for Ember+ communication

9000

Device-Side Setup

Follow Riedel MediorNet TDM Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Feature

Access

Exposed Operation and Scope

Ember+ Matrix Discovery

Read-only

Discover matrices exposed by the provider tree.

Ember+ Crosspoints

Read/write

Subscribe to exposed state and set supported Crosspoints.

Ember+ Parameters

Read/write

Control the Parameters that the provider publishes.

Device Coverage

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

This integration supports the Riedel MediorNet TDM range.

Tested With

  • Riedel MediorNet MicroN UHD

  • Riedel MediorNet TDM

Supported Product Range

The following MediorNet devices run in TDM routing mode and publish the Ember+ matrix layout through MediorWorks:

  • Riedel MediorNet Compact

  • Riedel MediorNet Compact Pro

  • Riedel MediorNet Modular

  • Riedel MediorNet MicroN

  • Riedel MediorNet MetroN

  • Riedel MediorNet HorizoN

Potentially Compatible (Not Yet Verified)

  • MediorNet TDM systems on MediorWorks releases or device configurations that have not been tested, where the Ember+ provider exposes the supported matrix layout.

Known Limitations

  • Large matrices and parameter trees can increase initial synchronization time.

  • This page covers TDM mode. Use the MediorNet IP FusioN / MuoN integration for IP workflows.

  • Configure third-party IDs and tags in MediorWorks, not in hi, and do it before you synchronize.

  • Riedel reserves MediorWorks third-party IDs 1002 through 1024 for connection states or future use. Do not assign these IDs to ordinary Sources. The corresponding protocol-layer IDs are shown separately in the MediorNet third-party interface documentation.

  • MediorWorks manages the NMOS registry connection, SNMP, and the Pro-Bel and TSL interfaces. These are separate from this Ember+ integration.

  • Validate the exposed Ember+ tree on the installed MediorNet 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 (level naming, port labels, redundancy setup) - use the vendor's native router-control tool.

  • 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

Riedel and MediorNet are trademarks of Riedel Communications GmbH & Co. KG.