Sunday, December 3, 2017

QCX - 30M Transceiver

Recently, I built a QRPLabs QCX, the 30M version.  I have stopped recommending anything to anyone, but I hope to build both the 40M and the 20M versions in the near future.  I have collected a few hints, in no particular order:

Hints:

*  There is a impressive video of a QCX build here by IZ7VHF.  Worth a look if you are considering the QCX.

*   The local big-box office supply store wanted more than the list price of the QCX to print a color manual - even just B/W was more than Hans charges for the kit plus shipping.  I put the manual on an old iPad and propped it up near my work area.  I only printed the inventory pages, the section concerned with winding of T1 and the Cheat Sheet near the end of the manual.  I had the Cheat Sheet laminated.

*   If you use something like an iPad or PC to display the manual, all the illustrations can be handily expanded.

*   I used a pair of binocular magnifying glasses.  Also very handy.

*   I would strongly advise a complete inventory of all parts (also see below).  I had one extra capacitor.

*   I would also strongly advise organizing - at an absolute minimum - the capacitors and resistors by value.  Muffin tins would be nice (and would only take moments to wash and slip back into the kitchen).  If you are fortunate enough to have a workplace that will remain undisturbed, at least draw circles for each value on a piece of cardboard and stick them in that.

*   All of my placement errors were with the resistors.  I strongly advise the hint above, and re-checking the color codes against each other and the inventory listings.  Use a VOM to resolve problems with color resolution.  Slight color (colour?) blindness runs in my family.

*   With my tired, old eyes, I found it hard to count the turns on T1.  I ended up taking a photo with my phone, transferring it to my PC and enlarging it on-screen.  I had one turn too many on the S3 winding.

*   When you cut the small connectors apart, I would strongly advise covering the connector and tool with a cloth.  My first cut ricocheted off the wall, then the bookcase then my chest.  Miraculously, I found it in the work area after an extensive search of the floor.  Of course, use eye protection.

*   Take Hans' suggestion and orient all the parts either the same way or at least in such a fashion that the values can be read later.  Remember that this project will be very crowded at the end.



*   The page breaks in the manual are occasionally unfortunate.  Be extra careful when the instructions and the illustration are on different pages.  As mentioned earlier, the illustrations in the Manual I downloaded to my iPad can be enlarged when clicked.

*   From my experience with SMT projects, I now have a large, cheap aluminum foil cookie sheet with a properly sized piece of white cotton cloth taped inside.  Very handy.  If you ground it, even better.




Finished:

First impressions - the receiver is HOT!  I am impressed.  The QCX seems to hear almost everything my K3 does.  




Power output was low - measured externally at about 1.4W.  

I spent some time reading the QRPLabs e-mail reflector and then followed Hans Summers' recommendations for mods to the QCX.


Mods:

Here is a listing of the modifications I made.

Before and after each change, I made a series of measurements.  First was a 5 second key-down followed by a 15 second rest, then repeated twice more.  Then a 30 second key-down, followed by a 1 minute rest , then repeated twice more.  I am reporting averages of these measurements.  Power was measured independently of the QCX with a 20W Elecraft 50 Ohm dummy load.  I also recorded the supply potential.

I did the mods in two stages, mostly because the changes to L1, L2 and L3 were a little tedious.

Mod #1        -   12.55V supply
    Before:      5s      1.55W
                30s      1.69W
    ** Removed 1 turn from L1, L2, and L3
    After:       5s      1.36W
                30s      1.38W
    ** Re-alignment
    After        5s      1.56W
                30s      1.52W 

Mods #2&3&4   -   12.38V supply
    Before       5s      1.4W
                30s      1.5W
    **Install 1N5819 Schottky diode
    After        5s      1.5W
                30s      1.6W
    **Install 10K resistor from Q5 drain to +12V
    After        5s      1.4W
                30s      1.6W
    **Replace MPS 2907 with MPS751
    After        5s      1.5W
                30s      1.6W


    **Re-alignment
    After        5s      2.0W
                30s      2.0W


The image below shows the diode and resistor addition to the bottom of the PCB.


I think (but do not know) that the removal of one turn from the low-pass filter did not do much.  I think the addition of the 10K Ohm resistor and the change to the MPS751 did a little good.

At this writing, I am satisfied enough that I will await more information from the designer before diving into the circuit board again.  

As it stands, 2W seems to do well on 30M given reasonable propagation.  The Reverse Beacon Network seems to hear me just fine.

More to come, I hope.


cln - Nick
WB5BKL

 

Friday, December 1, 2017

Ham Gadgets Ultra PicoKeyer

I have been using the AA0ZZ EZKeyer II for several years (see my earlier post).  It has worked well with my K1, which I typically use portable.  There are shortcomings, however:  No easy speed control and only 3 memories. 

I tried a keyer with 8 memories, but had so many problems with missing, broken or incorrect parts, odd i/o design and sporadic support that I gave up - sadder but wi$er.

 Then I found the Ham Gadgets Ultra PicoKeyer.
 

The price was right - and I could even chose a color!  Woo-hoo!  

The construction was pretty easy (and the manual is very good).  It was ready to go in under two hours (I work very slowly).

I hooked it up to the Elecraft K1, switched the K1 to 'straight key' mode and gave it a try...

Semi-gibberish.

After several tries and careful inspection - to no conclusion - I decided to give it a try with my K2.  Again semi-gibberish. 

More experiments and some searching of the Elecraft e-mail list archives suggested that the 'ring' connection was live. 

Note:  Elecraft requires a 1/8" three-conductor (stereo) plug for CW input to their K1 and K2 transceivers.  If used in straight key mode, nothing can be connected to the 'ring', just the tip and the shell.  Straight Key mode allows control by an external keyer.

I sacrificed a cable and opened the 'ring' wire.  Everything worked just fine!   How odd.

Then I decided to take a very close look at the PCB for potential shorts.  None found, but there was a PCB connection to the 'collar' pin on the output jack.  It was NOT on the schematic, but it's there:




Since it seemed to be the cause of the problem, I cut that trace.  Success! 

Everything worked normally for both the K1 and the K2. 

I did communicate my findings with Ham Gadgets, but I am not sure they fully understood the issue when the PicoKeyer was used with these Elecraft rigs. 

Hence, this entry.

I filled in the embossing on the front of the keyer.  Looks nice.





This is a neat little keyer.

cln - Nick
WB5BKL

Sunday, November 5, 2017

Debian Linux on an old Netbook


Briefly, an old Toshiba NB205 netbook made its way to me.

I was about to donate it to the local thrift store as it was missing a keytop and the Windows version installed had trouble with the WiFi hardware - but I decided to give Linux a go.






















I won't repeat that procedure here - check my older postings "Adventures with a 'Thin Client' – a HP t5740" and "Dual Booting Debian and Windows XP" for some hints on dual-booting Debian.

I was pleasantly surprised when the new OS was able to handle WiFi nicely.  Now the only blemish on this old machine was the missing key.

Sure enough, eBay had several dealers who had keys.  After some careful reading and research, I ordered a CTRL keytop from a dealer in Canada.

The keytop arrived in a few days along with some abbreviated instructions.  As I did not want to break anything, I looked for further information and - sure enough - there were a lot of YouTube videos on how to remove and replace keytops.

Success!
Now it's back in the stable of 'spares' and occasionally useful tools.  An old, but working, netbook (dual boot) with working WiFi for about $3.50.

cln - Nick
WB5BKL

Wednesday, August 9, 2017

The Hendricks DC30B Resurrection






Recently I found a partially completed Hendricks DC30B 30M transceiver kit on eBay. It is small - a bit larger than a pack of playing cards.  The transceiver is direct conversion, crystal-locked and CW only.  Below is the eBay posting image:

 
The partial kit was advertised as “incomplete, not working and/or for parts”. The image reveals some of the missing parts, Q1 (the final), a toroidal transformer, one capacitor, the case top, etc. For some reason the 78L05 voltage regulator had been removed and replaced but not soldered. I ordered about $5 worth of parts (including the suspect 78L05).

While waiting on the parts, I very carefully went over the construction and found one electrolytic installed backwards. Otherwise, I thought the build quality good.

I wonder why it was abandoned...





Once the missing parts arrived, I followed the extensive assembly instructions available on the web and – to my pleasant surprise, it fired right up. Here's the testing lash-up.



I found a fine resource in the Yahoo DC40Kits email group. I got good advice and welcome encouragement both on and off-list.

 
After testing, I completed the installation in the supplied clamshell chassis half. Unfortunately I could not locate the top – and have yet to find a suitable replacement.

Output was right at 1 Watt with a nice 12.6V supply. I called CQ a lot until I made my first QSO with NK8O in Kansas (image to the left). The antenna was a 30M sloper and Chas gave me a 579. I have since had better luck when 30M was in good shape, usually at night.  (Note:  The K3 was on - but not in use)


