MSF clock module

[cunninghamjohn]

Thanks Bob. I am pretty sure the clock is for Rugby/now Anthorn. So far I have got the pic to decode the minute information, and I have an LED flashing once per minute. I have 2 other LEDs flashing the 1s and 0s of the time/date information. I have been sat with a pen jotting down the 1s and 0s but not yet deciphered it into anything meaningful.

N var word
PAUSE 1000
HIGH PORTB.2
START
PULSIN PORTB.0,0,N
IF N=>49000 and N=<51000 THEN PULSOUT PORTB.4,50000 ;500mS 'minute'

IF N=<15000 and n=>5000 THEN PULSOUT PORTB.5,10000 ;100mS '0'

IF N=>15000 and n=<25000 THEN PULSOUT PORTB.6,10000 ;200mS '1'

GOTO START

I hear what you say on using interrupts, but with my limited experience im thinking of using a separate pic to drive the display and provide alarm functions. I only started using picbasic a couple of weeks ago, prior to that I havent used basic for at least 10 years. The code above is what im using to drive the 3 LEDs so far.

[derryck]

I have been sat with a pen jotting down the 1s and 0s but not yet deciphered it into anything meaningful.

That would be useful as a means of seeing if your receiver is correctly picking up the signal and as a learning aid, but otherwise not needed.

Your clock will never be accurate until you decode a whole minute's worth of time information and set your clock from that. You can then use that to perhaps update a RTC chip, which in turn keeps your clock running until the next time you decide to do an update from MSF, if you want some form of backup.

I won't comment on the supply to your receiver, or the level of its output as the latter might depend on how you ultimately decide to detect the pulses.

If you care to PM me with your email address, I will send you a document that I prepared for the local U3A Science and Technology group which I think clarifies the major part of the data stream format, omitting the niceties.