Dear Dean KK4DAS:

Back in December, Becky Schoenfeld W1BXY, Editorial Director for ARRL’s On the Air magazine, asked me if I would be interested in writing a detailed set of step-by-step instructions for my Drive-on Portable Antenna Support. Naturally, I said I would.

I submitted my manuscript, along with an all-new set of pictures. The article was published in the current issue (May/June 2024) of On the Air (pages 20-22).

If you’re interested, have a look. ARRL members have access On the Air as part of their membership.

73, Craig WB3GCK

Ed W4YWA is far too modest -- he has built a very FB homewbrew transmitter.  Congratulations Ed.  I think your original plan to use a Web SDR receiver will work, if you and the other station are just willing to pause for an additional second or two to let the internet catch up with the real world.  Also, you might find some Web SDRs that have less latency than other.  You could used a little SW receiver or a simple buzzer for your sidetone ( I think sidetone is your most pressing latency concern.)   My suggestion is to try to get a few contacts using the Web SDR (perhaps via schedule -- try the DX Summit or the SKCC web page to set some up). Then build yourself a simple Direct Conversion receiver to use with this rig.  You don't have to try to build a VFO at 14 MHz (that can be difficult) -- you could build one at 7 MHz (use the circuit from our High School receiver project) and pair it up with a "Subharmonic Mixer" so that you can tune the 20 meter band.  Please keep us posted on your progress. 

Ed writes: 

Home-Brew Fun and Failures 

When all was said and done, it was time to power it up and….. and …. nothing! Not a single function worked! I won’t bore you with the debug stories that took forever, but the only part I didn’t have in my junk box was the PA transistor. I got 10 of them for $5 off the Internets and they all failed to deliver. I could only get a few tenths of a watt from my design. In a fit of desperation, I un-soldered a PA transistor from an old CB radio and it immediately gave me 1.8 watts of pure CW ! ! ! ! Happy dance, happy dance! But, save your accolades. There were lots of other problems; they were my problems not component issues. For example, before you design your own RF filter be sure you understand cutoff frequencies. They are not the same for every filter design. I suggest Paul Harden’s NA5N site to learn about PA output filters. My first few filter attempts had the transmit frequency well down on the attenuation curve. I was attenuating my own signal ! So, after weeks of “why don’t the damn thing work,” I got a clean signal. Whoo-Hoo!

Now it was time to unshackle the dummy load and see where I can be heard. And, Oh boy… I’m beaming into Pennsylvania, Georgia and Northern VA, all from an inverted V on a tripod mounted paint stick, held apart with two tent stakes. But then, reality took over. My grandioso plans for using the web-based SDRs as a station receiver (and the side tone oscillator for my transmitter) didn’t account for the latency delays of the SDR software. If you ever listened talk radio and the host says, “Turn your radio off – the delay will make you sound like a ….” you know what I’m talking about. You would think that someone who over thinks everything, would have foreseen this issue before spending countless hours of breathing solder fumes? Humility and eating crow are my better traits. But not to worry, I’m not ready to give up. Stay tuned for more adventures of Home-Brew Fun and Failures. 

73s W4YWA

Need to wind some toroids?

While I’m waiting for my QRPLabs’ QMX kit to arrive, I thought I’d try to learn something about toroid winding. This video takes toroid winding to a whole new level.

W2AEW on CW bandwidth

Question T8A11, in the Technician Class question pool asks, “What is the approximate bandwidth required to transmit a CW signal?” The correct answer is 150 Hz. The question says “approximate” because the bandwidth depends on the speed at which the Morse Code is being sent.

In this video, Alan, W2AEW, actually makes some measurements to determine the bandwidth of a CW signal.

KB6NU on LICW

A couple of weeks ago, Bob, K4LRC,  asked me to speak to the LICW Portable Ops group about getting better at CW. I guess they ran out of qualified speakers. I don’t know if the group learned anything, but it was fun to speak to the group. TL;DR getting on the air and making contacts is the best way to improve your CW.

I kind of arrived at Dick Benson's QRZ.com page by accident, but what a happy accident it was.  There is a lot of homebrew goodness on Dicks page, both SDR and HDR.  

Check it out:  https://www.qrz.com/db/W1QG/

We’re still alive! November and December have been very busy months. In that short time I both decided to find a new job, found a new job, and started the new job. I’m back into doing what I love best: Fixing things, and writing things. I guess you could just say I’m wired that way. …

Continue reading

The post A New Prototyping PCB for QRP/Homebrew Radio appeared first on MiscDotGeek.

There are times when you wonder if your receiver and antenna are really working as they should. The band is dead, or empty, it’s the middle of the day, the D-Layer is sponging up every radio frequency excitation. Perhaps you can hear a few signals, but they are fleeting — and you need a steady and predictable signal source for a proper test. An RF signal generator will give you a steady carrier, but there are times when you’d prefer to have a true CW beacon to tune onto. This simple, general purpose multiband CW beacon can be run up on the frequency (or frequencies) of your choice, is powered on a 9V transistor radio battery, and can moved to attenuate to the desired signal level, for radio receiver system testing purposes.

This beacon transmits a hard-coded message in morse code on any frequency supported by the si5351 (10kHz to 160MHz). The code targets an Arduino Nano, Uno or bare ATMega328P and an si5351 breakout board. No display is necessary. You can add one, and controls, if you like. The code includes a simple CW keyer for manual sending (not used, but left in place for this application).

Any number of frequencies in the HF and VHF range can be specified by adding them to an array of transmit frequencies. The beacon iterates over the array and transmits the message on each frequency in sequence. The beacon’s CW speed is configurable. Sidetone is available as a 5v square wave on the D7 output. There is no support for switched low pass filters but this would be easy to add.

The Github repository is here.

There’s a reason why most homebrew transceiver kits and scratch-built projects are monoband and single mode — theres a chance you’ll finish it, or at least, get it working for a while. Building a multiband HF transceiver is a big job, as any homebrewer who has attempted it will tell you. It may take years.

My build of Eamon EI9GQ’s transceiver is no exception. It was started in 2018, the first rush of enthusiasm resulting in a working superhet receiver on 160 to 40m, and boxed up in a custom solid aluminum case. This video shows it off circa 2018.

With a heap of work ahead, and a list of unresolved minor problems, other projects took priority, and the rig ended up spending the next four years in a carton (with all my notes, schematics, assembly and PCB sketches, and unused components). Until recently.

Schematics

It’s my normal practive to include kicad schematics, but in this case the EI9GQ designs are copyright RSGB. So go and buy Eamon’s book from the RSGB Bookshop, or on Amazon, you won’t be disappointed.

Resumption

E-mail discussions with another keen maker (Neville ZL2BNE) about his build of this transceiver gradually tickled my interest to resume. Nev was making good progress, had his rig transceiving, and was working QRP DX. I dug mine out of its carton and fired it up — it had all the appeal and problems that I remembered from 2018. I resolved to kick it along the road for a bit, to see how much interest I could reconstitute. Upon resuming, a number of issues needed addressing, some easy, some repetitive, some more difficult but not impossible. Here are those that I can remember…

Firstly, the 9MHz IF amplifier oscillated with the manual AGC turned up, and was generally unstable. To fix this, I put a 5k5 resistor in parallel with the drain tuned circuit — a well known technique for taming high gain stages. I figured that of the three identical 15 to 20dB gain stages, it made sense to damp down the gain of the first stage. This did the trick, and all three stages exhibited a nice resonance peak using the trimcaps, and overall stability.

The next thing was to calibrate the si5351, a simple job I’d never bothered to do, resulting in the display showing odd and fractional frequencies for the property resolved SSB stations in the 2018 video. If you want to know how this is done, go to your si5351 library’s README file, it is quite easy to do, and once done, lasts for years, or for ever.

Next problem was the LCD backlight. The large font 20×4 LCD I had chosen for this rig was a bit of a novelty back in 2018. I liked that it’s huge characters could be read from half a room away. I used to joke with myself that I’d still be using this rig in my 90s, when all the compact rigs with fiddly little OLED displays were beyond my failing eyesight. And the four lines of 20 characters gave me extra display space for luxuries like a UTC clock and metering. But that big display had an equally oversized backlight which could light up a darkened room, but drew more than half an amp. Although this rig was intended for the shack bench, I was not used to my receivers pulling over an amp.

I decided to multiplex the LED array with a simple PWM LED dimmer, which uses one half of a 4093 quad gate as a variable duty cycle oscillator running at around 70kHz, driving an IRF540 FET switch. This worked a treat and the dim potentiometer was mounted right on the front panel. It controls the backlight from off to 90% on, when it drawn around 500mA.

The next mini-project was an AM detector. I was not interested in full AM transceive capability– I have other homebrew projects for operating VK legal limit AM — but I did want to be able to enjoy decent AM reception using the high quality 6kHz filter in this receiver’s set of three KVG crystal filters. I chose an infinite impedance AM detector, successfully used in a prior AM receiver project.

This mod necessitated making a PCB to overlay the existing product detector and audio preamp, with a plug-in board containing the AM detector, it’s own preamp, a miniature relay to steer the incoming IF signal to either detector, and a shared 4046 quad bilateral analogue switch which selects the product or AM detector’ s output, and additionally does receiver muting and Sidetone routing when in CW transmit mode. This assembly worked well. One hickup — I originally left the BFO powered up in AM mode — and even though there was no direct BFO coupling anywhere, there was more than enough stray coupling to resolve sideband. This was fixed by switching the BFO board’s DC power off in AM mode.

The next task involved coming up with a mechanism to select one of the three KVG (ex TelRad) filters. These high quality 9MHz crystal filters were common on eBay a few years back, and are a feature of this receiver. These filters came in a set of three. In a slight departure from superhet convention, a separate filter is used for USB and LSB, with a 6kHz AM filter in the middle. The BFO runs permanently on 9Mhz. I wanted to have filter selection under software control, so that the correct sideband filter would be selected for the current band. One of the front panel pushbuttons was used for a mode control — pushing it cycles thru the sidebands and an AM setting. A small daughter board was added to the filter assembly containing a PCF8574 demux IC on the I2C bus. A few additional lines of code implemented a simple control function.

The 2018 receiver’s front end board included space fo r an RF amp block, with a pair of miniature relays to bypass it. The original PCB was layed out for a MMIC which probably would have worked fine but in the end I built up one of EI9GQs broadband RF gain blocks using a parallel pair of MPSH10 transistors for around 20dB of gain. The EI9GQ amp was built on an overlay board sized for the available space.

A few minor additions followed. A 41MHz Low Pass Filter was added on the VFO buffer input. On the highest band (28MHz) the VFO is 9MHz higher, on 37MHz. This low pass filter cleans up any VFO harmonics, probably low anyway, but a safety precaution.

The diplexor was added, a balanced tee arrangement, with series and parallel 9MHz tuned circuits arranged to pass through 9MHz energy, but sink all other frequencies into 50 ohm resistors. This ensures proper termination of the receiver mixer and keeps unwanted mixing products, particularly at the image frequency, out of the first IF amplifier.

One of the nore repetitive jobs (which just has to be done!) is making and tuning up the remaining Band Pass Filter modules. Three mire were built, for 17, 15 and 10m, using the EI9GQ design. This gave eight bands, 160, 80, 40, 30, 20, 17, 15 and 10m. My approach to the last three boards was mostly as I’d used in 2018, other than improving the use of right angle 0.1″ header pins inserted through a row of holes drilled through the PCB for mechanical strength.

Next job was a small board mounted on the rear panel next to the two SO239 sockets. This board has the transmit-receive relay, and a second relay that switches between two SO239 for an Antenna A/B switch. Three 7812 regulators supply the three supply rails, 12v always on, 12v receive, 12v transmit. All three unregulated DC supplies are available on headers as well, to avoid heavy current being drawn thru these regulators, such as the transmitter PA and the LCD backlight.

The rear panel has two antenna sockets (for A and B antennas, switched from the front panel), a panel XT60 socket for DC 12V, and a set of 3.5mm and RCA sockets for connections (external muting, paddle, external speaker, and an auxiliary RCA, as yet unassigned). These 3.5mm switched stereo sockets are very useful pieces but unfortunately are not long enough to go through a 3mm aluminum panel. The best solution is to mill out a recess larger than the socket, but that requires a milling machine that I don’t have. So the workaround was to cut a rectangular hole in the 3mm rear panel, and bolt on a 1.2mm aluminum plate to hold the sockets. Its easy to paint and label this small piece.

