Showing posts with label TCVCXO. Show all posts
Showing posts with label TCVCXO. Show all posts

Monday, July 23, 2012

TCVCXO PCBs Received

I just received another set of boards from OshPark.com.

This time they are my corrected TCVCXO boards. The board will provide a Temperature Compensated, Processor I2C Corrected, 10MHz Master Clock for the Propeller Microcontroller (see previous post).

Top Side
Back Side
This board is 0.34 x 0.5 inches with 0603 components. If you click on the microscope photos above, the resulting image will be about 400 times actual size.

 I should have it loaded with parts within the next few days.

--

Wednesday, July 4, 2012

Under the Microscope

Cutting Under the Microscope
I think I have past a personal milestone on my forever quest to build ever smaller projects.

I noted the passing, when I realized it was much easier to cut-out my paper models of a new small PCB under the microscope.

The scissors look like huge shears under the microscope.

This new TCVCXO board is required due to pin mounting hole miss-alignment (my error) on the previous PCB. This time I am using the cut-out TO MAKE SURE it is correct.

Alignment Conformation
A straight pin pushed through the holes ensure hole alignment. The fifth pin is at an odd, non-standard location and has caused me trouble.

Note: for scaling, the protoboard holes are 1.0mm in diameter and on 1/10 inch centers.

The paper cut-out now confirms the new PCB layout

This paper image is the same that I would use to create a Homebrew Toner Transfer PCB (if that was my goal) but for this board I will be using the service of OshPark.com (again).

The five Crystal Pin Sockets (see previous post) are installed and ready to receive pins from the new TCVCXO board.

Pin-Sockets Installed
I took this pin-move opportunity to shrink the TCVCXO board even smaller, it is now only 0.34 X 0.5 inches, which is smaller by about 25 percent.

I do enjoy making projects as small as my abilities and eyes allow.

The two bottom Pin Sockets supply I2C Signals (jumper wires will be added on the back side), the next two Pin Sockets supply GND and 3.3Volts (the Propeller board already has them connect to VDD and VSS), and then the new TCVCXO board supplies its 10MHz output to the single Pin Socket (upper Center) to the Processor Crystal Input. The Processor multiplies its input by eight, to supply its internal required 80MHz clock frequency.

The sixth pin socket shown in the photo (upper right) is one of the the standard 5MHz Crystal sockets, which will not be used with the 10MHz TCVCXO board installed.

This is a proven circuit, I am just trying to get the final implementation right.

--

Tuesday, July 3, 2012

Part Quest

Crystal Pin Sockets
Several days ago, I received my order for Crystal Pin Sockets (see previous post) and have not had time to use them yet. I have been busy working on some projects, and trying to get ready for Salmoncon.


The smaller Crystal Pin Sockets will be used in Propeller Projects, Homebrew PCB Projects, and the larger (longer) ones will be used in Manhattan and Ugly Style Projects. The 2-Pin Header and the single Machined Pin/Post are shown for scale. The crystal leads will be cut to length as necessary for the project.

The Stash
These are by far the smallest mechanical devices in my bag of project parts. And, they are probably the most expensive per weight, at $0.20 each they are several times the price of GOLD. But, . . I only need a few :-)


The first photos shows several styles and sizes that I have obtained. The smaller ones are the style that I had in mind for my initial Part Quest, they fit into 1mm plated holes, and do not protrude much beyond on the backside of the PCB. Others were some initial trial parts.

--

Wednesday, June 20, 2012

Part Quest

I have been trying to find the part number of the Crystal Pin Socket for the Propeller. I want to use similar pin sockets for my small add-on Huff-n-Puff TCVCXO daughter board (see previous posts).

My daughter board was designed to fit existing holes on the Propeller Protoboard. Three of the five pin (holes) already have the correct Voltages/Signals present ( +3.3v, GND, and Xtal Input), only the two I2C lines will be jumpered as necessary.

Use of the very short Crystal Pin Socket will allow for a very low daughter board profile. In the past, I have used salvaged machined DIP socket/pins that stood up about 1/10 inch above the board, their hight make the daughter board a little wiggly.
Crystal Socket - H3153-50
http://goo.gl/NrRrf

I asked the folks at the Parallas Propeller Forum if anyone could provide the exact part number that was used in production. Several user suggestions were provided, and then with a lot of minuet specs comparing, I think I have found an acceptable part - I now have several on order.

