Tag: Ham

What is the point of ham radio

radio : by Tommy — October 16, 2017, 09:14AM
radioI hear this question quite a bit. "What's the point of ham radio?" usually tied in with "You know you can just pick up a phone and call someone right?" or "The internet lets you chat across the globe too, you know?"
Yes, I know it's possible to accomplish a task in a seemingly more efficient way, but that's not what makes ham radio interesting. What's the point of sailing, fishing, rock climbing, hiking, gaming, hunting, knitting, auto racing...? There are more efficient methods of travel, attaining food, clothing, etc. So what's the point of any hobby, really? Those who enjoy the hobby will say "it's fun", but that's not a very clear answer because what is fun to one person is boring to another.

With ham radio, like any other hobby, it's a pastime - one that happens to have a lot of electronic underpinnings.

In fact, I liken it to catch-and-release fishing more than chatting or phone calls. Yes, you talk to people, but the majority of hams don’t care about the content of the conversation as much as where the other party is.
In my fishing analogy, I say casting out your lure is like calling out on the radio. "Will I get a bite?" = "Will someone hear me?"

Someone probably will hear you and answer your call. So you respond and find out how well they're able to hear you, where they're from, and perhaps some other information about them. That's like reeling in a fish to measure and weigh them. "Wow! This guy's in the mountains of Nepal!"/"Wow, what a big fish!"
Sometimes the "fish" isn’t very big, the radio contact may be relatively close distance to you, so you say so-long and "cast" again - hoping for bigger fish.
Or maybe a rare fish...
Or a hard-to-catch fish...
Or a relatively famous fish...
Or maybe you want to try fishing with different equipment (bigger, smaller, new technology, relay through a satellite, etc) and see if that helps or hurts what you "reel in". That experimentation is what interests me personally. I'm into making radio contacts with a relatively minimalist (low power) setup from someplace other than home.

It’s a pastime full of opportunities to experiment with radio equipment to see what you can reel in.

Taking things a step further, one of the reasons ham radio creeps into the news cycle from time to time is thanks to ham radio's unique ability to communicate over long distances using no infrastructure at all. There's no infrastructure to be damaged in a natural disaster that would disrupt communications, there's no infrastructure vulnerable to a cyberattack that would knock out the ability to send and receive information - no, amateur radio is a do-it-yourself means of communicating over distances without relying on others to provide all the "in between" links.
So, yes, you can pick up a phone and call someone on the other side of the country (assuming you know their phone number), but that requires you to a) pay for such a service and b) be reliant upon service providers to ensure that link stays available when you need it. Ham radio has no such reliance on others. This is why you see ham radio - old as it may seem - always coming in to fill in the gaps where more modern and sophisticated systems fail.

CW Works

radio : by Tommy — February 16th 2016, 04:32PM
radioI posted earlier about my new MountainTopper Radio. They're only being made and sold in small batches so I was never able to get my hands on one until January 2016. When I visited the site and saw they were for sale, I jumped at the opportunity to secure one of the little radios and it arrived a couple of weeks later. I had a business trip to go on so I wasn't able to fully get to know the radio until I got home. After I got home, the following Monday I got on the radio with the manual open on my computer. I got a feel for all the features packed into the limited number of buttons. After a while I really got the hang of it.
The next night (Tuesday) was a NAQCC Weeknight Sprint (a mini 2-hr radio contest) and it was also a night when class was cancelled. The 40m band was in pretty decent condition that night and I easily nabbed 5 different states. At the conclusion of the contest I made a couple more contacts and decided I loved the little radio. I've been using it nightly for the past week, making at least one QRP CW contact each day ...and that's where I've learned something.

It's something I heard guys say over and over again and, like you reading this, I've seen others write about: CW Works.

