Cyanview RCP Parameter Controllable Device

Driver Maturity

Production

Recommended for normal production use.

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.

Minimum hi Version: v2.5.0

Overview

Cyanview camera-control parameters are exposed in hi through the RCP's Ember+ provider. hi reads the published parameter tree, subscribes to updates, and writes supported parameter values.

Network Requirements

Connection Model: hi initiates a persistent TCP connection to the RCP.
Multicast / Unicast: Unicast only.
VLAN / IGMP: No multicast configuration is required.
Bandwidth: Control traffic only.
IP Version: IPv4.
Firewall: Allow outbound TCP from hi to the Ember+ provider Port of the RCP. The Ember+ server of the RCP runs on TCP Port 9000, which hi pre-fills.

Standards Conformance

Standard	Conformance	Notes
Ember+ (Lawo)	Glow DTD parameter tree per Ember+ spec	Open community specification used as a de facto standard widely adopted

Operator Workflow

UI Surface in hi: Control Panel, Parameter Control, and Inventory
Template Selection: The template is listed as RCP Parameter Controllable Device, manufacturer CyanView.
Parameter Semantics: Parameters published by the Cyanview Ember+ provider appear under the device Node in Inventory.
Device Administration: Configure the RCP and cameras in Cyanview tooling. Only controls documented on this page are supported through hi.

Connection Details

Property	Value
Protocol	Ember+
Transport	TCP
Default Port	9000
Authentication	No credentials are configured by this hi integration
Encryption in Transit	None - this Ember+ connection uses plaintext TCP
Connection Model	Persistent TCP with parameter subscriptions
Required License	hiBase
Traffic Flow	Outbound connection with inbound responses and parameter updates

Required Configuration

Parameter	Description	Default
Host / IP Address	IP address or hostname of the Cyanview RCP	-
Port	Ember+ TCP Port	9000

Device-Side Setup

Follow Cyanview RCP Parameter Controllable Device Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Feature	Access	Exposed Operation and Scope
RCP Parameter Tree	Per-parameter access	Read published values and write only parameters whose Ember+ access metadata allows writing; other parameters are presented as read-only in hi.
Live Updates	Read-only subscription updates	Subscribe to and receive changes published by the RCP. Updates are read-only feedback.

Known Limitations

The parameter tree and available controls are defined by the connected Cyanview system.
If Parameters do not appear, 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.
Ember+ matrices appear as placeholders with the message This is a Matrix. Please add an Ember+ compatible router from the Nodes screen to manage it. Other unsupported element types also appear as placeholders.
The Cyanview RCP does not answer Ember+ keep-alive requests, so hi sends them every 5 seconds without waiting for an answer. hi detects a lost connection from the TCP connection instead.
When hi connects, it loads the top two levels of the Ember+ tree. hi loads deeper levels when you open them in the Parameter Browser, and it subscribes to value updates of pinned parameters.
hi presents Boolean, Integer, Real, String, and Enum parameters. When a parameter carries an Ember+ factor, hi divides the value by the factor and shows a decimal value.
The RCP configuration web interface uses TCP Port 5000. hi does not use this Port.
The Cyanview Ember+ interface offers limited functionality. Camera selection is published through the requested_camera and active_camera parameters of the RCP tree.

What's Not Supported

Controls that the connected RCP does not publish in its Ember+ tree.
Firmware updates, device backup, and camera or RCP network configuration.
Ember+ Functions, including Qualified Functions, and function invocation. The Ember+ specification defines them from Glow 2.20, and hi never sends an Invoke command.
Ember+ Templates, including Qualified Templates, and template references. The specification defines them from Glow 2.40. hi requests all fields of each element, and it does not resolve template references.
Ember+ Octets parameters. hi shows them with the message This parameter's data type can't currently be managed from hi.

Trademarks

Note

Cyanview is a trademark of Cyanview SPRL.

All product names, logos, and brands are property of their respective owners. Copyright in third-party software and materials remains with the respective owners. Use of these names does not imply endorsement.

RIEDEL Communications is not affiliated with, endorsed by, or officially partnered with Cyanview unless explicitly stated.