Model: DDU-24/26
Doc. Ref. no. : - m06bom101
Issue no. 09
User’s Manual
Page 49 of 51
PROBLEM:
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 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. DDU-24/26 input).
2. 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.
3. If your Time Code source is providing DST adjustments, Please Note that DDU-24/26, does not
support any kind of DST adjustments.
4. If your Time Code source is providing Time Zone offsets these functions must be disabled in your
DDU-24/26 in order to eliminate double offsets.
PROBLEM:
Unit time show more than 2 second delay.
Possible reasons/solutions:
Unit has been show correct time (<1s delay) when received wireless frame then after it show delay
(increment delay) time until next frame receive.
1. Check that unit receive frame from Multiple Master (more than one unit transmit frame on same
transmit channel)
2. If you are not using unit as master then you select no option in Retransmission configuration.
Problem:
Clock is unable to “Lock” to time code after 2 minutes.
Possible reasons/solutions:
1. Close the TELNET configuration window, if DDU-24/26 is under configuration over TELNET
Protocol.
2. Use
Cross
CAT5 or equivalent cable for synchronization of DDU-24/26 with Master Clock / Desktop
Computer.
3. Check the connectivity of DDU-24/26 in LAN using ping command. (if Ethernet as input)
4. For NTP + PoE model check connectivity between LAN and PoE injector and Display Unit and PoE
injector.
Problem:
Clock is unable to configure with received configuration frame from Master GPS-MC-2.
Possible reasons/solutions:
1. Make sure that Matching of Slave ID.
2. RF Receive Channel of Slave Clock is same as RF transmit Channel of Master GPS-MC-2.
3. When sending Configuration Frame then DP of Lower Digit of Minute or Slave Blinking or Not. If start
Blinking Means the Slave ID does not match.
Problem:
DDU-24 display Er.03 when sending configuration command From GPS-MC-2
Possible reasons/solutions:
1. DDU-24 does not support YY.MM.DD format it only display DD.MM or MM.DD format.
2. You can see the Table 4 for more understanding which type of Error is display.
Problem:
Display Unit with NTP +PoE input Model is not Power on.
Possible reasons/solutions:
3. Check the Power cable of PoE injector is proper connected.
4. Check the CAT5 cable connected between display unit and PoE injector is proper connected.
PROBLEM
: Clock is unable to find NTP reference.
Possible reasons/solutions:
