Grass Valley NV9000-SE v.5.0 - Manual (Page 82)

64
Routers
NVISION Profiles
The way it works is that when the NV9000 software receives an 0x00003001 command through
NVEP and “sees” that it is about to perform a switch on the profile’s level, it instead performs the
switch on all the levels of the (destination) device.
We presume there is no ambiguity involved — that the profile’s output port specified in the
take command belongs to one and only one NV9000 device. If not, the NV9000 will probably
use the first device it detects that includes that profile port.
Creating a “Profile”
Follow these guidelines. (The order of the steps is not critical. For instance, you can perform step
2 at any time. If you are starting with an NV9000 configuration that already has devices defined,
you can modify the existing devices easily.)
1 Define a virtual router that has type ‘NVISION Profile’. It must have one physical level.
Give this level a matrix large enough to accommodate all the devices you want to switch
using the external system.
2 Define a set of actual routers (with physical levels as needed).
3 Create a virtual level that represents the physical level of the “profile.” Use the ‘Virtual Levels’
table to do so.
4 Define a set of input and output devices that use one or more virtual levels corresponding to
actual routers and that also include the virtual level (and port numbers) of the “profile.”
The external system will issue “3000” or “3001” take commands, specifying the input port,
output port, and the physical level of the “profile.” (The external system must of course, know
the applicable port numbers and physical level ID.)
Example
This example uses a very simplified router configuration.
1 Define routers:
2 (Using the ‘Virtual Levels’ table, define a virtual level for the physical level of the profile:
The profile must use virtual router
protocol and be of type ‘NVISION
Profile’.
It must have enough ports to cover the
devices you want to switch externally.