GRASS VALLEY RCP-200 User manual

Router Manager User Guide
Version 1.90
M876-2000-104
18 June 2015

ii
i
Copyright and Trademark Notice
Copyright © 2015, Grass Valley USA, LLC. All rights reserved.
Belden, Belden Sending All The Right Signals, and the Belden logo are trademarks or regis-
tered trademarks of Belden Inc. or its affiliated companies in the United States and other juris-
dictions. Grass Valley, Miranda, iControl, Kaleido-X, NVision, and Densité are trademarks or
registered trademarks of Grass Valley USA, LLC. Belden Inc., Grass Valley USA, LLC, and other
parties may also have trademark rights in other terms used herein.
ATTENTION: Please read the following terms and conditions carefully. By using RCP-200 docu-
mentation, you agree to the following terms and conditions:
Grass Valley, a Belden brand hereby grants permission and license to owners of the RCP-200 to
use their product manuals for their own internal business use. Manuals for Grass Valley prod-
ucts may not be reproduced or transmitted in any form or by any means, electronic or
mechanical, including photocopying and recording, for any purpose unless specifically autho-
rized in writing by Grass Valley.
A Grass Valley manual may have been revised to reflect changes made to the product during
its manufacturing life. Thus, different versions of a manual may exist for any given product.
Care should be taken to ensure that one obtains the proper manual version for a specific prod-
uct serial number.
Information in this document is subject to change without notice and does not represent a
commitment on the part of Grass Valley.
Warranty Policies
Warranty information is available in the Support section of the Grass Valley Web site
(www.grassvalley.com).
Title RCP-200 Version 1.90 Router Manager User Guide
Part Number M876-2000-104
Revision Date 18 June 2015 3:19 pm