Some thoughts:

This was a lot of fun for the price of a couple of fancy coffees for the better half and me. My biggest mistake was to limit myself to the supplied case. I have since learned of several mods which I could have applied easily. My second mistake was to not mount a socket for the crystal. The supplied Xtal (10.120KHz) is nowhere near the usual QRP frequencies.  Personally, I consider the keyer IC WB5BKL-unfriendly.  I have also read of a few design deficiencies – which have not bothered me.

All in all, a fun project.

cln – Nick
WB5BKL

Sunday, August 6, 2017

Importing N1MM ADIF export files into XLog


I like the N1MM Contest Logger program for Amateur Radio contesting.

N1MM is quite amazing for free software and is very well maintained. It is aimed just at contesting and covers most of the major contests worldwide. It is easy to install and – though there is a steep learning curve – once set up, solid.

It supports exports to Cabrillo (.log) for contest log submissions and to the ADIF (.adi) format for import into other logging programs.

I prefer to use Linux on my computers. My 'Amateur Radio computer' is a dual-boot machine just so that I have access to the N1MM Contest Logger and an antenna modeling program – both available only on Windows. To the best of my knowledge there is no Linux equal for N1MM.

My everyday logging program is XLog – a Linux program. After each contest, I move the results into XLog. Unfortunately a direct import of the N1MM .adi file into XLog leaves a lot to be desired for me.

N1MM exports only the start time – to 6 places (hhmmss). I like both the QSO start and end times to be entered and 4 places (hhmm) is more common. I note that QSO start and end times in a contest are almost always identical.

N1MM exports the frequency to the nearest 0.1KHz. XLog's default is to the nearest Khz.

N1MM exports both a sent and a received signal report. In the weekly CWT contests I enjoy, neither report is exchanged but N1MM defaults to reports of 599 for both. I prefer that those false reports not be entered into XLog.

N1MM does export the contest exchange, but I like to include the name of the contest following the exchange in XLog.  XLog has a different name for this field.

Here is an example of one record from the N1MM exported .adi file. Note that this is all one line:

<CALL:4>K5OT <QSO_DATE:8>20170802 <TIME_ON:6>190518 <BAND:3>15M <STATION_CALLSIGN:6>WB5BKL <FREQ:8>21.03258 <CONTEST_ID:6>CW-Ops <FREQ_RX:8>21.03258 <MODE:2>CW <NAME:5>LARRY <RST_RCVD:3>599 <RST_SENT:3>599 <TX_PWR:1>5 <OPERATOR:6>WB5BKL <CQZ:1>4 <STX:1>2 <APP_N1MM_EXCHANGE1:3>127 <APP_N1MM_POINTS:1>1 <APP_N1MM_RADIO_NR:1>1 <APP_N1MM_CONTINENT:2>NA <APP_N1MM_RUN1RUN2:1>1 <APP_N1MM_RADIOINTERFACED:1>1 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:11>OPTIPLEX755 <APP_N1MM_ISRUNQSO:1>0 <EOR>

And here is what I would like the same line to look like for import into XLog:

<CALL:4>K5OT <QSO_DATE:8>20170802 <TIME_ON:4>190518 <TIME_OFF:4>190518 <BAND:3>15M <STATION_CALLSIGN:6>WB5BKL <FREQ:6>21.03258 <CONTEST_ID:6>CW-Ops <FREQ_RX:8>21.03258 <MODE:2>CW <NAME:5>LARRY <TX_PWR:1>5 <OPERATOR:6>WB5BKL <CQZ:1>4 <STX:1>2 <COMMENT:15>127 CWT-1900 <APP_N1MM_POINTS:1>1 <APP_N1MM_RADIO_NR:1>1 <APP_N1MM_CONTINENT:2>NA <APP_N1MM_RUN1RUN2:1>1 <APP_N1MM_RADIOINTERFACED:1>1 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:11>OPTIPLEX755 <APP_N1MM_ISRUNQSO:1>0 <EOR>

I have highlighted the areas that have been modified.

I did this with a little Bash script and the sed (Streaming EDitor) command. Below is the operational part of the sed command for one of the little contests I enjoy, the CWT at 1900Z each Wednesday:

# CWT1900.sed
#
#
s/\(<TIME_ON:6>\)\([0-9]*\)/<TIME_ON:4>\2 <TIME_OFF:4>\2/
#
s/<FREQ:8>/<FREQ:6>/
#
s/<FREQ:7>/<FREQ:5>/
#
s/ <RST_RCVD:3>599 <RST_SENT:3>599 / /
#
s/\(<APP_N1MM_EXCHANGE1\)\(:[0-9]*\)>\([A-Z0-9]*\)/<COMMENT:15>\3 CWT-1900/
#
#

