AmateurRadio.com

Announcements:

• Thanks, again, to Gamma Leonis for the opening and closing music for the show.
• LHS Merchandise is available at PrintFection and Cafe Press. LHS items make great Christmas gifts! Or, make a donation by clicking the Donate link on the website. Donations cover such things as the telephone lines, server fees, and more. Thank you!

Topics:

• Articles seem to be popping up at www.amateurradio.com designed to get us talking about Linux and Amateur Radio. The latest one is by Anthony, K3NG, self-proclaimed radio artisan. Our hosts discuss his assertions that:
  • Ham Radio Deluxe, DXLab, and N1MM software all beat any Linux offerings. (Note: Russ has found that both Ham Radio Deluxe and N1MM logger will run under WINE in Linux. DXLab, on the other hand, will not.)
  • There is more amateur radio software available for Windows than Linux.
  • CQRLOG is an adequate Linux program for casual logging, but not great for contesters.
  • “Quite simply, if one intends on using Linux exclusively in the hamshack they have to lower their expectations and requirements for logging and are between a rock and a hard place when it comes to contesting.”
  • He does praise fldigi, but still claims Windows software is better.
  • In summary, he thinks hard-core contesters may wish to stay with Windows. Our suggestion: run Linux and write a program that works better!
• Russ talks about his success with WSPR and Echolink.
• He found that instead of using “dpkg -i” to install the latest Debian WSPR package, use “dpkg -x”. You’ll extract the files to the current directory. You then run the program from a terminal session in your home directory using “./wspr”. If you run it that way, instead of letting it install, it seems to work a lot better. The Gnome launcher doesn’t seem to work with that sort of installation, but running it from a terminal works well.
• Russ has Echolink running under WINE v1.13. This version of WINE was chosen for it’s native support of PulseAudio, which made configuring EchoLink much easier. Russ’ node is on 146.225MHz simplex, Echolink node 54711.
• Russ then tells us why Echolink and IRLP are different and why IRLP might be “better.” (Hint: Echolink may not have an amateur radio anywhere in the link, while IRLP definitely uses a radio somewhere in the link.)

Feedback:

• Scott, HL2/AD7MI, sends his appreciation for the discussion in Episode 50 of his blog entry about his Ubuntu installation, and adds a note about problems with running CQRLOG under 64-bit Linux. He says you can install CQRLOG on a 64-bit machine, but it will only work with the 32-bit version of hamlib. Unfortunately, that breaks 64-bit fldigi, which expects the 64-bit version of hamlib. This issue has been reported on both the linuxham Yahoo group and the CQRLOG forum. Scott has also successfully installed Xastir, and is looking forward to receiving a MicroHAM III interface.
• Matt, KC8BEW, asks “What is a good and easy Linux distribution for a web server?” Russ recommends a plain vanilla installation of Debian server, without the X-windows environment, and either Apache or nginx (a light-weight web server).
• Dave, M0DCM, tells us of his success running fldigi and CQRLOG under Ubuntu 9.10 on an Acer Aspire A0751h netbook. Well done, Dave!

Donations:

• A very generous donation was received from Gerrit R. Thanks, Gerrit!

Contact Info:

• Contact Richard at [email protected], Russ at [email protected], or both at the same time at [email protected].
• Listen to the live stream every other Tuesday at 8:00pm Central time. Check the LHS web site for dates.
• Leave us a voice mail at 417-200-4811, or record an introduction to the podcast.
• Sign up for the LHS mailing list.
• Sign up for the MAGNetcon mailing list.
• Thanks to Dave from Gamma Leonis for the theme music.

Music:

• “Steel Concrete” by Mad Mav from the album “Black Sheep II”, courtesy of Jamendo.

Hello, everyone. We're coming to the end of another year and the world is aglow with holiday spirit. With that in mind, we bring you the second-to-last episode of Linux in the Ham Shack for 2010. We will have one more recording and release before the end of the year, so don't miss out on our holiday extravaganza.

We no longer broadcast video via Ustream, but we do have a live audio feed. Just point your streaming audio player at http://stream.lhspodcast.info:8008/lhslive starting about 30 minutes prior to air time (8:15pm CT). You can join in the chat room scene as well with your favorite IRC client. We are at irc.freenode.net in channel #lhspodcast. The channel is available 24/7, even when we're not doing a live show. Join in when you can and chat with other LHS listeners. During the live show, #lhspodcast becomes our chat room and our live connection with YOU.

