AmateurRadio.com

Heathkit announced today they have reached an agreement to acquire the assets of Radio Shack for $300M, blocking efforts from mobile wireless carrier Sprint to acquire a large portion of the struggling and now bankrupt North American consumer electronics retailer.  No further details were mentioned by Heathkit other than they “had big plans” and “everyone should stay tuned to the website for details.”

Radio Shack CEO Joseph Magnacca was quoted in a press release as saying “We are very happy and excited about the pending transaction with Heathkit.  The Heathkit team has shown us they have a more viable business plan than Sprint, and our creditors agree that the Heathkit team brings a higher level of management, leadership, and strategy to Radio Shack, more than the company has ever had.”

Immediately after the announcement amateur radio online forums were alive with discussions and speculation on when closed stores would reopen.  Several commenters reminisced about the days when Radio Shack offered amateur radios and components.  One person noted how difficult it is to get good 68k ohm resistors and Radio Shack could chart a course to profitability if they just stocked these resistors.  Others bemoaned Radio Shack’s practice of asking for customer addresses, claiming it was a front for NSA information-gathering efforts.  Several commenters agreed that Radio Shack should offer a vacuum tube code practice oscillator kit.

Some things are BFDs and some things just aren’t.  What are BFDs?  Well, son, this video might help you out.  BFDs would include passing healthcare legislation, your first kiss, discovering plutonium, or your parachute not opening.  There are two news items in amateur radio right now that, despite all the hubbub, aren’t BFDs.

Remote operation from anywhere is now allowed for DXCC awards.  ARRL will now allow contacts from remotely-operated stations to be submitted for DXCC awards, regardless of where the control point is located.  This seems to be a BFD for many people because of instead of buying a multi-giga dollar megastation, which was the previously accepted way to buy your way to DXCC, today with modern technology and better living through chemistry you can rent a megastation with a credit card and operate it with your favorite computing device from the comfort of your meager home station, hotel room, or police station drunk tank.  Why is it not a BFD?  Remote operation contacts were allowed for DXCC credit before, the only thing that has changed is where the control point is allowed.  The contact is still made over the air.  This isn’t like Echolink computer-to-computer contacts.  The remote station must be located within your home DXCC entity.  If you still want to get your DXCC the old fashioned way, you can.  DXCC is about personal achievement, and how you got it is a BFD to you, not anyone else.

The FCC will no longer issue paper licenses.  Why is this not a BFD?  There are several reasons.  The online ULS record is considered your official credential.  If you want a paper license, you can go to the ULS, download a PDF, and print it out.  One can also request the FCC send them a paper copy.  What is BFD is that the FCC will save $304K a year with this change.

Code-is-not-dead prognosticators and hand-wringers will be happy to hear Asus is touting a new smartphone camera feature with Morse code.  The smartphone feature has something to do with dual cameras and exceptional zoom capability but unfortunately appears to have no use of Morse code.  But a tip of the hat to Asus marketing folks for using code!

I’ve been considering getting a Raspberry Pi for awhile.  Several folks have asked me if I would port my Arduino Keyer code to it.  So I decided to take the plunge and acquire a Pi from Newark / Element 14, along with some “fixins”.  I got the Model A Pi, along with a WiFi dongle, and a cute little enclosure.

Big Things Come in Small Packages

I didn’t realize just how small the Pi was until I held one in my hand.  It’s just amazing this is a full blown computer.  It’s quite a leap from the VIC 20, the first computer I used 30 years ago as a teenager.

Raspbian Installation

The Raspberry Pi was surprisingly easy to fire up.  I bought a 16 GB SD card locally and burned a copy or Raspian on it.  After plumbing up a monitor to the HDMI port and connecting a USB keyboard and mouse, the unit booted right up, displaying messages familiar to anyone who runs Linux.  A few minutes later I entered startx and I was in XWindows.  Of course I just had to bring up a terminal window and verify this was really a ‘nix box and run top.

Nifty Little Pi Enclosure

Now that I have my Pi humming away, what projects should I do?  As I’ve mentioned a few folks have inquired about porting my keyer code to the Pi.  Googling around I found someone has ported the Wiring development platform , which is the basis for the Arduino environment, to the Raspberry Pi and aptly called it Wiring Pi.  Naturally it’s not 100% compatible and it’s not as easy as just plugging in the Arduino IDE and uploading compiled code.  I’m debating whether to take this approach of getting the keyer code to run under Wiring Pi, or just start from scratch with good old C and gcc for the compiler. I could get the core functionality going and then port over parts of the code from the Arduino for ancillary functions, if it makes sense.  Certain things don’t make sense to port, like the CW memories code.  On the Pi you don’t have to deal with EEPROM like you do on the Arduino.  Anything that needs to be persistent across reboots can just be written to a good old file on the file system.  While certain things like persistent memory and sound support are easier on a Pi, deterministic and precise timing, which is needed for CW timing, is challenging on a multi-tasking environment like Linux.  This realtime kernel may be just the ticket.

Compared to the Arduino, there aren’t a whole lot of interfacing pins on the Pi.  To really get the power of this board you need to do I2C.  I’m thinking about what it would take to port my antenna tuner to the Pi.  That project uses I2C for controlling many relays, but there is also a need to monitor the voltages of the SWR bridge.  The Pi doesn’t have this capability natively, so an I2C device would be needed to supply this functionality.

All in all the Raspberry Pi is a versatile and powerful little board.  To get my feet wet I think I’m going to write a little bare bones C and see if I can get a basic keyer working and see where this takes me.  This is going to be fun.

The World Radiosport Team Championship 2014 team has posted data on the radio equipment and software used by the teams.  There are a few interesting take-aways for me:

The top two radios used are no surprise, the Elecraft K3 by a wide margin at 64%, and the Yaesu FTdx5000 at 7%. The third choice surprisingly was the modest Kenwood TS-590 at 6% usage.  I’ve often thought this rig is one of the best in amateur radio today based on the price, features, performance, and value.  Despite Kenwood getting the number 3 spot with the TS-590, there was only one other Kenwood rig used, a single TS-850.  Ten Tec had a meager showing with two Orion II rigs.  Various other Icom and Yaesu rigs rounded out the statistics.  I find it sad that Kenwood doesn’t have more product offerings in these statistics.  The data suggests that there’s an opportunity in the market for another high performance $2.5K to $3K USD compact rig.

For software I expected the N1MM contest program to be the most popular choice, however Win-Test was used in 68% of the stations and N1MM garnered only 25% usage.  Perhaps it’s time I try Win-Test.  Despite the price of the N1MM program being attractive, the lack of source code for this freeware program has concerned me.  Win-Test costs 50 Euros or about $67 USD, however with the features listed it may be worth it.  There must be some “secret sauce” in the program that hardcore contesters like.