Only receipt of the order will confirm. Note: the photo suggests the part is longer than its specs (perceived aspect ratio) . The part fits into a 1.0mm hole and its over all length is only 3.61mm. The Pin Socket accepts a 0.51mm wire pin, similar to those found on small crystals, at 0.47mm dia (measured).

This will be a great (but very small) part to be added to my collection, for this and future projects.

I enjoy chasing/tracking down "small and interesting" parts for my projects. I have blogged about many other parts in the past, maybe it is an expression, or a long lost need, of a "hunter/gatherer". I may make this a re-occurring theme on my blog - Part Quest.

--

Monday, June 18, 2012

TCVCXO PCB Received from OshPark

I received my TCVCXO PCB back from OshPark.com (see previous post) This board with be used with the Parallax Propeller as a Crystal replacement. It is a Tiny board, only 0.365 x 0.650 inches (0.062 inch material). The PCB layout for this project was created using the DipTrace Schematic Capture and PCB Editor.

I attempted to take photos with the same origination as the previously posted 3D models (which proved to be more difficult than I thought :-) Here is the results. More "Light" is needed - I think I would like to build a "photo shoot light box" for taking future photos.

Top Side

Bottom Side


Now it is time to load and test this thing.



UPDATE:
OK, now I am envious, I just read Dave Richards -AA7EE,  post of his gorgeous Photos of the Air Variable Capacitor. Thanks Dave, I learned a few things!