Preview of the Exciter

To turn the EI9GQ receiver into a transceiver I needed a microphone amplifier, balanced modulator, transmit mixer, T/R switching, a PA stage and LPF set. Back in 2018 I built Eamon’s LM324-based microphone amplifier (a design out of EMRFD) and another hand made diode balanced modulator. All of these mixers use 1N5711 Shottky diodes individually matched to within a millivolt on the diode test setting on my digital multimeter. The transmit mixer is another hand made diode ring mixer, this time an unconventional triple balanced mixer.

The PA chain after the transmit mixer will be MPSH10 x 2, 2N5109 and a pair of RD16HHF1s for about 10 watts 160 to 10 meters. The LPFs will be by Eamon, derived from the original W3NQN designs, each filter on its own plug-in board, relay-switched at either end, filter selection via another PCF8574 on the I2C bus. There will be six LPFs (for 160, 80, 40 and 30, 20 and 17, 15 and 10 meters).

What’s next?

If you’ve made it this far, thanks for reading, feel free to leave a comment, and stand by for the third and final post on this transceiver project, which will address completing and commissioning the SSB and CW transmitter stages.

Weak Signal Propagation Reporter is a global radio propagation monitoring and reporting network comprised of thousands of low power beacons operating on the amateur radio bands. WSPR beacons can be detected from the lowest of Medium Wave frequencies (137kHz) all the way through the HF spectrum (all the bands from 160m to 10m are popular) to the VHF bands, 50 and 144MHz. WSPR receivers decode the tiny beacon packets and upload them to a central database, at WSPRNet.org, where anyone can literally ‘see’ the propagation paths that are currently open.

Equally, you can go back and revisit the radio frequency propagation conditions during any previous time window. Running a WSPR beacon from your home allows you to ‘watch’ the propagation paths open, peak, and close each day under the influences of solar radiation, sunspots, and other ionospheric conditions. Arduinos and a few common accessory boards that can be had for tens of dollars make a beacon accessible to just about any experimenter (with an amateur radio license).

I’m late to the WSPR party. I’ve wanted to try a beacon project for a few years. A while back, I took a copy of the ZachTeck script and experimented with it and a Ublox GPS, but after getting the NMEA strings decoded from the GPS unit at roughly one second intervals, the rest of my code was over-engineered and bloated, and did not fit into the small memory constraints of the Arduino Nano. I put is aside.

Recently, I did a much needed upgrade to my Arduino IDE and libraries. The thought occurred to me that improvements to both IDE and libraries may give me a fighting chance of getting that old WSPR script fitting. When I opened it up, and started to work through it, I saw some obvious ways of reducing memory usage. I had too many String objects (memory-hungry). And my code was writrten to parse each NMEA message string and tokenise it. This allowed me to get to discrete data fields a long way down the messages, like the number of detected satellites. In a simple WSPR beacon, all you really need is the UTC timestamp at the very start of a number of the NMEA messages. I ditched the superfluous stuff and got it uploading, and more to the point, not hanging!

WSPR dataset applications

WSPR is brilliant for teaching you about rare and exotic places that you feel compelled to Google when they turn up on your map in the morning, places like Orlygshafnarvegur (TF4AH, Iceland) or Fuerteventura (EA8BFK on the Canary Islands).

The database of historical propagation across the HF spectrum is widely used by amateur researchers to learn about propagation and has some more serious applications as well. Experimenters have used the data to support ideas or research questions about how symmetrical propagation is at opposite sides of the globe in the same period, and to test antennas. More seriously, a theory was proposed that impressions in the WSPR dataset may indicate the path of the lost flight, Malaysian Airlines flight MH370.

Script

The script is here: https://github.com/prt459/WSPR_GPS_Beacon

Schematic

The schematic is so simple it really doesn’t need a kicad. The Ublox 6M GPS connects to Arduino D2 and D3 for serial data transfer. It also needs GND and +5V. The si5351 breakout board uses I2C and so goes to Arduino A4 (SDA) and A5 (SCK). Connect the si5351’s CLK0 to whatever low power HF amp you like. Mine is from Experimental Methods in RF Design (EMRFD), Fig 12.32, but I could have chosen any number of similar two-transistor stages.

