Grass Valley Densité 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 Densité AppServer connects to hi as one Parameter Control Node. hi reaches the cards only through the AppServer, so the AppServer must discover the frames and cards first. Each Densité manager on the AppServer can use its own Port, so enter the Port of the manager that hosts your cards.
Caution
The template pre-fills a default account. Replace it with a dedicated AppServer account before production use. hi sends the account with HTTP Basic authentication over plain HTTP.
Before You Begin
-
Use Node admin and open Inventory > Nodes. See Manage Nodes.
-
Confirm the license and minimum hi version in Required Configuration.
-
Use Grass Valley iControl to administer the AppServer and its accounts. The Densité REST service is available from iControl 7.20.
-
Confirm the network access in Network Requirements.
Configure Densité Parameter Control
Use this configuration to read and write card parameters through a Densité AppServer.
Device Configuration
-
Confirm that the AppServer discovers the required frames and cards.
-
Record the REST Port of the Densité manager that hosts your cards. The default Port is
5955. -
Create an AppServer account with access to the required parameters.
hi Configuration
-
Add the Densité Parameter Controllable Device integration, manufacturer Grass Valley, in Inventory.
-
Enter the AppServer address and the REST Port. hi pre-fills
5955. -
In the Authentication group, enter Login Name and Password of the AppServer account.
-
Create the Node. hi queries the cards and their parameter names, and then opens one update session for each frame.
-
In the Parameter Browser, open a card, select the parameters that hi must monitor, and select Pin Selected.
-
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 |
|---|---|---|
|
REST Port |
Port of the Densité manager
|
Port
|
|
Account |
AppServer account |
Login Name and Password |
Common Checks
|
Symptom |
Check |
|---|---|
|
The Node does not connect. |
Confirm the Port of the Densité manager and that the AppServer accepts the account. |
|
Cards are missing. |
Confirm that the AppServer shows the cards and that the Port belongs to the manager that hosts them. |
|
The Node reinitializes without user action. |
The card list of the AppServer changed. hi reinitializes the Node when it detects a change. |
Verify the Configuration
Confirm that the Node reports a connected state and that the Parameter Browser lists the expected frames and cards. Pin a known parameter, change it on the card, and confirm that hi shows the new value. Then change a safe parameter from hi and confirm that the card shows the same value.