[ntp:questions] Sure RPC DCF77 clock under Linux?

Ulrich Mueller ulm at kph.uni-mainz.de
Thu Jan 5 16:47:50 UTC 2006


Could anybody give me some advice how to run the "Sure RPC" DCF77
clock under Linux?

If I try to operate it with the Parse clock driver in mode 16, the
DCF77 information cannot be decoded and lines like the following
appear in the logfile:

 5 Jan 10:46:00 ntpd[6092]: parse: convert_rawdcf: parity check FAILED for "-------------------Ls1-48---P1----2p12-8-----12-----48----"
 5 Jan 10:47:00 ntpd[6092]: parse: convert_rawdcf: parity check FAILED for "-------------------Ls1248---P-----2p12-8-----12-----48----"
 5 Jan 10:48:00 ntpd[6092]: parse: convert_rawdcf: parity check FAILED for "-------------------Ls1---1--P-----2p12-8-----12-----48----"
 5 Jan 10:49:00 ntpd[6092]: parse: convert_rawdcf: parity check FAILED for "-------------------Ls12--1--P1----2p12-8-----12-----48----"
 5 Jan 10:50:00 ntpd[6092]: parse: convert_rawdcf: parity check FAILED for "-------------------Ls1----2-P-----2p12-8-----12-----48----"
 5 Jan 10:51:00 ntpd[6092]: parse: convert_rawdcf: parity check FAILED for "-------------------Ls12---2-P1----2p12-8-----12-----48----"
 5 Jan 10:52:00 ntpd[6092]: parse: convert_rawdcf: parity check FAILED for "-------------------Ls1-4--2-P1----2p12-8-----12-----48----"

It looks like my hardware is functioning properly, but the telegrams
appear to be shifted by one bit.

I have tried with ntp-4.1.2 and ntp-stable-4.2.0.20050303 under kernel
versions 2.4.28 and 2.6.11 (only 3 of the 4 possible combinations
though), always with the same result. Running with mode 5 instead of
mode 16 and manually setting the RTS and DTR bits does not help either.

Any hints or pointers?

Best regards
Uli




More information about the questions mailing list