Wrong UTC time or date when using time code input

NTDS/TCDS controller check

For NTDS/TCDS displays, including LUX, time-code input requires a TC or dual controller. An NTP-only controller has no Time Code Reader option. TC-only controllers have no NTP or network options; configure the reader through the device interface supported by that controller. See NTP, TC and dual controller types.

Symptoms

• Time code is received, but the decoded UTC time or date is incorrect.
• Time differs by a consistent offset, or the expected date/year is missing.

Possible causes

• The source does not encode the required date/year information.
• The source or receiver applies a time zone, DST, or other offset.
• Input signal level or integrity prevents reliable decoding.

Troubleshooting steps

1. Confirm the time code signal is present at the receiver input and meets the input requirements in the device documentation.
2. Confirm the source encodes date/year where required. The existing documentation identifies SMPTE Leitch-style user bits and IRIG-B IEEE 1344 control functions as relevant formats; verify compatibility for the source and receiver in use.
3. Review UTC/local time, time zone, DST, and offset handling at both ends. Disable unwanted source offsets or use receiver offset settings where available.
4. For non-date-encoded time code, review any overwrite settings against the intended behavior.

Related articles

• Why time code requires clean signal levels
• What is the difference between UTC and local time?
• PCIe time code decoding fails due to signal issues