WSPR works on truly tiny power levels. If you connect the bare si5351 clock output to an antenna, you will get decodes! (You should add a Low Pass Filter if this is anything more than a quick test). So use a single 2N3904, or anything with gain, up to a full 5 watt QRP PA with an IRF510 or Mitsubishi RF FET, which is a ‘big gun’ in the WSPR world. Mine uses a 2N3904 and 2N4427 in common emitter feedback configuration, delivering around 10 volts peak to peak into 50 ohms, followed by a W3NQN Low Pass Filter for the band of interest.

Gallery

Acknowledgements

Thanks to Harry from ZachTek for making his code open source. And to Jason Milldrum NT7s for his si5351 and JTEncode libraries.

SPRAT #192

After publication of this project in the RSGBs SPRAT #192 Autumn 2022 a number of builders commented below the post or contacted me with build reports and questions.

First, the 12v DC series decoupling resistor was not labeled in the published schematic, it can be anything between 47 and 100 ohms (see corrected scheatic below).  

Secondly, Ian McCrum did an LTSpice model of the PA which revealed that I omitted  a resistor from the original design in EMRFD (in parallel with the 100n coupling capacitor between the stages) which forms part of the biasing of the PA transistor. If omitted, the PA works, but with reduced power.  Adding the resistor increases the RF power output to around 0.5W, although this will vary depending on drive level, the PA transistor, and the DC supply voltage. Thanks Ian for taking the time to LTSpice this QRP PA.
 
Steve K8SDK got more power out of his PA by increasing the si5351 drive level from 2MA (my value) to 4, 6 or 8MA.  There is a general understanding and some analyses that report the si5351 clock phase noise gets dirtier as you go up in drive level, and for this reason I left it at 2MA.  But with sub 1 watt power levels and a LPF on the output I don’t think it would make any practical difference.

On the question of WSPR beacon power, I don’t think 0.5W is preferable to 0.2W under curent band conditions. With 0.2W the decodes at DX WSPR receivers get marginal and the spread of the band opening can be seen as the grey line moves across the globe. Higher beacon powers can result in saturation which looks like a more rapid ‘lighting-up’ of the remote receivers on the map, and the subtleties of propagation can be lost. This is another way of saying that you should really use a minimum power necessary to get decodes at the far end. However my preference for low power is a personal preference, and some may need slightly higher power to overcome antenna losses.

Several people reporting having to use the set_correction() call with the second parameter (around line 320). I added a comment note immediately above the call in question:

// NOTE: There was a library change to the signature of this method. If you get a compiler error, try this:
// si5351.set_correction(19100, SI5351_PLL_INPUT_XO);

I did it this way to allow for compatibility with subsequent versions of the NT7S si5351 library. But a few people got the compile error and did not trace it back to the offending source line, or perhaps read the comment. I should have just made this change in the repo code to make it foolproof for all comers.

Neil G0ORG emailed with a question about si5351 calibration, his calibration attempt resulted in a value of 149850 for the call to set_correction().  I personally have not seen a calibration offset that large, however, the tiny crystals on the Adafuit and clone breakout boards must vary considerably. Neil reported that this offset pulled his si5351 outside the WSPR passband — we are not sure what went wrong with the usual calibration process for this to happen, bit Neil got his beacon back on the spot by experimentally reducing this large offset value.

Stephen G3ZNG had problems compiling the sketch, and after a bit of investigation discovered he had a previously installed JTEncode library. Upgrading the library fixed the problems and Stephen reported his beacon was working.

Chris G4BMW had the same problem. When he installed JTEncode v1.3.1 and Si5352 v2.1.4 it worked. Chris then discovered that GPS units do not always work inside, and had to move his unit next to a window to give the GPS receiver a sniff of the overhead statellite’s signals.

John G8CHP emailed me a photo of his completed WSPR beacon in a sandwich box. John reports spots in western Canada from his QTH on the east coast of the UK. John used a QRP Labs QLG1 GPS unit, mainly because it was on hand, and a 2N3866 for the PA.

Jonathan G5LUX got his beacon working on a breadboard, and it worked first time.

Aaron K5ATG emailed to discuss his build options, saying that most commercial WSPR beacon products are reasonably pricey for what they are, and my design is made from just a handful of commonly available components, most of which he already had.