UPDATE:
Dang! . . . I got the pin hole alignment wrong, I need to re-layout the board, again  :-(

--

Sunday, June 10, 2012

Prop UI Progress

It has been a grueling 18 days since my last post. The Propeller UI Board that I have been working on has provided some real challenges. All of the UI Board peripherals on wired to the same I2C Bus. Which means my standard method of debugging the code via a working a Display was not available. The Bus Pirate and a new VGA Display was necessary, which had to be configured which added to a already steep learning curve.

UI Board Installed on the Prop ProtoBoard
Coordinating and developing the Objects for the six UI peripheral was a challenge The task was a little easier thanks to Jeff - KO7M, who helped with the I2C Bus to Parallel Expander Code, and the necessary modification to his I2C LCD Driver.

Currently ALL six UI peripherals, which are on the same I2C Bus, are working in concert with each other without perceivable delays for; the two Rotary Encoders, four Push Buttons, eight LEDs, a Realtime Clock (RTC), and the LCD Display. Also there are the Sound (beeper) and the three I2C POTs that control the LCD Backlight Brightness, LCD Contrast, and Sound Volume - all working seamlessly together.

One of the Software Driver Goals is make moving the Programmed Display from LCD to VGA (and back) without difficultly, other than the obvious which are the Number of Lines and Number of Characters Per Line.

Note: my new I2C Huff-n-Puff board (see previous blog) will also be added to that same I2C Bus (external to the UI).

I had to learn a few new Propeller SPIN tricks to make it all work. Specifically how to coordinate and use "Locks" for Objects and COGs.

Only a few modifications were necessary to the UI PCB. I have already started the re-design with modifications for the next PCB. I will be adding more Pull-ups, and 0-Ohm Jumpers to make separation of circuits easier for future development and debugging.

I have several ideas and better organization of the current code, but that will wait for another day.

It has been a lot of fun. Now on to some projects that will use the Prop UI Board.

First, on the list to port are; my QRSS and WSPR Beacons, Jeff's Keyer, the Huff-n-Puff Freq Standard, and several other Prop Projects that are planned to use the new UI.


--

Tuesday, May 22, 2012

New TCVCXO PCB with OnBoard I2C Control

With the very good results of the TCVCXO Propeller Master Clock experiments (see previous post), I decided to rebuild the PCB to include the I2C Pot and Filter Caps on the same board. This is the expected results when produced:
Top
Bottom
Note: This board is very small, it is only 0.365 x 0.650 inches. The above images are local screen prints of DipTrace 3D output.

I often use Homebrew Tone Transfer Method to produce my PCB's, but I use DorkBotPBX to produce my manufactured boards.

Laen (the owner of DorkBotPBX PCB) is now using a new web site: OshPark.com and using a new interactive process for submitting PCP designs. The new web site was introduced at the Bay Area Maker Faire 2012.

The site accepts Eagle and Generic ZIP'd Gerbers (as exported from DipTrace). The interactive process receives the ZIP'd file and renders the design, showing the individual layers and what the board will look like when finished (in Laen's standard Purple color). Very Cool.

The price is the same, $5.00 per square inch for a set of three, two sided boards.

Check it out at: OshPark.com

--

Wednesday, May 16, 2012

The Results Are In

 . . . . I think.

Last night I took my Huff-n-Puff driven Master Clock for the Propeller Microprocessor to Jack's Homebrew Amateur Radio Meeting, to compare it with his GPS Disciplined 10MHz Standard (see previous post).

Jack had problem getting his equipment ready, the 10MHz Standard was questionable and he had not built the Phase Comparator/Detector as of yet. We proceeded anyway to look at his and my 10MHz signal on his Dual Trace Scope.

I had previously miss-adjusted my TCVCXO to a slightly lower frequency, so that we could watch the Huff-n-Puff circuit in action. Jack's 10MHz signal was connected to one Scope Channel (and driving the Sync), my signal was on the second channel.

With the Huff-n-Puff still turned OFF, it was obvious that my signal was  marching across the Scope screen, right to left (indicating a lower freq). We waited a short period to allow my GPS to be acquire it's satellites, and then I turned ON the Huff-n-Puff function.

Like magic my Scope signal slowed down its march across the screen as the Huff-n-Puff derived TCVCXO correction voltage was being applied. The I2C POT displayed value went from 0 (wiper center) to +12 in about 45 seconds. After a little more settling, it stopped on +14, the two 10MHz signals were almost the same, But not perfect.

At this point Jack's Standard was still suspect, because we could not verify that it was working with the internal GPS receiver and in Sync with the satellites. We were not familiar with the computer program that provided information and therefore unsure. We were just going to assume that it was working.

Jack did not have his detector built, so we did the next best thing. We put the the scope in "Signal Add" mode, so I could count the "in and out" of phase condition by observing the screen.

With Jack's stop-watch, I counted 50 nulls in 141 seconds:

50 / 141 / 10M = 0.0000000354 => 35 ppb

At his point, the best that we could do was; state that we were close in Frequency, by 35 ppb (parts per billion) or 35 x 10^-9 (I think I have the math correct).

This morning I received an email from Jack, stating that he has learned more about his Standard and its operation, and now he thinks his 10MHz Standard was probably working with the GPS and therefore we can assume it to be correct, or within reported/stated accuracy In either case, we will do the experiment again, maybe next month.

If our initial results are correct, then my Huff-n-Puff has Out Performed my expectation by 15 ppb, as suggested on my previous post were I had calculated 50 ppb.

I am a happy camper :-)

I really should rename this circuit, because it is NOT a traditional active/passive Huff-n-Puff circuit, it is mostly in Software (with only a small computer controlled POT). Maybe, I should  call it a: Software Defined Huff-n-Puff - or SDHnP !

With this configuration I should be able to provide very accurate WSPR and QRSS signals - That is the GOAL.



UPDATE
The method used to compare the standard with my TCVCXO did not take into account the direction (sign) of the drift between the two, and therefore the "absolute" frequency may be better than the reported 35 ppb. About half of the time my TCVCXO signal appeared to change directions relative to Jack's Standard. More experiments and some research is necessary to understand what was observed.

--

Monday, May 14, 2012

More Huff-n-Puff

I have been working several days, trying to get my Huff-n-Puff circuit to properly control the TCVCXO Oscillator, which is used as the Master Clock replacement for my Propellers.  When I started the experiment, I thought for sure it would be an easy task.

The plan was, to use a one second square wave from a GPS to compare with timing from the Propeller, the output would drive an Double Gang RC circuit, and that would provide a DC voltage to steer the TCVCXO to make the output Frequency as accurate as the received GPS. My goal was to use only passive components.

It worked, but much less than optimal.

For the Passive RC circuit to work correctly, components would have to be optimized:
  • for RC filtering
  • for low input impedance for the Charging Circuit
  • for high output impedance to avoid Discharge
  • yet, for low output impedance to provide drive to the TCVCXO
There were just too many things to consider while trying to make them all work during Startup and Stable Run conditions. I got just enough working to validate the Huff-n-Puff goal, but this circuit was not going to be successful.

To continue this approach, active components would be needed.

My new plan was to introduce two OpAmps, one to sample-n-hold the output from the comparator, a second to provide drive for the TCVCXO. This circuit could be contained within one chip, but I really did not want to build it.

Yet, another approach.

While working with another project (my UI) I had planned to provide control of the Backlight and Beeper Volume via a I2C POT. A simple I2C command sets the POT wiper value - sweet !

The I2C POT that I planned on using was a MCP4018. Late in the UI design and after ordering some parts. I noticed that you can NOT have more than one MCP4018 on a single I2C Bus (What?? only one I2C address??). I had to change the design to Quad I2C POT MCP4441, which contains 4 POTs, plus the chip provides address pins so as many as eight can be used on a single I2C circuit - very nice. My UI circuit design was modified.

Now, while thinking about my Huff-n-Puff problem, it came to me that I could replace all of the above planed active OpAmp circuits with just one MCP4018 I2C POT, that would be controlled by the Propeller (I only need one POT for this test). The POT has wiper value storage and the proper output impedance to drive the TCVCXO, via a simple RC and resister divider circuit (similar to the original passive circuit, but smaller values). The comparing, filtering and tracking will all be done in software - easy to do.
CircuitLab

The new I2C POT Huff-n-Puff was installed, and checked with the Bus Pirate. A little change to Propeller SPIN code (and I2C driver) was all that was needed to make the circuit work! The I2C driver needed to be modified because, the MCP4018 does not use internal Register addresses, only one address byte followed by one data byte.

Success

It is now fun to watch the I2C POT adjust the voltage on the TCVCXO to correct the Frequency of the Propeller's Master Clock, and then continue to stay locked onto the GPS. The I2C POT wiper's numerical position is displayed on the LCD.

Tomorrow night I plan to take this new circuit to Jack's Amateur Radio Homebrew Meeting where a Frequency Standard is available and can be compared. I hope this all works as planned. If my calculations are correct, my Propeller Master Clock should now be within +/-50 ppb of GPS Standard Frequency.

I do not expect this effort will do anything to correct inherent PLL jitter, it will only improve the Output Frequency Accuracy.

--

Thursday, April 26, 2012

Gremlins In the Prop

Several weeks ago, I built a Power Amplifier (PA) for my Propeller 30m Beacon (at 10.140MHz). I was a little reluctant to put it on the air, as I did not know the output characteristic and the effectiveness of the included Low Pass Filter.

Jeff - KO7M brought over his Spectrum Analyzer so we could look at the output. Harmonics were well below requirements and that was very good news.

But, during the inspection we noticed that once in a while the PA appeared to jump into low level oscillation, and some how it was associated with the make-shift connection to the Propeller board. The oscillation only happened once in a while.

I (some what) expected this to happen, as the PA was built to be a wide band amplifier with only some filtering on the output. Oscillation (Gremlins) can easily occur on untried designs. According to the Analyzer, the Oscillation was NOT on the Frequency of my Beacon (10.140MHz), but at slightly lower unknown frequency.

I was a little bummebed out, as it meant that I needed to rework my faulty (guilty) PA design to provide some neutralization. That would have to wait for another day.

Now, A Few Weeks Later

The last few days I have been building and attempting to characterizing a new set of Low Pass Filters (see previous post). The Filters are intended to be connected directly to the Propeller board via a cable and SMA connectors. Again, with the loan of Jeff's Spectrum Analyzer the task was made easy. The Filters passed with with flying colors.

But Then, . .

On occasion, a very Low Level signal appeared on the Analyzer between RF transmissions, and near (slightly lower) the intended test 10.140MHz signal that I was using for the experiment. It appeared only about 50% of the time, and after an RF output. It was measured about 15db above the noise floor on the Analyzer.


But Then, . .

When the above signal was not present, and looking closer (at the same high gain setting) an even lower level signal was always present. It was measured at about 3db above the noise floor.

I assumed it was hash being picked up by the connecting wire around and from the Propeller Processor.



But Then, . .

It only was observed after tests were started, that is, after the first RF transmission. It was NOT observed just after Propeller power up and before the first RF signal was produced. Note: the photos were taken with the same configuration for each.


And Then, . .

It occurred to me that, maybe the RF output Pin was Leaking !

To check it out, . .

I changes the RF signal Frequency to 7.030MHz.

But No, . .

The Propeller was not leaking at the set RF frequency, the leak was higher, near the previously observed 10MHz Frequency.

What is going on, . . ?

In the transmit program code, we traditionally turned on the PLL Oscillator by setting the intended Frequency. And then, to turn off the output, we just set the frequency of the PLL Oscillator to Zero, as per the Propeller Object Library suggestion.


                                
pri sendTone(tone)
  Freq.Synth("A", RFPin, Frequency + tone)

pri noTone
  Freq.Synth("A", RFPin, 0)


This has always worked well in the past, or at least we thought so. Maybe we had never looked close enough at the output.

I changed to code to; just turn on-and-off the output pin, and leave the Synth (oscillator) running between transmissions, and only executing the Synth command as necessary (if Frequency changes).



VAR
  Long PrevF

pri sendTone(tone) | F
  F := Frequency + tone
  if F <> PrevF
     Freq.Synth("A",RFPin, F)
  PrevF := F
  dira[RFPin]~~  'set for output

pri noTone
  dira[RFPin]~   'turn off output


And the Results, . .

It worked, no observable leakage!

I now suspect that the open output pin allows the Master Clock (at 10MHz) to leak at very low levels at the pin. Maybe a product of clocking the Propeller COG in which the program is running.

And So, . .

The previous suspected problem with the PA oscillating, was NOT actually a problem at all. The PA was just doing what it does best, it was amplifying the small Leaking Master Clock of the Propellers.

Problem solved!

The code will be changed on each of my Propeller Programs.

My Prop and PA can now be put back in service as a 30m QRSS, WSPE, and OPERA Beacon without, out-of-band concerns.

With restored faith in design, I can move on, and produce a proper PCB to replace the now acquitted PA circuit.

--

Tuesday, April 24, 2012

30m Low Pass Filter Results

Here are the measured results of the 30m Low Pass Filter (see previous post).

Here is the Propeller Output without a Low Pass Filter. The tall center signal is the Spectrum Analyser's LO, the Propeller 10.140MHz signal is to the right of the LO, and the negative images are seen on the left side. The third and fifth harmonics can be easily seen, odd harmonics are typical of a square wave output.

Without LP Filter
And, here is the Output with a Low Pass Filter

With LP Filter

Here is the Propeller and Low Pass Filter test configuration.

Prop and Low Pass Filter

--

Monday, April 23, 2012

More 30m Low Pass Filters

Today was again, Low Pass Filter Day.

I built three 30m Low Pass Filters to use with the Propeller as the Keyer and RF exciter. Previous filter builds included a DC blocking Cap to avoid DC loading the Prop, but a Low Pass Filter should not include elements that prevent Low Frequency signals to pass even if they are not wanted. DC blocking should come before the LP Filter on the Prop.

My previous built filter were a little flimsy, they were built on .031mil PCB material, components in line with the axes tended to crack and stop working. For these board, I used .064mil PCB material.

The circuit I am using was calculated via the CalculatorEdge online service (there may be other online calculators that would work as well, but this is the one that came up first in Google search).

The Calculator suggested the following, which became (=>) the available parts used.
  • Two Inductors 594.4nH => 680nH as hand wound (I could have been more precise here, but, . . .  :-)
  • Two End Caps  1086.5pF => 990pF (3 - 330pF)
  • Middle Cap 1416.1pF => 1320pF (4 - 330pF)
30m Low Pass Filter
I updated the circuit on my CircuitLabs Workspace, and ran some plots with the slightly different component values that I have available. The second harmonic rejection is reported as down -45db.

Down -45db at 20MHz
The results:
30m Low Pass Filters
I am going to use SMA connectors for all of my projects now, thanks to Jeff - KO7M I had enough connectors to complete two filers. More SMA Connectors and Jumpers Cables are on order.

One of the above Filters will be sent to a friend.

--

Monday, April 16, 2012

TCVCXO Six Hour Stats

In preperation for finish building Huff-n-Puff Circuit, and then running the Huff-n-Puff TCVCXO Spin Code on the Propeller, I have been running some Master Clock Frequency Stability and Accuracy data collection code in monitor mode and displaying the statics.

The displayed Frequency Error is computed as; the clock count form the desired 80M clocks, per 1 second pulse from a GPS. The percentage reflects; the direction, and magnitude of over a sample period. For this test the sample period is 6 hours.

Note: the resolution from the clock counter within the Propeller when compared to the GPS second pulse is 16Hz, this maybe a function of my particular GPS or the clock count function of the Prop. Regardless, the error is recorded as; ERROR/16.

After about 12 hours of data collection, the TCVCXO stats indicates about +6% X 16 cycles per 80M clock cycles, or an error of;

16 x .06 / 80M => 12 x 10^-9 
or, 12 parts per billion

The intent is to install the Huff-n-Puff circuit and then note the same stats.


Is this necessary?      No, . . but it is fun to see what frequency accuracy and stability can be obtained with simple hardware!  :-)

