hi human interface®
hi human interface®
English
Breadcrumbs

Riedel MediorNet TDM Integration Configuration

Riedel MediorNet TDM 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 MediorNet system in TDM routing mode connects to hi through its Ember+ provider. MediorNet publishes the video, audio, multichannel audio, data, and GPI signals as separate matrices, and hi lists them separately.

Configuration

What hi Sees

Use When

MediorNet TDM Routing

Up to five matrices, which are Video, Audio, Multichannel Audio, Data, and GPI, as the provider publishes them.

hi must route MediorNet TDM Sources and Destinations.

Caution

A Source or Destination without a third-party ID is not visible to hi. Leave the third-party IDs that Riedel reserves for connection states unassigned.

Before You Begin

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

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

  • Use MediorWorks to edit the MediorNet configuration.

  • Record the Ember+ provider address and Port.

  • Confirm the network access in Network Requirements. The default Ember+ port is 9000.

Configure MediorNet TDM Routing

Device Configuration

  1. Confirm that the MediorNet system is in TDM routing mode.

  2. In MediorWorks, open the 3rd Party Interfaces window and enable Ember+. Ember+ and Pro-Bel are separate third-party interfaces, and hi uses Ember+.

  3. Assign third-party IDs to the Sources and Destinations that hi must route. Assign the IDs separately in the video, audio, multichannel audio, data, and GPI matrices.

  4. Leave the IDs that Riedel reserves unassigned. The reserved IDs are 1002 through 1024; they signal connection states or are reserved for future use.

  5. If the 3rd Party Configuration includes a 3rd Party Master(s) area, select the primary and secondary master Frames there. Record the Config port addresses of the Frames that provide the Ember+ connection. For a system with master Frames, prefer their Config port addresses; the connection can also use the Config port of another Frame in the same net.

  6. Confirm the Ember+ Port. The default is 9000.

hi Configuration

  1. Add the Riedel MediorNet TDM integration in Inventory.

  2. Enter the recorded Config port addresses and the Ember+ Port. hi connects to whichever controller publishes the Ember+ tree. For a system with one controller, enter the same address in both entries.

  3. Create the Node.

  4. Wait for hi to discover the provider tree.

Settings Summary

Setting

Device Side

hi Side

Ember+ provider

Ember+ enabled in 3rd Party Interfaces

Address and Port
default 9000

Signals

Third-party IDs for each matrix

Sources
Destinations
and Crosspoints of each matrix

Common Checks

Symptom

Check

Discovery fails.

Confirm that Ember+ is enabled, that the provider runs, and that the Port is reachable.

A signal is missing.

Confirm that it has a third-party ID in the matrix of its signal type.

Verify the Configuration

Compare the discovered Ports and Crosspoints with MediorNet. Then test a route on a noncritical Destination.