Elecraft K3s DDS/PLL Induced Drift

I wasn’t very clear when I was posting about my pre-FMT calibration.  But I did describe that the K3s was not a particularly effective rig to use for a FMT.  This is because of how the digital synthesizer was implemented.  Even with the optional high-stability oscillator, which my K3s has installed, the issue remains.

The behavior is very evident in the Spectrum Lab screen capture below.  The K3s was fed a Rubidium based 10 MHz signal that is stable in the microhertz range.  The K3s is in CW mode with a 500 Hz Pitch selected , so we would expect it to produce a 500.000 Hz tone.

On the bottom of the illustration, in the waterfall area, the horizontal dashed lines are 5 minute interval time stamps, so we are seeing the variation in tone over a 15 minutes interval.  During that time, the DDS/PLL is performing a stair-step adjustment that is causing the tone to vary from about 501.2 Hz to 501.8 Hz.  One might describe this as 501.5 Hz, plus or minus 0.3 Hertz.

By the way, the older K3 would do exactly the same thing.  This is not a defect, as the K3s is working exactly as designed.  It was done to maximize dynamic range and minimize unwanted noise from the synthesizer.  The designer saw no reason to have its short term stability be better than +/- 0.3 Hertz.  For ham use, that is more than acceptable.  It is highly stable a longer term.  It will remain at 501.5 Hz +/- 0.3 Hertz for many days.

By the way, this is also pretty much what you can expect for Doppler on a 20-meter band signal anyway.  So the rig is just as stable as the ionosphere is in the short term.

Posted in FMT, Gear | Leave a comment

So Long OLD Friend!

And just like that, my 1980 vintage HP 3335A Synthesizer died this afternoon when I turned it on to get a better graph of my K3s PLL frequency hunting.  Dreaded “Unlocked” indicator and crazy display.  I have another that I’ve already cannibalized for parts, so there is some chance I can repair the one that was working.  But this also gives me an excuse to check out my Siglent SDG-2042X, which sports a 10 MHz external reference.  It all depends on how they implemented their PLL if it will be useful at the sub millihertz level like the HP was.  If the Siglent works, then I will pull the HP Oven controlled Reference out of both and eBay them.

Good timing, however, as I was able to use the HP to verify that everything was all set correctly prior to the FMT.  I will miss the old fella.

Posted in FMT | Leave a comment

Preliminary Results for April 2019 FMT

I was able to participate in the FMT last night (around 10 PM local time).  This was a pretty big deal for me, because I haven’t been in the basement that late at night since I was in the hospital last October (my equilibrium has been quite bad, especially at night, making the journey from basement to bedroom a challenge).

I was fumbling wildly with the Spectrum Lab settings during the initial call-up on 40-meters.  I thought I’d be able to locate my target tone (about 1000 Hz) quickly.  I wasn’t.  I finally got things locked in right as Connie K5CM went carrier down.

The results below are simply an audio analysis and don’t reveal my receiver dial frequency.  The audio frequency is either added or subtracted from the RX dial frequency depending on which side of the carrier the tone is received.

The image above is a screen capture from DL4YHF’s Spectrum Lab (Audio Signal Analyzer) taken during the 40-meter run (somewhere near 7.065 MHz).  You can see how the signal spreads out over the two minute key-down interval.  I saw a minimum of 1011.6762 Hz, and a maximum of 1012.240 Hz.  Visually I called the tone at 1012.03.  After mathematical analysis, it seems more like 1011.988 Hz.  The signal shifted over a range of 0.360 Hz (the actual frequency is somewhere in that noisy band).  I might “hunch” a frequency of 1012.20 if I believed I knew what Doppler was at that moment.  It will be interesting to see which of those three frequencies are closer to the mark (math=1011.99, eye=1012.03, hunch 1012.20).

The image above was taken during the 80-meter run (somewhere near 3.999 MHz).  I saw a minimum of 997.8961 Hz, and a maximum of 998.3294 Hz.  Visually I called the tone at 998.10.  After mathematical analysis, it seems more like 998.138 Hz.  The signal shifted over a range of 0.234 Hz.  I might “hunch” a frequency of 998.20 if I believed I knew what Doppler was doing then.  It will be interesting to see which of those three frequencies are closer to the mark (math 998.14, eye=998.10, hunch=998.20).

Results will be posted Sunday April 14 at 10 PM — Connie K5CM is that quick!

Posted in FMT | Leave a comment

Rig Instability and Calibrating for FMT

