User manual

TCDS Series User Manual – Rev. 2.0.1 Page 32
Not displaying the correct local time and/or date.
Possible reasons/solutions:
1. The TCDS has a time zone offset and/or DST offset configured.
2. Your time code source and/or the TCDS are set with time zone and/or DST offsets.
3. Your time code source is not providing the time and/or date that you expect. Contact the
individual responsible for the time code source for more information.
Clock did not properly negotiate the DST.
Possible reasons/solutions:
1. Your time code source is not providing date information and/or a valid date was not
programmed into the TCDS.
2. Your time code source already provides the DST adjustment.
3. Your time code source or the TCDS does not have the correct DST rules configured.
UTC time and/or date is incorrect.
There are several potential failure points:
• Invalid, intermittent or missing time code source
• Date/year overwrite function for non-date encoded time code may be configured improperly
• Battery may need to be replaced
• A local time zone or DST configuration not set correctly
1. Verify that your time code source is generating the UTC referenced time and date that you
expect and that this time code format is at an acceptable signal level and quality that can be
detected at the client side (i.e. TCDS input).
2. When using SMPTE time code, verify that you are not using drop frame time code. Use only
NDF (non-drop frame) SMPTE time code.
3. If you are using in-house time code, verify that the time code source is locked to the GPS
satellite system for UTC time code. Time code sources such as SMPTE time code that is fed via
a broadcast satellite will have a delay due to the satellite transmission. The TCDS cannot
compensate for satellite transmission delays.
4. If you are using a time code source from another vendor, be certain your time code contains
encoded year/date information to the IEEE 1344 [IRIG-B] or Masterclock/Leitch [SMPTE] time
code encoding formats. IRIG-B(0)/B(1) time code format must have the year/date encoded to
the IEEE 1344 specification in the CF (Control Functions). SMPTE-type time codes must have
the date be encoded to the Masterclock/Leitch specification in the user bits.
5. If your time code source is providing DST adjustments and time zone offsets these functions
must be disabled in your TCDS in order to eliminate double offsets.
6. If you are using the date/time display such as on a Windows system to validate the time on
the clock, this may provide misleading information as these may be configured to display local
time zone and daylight saving time information and they may not be currently synchronized to
UTC time. This is configured through the Date/Time applet in the Control Panel or using an
NTP client.