Overview
From the original RE to the latest version, these disciplined REferences have had the primary objective to be very low cost, accurate and high value devices for synchronizing amateur radio communications equipment. LF through VHF communications by way of the ionosphere has been a particular target. Design choices have consistently favored low cost above numerical performance as long as it exceeds that which is useful for these radio applications. These designs have proven themselves to meet these objectives well.
It has been suggested that v1 and v2 “under-perform” because phase noise is higher than other, more expensive, disciplined references that are commercially available. Because v2 does meet the original goals of the project to be very economical and work “well enough” for any foreseeable amateur radio LF–VHF uses involving the ionosphere, a ‘better’ version has not previously been offered. The total parts cost for that entire PCB, enclosure, and all other parts meet the goals well. Without US tariff penalties, projected total cost is < US$50 for small quantities and is deemed part of its “performance”.
Fundamentally, beyond the disciplining PLL’s bandwidth, a disciplined reference is no better than the local reference oscillator being disciplined. In v2 that was only a VCXO – currently costing only US$1.54. Using a low-cost GNSS module as the disciplining source, the possible bandwidth is quite limited. This is because internal algorithmic phase corrections performed by the module’s code inject small phase steps in the disciplining time pulse as that module’s local TCXO is kept synchronous with GPS time. “Time keeping” versions of GNSS modules which avoid these phase corrections are available but are either more expensive or require proprietary code. However, as described, for foreseeable and known LF–VHF communications applications there should be no discernible difference with this design compared to more costly solutions, except for its much lower cost and extended features.
What v3 adds
v3 is an increment of the v2 design. It does not meet the lowest cost, high value goals of the original v1 and v2 projects. Instead it also allows for internal or external OCXOs. This can easily double the total component cost. One improvement it can offer is stand-alone operation – operation not requiring a GPS antenna. While the most precise OCXO mode is disciplined by way of a frequency locked loop (FLL) to potentially provide sub-ppb accuracy, that too uses the GNSS constellation and module for discipline. However if a high quality (expensive) OCXO such as the HP10811D is used, once calibrated, it is possible to operate v3 for extended periods of time without GNSS required. For some amateur applications this could be a benefit worth the significant added component cost.
Even so, the v3 design may be produced without the addition of an internal OCXO. This moves the functionality back to that of v2 but keeps the possibility of using an external OCXO, if desired. The incremental component cost to build v3 rather than v2 is quite low so this design may be a preferred one for many builders. The KiCad files below already do not include one of two potential internal OCXO options so nothing need be done to build and assemble an “OCXO-less” v3. If an internal OCXO is desired, that would normally be provided separately and added at final assembly time. The Isotemp ocxo131-100 option might be purchased from eBay while the three components for the ECOC-9775-VC option would be purchased from normal vendors such as Mouser or Digikey. While raising the total cost of the OCXO option, providing the design in this manner makes the most economical version automatic while allowing the user to option-in the OCXO of choice, if so desired. It’s also possible to assemble the PCB with no VCXO or PLL components. If the result is only intended to operate with either an internal or external OCXO, this may also be a very cost effective option having quite good phase noise performance.
Features & Improvements
- May use either an internal or external OCXO to provide improved phase noise and long term stability
- Can operate apart from any GNSS connection – continuous antenna connection may not be necessary
- Provides up to 7 configurable user outputs, master clock for HF transceiver or SDR
- Common SDR and HF transceiver frequency presets
- Implements Continued Fractions algorithm for essentially perfect frequency accuracy
- GNSS satellite or local 10 MHz frequency reference
- Flexible supply 11–15 VDC
- Typically better than 0.1 ppb (0.00000001%) long-term accuracy and stability
- WiFi web interface – works with Windows, Apple or Linux systems
- OTA firmware update via web interface
Connections
- SMA: GNSS antenna
- SMA:External 10 MHz reference
- Seven SMA: user-selectable outputs 4 kHz to 200 MHz
- 2.1 mm power barrel connector
Construction
- Four-layer, through-hole plated, silk-screen printed PCB
- Split-case aluminum enclosure
Web Interface
Phase Noise Measurements
Two v3 REferences with internal Isotemp OCXOs
The first measurement below is of two v3 REferences each having internal Isotemp OCXOs installed and after 10 days of warmup. These have been set for 200 MHz, +13 dBm outputs from Clock2. These outputs drive the RF and LO inputs of a Mini-Circuits SBL-2 doubly balanced mixer.
The IF port of that mixer, acting as a phase detector, shows nearly constant slope – a triangule wave output – when the signals are offset from one another by 100 Hz. This offset configuration allows creating a reference carrier level at the input of a Behringer UMC202HD audio interface which is used to calibrate measured phase noise when coupled to an AudMes measurement tool set to Spectrum Analyzer mode and using 192 ksps clocking.
Assuming similar phase noise performance for the two, this would seem to indicate < −116 dBc at 100 Hz offset from the carrier at 200 MHz. This is equivalent to 26 dB lower noise, -142 dBc, when normalized to 10 MHz.
These measurements would indicate at 10 MHz about −142 dBc phase noise at 100 Hz offset when a well-stabilized REference v3 is used with an internal Isotemp OCXO.
Comparison with Leo Bodnar GPSDOs
The next plot shows the same measurement setup but with Leo Bodnar original two-output and “Mini” GPSDOs, each operating at 200 MHz, substituted for one of the Isotemp v3 REferences. This measurement is slightly more difficult to make because the limited PLL loop bandwidth and reduced low frequency loop gain of the Bodnar units (perhaps 15 Hz?) makes them incapable of rapidly following the GNSS module’s time reference, so that an overall “wander” on the order of 1 ppb (10 milli-Hz at 10 MHz) moves the phase detector inputs too far from quadrature over the time required for 5 averages when measuring at 200 MHz.
Even so, generally speaking and taken together, these measurements would seem to indicate that the Isotemp’s performance is more than 20 dB better for both noise and spurious signals compared to the Bodnar GPSDOs. Their coherent spurious and phase noise floors completely exceed and mask the Isotemp OCXO’s performance. It is to be expected that similar results would apply when a REference using only VCXO/PLL disciplining was being compared.
It should also be noted the normalized REference phase noise doesn’t appear to be identical at all selected Clock output frequencies or times. If a particular use requiring very high performance is contemplated, the noise at the candidate frequency should be verified.
Noting this, it should still be emphasized that the performance levels of all these Si53xx family references should be totally adequate for known or projected HF radio communications applications with any of these units.
Assembly Options
This project may be configured and optioned a number of ways.
Why you might choose an OCXO option
Choice of either OCXO option, internal or external, may have one or two potential advantages. Those are that the unit may be operated for significant periods of time without any satellite antenna connections and GNSS discipline at all without having negative effect on utility. For better OCXOs the long term drift can be so low that the errors don’t reach a point of impacting practical applications. Very infrequent connections to the GNSS constellation can allow the current best tuning value to be discovered and used as an OCXO ages.
Additionally, though not an original target of the REference project as a whole, the resulting spectral purity, both short and long term, from a quality OCXO may make one or more Clock outputs suitable as a basis for further microwave or even millimeter wave LO referencing. A clock might be used to phase lock a microwave or millimeter wave LO for frequency conversion in, say, a 24 GHz transverter.
Any of the above configurations may be decided on at fabrication time. It is only a matter of deselecting any unnecessary VCXO and PLL components to distinguish the results.
Material List
What you will need to build this hardware.
For better quick viewing of the design, download the KiCad file from the Material List below, unzip it and drop the .sch or .pcb file onto kicanvas from a web browser.
| Item | Provider / Download | Notes | Approx. Material Cost (excludes setup fees, tariffs, taxes, one-time charges, and shipping) |
|---|---|---|---|
| Assembled RE3 PCB and Front & Rear Panels |
KiCad files v3.1 (waiting for fab verification) |
A newer, not-yet-fabricated-and-tested version 3.1 is pending a test fabrication run. Use the ‘Production’ sub-directory to obtain .zip (Gerber), .bom and position.csv files for JLCPCB fabrication. | US$40 |
| 2 × 20-pin CPU socket | Adafruit | US$1 | |
| 38×88×120 mm Clamshell Enclosure & Front/Rear Panels | JLC | Other sources possible. Enclosure needs to accept 84 mm wide PCB. | US$3 & US$2 |
| CPU | |||
| RPi Pico 2W | RPi Pico2W with header | US$8 + shipping | |
| Arduino code |
|
Code also supports v2 and TR options. Select OCXO type in AAconfig.h. |
|
| Auxiliary programs | Python programs to plot FLL OCXO performance. | ||
Final Assembly, Test & Operation
Initial checks
After receiving the assembled PCB from fabrication and before final assembly with the CPU & socket, first verify with an ohmmeter that the power input line and the 5 V and 3 V regulator outputs are not shorted. Next, power the board from a current-limited or low-power 11–15 VDC source. Without the CPU, verify that only a few mA are flowing. The raw PCBs have already been pretested but doing this makes sure nothing has gone wrong during component assembly or soldering.
CPU socket
Final assembly and soldering of the CPU socket is next. Plug an RPi Pico2W into the socket to assure alignment, then mount everything on the PCB squarely. Solder the corner pins on the socket, making sure everything is flush and squarely aligned. Once the position is good, solder all the rest of the pin connections on both the PCB and the CPU.
Program the CPU
As received from the vendor, the Pico2W will have no code or perhaps a “Blink” sketch running. It will need to be programmed. As an alternative to full recompilation by the IDE, the precompiled .bin files appropriate to the HW option assembled, can be downloaded and then directly uploaded onto the Pico2W using its USB interface.
Full recompilation can be done by first downloading and installing
the Arduino
IDE. Once this is complete, the sketch for the reference may be
unzipped into its own directory. In the AAconfig.h tab,
if an OCXO is being used it should be enabled with a #define
so that suitable FLL code to support it will be included once the code
is compiled. Contact me for most recent Arduino sketch source code.
If compilng the code, be sure to always select Tools → Flash Size: “4MB (Sketch 2MB; FS:2MB)” to provide space for future over-the-air (OTA) code updates. Not compiling with this file space allocated will result in operation but not allow future OTA changes. Uploading would then be need to done via USB cable.
The first time it is attempted, selecting ‘Compile’ will result in some errors because additional libraries will be needed. These are satisfied one at a time by using Tools → Manage Libraries and installing each indicated by the error. When all have been installed, the code will successfully compile and be ready to Upload into the Pico2W by way of a USB cable. The Pico2W can be programmed without being plugged into the REference HW. When an Upload has successfully completed, the Pico2W may be plugged into the waiting socket on the assembled Reference PCB.
As long as Flash Size is always set to allow it, the web page access will permit OTA programming from this point forward, so the USB serial port connection will not be necessary for code changes and updates. However, code uploaded without this Flash Size setting may effectively “brick” OTA updates, and the unit will have to be opened so that serial port access can once again be used.
Once programming is complete, the REference may be accessed either through the IDE Serial Port or may be opened from a web browser.
First Web Connection
At this point again apply DC power and verify that the 3.3 V output is present and the CPU comes alive. LEDs should light and after a few moments it should now be web accessible. Prior to associating with a local 2.4 GHz WiFi AP, the unit will bring up its own AP with an mDNS address of the form “http:// RE2-**.local:8078/”, where “**” will indicate the last two characters of the MAC address. In addition to being shown on the Utility page, this IP and MAC address will also be output to the USB serial port as part of startup information. It should be recorded for use in the absence of a local WiFi AP, which will be the normal access route but could change if the unit is moved to a new location. If mDNS isn't available on the network, the WiFi router's page should show the address for new Pico2W Access Point.
Future Web Connections
Once there is a connection, the Reference may be configured with a local WiFi AP’s SSID:Password either from the serial terminal or from the Utility page, saved into EEPROM and used for all future access. This will allow complete access from within the users local network just like any other local device.
You can now slide the PCB into the clamshell enclosure and attach the end panels, but leave the top clamshell off until later.
From here on you can use the web page interface to preset the DAC via the Utility page so that the XO mode is nominally at the right frequency and ready to be disciplined by GNSS or Ext10 sources.
Provide either a GNSS antenna or else a 10 MHz reference and verify that when the corresponding disciplined mode is selected the unit shows LOCK on the Utility web page.
If you have compiled for use with either an internal or external OCXO, no pretuning is necessary since the firmware will calculate and store settings once GNSS timepulse is present the first time it is run.
From this point on, all configuration and monitoring can be done by way of a web browser. This includes OTA reprogramming of the unit’s FW from the Utility page, should that ever become desirable.
OCXO Support
Selections and settings as well as OCXO monitoring are all done via
the web pages. If the OCXO option was selected and either an internal
OCXO such as the Isotemp has been installed on the PCB or an external
OCXO such as the HP10811D is being used, that will have been chosen in
AAconfig.h prior to compile and upload. This will add an
additional FLL page where operation can be modified and monitored.
Once running, many OCXOs may require several days, or perhaps even a
month of continuous operation to reach a steady state condition of
maximum performance. In the case of very high quality OCXOs, it should
be possible to operate for very considerable periods of time, even
months or years, without any connection or use of the GNSS
disciplining. Once characterized and stable, long term drift may be so
small as to be unmeasurable in the context of ionospheric
communication applications.