--

Tuesday, April 3, 2012

TCVCXO Boards Received

Yesterday, I received my TCVCXO PCB back from DorkbotPDX (15 days). These will be used as a stable replacement for the Master Clock on the Propeller USB Protoboard (see several previous posts).






HB 10MHz TCVCXO Propeller Daughter Boards


With a little work two boards were; loaded and initially tested. Jeff - KO7M will receive the second board for his Prop.







Ready to Load Parts


The board size is a little over 0.4 x 0.4 inches, and is made for 0603 and 0805 components. This new board was created to plug into existing hole on the Propeller USB Protoboard.

And of course, More testing is yet to come (although the Homebrew prototype has been doing well, and has be used in my 30m Beacon for the last few weeks).


UPDATE
Jeff and I have used the TCVCXO sucessfully with our Protoboards, the only difficulty is I miss located the third (single) pin on the PCB, it is slightly left of the of its intend spot.  This mistake makes the board sit slightly crooked on the Protoboard. But, the hole-to-pin slop allows correction (while soldering) for most of the misalignment. The alignment will be corrected on the next boards.

--

Saturday, March 31, 2012

More Propeller Projects

I plan to attempt to use the Propeller for both LO and BFO for a small receiver. Jeff put me onto a neat little receiver which is just begging for experimentation. The Propeller can produce multiple RF signals simultaneously, just as needed for the receiver. More information can be found on this single conversion superhetrodyne receiver kit from N3ZI

