hi human interface®
hi human interface®
English
Breadcrumbs

Imagine Communications LRC Compatible Router Integration Configuration

Imagine Communications LRC Compatible Router 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

An Imagine router controller that serves LRC connects to hi as one router Node. hi reads the Source and Destination counts, the names, the channels, and the Crosspoints from the logical database of the router. Use LRC Plus wherever possible, and use this integration where LRC Plus does not perform as expected with a device.

Configuration

What hi Sees

Use When

LRC Router

One matrix of logical Sources and Destinations, with their names and Crosspoints.

The controller serves LRC and LRC Plus does not perform as expected with the device.

Before You Begin

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

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

  • Confirm the network access in Network Requirements.

  • Record the LRC controller address and Port.

  • Use RouterMAPPER or the Magellan CCS Navigator to read the logical database and the LRC server settings.

  • LRC has no authentication. Anyone who can reach the Port can route. Keep the controller on a routing-control network.

Configure LRC Router

Device Configuration

  1. Confirm that the controller supports the LRC socket interface. Availability depends on the device. See the device documentation for how to enable it.

  2. On a Platinum frame with PT-RES firmware 4.2 or later and a factory configuration, the LRC protocol is enabled by default. On an upgraded frame, select LRC Protocol on the Protocols tab of the protocol settings.

  3. On the Servers tab, add a server of type LRC TCP Server, confirm that it is enabled, and check the client limit and the LRC port. The LRC/TCP listener uses Port 52116. Confirm that this Port is reachable from hi.

  4. Send the new configuration to the frame.

  5. Confirm that the logical database defines the Sources, Destinations, and channels (levels) that hi must use. LRC addresses the names and IDs of this logical database, so an incomplete database gives incomplete names and status.

hi Configuration

  1. Add the LRC Compatible Router integration (manufacturer Imagine Communications) in Inventory.

  2. Enter the controller address and the Port. hi defaults to 52116.

  3. Select Signal Type. The choices are Audio and Video, and the default is Video.

  4. Enter Input Count and Output Count from the router configuration software. The defaults are 16 and 16. Signal Type, Input Count, and Output Count are available only when you create the Node.

  5. Create the Node. hi connects and shows Synchronizing with router while it reads the counts, the names, the channels, and the Crosspoints. hi adds a port for each reported Source or Destination that has no port with the same number.

Settings Summary

Setting

Device Side

hi Side

Control Port

LRC TCP Server
Port 52116

Port
default 52116

Matrix size

Logical Sources and Destinations in the logical database

Input Count and Output Count
default 16

Signal format

Channel names in the logical database

Port format from the channel name
and Signal Type at creation

Common Checks

Symptom

Check

The Node does not connect.

Confirm that the LRC TCP Server is enabled, that its client limit is not reached, and that Port 52116 is reachable from hi.

Names or Sources are missing.

Confirm that the logical database defines the Sources, Destinations, and channels, and that the configuration was sent to the frame.

A Crosspoint that the router shows does not appear in hi.

Confirm that the channel names of the Source and the Destination give the same format.

The Node synchronizes again without an operator action.

The router reported a change to its logical database. hi reloads the names and the Crosspoints.

Verify the Configuration

Compare the Source names, the Destination names, and several Crosspoints with the controller. Route a noncritical Destination from hi, and confirm that the change returns to hi. Then change a Crosspoint from a router panel, and confirm that hi shows it without a restart.