A Simplified GPS-Derived Frequency Standard By: Bertrand Zauhar, VE2ZAZ Published in the September/October 2006 issue of ARRL's QEX Magazine

INDEX

INTRODUCTION ORIGINAL QEX ARTICLE GPS-STANDARD MAILING LIST COMPONENT PROCUREMENT ERRATA AND IMPROVEMENTS USER COMMENTS AND END RESULTS USER MANUAL Montrol SOFTWARE FOR WINDOWS MAKING YOUR OWN PCB LEARNING / PROGRAMMING THE FIRMWARE ADDITIONAL ASSEMBLY INSTRUCTIONS & HINTS COMMENTS ON FLL PARAMETERS COMMENTS ON STABILITY AND ACCURACY COMMENTS ON GPS RECEIVER BEHAVIOR TTL-RS232 CONVERTER REFERENCES DESIGN BACKGROUND Page last updated: 01/11/2020

This page complements article "A Simplified GPS-Derived Frequency Standard" published in the September/October 2006 issue of ARRL's QEX magazine. This page also provides updates to the original article.

Please visit this page frequently, and right before assembling the project, as new information will get added regularly. There is also a mailing list that you can subscribe to to stay updated. See details below.

For those who have not read the article yet, this is the best place to start learning about this project. Reproduced with permission. Copyright ARRL, 2006 all rights reserved. This material originally appeared in QEX: Forum for Communications experimenters (www.arrl.org/qex). Please report any broken hyperlinks to me. Thank you.

A simplified GPS-Derived Frequency Standard QEX Magazine Sept/Oct 2006

• The 0.1uF capacitor I specified (478-2472-ND) from Digikey is now discontinued. Please order 478-3188-ND, , a RoHS-compliant equivalent.
• The 1uF capacitors can be replaced with 478-3195-ND, a RoHS-compliant equivalent.
  
• The Bi-color LED (MV6461A-ND) is obsolete. You can use Digikey part 160-1058-ND instead.
• The Green LED can be substituted with Avago HLMP-1540 (516-1301-ND) or
  Panasonic LN38GCPX (P607-ND, minimum qantity is 10).
• The LTC1485 (LTC1485CN8-ND) can be replaced with LTC1485CN8#PBF-ND, a RoHS-compliant equivalent.
• It has come to my attention that Dual operational amplifier OPA2705 may be hard to get. A good substitute available at Digikey is LMC6482 (Digikey part LMC6482AIN-ND). In fact, you can substitute the OPA2705 with a dual operational amplifier that offers the following characteristics:
• It must tolerate the supply rails you will submit it to (0 to +5V or -5V to +5V, depending on the OCXO to control).
• It must be of the Rail-to-Rail input and output type, otherwise you will lose some tuning range. A LM358 is not a good choice because of this.
• It must be able to drive the equivalent capacitance of the OCXO tuning input pin. In case an oscillation is seen, a 1K resistor added in series with the Tuning Output voltage should dampen any oscillation.
  
• It must (of course) have a DIP-8 package and have the same pinout.

To help in generating a Digikey order, I have created an .xls spreadsheet file with all the electronic components required to assemble the board. You will be able to import this file directly into the Digikey website and generate an order. I cannot guarantee that all the components listed will be available when you order; you may have to find substitutes. But it is still a good starting point. Insure that you remove any of the components that you already have and/or don't need to order before submitting the final order. An example is the non-programmed PIC18F2220 micro-controller which you may remove if you don't own a PIC programmer...

GPS_Std_Digikey_ BOM_Feb2011.xls

• An Alarm Latch clear push-button feature which allows to clear any latched alarm without having to log on to the system via RS-232C. Grounding pin 22 momentarily will clear the alarm latch.
  
• A 10MHz/5MHz OCXO rate selection based on the state of pin 21. High (default, floating) state is 10MHz, Low (grounded) state is 5MHz. Selection is made at power up only.
  

• I have only run basic acquisition and lock test with a 5MHz oscillator. I did not perform long term accuracy measurements so I cannot provide any indication on the level of performance obtained. I have every reason to believe that it will work well though.
  
• The output sub-rates will be 2.5MHz and 500KHz, which are odd frequencies from a frequency standard's perspective.
  
• Some software parameters will have to change for optimized performance. The user will have to experiment. An example, for a known Averaging Cycle Size (S), accuracy will be less; this is obvious since the measurement resolution of the system becomes one pulse in 80,000,000 instead of one in 160,000,000. A longer Averaging Cycle Size (S) will compensate though.
• I will make no modifications to existing documentation. Wherever you read numbers such as 10MHz and 0x6800 (26624 decimal), you should instead read 5MHz and 0xB400 (46080 decimal) if you are using a 5MHz OCXO.

• Jacques, VE2AZX, was the beta-tester for this project. He did a pretty good job of integrating the system into an existing HP 5328A frequency counter with a built-in HP 10544 OCXO. Jacques provides this info along with some small mods/improvements to the PCB and some system spurs and stability analysis in one zip file available on his website. Thanks Jacques!
• Jeremy, AD7MK led their class project at the Idaho State University. They decided they needed a better standard for their lab, so they procured the PIC micro and PCB. After project completion, they ran their standard against a commercial-grade GPS standard (NIST-traceable) and were impressed with the results. See their webpage.
  

I wrote a comprehensive user manual that describes VE2ZAZ's GPS-derived frequency standard. Topics such as detailed system description, hardware and firmware setup, serial port strings and commands are covered in the manual. This document is a must if you are looking for the information on how to put together the "Simplified GPS-Derived Frequency Standard".

GPS-derived Frequency Standard USER MANUAL - Ver 1.1, April 2013

I also wrote a Windows program that provides a more user-friendly interface to the GPS_Std Frequency Standard system. The software provides the following features:

Window-based program with main toolbar and multiple windows, Full Monitoring and Control of the GPS_Std PIC firmware, All parameters read or written in decimal, Serial port logging of system status string for future analysis, Integrated DAC plotting feature that graphs the DAC value as a function of time. Statistics window with average offset, standard deviation and min/max values computed.

GPS Standard MonTrol Software for Windows Version 4, April 2009

This software was developed and tested in a Windows 98 environment. It was also tested in Windows 2000 and Windows XP. Since these operating systems cover two main branches of Windows (9x and NT), the software is expected to run in all Windows environments from Windows 95 through Windows XP.

Note to users: In order for Montrol to send a new Parameter value to the PIC, you must enter the parameter value in the numeric field and then press the <Return> key. A Parameter readback will confirm that the PIC took the new value.

Version History

Version 4 (April 2009): This version corrects a minor display problem found in the Montrol software statistics window. Under certain circumstances, abnormally small but non-zero Current and Accumulated Average Frequency Offset values may display.

Version 3 (July 2008): All statistics displayed were previously computed assuming a 10MHz oscillator. Now detects when a 5MHz OCXO is used and calculates the stats accordingly. Serial ports COM5 to COM8 are now supported. The Plot feature is now much improved.

Version 2 (September 2006): Corrects an access violation popup window problem that may show up when trying to change the COM port using the "Config" button.

Version 1 (September 2006): Initial Release.

MAKING YOUR OWN PCB

For those of you who would like to make their own GPS_Std Frequency Standard system PCB, here are the top layer, bottom layer and top silkscreen layers saved in .PDF format. The document prints on Letter-size paper. When printing in full size (no scaling), the size and proportions should be accurate.

GPS_Std_Layout_v1.pdf

• This PCB can be made of double-sided copper clad glass-epoxy materal. A thickness of 0.062 inch is typical.
• The copper patterns reside on the PCB top and bottom sides.
• The board layout is designed so that signals jump from layer to layer using component pins. The user shall solder all components and wiring on both PCB sides in order to allow signals to jump.

LEARNING ABOUT AND PROGRAMMING THE PIC FIRMWARE

If you would like to look at the firmware load running inside the PIC micro-controller, well here it is! The ASM file is a text file of the source code I wrote. Beware! This is Assembly language...The code is well documented though. Have fun... ;-) I also provide the latest HEX file required to upload the firmware load into the PIC 18F2220's program flash. This file is in 8-bit Intel HEX format, which is the industry standard for 8-bit micro-controllers. In order to accomplish the firmware upload, you need a PIC programmer that can handle the PIC 18F series chips. Firmware Version History GPS_Std v4 (18/03/2009): This firmware release adds a couple of nice-to-have features: An Alarm Latch clear push-button feature which allows to clear any latched alarm without having to log on to the system via RS-232C. Grounding pin 22 momentarily will clear the alarm latch. A 10MHz/5MHz OCXO rate power up selection based on the state of pin 21. High (default, floating) state is 10MHz, Low (grounded) state is 5MHz. No change to the FLL functionality is made here. Since this firmware version creates a "universal" PIC able to work on both 10MHz and 5MHz systems, I will no longer be distribuing a 5MHz firmware version. Those who wish to use a 5MHz OXCO must ground the PIC's pin 21 to enable the 5MHz mode. See the Additional Assembly Instructions section below. GPS_Std v3 (12/09/2008): Microchip have added a defect in their latest chip errata that affects newer batches of PICs.  This bug will hold the chip in reset unless the power up delay feature is turned off (configuration bit CONFIG2L, bit 0). This bug is seen on chips with date codes greater than 0813 (2008, 13th week). So a new firmware is required to be fully compatible with the newer batch of chips. The firmware change is also fully backwards compatible with previous batched of chips. GPS_Std v2 (25/08/2008): Fixes a problem occuring on PICs programmed for the 10MHz OCXO frequency. The issue only affects the Voting mode. The Summing mode does not exhibit the problem. This faulty firmware will cause the DAC to over-correct the OCXO frequency, which will lead to a significant offset from nominal frequency or could prevent the FLL from locking. Note: Those who used the v1 file previously downloaded form this site do NOT need to perform the upgrade to v2, as the bug was introduced by mistake at a later date than the v1 file originally posted here. GPS_Std v1 (September 2006): Initial firmware release.

