PCIe time code decoding fails due to signal issues

Symptoms

• Decoded time code is intermittent, unstable, or drops out.
• The system does not update consistently from the time code input.

Possible causes

• Noise, grounding/shielding problems, or ground loops affect the signal.
• Cables, connectors, or signal levels do not meet the receiver requirements.
• The source uses an unsupported time code format.

PCIe-TCR input formats

The PCIe-TCR supports the following time-code inputs. For current product documentation, visit Masterclock Resources:

• SMPTE non-drop-frame time code with Leitch date encoding.
• IRIG-B pulse-width-coded, unmodulated DC with IEEE 1344 support.
• IRIG-B(1), 1 kHz amplitude-modulated, with IEEE 1344 support.

Balanced and unbalanced inputs are supported. These details apply to the PCIe-TCR model; confirm the installed model before using them to assess the source signal.

Troubleshooting steps

1. Compare the source format and signal level with the requirements for the installed PCIe card.
2. Inspect the cable and connectors, including connector seating and any visible damage.
3. Review cable length and grounding/shielding against the installation documentation.
4. After correcting an identified signal-path issue, check decoded time again before making another change.

Related articles

• PCIe TCR shows calibration in progress or unhealthy
• PCIe time code input is not decoding

• Wrong UTC time or date when using time code input