NTP daemon driver for the Lindy Precision Clock MSF radio receiver

What is it?

The Lindy precision clock is an MSF receiver. MSF is the time signal send by the NPL in the UK. This signal sends the current date and time for the UK. This signal can be received in the whole UK and parts of Europe. I had a very good signal in Gouda in the Netherlands. It is calculated from an atomic clock.
Other signals are DCF77 (Germany), HBG (Swiss) and TDF (France).

Specs / what does it look like?

The Lindy precision clock has either a 2 meters long cable with either RS232 (9 pins) or USB connector.
picture of the Lindy precision clock

The device is sold by www.gude.info and www.lindy.co.uk.

Download

Please check the 'README'-file in the tar-ball for instructions on how to use this driver.
Linux users: kernel 2.6.22 (or more recent) is required as well as the header-files of this kernel (or else it won't even compile).
Download link:lpc-ntpd-1.0.2.tgz
lpc-ntpd-1.0.1.tgz
lpc-ntpd-1.0.0.tgz
lpc-ntpd-0.0.7.tgz
lpc-ntpd-0.0.6.tgz
lpc-ntpd-0.0.5.tgz
lpc-ntpd-0.0.4.tgz
lpc-ntpd-0.0.3.tgz
lpc-ntpd-0.0.2.tgz
lpc-ntpd-0.0.1.tgz

Changes

1.0.2more elaborate debugging output, some fixes
1.0.1when an EOF is received from the device the program now exits (this happens for example when the USB device is unplugged)
1.0.0now can also use the USB version of the clock (option '-b'), added parity check, properly handle summertime
0.0.7offsets too big were incorrectly used in the statistics, now displays percentage correctly received messages of total, 'saturday' was displayed as '(null)' (fixed that), code clean-ups
0.0.6now shows how long syncing takes on average (excluding initial sync), compensated for the delay introduced by receiver
0.0.5more verbose output
0.0.4fixed bug in offset calculation, added "write measurements to disk" option '-S', read-only mode ('-n') added, one can now set a user to run as, write pid to file
0.0.3added setting of fudge factor with the '-F' commandline switch (compensation of delays in the uart, etc.), added '-u' switch to select a shared memory slot, fixed communication with ntp daemon
0.0.2many code clean-ups, bug-fixes and move verbose output
0.0.1initial release

Solving bad reception

When you see a lot of errors (parity errors, strange offsets, etc.), make sure you have aligned the receiver correctly. It should be perpendicular to the transmitter of the MSF signal in Anthorn in the United Kingdom. Also if possible place the receiver as close to a window as possible, a window without heat-shielding coating or else you'll probably won't receive anything at all.
E.g. when your receiver is located in Marbihan, in Bretagne in France, make sure the line between the cable and the led of the receiver is aligned from west to east (or vice versa):




Check out my united states Mega Millions lottery winning help page