FOR-A HVS Series

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: v1.2.1

Overview

The FOR-A^® HVS integration receives Tally states and UMD labels through TSL UMD. An optional TSL output sends dynamic Source labels back to the switcher.

Network Requirements

Connection Model: Inbound TSL to hi, with optional outbound dynamic-label delivery
Multicast / Unicast: Unicast only
Bandwidth: Control traffic only.
IP Version: IPv4 (IPv6 support varies by vendor - verify before relying on it)
Firewall: Allow inbound TCP or UDP to hi on port 31000 by default. If Dynamic Labels are enabled, allow outbound TCP or UDP to the port shown in LAN2(SUB) PORT on the HVS.

Information

Send the switcher's TSL UMD output to the commissioned hi server address and this integration's listener Port. The default is 31000, and the permitted range is 31000 to 31999. If you change it, update the switcher's target and the firewall rule. The optional Dynamic-Label output uses a separate listener on the switcher, at the port that the HVS shows in LAN2(SUB) PORT.

Standards Conformance

Standard	Conformance	Notes
TSL UMD Protocol v3.1 / v5.0	Inbound Tally and UMD plus optional outbound Dynamic Labels	Published TSL protocol implemented by the hi integration

Operator Workflow

UI Surface in hi: Tally, UMD, and Dynamic Labels
Capabilities: Inbound TSL Tally/UMD data and an optional separately configured dynamic-label output
Routing Semantics: The integration does not expose switcher routing or Crosspoint control.
Tally / UMD Relationship: hi receives switcher TSL UMD frames and reflects their Tally states and labels across Hardware Panels and Multiviewers.
Notes for Operators Familiar with the Vendor's Own Tooling: Configure production switching and TSL output in the vendor tooling; use hi for Tally, UMD, and dynamic-label workflows.

Connection Methods

Connection: Inbound TSL UMD

Connection Details

Property	Value
Protocol	Inbound TSL v3.1 / v5.0
Transport	TCP or UDP
Default Port	31000
Authentication	None - the TSL UMD protocol does not define authentication unidirectional display protocol
Encryption in Transit	None at the TSL protocol layer
Connection Model	TCP or UDP server for inbound TSL
Required License	hiBase
Traffic Flow	Inbound to hi

Connection: Optional Dynamic-Label Output

Connection Details

Property	Value
Protocol	TSL UMD v3.1 / v5.0
Transport	TCP or UDP
Default Port	8901
Authentication	None at the TSL protocol layer
Encryption in Transit	None at the TSL protocol layer
Connection Model	TSL client
Required License	hiBase
Traffic Flow	Outbound from hi

Required Configuration

Parameter	Description	Default
hi server Address	IP address of the hi server used as the switcher's TSL target	-
Tally Listening Port	Port on which hi receives TSL	31000
Dynamic-Label Address	Optional switcher address that receives TSL labels from hi	-
Dynamic-Label Port	The port shown in LAN2(SUB) PORT on the HVS. hi pre-fills `8901`; replace it with the port that the HVS shows.	8901 (hi pre-fill)
Tally Protocol	TSL variant that the switcher sends. Select `TSL5` for the HVS-2000.	TSL31
Tally Transport	Transport of the switcher TSL output	UDP
TSL Address Offset (TSL Settings)	Added to each received TSL address to form the hi Port number. With `1`, HVS Display ID `0` becomes Port `1`.	1
Label Protocol	TSL variant of the switcher label receiver. Select `TSL5` for the HVS-2000.	TSL31
Label Transport	Transport of the switcher label receiver	UDP
TSL Address Offset (Dynamic Label Settings)	Subtracted from the hi Port number to form the outgoing TSL address	1

Device-Side Setup

Follow FOR-A HVS Series Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Feature	Access	Exposed Operation and Scope
Source Ports	Read-only input	Create an input Port for each received TSL display address, and name it from the received UMD text.
Tally States	Read-only input	Receive the Tally states supported by the selected TSL version.
UMD Label Text (TSL v3.1)	Read-only input	Receive legacy under-monitor display label messages.
UMD Label Text (TSL v5.0)	Read-only input	Receive screen/display-addressed variable-length label messages.
Dynamic Source Labels	Write-only output	Send Source labels through the optional, separately configured TSL output.

Known Limitations

Optional Dynamic Label output uses a separately configured client.
hi creates input Ports only for the display addresses that it receives. Dynamic Label entries exist only for these Ports, so the switcher must send TSL to hi before you set up Dynamic Labels.
hi forms each Port number from the received display address plus TSL Address Offset, which defaults to 1. With the default, HVS-2000 input 1 (Display ID 0) becomes Port 1, AUX 1 (Display ID 50) becomes Port 51, and the M/E1 program output (Display ID 70) becomes Port 71.
hi uses the display address of each received TSL 5 message and ignores its screen number.
Over TCP, hi accepts only TSL 5 packets that start with the DLE/STX packet start. Over UDP, it accepts packets with or without the packet start.
When Label Protocol is TSL5, hi sends each Dynamic Label as a TSL 5 single display message on screen 0, with the DLE/STX packet start. The outgoing display address is the Port number minus the TSL Address Offset in Dynamic Label Settings.
hi receives and sends TSL over TCP or UDP only and has no serial TSL connection. The HVS-100, HVS-110, HVS-XT100, and HVS-XT110 send TSL Tally on RS-422 only, so hi cannot receive TSL from these models. The HVS-2000 sends and receives TSL UMD 5.0 over Ethernet on its LAN2 (SUB) port, and the HVS-490 on its LAN EXT port.

What's Not Supported

Sending Tally to the switcher. Dynamic Label messages carry the label text only.
Switcher routing, Crosspoint control, macro authoring, and ME setup.
Firmware updates, device configuration backup, panel calibration, and engineering configuration.

Trademarks

Note

FOR-A is a registered trademark of FOR-A Company Ltd.

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