The PiRLP node provided EchoIRLP capability. With the node, I was able to use IRLP and Echolink. The PiRLP interfaced directly to my Kenwood TM-D710. I have been using the nodes from David Cameron, VE7LTD, for a number of years with only very small problems now and again.
Once I got my Davis Vantage Pro2 weather station up on APRS via the same TM-D710, I started experiencing problems with the audio output level of the PiRLP node. The big problem was that if I wanted to use the TM-D710 to get on the local repeater, I had to shut down the PiRLP node first. Not ideal.
Enter the NORMAD IRLP node. I first heard about the node on Jeff’s blog at KE9V.net. Like my node for Wires/Fusion, the NORMAD IRLP node has a small transceiver built into it. This is a great solution. It provides me the ability to dedicate my TM-D710 for weather APRS as well as also using it to monitor the local repeater without making any changes here in the hamshack.
The primary purpose of this blog is to act as a station notebook. A log that serves as a record as to what I am doing in the shack, how I configured certain items, how I overcame obstacles that were in front of me. Admittedly I have done a poor job at keeping up. And sometimes I do not realize or remember what I have placed in the log so it could assist me in the future.
My configuration of the Normad for Echolink operations (in addition to its native IRLP ability) is a great example. I wished I had looked here first – it would have saved me about two hours. I received the Normad and swapped it out with my older PiIRLP. Got on to IRLP immediately. NOTE: here two great troubleshooting commands for trying to get Echolink working; killall tbd and tbd -ddd. The results provided by tbd -ddd show if your callsign and password are valid for the Echolink connection. A key place to start when Echolink is not working correctly.
I also enjoy using the Echolink functionality of EchoIRLP – mainly to listen to the Coffee Break net hosted by W6EK, the Sierra Foothills ARC every morning from 7:30am to 10am (Pacific).
If you are lucky, you have been involved in a truly great net at one point in your radio amateur career. The most memorable net for me was a 2m morning commute net back in Hampton Roads, Virginia. The participants were smart, well spoken, and directed the conversation to a number of topics which almost always focused on some aspect of amateur radio. In classic roundtable fashion, the conversation moved cleanly between those that checked in which allowed the focus to be on the conversation. Mark, N1LO, was one of the ringleaders. I miss those guys.
The Coffee Break Net is very similar. Check it out if you can. While the net does run on their terrestrial repeater (145.430 MHz -0.6 Offset PL Tone 162.2), you can join via AllStar (51018), Wires-X (W6EK-2M-ROOM (62545)), or Echolink (4128).
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.
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.
Once I knew that I had a new callsign, I sat down a wrote down a list of what I needed to do…
(1) QRZ.com website. When my callsign changed a few years back from AD7MI to NI0L, I jumped on the air to “test it out”. On 20m, I was having a PSK31 QSO when the distant party thought I was a pirate station because on QRZ.com my new callsign did not reflect the name and QTH I was using. A pirate! I explained that it was a new callsign but I could tell that the other guy was not buying it.
I thought I would need to go on to QRZ.com and register as a new user. I made a posting in the QRZ.com forum category dedicated to callsign problems. The end result: just wait… the change will take place automatically in a few days.
And that is the case. If you are a US ham and change your callsign, just wait. Within two or three days the callsign change will be reflected on QRZ.com. If you get on the air before QRZ.com is updated, be prepared for people to think you are a pirate.
(2) Log of The World. Easy to do. Just submit for a new certificate under the new callsign. ARRL usually responds within one working day.
(3) EchoIRLP node. This ended up being much easier than I thought it would be.
a. To change your callsign in the IRLP database, go to this webpage using a computer connected to the same router as the IRLP node.
b. Go into your node and edit irlp/custom/environment file to change the old callsign to the new callsign. Restart the node and verify the changes have taken effect.
c. For the EchoLink side:
– Validate your new callsign.
– Check for validation of the new EchoLink call sign / node number on EchoLink using the EchoLink PC client software. Remember, EchoIRLP only allows link (-L) or repeater (-R) nodes.
– Note: you can only register the new callsign once the EchoLink folks of pulled the latest and greatest database update from the FCC. This may take a day or two. Once that is done, you can validate your new callsign. Your new callsign will be assigned a new EchoLink node number. If you want to use your previous node number, EchoLink allows you to swap node numbers between your old callsign and your new callsign.
– Once you are validated and have swapped node numbers edit the files and settings listed below:
Restart IRLP from root login with script /home/irlp/custom/ rc.irlp, or reboot the node.
IRLP node 4433 and EchoLink node 536398 are up and operational.
(4) APRS – change the callsign in my vehicle, HTs, and UI-View32. Pretty straight forward. The home weather station info can now be found here.
(5) Change the blog website. I have been keeping an amateur radio blog for about 10 years now. Web hosting companies make it pretty easy to get a domain for your website and then setup web hosting. I like using WordPress to setup and maintain the actual blog. Fairly straight forward but flexible to do just about anything you would want for a amateur radio blog. The new website is up and running.
(6) Callsign license plate. Kansas makes the pretty simple. I went down to my county office on Friday after work. The application process was smooth and the wait should be about 4-6 weeks.
(7) New QSL card. I am thinking of going with this:
Had a good day in shack. Was able to get a good portion of it cleaned up. Filled up a trash bag and a big box of “stuff” I just do not need.
Fired up the HF rig and ran it through it’s paces. Had a Phone QSO with a station down in Costa Rica and worked a few stations around the US on PSK-31. Enough to let me know the rig is still working. Listened to my favorite bunch of old timers who meet weekday mornings (8AM) around 7.140 MHz. I’ve never joined in, but used to listen to them all the time from my mobile when my work hours were a bit different. Nowadays I don’t get the opportunity to hear them.
For the last few weeks I have been trying to square away my VHF/UHF setup. My embedded EchoIRLP node has consistently suffered from pulsing. I have tweaked about every software setting and radio setting possible but was unable to fix the issue. It looks like the pulsing generally correlates with my APRS signal. I use a Kenwood TM-D710A in the shack. A computer with UI-View32 is driving the left half of the TM-D710A, sending and receiving APRS data. The right side I usually dedicate to the EchoIRLP node which is normally set to a simplex UHF frequency. I started to notice that everytime UI-View32 sends out my position or weather report, my EchoIRLP node would pulse. I honestly think the rig is the issue.
What I like best about the TM-D710A is that I can use my one antenna that I have mounted off my chimney. The TM-D710A allows me to use both the APRS and EchoIRLP at the same time. But I think that pulsing issue will keep me off IRLP reflectors or Echolink conferences unless I disable UI-View32 and the TM-D710A’s TNC while I am using the reflector/conference.
I upgraded my version of fldigi. I made sure my log and settings were backed up and the upgrade went without significant issue. I was able to setup the WX macro function, which I have been meaning to do. The macro pulls the latest WX from Kansas City International Airport (MCI) and allows me to slide that into a PSK-31 QSO via macro. I wish it could pull the data right from my WX station. Not sure how to do that.
I setup my D-Star DV Access Point Dongle – hadn’t done that in a while. I am consistently unimpressed with the audio quality that I get listening to the D-Star reflector on my ICOM IC-92AD. The audio is very metallic and tinny.
APRS has taken up a bit of my time lately. I enjoy playing around with my Yaesu VX-8GR. I am amazed at the different ways you can send a message from the APRS system to an email address. I have improved my ability to work the VX-8GR to input text for a message.
I figured out how to get my UI-View32/TM-D-710A setup to only digipeat APRS packets from either my callsign or the XYLs. That comes in handy when I have the HT. One thing I have not been able to figure out is how to get my UI-View32/TM-D710A setup to digipeat packets destined for my HT’s SSID. For example, if I send a message from my HT, it is digipeated out through my UI-View32/TM-D710A setup and picked up by a nearby real digipeater. But when the “Ack” packet comes back, my HT won’t hear it and I am not sure how to get my UI-View32/TM-D710A to recognize that packet and digipeat it.
Did I mention the humidity sensor on the Davis Vantage Pro2 is not working properly?
I checked into a net tonight! We have an awesome daily email called Larry’s List that contains all kinds of interesting information about the amateur radio goings on in the greater Kansas City area. From swap and shop, to license testing, and opportunities to volunteer in support of public events to various club activities and nets…. Larry’s List is one stop shopping for anything you would want to know about what is happening. The list mentioned a net conducted from a repeater setup on top of the VA hospital in Kansas City (KC0VA). I decided to check in and was privileged to partake in a very interesting discussion about how to handle an emergency if it occurred during a net. I also learned about the Q-signal “QRRR”… which I had never heard or read of before.
I enjoy having a weather station at home. It is hooked up to APRS, weatherunderground.com, and I even have a weather webpage. One of the standard exchanges of information in most general QSOs is the weather: temperature, rain, …. I also like telling the folks in Florida that my humidity is 40% (I am not a fan of humidity having expierenced Fort Benning, GA in the summertime and monsoon season in Korea, not to mention my unairconditioned room at The Citadel (although I hear they have air conditioning now!)). It is easy to look at my desktop display and get all the data I need. I have heard of some folks who have a way to pull their weather data directly from their weather stations and input it into their PSK QSOs. Pretty slick, but I have never figured out how to do that (… yet).
All that being said, I do not get into weather prediction that much. If I see the barometer dropping, I may check the locak National Weather Service radar to see if anything is moving in (weather here moves from west to east). But if I wanted to get into weather prediction, this would make an interesting homebrew project: The Tempest Prognosticator.
Developed in the 1850s by Dr. George Merryweather, this device used leeches that would ring a bell if a storm was approaching. The device was even featured in Britian’s Great Exhibition of 1851. Despite the publicity, Dr. Merryweather was never able to get the government interested in putting the device into use.
I am sure there would be a way to interface the slugs with some kinda of Arduino device that would send out weather predicitions via APRS data. 🙂
(1) Two shelves are up. I offloaded my computer that handles the weather station, my printer, the EchoIRLP node, and the TM-D710A that supports both the weather station via APRS and the EchoIRLP node. I put wheels on the hamshack table after I moved it from the rental we were in to our current house. This raised the table to the perfect height, allowing my chair to slide under. The wheels also allow me to swing the table out to get to the back side and take care of any wiring issues with a fair degree of ease. But the weight of the equipment that piled up on the far end of the table made it hard to move. With the equipment I rarely touch placed up on the shelves, the table is much easier to move.
(2) I got my West Mountain Radio Super PWRgate PG40S hooked up. And it works! Additionaly, I have an UPS hooked up. So I should be good for backup power to run the weather/APRS station.
(3) The maps are up! I have the world map and a North America map. It looks like Millennia Arts no longer produce these maps. Who can blame them? I purchased these maps in 2006 and how many additional entities have there been since then? I’d imagine it is just not cost effective to produce up-to-date, high-quality maps like these.
(4) My kindergardener had a weekend project to collect 100 of something. Why not a 100 QSL cards? I dug through my pile pieceing together a variety of cards. Not quite ready for DXCC submission, but going through my tub-o-cards has motivated me to organize my card collection (… and prep for my DXCC submission).
(5) Speaking of QSL cards, it is time to address the “log problem”. Since my first DX contact (VP5VAC, 21 May 2005, on 6M), I have jumped around to differnt logging programs (and different computer OSes). I have txt files, MDB files, and adi files. Logs from special event stations, lighthouse activations, Field Day, Iraq, Korea, and just sitting in front of the rig spinning and grinning. I have used LoTW and eQSL. I’ve also had a few different callsigns. It is time to establish the MASTER LOG. One-stop-shopping for all my contacts that exist currently as some form of a digital log. The tool to get me to where I need to be appears to be DX Shell’s Contest LogChecker. The application will allow me to take many different types of formated logs and combine them together.
(6) Were we speaking of QSL cards? Jeff, KE9V, says he is getting out of the QSL card game. [AE5X as well] I can understand his motivations and why he arrived at the decision to forego the hard copy QSL card. I may, someday, arrive at a similar decision. Although it looks like AA6E is proud of his card. But as of now, I still love QSL cards… desinging my own, sending them, receiving them, getting that fat package from the Buro, etc. That being said, I designed a new QSL card for my new QTH here in Lansing, KS:
…. I hope to receive them soon – and hope to work you soon so I can send one your way.
aprs.fi will join Wikipedia and Reddit, and protest the proposed U.S. SOPA/PROTECT-IP legislation by closing down on Wednesday.
The aprs.fi outage will only affect clients in the United States (or those with IP address mapping an U.S. network operator – the targeting is not fully accurate).
Although the law is being made in the U.S., it will break the Internet on a global scale by making sites such as aprs.fi liable for links and content posted by the users of the site. Sites like aprs.fi are commonly run by individual developers or small volunteer teams. Due to the huge volume of automatically published user-generated content (50 packets per second currently!) it would be impossible for me to go through it all before publishing. If some APRS user would post links to copyright-infringing material, even when that material would reside somewhere else than aprs.fi itself, aprs.fi could be shut down in the U.S. and there would not be much that I could do about it.
I read earlier about the Wikipedia outage. I wonder who will be next to jump on the protest bandwagon. There is nothing that warms the cockles of my heart more than a good ol’ fashion protest.
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.
More success with the Ubuntu hamputer. I found a great wiki that does a great job of walking through the install process. Once I had Xastir up an running, it was interesting to see the massive amount of APRS in Japan compared to the absolute minuscule amount of APRS activity here in Korea. I have a hard time understanding why APRS is not embraced here.