Cheers and 73 from the LHS Guys

The Micro SD card I ordered arrived on Monday so I was eventually able to try installing the Google Android OS on my HTC Touch Pro. The delay turned out to be a benefit as I was able to take the advice of Eric SA5BKE who commented to my earlier post that he had found a better set of installation instructions to the ones I mentioned.

Still, as usual when I try to do anything with computers, if something can go wrong it will. First, the phone could not see the new SD Card. I had to format it with a utility from the SD Card Association. Then I messed up the screen calibration where you have to click, when prompted, on the corners of the screen, and wasted some time trying to recover from my mess-up. But eventually I was rewarded with the sight of the Android home screen on my HTC Touch Pro.

The effort was worthwhile. I really like the Android OS. It is so much better a smartphone operating system than Windows Mobile 6.1. You still feel that you are using a phone, not a Windows PC that has an annoyingly small screen. Making phone calls and sending text messages is really simple, as it should be. And once you have found out how the new OS is supposed to be used (since the download doesn’t come with a user guide) it’s easy to use.

I am a huge fan of Google – I have five GMail accounts and probably make hundreds of Google searches a week – and what I really like about Android is the way Google features are integrated into the OS. Until now I could never understand why people liked smartphones and would actually want to use them to answer email because my experience was based on trying to access GMail using one of the two awful web browsers on my Windows phone. But now I get a notification whenever a new email comes into any of my inboxes and I can either clear it or click on the email to read it in full or reply on a display designed to make full use of the small screen. I guess that’s how other smartphones work if you have a corporate mail server running Microsoft Exchange, but I’ve never had one.

I was also very impressed with the Google search widget on one of the virtual desktops of the home screen. It had a microphone icon so, out of curiosity, I clicked it and was invited to speak. A moment later it typed what I had said into the search box and was performing a search on it. Fortunately I hadn’t said something rude! I then had some fun composing emails and text messages without using the keyboard. Unfortunately the speech engine doesn’t recognize words like “comma”, “full stop” or “newline” as punctuation and formatting, nor does it recognize commands like “send.” But I was very impressed with the accuracy with which it understood what I said – the last time I tried voice input was at least a decade ago on a PC and I found it ultimately frustrating.

One of the applications I was keen to try out was Navigation, Google’s free satnav program based on Google Maps which is not available for Windows Mobile. I haven’t had a chance to test it in the car, but it seems like the full works, with a text to speech engine that barks directions at you. The optional but probably rather unnecessary satellite view looks rather cool, though I was rather less impressed by the route it suggested from home to Keswick, south-east of here, which involved turning right at the end of the cul-de-sac and going north, then west for a mile to reach the A66 before going east, instead of turning left and heading east which would save best part of two miles. My old satnav does that too, but that’s because the estate hadn’t been completed when the maps were made and it believes the top of the estate is still a building site.

The Android Market contains thousands of apps that you can download, either free or for a modest charge. However, sorting the wheat from the chaff seems like one of those things life’s too short for. It reminds me a bit of the early Windows “shareware” market when anyone who had taught themselves Visual Basic thought they would be the next Bill Gates by releasing some flaky software that did very little and usually crashed as soon as it experienced some condition the programmer hadn’t thought of.

There seem to be very few ham radio applications, though, and almost no really good ones. I saw quite a few apps to do with Morse, giving the lie to the idea that code is dead, but nothing that looked worth trying. The only professional quality radio application I could find is the new EchoLink client for Android.

My feelings about this have mellowed a bit since I wrote about it just over a week ago. Last Friday just before dinner I received a call through my EchoLink node from Practical Wireless VHF columnist and fellow blogger Tim Kirby, G4VXE, who was on his way home from work by train and called me using the EchoLink client for his iPhone. Though we’ve exchanged blog comments a few times it was very pleasant to speak with Tim for the first time. This was a contact we would be unlikely to make over radio and certainly not in that particular situation. Only EchoLink made it possible.

In the interests of research I had a conversation with myself using the EchoTest server and found the audio quality to be just as good as when I use my Kenwood TH-F7E to make contacts via my RF node. However the cellphone client has one disappointing limitation. You can’t make a direct connection using the cellular network. You have to use a communication option called “Relay” which only allows you to call other non-cellphone EchoLink users. It doesn’t allow other EchoLink users to call you. It’s a bit like having a radio and not being able to call CQ.