But, I am diverted to yet another project, to build an even more accurate Frequency Source for the Propeller Master Clock. The TCVCXO that I built using the Homebrew circuit board has been doing very well in all experiments. It occurred to me that if it was connected to a GPS one second tick, it could be steered to even more accuracy.

So far, only initial plans are in place, with some circuit diagrams and example code.

The strategy is to implement a Huff-n-Puff circuit and support Propeller SPIN code to "drive" the Voltage Control Pin with corrections - Results: A GPS Disciplined Frequency Master Clock.

Google: Huff-n-Puff Oscillators

Actually, this is all experimental, and I do not really know what to expect. But, this is what I have at present.


https://www.circuitlab.com/circuit/8bt74u/prop-tcvcxo-huffnpuff/


The following is a code snippet from my current GPS ISR Object (has not been tested).



PRI Huff_n_Puff | C, PrevC
  PrevC := 0
  Trend := 0

  dira[GPSPin]~              ' Set for Input, and Float high via Pullup 10K Resistors

  repeat
    Trend #>=  10
    Trend <#= -10
    pause(80 * ||Trend)    'Pause should be less than ~900ms
    dira[HnPPin]~          'Set Tri-state Mode

    waitpeq(0, 1<<GPSPin, 0) 'waiting for CPS SEC Pin to be LOW
    waitpne(0, 1<<GPSPin, 0) 'waiting for CPS SEC Pin to go HIGH

    C := cnt
    CountError := C - PrevC - CLKFREQ
    PrevC := C          'Save for next iteration

    if(CountError > DEAD_BAND)
        Trend #>= 0
        Trend--
        IF( HnPEnabled)
            HnPStat--
            outa[HnPPin]~     'Huff - Make Pin LOW
            dira[HnPPin]~~    'Output Mode

    elseif(CountError < -DEAD_BAND)
         Trend <#= 0
         Trend++
         IF( HnPEnabled)
             HnPStat++
             outa[HnPPin]~~    'Puff - Make Pin HIGH
             dira[HnPPin]~~    'Output Mode

    else
         Trend := 0