It's not just some old geezer claiming his tastes/choice mode is superior. What I mean to say is when the bands are great or incredibly noisy, CW still gets through. To modify the slogan "When all else fails... CW". Sure, digital modes get through when conditions are equally rough. (I first learned that late at night during Field Day one year using PSK31. Voice was impossible. It was too noisy and at night 20m usually will not propagate. I couldn't hear anything but there on my computer screen was a host of PSK signals "down in the mud" that the computer was able to identify.)
The "trouble" with digital modes is they require more gear (a computer). For camping/backpacking/portable operations, that's more gear to bring with you and (usually) another power source. CW requires less setup, less favorable band conditions and fundamentally has not changed much since the early days of radio. What surprised me over my week of CW contacts is how the band conditions would change from day to day, but I was still able to make contacts.

As someone deeply interested in education and how the human brain works, Morse Code is extremely fascinating. For the newcomer/outsider it's an unintelligible string of dits and dahs. To the trained ear it's a steady stream of letters, numbers, words and phrases sent with the simplest radio equipment out there. Learning Morse Code can be tricky and, like a diet or exercise, takes dedication and a committed personal desire to want it. When you do finally get the hang of it at whatever speed (most would contend 5wpm is minimum threshold), there is something strangely relaxing from fully utilizing your mental capacity. (I know programmers and mathematicians can attest.) When you're "in the zone" and working CW you're focused on the conversation, it requires mental concentration but is also relaxed. (I'm no runner but I hear endurance runners have a similar feeling.)

Ok, so why does CW work?
A CW signal is just a modulated signal. It's the presence/absence and timing of a carrier. That's it. You don't have to worry about distortion really. You'll either hear that carrier or you won't. The other party is turning it on and off - so long as you can hear something, the intelligence is there. When conditions are bad, when your signal is really, really weak, it might be harder for the other station to hear you but they're still hearing you. With voice you have to be able to hear them well enough to detect the various parts of speech. Anyone that has ever heard a sideband QRP station knows how difficult that is. The poor guy on the other end might be screaming into his microphone but if propagation isn't carrying the signal enough you just won't hear them. With CW, if you can hear something, that's enough to copy them. (Now, whether or not they'll hear you is a matter of your signal strength.)
Taking this concept one step further is why so many QRP guys are CW guys. QRP voice can be endlessly frustrating. When QRP SSB works, it's cool, but more often than not conditions will not permit QRP SSB. When it does work, it's usually really weak. With CW, like I said, it's either there or it's not. With CW, a QRP signal is only one S-unit down from a 599 signal report. That's 1/20th the power used for a still perfectly legible signal! QRP is plenty good enough to work all of North America from my home in Texas. If I were to move up to a full 100W, that's enough to work the world! With SSB, you need some serious antenna gain and a good sized amplifier to reliably work the globe.

