Tally Does Not Reach a Downstream Device

Diagnosis

Scenario

An upstream device reports Tally, but an expected downstream indication does not change.

Observed Behavior

The downstream Port, Multiviewer, UMD, or Hardware Panel does not show the expected Tally state.

Possible Causes

Tally propagation depends on supported device behavior, configured Tally sources, and an accurate Topology and Signal Path.

Prerequisites

Operator checks require Control Panel access and Tag access to the affected Ports.
Node configuration changes require Node admin; Tally changes require Tally admin. Topology changes require the administrator responsible for that configuration.
Agree a test state and affected outputs with the responsible operator before changing a live Tally state.

Resolution

Operator: Record the Tally Source, affected downstream object, expected state, and observed state.
Check the relevant Node states. If a Node is offline, follow A Node Remains Offline or Unreachable.
Follow Inspect a Signal Path to identify where the expected path stops. Record that point for the administrator.
Administrator: Compare the configured wiring between the upstream and downstream Ports with the intended Topology. Review the configured Tally sources using Manage Tally.
Confirm Tally support and limitations on the affected Supported Integration pages. Correct a confirmed configuration mismatch only within the supported device behavior.

Verify the Result

Using the agreed test state, confirm that the expected indication appears on the affected downstream device and follows the configured Signal Path. A connected Node alone does not verify Tally propagation.

See Tally and Labels.

If the issue persists after these checks, contact Riedel Customer Success. Include the observations from this page, the Serial Number or Installation ID, the hi version, and a Backup and log export. See Customer Support.