Model: DDU-TM-44/46 or DDU-44/46
Doc. Ref. no. : - m06c/om/101
Issue no. 04
User’s Manual
Page 34 of 36
9. TROUBLESHOOTING TIPS
If the operating display does not appear after turning on the controller’s power, follow the measures in
the procedure below.
If a problem appears complicated, contact our Customer support representative.
IMPORTANT
Take note of the parameter settings when asking the vendor for repair.
Time Code decoding problems can include any of the following:
• No Time Code present
• Ground loops or other interference such as coupling from nearby AC power lines, bad/intermittent
cables, wiring or connectors incorrect wiring connection for unbalanced or balanced input signals
• Out of range signal level that is too high or too low
• Fluctuating signal level
• A signal that is distorted
• A Time Code frame that your clock does not support
• In case of Wireless input, distance between Wireless master and slave is too far from Master so slave
cannot get the time code signal.
Problem:
Clock is unable to “Lock” to time code after 2 minutes.
Possible reasons/solutions:
For Incase of Serial Input:
1. Verify that
GPS master’s Baud rate, stop bit and parity bit are same as in DDU-TM-44/46 or DDU-
44/46.
2. Check all the input signals voltage level for DDU-TM-44/46 or DDU-44/46 synchronization. E.g.
RS232
– approx. 10.4 V DC, RS-485 – Varies between 0-5 V DC. Here these voltages are measured
with multi meter. This is not the exact voltage level of any signal but this gives ruff idea about signal
presence on port.
3. The time code being fed to the DDU-TM-44/46 or DDU-44/46 must be recognized format. Verify that
your time code source is providing one of the time code formats that the DDU-TM-44/46 or DDU-
44/46 can decode & match its frame length as per standard.
For Incase of Wireless Input:
4. Check the RF Receive channel is same
as the Wireless master’s Transmitting channel or DDU-TM-
44/46 or DDU-44/46 in Auto mode.
5. If you are trying to sync DDU-TM-XX with Wireless mater , then check they are not out of range , both
unit must be in range of 100 meter area , and if you are trying to sync DDU-TM-44/46 or DDU-44/46
with DDU-TM-44/46 or DDU-44/46 , slave to slave communication , then it must be in range of 50
meter area.
Problem:
Not displaying the correct local time and/or date.
Possible reasons/solutions:
1. For Serial communication: NGTS & T format supports IST only and so there is no requirement of Time
Zone offset, please enter 00:00 in Time Zone offset.
In case of NMEA ($GPRMC) frame format and Wireless input they are supporting UTC time so , enter
time zone offset as per your local time zone offset.
2. If LED in DDU-TM-44/46 or DDU-44/46 blinks after the time zone configuration done in DDU-TM-
44/46 or DDU-44/46, reset the power of the DDU-TM-44/46 or DDU-44/46 is must for effective
synchronization.
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