The intent is to "drive" the Voltage Control Oscillator (TCVCXO) to match the GPS. The RC time constant of the Huff-n-Puff circuit above, along with the Program logic should only gently correct the output Frequency.

What I expect for output is a square wave (at HnPPin), varying duty cycle depending on correction needed.

Obviously, more development and testing is needed.

Please comment, if you have experience with this sort of thing.


UPDATE
I found the following interesting page: http://www.rt66.com/~shera/index_fs.htm


--

Wednesday, March 21, 2012

Proposed OS Freq Standard

I have an idea for an Open Source Project, but first some background, . .

Background

Dave Jones of EEVblog fame, is designing and building a very neat Open Source Power Supply, if you are not familiar with his project check it out at his Blog. His other blog enteries describe some of his design, process, and trade-offs. It is a very interesting project and I for one, will be ordering at least two when they are available.

If you are a reader of the blog, you will know that I have been experimenting with the Parallel Propeller Micro Processor (Prop) for use as a Amateur Radio Multi-Mode Beacon. The Propeller has within is the ability to generate RF square waves that I use to drive my Beacon. This Frequency can be set to any frequency from 500Hz to 120MHz. But there is a bit of a problem with the "stock" Propeller frequency synthesizer; it is not very stable or accurate. In my quest to solve this problem; Jeff - KO7M and I ( and with some help from some of my readers) hit upon the idea of using a TCVCXO for the system clock. Initial experiment suggest the Beacon frequency can be made to be very stable and accurate.