So, chalk another one up to the CW believers column. You don't have to believe me. You don't have to love CW. (I'm not a CW purist or a digital mode hater either!) I'm just fascinated that no matter the conditions, CW works.

MountainTopper Radio

radio : by Tommy — February 16th 2016, 10:25AM
radioIt's been quite a while since I last made a post but this is one I have to mark the occassion for. For the better part of the past 6 months I've had my eye on the MountainTopper Radio. It's a small QRP CW radio designed by Steve Weber, KD1JV, and sold by LNR Precision. The model I got is the 3-band version. (At the time of this writing there are rumors stirring about an upcoming 5-band version. Since I'm really only active on 40m and 20m, I'll pass on the 5 band model.)

The radio is very small - about the size of a deck of cards. There's no internal antenna tuner or battery. The volume, RF gain, and filter settings are fixed so there's no need for adjustment knobs. Nor is there a tuning knob. Tuning is done by two push buttons (UP and DOWN) that nudge the VFO up or down 50Hz. Holding down the button will change the frequency in 100Hz steps at a rate of 10 steps per second.
The elimination of knobs on the face of the radio allows the radio to pack very small. It's so small in fact, I was moved to get a Micro key from KK5PY. It has to be the smallest paddles I've ever used. To match the small size, the MTR can be powered by a 9V battery or a small 12V LiPo battery pack. Pack in some earbuds, a wire antenna, and a paper logbook and the whole kit fits into a small padded, zippered case ready to go. It's a radio meant for travel! I can't wait to take it on the road with me.
I've been using it to make QRP CW contacts each day for the past week and I'm going to try to get QRP Worked All States on 40m CW. (Paper QSL cards only!)

Hopefully I'll have more posts about this remarkable little radio in the future. To any ham considering purchasing one of these radios, I'm highly, highly impressed and absolutely love the compact size and performance of the radio. I can't recommend it enough. (Also I still have my Elecraft KX1, but the MTR is smaller and less to fuss with!)

WebSDR on Raspberry Pi

radio : by Tommy — August 10th 2015, 05:12PM
radioIn Fall 2014, I setup my first Raspberry Pi WebSDR receiver for the 40m amateur radio band. In late July 2015, the Raspberry Pi stopped working at all. Once I hooked a monitor up to it, I learned the SD card had been corrupted. I'm now in the process of rebuilding the receiver and will be updating the steps required to setup this project on my project page.
The receiver hardware itself is fine and operational, it is only the WebSDR host (Raspberry Pi) that is out of commission.

For now the WebSDR and ISS iGate must connect to my home network via a wireless link from my ham shack behind my house. I'm in the process of digging a trench to run a network connection out to the shack so I don't have to wrestle with spotty wifi coverage. I'm going to be running fiber optic for the main run for reason I'll explain that in an upcoming post.

HOWTO: Configure Hamlib for Linux Hams - Part 2

radio : by Tommy — December 3rd 2013, 06:48PM
radioThis is a continuation of a two part series about how to configure hamlib for Linux ham radio users.
To get started, be sure to read through Part 1.

In the last post, I pointed out that hamlib was create to simplify the once fragmented world of computer control for amateur radio. With hamlib in place, developers can interact with hamlib which serves as an abstraction layer of sorts for software development. Developers don't need to worry that you're running a particular model of radio, so long as you get your radio working with hamlib, your radio is supported.
I'm going to assume you have /dev/radio and /dev/rotator already configured (since we did that in the previous post). Now, we're going to configure the daemons (servers) that allow a myriad of radio related applications to interact with your amateur radio equipment.

Daemons
Hamlib centers around two core daemons: rigctld and rotctld. The daemons receive commands from applications via TCP. It is possible to have these daemons controlled via the network if you so wish. That functionality is a bit beyond the scope of this article, but the concepts below are exactly the same and just requires the correct ports be opened. Speaking of ports, rigctld and rotctld use ports 4532 and 4533, respectively. Also note that there is no security built into these devices. Should you need external connectivity, you should create an SSH tunnel.

Find your equipment
The first step in configuring rigctld is to find if your particular radio (and rotator for rotctld) is supported. Here is a list of all supported radios for rigctld (chances are, if it's a modern radio with computer interface, it's supported). For rotctld, things get a little more difficult. In order to see if your rotator controller is supported, you need to identify which protocol is supported. As I stated before, my rotator is a Yaesu G-5500 and my interface is the ARRL Satellite Tracker Interface. I know from prior experience and documentation this uses the EasyComm 1 protocol. Armed with this information I can proceed with configuring each daemon independently.

Gathering Radio Settings Information
Now that we know our radio is supported, we can determine all of the command line options necessary to setup rigctld. My radio is a Yaesu FT-847, so I'll be using that for my examples - adjust accordingly. For starters, we need to be on the command line so open Terminal or a shell. This whole time I've been referencing rigctld, but for initial configuration and testing we're going to use rigctl. The two programs are essentially the same except the daemon is "headless" (no uder interface) listens for commands via a TCP port. rigctl gives us an internal command line wherein we can issue commands to check communication with our radio. Both rigctl and rigctld require 3 pieces of information, although you can get by with only 2 (we'll give it 4 just to be specific and safe).
The first information rigctl wants to know is what kind of radio are you using. You can find rigctl's list of radios by issuing the following command
rigctl -l

