hi human interface®
hi human interface®
English
Breadcrumbs

Cyanview RCP Parameter Controllable Device Integration Configuration

Cyanview RCP Parameter Controllable Device 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

A Cyanview RCP connects to hi as one Parameter Control Node through the Ember+ provider of the RCP. The RCP decides which parameters exist, so hi shows only what the provider publishes. The Ember+ server of the RCP runs on TCP Port 9000 and is reachable on every IP address of the RCP.

Caution

Writes from hi change camera settings on the RCP. Test writes on a safe parameter only, and agree with the camera operator which side controls a parameter.

Before You Begin

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

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

  • Obtain access to the RCP configuration web UI and to the current Cyanview documentation.

  • Confirm the network access in Network Requirements.

Configure RCP Parameter Control

Use this configuration to read and write the camera-control parameters that the RCP publishes over Ember+.

Device Configuration

  1. Confirm that the RCP runs firmware 25.12.1rc1 or later. Earlier firmware does not report the last node of the Ember+ tree when no virtual GPIOs exist. The Ember+ server runs on TCP Port 9000 and needs no enabling.

  2. Record the RCP address and the Ember+ Port. Allow outbound TCP from hi to that Port of the RCP.

hi Configuration

  1. Add the RCP Parameter Controllable Device integration, manufacturer CyanView, in Inventory.

  2. Enter the RCP address and the Ember+ Port. hi pre-fills 9000. This template has no further settings.

  3. Create the Node. hi connects and loads the top two levels of the Ember+ tree.

  4. In the Parameter Browser, open the branches that you need, select the parameters that hi must monitor, and select Pin Selected. hi subscribes to the value updates of pinned parameters.

  5. Assign pinned parameters to Ports when operators need them on the Control Panel. See Assign a Parameter Control.

Settings Summary

Setting

Device Side

hi Side

Address

RCP IP address

Host of the Node

Ember+ Port

Ember+ provider Port of the RCP

Port
pre-filled 9000

Common Checks

Symptom

Check

The Node does not connect.

Confirm that hi reaches the RCP on TCP Port 9000 and that the Port in hi is 9000.

An element shows This is a Matrix.

The element is an Ember+ matrix. This integration does not manage matrices.

A parameter cannot be changed.

Confirm that the Ember+ access of the parameter allows writing. hi presents parameters without write access as read-only.

Verify the Configuration

Confirm that the Node reports a connected state and that the Parameter Browser shows the RCP tree. Pin a known parameter, change it on the RCP, and confirm that hi shows the new value. Then change a safe parameter from hi and confirm that the RCP shows the same value.