This sed file makes the four changes I listed above. Now I can run the .adi output files from N1MM through my little bash script and import them into XLog with no editing needed!

If you would like copies of my bash script for the three CWT contests, with the accompanying sed files and some informal notes, email me at my QRZ.com address.


cln - Nick
WB5BKL

Saturday, June 24, 2017

Adventures with a 'Thin Client' – a HP t5740


Recently I got interested in 'thin clients'. Small PCs with no moving parts. Here is a really good resource:


I like having a spare small profile computer to do my Amateur Radio logging function. The only real requirement (besides a little storage space) was an RS-232 port (the logging program receives data from my transceiver via RS-232).

I found a HP t5740W on eBay for $24 shipped, with power supply, 4G of ram and 4G of flash memory.


The thin client arrived (as expected) with no OS. I looked online for advice about the best small footprint Linux and found that my personal choice, Debian, was one of the top ten. I loaded a Debian Jessie “Net Install” iso on a USB stick and gave it a try just to see what would happen with the 4G flash memory. It fit!

But just barely - there was very little space left, maybe 11% or so after installing the logging program, XLog. That's a little tight, even for my tiny ham radio app.  I decided to attempt the installation of a disc drive, as mentioned in the “Mods” section of the 'Thin Clients' website above.  Here's the SATA connector on the motherboard.
That's an odd connector.  I am very lucky to have a Goodwill Computer Store fairly close. The knowledgeable folks there helped me pick out some potential 'donor' cables and the smallest 2.5” SATA drive they had (160Gb). Another $10 invested. Cheap works for me.

I followed the guide in the mods section for the HP t5740 (drill down: Home – Details – HP, etc). The big gotcha is the SATA data and power cables. Both must be modified to fit the connector on the mother board. Here is an image of a before and after mod for the data cable. The power cable will need a similar mod.
Click to enlarge the image.  All the Xacto wounds have now healed.  Note:  Band-Aids are remarkably difficult to apply if the cut is on your thumb...

Photos in the mods section mentioned above show the installation of the drive better than I can.  I did move the RAM memory as suggested.  

Success!  I now have two installations of Debian Jessie on the t5740, one on the 160Gb hard drive and one on the 4Gb flash memory. Via Grub, I can boot to either. 

Had fun.

cln – Nick
WB5BKL

Saturday, October 24, 2015

Linux: Finding Hams from a particular state in a list of Callsigns


Recently I wanted to extract the Texas hams from a long list of callsigns. As there were over several hundred calls in the list (and I am lazy), some automation was needed. I did it with a little Bash script and the Callsign Server at the University of Arkansas:






The callsign server at UALR can report the address the FCC has for hams in its database.



[Note: This script assumes you are familiar with Linux at the command line level and are running the Bash shell or similar]



First place the list of callsigns you need to search into a file with each call on a single line. Here is an example (add a few calls if you like):



W1AW
WB5BKL
K5HLA
W5CT



The list can be quite long. Save this as a file called:



call-list



Here is the Bash call-list.cmd script:



#!/bin/bash
# call-list.cmd by cln – WB5BKL 10/2015
#
for CALL in `cat ./call-list`
do
echo -e "\n"
echo "\$CALL="$CALL
echo -e "\n"
sleep 1
wget -O $CALL.htm http://callsign.ualr.edu/cdetail.php?call=$CALL
done
#



Copy and save this script as call-list.cmd. Make the script executable:



chmod +x call-list.cmd



Then place it in the same directory as the call-list file. I would strongly suggest an directory empty except for these two files.



Then execute the call-list.cmd:



./call-list.cmd





You should find a series of files have been created in the directory with the suffix: .htm  For example:

W1AW.htm



Then execute the following command (assuming you want only the calls that were in Texas:



grep -l "TX" *.htm



and you will see a list of the calls that have TX as part of their address field.

Or you could do this:



grep -l "TX" *.htm > TXcalls.txt



and the file TXcalls.txt will contain a list of the files that had TX as a part of the address. This list could then easily be edited to remover the “.htm” extension – and you have your list of hams in Texas.



Of course, you could use this to look for other states, or even calls that had “Extra” or “CT” or “John” as a part of their listing. Lots of possibilities here.

cln - Nick
WB5BKL