AmateurRadio.com

See http://www.qrpkits.com/bitx20a.html

If I was looking for a simple, reliable QRP SSB rig for HF use in the coming years then the Hendricks QRP Kits version of Ashlan Farhan’s BitX transceiver for 20m would be in the frame. They also do a version for 17m, but there is more chance of QSOs on 20m.  The rig has a useful 5W pep output and looks straightforward to build for most people. The Ashlan Farhan design is well proven. Going from 100W down to 5W is only just over a couple of S-points. 5W will get you plenty of QSOs on 20m SSB. 5W is fun.

A 10m version would be fun, but sadly is not available, but likely to be less useful in the years to come, apart from summertime Es. A 10m design would need better MOSFET PA devices anyway I think.

Roger Lapthorn, G3XBM, is a regular contributor to AmateurRadio.com and writes from Cambridge, England.

Larry Makoski, W2LJ, is a regular contributor to AmateurRadio.com and writes from New Jersey, USA. Contact him at [email protected].

10' x 20' LF Loop

As is usually the case, conditions deteriorated rapidly as the CLE weekend approached. Conditions varied throughout North America as those listening from the south-eastern regions of the U.S. reported much better propagation than those further to the northwest. Friday night appeared to be the best of the lot but all three nights were very much less than stellar.

The three-night event produced a total of 39 NDBs, with a couple of surprises.






DD UTC    kHz     Call       mi   Location
----------------------------------------------------------

22 05:00  370     YBV        1169 Berens River Apt, MB, CAN
22 06:59  370     OUN        1611 UoOk Westheimer Apt, OK, USA
22 05:00  371     YK         211  Yakima, WA, USA
23 09:00  371     PUR        1629 Marshall, MO, USA
22 05:00  371     ITU        558  Great Falls, MT, USA
22 05:00  371     GW         1946 Kuujjuarapik, QC, CAN
22 05:00  372     ZPA        824  Prince Albert, SK, CAN
22 05:00  372     YCO        1340 Coppermine, NU, CAN
22 05:12  372     FPN        675  Petersburg, ALS
22 07:00  373     TF         1191 Pueblo Mem Apt, CO, USA
22 05:00  373     MF         444  Table Rock, OR, USA
22 05:00  374     LV         776  Livermore, CA, USA
22 05:00  374     EX         190  Kelowna, BC, CAN
23 09:00  374     EE         1319 Forada, MN, USA
22 05:00  374     BOD        942  Bowman, ND, USA
24 09:59  375     PSN        1854 Palestine, TX, USA
22 05:00  375     FS         896  Fort Simpson, NT, CAN
22 10:59  375     DW         1629 Owasso, OK, USA
22 07:00  375     CP         900  Casper, WY, USA
22 05:00  375     BD         803  Moose Jaw, SK, CAN
22 07:00  376     ZIN        3326 Matthew Town, BAH
22 07:00  376     YAG        1345 Fort Frances, ON, CAN
22 13:59  376     PVQ        1690 Deadhorse, ALS
22 06:59  377     EHA        1350 Elkhart, KS, USA
23 06:59  378     ZFA        1000 Faro Municipal Apt, YT, CAN
22 05:00  378     OT         381  North Bend, OR, USA
22 10:59  379     ZEG        526  Edmonton Intl, AB, CAN
22 05:00  379     YBE        945  Uranium City, SK, CAN
23 12:59  379     IWW        1360 Kenai, ALS
22 09:00  380     OEL        1297 Oakley, KS, USA
22 05:00  380     GC         899  Gillette, WY, USA
22 05:00  382     YPW        86   Powell River, BC, CAN
22 05:00  382     YE         686  Fort Nelson, BC, CAN
22 12:59  382     JNR        1731 Unalakleet, ALS
22 12:00  382     GRN        1522 Guerro Negro, MEX
22 05:00  382     AW         75   Marysville, WA, USA
22 06:59  383     PI         658  Pocatello, ID, USA
22 05:20  383     CNP        1146 Chappell, NE, USA
22 05:00  384     3F         792  Ile-a-la-crosse, SK, CAN
-----------------------------------------------------------------