Nigel, G4ZA emailed me to say that he had also come up with his own homebrew WSPR beacon, and that Harry’s code (Zachtek) saved him a ton of work too.

Steve K8SDK used three FETs (presumably in the conventional Class E PA configuration as used in many QRP CW PAs) (see comments below post).

And finally, Dave AA7EE has done a superlative job of building his own WSPR beacon using my script, and of course, his blog write-up is amusing, informative and a celebration of the finest amateur radio homebrew spirit. Dave set up his beacon on 10m but had si5351 stability issues which he describes in detail. He solved the drift problems with patience and experimentation, eventually settling on 20m. His post shows remarkable QRPp WSPR results. Thanks Dave for the acknowledgments peppered throughout your post. (See also Dave’s comments below).

A number of builders commented below the post, please read for further discussion. As well, I did receive other emails so if I have missed you please leave a comment below.

Working beacon by G5LUX

This board is a universal radio project controller, with an ATMega328P(U) microcontroller and lots of options. The intention was for it to become a basic building block in transceivers, receivers, transmitters, signal generators, anywhere you need either a digital controller, one to three clocks, or both. The board has headers for the common si5351 breakout board, available from Adafruit or as a .CN clone, and a 16×2 HD7044 Liquid Crystal Display using the standard 14+2 parallel data header (+2 for backlight). It brings out all of the available digital IOs (D2..D13), analogue inputs (ADC) A0..A5), as well as headers for a 12V supply, and access to the regulated 7805 5v output, access to the LCD backlight in case you wish to take control of this in software, and an FTDI-compatible USB-to-serial programming board.

More features

However it doesn’t end there, as the point of this desgn was to incorporate as many of the additional components that have so often been relegated to small boards hanging off front, side and rear panel sockets and switches. So there are these additional headers:

• a header for 1, 2 or 3 pushbuttons for general control purposes, intended to be mounted on a front panel for channel selection, VFO control, VFO step etc (additional buttons can easily be added in desired)
• a header for a paddle and 1, 2 or 3 keyer memory pushbuttons (again, more may be added)
• a header to take digitally generated and filtered sidetone (with an on-board level setting trimpot) off to a transcever’s audio stage
• a header for a mechanical or optical emcoder (tuning), including a line for an integrated pushbutton.

The ATMega328 MCU’s I2C SDA and SCL, ground and 5v are additionally available on an I2C header, for all kinds of extensions via sensors that talk I2C or those on breakout boards. This feature opens up the possibility of using any of the OLED displays instead of the LCD, as OLEDs interface via I2C. Another option is to use an LCD with I2C backpack which would free up 6 additional digital IO lines.

In fact there is no reason to have a display if you don’t need one, this board could control a headless WSPR beacon, Automatic ATU or Satellite Tracker if needed. The possibilities are fairly much as endless as you get from an Arduino Uno.

The board was designed using EasyEDA and fabricated including assembly at JLCPCB. The design process was a part time project that lasted about 6 weeks. The first batch of five boards was done and delivered in about two and a half weeks from ordering, with DHL delivery.

Clock buffers

The three si5351 clocks are each buffered on-board, delivering a solid +13dBm (20mW) into 50 ohms, perfect for driving an L7 mixer (via a pad) or a transmitter pre-driver or driver. The buffers are 74LVC1G126 , fast single buffer/line drivers with 3-state output and a Schmitt-trigger on the input for handling any variation in the si5351 clock rise and fall times as frequency increases. The buffers are permanently powered and will only draw curent if the clock is enabled.

Gallery

Schematic

The schematic is here.

Wiring diagram

Firmware

My VFO_Controller script now has a new compilation target, UNIVERSAL_VFO_CONTROLLER, which, if #defined, includes the code for the pushbuttons and other features of this particular board. Get it here:

https://github.com/prt459/Arduino_si5351_VFO_Controller_Keyer

First use: a 20mW QRPp transmitter!

The first real use of the board in the shack was as a QRPp transmitter. Just power it up, connect a resonant antenna to CLK#1 output, plug in a paddle, and it’s ready. Adding a 2N2222 or BS170 (and a Low Pass Filter) should get to half a watt, an additional IRF510 for a full five watts, so simple!

