hi human interface®
hi human interface®
English
Breadcrumbs

Sony HDCU-5500 Integration Configuration

Sony HDCU-5500 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

The HDCU-5500 Node can use two control surfaces. Ember+ provides Parameter Control. TSL UMD sends the monitored Source name and Tally states to the HDCU display. Each surface is optional and uses its own Port.

Configuration

What hi Sees

Use When

Ember+ Parameter Control

The Ember+ Parameters that the HDCU-5500 exposes, under the Node in Inventory.

Camera Parameters must be read or written from hi.

TSL UMD

No additional objects. hi sends label and Tally data to the HDCU.

The HDCU display must show the monitored Source name and Tally.

Before You Begin

Configure Ember+ Parameter Control

Device Configuration

  1. Confirm that the HDCU-5500 has the Sony HZCU-CNFG50 Ember+ protocol license. This option provides Ember+ control on the HDCU-5500, HDCU-3500, HDCU-3170, and HDCU-3100. Set EMBER+ to ENABLE on the EMBER+ page of the NETWORK menu. The HDCU accepts Ember+ connections on TCP Port 9000, which is also the hi default.

  2. On the HDCU-3100, load the license file from a USB flash drive on the OPTION KEY page of the MAINTENANCE menu, and then set EMBER+ to ENABLE on the EMBER+ page of the NETWORK menu. The CCU then accepts Ember+ connections on Port 9000 of its LAN-COM connector, and CONNECTION STATUS on the same page shows the connection state. The HDCU-5500 uses the same EMBER+ page of the NETWORK menu, where PORT NUMBER shows 9000.

hi Configuration

  1. Add the Sony HDCU-5500 integration in Inventory.

  2. Enter the HDCU address.

  3. Set Count to 1, and set Start numbering with to the number of the CCU. All CCUs created together initially use the same Ember+ and TSL addresses. Create one Node for each HDCU-5500, or edit each Node's addresses afterward.

  4. Create the Tally definitions that hi must send before you create the Node. hi sends the first two Tally definitions, by order, that exist at that time.

  5. Create the Node, and confirm that the Ember+ connection uses the commissioned Port.

hi discovers the exposed Parameters after the connection is established.

Configure TSL UMD

Device Configuration

  1. IP Tally with TSL UMD v5.0 is a standard feature of the HDCU-5500. Set TSL UMD to ENABLE on the TSL UMD page of the NETWORK menu. PORT NUMBER shows the UDP Port, 8900, which is also the hi default.

  2. hi sends TSL 5 display index 1 on screen 0. After hi sends a label or Tally, confirm that PACKET STATUS on the TSL UMD page shows RECEIVED with ID 1.

hi Configuration

  1. Open the Node that you created.

  2. Confirm that the TSL UMD connection uses the HDCU address and Port 8900.

Settings Summary

Setting

Device Side

hi Side

Parameter Control

NETWORK > EMBER+
EMBER+

ENABLE
TCP Port 9000

Ember+ connection
default Port 9000

UMD display

NETWORK > TSL UMD
TSL UMD

ENABLE
UDP Port 8900

TSL UMD connection
default UDP Port 8900
display index 1

CCU numbering

Not applicable

Count and Start numbering with

Common Checks

Symptom

Check

Parameters are missing.

Confirm that the Ember+ interface is enabled and that its Port is reachable.

The display shows no label or Tally.

Confirm that TSL UMD is ENABLE, that UDP Port 8900 is reachable from hi, and that PACKET STATUS on the TSL UMD page shows RECEIVED with ID 1.

Verify the Configuration

Read one supported Ember+ Parameter. When TSL UMD is enabled, change a label or a Tally state in hi and confirm that the HDCU display updates.