GPS_Std Firmware.zip Version 4, March 2009

• The 7805 voltage regulator should be mounted with its case "grounded". A small TO-220 heatsink should be inserted between the PCB and the regulator case. A good example of a suitable heatsink is Digikey's HS107-ND. A small bead of heat-conductive paste should be applied to both surfaces.
• LED D1 and D2 locations do not have any pin marking showing proper orientation during soldering. Here is how the LEDs should be mounted:
  
• D1 should have its green diode anode soldered to the pad closest to resistor R3. For Digikey's MV6461A-ND, this is the longest lead. This orientation will make D1 come on as red-flashing-off at power up (assuming a valid 1PPS signal is fed to the system).
  
• D2 should have its anode soldered to the pad closest to resistor R9. For Digikey's MV5477C-ND, this is the longest lead. This orientation will make D2 come on as green at power up.
• Need a -5V supply? Do you use a MAX-232 TTL-to-RS232 conveter chip in the system? Here is an easy way to generate a -5V supply for the filter stage operational amplifiers U5A and U5B. Tap off the -10V charge pump supply from the MAX-232 TTL-to-RS232 conveter chip. Pass it through a 79L05 voltage regulator, Voilà! The amount of current available is limited though. Since the operational amplifiers' quiescent current is much less than 1mA, this leaves us with a few milli-amps of current to drive the VCXO. Check that the VCXO input tuning pin draws little current, a couple of milliamps maximum. Otherwise, the RS-232 negative voltage level will sink. This is not a problem with the HP oscillators since their tuning voltage input has an impedance of greater than 100K ohms.
• Low-voltage GPS Receivers: One user reported problems locking his 10MHz OCXO to a GPS receiver. The system would remain permanently in Holdover state, with wildly varying frequency samples as opposed to the more typical 26624 (0x6800) value. It ended up being an insuffucient voltage swing on his Motorola M12M's 1PPS signal. Always make sure that the PPS swing of your GPS is of TTL-grade with at least +4V on the high state, otherwise add some buffering. A NPN/PNP tansistor pair in cascade is a good way to restore the required swing for the PIC microcontroller.
• Alarm Latch Clear Pushbutton: In order to use the Alarm Latch clear push button feature introduced in the v4 firmware, a momentary SPST, normally open push button must be wired between PIC U4-pin 22 and any ground point in the circuit. No pull up resistor is required as there is an internal one assigned to the pin. Momentarily pressing on the pushbutton will clear any latched alarm. Of course, if the system is in Unlocked state, this action will have no effect.
• 10MHz / 5MHz OCXO frequency selection: Beginning in the v4 firmware, it is possible to switch to a 5MHz OCXO frequency instead of the more common 10MHz. A connection of U4-pin 21 to any convenient ground point must be made for 5MHz selection. By default, when the pin is left unconnected, its state is high and the 10MHz frequency is selected. No pull up resistor is required as there is an internal one assigned to the pin. The pin state is sensed by firmware only at power up. Toggling this pin during normal operation will have no effect.
  

The bottom line accuracy is the result of several factors. The two most important ones are GPS 1PPS accuracy and VCXO stability. We know that the worst case accuracy of the 1PPS is 10^-6. In practice though, short term GPS 1PPS accuracy is more like 10^-7. Obviously, the longer you integrate the 1PPS GPS signal for, the better the accuracy will be. But the drawback of this is that the longer the integration time (averaging cycle), the more the VCXO will (or might) drift. Of course, the better the VCXO, the more stability you will get. But the overall bottom line system accuracy equation is challenging to specify, let alone quantify.

I have measured on several occasions my system going into the low 10^-11 and even high 10^-12, but it did not stabilize there. Eventually, the VCXO drifted or the 1PPS pulled it away from there. I have made observations over several months, and concluded that the 10^-10 decade (from 10^-10 to 10^-9) is a reasonable expectation from this system. Trying to shoot for better than this range would mean stretching the integration time to an impractical duration. Other disturbances like holdover and power outages would constantly interrupt your averaging cycle and make the FLL more or less useless. I found that an averaging cycle of a few hours is a good compromise. I guess it is like everything else in life: A good balance is the key!

