Grass Valley NVision NP0016 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

The choice depends on whether the router controller sends asynchronous Crosspoint change announcements.

Configuration	What hi Sees	Use When
Change Announcements	The level 1 matrix, with Crosspoint changes reported by the controller.	The controller supports asynchronous status registration.
Crosspoint Polling	The level 1 matrix, with Crosspoint changes found by polling the Destination status.	The controller is a legacy router, such as the NV8288, that does not send change announcements.

Before You Begin

Use Node admin and open Inventory > Nodes. See Manage Nodes.
Confirm the license and minimum hi version in Required Configuration.
Record the address of each router controller, and confirm which partitions and levels the controller reports.
Confirm the network access in Network Requirements.
NP0016 has no authentication. Anyone who can reach the Port can route. Keep the controllers on a routing-control network.

Configure Change Announcements

Device Configuration

Confirm that the controller is an EM0833 controller card with software release 3.5 or later. The EM0833 supports asynchronous status registration from that release. For other controller cards, follow Configure Crosspoint Polling.
Confirm that the routing that hi must control is on level 1.
Confirm that the hi server can reach each controller on TCP Port 5194. The control card listens on that Port on each of its IP interfaces and accepts several clients at the same time.

hi Configuration

Add the NVision NP0016 Compatible Router integration (manufacturer Grass Valley) in Inventory.
Enter the address of the primary controller. The template default Port is 5194.
For a controller pair, enter the address of the secondary controller.
Keep Enable polling for crosspoints at No in the Options group.
Create the Node. hi reads the level 1 partition, creates the Sources and Destinations, and registers for Crosspoint changes on that level.
When an operator disconnect must route a specific Source, open the Node and enter that Source number in Video disconnect in the Options group. This setting is available only after the Node is created.

Configure Crosspoint Polling

Device Configuration

Confirm that the routing that hi must control is on level 1.
Confirm that the hi server can reach each controller on TCP Port 5194.

hi Configuration

Complete steps 1 to 3 of the change announcements configuration.
Set Enable polling for crosspoints to Yes in the Options group. hi shows this setting at creation and after the Node is created.
Create the Node. hi reads the level 1 partition and then polls the Destination status instead of registering for changes.

Settings Summary

Setting	Device Side	hi Side
Address	Address of each router controller	Primary and secondary controller addresses
Port	NP0016 TCP Port `5194`	Port default `5194`
Change detection	Asynchronous status registration support of the controller and release	Enable polling for crosspoints default `No`
Level	Level 1 partition	Read from the controller

Common Checks

Symptom	Check
The Node connects but does not initialize on a controller pair.	hi found no active controller and retries after 30 seconds. Select Set Primary Active or Set Secondary Active in the Operations group for a connected controller.
Routes from other panels do not appear in hi.	Confirm that the controller supports asynchronous status registration. If it does not, set Enable polling for crosspoints to `Yes`.
A level is missing.	hi uses only the level 1 partition that the controller reports.

Verify the Configuration

Wait for the partition information and the Destination status to synchronize. Compare the Sources, the Destinations, and several Crosspoints with the router control system. If synchronization fails, verify the active controller, the partition availability, the Port, and the network path to each controller. hi opens the connection, and the controllers make no connection to hi. Route a noncritical Destination from hi and confirm the change on the router. Then change a Crosspoint from a router panel and confirm that hi shows it without a restart.