Ross Video Carbonite Series 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 Carbonite switcher sends its Tally to hi as TSL UMD data, and hi listens for it. You add a TSL UMD device on the switcher that points to the hi server, and you add a Carbonite Node in hi that listens on the same Port.

Configuration	What hi Sees	Use When
Receive Tally	The switcher sources as input Ports, named from their TSL text, and the switcher tally bits, which you map to hi Tallies.	hi must show the on-air state of the Carbonite inputs.

Caution

The TSL version, the transport, and the Port must match on the switcher and in hi.

Before You Begin

Use Node admin and open Inventory > Nodes. See Manage Nodes.
Confirm the license and minimum hi version in Required Configuration.
Choose a listening Port in the range 31000 to 31999. Give each Node its own Port.
Select TSL v3.1 or v5.0 and TCP or UDP, and record the hi listening address.
Open the switcher in Ross DashBoard.
Confirm the network access in Network Requirements.

Configure Receive Tally

Device Configuration

In DashBoard, select Navigation Menu > Configuration > Devices.
Select Add Device, and select a free Ethernet device slot in Slot. A slot that another device uses does not appear in the list.
In the Type area, select TSL UMD. In the Driver area, select TSL 5.
Enter these settings for the device:

Setting	Value
IP Address	The IP address of the hi server. In a redundant installation, enter the virtual IP address.
Port	The listening Port of the hi Node.
Transport	TCP or UDP. The Transport must match the Port that you chose and the transport in hi.
Screen	`0`, the default.
TSL Header	Off for TSL 5 over UDP for TSL 5 over TCP, configure DLE/STX framing
TSL Brightness	`1`, low, by default. `0` is off, `2` is medium, and `3` is high.
1 Second Update	Off sends every address once each minute. On sends a single address each second.
Center	On centers the label text.
FSFC Label	On adds the FSFC to the label when an FSFC is applied to the source.
Show Bus Name	On adds the bus name to the label. Off sends only the source name.
Show UMD ID	On starts the label with the decimal UMD ID of the source.

Select Save.
The switcher sends Tally for its sources by their TSL IDs. Read the TSL ID of each source in the Ross device database for the switcher.
If several switchers send to the same receiver, give each one a different TSL Offset. Input 1 with offset 0 uses ID 1, and with offset 10000 it uses ID 10001. On an Ultrix Carbonite, router tally IDs can start at 0 for input 1. Confirm the first ID before production use.

On a Carbonite, Carbonite Black, or Carbonite Ultra, the panel menu path is MENU > SYSTEM > NEXT > NEXT > Device Config. Press Add, select an Ethernet slot, set Type to SerialTally and SubType to TSLUMD_1.0, enter the IP address of the hi server, and set Port, Transport, Center, FSLBL, ShowBusName, ShowUMDId, and 1SecUpdate with the Option and Value knobs. This device sends TSL 3.1 with labels of up to 16 characters. ID 0 carries black, background, or no source, and input 1 uses ID 1.

Information

The numbered DashBoard procedure above applies to the Ultrix Carbonite. Menu paths can differ on other Carbonite models and software versions. TSL 3.1 carries addresses 0 to 126, so use TSL 5 for higher IDs. The switcher itself accepts incoming TSL 3.1 data on TCP Port 5727 and TSL 5 data on TCP Port 5728.

hi Configuration

Add the Carbonite integration in Inventory.
Enter the listening Port, and select the TSL version and the same transport as on the switcher.
Create the Node and wait for it to initialize.
Open the Tallies tab and map each switcher tally, for example TSL3 Bit 0 - Tally 1 or TSL5 Bit 2 - Text Red, to a hi Tally. The received sources appear as the input Ports of the Node. With TSL 3.1 from a Carbonite, Carbonite Black, or Carbonite Ultra, Tally 1 is preview and Tally 2 is program. Tallies 3 and 4 are always off.
Verify Tally Protocol and Tally Transport on the Node. They default to TSL 3.1 and UDP. Set Tally Protocol to TSL 5 for the TSL 5 driver, or keep TSL 3.1 for the TSLUMD_1.0 subtype, and set Tally Transport to the transport that you chose on the switcher. Leave TSL Address Offset at its default of 1 unless the first Port number must differ. The offset is added to each received address to form the hi Port number.

Settings Summary

Setting	Device Side	hi Side
Destination	IP Address of the hi server	The hi server
Port	Port of the TSL UMD device	Listening Port from `31000` to `31999`
Version	Driver TSL 5 or SubType TSLUMD_1.0 for TSL 3.1	Tally Protocol the same version
Transport	Transport	Tally Transport the same transport
Input identity	TSL ID of each source in the device database plus TSL Offset	Port number from the received address plus TSL Address Offset

Common Checks

Symptom	Check
hi receives nothing.	Confirm that the switcher targets the hi server address and the Node Port, and that the version and transport match.
TSL IDs do not match the inputs.	Confirm the TSL ID of each input and the TSL Offset of the switcher.
TSL data arrives and the Tally does not work.	For TSL 5 over UDP, keep TSL Header Off. For TSL 5 over TCP, configure DLE/STX framing and verify that the switcher sends the wrapper.
Two Nodes behave as one.	Give each Node its own Port.

Verify the Configuration

Select an input on the switcher and confirm that the matching input Port of the Node follows. Map a switcher tally on the Tallies tab to a hi Tally and confirm that the Tally follows the switcher.