I was somewhat unimpressed by the Android APRS app, APRSdroid, not just in comparison with Lynn, KJ4ERJ’s APRSISCE for Windows Mobile, but even with the iBCNU app for the iPhone. The user interface is basically a console window: you can see position packets going out, and if you wish you can see raw packets of other users within a selected radius of your location. There is no support for messaging at all in the present version.

Tracking doesn’t seem to work very well either, unless you are also running another application such as Navigation that keeps the GPS on all the time. I think the problem is that the app tries to save power by turning on the GPS, waiting for a fix and then turning it off again until the next time interval. It didn’t work too badly when the phone was sitting in its charger cradle on my desktop, but getting a GPS fix when you are moving can take a very long time. There is a need for a simple APRS tracking and messaging application for Android but this has a way to go before it gets there.

The HTC port of Android OS is not an official release and has quite a few bugs and things that are still To Be Done. I’ve had the phone lock up and fail to respond to anything and have had to pull the battery a few times. There is no support for the built-in camera and the battery charge indication is completely fictitious. It’s also best not to use wi-fi as it warms up the phone and consumes a lot more power than under Windows Mobile.

Unlike most people I bought my HTC Touch Pro SIM-free and unlocked because I don’t like to be tied to a network. As a consequence I’m not going to be offered an upgrade for no extra cost when my contract runs out. I need to keep the phone for a while but I’d be more than happy to dump Windows Mobile because as a phone it’s too much hassle, even though it does allow me to run some pretty powerful applications. I hope that the issues with the HTC Android port will be resolved in order that it becomes stable enough and functional enough for me to use it on my phone all the time.

I was reflecting on what I wrote yesterday about the EchoLink app for Android and why I find it and similar developments disturbing. I thought it was because it made me uneasy having to face the fact that the internet and a cellphone appears to make ham radio redundant by allowing us to make the same contacts so much more easily without using the ham bands at all. Then I had a blinding revelation. Ham radio is not about making contacts. It is about not making contacts, or making them only with luck and some difficulty.

I almost stumbled across this truth a few months ago after I sold my first VX-8R to do APRS on a smartphone using Lynn KJ4ERJ’s excellent APRSISCE software. It worked far better than the 2m radio, allowing me to be tracked and exchange messages in places where there was no 2m signal. But I went back to using RF for precisely that reason. The smartphone didn’t provide the interest of allowing me to see how VHF RF propagates around the local terrain. The disappointment of not being tracked as I slogged up the mountain was balanced by my surprise when a beacon was gated from a location I wouldn’t have thought possible and the interest created in working out how it happened. There is also the technical challenge of finding ways to improve coverage and get a radio signal out of difficult locations, for which buying a smartphone is simply a cop-out.

When you look at other ham activities that remain popular or are even gaining in popularity it’s obvious that the interest is not in how easy it is to make contacts, but how hard. DXing isn’t about pressing the PTT and ticking another entity off the list a minute later, it’s about what you have to do – buy equipment, improve your antennas, learn about propagation, develop operating skills, be patient – in order to achieve it. People boast about the DX they’ve worked, but what keeps them interested in DXing is the places they haven’t worked and how hard it will be to work them. Dialling up a contact using an internet application has nothing to do with it.

Contesting isn’t popular because it’s easy to amass a winning score but because you need the best equipment, the best antennas and lots of skill to get even close. It isn’t meant to be a level playing field. That’s why many people dislike developments like reverse beacons and skimmers that take away some of the skill required.

QRP pursuits like WSPR or MEPT beaconing aren’t about making contacts at all, but just about seeing how far a whiff of RF can go. The excitement isn’t in being received by someone for the nth time, it’s that first barely detectable trace on the screen of someone or somewhere new that makes you punch the air (if QRPers go in for such QRO expressions of emotion.)

The thing about VHF FM activity is that for the most part it isn’t about the achievement of the contact at all. It’s just about being able to converse with people. When I was first licensed, before mobile phones and inclusive call packages, chatting on 2m FM was actually the best and certainly the cheapest way of keeping in contact with my local ham friends. But things have changed over the last 35 years and I haven’t been paying attention. I’m the dinosaur who wouldn’t disclose his mobile number to the radio club database because I felt that if someone wanted to talk to me about radio they could wait until they can contact me on the radio. But I suspect that everyone else has moved on. If they want to speak with one of their ham buddies they pick up the phone. Which may partly explain why the VHF bands these days are almost dead. Or even the development of D-Star, which provides some of the convenience of calling someone on the phone without totally abandoning use of the ham bands.