Another contributing factor to stability/accuracy is voltage regulation as a function of load current on the +5V regulator. A +5V variation will impact the PWM output amplitude on the PIC micro. It will also impact the offset applied to the operational amplifier to shift the tuning voltage negative in the case where you control a VCXO with a -5V to +5V tuning range.

The single biggest contributor to load variation on the 7805 regulator is change to the 10MHz output terminations. I have seen variations of a few parts in 10^-10 when disconnecting instruments form the system. The workaround to this (assuming this variation affects you) is to always put 50 ohm terminations on unused outputs. When adding an instrument, remove the BNC termination and connect the instrument. This will maintain a nominal current consumption on the output driver chip. Obviously, you will want to set the controller so that the outputs are always on. Other current consumers, such as the LED, the input driver and the decade counter do not affect stability in a meaningful manner.

There is no doubt in my mind that some things could have been done differently to improve performance. I could have used an external DAC chip, I could have used an external voltage reference, I could have split the supplies with two or three regulators, and so on. This might have improved stability somewhat and would have made the board bigger and more expensive to put together. The original goal though was to keep the design as simple as possible, while still achieving 1x10^-9 or better accuracy.

That being said, those of you who operate a tuning voltage from -5V to +5V (and this is the case with the HP oscillators) - should try to center the tuning voltage at or close to 0V. It can be mathematically demonstrated that this is where the effects of the +5V voltage variations cancel out. For applications that require a 0 to +5V tuning voltage, obviously, the closest to 0V, the better.

• There is a large frequency deviation (sudden unexpected frequency increase) caused by a spurious slow down of the 1PPS GPS frequency. This kind of deviation occurs once or twice per day, on average. Note that frequency deviations in both directions are seen on the Garmin GPS-25 / 35 1PPS signal.
  
• The GPS-Derived Frequency Standard software must reject the frequency samples during this large deviation, otherwise the whole averaging calculation will be erroneous. This is where the FLL Holdover states becomes useful!
  
• Not considering this large deviation, the sample-to-sample frequency deviation stays roughly within +/-5 of nominal frequency (26624). This is considered to be regrouped. Medium-to-long averaging cycles should yield good system accuracy.
  
• The plot should give the user an idea of what value to assign to the Holdover limit parameter H. For this example, a Holdover Limit H ranging from 6 to 8 should provide good imunity to these spurious deviations, while still letting all good samples through.

• Unlike the GPS-25 / 35 GPS, there is no large frequency deviation caused by a spurious variation of the 1PPS GPS frequency. With a GPS unit like this one, it is less critical to have a Holdover limit parameter H set quite tight compared to the sample-to-sample deviation spread.
• On the Motorola Oncore GT+ GPS , the sample-to-sample frequency deviation stays roughly within +/-16 of nominal frequency (26624). This is considered quite spreaded. With such a GPS receiver, for statistical reasons, a short averaging cycle is meaningless when trying to achieve optimal system accuracy. Only long averaging cycles will yield good accuracy.
  
• The plot should give the user an idea of what value to assign to the Holdover limit parameter H. For this example, a Holdover Limit H set to 18 or higher should provide good imunity to any unexpected spurious deviations.

• Maxim's MAX232 chip. Two channels, which are required for GPS_Std system and GPS board.
• PICList Website. Various easy circuits and links for TTL-to-RS-232 conversion.
  

DESIGN BACKGROUND

The project started with a wish to make a GPS-derived Frequency Standard based on frequency measurement, as opposed to phase measurement, which is more complex in terms of hardware. Hopefully, a simple micro-controller would do the trick.

In order to demonstrate the feasibility of such design, I build an instrument-based system controlled over GPIB using Labview, my all-time favorite control software. The figure below shows the instrument setup. Pretty quickly, it became obvious that it would work.

Selecting the right micro-controller was the next thing to do. I elected to use a Microchip PIC 18F2220. It had built-in synchronous counter incrementing and latching via external signals, exactly what I needed! Though it lacked a DAC, it had a pretty decent Pulse Width Modulator that could produce a variable DC output with a suitable external low-pass filter. It also had serial port support. I had all I needed to make this project a success.

Writing the firmware (software) was definitely the most tedious part of the story. All in all, I spent six months testing it, analysing the results, and increasing its functionality.

As a side activitiy, I designed a PCB to host the components, built a prototype to prove it. I also wrote a Windows software to monitor and control the system in a more user-friendly ashion. I finally wrote a user manual, a magazine article and this web page.

Honestly, the results are gratifying. I am quite happy with the final system. I hope you can sense the amount of perfectionism I put in that project.