News:

PROTON pic BASIC Compilers for PIC, PIC24, dsPIC33

Main Menu

MSF time signal from Anthorn in the UK

Started by Bob (G8GFA), Feb 13, 2021, 10:43 AM

Previous topic - Next topic

Bob (G8GFA)

This article shows how the MSF time signal from Anthorn in the UK may be decoded and displayed. A Symtrik SYM-RFT-60 module is used to receive the 60kHz signal and a 16F628A employed to decode it. Both time and date are displayed on a standard 16*2 LCD. A DS1307 RTC acts as a backup for times when a valid MSF signal is unavailable. The MSF time signal can  be received throughout much of Western Europe, including Ireland and the Channel Islands.


The MSF Protocol

There is much detailed information available on the Internet regarding the MSF protocol and consequently it is not my intention to repeat it here. That said, a short overview of the signal coming from Anthorn will help the reader understand what is happening within the program.

The signal transmitted from Anthorn uses a simple carrier on-off type of modulation. The presence of the carrier (radio signal) indicates logic 0 whilst logic 1 is represented by carrier absence.  All the information required to display both the time and date is received within a one minute period.

It is useful to think of each second of transmission as being broken up into ten 100ms pieces, each representing a single bit. The beginning of each minute (second 00) is marked by 500ms of logic 1 followed by 500ms of logic 0. In other words the received data is %1111100000. The following seconds (01 – 59) are transmitted in the format %1AB0000000. The 1 seen at the beginning of this string is used as a second marker. The A and B bits are varied according to the value of the data being transmitted.

Seconds 1 to 16 are used to transmit DUT1 information. This is the difference between atomic and astronomical time and is not required by this application.  Seconds 17 to 51 contain time and date information in binary coded decimal form. The remaining seconds (52 – 59) are used for a variety of things such as warning that summer time (BST) is in effect and parity error checking.

It should be understood that time and date information collected during one minute  relates to the minute which follows it. To put it another way, during minute 30 (for example) information about minute 31 is being collected.



Program Description

Before giving a brief overview of how the program works it is useful for the reader to be aware that the Symtrik SYM-RFT-60 module inverts the MSF signal. In other words a logic 1 is represented by (approximately) +Vcc and 0 by (approximately) 0V

It is also important to understand that the values used in the Select DataIn case statements (i.e. Case 475 To 550) are based on a crystal frequency of 4MHz. Change the crystal value and you'll need to alter the values used. See the Proton manual for further details.


After initialisation the program uses the PulsIn command to look for a positive going pulse on (in my case) PortB bit 3. What happens next is dependent on the length of the pulse detected.

Consider the case where the first pulse received is 500ms long. This is the start of the minute marker. The seconds counter (SecCnt) is set to 0 and the variable Flag is set to 1. This bit indicates that minute synchronisation has been achieved.  As none of the conditions set out in the various case statements are true, the program moves towards the end where it encounters a BusIn command which reads the DS1307 RTC. The result of this read is then displayed on an LCD.  A delay of 350ms is included at the end of the While – Wend loop and is important for two reasons. Firstly, it ensures that the PulsIn command at the top of the loop does not time out. Secondly, it masks any second pulse which might occur during seconds 1 – 16 as the result of bit B being set i.e. AB = 01. 

During seconds 1-16 the program detects the 100ms pulse of the second marker and increments the SecCnt variable. The DUT1 data is not required and therefore never collected.

With the arrival of second 17, the program starts to retrieve the time and date data. 
All relevant time and date variables are cleared before the start of second one. With each passing second a given bit of a particular variable will be set, or not, depending on the length of the pulse detected by the PulsIn command.  A 200ms pulse causes a bit to be set, otherwise it is left untouched. 

So take, for example, the year data stored in the Year variable. Information about the year is transmitted (MSB first) during seconds 17 – 24 inclusive. The data for 2014 would be stored as $14 or %00010100. During seconds 20 and 22 a 200ms pulse would be transmitted causing bits Year.4 and Year.2  to be set. The pulses relating to all other bits would only be 100ms in duration.

