My interest in amateur radio and introduction to APRS also got me interested in maintaining a home weather station. When I lived back in Virginia, I first deployed a home weather station and took the steps of interfacing it with a 2m radio for use on APRS. I also attended National Weather Service weather spotter training… even had a card at one point with my weather spotter ID number. After the move to Kansas, I continued to keep a home weather station active and had a working webpage linked from the blog where one could see the latest weather data.
Pairing the Davis Vantage Pro2 weather station with a linux system was never straight forward. My previous linkage between weather station, computer, and radio had been Windows-based. UI-View32 was a sound and stable program. My desire to ditch Windows for linux acted as a strong influence to make the leap from UI-View32 to the linux-based Xastir, but the problem was with the Vantage Pro2’s data stream. As mentioned earlier, the good folks at Xastir finally created a work around using weewx to use the Vantage Pro2, Xastir, and my TM D710A to dependably beacon out my weather data.
But here is what I need to do… I need to capture all the steps of how to set everything up as well as mark all the references I used to gain eventual success. Documentation! I have mentioned before that this blog services as my station notebook and I think that is still a great idea – but it requires a bit more work on my end.
An example of a great reference that I found is a blog post entitled: New Weather Station – Davis Vantage Vue – Part 2 of 2: Linux installation. In addition to maintaining a link, I am also going to grab a copy of the post and save it as a pdf file as a backup reference. We know that information on the internet will not be here permanently.
The other reason that I need to capture these reference sites is that I have a habit of leaving tabs open on my browser. Before you know it, I have tab after tab – and I don’t want to close the tab because… well, that was sure interesting and possibly useful. The cure for my tab addiction is to lay it out here in the blog.
I have endeavored to have my hamshack be 100% linux for a number of years. Licensed in 2001, my ham career really got going when I returned to the States in 2005. Upgrading to General and getting on HF, I integrated a computer into my operations. Ham Radio Deluxe was one of the most popular at the time and I used it – great for logging, digital modes, and rig control. When I had fun with APRS, I used UI-View, which was Windows based.
My first experience with linux was in the late 1990s. I had limited success. Not much later, Ubuntu gave me more of an opportunity to use linux for meeting my requirements for computing. I began to dip my toe in, using linux for rig control and logging. I switched to Mint around 2010-11. I found that Mint was easy to use and allowed me to use fldigi for digital modes, rig control, and logging. ARRL’s LOTW could also be used with linux and was integrated into fldigi. It was hard to find any aspect of the amateur radio hobby that required a computer and could not be done with linux.
Except, in my case, for one area of pursuit. APRS and my weather station. I had become a Davis Instruments fan since I got my first weather station in 2005. As mentioned before, UI-View handled the APRS portion and Davis had its own Windows-based software for handling the weather data the console produced. Back in 2011, the standard for linux-based APRS was Xastir. Xastir is a solid application and I had success using it to handle both internet and RF APRS traffic. But Xastir would not play well with the Davis Vantage Pro2. There was internet talk of a work around using a MySQL database. I had no luck. I kept my system on Windows, using UI-View for weather and APRS.
About two years ago, my Vantage Pro2, which I had since I was over in Iraq in 2007, finally died. The sensor package was mounted off my chimney when we first moved in to our current house over a decade ago. A great location for the weather station as it it high and clear of obstructions. Our roof, however, is steeply pitched and not something easy for me to traverse. I had gotten a TV antenna installation guy to install it – he did a great job. I think I had him back a few years later to swap out the battery. At one point, the board on the unit when bad and I replaced it. Then two years ago, one of our dogs shows up with an anemometer cup in her mouth. Perhaps a good sized chunk of hail had it the cup? Outside temperature data stopped working.
Rather than attempt to fix/repair the existing unit, it was time to replace. Over a decade is a long time to be exposed to the elements. I purchased a new Vantage Pro2 but then had a hard time finding someone to install. The local tv antenna guy took one look at my roof and said nope. A month ago we were getting our chimney inspected and cleaned and the gentleman was showing me pictures of the crown of the chimney. He’d just climbed up there. I asked if, for a reasonable fee, he’d be willing to swap out the weather station (and the VHF/UHF antenna). We struck a deal and now the weather station was operational again.
But could I still achieve my goal of a linux-based APRS/weather station? Enter weewx. This is an application that is like the Swiss army knife of weather station apps. I am not sure of what it does not do. The key aspect is that weewx produces a file (wxnow.txt) every minute using the same format used by APRS for weather data. Even better, the good folks at xastir created a script (wxnowsrv.pl) that copies the wxnow.txt information and pulls it into xastir. This was the solution!
And it works! Both weewx and xastir are happily working together on their own minimalist linux box, pulling in weather data from the Vantage Pro2 console via a serial connection while xastir is using a serial connection to transmit the weather data via my TM-D710A TNC functionality into the APRS system via RF. Weewx also creates a simple weather webpage which you can see here.
I kept a careful list of all the steps I completed in installing both weewx, MySQL, and xastir that I will post here soon – in case I need to reinstall. As of now the system seems to be stable and working nicely.
I have put in some serious time trying to get the ham shack back in usable order. A lot of progress has been made.
(1) The shack computer has been replaced with a new Shuttle DS77U. Not a fancy, powerful computer but what I really enjoy is that it is small (slightly smaller than a cigar box (remember as a kid when you had a cigar box to keep your treasures)) size and that it is fanless (which equals quiet). It took a few iterations to settle on a linux distribution and to get fldigi and wsjtx working properly. During one of my test iterations I had xastir up and working (kinda of). I was able to pair it with the TM-D710A and it worked for transmitting, receiving, and plotting APRS signals. My failure was in getting the maps to work. Ends up it was an installation issue on my part. My end goal is to get xastir working on a separate linux box, possibly working with my Davis Vantage Pro2. I have seen very few clean, direct implementations of pairing xastir with a Davis Vantage Pro2… so, we’ll see. The other problem was tqsl or the software that runs LOTW. During one of my trial iterations, I had fldigi configured to log every completed contact directly to LOTW – it was great! It was challenging trying to install the latest version of tqsl and get it working properly. The version that is available in the repositories is outdated. The version available for ARRL is difficult to work with (using some distributions) due to dependencies. I had a great deal of success using the latest version of Linux Mint (19.3) which already had all the needed dependencies for tqsl. Now when I log a contact into fldigi’s logbook, it gets immediately uploaded to LOTW. It would be nice if wsjtx did the same, but it is no big deal to sign and upload that log later. All that being said, the shack computer is working nicely for what I need to have the basic functions to get on air.
(2) Selling off gear I don’t need. One of the factors that made the shack uninhabitable was all the excess stuff. I started selling gear off using QRZ.com’s forum. The gear is doing me no good, so it makes sense to lighten the load here. Up to this point I have listed and sold a Bencher BY-1 black-based paddle and two QRP kits I had sitting on the shelf. Next up will be the IC-92AD with all the bells and whistles (drop in charger, DV access point dongle, four batteries, the Nifty manual, the GPS speaker mic, plus the original box. What I like about the IC-92AD is its construction. The chassis is diecast aluminum, so the feel is solid… not something you get with the vast majority of HTs. I enjoyed using this HT from the indoors, using the dual band capability to monitor both my EchoIRLP node and D-STARS. I don’t do that anymore, so I think it is time the IC-92AD goes. I also found an old unbuilt NorCal 40a kit that includes a theory book on electronics. And it is also time to get rid of the FT-817ND that is tricked out with about every modification and additional gadget you could think of. There is a Bencher BY-2 that needs a new home. I also have maybe a half dozen unbuilt kits. Some I am unsure exactly what they are, although still in their original packaging. Many are from the now shuttered Small Wonders Lab. I am going to have to take some pictures of the ones I don’t recognize to see if I can figure out exactly what they are.
(3) Now the biggest issue that faces me is antenna improvement. Currently deployed in the trees off to the side of the house is a Radio Works G5RV. How sad I was to learn that Radio Works has also closed its doors. I was introduced to Radio Works when I lived in Hampton Roads, them being based in Portsmouth. Man they made great antennas. I still have one of their Carolina Windoms that I would like to put up. The G5RV needs to be replaced. It has made it through many Kansas winters and is ready to be retired. In cleaning the shack, I have pulled together all the odds and ends for hanging and installing antennas and I have everything I need on hand. Time to make it happen.
In non-shack news, I was going to replace the XYL’s TM-D710A with a D710GA, as well as a new motor to raise/lower the antenna. The antenna motor install was accomplished without issue. I attempted to install the D710GA without first testing it in the shack = mistake. Ends up the a-side control pot for volume/squelch was bad. As I purchased the rig as a Christmas present, I didn’t test it within the 14 day period required by Gigaparts in order to get the rig directly replaced. Instead, I have to send it in for warranty repair. Hopefully that goes smooth.
I am also hoping to have exciting news tomorrow. Keep your fingers crossed.
Last summer when we were camping in the national parks, there were many campsites where we had no cell phone service. I am not complaining about that, but our work around to communicate back home to the XYL often required a trip to the pay phone (sometimes hard to find). I thought about perhaps using APRS’s capability of relaying short pieces of text as emails. Part of the problem is that there are many areas of the parks that don’t have any APRS digipeater coverage (Glacier and Yellowstone National Parks for example). How to get a message through?
Then I remembered my MARS station (AEN5AC) in Iraq. I was using an ICOM IC-7000 and an SCS PTC-IIusb modem to pass MARSGRAMS from my location north of Baghdad to another station at the US embassy in Qatar. The pairing worked quite well and I was consistently able to connect and pass traffic using PACTOR 3 at the 1400 baud rate. Could I use a similar setup to provide an HF email option while camping this summer?
I dug out my SCS PTC-IIusb modem. I had not used it since shutting down the MARS station in June of 2008. Everything was still in the box. To include the cables necessary to interface the modem with an ICOM IC-706MKIIG… the same rig I use for HF mobile.
I pulled out my spare IC-706MKIIG. Coming back to Kansas from Field Day in California back in 2009, my IC-706MKIIG quit on me. I ended up buying a second at the HRO in Denver and sent the broke one to ICOM. ICOM fixed it and returned it. I kept it in the box and it went back on the shelf. I did order a 6 pin Molex connector with powerpoles to allow for an easy power connection (#9). I connected the two cables from the modem to the rig. Once cable is for the data and plugs into the 706’s 13 pin accessory connection (#4). The other cable connects to the 706’s CI-V interface (#6) to have the radio change frequencies based on what station is being contacted.
I had the basic hardware of a HF email station, except for a computer. I would need one that would function out of the vehicle. This would probably require a laptop. I also decided for the ease of simplicity that the computer should be Windows driven (instead of Linux). Gasp! The bottom line is that the software and drivers required to send email via HF and use the SCS PTC-IIusb modem is Windows based. The answer ended up being an Dell XPS 15.
Using a Windows based computer helped me with a number of summer travel tasks that could not be accomplished by my small Linux laptop:
(1) Run the software required for HF email (more on Winlink and Airmail later)
(2) Run ARRL’s TravelPlus for Repeaters
(3) Run RT Systems radio programming software for my TM-D710A
(4) Run RT Systems radio programming software for my VX-8RGs
(5) Read the SD card from my Canon digital camera
Interestingly enough, the new laptop does not have a CD/DVD drive nor an RJ-45 connection for a LAN cable. Neither of these have been a show stopper yet.
ARRL’s TravelPlus for Repeaters
I had purchased TravelPlus for Repeaters with the intent of installing it on my existing Linux laptop and running it under a VirtualBox Windows session (similar to how I run iTunes on my Linux laptop). However the software failed to install. I tried troubleshooting and looking at suggested fixes found on the forum sites but still had no luck. I tried installing TravelPlus using WINE. It installed but would not run as well.
Dell XPS 15 to the rescue. As the laptop does not have a CD/DVD drive, I copied the drive onto network storage. I then was able to install TravelPlus over the network and it is working without issue.
RT Systems Programming Software
The RT Systems programming software works fine under a VirtualBox Windows session. As I was moving all my vehicle related radio/computer tasks to the new Windows laptop, I attempted to install the programming software for the TM-D710A (used for beaconing the location of my vehicle and talking on VHF/UHF). Following a similar procedure that worked for TravelPlus, I copied the programming software from the install disks to a network drive. The software installation for the TM-D710A worked without a hitch. The software for the VX-8RGs (HTs we use for around camp and hiking) failed to load. The error said that I must use the original disk to install. A big challenge when the laptop doesn’t have a CD/DVD drive. The work around is that you find another Windows computer with a CD drive, load the software CD, then back on the driveless laptop, map the CD drive (like you would map a network drive). That worked and I was able to install the programing software for the VX-8GR.
HF Email Software
There are two main choices for software to allow for HF email: RMS Express and Airmail. I installed both. Airmail was the same program I used in Iraq and it offered easy configuration with the IC-706MKIIG and the SCS PTC-IIusb.
I now had all my equipment for a test run setup in my basement hamshack: spare IC-706MKIIG, SCS PTC-IIusb, and the Dell XPS 15 with Airmail. I connected the IC-706MKIIG to my Elecraft tuner and used my existing G5RV antenna. Airmail configures easily. The software has a list of stations offering mailbox services that can be viewed on a propagation chart by frequency and distance. Based on time of day, I selected a station in Texas that offered a 40M PACTOR 3 connection. Airmail allows me to click on the frequency in the propagation chart which then changes the dial frequency of the radio. After listening to see if there were any ongoing connections, I initiated contact. The modem lights flashed and the rig clicked between transmit and receive. The connection was made and I was able to send a test email as well as a position report.
Success! The position reports that go into the Winlink system are copied over into APRS. Now, even if I am not able to reach a digipeater with my VHF APRS beacon, I can send a position report over HF to let the XYL know where we are.
I then thought about the steps I would have to take of transitioning my IC-706MKIIG configured for HF mobile to be ready to work with the PTC-IIusb to send email. As the remote head is located up near the drivers seat, this would present problems with being able to observe the modem, laptop, and radio control head all at the same time.
What if I just dedicated the spare IC-706MKIIG rig to the task of HF email? It would save me time and bother in pulling and plugging cables. It would also give the camping option of being able to operate HF from outside the vehicle.
Using an additional iPortable box, I rack mounted the spare IC-706MKIIG and the SCS PTC-IIusb. Now I will have a spare HF rig with me, so if one goes out I will still be operational. I also attached the Tarheel screwdriver antenna’s rocker switch to raise and lower the antenna on the side of the box. During normal HF mobile operations, the TurboTuner (connected to the other IC-706’s tuner connection and CI-V connection) manages achieving a correct match between the operating frequency and the screwdriver antenna.
I only have the one TurboTuner. The TurboTuner requires a connection to the CI-V. So does the SCS PTC-IIusb. My solution was to leave the TurboTuner alone. Instead, using the rocker switch, I can manually tune the antenna while visually observing the 706’s SWR meter.
To transition between using the 706 dedicated to HF mobile to the 706 now dedicated to HF email, I have to do the following:
(1) disconnect the antenna feedline from the TurboTuner
(2) disconnect the control line that goes from the TurboTuner to the Tarheel screwdriver antenna
(3) connect the antenna feedline directly to the HF email 706
(4) connect the control line to the rocker switch
(5) connect the laptop to the SCS PTC-IIusb via a USB cable
(6) connect the iPortable’s powerpole connection to the junction box in the back of the vehicle
… then I am ready to go. The iPortable box rests nicely on the vehicle’s tailgate, next to the laptop. All at about lawn chair height. Not only can I use this setup to send email via HF, but I can also use it for causal National Parks On The Air contacts as well.
What’s left to do:
(1) Constant cooling fan modification for both IC-706s (see AD5X’s article)
(2) An extended control cable for the Tarheel screwdriver antenna. This will allow me to further remote away from the vehicle, but still use the antenna.
(3) A length of antenna feedline for remoting.
(4) A length of powerpole-ready powerline to attach to either the travel trailer battery or directly to the spare vehicle battery… again for remoting away from the vehicle.
(5) I have a set of Heil headsets that worked with my IC-7000. I think if I get the AD-1ICM, I should be able to use them with the 706.
(6) A Heil HS-2 hand PTT switch to use with the headset.
I have been using small footprint computers in ham shack for a while. It started with the Dell Zino. Always a bit under powered, but enough to get the hamming done. The latest computer driving everything was one of those barebones models that was the size of a shoe box. The first sign of decline was when the fan kept getting louder and LOUDER. The the drive (500GBs of SATA) then decided to give up the ghost.
An immediate lesson learned… back up my log. I have been good at uploading my logs (almost daily, when on the air) to LOTW, QRZ.com, and eQSL. But I would only export that days contacts, consistently replacing the previous days exported log.
I choose not to abandon the small footprint computer and went back to the Shuttle. Newegg.org was my one stop shopping:
The case and motherboard: Shuttle XH81 Intel Core i7 / i5 / i3 / Pentium / Celeron 65W Intel H81 1 x HDMI Barebone system
– small form factor, fits neatly underneath monitor.
– 2x RS-232 connections on the back. Perfect for connecting to the Elecraft amp and tuner.
– Plenty of USB connections
Intel Core i7-4770S Haswell Quad-Core 3.1 GHz LGA 1150 65W BX80646I74770S Desktop Processor Intel HD Graphics
– not the fastest, but fast enough.
– comes with a super quiet fan.
Transcend JetRam 8GB 204-Pin DDR3 SO-DIMM DDR3 1600 (PC3 12800) Laptop Memory Model JM1600KSH-8G
– I got two DIMMs to keep things moving… 16GBs = snappy!
SAMSUNG 850 EVO 2.5″ 250GB SATA III 3-D Vertical Internal Solid State Drive (SSD) MZ-75E250B/AM
– Good bye disk, hello solid state. Faster. Silent.
The actual build was plug and play. The Shuttle line has come a long way since my last experience with their product. I think these specific computers are designed to operate older types of technology (hint…. 2x RS-232 connections?) which works great with most amateur radio needs.
The next step was loading the OS. LiLi USB Creator is my go to solution for installing linux when I don’t have an optical drive (which is more often the case). This allows you to load the OS through booting directly from the USB stick.
The linux flavor of the day: Mint with the MATE edition. I was an Ubuntu man until Unity. Then made the jump to Mint. The OS loaded without issue and I was off and running.
Amazingly enough, I was able to install TQSL-2.2. In the past, I have been able to install TQSL from the Software Manager. But this has been an older version of TQSL. The newer versions ALWAYS gave my problems with dependency issues during attempted installs. I stayed with it this time and finally got it working. Phew!
The install of fldigi went smoothe, but configuring it to work with my Elecraft K3 was giving me fits. In my past setup, I’ve always used hamlib for rig control and the trick was just finding which USB number was being used for my USB Microham III. But this time, the USB Microham III was identified by name as a choice. Great! But it didn’t initialize. I tried USB0 (…. nothing), combed over the results of lsusb…. not… working. After some intense Googling, I ran across a command I had never seen before:
sudo adduser [username] dialout
Dialout!? Who knew? But that did the trick.
Now, here is something funny. We all have our junk boxes. As hams, we are pack rats. We hang on to stuff that has no current use, but may someday. I had a box RS-232 cables. When Fall Cleaning swept through the ham shack, I looked at the RS-232 cables. I am really going to need 15 RS-232 cables ranging in length between two and 15 feet? The box headed to the dump.
Now, with my growing K-Line, I can use Elecraft software (linux versions available) to monitor data from the amp and tuner. But the connections are serial. SERIAL. I turned the ham shack upside down and not an RS-232 cable to be found. I really don’t want to have to actually go out and BUY a serial cable.
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn’t have /sbin/init.
No init found. Try passing init=bootarg.
BusyBox v1.18.5 (Ubuntu 1:1.18.5-1ubuntu4) built-in shell (ash)
Enter ‘help’ for a list of built-in commands.
(initramfs)
This has happen on my Dell laptop much more than I’d like:
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn’t have /sbin/init.
No init found. Try passing init=bootarg.
BusyBox v1.18.5 (Ubuntu 1:1.18.5-1ubuntu4) built-in shell (ash)
Enter ‘help’ for a list of built-in commands.
(initramfs)
I’ve recently re-established my station here in Kansas. The majority of all the components of my station I was using previously in Korea: Elecraft K3 rig, a Dell Zino PC, using the MicroHam USB III as an interface between the radio and computer. The Dell Zino PC is configured for dual-boot: Windows 7 and Ubuntu. Last year I spent a good deal of time configuring fldigi, under Ubuntu, to fulfill the majority of my amateur radio automation requirements (rig control, logging, digital modes). After a bit of trial and error, I had fldigi working quite well.
Once I was back here in Kansas, I had a problem configuring the K3 – CW, as a mode, wasn’t working. Figuring I had messed up a setting, I reset the K3… which ended up not being the smartest move. Up to this point, I had never updated the K3’s firmware or backed up the settings. I (incorrectly) believed that Elecraft’s configuration software was for Windows only. An email to Elecraft generated a quick response with a copy of the software configuration file for my specific rig.
Weeks past as I avoided getting the hamshack into proper order. The hamshack became the default location for stashing half unpacked boxes. Once I finally made serious progress in sorting through and organizing everything, I was able to get to the K3 and PC. I booted up Windows 7, connected the PC to the K3, updated the firmware, and reloaded the original factory software settings. Things were looking up.
I decided to see if Ham Radio Deluxe under Windows 7 was easier to use than fldigi. I updated Ham Radio Deluxe to the current version and then attempted to get the MicroHam USB III to work. Frankly it was a pretty kludgey process. An additional program had to be installed to create a virtual com port in order to allow the MicroHam USB III to work. Configuring the soundcard, resident in the USB III, was also not very successful. Then I tried Ham Radio Deluxe, which had been my software of choice a little over a year ago. Bottom line, I was not pleased with Ham Radio Deluxe and decided to switch back to fldigi.
Booting into Ubuntu, fldigi worked from the get go…. rig control, log, and digital modes. For now, I’ll be sticking with Ubuntu and fldigi.
NOTE: Here is a list of settings that I use:
Fldigi config:
Rig control
– RigCAT
– /dev/tty/USB0
– Baud rate: 38400
– Toggle DTR for PTT
Ubuntu Sound Preferences
– Hardware: USB Audio CODEC, Analog Stereo Duplex
– Input: Internal Audio Analog Stereo [this confuses me, because I would expect the input would be associated with the USB Audio device (aka the Microham)
– Output: USB Audio CODEC Analog Stereo
– Application: No application
Here is a a re-cap of my amateur radio activities during my past twelve months in Korea:
(1) DX – I enjoyed working a good bit of DX, enjoying most QSOs with stateside contacts as well as Pacific exotics. The greatest limitation I had was my operation location and resulting inability to ideally situate an HF antenna. Living in the barracks (the ultimate in CC&R) restricted any type of permanent antenna installation, further limiting my options. I solely used a Buddipole (which after many additional accessory purchases, became two Buddipoles). Despite the antennas being positioned next to a three story building, I was able to make contacts to North America, South America, Europe, and even Africa. I credit this to improved band conditions over the past months and also the Buddipole… it’s a keeper.
(2) EchoIRLP node – I brought my embedded EchoIRLP node to Korea and interfaced it with a Kenwood VHF/UHF rig. Again, with my poor location and inability, I could not have an antenna installed outdoors. Instead, I kept the Kenwood rig at its minimum wattage setting and used a roll-up J-Pole made from ladder line. With my HT also set on minimum power, I was able to make effective use of the EchoIRLP node. My primary contacts via the node were with the XYL back in Kansas. She has a mobile VHF rig, to include APRS. I could check to see when she was on the road for her morning or afternoon commutes, connect through my EchoIRLP node here in Korea to our EchoIRLP node back in Kansas. With the XYL’s rig set to the frequency of the Kansas node, I could frequently ride along with the XYL and harmonics as they moved about. Additionally, the Echolink capability of the embedded node allowed me to regularly talk to my dad, KD6EUG, while he connected to my node via an app on his cell phone. Another great enjoyment was the ability to monitor the different IRLP reflectors and sometimes participate in ongoing nets. I am sold on the flexability of the embedded EchoIRLP node and will take it with me again when I get deployed for a long duration.
(3) D-STAR – starting with a D-STAR Dongle, I moved to a DV Access Point and got an ICOM D-STAR HT. I enjoyed playing with D-STAR and the ease of having the Access Point as well as the IC-92AD (http://www.universal-radio.com/catalog/ht/5092.html) made using D-STAR pretty straight forward. There is no aruging that the audio quality for D-STARS is poor. The complicated nature of setting up a rig at home for the XYL would also make D-STAR a poor choice to replace the EchoIRLP node. However, I enjoyed having the flexibility of having the ability of getting on D-STAR.
(4) Linux – all my radio operations here were supported by using the Ubuntu distrobution of Linux. After toying with CQRlog, I have settled on fldigi as my primary interface to my HF rig.
(5) APRS – although my APRS operations here were limited to the internet (Korea has virtually no APRS traffic), I used xastir (www.xastir.org) to show where my operating location was and also advertised my EchoIRLP node.
(6) WX station – never happen. I could not find a good location to place the collector, so it is still in the box. More importantly, wgoohat I didn’t get the opportunity to learn was how to interface a weather station to the APRS application xastir.
(7) Stars & Stripes article – I was able to discuss my amateur radio experiences with a reporter from Stars & Stripes.
Yet again, more success with Ubuntu and ham radio. I purchased a D-Star DV Dongle earlier this year and never had much time to play with it. I do not own an actual D-Star radio and the only time I have really ever seen D-Stars in action was at this year’s Hamvention. I am a fan of Echolink and IRLP – the DV Dongle seemed like a good way to dip my toe in the D-Stars pool without a big cash investment. Additionally, I haven’t been living near any existing D-Star repeaters (either back in Kansas or here in Korea).
Installing the DV Dongle on the hamputer went smoothly. Great instructions are located here or here. For support, there is a Yahoo Group which is active and brings quick response in troubleshooting problems.
Once I had the DV Dongle up and running, NJ6N has a webpage that provides a live look at who is active on which D-Star repeaters and reflectors.
There are plenty of resources out there, which could indicate the growing popularity of D-Stars.
If you are interested in having a D-Stars QSO, let me know.
Here are details for my Ubuntu hamputer installation:
(1) Install the 32-bit version of Ubuntu 10.04… DO NOT INSTALL THE 64-BIT VERSION!
(2) Run Update Manager and reboot
(3) From the terminal sudo apt-get install: libssl-dev, libhamlib2 and libhsmlin-utild
(4) Download CQRLOG (my version was cqrlog_0.9.6_install.tar.gz)
(5) Extract file and you get cqrlog_install.sh – run the script in the terminal
(6) After the install is complete, you should be able to start and run CQRLOG
(7) Now you need Fldigi… this takes a bit more work to get the latest version
(8) From the Synaptic Package Manager, install: g++, libfltk1.1, and libfltk1.1-dev
(9) Find via Google (or use the supplied links), download, extract, configure, make and install: libsamplerate-0.1.7.tar.gz, pa_snapshot.tgz (v19), libpng-1.2.9beta11, and hamlib-1.2.7
(10) Then download fldigi-3.20.29, configure, make, and install
(11) That is it – everything should be good to go.
(12) For bonus points, download and install Flrig
For more on CQRLOG – listen to Episode 47: CQRLOG Revisited of Linux in the Ham Shack… the best (and only) amateur radio/linux podcast out there.