SOTA Activation Report: Stratton Bald Radio Expedition

I'm a recently minted General Class amateur radio license holder, with such poor radio reception at home that I decided to try portable operation from a better location. Participating in the SOTA program, my eldest son and I mounted an expedition to transmit atop Stratton Bald in North Carolina at 5360'.

We hit the trailhead at 11 on Saturday, October 6, 2012. With radio and camping equipment, our packs were 58 and 35 pounds. For us, that's a lot. Combined with some wet leaves on wet roots, I took a tumble on the way in which left me with a minor abrasion and the ignomy of flailing on my back like an overturned turtle.

We were the first to arrive in the meadow at the summit, so we were able to claim the high ground. Visibility was about 50 yards, due to fog. We set up camp in a breeze I estimate at 10 MPH. It was chilly. After nightfall, the fog closed in and we had some heavy rain overnight, with a little lightning a mile or so away. Visibility fell to about 25 yards at dusk. It was typical weather for Stratton Bald.

The plan was to operate first with a vertical antenna and then with a W3EDP horizontal. We set up the vertical and staged the W3EDP, with one end about 20' up the tallest tree we could find. Since we were traveling light, we left the feed line at home. We attached the antenna wire to a BNC-to-binding-post adapter on my Elecraft KX3, and we set up four 17' radials near ground level (strung across the grass -- generally not in direct contact with earth). The vertical component was 33' of wire zip tied to a 31' Jackite pole, with 2 ft' running horizontal to the radio. We used 22 gauge stranded wire, with Teflon insulation. My radio's antenna tuner only managed an SWR of 4-to-1, which surprised me.

Shortly before airtime at 1 PM, we found a contester (K6LA) using our primary frequency of 14.285, and at 1900+ contacts, he showing no signs of fading anytime soon. I made a *brief* contact with him -- my first (lifetime) QSO. There was lots of noise on 14.345, our alternate frequency, so we called CQ on several nearby frequencies, with no response. At about 1:10 I decided we'd call CQ on my published frequency for 15 minutes, despite the noise and throw in the towel on the vertical, if we didn't raise someone.

N1FJ responded from west Massachusetts within a couple of minutes and gave us our first spot at SOTAWatch, and a signal report of 57. NT1K also spotted us, as did N2YTF.

I *think* it is fair to say that I had a small pileup. At least, it seemed that way to me. The wind picked up about the time we went on the air, so I had a little trouble hearing. As I mentioned, I'm a very new ham, so I messed up a lot. Experienced hams rattle off their call signs quickly, and I think that experienced hams also *hear* and remember call signs quickly. I had to ask for lots of repeated identification in order to accurately record the call signs. Everyone was very patient and helpful.

One way I messed up is that I was just scribbling call signs, locations, and signal reports on scraps of paper. I neglected to accurately note the precise time for each QSO, and since I scribbled on multiple pieces of paper, I can't reconstruct the exact sequence of whom I spoke with when!  I started with a notepad and at some point I lost it in the folds of my jacket, so I started scribbling contacts on my cheat sheet of licensed frequencies.  (Next time I operate sitting cross-legged with a radio in my lap, I want to use a kneeboard with pre-printed log forms -- on waterproof paper.)

The fog turned to mist. The mist turned to rain and the wind picked up, so I had to shut down. Since we'd spent a full day in a thick fog, everything was getting damp, including our sleeping bags inside the tent. We were scheduled to return to the air at 4 PM with our other antenna, and planned to stay a second night. Since we'd been shivering in an open field, with damp clothes/sleeping bags/tent, and my stove had been difficult to light, and I was experiencing gastric distress, I decided it was time to get us off the mountain before we had an emergency It took us about 90 minutes to strike camp in the rain and to hit the trail.

By 4:30, we were half-way down the mountain, the weather warmed, and the sun came out! If we could have seen the future, we'd have stayed and held our second session and we'd have gotten to see the stars at night. (Since Stratton Bald is in a wilderness area, if you're on top and the sky is clear, the stars are awe inspiring.) On the other hand, if we'd stayed and encountered more heavy rain with high winds, we'd have had a problem. I'd rather be in the valley, wishing I was on the mountain, than on the mountain, wishing I was in the valley. Plus, I'd promised Mom to bring our son home in good health!

We achieved a number of firsts:

  • First activation of Stratton Bald (summit ID = W4C/WM-020). My son is very excited that we're the first to transmit from there.
  • My first QSO
  • First QSO with my new Elecraft KX3 transceiver
  • First portable operation
  • My first summit-to-summit activation
  • QSO with Canada
  • QSO with England
  • QSO with Germany

As best I can reconstruct it, here's my list of SOTA QSOs:


Call Sign UTC Time Location RST for My Signal Comments
N1FJ 1713 West Massachusetts 57 N1FJ followed up with a kind email, with helpful suggestions.
DK1AX 1715 Germany  

Confirmed afterward via email.  Klaus says, "I was in Germany - had about 700 Watts and a 3 element yagi.  You had a good signal here in SW Germany... Good condx - but you must have also a good station."

I guess the KX3 did pretty well, and my half-wave vertical wasn't such a bad idea after all.  Plus 5360' of terrain helped. ;-)

N1EU   Albany 57  
W0MNA   Leavenworth, Kansas 59 His signal was 59 too.  I wonder if he had a beam or an exceptional antenna.
N2YTF        
NT1K   Massachussets 55  
VE2JCW   Montreal 55  
G4OBK     44 G4 Oscar Bravo Kilo was very patient.  I had a tough time copying the 'B'.  Someone else was kind enough to interject and correct me when I read back 'R' instead of 'B' for the umpteenth time.
WA2UEM   New Jersey 56  
VA3SIE  

Mont Sutton, Canada

  I'd already called a sign off (QRT) due to the rain, but he called with a summit-to-summit activation, and I couldn't let that pass. Mont Sutton is SOTA ref VE2/ES-009


All this on 8 AA lithium batteries and 6 watts.  (Bad SWR caused KX3 to reduce power.)

There were more people to talk to, but the rain was a real problem.  For the last 2-3 contacts, I was peering at my radio under the edge of a poncho I'd draped over it to try an keep it dry.  The ink on my log was starting to smear and the pages were turning to mush, so I really *had* to quit.

The big observation from this trip -- Ham radio is really much more fun when you make contact that when you call CQ and get no response.  (Duh!)

The best part of the trip is that I've got a great Number One Son.  He did a lot of work, carried a heavy pack, was an extra pair of hands with setting up the antenna, and hiked for hours in the rain without a complaint.

All errors in capturing contacts accurately are entirely my fault, and the result of my inexperience.

I am *so* grateful to the hams who returned my call and patiently worked with me as I shivered and stammered and mis-copied.  THANK YOU!

 

Cell Phone Coverage
  • No cell coverage is available at the summit.
  • I could not reach 2 meter repeaters. If you have 2 beam, you might do better.
 