Table of Contents
iii
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
Communications with Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
User Interfaces Available with RCP-200 Router Manager Software . . . . . . . . . . . . . . . . . . .2
Configuration Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Operating Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2 Configuration Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
System Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Detailed Directions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Configuring Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Configuring Routers Dynamically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3 Routing Switchers Tips and Tricks . . . . . . . . . . . . . . . . . . . . . . 35
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Nevion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Network Compact Protocol (Default Driver for VikinX Compact Routers) . . . . . . . 36
Network Modular Protocol (Control Protocol for VikinX Modular Routers) . . . . . . 36
Leitch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
How to get Firmware Version Number? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Utah Scientific RCP-3 (SC-4 Controller Ethernet Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Utah Scientific RCP-1 (SC-3 Controller) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Utah Scientific AVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Philips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Digipath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Thomson / Grass Valley GVG Series 7000 Native Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Lightwave Matrix-Hub 1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Snell (Pro-Bel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
SW-P-08 (General Remote Control Protocol) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
SW-P-02 (General Switcher Communication Protocol) . . . . . . . . . . . . . . . . . . . . . . . . . 46

iv
toc
NVISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
NVISION Ethernet Protocol - Enterprise Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
NVISION Ethernet Protocol - Enterprise Router (Logical) . . . . . . . . . . . . . . . . . . . . . . . 52
NVISION Ethernet Protocol - Compact Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
NVISION Serial Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Pesa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
CPU Link Protocol No.1 or P1 (Pesa) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Unsolicited Status Protocol (Pesa USP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Sony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Quintech . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Quick Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Detailed Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Contact Us. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Introduction
The RCP-200 Router Manager Software allows you to create a virtual routing environment
where physical router resources can be arranged into one or more logical configurations that
are optimized for operational needs. This document shows you how to configure and operate
router configurations using RCP-200.
Summary
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Communications with Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
User Interfaces Available with RCP-200 Router Manager Software . . . . . . . . . . . . . . . . . . . . . 2
Overview
The RCP-200 Router Manager Software allows you to create a virtual routing environment
where actual physical router resources are deployed and controlled by software into a
customized configuration optimized for your operational needs. Large routers can be
operated as if they were multiple smaller routers. For example, a 64 × 64 router can be
operated as if it were three separate smaller routers: for instance, a 64 × 15 router, a 12 × 5
router and a 32 × 44 router. Control and monitoring are handled by software, and are readily
changed. Each operator benefits by seeing only the resources actually being used. This
software can also be used as a bridge interface between a Kaleido or iControl Web system and
a routing device. In this configuration, it will be used to update UMD text, and for router
control functions initiated from the Kaleido or iControl Web user interface. The software
includes the following features:
• bridge interface via TCP-IP for Kaleido and iControl Web software
• distributed architecture
• highly configurable
• multiple number of levels
• support for logical routers
• support for a mix of different frame types from different manufacturers
Communications with Routers
The host computer and the routing devices you wish to control must be interconnected by a
serial or Ethernet cable. Most of the supported routers are serial (RS-422) devices. Some newer
devices may support TCP\IP connection.

Introduction
User Interfaces Available with RCP-200 Router Manager Software
2
Install the appropriate connection, either by using dedicated cabling or through an existing
network.
User Interfaces Available with RCP-200 Router Manager Software
RCP-200 Router Manager software includes two types of interfaces:
• a configuration interface
•operatinginterfaces
Configuration Interface
The configuration interface, called Router Manager Configurator, is used for router setup and
configuration. Use this application to define physical and logical routers.
Operating Interface
The operating interface used to monitor and control the logical routers is on the RCP-200
device.
See also
For more information, see "Routing Switchers Tips and Tricks" on page 35.
Term Description
Physical Router A physical router represents the connection to your existing router (RS-422 or TCP). Configure one
physical router for each device you wish to control from the RCP-200 Router Manager software.
Logical Router A logical router represents an entire physical router, or a subset of a physical router. The operating
interfaces handle logical routers.
For instance, if you configured one 16 × 16 physical router, you can create two 8 × 8 logical routers
with levels 0 and 1.
See also
For more information, see "Configuration Interface" on page 3.

Configuration Interface
The process of creating and configuring a third-party router or router control panel consists of
four steps:
1. Defining a physical router
2. Adding one or more physical levels
3. Adding one or more logical routers
4. Adding one or more logical levels
Summary
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Configuring Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Configuring Routers Dynamically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Overview
The Router Manager Configurator interface has two panes. The left pane always displays a
hierarchical list of folders which can be expanded to expose more detailed information.
The Router Manager folder is always at the top level in the list, and typically includes the
Physical routers and the Logical routers subfolders. The subfolder structure is variable and is
established during the system setup. There are two tabs at the top of the left pane:
Configuration and Dynamic Control.
•UsetheConfiguration tab to set up and configure your system, after which the router
service and clients must be restarted for changes to become effective.
•UsetheDynamic Control tab to perform any of a subset of live configuration changes,
after which no restart is required.
In either tab, click a folder or a list item to select it; double-click a folder to open it. Both tabs
also have a tool bar with buttons to open and close the router manager folder, at the top of the
list (not the currently selected folder). The Close button is available when the router manager
folder is open; conversely, the Open button is available when the router manager folder is
closed. The Configuration tab also has a Save button which becomes available whenever you
make some change to the system configuration.
The right pane displays data-entry zones and information areas associated with the current
left-pane selection. When a logical router is selected in the left pane, the right pane has
additional tabs.

Configuration Interface
System Recommendations
4
System Recommendations
Grass Valley recommends the following hardware specifications for optimal performance:
Grass Valley requires that the following software is installed on your client PC:
Detailed Directions
The procedures outlined in the following sample workflow are tasks performed exclusively on
the Configuration tab:
Recommended hardware specifications for optimal performance
Memory Processor Operating System
2 GB RAM Intel Core i3 or better Windows 7 or Windows 8
Minimum software requirement
Java 2 Runtime Environment (JRE) version 1.5 or later.
Sample workflow: Configuring routers
1. Open Router Manager Configurator (see page 5).
2. Define all of your physical routers. Do one of the following, as required:
•"Adding Physical Routers" on page 6
•"Importing an NVISION Physical Router Configuration" on page 9
3. [OPTIONAL] Assign aliases to physical input and destination port (see "Adding Aliases for your
Physical Input Ports", on page 16).
4. [OPTIONAL] Remove any physical routers that you would like to remove (see page 22).
5. [OPTIONAL] Modify any pre-existing physical router configurations, if required (see page 19).
6. Define levels for your physical router definitions (see "Adding Physical Router Levels", on page 13).
7. [OPTIONAL] Modify or remove any pre-existing physical router level definitions, if required
(see "Modifying Physical Router Configurations", on page 19).
8. Define all of your logical routers (see "Configuring Logical Routers", on page 22).
9. [OPTIONAL] Remove any logical routers that you would like to remove (see "Configuring Logical
Routers", on page 22).
10. Define levels for your logical routers (see "Configuring Logical Routers", on page 22).
11. [OPTIONAL] Modify any pre-existing logical routers and their levels, if required (see "Configuring
Logical Routers", on page 22).
12. [OPTIONAL] Remove any logical router levels, if required (see "Configuring Logical Routers",
on page 22).

RCP-200
Router Manager User Guide
5
Configuring Routers
Opening Router Manager Configurator
To open Router Manager Configurator
• On the Main RCP-200 Web page, click iC Router Control.
Router Manager Configurator appears.

Configuration Interface
Adding Physical Routers
6
Adding Physical Routers
To add a physical router
1. In Router Manager Configurator, on the Configuration tab, select the router manager
folder (named RouterManager in the graphic, below), and then click Open.
2. Select the Physical Routers folder.
A list of all physical routers added so far to your system appears in the right pane.
3. Click Add Router.
A new Router N folder appears in the Physical Routers folder on the left, and detailed
data-entry areas appear in the right pane.
Note: Although it is possible to perform the following procedure as a stand-alone
task (assuming all stated requirements are met), Grass Valley recommends you
familiarize yourself with the sample workflow (see page 4) in which this procedure is
only one step within a sequence.
REQUIREMENT
Before beginning this procedure, make sure you have opened Router Manager Configurator
(see page 5).

RCP-200
Router Manager User Guide
7
4. In the Router name box, type a name for the router.
5. In the Router protocol list, select a protocol.
6. Click Help to review information about the selected protocol.
7. Under Connection type, select Serial, TCP/IP, or UDP, as appropriate for the selected
protocol.
IMPORTANT: Naming Restrictions
Do not use special characters in the router name. Spaces are allowed.
Note: Presently, there are several protocols for which online help is unavailable.

Configuration Interface
Adding Physical Routers
8
The Communication parameters zone varies according to the selected connection type,
as follows:
Figure 2-1: Communications settings for a serial connection
Figure 2-2: Communications settings for a TCP/IP connection
Figure 2-3: Communications settings for a UDP/IP connection
8. In the Communications parameters area, specify all required information, or click Use
protocol defaults to apply the selected protocol’s default communication settings.
9. Click Save at the top of the left pane.

RCP-200
Router Manager User Guide
9
Importing an NVISION Physical Router Configuration
To import an NVISION configuration
1. Select the RouterManager folder, and then click Open.
2. Select the Physical routers folder.
The list of all physical routers added so far to your system appears in the right pane.
3. Click Import NVISION config.
Notes
• The collection of protocol-specific information, that you can read by clicking
Help for each protocol, can also be found at the end of this manual
(see "Routing Switchers Tips and Tricks", on page 35).
• The RS-232 baud rates for Network routers differ from model to model.
Although the standard value is 19200, you should refer to your router’s user
manual to verify the appropriate value for your specific model.
IMPORTANT: Risk of Deleting Router Configuration Data
If, after adding aliases, you are importing router configuration data in which
there is a physical router with the same name as one of your own in Router
Manager, the alias data you configured for that router will be overwritten.
REQUIREMENTS
Make sure you meet the following conditions before beginning this procedure:
• You have available the host name or IP address of the NVISION router controller whose
configuration you would like to import.
• You have opened Router Manager Configurator (see page 5).

Configuration Interface
Importing an NVISION Physical Router Configuration
10
The Import Configuration window appears.
4. In the Host name / IP address box, type the host name or IP address of the NVISION router
controller whose configuration you would like to import.
5. Click Fetch preview.
The levels of the NVISION router appear listed in the Import preview area.

RCP-200
Router Manager User Guide
11
6. Select the levels you would like to import, and then click OK.
A confirmation window appears.
A progress window appears, allowing you to cancel the operation if required.
IMPORTANT: Risk of losing current router configuration data
If you click OK in the confirmation window and then click Save in Router
Manager Configurator, the imported NVISION data will permanently
overwrite any existing configuration data.

Configuration Interface
Importing an NVISION Physical Router Configuration
12
7. After the confirmation window disappears, click Save to overwrite your configuration data
with the newly imported data.
8. Refresh your browser.
The NVISION router controller’s level configurations are listed among the physical routers in
the left and right panes of the Router Manager Configurator.
Selecting the physical router in the left pane yields general information, communication
parameters, and a list of levels imported from the router.

RCP-200
Router Manager User Guide
13
Adding Physical Router Levels
The physical levels from which the router is going to be built must be defined. Typical levels
include video, audio 1, audio 2, etc. These levels each represent a physical device. Each level
must be named, and its type and size specified.
To add a level to a physical router
1. In Router Manager Configurator, in the left pane, select the physical router you wish to
configure.
The list of existing levels appears under Levels.
IMPORTANT: Using Telecom and Data Routers
• Network series RS-422 Data routers have to be configured as an audio level.
Select an appropriate audio frame type. For example, if you have an 8 × 8
RS-422 router, you should select Network Audio 8 × 8 frame type.
• Network series Telecom routers are configured to work as a video level so you
can use an appropriate video frame. For example, if you have an 8 × 8
Telecom frame then you should select Network Video 8 × 8 frame type.
Note: Although it is possible to perform the following procedure as a stand-alone
task (assuming all stated requirements are met), Grass Valley recommends you
familiarize yourself with the sample workflow (see page 4) in which this procedure is
only one step within a sequence.
REQUIREMENT
Before beginning this procedure, make sure you have opened Router Manager Configurator
(see page 5).

Configuration Interface
Adding Physical Router Levels
14
2. Click Add level.
The Physical Level Configuration window appears. Its content varies according to the
selected router protocol:
Figure 2-4: Physical Level Configuration window (for most protocols)
Figure 2-5: Physical Level Configuration window (for a Snell SW-P-08 device)

RCP-200
Router Manager User Guide
15
Figure 2-6: Physical Level Configuration window (for a Redundancy Control device)
3. In the Level name box, type a name for this level.
4. Click Edit.
The Edit Level Size window appears.
5. Specify the number of sources and destinations associated with the physical level.
6. In the case of a Snell SW-P-08 device, type the appropriate value in the Matrix ID box (click
Help for more information).
7. In the case of a Redundancy Control device, select the appropriate main level and backup
level from the lists (click Help for more information).
8. Click OK to close the Edit Level Size window.
9. Click OK to close the Physical Level Configuration window.
At this point, you have added a level to a physical router, which appears in the Levels list
under the Configurations tab.
Note: The three option buttons labeled Video, Audio and Other are used for
Network Electronics routers only, for which levels must be classified as either Video or
Audio. These settings are ignored by routers from other manufacturers.

Configuration Interface
Adding Aliases for your Physical Input Ports
16
Figure 2-7: Newly added physical router level
The Frame ID in the physical level configuration is the frame address that is set by the
DIP switches on the router frame. The Physical Level ID is the internal identifier of the frame
and should be unique within each physical router. If it's not unique, then you will get an
error message when you try to save the changes. The Matrix ID is an optional entry for a
Probel router.
The Physical Router definition is now complete.
Adding Aliases for your Physical Input Ports
Aliases are names assigned to input and destination ports. Aliases are useful when trying to
remember specific ports on different routers or devices, or on different physical levels, that
have identical port numbers. For example, input port 1 on Router 1 can be assigned the alias
router1on1 and input port 1 on Router 2 can be assigned the alias router2on1 so that each port
can be easily distinquished.
Notes
• If you have several 16 × 2 frames configured to work together then you have
to add only one frame and select an appropriate frame type on the Edit
Physical Level window. For example, if you have three 16 × 2 video frames
configured to make a 48 × 2 router then you should select a Network Video
48 × 2 frame type.
• When the tab is opened, data boxes will appear in which the name, Frame
Type, Frame ID and Physical Level ID can be entered, and two charts (tab-
accessed) will appear below in which the Sources and Destinations can be
identified and labeled.. These should conform to the actual physical
connections made to the router being controlled.
IMPORTANT: Risk of Deleting Router Configuration Data
If, after adding aliases in RCP-200, you decide you would like to import router
configuration data in which there is a physical router with the same name as one
of your own in Router Manager, the alias data for that router will be over-written.