hi human interface®
English

Grass Valley Sirius / Vega Series Integration Configuration

Grass Valley Sirius / Vega Series 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 Sirius or Vega system exposes two control surfaces to hi. SW-P-08 carries routing. RollCall carries Parameters. Configure routing first, then add RollCall when Parameter Control is needed.

Configuration

What hi Sees

Use When

SW-P-08 Routing

Sources, Destinations, labels, and Crosspoints of one matrix and level.

hi must route the router.

RollCall Parameter Control

Parameters that the router exposes through RollCall, in addition to routing.

Parameters must be read, monitored, or written from hi.

Before You Begin

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

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

  • Use the Grass Valley router configuration tool to read the levels, matrices, and counts.

  • Record the address of each controller for the SW-P-08 and RollCall connections.

  • Confirm the network access in Network Requirements. The default ports are 2008 for SW-P-08 and 2050 for RollCall.

Configure SW-P-08 Routing

Device Configuration

  1. Enable SW-P-08 routing control on the Sirius or Vega controller. On a Sirius 800, SW-P-08 over IP (SW-P-08 IN) requires a Nucleus2 2464 or 2463 controller.

    • On a Vega 30, open Configuration in the web interface, select Enable under SW-P-08, keep the default Port 2008, and select Apply.

  2. Confirm that the SW-P-08 Port is reachable from the hi server.

  3. Record the level index, the matrix index, the number of Sources, and the number of Destinations.

hi Configuration

  1. Add the Grass Valley Sirius / Vega Series integration in Inventory.

  2. Enter the address of the primary controller in the first SW-P-08 connection. Enter the address of the secondary controller in the second connection, or clear the second host for a system with one controller. Enter the SW-P-08 Port.

  3. Select the Signal Type, and enter Level and Matrix as recorded. hi numbers Level and Matrix from 0. If the router configuration tool numbers them from 1, subtract 1.

  4. Enter Input Count and Output Count.

  5. Create the Node.

Configure RollCall Parameter Control

Device Configuration

  1. Enable RollCall on the Sirius or Vega controller.

    • On a Sirius 800 Nucleus2 controller, RollCall is enabled by default. In the Workbench Online Editor, open ConfigurationItems > RollCall and confirm that Enabled is True. When two controllers are fitted, enable RollCall on both. Reset the controller to apply a change.

    • On a Vega controller, open the Comms Setup page in the RollCall Control Panel and note the RollCall IP Share Port. Select Restart Unit to apply a change.

  2. Confirm that the RollCall Port is reachable from the hi server.

hi Configuration

  1. Open the Node that you created for routing.

  2. Enter the controller address and the recorded RollCall Port. The default Port is 2050.

  3. Wait for hi to discover the exposed Parameters.

Settings Summary

Setting

Device Side

hi Side

Routing control

SW-P-08 enabled
default Port 2008

SW-P-08 Port

Parameter Control

RollCall enabled
default Port 2050

RollCall connection

Level and matrix

Level and matrix indexes

Level and Matrix
numbered from 0

Common Checks

Symptom

Check

Routing works and Parameters are missing.

Confirm that RollCall is enabled and that Port 2050 is reachable.

Parameters work and routing is missing.

Confirm that SW-P-08 is enabled and that Port 2008 is reachable.

Names are missing or out of date.

Select Refresh Labels in the Operations group after you change names on the router. To read names at every connection, set Read labels on startup to Yes.

Verify the Configuration

Wait for synchronization to finish. Compare labels and Crosspoints with the router and test a noncritical route. When RollCall is enabled, read and write one noncritical Parameter.