A week or so ago I downloaded the latest version of K1JT's WSPR software. It has a few interesting features including a facility to set your transceiver's frequency using computer control and a way to compensate for any frequency readout inaccuracy - important when you are working within a sub-band only 200Hz wide. The process involves measuring the error at various frequencies by tuning 1.5KHz below stations of known accuracy and measuring the frequency of the heterodyne. The program will then calculate and apply the correct offset for each amateur band. However a better solution if you don't mind opening up the case is to adjust the master oscillator in the transceiver so that the readout is spot-on in the first place.
I did this first with the K3, which was easy because the master oscillator is adjusted digitally using a menu. I then decided to calibrate my FT-817ND. The reference oscillator is accessed by removing the top cover. With the radio facing towards you it is on the left hand side. The trimmer you need to adjust is shown by the arrow.
I don't have the optional TCXO module which is rather expensive, but at shack temperature the standard oscillator seems pretty stable. However, the calibration adjustment is very touchy. The tiniest hint of movement can change the transmitter frequency by as much as 10Hz at 10MHz.
I tuned 1.5KHz below WWV on 10MHz and then adjusted the trimmer so the audio frequency of the heterodyne was measured as 1500.00Hz. Adjustment was an iterative process. The audio frequency might be 1497.35Hz, then I'd nudge it up to 1497.85Hz, then the next time it would go up to 1505.43Hz and I'd have to start nudging it back again. This went on for some time, getting within a fraction of a Hz and then overshooting by several Hz in my attempt to get it spot on and having to start again. I probably spent over an hour on this and was getting a bit frustrated by the end of it, but eventually I got to within 0.15Hz which is probably as good as you can expect with an FT-817ND.
The audio frequency is measured using the computer sound card, which is not a calibrated device, and I wondered if errors in the sound card clock frequency could make this calibration method invalid. I asked about this in the WSPRnet forum and Joe, K1JT replied: "If the crystal oscillator controlling your soundcard's sample rate is off by, say, 100 ppm then your measurement of a 1500 Hz audio tone's frequency will be off by 1500 * 100 / 1000000 = 0.15 Hz. It's a pretty lousy crystal oscillator that is off by more than that. There are many ways to test your soundcard's sample rate. All of them boil down to measuring a supposedly known audio frequency. One good method: put your radio in AM mode and use WSPR's "Measure an audio frequency" button while listening to WWV, during one of the periods when they broadcast a standard tone."
I can't receive WWV that well here and I have never heard it broadcast a continuous audio tone, so for the time being I'll accept Joe's assurance that my soundcard is unlikely to be out by more than the degree of precision that I'm able to adjust the reference oscillator to anyway.
2 comments:
Hi Julian, Yet another interesting item on your blog!
My opinion, as (now retired) former Head of Laboratory at British Telecom Electrical Standards Laboratory maintaining standards for test equipment used by BT in the UK.
You were fortunate in being able to set your master oscillator to 0.15Hz at 10MHz, which is an accuracy of 0.015ppm (parts per million). The specification for stability of the FT-817 after warm up at 25C is 1ppm per hour - you will probably find it is better than this but not better than 0.1ppm/hour. Indeed, the more expensive option TCXO-9 is specified at 0.5ppm/hour. You were trying to achieve an accuracy of around 1 part in 10^8 (0.01ppm) which can be achieved with professional test equipment but at a cost over the price of consumer electronics equipment like the FT-817. Then how long will it keep to this accuracy? If you take the spec literally this would be 36 seconds, but even at 0.1ppm/hour this works out to 6 minutes.
The Yaesu spec should ideally include contributions for temperature coefficient, supply voltage and ageing of the crystal oscillator in the FT-817. You can't do much with the first two parameters, but at least with the last one you can compensate for it. Now you have set it to "nominal", repeat you test after a month and see how far it has drifted. Don't be surprised if it has drifted 10Hz, after all that is only 1ppm. Do not adjust it yet, leave it another month and see if the drift is repeatable. Assuming it is, then readjust the oscillator so that it will drift towards nominal during a month (or whatever period you choose) and then, after twice this period, it should have drifted the same amount the other side of nominal. Now is the time to perform the adjustment again!
This is the technique used for calibration of frequency counters used by BT technicians while I still worked there.
This sounds quite involved, but I wouldn't like you to think that once you have achieved the accuracy of 0,15Hz at 10MHz it will actually stay there!
Regards Maurice G4DVM.
Hello Maurice. Thank you for taking the time to contribute this comment. It is very illuminating. I think we all tend to think that having taken the trouble to tweak our rigs down to a fraction of a Hz that they will stay there, at least once warmed up. It isn't immediately obvious, until it is pointed out, that a stability of 1ppm means a potential error of 10Hz at 10MHz - quite significant in terms of WSPR operation - and a whopping 140Hz on 2 metres, which is very significant if you're looking for weak beacons using a narrow filter.
I found the stability of the FT-817 to be quite good. Once set it tended to stay within +/- 0.15Hz of the frequency. I think the long term stability isn't bad either. In fact when I started it was less than 10Hz off at 5MHz, and it had never been calibrated since it left the factory several years ago.
However I now have renewed interest in the availability of the option to lock my K3 to a frequency standard!
Post a Comment