This particular frequency range (370-384.9kHz) is a tough one for me, since my local pest signal, 'AP' is on 378kHz, smack in the middle of the listening range. 'AP's antenna is just .4 miles (2100') from my antenna and its signal is about 60db over S9.... Very loud!

AP to me...Courtesy: https://www.google.ca/maps/

The new 10' x 20' rotatable loop continues to work well. When pointed towards the east, it offers significant nulling of AP's signal and when carefully aligned to the deepest null-point, reduces the signal by almost 30db...but still leaves a very strong signal.

Using this 'deep null' position, I was (somewhat surprisingly) able to log another Canadian NDB (ZFA  Mayo Airprt, Yukon Territory) on the same frequency as AP. The ident-tone modulation frequencies are separated by 10Hz (408Hz vs 418Hz) which was enough to allow the very narrow ~3Hz Perseus filtering, combined with two notch filters, to reveal the 'ZFA' identifier between the 'AP' identifier. Listen for the weak 'ZFA' ident after the loud keying artifacts of 'AP', when they are transmitting just a steady tone.



The other surprise was the logging of 'PVQ' in Deadhorse, Alaska, way up on the extreme northern slope oil fields.

Courtesy: https://www.google.ca/maps/

My last reception of this beacon was in March and conditions usually have to be very quiet, geomagnetically, to hear it at all. The coronal-hole streaming of this past weekend, putting the damper on LF propagation, makes this path very unlikely and surprising! See if you can hear the weak 'PVQ' identifier during its short appearance early on Saturday morning:


CLE organizer, Brian Keyte (G3SIA), reports 51 participants worldwide and over 2100 reception reports. All reports have been added to the RNA/REU beacon database.

As well, Brian will be publishing all results on the NDB Information page shortly.

All-in-all CLE188 was another enjoyable event....hopefully conditions will be better by this time next month and if you did not participate, maybe you will give it a try next time!
Steve McDonald, VE7SL, is a regular contributor to AmateurRadio.com and writes from British Columbia, Canada. Contact him at [email protected].

I’ve discovered an archive of several older electronics and radio-related magazines available for download in PDF format.

http://www.americanradiohistory.com/Popular-Electronics-Guide.htm

In addition to Popular Electronics, they also have archives of the following titles available:

Electronics Illustrated (1958-1972)
Electronics World (1959-1972)
Radio Electronics (1948-1992)
Elementary Electronics (1964-1980 sporadic)
BYTE (1975-1984)

And many more….

Matt Thomas, W1MST, is the managing editor of AmateurRadio.com. Contact him at [email protected].

In the early days of wireless, spark transmitters were all they had. Selectivity and bandwidths were not major concerns.  These days it is all so different with sometimes very crowded bands and the bandwidth of both transmitter and receiver being of major importance.

See http://en.wikipedia.org/wiki/Spark-gap_transmitter for some interesting reading. I recommend you do not try a spark transmitter as you would be very unpopular because of the wide signal and interference caused.   By all means read about them though.

A modern challenge is to see just how simple rigs can be made yet still function credibly on the amateur bands today.  Rigs like the Pixie are fun, but such ultra-simple transceivers are let down by deaf or easily overloaded receivers. To my mind, the receivers have to be selective, sensitive, have netting, and not be easily overloaded. The challenge is to overcome these issues! Often TX power is not the deal breaker.

UPDATE 1740z:  W5OLF has just shown me a photo of is tiny 1 inch ferrite rod antenna on which he has had some success with on 10m WSPR. I tried some WSPR experiments with ferrite antennas some years ago on 40m, 30m and 20m. As long as the ferrite does not saturate they do work. See www.g3xbm.co.uk .

Roger Lapthorn, G3XBM, is a regular contributor to AmateurRadio.com and writes from Cambridge, England.

Thanksgiving.

What?!?

Yes, Virginia, it looks like the east coast is going to receive a rare white Thanksgiving.  Even though it approached 70F (21C) here yesterday, a change is in the offing.  By 8:00 AM tomorrow morning, the busiest travel day of the entire year, a classic Nor'easter will be making its way up the coast, bringing much colder air and snow with it. By Buffalo, NY and Great Lakes region standards, we're talking a mere dusting of snow - maybe only 3-8 inches (7-20 cm), but enough to make traveling to Grandma's house a trickier proposition than normal. By the way, the last time it snowed in these parts for Thanksgiving was 1989 - some 25 years ago.


On a Ham Radio note, it appears my W3EDP antenna has gone the way of the DoDo Bird, that is - extinct.  I plugged it into the KX3 the other day and I noticed that it is considerably deaf.  Stations that I can hear plainly and loudly with the EDZ and the Butternut are but a mere whisper on the W3EDP.

I suspect I know where the trouble is.  There are only three parts to this antenna - the actual wire, the balun, the coax.  I'm placing my money on the coax.  I suppose water could have gotten into the balun and could be wreaking havoc, but it is a commercial brand, popular make balun.  I think it's way more likely that water probably got into the coax.  I probably didn't weather-proof the connection as well as I thought I had.

Unfortunately, I don't have a piece of coax long enough to replace it right now.  Guess I'll be ordering some over the long Holiday weekend.  I don't suppose there are any coax stores holding day-after-Thanksgiving Black Friday sales, eh?

72 de Larry W2LJ
QRP - When you care to send the very least!
Larry Makoski, W2LJ, is a regular contributor to AmateurRadio.com and writes from New Jersey, USA. Contact him at [email protected].

I doubt anyone missed the recent FTDI driver controversy.

The Scottish company Future Technology Devices International (FTDI) released an updated version of their USB-to-Serial driver for Windows on their website late September and last month the driver became available via Microsoft Windows Update. It soon became apparent that these new drivers could 'soft brick' counterfeit and software-compatible clones of their chips by re-writing the USB product ID (PID) to "0000". This action prevents the chip from being recognised by drivers of any operating system, effectively making them inoperable unless the PID is changed back. This clumsy and ill thought out measure was intended to protect its intellectual property.

The ability to reprogram the USB Vendor/Product IDs is a feature of FTDI devices offered to equipment manufacturers and so most bricked devices could be reset by using the downloadable FTDI utility.

Obviously there was much outrage from the hobbyist community and FTDI were roundly criticised and as a result the malicious driver was supposedly removed from the Windows update system.

Or so I thought...

I am currently constructing another data mode interface for some experiments with FreeDV. It requires the usual PTT control driven using the RTS line from a serial port. I purchased a couple of simple TTL level interface boards on eBay which claimed to use FTDI chips.



I built up a little scrappy veroboard circuit with an open-collector drive transistor and plugged into the shack PC and everything seemed okay as this PC already had an older FTDI driver installed.

I am using another computer for the FreeDV experiments and plugged the board into this thinking it too already had a safe FTDI driver installed but instead it brought up the installing driver dialogue and appeared to go online and download drivers and install them. I really didn't pay much notice as I wasn't too worried as any malicious drivers had supposedly been pulled and sure enough after installation everything appeared to work, the port appeared in device manager.

I unplugged the board to make a slight change and was surprised when I plugged it back in the PC the driver installation dialogue reappeared followed by an error message saying driver couldn't be installed and contact the manufacturer.

The serial port now appeared in the device manager with a yellow exclamation mark saying no driver installed error 28. Examining the device details showed that the VID was still 0403 but the PID was 0000 it had been bricked! Unfortunately not soft bricked as I have been unable to reset the chips PID using the FTDI utility.

I am not exactly sure what has happened but still a case of beware when it comes to FTDI devices and I shall be avoiding them from now on.
Andrew Garratt, MØNRD, is a regular contributor to AmateurRadio.com and writes from East Midlands, England. Contact him at [email protected].