Back in the day, a superhet receiver, employed several mixer stages, requiring various oscillators, and a sometimes sketchy VFO (Anybody remember the Swan 753 — lovingly referred to as the Seven Drifty Three?).  That made for a real challenge when trying to accurately measure frequency.  All those oscillators drift at different rates (sometimes different directions).  No matter what the stability of your reference signal, within minutes things were moving all over the place.  Hertz-level measurements were about the best that could be obtained.

More modern gear started shifting to a single reference oscillator and deriving all other frequencies from that.  At least then everything drifted at a consistent rate.  Some of those 1980’s era rigs, like those made by RACAL or Watkins-Johnson, used very sophisticated digital synthesis and phase locked loops to produce a receiver capable of resolving a frequency on the display to a hertz, and yet were stable on a millihertz or microhertz scale.  Those receivers often allowed for an external 1/5/10 MHz oscillator; perhaps a Rubidium or Cesium standard to replace the internal reference oscillator (often a VERY expensive double oven based crystal oscillator).

Once ham gear started moving into the DSP era, was a simple task to have everything working off of one oscillator, and in fact many rigs do that (to save money, actually).  But several use one oscillator for reference generation, yet clock their DSP chips off independent oscillators which can cause some issues when converting the analog RF into the digital domain, then back in the audio domain for listening.  Even those that tried to keep everything tied together might have different design objectives for their digital synthesis scheme.

As a result, some rigs are not very stable on a millihertz or microhertz scale, yet are more than adequate for a human ear or decoding FT8.  An example of this is the otherwise outstanding Elecraft K3 line.   One can see the impact of the PLL causing a reference signal to appear to drift around by about +/- 100 milliherts in a staircase pattern that repeats every 5 minutes or so, but sometimes much wilder excursions of +/-500 milliherts happens too.  Nevertheless, K3s are used all the time in FMT with green band results (< 100 millihertz error).  I used my K3 as an AM detector by injecting a known carrier near the unknown signal to produce a beat tone.  Any PLL stepping has no impact as long as the passband is wider than the drift.

So a FMT purist would seek out a radio that would be stable into the microhertz range over long time periods.  Such a receiver is the RACAL RA6790/GM (1980 era superhet).  I’ve had mine turned on for a few days, locked to a Rubidium source, and monitoring a second GPS referenced Rubidium source.  Using Spectrum Labs, after calibrating the sound card, it has been providing a rock-solid reading of 300.00000 +/- 20 microhertz for the past day.  I deem my receiver more than adequate (by at least 3 orders of magnitude), so all errors will be due to operator error or inability to divine Doppler this Thursday.

By the way, prior to calibration, the sound card I was using (Behringer UCA222) was producing a tone reading of 300.02400 Hertz, off by 24 millihertz, or 80 ppm.  After calibration with +/- 20 microhertz wobble, it is more like 70 ppb.

Posted in FMT, Gear | Leave a comment

Getting Ready for April 12 FMT

The next Frequency Measuring Test (FMT) is scheduled for 0200 UTC on April 12.  For us East-coasters, that would be 10 PM EDT on THURSDAY.

I’ve just powered up my gear so it will be sitting in a stable for the next 6 days.  I still have to make the interface cable between my receiver and the sound card I will be using to do the Doppler observations and millihertz measurements using Spectrum Labs.

Equipment stack for FMT (top down): Fluke PM6685R Rubidium Standard, Racal RA6790/GM Receiver, HP3335A Synthesizer for local test signals.

Here’s the ARRL Announcement from the April 2019 QST:

Posted in FMT | Leave a comment

DMR 2 YSF Crossover

Having now gotten my DJ-MD5 working well on DMR, I figured it was time to up the stakes and see if I could use the DMR2YSF bridge feature.  Sure enough it works, although not fully yet.  It appears that the only YSF room that will work is the one you set as the YSF startup (in my case FCS 4-22, American Ragchew).  It doesn’t matter what DMR talkgroup you use on the radio — it just bridges over to the YSF room.  Folks on the other end will see your callsign, but there will be no indication of their call either on the dashboard or radio display.  They will also report that your audio is loud compared to a YSF radio, so speak a tad softer.

To get this working you must enable the DMR mode and DMR2YSF in Configuration.  Select whatever Startup YSF room you want from the YSF pick list.  Here is what my Dashboard looks like (Note DMR and DMR XMode are enabled and green, and DMR net and DMR2YSF are both enabled and green):

Here is what my Configuration looks like:

When NOT trying to bridge DMR to YSF, I would have the DMR Master set to “DMRGateway”.  Again, keep in mind that the only YSF Room that can be accessed is the one listed under the YSF Startup Host.  The original intent was to allow DMR radios to us a talkgroup to select the YSF room (TG 7100422 would select FCS 4-22, for example), but that feature is not operational at the moment.

Posted in DJ-MD5, DMR, YSF, ZumSpot | 5 Comments

160-meter WAS Certificate Received

Just a few days ago I used LotW to apply for my 160-meter WAS certificate.  I received it today (fast service, thanks ARRL!)

I was surprised to see a fairly low number (1667).  Hard to believe that 160-meter WAS is that scarce.  I checked on my 5-Band WAS, which was issued in 2014, and it was #3167.  One would assume that most folks with 160-meter WAS probably already have 5-band WAS, so only about half to on to complete their 160-meter WAS.  After putting in crazy hours on 160-meters the last couple of years, I can understand why.

Posted in 160-Meters, WAS | Leave a comment

Update on DMR and ZumSpot

Back in December, I wrote a post about my initial impressions of the Alinco DJ-MD5GP Type 90 approved DMR/Analog Dual Band HT.  With no DMR repeaters nearby (and only a couple in all of RI), I needed to use this with a ZumSpot.  I described my mostly failed attempts as well.  The problem I was experiencing was that one I selected a talkgroup, it seemed that it was always selected.  So if I picked North America, and later picked Rhode Island, then the North America selection remained active.  I was getting a lot of chatter that I didn’t want to hear.

A few months later, Scott K4SEH, commented to me that he was having no problem, doing exactly what I had tried to do originally (programming a single frequency/channel for my Hotspot, then programming a list of all the talkgroups I was interested in).

I finally had some time to give things another try yesterday.  First things first, I updated the ZumSpot software to the latest version, then changed over to DMR mode.  At that point, things started working exactly as I would have hoped.  Using the red button <List>, I would see my contact list (which is just a list of talkgroups), scroll down to the one I wanted, then press the green button to <Select> the one I wanted. That brings me to the “Option” menu, which I scroll down to find the “Select” entry.  A final press of the green button <Select> activates that talkgroup.

Can say for sure why it works now and did not in December.  My DJ-MD5 is still running version 1.02 firmware, and has the same code plug as I was using back in December, so it isn’t that.  However there have been multiple updates to the Dashboard as well as the Pi-Star software since then, so I wouldn’t be surprised if that was the fix (but how the heck multiple code groups could work through a Zumspot is beyond me).

With the talkgroup selection now working cleanly, I’ve revised my opinion of the radio upward.  It is reasonably priced around $150 (less than half of a ID-51 DSTAR radio), about the same as the Yaesu YSF FT-70D.  I paid $130 for my slightly more expensive DJ-MD5GP GPS version on sale back in December.  At that time, the GPS was mostly useless, but I understand that the latest firmware adds D-APRS support.

Posted in DJ-MD5, DMR, ZumSpot | Leave a comment

So what was going on in solar weather today?

I thought it might be useful to see what the solar conditions were this morning when I worked Alaska on 160-m.  We had a solar disturbance and sunspot making things interesting for us a few days ago (spot 2736), but that had just rotated around to the other side of the sun. The increase in solar activity energized the F-layer for a bit at the expense of increased D-layer absorption.  With the sunspot gone, the D-layer faded quickly as the F-layer retained some of its energy, allowing multi-hops to be effective on 160-meters.

The biggie was the Kp-factor, which had been averaging about 3 the last few days, but had quietened down to 1 or less this morning.

In addition, D-layer absorption was non-existent globally

Posted in 160-Meters, Solar Cycles | Leave a comment

Dreams do come true: Alaska on 160-meters

With age comes experience and also a smaller bladder.  I often check my radio at odd hours of the morning because of the latter.  Today happened to be a first for me; when I checked, I saw that Alaska had been showing up on my screen a bit earlier.

Multiple times between 1:50 AM and 2:50 AM (15:50 to 16:50 UTC), AL7TC was visible, between -14 and -18.

I started calling Terry shortly after 3 AM my time, and he was hearing me almost every pass.  It took a bit before I heard him, but I did!  I often try to capture the moment, but this time my fingers were trembling quite a bit and I missed my usual screen shot.  But I did manage to snag a section of it.

Many thanks to Terry, for being on tonight, and for completing my WAS on 160-meters.  He was nice enough to upload to LotW quickly.

Now how the heck do I get back to sleep?  Then again, this is ham radio, who needs sleep!

Posted in 160-Meters, DX | Leave a comment