Once all the time and date information has been collected all subsequent data is ignored until second 54 is reached. At this point, and until second 57, parity error data is collected. The data collection process is identical to that described above except that a 300ms pulse is required to set any bit in the CalChkSum variable.

At the end of second 59 the process begins again.  However this time, because the Flag variable bit has been set, parity bits for the time and date data collected will be generated. These are then compared with those received during the previous minute. If the two agree, then the RTC is updated. If this is not the case, the RTC remains unchanged.


Finally

A couple of points worth noting. Firstly, if you're going to power the clock from the mains using a low voltage adapter (wall wart), be careful not to use one of the switched mode types. These create a lot of electrical noise which makes life difficult for the MSF receiver. Secondly, and for the same reason, testing the clock near a computer is not a good idea.



More information about the MSF time signal can be found here:-

          https://www.npl.co.uk/products-services/time-frequency/msf-radio-time-signal/msf_time_date_code

and here:-

          http://en.wikipedia.org/wiki/Time_from_NPL

Amazingly, the compiled code only takes up 886 bytes, a tribute to Proton's efficiency I suggest. It also leaves plenty of room to add additional features if you so wish!
 

'****************************************************************
'*  Name    : MSF Radio Clock                                   *
'*  Author  : Bob Marshall                                      *
'*  Date    : 03/01/2014                                        *
'*  Version : 1.0                                               *
'*  Notes   : Compiler Version 3.5.6.2                          *
'*          : The purpose of this program is to decode and      *
'*          : display the RF time signal from MSF Anthorn, UK.  *
'*          : A Symtrik SYM-RFT-60 module is used to receive    *
'*          : the 60kHz signal and a 16F628A employed to decode *
'*          : and display both the time and date on a standard  *
'*          : 16*2 LCD. Long wave  RF  signals, such as         *
'*          : those from Anthorn, are  sometimes  subject to    *
'*          : interference  which  can  cause an erroneous      *
'*          : display. In this version of the program correctly *
'*          : decoded time and date information is used to      *
'*          : update a DS1307 RCT chip every second. Updating   *
'*          : the RTC so frequently is hardly necessary, but in *
'*          : this case there is little else for the PIC to do. *
'*          : Of  course  the update  frequency  could be       *
'*          : easily altered to suit other applications. The    *
'*          : displayed time and date are read from the RTC.    *
'*          : This has the advantage that when the RF signal is *
'*          : corrupted or missing, the displayed information   *
'*          : remains correct.                                  *
'*          : The MSF protocol employs a simple form of parity  *
'*          : error checking. This is used to determine if the  *
'*          : time and date information is good.                *
'*          : No effort is made to decode the DUT1 (the         *
'*          : difference between atomic and astronomical time)  *
'*          : data.                                             *
'****************************************************************

;-------------------------------------------------------------------------------
;**** Added by Fuse Configurator ****
; Use the Fuse Configurator plug-in to change these settings

    Device = 16F628A

    Config FOSC_XT, WDTE_OFF, PWRTE_ON, MCLRE_OFF, BOREN_ON, LVP_OFF, CPD_OFF, CP_OFF

;**** End of Fuse Configurator Settings ****
;-------------------------------------------------------------------------------

    Declare Xtal = 4

    Declare LCD_Interface = 4
    Declare LCD_DTPin PORTB.4
    Declare LCD_ENPin PORTA.0
    Declare LCD_RSPin PORTA.1
    Declare LCD_Lines = 2
    Declare LCD_Type = 0

    Declare SDA_Pin PORTA.3
    Declare SCL_Pin PORTA.2

    Symbol ClockPin = PORTB.3
    Symbol DS1307 = $D0

    Dim DataIn As Word
    Dim DataVal As Byte
    Dim BitPtr As Byte
    Dim Flag As Bit
    Dim ChkSum As Byte
    Dim PCnt As Bit
    Dim CalcChkSum As Byte
    Dim Temp As Word

   ' These variables are used to collect incoming MSF time data.
    Dim Year As Byte
    Dim Month As Byte
    Dim DayOfMonth As Byte
    Dim DoW As Byte
    Dim Hour As Byte
    Dim Minute As Byte
    Dim SecCnt As Byte

    ' These variables are used to store the time from the RTC.
    Dim Yr As Byte
    Dim Mon As Byte
    Dim DoM As Byte
    Dim Day As Byte
    Dim Hr As Byte
    Dim Minit As Byte
    Dim Sec As Byte

    CMCON = 7   'All digital = true

    GoTo _Main