Getting There - Driving
  • From Atlanta, take I-75 north.
  • Take I-575 north.
  • Take GA-5 north.
  • In Copperhill, turn left on TN-68.
  • In Tellico Plains, turn right on TN-165/Cherohala Skyway
  • At 23.8 miles, you'll cross the TN/NC state line.
  • Park in the lot on the left at 35.34518, -84.03546.  (There's a real, paved parking lot.  It has a low, rock wall between the lot and the road.
    • The Benton McKaye trail is supposed to exit the lot on the north end (the end from which you were driving). In 2012, this section of the trail was closed.  You'll hike back up the skyway (northwest) about a tenth of a mile.  There's a gated road to your right.  (The gate is up the road a bit.) This was our trailhead.
 
Getting There - Hiking
  • Follow the trail along the state line.  (It is a two-track dirt road.)
  • There's a well-marked (in 2012) trail crossing in Cold Spring Junction, a couple of miles from the trailhead.  My memory is a little fuzzy here. There's a cross-trail, the Benton McKaye trail ahead, and a trail ahead and to the right, and it climbs.
  • The trail ahead and right is the old trail, from before the Benton McKaye trail re-routed the Fodderstack trail. You want the trail up and right.  It runs up the ridge to the Stratton Bald trail.  One of the guide books refers to this trail as being left nameless when Fodderstack was re-routed.  When we were there, this trail had a metal post with "54A" on it.   (It is #95 on some older maps, but 95 now continues straight, rather than going up+right.)
  • After lots of up-hill hiking, and duck-walking through rhododendron, you'll come to "the Bob Tee,"  with a trail running to your right, to Bob Bald and Stratton Bald.  Take the trail to your right.  (The other trail takes you back down to Fodderstack/Benton at Cherry Log Gap.)  As you walk it, pay attention to your left.  At about 0.1 mile, you'll hear running water and see a short length of white PVC pipe.  This is your best bet for water.
  • There is an alternate source for water just off the bald.  It was too cloudy for my taste, but it might be OK with a filter.  After you enter the open bald and climb to the very top, turn slightly to your right and there is a stand of green fir trees. In the hollow below the trees is the spring.  You'll find it as there are little side trails down to it.

 

 
 
 

 

Set Up DSP Radio 1.3.5 for Softrock Lite II 20 Meters

The Absolute Minimum – Just Get Some Output

  • Softrock Lite 20 meters “Make it go” (after copying to /Applications). Note: I’ve been told this is the wrong way to set it up. Acknowledged. This is just my record of how I got it to work the first time.
    • In Audio Devices (Window=>Show/Hide Audio Devices):
      • Set the ‘Input’ checkbox for the ‘Built-in Input’ device.
      • Set the ‘Output’ checkbox for the ‘Built-in Output’ device.
      • Close the Audio Devices window.
    • In Configuration (Window=>Show/Hide Configuration):
      • Set FA SY-1 frequency to 14.0475
        • Note: The default value for Oscilator nominal frequency is 114.2335
      • Press ‘Add Configuration’.
        • Set Input Gain and Output Gain to 20.
          • Note: Once, I found it worked better with Input Gain = 70, and Output Gain = 20.
        • Name this Configuration SR-Lite-1
      • Set the Active checkbox for SR-Lite-1
        • Note: Whenever you edit a Configuration, clear all ‘Active’ checkboxes first!
      • Close the Configuration window.
    • Connect an audio signal source to the Mac’s audio input jack. (I ran a stereo 1/8” patch cord from my iPhone’s earphone jack to my Mac.)
    • Play audio on your audio source. (I used a piano application on my iPhone.)
      • Confirm that you hear your audio on your Mac’s speakers, and you see the spectrum change in DSP Radio. If you don’t hear audio:
        • Plug earphones into your audio device, and make sure it is really generating audio. (This was a problem in one of my tests.)
    • Replaced the audio device with the input from your Softrock Lite.
      • You should see radio signals. If not:
        • Your antenna might be borked. If you have another 20m radio, see if there are any signals on it, when using the same antenna.
        • Try enabling AGC (Automatic Gain Control) on the Configuration window. (Remember to make the configuration row NOT active while editing!)
        • CW seems to work best. Set the Mode listbox in the left pane to “CW”.
    • One surprise from this exercise – When set up this way, the values under the “Rx Frequency” appear to have no impact on the frequency that is tuned. When I press Command and scroll, those frequencies change, but the tuned signal does not. (In fact, they are displaying about 3 kHz, and I’m receiving around 14 MHz.) Dragging the green bar is the only way I can get it to tune.
  • Updated “Make it go” based on instructions by Jas Strong (She has a video at http://www.youtube.com/watch?v=yEfToeTW8rU ). These work for the Ensemble RX II, which tunes from broadcast AM radio to about 30 Mhz.
    • Window=>Launch Audio MIDI Setup, and choose Window=>Show Audio Window.
      • Define a “Softrock” aggregate device in the left most pane, by clicking on the “+”. Double-click on it, to rename it to “Softrock”.
      • In the physical device list (right pane), select Built-in Output, and Built-in Input, and if you have a USB Sound card, also select it.
      • Do not close the Audio Devices window. Move it out of the way.
    • Window=>Show Audio Devices
      • Press Update Audio Device List, and resize the window so you can see all your devices.
      • Select the Softrock device for Input and Output.
    • Window=>Show Configuration
      • Press Add Configuration. Do NOT select the Active checkbox for New Configuration!
      • Find your Audio Devices (Audio MIDI Setup) window. Locate the “In” and the “Out” column in this window.
        • Where you see a zero, you don’t have a device. Where you see a 2, you have two devices.
        • The devices are numbered from the top, starting with zero. The input devices are counted separately from the output devices.
          • i.e. You’ll have input devices zero and one, and output devices zero and one, and if you have more than one input/output, you’ll have higher numbers too.
      • In the Configuration window, set Input I and Input Q to the input devices you want to use. If you set them both to zero and one, you’ll use the first input device and the first output device listed in the Audio Devices window.
      • Scroll a little to the right, and set input gain and output gain to 20
      • Now you can set the Active checkbox for your new configuration. As soon as you do, you should start hearing hissing, if your Softrock is connected.
      • Close the Audio Devices window and the Configuration window.

Ham Radio Log Programs

Here are some notes on ham radio logging and rig control software. These are not real reviews, in that I didn’t look at all the features for most programs. If I found a fatal flaw which would prevent me from using a program at this point in my ham-life, I looked no further.

I have to have:

  • IOTA (directly, or via custom fields).
  • SOTA (directly, or via custom fields). Must distinguish between summit I activated and summit I chased. Must accurately record S2S activation+chase.
  • Accepts as little as a call-sign and a date+time (i.e. does not demand other fields in order to create a record)
  • Captures operating location (could be combined with SOTA/IOTA)
  • Upload to LoTW.
  • Upload to SOTA.
  • CSV import/export

Ham Radio Deluxe v5

  • Windows program.
  • This has lots of pieces, but right now I’m looking only at the logbook.
  • Does not support SOTA.
  • Does support custom fields. You can customize the captions for the custom fields.
  • I like the automatic lookup of related info that it does.
  • Data store is a Microsoft Access database. Can be tweaked to use any ODBC database.
    • See http://wiki.ham-radio-deluxe.com/index.php?title=Setting_up_Logbook_Databases
  • Supports eQSL and LOTW
  • This one is interesting.

dxLab

  • PC program
  • 4.8 rating on eHam.net
  • 8 user-defined items with captions. Config for these is split across multiple screens, but I was able to configure them as desired.
  • It uses a funky downloader/installer/wrapper. I have concerns about not being able to store the setup program locally, in case they disappear. Manual download/install instructions, which address this issue, are at http://www.dxlabsuite.com/dxkeeper/download.htm .
  • Data store is a Microsoft Access database.
  • Supports eQSL and LOTW
  • This one is interesting.

AMATEUR CONTACT LOGGER by N3FJP

  • See http://www.n3fjp.com/ACLog.htm
  • $25
  • PC program
  • 4.8 rating on eHam.net
  • It does have 4 “Other” fields, which could handle SOTA. You can customize the captions for the custom fields.
  • Captures Band and Frequency. If you enter Frequency, it does NOT calculate Band.
  • Fields have little editing. e.g. If you enter “5” or “5W” in Power, it records those characters.
  • No SOTA support.
  • No control over exported fields. It exports the entire records, with no column titles. Upload to SOTA would be labor intensive.
    • Maybe I could export the whole DB, import/attach it in Access, and write Access code/tables to manage SOTA export.
    • Maybe write Perl/Python/Ruby script to convert exported records to LOTW format.
    • A free program called ASC2ADIF is reported to do this: http://kh2d.net/software/
    • Excel/ADIF converter - http://www.mydarc.de/DL1HW/
    • See also http://www.dxzone.com/catalog/Software/Log_Converters/
    • How would a non-SOTA-aware program handle tracking of whether a record was SOTA-uploaded? I think I’d have to do that (perhaps just mentally).
  • Looks like a proprietary data store. (Maybe fixed length records with fixed length fields.)
  • This one is interesting.

Logger 32

  • PC program
  • 7 User-defined fields, and you can set the caption for each one – in some screens but not others. Not all 7 can be displayed in the ‘grid’ view.
  • I dislike it.

Win-EQF

  • PC program
  • $60
  • 4.8 on eham.net
  • Looks like a MS-DOS program
  • Has 2 fields whose captions can be customized.
  • I dislike it.

Unusable items are below this line.


CommCat

  • Windows program.
  • This has an iPad/iPhone remote control app which is really cool.
  • The log book does not support SOTA and it does not support custom fields. I could live without explicit SOTA support, but I’m going to capture summit IDs for export+upload to SOTA.
    • This is a deal-killer for me.

RumLog

  • Popular Mac program.
  • It requires entry of sent and received RST signal reports. I don’t always record these accurately. I’d be willing to enter a bogus report like 00, but it insists on a valid signal report. I don’t want to make one up.
    • This is a deal-killer for me.

MacLoggerDX

  • Mac program.
  • This has lots of pieces, but right now I’m looking only at the logbook.
  • $95 seems a little pricey for something I could do with an Excel spreadsheet.
  • It really wants me to enter time including seconds. Since I enter many QSOs after the fact, this is a bother.
  • I’d like to see a date+time picker, rather than manual entry of the digits.
  • The log book does not support SOTA and it does not support custom fields. I could live without explicit SOTA support, but I’m going to capture summit IDs for export+upload to SOTA.
    • This is a deal-killer for me.

Aether

  • Mac program.
  • Straightforward.
  • The log book does not support SOTA and it does not support custom fields. I could live without explicit SOTA support, but I’m going to capture summit IDs for export+upload to SOTA.
    • This is a deal-killer for me.

Log4OM

  • PC program.
  • The log book does not support SOTA and it does not support custom fields. I could live without explicit SOTA support, but I’m going to capture summit IDs for export+upload to SOTA.
    • This is a deal-killer for me.

XMLog

  • PC Program
  • The log book does not support SOTA and it does not support custom fields. I could live without explicit SOTA support, but I’m going to capture summit IDs for export+upload to SOTA.
    • This is a deal-killer for me.

E-MU 0204 and Parallels Don't Play Well Together

I bought an E-MU 0204 USB sound card to go with my Softrock Lite II (built for 20 meters). I wanted to get 96 kHz sampling, in order to expand the tunable range on my Softrock. I wanted USB because I’m running my SDR software in a VM, so I can run it in Windows XP or Ubuntu 12. (Few SDR packages work on Windows with a sound card based SDR.)

I installed the E-MU drivers, rebooted the VM and boom - it crashed. I removed, reinstalled, rebooted several times. The VM is just unstable when the E-MU is connected to it and the E-MU software is installed. When the VM crashes, Parallels recognizes that it was a Parallels problem, and it goes into its let’s-report-a-Parallels-crash routine. (This is with Parallels Desktop 7.0.15104, Revision 778994; July 10, 2012 and Windows XP Pro with all patches applied through July 27.)

I did a little Googling, and found someone else who had a problem with an E-MU 0202 USB causing Parallels to crash with Windows (Win 7 and Win XP in his case). He found happiness by using VMware Fusion. I installed VMware Fusion 4.1.3 (730298) and imported my Parallels VM. E-MU 0202 works just fine in Fusion.

In general, I like the feel and performance of Parallels, but this is not the first incompatibility I’ve found with Parallels. VMware does a more trouble-free VM, in my experience.

DXLabs DXKeeper Content Not Fitting

I installed DXLabs DXKeeper on Windows XP, and it was ugly. Content didn’t fit within the controls. e.g. Button labels wrapped (and the button wasn’t big enough to display the wrapped content). Drop-downs were unreadable.

The standard suggestion for addressing this sort of problem is to visit Display setting, and ensure that you’re using Normal font size. Been there. Done that. (Right-click Desktop, Properties, Settings, Advanced, Normal Size (96 DPI).)

I found that following this same path, setting DPI to 99%, rebooting, setting DPI back to 100%, and rebooting – that cured it.

Brief Catalog of SDR Software on Mac OS X

Here are some of the SDR programs I’ve looked at.

#My environment#

  • My primary PC is a Macbook Pro, running OS X Lion. I’ve got VMware and Parallels to run Windows and Ubuntu. I’d prefer a native Mac program, because that’s simpler, and I’ve seen some anomalies in running SDRs in my VMs which might be because they don’t get 100% of the CPU power.
  • My SDR hardware is a Softrock Lite II built for 20 meters.
  • Sound Card: Both my Macbook’s built-in audio and an E-MU 0204 USB. When I run in a VM, the VM emulates a sound card derived from the Mac’s built-in audio, and I can also connect the E-MU USB to the VM as a USB device, so the VM sees it as if it were a native E-MU 2024.

Note: If it looks like NOTHING is coming in from the sound card, hook up an audio source (such as your iPod headphone jack) to the audio input on your computer, and see if Sound Recorder can record it. Get that working. Then feed your audio source into Rocky (or other SDR program). It won’t render as a coherent audio signal, but you should see lots of spectrum activity. This allows you to separate audio input issues from SDR hardware issues.

#The Programs#

  • Rocky 3.7
    • URL: http://www.dxatlas.com/Rocky/ (see also http://www.wb5rvz.com/sdr/sr_lite_ii/07_extconn.htm)
    • Platform: Windows XP
    • Works: Yes
    • Advantages:
      • Simple.
    • Disadvantages:
      • No DSP beyond bandpass filter width.
      • I only get 44 kHz from my sound card in my VM. The Mac hardware does 96 kHz.
      • Reportedly has problems on Windows 7
    • Make it go (after installing):
      • View/Settings, Audio tab:
        • Select I/O Input Device to match where the Softrock is plugged in
        • Set sampling rate to 48 kHz
      • View/Settings, DSP tab:
        • Set Local Oscilator to Single Band
        • Set Local Oscilator to frequency 14047500
      • View, select Waterfall
      • File/Start Radio
  • DSP Radio 1.3.5
    • URL: http://dl2sdr.homepage.t-online.de/
    • Platform: OS X
    • Works: Yes, but…
    • Advantages:
      • Works with OS X.
      • 96 kHz bandwidth with the native Mac audio input
    • Disadvantages:
      • Very ‘fiddly.’ It is easy to get it so messed up you have to uninstall/reinstall.
      • Its display sometimes freezes, and you have to restart it.
      • I can’t figure out how to set the width of the received signal.
      • No DSP beyond bandpass filter width and filter shape.
    • Make it go” (after copying to /Applications):
      • See http://www.kleinfelter.com/content/set-dsp-radio-135-softrock-lite-ii-20-meters
  • CuteSDR
    • URL: http://sourceforge.net/projects/cutesdr/
    • Platform: OS X
    • Works: No. Does not support Softrock Lite.
  • Gqrx
    • URL: http://www.oz9aec.net/index.php/gnu-radio/gqrx-sdr
    • Platform: Linux
    • Works: No. Does not support Softrock Lite.
  • SdrNetSetup
    • URL: ?
    • Platform: ?
    • Works: No. Supports “network connected software defined radios”
  • QtRadio
    • URL: http://napan.ca/ghpsdr3/index.php/QtRadio_Installation
    • Platform: Windows, Linux, OS X (maybe)
    • Works: I’ve seen some guy’s posting “After several days of hacking I finally have a running version of QtRadio on my Mac”, but I haven’t found him or his hacked version yet.
    • Advantages:
      • ?
    • Disadvantages:
      • ?
    • Make it go (after installing):
      • ?
  • someAppThatWorks
    • URL:
    • Platform:
    • Works:
    • Advantages:
      • ?
    • Disadvantages:
      • ?
    • Make it go (after installing):
      • ?

… more to follow

Assemble a Coax Cable With BNC Clamp Connector From eBay connekt

 

I recently purchased some BNC connectors for PL-174 coax from eBay seller connekt.  It took me a little while to figure out how to use them, so here's my notes.

  • Cut cable to desired length.
  • Put tape backstop on cable.  (This is to keep the parts you slide onto the cable from sliding far down the cable.)
  • Slide the screw connector onto the cable. (Item 1 in the image above -- The part of the connector through which the cable exits.)
  • Slide on the big-hole metal washer.  (Look closely.  One has a little bigger hole. Item 3 in the above picture.)
  • Slide on the rubber ring. (Item 4 in the picture.)
  • Slide on the little-hole washer. (Item 5 in the picture.)
  • THEN strip the end of the cable.
    • strip 3/4" of jacket
    • push back the braid
    • Slide on the braid-spreading washer - tube-end first, washer last.  (Item 2 in the picture.)
    • shove it on snug
    • splay the braid
    • trim excess braid
    • strip dielectric, leaving 1/16" (a little less than thickness of the braid spreading washer)
    • tin and trim center conductor of the cable. Leave the conductor about 1/16" too long for the pin.
  • screw it all together and test.

This uses only contact/pressure to make contact between the center wire of the cable and the inside of the pin.  I did one this way and I did one soldering the wire inside the pin.  It is really tough to solder the wire inside the pin!  We'll see if one lasts longer than the other.  If the contact-only pins last, these are nice, easy-to-use connectors.  If they don't, I'll stick with crimp connectors.