(That's a lowercase L, by the way - short for "list") That's going to be a long list though. You could scroll and find your radio or you can pare it down with grep
:
rigctl -l | grep 847

That's more like it. Now I only see the line of info for my FT-847. The key information we're after is the number on the left. In this case, 101.

The other pieces of information rigctl wants are the device name and the speed at which we'll communicate with the device. For the name, we created the symlink /dev/radio using udev in the previous HOWTO. For the speed, you'll need to check your radio's menu settings. It should be be something like CAT rate, COMM rate or Serial rate (refer to your manual for assistance). I currently have my FT-847 set to 9600 baud, though it's capable of 57600 and 4800 as well. rigctl takes our pieces of information in the form of command line arguments which are -m for model, -r for device (rig) and -s for speed. Another argument we'll pass to rigctld later on, just to be specific, is -t for TCP port. note: you Icom users will need to specify the CI-V address of your radio using the -c argument.

Running and testing rigctl
To establish a connection with the radio, we'll issue the following command:
rigctl -m 101 -r /dev/radio -s 9600

Once rigctl is up and running, you'll be able to issue commands to the radio directly to either read a setting or set a setting. If you have successfully started rigctl, try issuing the "read frequency" command. To do this, simply enter f by itself and press enter. The radio should respond with it's current frequency in Hertz.
To set the radio's frequency, enter F followed by the frequency in Hertz. (In hamlib, capitalized letters set, lowercase letters get)
For example, to set the radio frequency to 146.520:
F 146520


Switching over to rigctld
If everything has checked out thus far, we can now quit rigctl (enter q) and begin moving over to rigctld.
Essentially, you can run rigctld with the exact same settings as rigctl. For safety, I also issue -t 4532 to specify the port I want rigctld listening to. This is the default port and is unnecessary, but it's nice say exactly what you mean even when it's implied. :)
So, to start rigctld, we run something like the following:
rigctld -m 101 -r /dev/radio -s 9600 -t 4532
(You can run the command above with an ampersand at the end to "background" the process, but for the time being it's unnecessary.)

With the daemon running, you should now be able to interact with your radio with you program of choice. If you do not yet have a program installed, check out grig which should have come with hamlib. grig is a Graphical Rig that gives you a generic radio graphical interface where you can change frequency on the screen and see the frequency change on the radio and vice versa. It's nothing special and you probably will get a more useful interface with your application of choice, but this is a good testbed.

To keep things tidy (and so I don't have to manually run rigctld everytime I boot up, I created an entry in rc.local (found in /etc) to run with the same settings I used above. (Just remember to "background" the process by putting a & at the end.

Now with rotctl...
Configuring rotctl and rotctld isn't all that different from rigctl. Refer to the man page for rigctl for specific command line flags for it, but you should have no difficulty if you already know the rotator controller's protocol. It's very satisfying to issue a command to rotctl and hear the rotator turning and see the indicator needles moving.
My setup looks like this:
rotctld -m 201 -r /dev/rotator -s 9600

Once you have rotctl setup how you like, create an entry in rc.local using rigctld, configure your application for the appropriate settings (remember rotctld likes port 4533 by default) and enjoy the fruits of your labor. (Again, don't forget to background the process with & at the end of the line in your rc.local entry.

Final Overview
So, with everything working correctly, I shouldn't have to do anything to get the functionality I want. udev detects our device connecting our radio and rotator and creates the symlinks of our choosing. rc.local, after the OS has mounted the devices, will startup rigctld and rotctld with the settings specific to our radio and rotator. All that's left is to run our application of choice (CQRLog, gpredict, fldigi, etc) and configure the application to talk to our daemon running on localhost.

Overall, the whole process is not too terribly complex. It's a few new steps you may not have done before, but in the end it all works out nicely. 73 and good DX!