'******************************************************************************
    CalcParityBit:
    ' Check to see if the number of 1s is an odd or even number.
    ' PCnt = 0 indicates an even number of 1s.
    ' PCnt = 1 indicates an odd number of 1s.
    ' End loop when no 1s are left to count.
    ' Invert PCnt to produce correct parity bit.
    PCnt = 0
    Repeat
        If Temp.0 = 1 Then Inc PCnt
        Temp = Temp >> 1
    Until Temp = 0
    PCnt = ~PCnt
    Return

'******************************************************************************

    _Main:

    Cls
    Print "-*-MSF  Clock-*-"
    DelayMS 3000
    Cls
    Clear

    While
        DataIn = PulsIn ClockPin,High
        DataIn = DataIn/100
        Select DataIn
        Case  475 To 550 'Start of minute marker
            SecCnt = 0
            If Flag = 1 Then
                'Year parity
                Temp = Year
                GoSub CalcParityBit
                CalcChkSum.3 = PCnt

                'Day parity
                Temp.Byte0 = Month
                Temp.Byte1 = DayOfMonth
                GoSub CalcParityBit
                CalcChkSum.2 = PCnt

                'Day of week parity
                Temp = DoW
                GoSub CalcParityBit
                CalcChkSum.1 = PCnt

                'Time Parity
                Temp.Byte0 = Minute
                Temp.Byte1 = Hour
                GoSub CalcParityBit
                CalcChkSum.0 = PCnt

                If ChkSum = CalcChkSum Then
                    BusOut DS1307,0,[0,Minute,Hour,DoW,DayOfMonth,Month,Year]
                    Print At 1,16,"U"  'Indicates the DS1307 has been updated.
                                       'Included for diagnostic purposes. Remove
                                       'if not needed.
                Else
                    Print At 1,16,"E"  'DS1307 NOT updated due to checksum error.
                                       'Included for diagnostic purposes. Remove
                                       'if not needed.
                EndIf
            EndIf
            Year = 0:Month = 0:DayOfMonth = 0:Hour = 0:Minute = 0:DoW = 0
            ChkSum = 0:CalcChkSum = 0:Temp=0:Flag = 1

        Case  75 To 150   'AB bits = 00
            Inc SecCnt
            DataVal = 0
        Case  175 To 250  'AB bits = 10
            Inc SecCnt
            DataVal = 1
        Case  275 To 350  'AB bits = 11
            Inc SecCnt
            DataVal = 3
        EndSelect

        Select SecCnt
        Case 17 To 24
            BitPtr = 24 - SecCnt
            If DataVal = 1 Then SetBit Year,BitPtr
        Case 25 To 29
            BitPtr = 29 - SecCnt
            If DataVal = 1 Then SetBit Month,BitPtr
        Case 30 To 35
            BitPtr = 35 - SecCnt
            If DataVal = 1 Then SetBit DayOfMonth,BitPtr
        Case 36 To 38
            BitPtr = 38 - SecCnt
            If DataVal = 1 Then SetBit DoW,BitPtr
        Case 39 To 44
            BitPtr = 44 - SecCnt
            If DataVal = 1 Then SetBit Hour,BitPtr
        Case 45 To 51
            BitPtr = 51 - SecCnt
            If DataVal = 1 Then SetBit Minute,BitPtr
        Case 54 To 57
            BitPtr = 57 - SecCnt
            If DataVal = 3 Then SetBit ChkSum,BitPtr
        EndSelect

        BusIn DS1307,0,[Sec,Minit,Hr,Day,DoM,Mon,Yr]
        Print At 1,1, "Time: ",Hex2 Hr,":", Hex2 Minit,":",Hex2 Sec
        Print At 2,1, "Date: ",Hex2 DoM,"/",Hex2 Mon,"/20",Hex2 Yr

        DelayMS 350
    Wend

