Grass Valley Prelude v.3.0 - Manual (Page 68)

68 Prelude — Instruction Manual
Section 2 — Installation and Initial Setup
Save and Send Router Configuration File
The changes you have made to this router configuration will not take effect
until the file is sent to the Prelude panels. Save and Send the configuration
file, as described on
page 64 .
Prelude Native Protocol Server
Introduction
Prelude control panels can be configured to act as Native Protocol (NP)
servers. Doing so can give external entities access to a Prelude routing
system. Some external devices, like Under Monitor Displays and the Visual
Status Display application, can use this interface to receive and display
status information. Other external devices, like automation systems, can
use this interface to actually control Prelude system crosspoints.
Prelude panels by default are not configured for external access. This
feature is activated by specifying the external client device that will be per-
mitted access (via its IP address or Serial port settings) to a panel’s NP
server. That external client will then be able to communicate with that
server and, through that panel, interact with the rest of the Prelude system.
Client configurations can be created and saved for reuse on different
panels. This permits easy redundancy configuration for external clients
that support this capability.
All Prelude system control panel models support up to four Ethernet NP
servers. The UCP control panel supports one Serial port NP server in addi-
tion to the four Ethernet servers.
NP Client/Server Configuration Process
The NP client/server configuration process involves several steps.
1. An external device client configuration is created and saved. This
configuration has a name for the client and the communications
settings to be used (IP address or serial communications port).
2. The client configuration is assigned to a specific server on a specific
panel. If that panel will support multiple clients, additional clients are
created and assigned to other servers on that panel (up to five).
3. The single or collection of client/server assignments is saved for that
panel.
4. The panel configuration with these assignments is sent to the panel.