Credits

The schematic is derived from Ashar Farhan VU2ESE’s Raduino. A number of ideas for improvements were made by David VK3KR. The use of si5351 clock buffers and selection of 74LVC1G126 devices was first done by Glenn VK3PE.

First run boards are being evaluated by David and Peter VK3TPM. Once the bugs are ironed out (and there are a few!) a second run will be done, verified, and then the PCB design will be opened up to anyone who would like to spin up their own pieces.

The bottom ends of 80, 40 and 20m are not what they used to be. For starters, the busiest part is the digital segment where computers talk to computers – listening to this segment is like eavesdropping on a bunch of dialup bulletin boards having a party in 1983. Then there’s the CW segment. When there are CW signals to listen to, all are frequency stable, chirp and click-free, generated by more computers from deep inside rigs that are more computer than radio. These shining examples of digital CW perfection have traded efficiency and quality… for personality.

In 1979 as a teenager I spent countless hours scanning these frequencies on my FT200, and the sounds from those days are indelibly printed on my memory. The CW segments were a managerie of good, average and bad sounding fists, warbles and tones. There were the regular VK DX men with polished 599 emissions, frequency stable and chirp free, some with curious hand-keyed idioms and flourishes. There were JAs by the dozen, banging out formulaic patterned QSOs, and Eastern Europeans, some on their creaky old ex-WW2 equipment that had to be heard to be believed — sloppy, chirpy, drifty, and gloriously messy CW. And of course the Americans with their kilowatt CW reaching out half way around the globe, some with the self-assurance of a military comms man, armed and dangerous.

It was possible back then to tell where a station was from before hearing the callsign by the combination of signal quality and the operator’s fist. The key to this ability was variety. The CW segment was a rich technical and cultural melting pot of sounds and styles, like the marketplace in some kind of global village populated only by fanatical radio enthusiasts, the ham equivalent of the bar scene from Star Wars 4. In those days, sending a CW CQ gave me butterflies–you could be answered by absolutely anyone, or anything!

The loss of analogue CW struck me again when reading the comments under Peter VK3YE’s video on a two transistor CW transmitter, in which he tries different values of the VXO to PA coupling capacitor. 1nF gives ample drive but pulls the oscillator when keyed. 470pF gives lower drive but less chirp. The CW sound was evocative. Several viewers commented that they would always answer a chirpy CQ because it was likely to be a boat anchor or homebrew rig, something more exotic, perhaps something to discuss during the QSO. The thought of a chirpy CW signal being irresistible to some, a feeble flickering flame to which the morse moths are helplessly drawn, began to form.

Using digital technologies to simulate analogue predecessors for continuity or nostalgia is not unusual. Society has recognised the impact of the digital transition on those of us who are living through it. Melbourne Trams sound a digital facsimile of a 1920s bell, a sound synonymous with the city’s central shopping district for 120 years. Electric vehicles include computer controlled devices to generate a petrol engine’s sound to alert pedestrians, or in the case of the new Dodge, maintain faith with the rusted on fan base.

So, why not do the same for CW? It occurred to me that the power of microcontrollers and multisynth PLL clock generators could easily make this happen. It was a simple coding task to modify my keyer code to make small frequency shifts during dot and dash formation for chitp, and to consistently increment or decrement the oscillator’s base frequency to simulate drift. Time constants were #defined as labels for tuning. With a bit of experimenting, a reasonable approximation of both chirp and drift was found.

These first simulation attempts may be overly simple, as a typical analogue oscillator’s chirp does dot pull the frequency as a linear function of time, but rather, might pull hard, then ease off as the oscillator and subsequent amplifier stages settle down. The corresponding mathematical function is probably a complex polynomial. The same with drift. Most of my analogue oscillators have drifted in one direction, then reached some kind of equilibrium, thereby stabilizing. I’m not a big boat anchor guy, but I wouldn’t mind betting that certain old transmitters have their own chirp and drift signature. How else would you recognize them when you hear them?

I leave more sophisticated simulations of bad CW as an exercise for the reader. Same for the many ways you could use this CW party trick. For example, why not arrange for a switch that disengages the chirp and drift. You could call a chirpy CQ to attract attention, then when you snare someone, turn it off for computer-perfect CW. The options are endless.