Last night at Jack - WA7KMR's Homebrew Meeting; we discussed Frequency Standards and the relative size, resolution and stability of some of the equipment that Jack had collected over the years. We also discussed feedback loops to increase accuracy and stability.

After getting home late, and after turning off the lights, my brain tuned on.

Most readers of this blog can always use more test equipment - right?. Therefore, . . .

My Proposal

An Inexpensive Open Source Variable Frequency Standard, based on the hardware design of Dave Jones's Power Supply; using the same case, battery pack, input voltage regulators, LCD display and push button layout. And using the TCVCXO and Propeller Micro Processor for control and function of the Frequency Standard.

  • Use the TCVCXO for the master clock of a Variable Frequency Standard
  • The Prop could select the source for the output, either a straight divide by N circuit, or an output from the Prop synthesizer.
  • The display could indicate the frequency and source.
  • A GPS input could be used to phase lock and adjust the already +/-2 ppm TCVCXO to much-much tighter tolerances. The Prop has these functions built-in.
  • The Prop would detect and display the TCVCXO and GPS phase error.
  • Feedback from the Prop to the TCVCXO (via filters filters) would adjust as TCVCXO as necessary.
  • The device would be small, battery powered and portable.
  • Multiple Frequencies can be produced simultaneously, on different output connectors.
  • And, relative inexpensive.

Jeff's and my initial work with the TCVCXO was with his Frequency Standard, but it only had a few decade switch selectable frequencies available, I think the Prop can provide much more flexibility.

I know there are many High Accuracy Time Standard hobbiest, and this would not qualify in that category. The expected Stability and Accuracy that can be expected is still debatable and untested, but I think the idea is worth pursuit for a bench source.

Dave Jones has done some great work; his generic input power supply and charging circuit, the case selection and layout, display and controls, are just begging for additional creative devices. I suspect his Open Source equipment form factor and layout will become a Standard, and it will become known as; The Platypus.

My Proposed Variable Frequency Standard would be an Open Source Project based on The Platypus.

Note: there are other similar projects on the web: Google, Open Source Frequency Generator

I am looking for feedback.

What say you?


--

Sunday, March 18, 2012

Prop WSPR

I think my 250mW 30m Propeller Beacon has covered North America, except a few stations around Seattle. My Beacon has NOT been received by Jeff - KO7M, about 35 miles away. I guess, there is just not enough ground wave. The stations as shown in the screen print, reported within the previous 3 hours.

WSPR Reporting Station - Previous 3 Hours

--

Friday, March 16, 2012

Measured Success

After installing the Homebrew PCB with the 10MHz TCVCXO Frequency Standard Clock on the Propeller, I finally got it connected to an Antenna as a WSPR, QRSS and OPERA 200mW Beacon.

