Follow

Clock Error Codes and Resolution

Waiting to Connect

Reason:

 

This message is displayed when the DTC is unable to communicate with the display controller, thus by default this message is shown on the screen. In older PCB versions, the DTC uses the BUS to communicate with the display controller. Newer clocks use local serial communication, less likely to be affected by the BUS.

 

  1. i) Possible Issue:

 

BUS is corrupted (unstable): Since older PCB clocks communicated with the display’s controller over the bus, if the bus is unstable, this message will be displayed.

 

Resolution:

 

  • Stabilize the bus; check for bad CAT5 and bad clock cable; additional or missing terminator or a bad device.

 

 

 

  1. ii) Possible Issue:

 

DTC's firmware is unable to pass through a RESET routine to get out of the error loop. (Pre-4.xx firmware when 60Hz time base is missing).

 

Informational: There should be a 60Hz signal to the DTC (Sine wave for regular clocks, TTL square wave for Blue Boxes).

 

Resolution: 

 

  • Test for a steady voltage to the Control card from the transformer.
  • Check the clock cable and make sure it is not damaged or nicked.

 

 

iii) Possible Issue:

 

An upgrade process was interrupted most likely due to a bad quality phone line or power loss before the process was completed. After an incomplete upgrade process, the power has been cycled (unplugged). Unfortunately some techs in the past did not document an unsuccessful upgrade, and time by time we run into this issue.

 

Resolution: 

 

  • Attempt to upgrade to the latest clock version normally and it should be able to complete the upgrade process. While upgrading for the second time, the modem should answer. Please make an announcement if an unfinished upgrade occurs and try again or see Zoly and let him know. It is possible that the phone line is not so stable. As always, please enter clear and accurate notes into M3!

 

 

 

 

 

  1. iv) Possible Issue:

 

The power source to the control card is below 12V. Clocks require a minimum of 8.5V to start up and after being powered up, they normally require at least 10.5V.

 

Resolution: 

 

  • Check the following voltage levels:
    1. Breaker to Panel (Line Voltage)
    2. Dual Voltage Card to Primary Side of the transformer (120V or 277V AC)
    3. Secondary Side of the transformer to the Control Card (2x10V)
    4. Control card to DTC (For GR2400). For Blue boxes, check the voltage to the control card since the clock is on the Control card.

 

Upload is in Progress

 

Reason:

 

This message is displayed on a DTC if an upgrade process was interrupted and not completed. On Blue box master control cards, the screen may be blank if the clock upgrade was interrupted and the card power cycled.

 

  1. i) Possible Issue:

 

An upgrade process was interrupted most likely due to a bad quality phone line or power loss before the process was completed as was the case with issue (iii) in the previous section; with the exception that the power has not been cycled yet.

 

Resolution:

 

  • The fix is the same as it was for issue (iii) in the previous section. Attempt to upgrade to the latest clock version normally and it should be able to complete the upgrade process. While upgrading for the second time, the modem should answer. Please make an announcement if an unfinished upgrade occurs and try again or see Zoly and let him know. It is possible that the phone line is not so stable. As always, please enter clear and accurate notes into M3!

 

Hard Code Failure 02

 
Reason:

 

This message appears when the DTC gives a direct error code to the display controller during the peripheral checking test and the test fails. Peripheral checking is a process consisting of a series of tests that verify communication between all components on the board. If any of the checks fail during the peripheral checking test, a “Hard Code Failure 02 error is displayed on the DTC screen.

 

 

  1. i) Possible Issue:

 

DTC's MCU can not read/write the FLASH or RAM properly (loose solder or impact of EMF). It is also possible that any other internal peripheral error can cause this event.

Resolution:

 

  • Power cycle the clock; if the clock does not boot up normally after this, replace the clock and have it sent back directly to Zoly for analysis.

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.