In only a handful of pursuits like SOTA and WOTA where the point is to make a contact direct using radio is 2m FM still used in what I would call a traditional manner. People will struggle to hear their signal report even if the activator is right down in the noise and get a feeling of having accomplished something when they are successful.

So EchoLink on a smartphone really doesn’t change anything. It already changed. Whether hams call one another on the phone using their phone number or their EchoLink node number really makes no difference. It has just been blinkered thinking on my part to have felt that if people hold ham radio licenses they ought to talk to each other using ham radio even if it isn’t the most convenient way of doing so.

An EchoLink app has recently been released for Android mobile phones. That makes two smartphone platforms – Android and iPhone – that can now be used to access EchoLink. Is this really a good idea?

Let me make it clear from the start: I like EchoLink. What I like about it is that it can be used to link repeaters in different parts of the country or the world, and even allows individual operators like myself to set up simplex voice nodes without the technical complications, expense and licensing issues of running a repeater, the aim being simply to get some interesting activity on what may otherwise be a more or less dead band.

I realize that contacts made using EchoLink are not traditional amateur radio point to point contacts, so I don’t want to start up the old “it’s not ham radio” argument again. But I don’t think the point of most contacts made on VHF FM is that you worked direct and exchange QSLs afterwards. They are just conversations between hams. The fact that the transmission went most of the way over the internet is of no more significance than if you used a conventional repeater. However it does matter to me that radios are used at each end, otherwise it’s internet chat not a radio contact in any shape or form. So far, that seems to be the case with most of the EchoLink contacts I have made, but for how long?

The trouble with EchoLink apps for smartphones is that they are VoIP apps pure and simple. They encourage the use of EchoLink as a VoIP chat mode. Smartphones are so popular now that I’m afraid this could become the dominant way of using the system. It could even replace ham radio handhelds. Users are going to ask themselves: Why bother carrying this goofy looking radio about when I can just use my phone? One more nail in the coffin of amateur radio?

David Rowe has released an early version of his low bit rate open source digital voice codec. Whilst this is certainly a significant achievement, I can’t get very excited about it for two reasons. First, it is incompatible with the AMBE codec used by Icom in D-Star, so it is never going to be able to work with existing D-Star equipment and it is not all that likely that it will be incorporated in future versions. And second, I still don’t see what benefits digital voice offers us as radio hams in the real world.

Digital audio gives you clear “fully quieting” audio up until the signal starts to be lost, when it quickly breaks up and you get nothing. Analogue audio experiences a gradual degradation as the signal gets weaker. Those who have used the two report that an analogue signal is usably copyable about 15 – 20% further out than a digital signal. I can understand that for some professional services nothing but clear copy will do. But we are amateurs who are supposed to be good at digging weak signals out of the noise. Is this really “progress”, in the context of what ham radio is used for?

The other reason for my antipathy to digital voice is that I question whether we need another voice mode at a time when VHF analogue voice operation itself seems to be in decline. Surely it would be better to be making more use of existing technologies like Echolink to create more activity for users of existing equipment than to introduce new digital modes that will have an even smaller number of users. I’ve seen D-Star radios up for sale because the original purchaser found there was hardly anyone to talk to, and D-Star has now been around for several years. I don’t see the availability of an open source digital voice codec changing that situation somehow.

I was in the shack making a few adjustments to the Echolink software configuration. The K3 was on 30m APRS with the speaker volume turned down to almost inaudible. Suddenly, at about 1410 UTC, I heard a buzzing type of interference. I looked at the TrueTTY waterfall and saw there were interference bars every 50Hz right across the screen, strong enough to prevent anything from being decoded.

50Hz is the mains frequency here in the UK. With a sinking feeling my immediate thought was that one of the neighbours had discovered a new way to make the HF bands unusable. Then I remembered that Lynn, KJ4ERJ had posted a screenshot of similar interference only the day before in an APRS forum. I checked back, and sure enough the interference Lynn had seen in Florida was exactly the same.

I don’t know what it is, but I don’t think even my neighbours are capable of generating interference that could be heard across the Atlantic. It’s still going strong 30 minutes later. I haven’t seen an HF band wiped out like this since the Woodpecker fell silent back in the ’80s. Well, at least I’ve got Echolink!