hi human interface®
hi human interface®
English
Breadcrumbs

Grass Valley Camera Connect Integration Configuration

Grass Valley Camera Connect 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

One Camera Connect server connects to hi as one Node. hi reads the cameras, base stations, and OCPs that the gateway publishes, and shows their functions as Parameters. The Node has no camera Ports. To show a camera or an XCU in the Topology, add the LDX Series or XCU Series template as well.

Configuration

What hi Sees

Use When

Camera Connect Gateway

A C2IP Network Parameter tree with Camera, Basestation, and OCP folders, and the functions of each device.

hi must monitor or control Grass Valley cameras through a Camera Connect server.

Before You Begin

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

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

  • Confirm the network access in Network Requirements.

  • Count the XML clients that already use the gateway. The gateway accepts up to 32 clients, and hi uses one.

Configure Camera Connect Gateway

Device Configuration

  1. Connect the public Ethernet port of the Camera Connect server to a network that the hi server can reach. Keep the second port on the C2IP camera network.

  2. Open the Camera Connect web interface in a browser and sign in.

  3. Open the XML Control page and confirm that the Connect Gateway is running. The gateway starts automatically with the server. Use Start if an operator stopped it. Stopping the gateway disconnects all XML clients.

  4. Give each camera, base station, and OCP that hi must control a device ID, for example its camera position, base station rack position, or OCP desk position. hi lists only devices that have a device ID.

  5. Record the IP address of the public network interface and the TCP Port of the gateway.

hi Configuration

  1. Add the Camera Connect integration (manufacturer Grass Valley) in Inventory.

  2. Enter the address of the public network interface and the Port. hi defaults to 8080. The Node has no other settings.

  3. Create the Node. hi identifies itself to the gateway, reads the devices and their functions, and then reads the function values.

Common Checks

Symptom

Check

The Node does not connect.

Confirm that the Connect Gateway is running on the XML Control page, that the address is on the public network side, and that fewer than 32 XML clients are connected.

A camera is missing from the Parameter tree.

Confirm that the camera has a device ID and that the gateway shows it as connected.

A Parameter cannot be changed.

The gateway publishes the function without write access. hi also shows device-ID functions as read-only.

A device folder disappears.

The device disconnected from the gateway, or the gateway reports it as unsupported. hi adds it again when it returns.

Verify the Configuration

Confirm that hi appears in the list of connected XML clients on the XML Control page. Compare the devices in the C2IP Network tree with the devices in the Camera Connect web interface. Change a writable function from hi, and confirm that the camera applies it. Then change the same function from an OCP, and confirm that hi shows the new value.