OG

NPL links are being changed.
The correct link at the moment.
https://www.npl.co.uk/msf-signal
Let's copy the content here.


Accurate and reliable time

The MSF radio signal is a dedicated standard-frequency and time broadcast that provides an accurate and reliable source of UK civil time. It is available 24 hours a day across the whole of the UK and beyond. The signal operates on a frequency of 60 kHz and carries a time and date code that can be received and decoded by a wide range of readily-available radio-controlled clocks.

The MSF signal is transmitted from Anthorn Radio Station in Cumbria by Babcock International, under contract to NPL. The signal covers the whole of the UK, and can also be received throughout most of northern and western Europe. It is monitored against the national time scale UTC(NPL) and corrected when necessary, ensuring that the transmitted time is always correct.


Technical information

Find out more detailed technical information about the MSF time code, signal strength and carrier frequency accuracy.
MSF signal technical data
msf_time_date_code.zip


MSF signal outages
The signal is occasionally taken off-air to allow maintenance work on the masts and antennas at Anthorn Radio Station to be carried out in safety. A radio-controlled clock will not be able to pick up the MSF signal during these periods, so may drift off from the correct time.

MSF reception difficulties

The main causes of reception problems are local interference from electrical equipment and a reduced local signal due to screening by nearby metalwork, for example in a steel-framed building. If your radio-controlled clock is having difficulty receiving the MSF signal, please first read through the information in the 'Common clock problems' document.

Common MSF signal reception problems
msf-reception-problems.zip


Forthcoming scheduled maintenance periods
The shutdowns will take place between 10:00 and 14:00 BST in June and September, and between 10:00 and 14:00 UTC in December. The duration of each outage period will be kept to a minimum, and the signal may be back on-air prior to the times given above.

In addition to these dates, the signal is likely to be taken off-air for a two-week period during summer each year, though the transmission will be restored overnight whenever possible. The dates of this longer outage will be announced on this page and by emailed notices to registered users as soon as they are known.

The dates and times of the 2020-2021 maintenance periods are as follows:

28 April to 13 May 2020 – work completed early and service operating normally from 4 May

12 March 2020 from 10:00 to 14:00 UTC

11 June 2020 from 10:00 to 14:00 BST
 
10 September 2020 from 10:00 to 14:00 BST
 
10 December 2020 from 10:00 to 14:00 UTC
 
11 March 2021 from 10:00 to 14:00 UTC
 
10 June 2021 from 10:00 to 14:00 BST
 
09 September 2021 from 10:00 to 14:00 BST
 
09 December 2021 from 10:00 to 14:00 UTC



charliecoutas

A nice piece of coding Bob.

Charlie

top204

#3
An excellent piece of Coding Bob. I thought they had stopped the MSF clock a while back, did't it used to be called the Rugby time signal?

I built a clock using a LW (Long Wave) TRF receiver back in the 1980s that fitted onto my ZX81, so I could decode the signal. :-) Showing my age now, but I was only a young lad at the time. LOL


charliecoutas

Les, was your BBC LW "clock" decoding the phase shift on the 198khz signal? I tried this several times and failed.

Charlie

top204

Crickey Charlie, now your asking something I can barely remember. LOL

It wasn't MW frequency, and was, in my opinion, VLF (Very Low Frequency), but it was classed as LW (Long Wave) of about 60KHz. If I remember rightly, it was pulsed Frequency Shift Keying and I had to write the code in Z80 assembler for the ZX81's tape cassette "in" socket. :-)

I wrote similar codes to speed up the cassette saving and loading on teh ZX81 and the ZX Spectrum and it made them more reliable. Good times. :-)