If you are brave enough to use this, I ask only three simple things: use digichirp mode sparingly, don’t drift out of the band or segment, and don’t blame me for your bad signal quality reports!

Chirp gallery

Here’s a rogue’s gallery of dubious CW signals. Enjoy!

Continue reading "VHF Design QRO LNA Case"

For AGC controlled IF stages in receivers I have often chosen a 2 or 3 stage dual gate MOSFET strip, or a cascode arrangement with a bipolar and JFET pair.  These work well, have more than enough overall gain, and provide good AGC-controlled gain range.    I’ve also built a BiTX style transceiver (Andy G6LBQ’s design) with two Termination Insensitive Amplifier blocks. TIAs exhibit stable input and output impedance regardless of load, and work symmetrically (for receive and transmit) but are fixed gain. My BiTx receiver worked acceptably on 40m but was underpowered on 20m. Increasing the gain to make it more lively on 20m would have made it over-powered on 40m. You don’t have this problem when you have an AGC controlled IF.

So when I saw a mod by George VK4AMG to increase a friend’s uBiTx receiver gain on 28MHz I was very interested.

The uBitx transceiver uses Termination Insensitive Amplifiers in the high and low intermediate frequencies. The Termination Insensitive Amplifier is a design element of great pedigree. It originated with some Plessey radio transceiver designs in the 60s and was popularized for amateur use by Wes Hayward W7ZOI and Bob Kopski K3NHI.

On the uBitx page, designer Ashar Farhan VU2ESE writes … “We used the excellent termination insensitive amplifiers (TIA) developed by Wes Hayward and Bob Kopski (read about them on www.w7zoi.net). These amplifiers work without transformers and they provide excellent termination on both sides. This is a key requirement for bidirectional transceivers like the µBITX . We use four blocks of these amplifiers in this transceiver. The amplifier block has a gain of 16 db and OIP3 of about +20 dbm as measured inside the µBITX .”

So I prototyped the uBitx TIA with George’s mod, a 2N3904 in place of the 10 ohm emitter resistor.  I first drew it in kicad. It’s easy to see how the additional transistor replaces the usual low value resistor in the emitter degeration.

Built on a scrap of etched PCB using surface mount parts. 

I measured 14dB of total gain this block, not the 25 to 30dB I expected, with 14dB AGC action.  Here are some measurements:

The amp stage is flat to about 15MHz, that’s good.  And at 8V of AGC the block delivers 19dB of gain which is about spot on for a typical receiver, assuming you will use two or three such blocks. I dropped the 3k3  resistor in series with   the controlling 2n3904 base to 1k and measured nearly 20dB of gain.

Prototype 4MHz IF strip

Next, I built two of these gain controlled TIA blocks in an IF strip for a CW superhet receiver.  A narrow crystal filter provides the intended CW receiver bandwidth, adding 3 to 5 dB attenuation in its passband. The bench test is shown in the video — 50dB of total gain with 30dB of AGC range, not as much as can be achieved with MOSFETs, or as much as George measured, but still a useful range.

Discussion with Bill and Pete

Next, I shared a knock-up video with Bill and Pete from Soldersmoke, as they have both been strong promoters of the TIA in their projects and through the podcast and blog. Bill wondered what other side effects of varying Rd might be, and that sent me back to Wes and Bob’s 2009 paper. Another likely consequence is that dynamically changing Rd is likely to change the input impedance away from the desired 50 ohms. So the AGC controlled TIA is not really a TIA anymore.

Conclusion

Is this a useful TIA hack? Certainly the gain swing is useful. The impact of having the TIA gain block’s input impedance swinging around in sympathy with signal strength does not sound ideal, but probably depends on what each block is interfacing with. In my prototype receiver, the second TIA block interfaces to the output side of the 4MHz crystal filter via a matching transformer. An impedance mismatch here will result in some power loss. The first TIA interfaces with the output of a ‘strong’ 2N5179 post-mixer IF amplifier stage, which is via a 50 ohm pi-attenuator.

I you find this TIA ‘hack’ interesting and maybe give it a try. Please let me know what you think of it in a video comment.

Thanks to George VK4AMG for sharing it on VK Homebrew on Facebook and for subsequent email correspondence.