The results are amazing, the Frequency is measure as very Stable and the Frequency is measured to be as set.  The reporting site, and measurement that I trust the most is W1BW (Operated from ARRL HQ);  they report Zero Hertz Drift and at the desired frequency of 10.140210MHz - exactly as I have programmed the Beacon.

Note: Not only does the TCVCXO provide for a stable and accurate RF frequency, but it also provide accurate scheduling for the Beacons. WSPR requires scheduled transmittion on two minute boundaries, starting the actual beacon two seconds (+/-1) past the minute. This Propeller Beacon is on-time, every time :-).

Also, the three beacons run in quick succession, that is: WSPR starts on a two minute boundry (runs for 2 min), followed by QRSS on the top of the next minute (runs for about 3 min), followed by OPERA on the next minute (runs for about 2.2 min). Then all repeats 10 minutes later. The 10 minute schedule allows the QRSS beacon to be displayed at the same place within the 10 minute remote Grabber captures.

I am receiving many reports (spots) from around the US, no DX yet, but the night is young.
My WSPR on the Map
Note: the W1BW report (at 3939 km) in the following list (click to view).
My WSPR Spots - as Reported by WSPRNET.org
Also, the following was reported by the KK7CC Grabber, note the frequency scale, which is out side of the normal QRSS Subband, I had to pick a frequency to allow my signal to show up on his Grabber. I picked 10.139930MHz, KK7CC reports the same !

My signal is the lower trace with Propeller graphic and my Call in slash code.

My QRSS on KK7CC Grabber - Las Vegas

I am a Very Happy Camper !!   :-)



UPDATE
New DX report at 7049km with only 200mW:

TimestampCallMHzSNRDriftGridPwrReporterRGridkmaz
 2012-03-17 03:54  WA0UWH  10.140204  -24  -1  CN88xc  0.2  WA2YUN  RK39hh  7049  270

And, Two more:

TimestampCallMHzSNRDriftGridPwrReporterRGridkmaz
2012-03-17 10:04  WA0UWH  10.140208  -14  0  CN88xc  0.2  VKFRG  QF44np  12766  244 
 2012-03-17 10:04  WA0UWH  10.140199  -26  0  CN88xc  0.2  VK4TMH  QG56fj  11758  252


--

Thursday, March 15, 2012

TCVCXO Boards Are On Order

After a few slight modification, I just placed an order with DorkbotPDX for the 10MHz TCVCXO circuit boards. This is the board that will be used for the Propeller Clock (see previous posts). They should be in my hands in two weeks plus a few days.

Gerber File

Note: The boards will not be Green, DorkbotPDX boards are a very nice Purple !

--

Wednesday, March 14, 2012

Prop TCVCXO PCB

I have been watching/testing the 10MHz TCVCXO that I installed to replace the master clock on the Propeller (see previous posts). The stability is better than I had hoped, but the installation was NOT as good. I just soldered the TCVCXO onto the Propeller Protoboard where pads were available, but spacing was not optimal as solder bridges where necessary to make it fit. It was a jury-rig just to do some initial test.

Now that I had time to think about how it should be mounted, I decided to build a small PCB to hold the the parts; TCVCXO, by-pass cap, two fixed resistors, a variable tuning resistor, and a output cap.

Schematic on CircuitLab
Keeping with my on-going project goal, I wanted it to be as small as my ability allow. The results was a PCB that is 0.453 inches by 0.492 inches. The circuit will stand on three legs/pins which insert into mating sockets. I installed the sockets on the Prop Protoboard using existing holes, which provide 3.3v, ground and the clock input.

If the TCVCXO can not to be used, or if I want to use the original crystal, it can be re-inserted. Only the three pin-sockets were necessary and they can be abandoned.

DipTrace Layup
I will have the board made by a commercial PCB vendor, but for a quick test, I resorted to my tried-and-true Toner Transfer Method.
Circuit at Different Stages of Toner Transfer
I made more than one copy, Just in case Murphy was Watching

Components Loaded and Ready to Install
Some things just looks Ugly, when you get TOO close.
The TCVCXO PCB,
Two Fixed Resistors and Pot in Foreground
10MHz TCVCXO Center
Two Cap's in at the Far Edge
Using the board, is just a matter of changing the clock parameters and plugging the TCVCXO in.
TCVCXO Installed on the Prop Protoboard
It Sets Just Below the Edge of the LCD
I was easy to do, and it works GREAT!

--