My current assignment at Fort Leavenworth has me traveling quite a bit. My intent has been to bring a rig with me and have some casual QSOs while on the road. My success has been mixed. I would mostly attribute this to either a lack of planning on my part or being in a stuck in a hotel room with zero antenna opportunities.
One of the most inspiring ham radio blogs I ever ran across was the 100 Pound Dxpedition. I enjoyed how Scott, NE1RD, covered his adventures of conducting portable operations… documenting what worked and what did not. His last post on that paticular blog was back in 2007, but I still use the site as a reference. Scott’s praise for the Buddipole led me in using the Buddipole during my recent tour in Korea. Another tip from Scott I am going to try out is using a hardside golf bag case to transport my Buddipole to Hawaii.
Now for a rig… I think the Elecraft KX3 would be ideal for a Hawaii trip. With 10 watts output and an internal battery, I can’t think of better rig to take to the beach. But the wait time for the KX3 is still quite a while. I have both an Elecraft KX1 and a Yaesu FT-817ND. The KX1 would be great due to its small size and ease of use. But it is limited to only CW and I would like to do some PSK in addition to CW.
I pulled out my FT-817 and conducted an inventory:
- West Mountain Radio RIGblaster Plug n Play connects directly to the DIN socket on the back of the rig.
- CAT cable that connects from the RIGblaster to the rig’s ACC socket which enables rig control.
- PowerPole 12v adapter.
- Palm Paddle.
- Elecraft T1 Auto-tuner.
- Nifty manual for the FT-817.
My FT-817 has quite a few of the optional bells and whistles from W4RT:
- Peg Leg tilt stand – I think this will be helpful as one of my significant dislikes of the FT-817 is the small display which is hard to see.
- Magnets for the Palm Paddle – this is critically important as the Palm Paddle by itself is not heavy enough. The magnets allow the Palm Paddles to firmly stick to the top of the FT-817.
For PSK, rig control, and logging I have my Dell Mini netbook. I had not used the netbook in a while, so I started it up to see how it was working. I initally purchased it back in 2009 baselined with Ubuntu and have kept Ubuntu installed on it since then. After booting it up. I updated the distribution to 10.04 LTS and installed fldigi. The RIGblaster easily interfaced with the netbook via a USB connection and the headphone/microphone jacks.
I configured fldigi to work with the RIGblaster to include rig control using Hamlib:
- Audio: PortAudio using the netbook’s hardware soundcard for both Capture and Playback
- Rig: Hamlib; Device /dev/ttyUSB0; Baud rate 38400; Stopbits 2; PTT via Hamlib command checked
… clicked on the Initialize button and I was good to go.
Setting up the macros on flidigi is pretty straightforward with the default macros only needing slight tweaking for my personal preferemces.
Once I fired everything up all I had to do was switch to 14.070 MHz, switch the mode to DIG, and drop the input level a bit. With the narrow yellow PSK streams cascading down the waterfall, I picked one that was calling CQ and answered. Transmit worked and my home antenna provided a nice low SWR, no need for the tuner. My macros worked and the QSO was concluded successfully. All with 5 watts.
I plugged in the Palm Paddle, switched to 7.115 MHz, listened and heard nothing, then used the paddles to send QRL? a few times. SWR still looked decent. After a few CQ calls, I got an answer followed by a short QSO. Great – both PSK and CW were working FB.
Now the question is: do I want to bring my small Tokyo Hy-Power HL-100B amplifier that will raise the output to 100 watts? If I bring the amp, I will have to bring a power supply and a different tuner. I am thinking I need to be able to use two different configurations:
(A) Beach and Buddipole: using the barefoot FT-817, running everything on batteries.
(B) Lanai Portable: used from the hotel room, with amp and assoicated power supply.
Now it is time to go through my Buddipole bags and figure out what I need to pack.
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:
- 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
Back in February I talked about my plans to piece together a portable station based around the iPORTABLE enclosures, an IC-7000, and a Dell Zino HD computer. In one iPORTABLE I installed an LDG AT-200pro and the IC-7000. The other iPORTABLE contains an Alinco DM-330MV power supply and the Dell Zino.
The iPORTABLE enclosures keep everything contained and compact. I’ve set them up, one stacked upon the other on my desk near the window in my quarters here in Korea… which makes it easy to connect to the antenna feedline.
When I recently received my Buddipole and subsequently got on the air, I looked to an Ubuntu solution for managing my log, digital modes, as well as rig control. Fldigi, by itself, was great for digital modes… but was difficult to get working with my Dell Zino’s sound card and my West Mountain Radio’s (not so) Plug & Play RIGBlaster. Using Grig for rig control was unsatisfying. Logging with Xlog worked, but it wasn’t integrated with either rig control or Fldigi. I was looking for a similar experience that I got from Ham Radio Deluxe.
Many of the Linux crowd bash Ham Radio Deluxe – and I am not fully sure why. First off – it is free… doesn’t cost a dime. The two primary gripes are that HRD doesn’t offer a linux version and that the overall software package is bloated. I’ll be the first to say that I used HRD for quite a while and found all its features quite useful. The integration of its digital modes software package with HRD made HRD that much better. I used HRD as my primary logging/digital modes suite when I was operating from Iraq and the software never let me down.
That being said… I still wanted to find the Linux solution, if for no other reason than to just do it. I tried shackbox. shackbox was on the right path, but installation was a bit wonky and then the developer stopped supporting it. Linux In The Ham Shack taunted me with the elusive vision of a amateur radio station seamlessly powered by Linux. Using WINE to run HRD under Ubuntu seemed ridiculous… using WINE, to me, seems to defeat the purpose of having Linux.
Fldigi has long been a linux ham radio star. Featured in the January 2010 issue of Linux Journal, it is a favorite. But for me, it wasn’t a replacement for HRD. It lacked full rig control and the logging was pretty basic. CQRLOG offered a solution. It claimed to integrate Fldigi and provide top-notch logging along with rig control. Was this the solution I was looking for?
For hardware, I selected the Dell Zino HD. It has a small form factor – just fitting into one of the two shelves in the iPORTABLE enclosure. The computer ended up being easy to configure as a dual boot – Windows 7 and Ubuntu. I tried using Fldigi, but kept running into problems. Thinking it was a problem with the Zino’s soundcard, I ordered one of those USB stick soundcards from Startech.com… which I got and stuck in the drawer, still in its blister-pak.
The arrival of the Buddipole spurred a renewed sense of urgency to achieve a Linux-ham solution. I tried to install CQRLOG… it looked like it installed fine but when it I tried to start it – nothing happen. Caught between a decision to get on the air and participate in CQ WW DX Contest or dork around with Linux, I defaulted to using Windows 7 and HRD.
Now that the big contest is over – I decided to tackle this issue of ham and linux. The problem, as I’d left it, was that CQRLOG wasn’t working and I had a questionable soundcard. After researching, Googling, peeking, and poking I figured out that the problem was that CQRLOG does not play well with 64-bit distributions of Ubuntu. I reinstalled Ubuntu using a 32-bit distribution, installed all the required libraries, configured, make’d, sudo’ed make install…. and then…. it WORKED! After more tweaking with the rig control, Fldigi worked along side CQRLOG. Flrig as well – which is a great rig control app.
The final nail in the coffin for Windows and HRD was when I exported my log and then imported into CQRLOG… without issue. Now I am truly Spinning and Grinning in a 100% Linux Nirvana.
Today was a real adventure on the airwaves. I only made 12 contacts, but there were a few that are quite memorable. My location here in South Korea affords me the ability to make contact with exotic locations even with my modest Buddipole antenna. The first contact wasn’t actually a contact – tuning around 20M, I stumbled across 9W6HLM and 9W6BOB operating from Borneo (yes, 9W6BOB is Borneo Bob… how cool is that?). Both stations were on the air, leisurely trolling for contacts… although they couldn’t hear me. I was able to hear them work Denis, WA5TYJ, in New Mexico. Fortunately, the noise level for me was very low and I could just hear Denis.
The next two contacts were with JA’s – a completely unremarkable accomplishment from the QTH here in HL-land. However, they were made using my newly basedlined Linux Ubuntu hamputer using CQRLOG, Fldigi, and Flrig. Again, an unremarkable accomplishment on the face of it… until you hear about my trials and tribulations of getting it working.
Then I worked ZS6CCY, a South African station, on 20M phone! That was pretty exciting. I switched to Fldigi to give PSK31 a try and was able to work a few Russian stations. Then booming down the waterfall came Kim, HL2DYS. I had yet to work another station here in South Korea… but I had to be patient. Kim was working the South Pacific and Europe. When there was a hole, a jumped in and we had a great QSO. Hopefully I will be able to meet Kim soon for an eyeball QSO.
There was a major JA phone contest underway, so I decided to head up to 17M and see if I could scare up another phone contact. While spinning and grinning I fell upon V73RS… Rob on the Kwajalein Atoll in the Republic of the Marshall Islands. Wow!! He was just above the noise level and I was his first contact before the spotters got him and the pile-up hit. Rob stuck with me, which is saying something. First – because my callsign here is HL2/AD7MI…. which is horrendously difficult to pass across less than desirable band conditions. Second – Rob wanted the name of my city, which is Uijeongbu (I spell: Uniform India Juliet Echo Oscar November Golf Bravo Uniform). It is quite a mouthful. The pileup kept building, but Rob stayed with the QSO and told me he was there on Kwajalein and that I should look for him on 10M, as conditions generally more favorable for a 2-way exchange.
Back to 20M where I worked another Russian station. Then I snagged JT1DN, a station for Ulaanbaatar, Mongolia. It is hard to get more exotic than Ulaanbaatar. Mongolia is not actually far from Korea, but it was my first contact ever with the country and I won’t soon forget it.
Maintaining the exotic theme – my next contact was with YC9ETJ – Bali Island, Indonesia. Agung had quite a pile up and I was glad to get picked up by him.
Sunset and the grayline approached and I was successful in working Poland and Norway. All in all – I was quite excited with the contacts for the day.
My Field Day adventure started on Tuesday, 23 June. I finished the final touched to the eARSIB and then through every possible item I thought I might need (minus a 25 pin to 9 pin cable for a Kantronics KPC-3+ which I will talk about later) in a total of 3 footlockers. I packed up the truck, loaded up the dog and was on the road by 10:30am. There was good APRS coverage on my route along I-80 up until western Nebraska where I encountered an almost 200 mile gap. Once I hit Cheyenne, I was back in APRS coverage. My stop for the first night was Laramie, Wyoming, which I made before sunset.
The next day I pushed on west. While in western Wyoming I was able to check into the 40M Sparkle Net (7262 kHz) and talk with Dave, KE0DL, back in Leavenworth, Kansas. I also noticed on my GPS that one of the APRS stations was moving along I-80 the same direction that I was going. I gave a short call on the 2M National Simplex frequency and got a reply. We had both started the drive in Wyoming but parted ways in Salt Lake; he headed south on I-15 to Vegas, I kept west on I-80. I enjoyed the drive through eastern Utah. Park City, Utah is a place I had spent a lot of time skiing about twenty years ago. I’d been there often in the winter, but this was the first time seeing it during the summer.
Traffic was heavy through Salt Lake City and I did my best to make my way around the city as quickly as possible. West of the Great Salt Lake, I had an interesting HF QSO with a gentleman in Southern California who was using an Elecraft K3 with an the diminutive MT-1 antenna. My initial plan was to spend the night in Winnemucca, Nevada but upon arriving discovered they had me on the second floor in a non-pet room. Instead of hauling my footlockers up a flight of stairs I decided to push on to Fernley, Nevada (just east of Reno) where I found a great hotel with a first floor room I could practically back my truck up into. The dog liked it too.
Thursday morning I worked my way up the eastern side of the Sierra Nevadas, listening to a few 40M nets. I reached the Sonora Pass around noon and enjoyed the view. The dog a I hiked up to a nearby plateau and took in the view.
After traveling down the western side of the mountains I was able to raise my dad, KD6EUG, on a repeater near his cabin in Mi-Wuk Village. California Hwy 108 wound its way down from Sonora Pass. The drive was spectacular along the scenic route and traffic was sparse. I rolled down the windows and opened the sun roof to take in gorgeous day. Reaching the cabin in Mi-Wuk, both the dog and I got to strech our legs and rest up. Thursday night we assembled the gear that would become a permanent station at the cabin: an IC-706MKIIG, LDG Z-11 Pro, RIGblaster PnP, IC-208H, all powered by an Icom PS-125. In addition to the radio gear, the station would also integrate a Davis Vantage Pro2 weather station, beaconing the weather data view APRS.
To simplify the APRS setup in the cabin, I decided to use a special add-on piece of equipment from Davis specifically designed to be used for APRS – the WeatherLink APRS streaming data logger. The data logger, once configured, streams weather data directly to a TNC, eliminating the need for a computer (or UI-View32). With this setup, it was not necessary to leave a computer running to keep the weather station pushing data to the TNC and VHF radio. The weather data is formated by the data logger to be ready for transmission into APRS. The station also has a laptop which I installed the WeatherLink software that would allow me to configure the APRS data logger. Configuring the data logger was pretty straight forward. Setting the parameters in the TNC to grab the data loggers APRS weather info proved a bit more challenging. The challenge was further compounded by my forgetting to pack the 25 pin to 9 pin cable that connects the laptop to the Kantronics KPC-3+ TNC.
The real work started Friday. The first task was completing the installation of a Davis Vantage Pro2 weather station on the cabin roof. That was done without much trouble.
The next step would be to get the weather data out via APRS using the IC-208H paired with the Kantronics KPC-3+ TNC and the Davis APRS streaming data logger. With the lack of a good cable to use between the laptop and TNC as well as not knowing exactly what parameters were need in the TNC we decided that task would have to wait until after Field Day.
Now it was time to string some antennas. The first was a 132′ dipole which ran N/S. I’d packed my CVS19 Pneumatic Antenna Launcher (aka tennis ball launcher) which helped us position the antenna up about 40′.
Next we strung a G5RV going E/W. This is the same G5RV I bought from a fellow ham when I lived back in Virginia. He had never used it and I had used the antenna only once while running a special event station at Fort Monroe.
It quickly became apparent that we could not both operate using both antennas due to their proximity to each other and surrounding powerlines prevented us from placing the antennas end to end in order to minimize interference. The solution: my dad’s Force 12 Sigma 5. The problem: the antenna was back in San Jose. So Friday night consisted of my dad traveling back to the Bay Area to retrieve the vertical antenna while I continued to configure the laptop (N3FJP Field Day networked logging software, Digipan for PSK-31, and the Davis Weatherlink program) in addition to setting up my operating position on the back deck of the cabin.
My operating position setup consisted of a 10′x10′ pop-up shelter (with mosquito net) and a large table with comfortable folding chair. Inside the shelter I placed a large table with the eARSIB and my station’s laptop.
I verified that the laptops at either operating position (the one inside the cabin and mine outside on the deck) could communicate via WiFi using the N3FJP software: it worked like a charm. The software allows two (or more) operating positions to share one log. Each operator gets to see the combined log and is notified of potential dupes.
Saturday morning my dad arrived back from the Bay Area and we setup the Sigma 5.
My operating position on the deck had the antenna connections for both the G5RV and the Sigma 5, my dad’s position had the 132′ ladderline-fed dipole. Interference between the two positions was sometimes a problem. I could use the Sigma 5 vertical on 20M, 15M, and 10M as long as my dad stayed on 80M or 40M (as long as I wasn’t on 15M). While this slowed down operations a bit, it gave us time to take plenty of breaks. My dad started Field Day by working PSK-31 on 20M. I worked phone contacts on 15M and 10M. Later my dad switched to phone, which he really started to enjoy.
10M and 15M were really incredible. I was able to work all the way to the East Coast and up and down the West Coast. For dinner, I BBQ’d some brauts. By midnight we were both exhausted and decided to get some rest.
I enjoyed using my eARSIB. This is the first time I used a foot pedal for my PTT – paired with a Heil headset. That worked great, allowing me to use both hands on the keyboard. I had been unable to configure the West Mountain RIGtalk to work on my laptop – not sure why. But it wasn’t too hard to just flip the band in the logging software. I had not used my Logikey CMOS4 Keyer in some time. I paired it with my Vibroplex paddle and the two worked well together. I enjoyed a few QRS CW QSOs – thank you for those who took the time to slow down for me. I had picked up a marine battery to use with my PWRgate and that worked well.
Sunday I got up after four hours of sleep and started working 80M using the G5RV.
The G5RV worked nicely and I contacted stations from Western Canada down to Southern California and Arizona. I moved up to 40M and expierenced similar results – but was also able to work a station in Japan. My dad was up soon and started to work on 80M and 40M with the 132′ dipole while I switched to the vertical and worked stations on 20M. By about 11:30am we were both pretty much spent. Overall we made about 250 contacts, mostly phone but also a few PSK-31 and CW…. and we had a great time!
KD6EUG Brags About The Number of QSOs He Made
We slept well Sunday night and Monday morning had me back working on the Kantronics KPC-3+/Davis weather station. The biggest problem I was having was figuring out what value to use for the GPSHEAD parameter. Without the correct value, the KPC-3+ was not grabbing the weather data. GPSHEAD would pull in the data a place it in LT (a buffer). LPT setup the APRS path. BLT setup the amount of time in between the TNC initiating a beacon transmission containing weather data.
After a few calls to the Davis headquarters, I was able to figure out that “@” was the magic value for GPSHEAD. Now the weather station is up and operational.
It was then back on the road, up and over the Sonora Pass. I was able to talk to my dad, operating from the Mi-Wuk cabin station, on 80M from the top of the pass. I spent the night in Carson City, Nevada and the next day headed east on I-80. I had made the decision to take I-70 back to Kansas in order to try something different as well as seeing a part of Colorado I had never seen before. It was a long haul to Grand Junction, Colorado – I arrived around midnight. After a few hours of sleep, I was on the road again heading east through some of the most beautiful scenery of the trip. Aspen and Veil were beautiful cities – I hope I get a chance to go back there someday. But while the drive was scenic, the going was slowed and progress was not nearly as quick as I had experienced before while moving through Wyoming and Nebraska.
I finally emerged from the Rockies and headed into Denver, stopping at the Ham Radio Outlet located there. Terry, KC0VFO, and I talked about our Field Day experiences – he operated mobile. His call sign looked familiar and sure enough, I had worked Terry on 15M during Field Day.
Moving east through Denver I was back on the open road, moving rapidly along I-70. I heard a call coming over the 2M National Simplex frequency. It was a gentleman operating from the Mt. Evans Observatory – we had an enjoyable QSO and he went on to work others. The Canada Day contest was also underway and I started to hand out contacts from the mobile. I had planned to make it all the way back to Leavenworth, Kansas but realized I was too tired and needed to spend the night somewhere. I crossed the Colorado/Kansas border and arrived in Goodland, Kansas were I found a hotel room and promptly fell fast asleep.
My final day on the road was pretty easy driving. When you think about Kansas, it is usually what you see in western Kansas along I-70. Flat terrain, lots of farms, not much else. For some reason, the speed limit max in Kansas drops to 70mph (Nebraska, Wyoming, Nevada, Utah, and Colorado all have a max of 75mph). I listened to some of the morning HF nets on 80M and 40M, then made contact with K2L, a special events station in Charleston, South Carolina. I was also able to check into the Sparkle Net on 40M and then later worked two stations on 17M, both located in and around the western border area between North and South Carolina. Soon I was back home, arriving before 3pm.
It has been a cold, rainy Sunday. We are on short final for the delivery of child number two… about 12 more days. Spent part of the day finishing the fixes to the nursery. Despite the rain, I BBQ’d two excellent steaks for dinner. I spent a good amount of time at Fort Lewis, WA so BBQing in the rain is no big deal.
Yesterday I mounted a bike seat for my daughter (age 3) on the back of my underused Trek bicycle. The weather was pretty nice, sun and a little cool. I decided to take along my TH-D7A and mounted my Garmin eTrex on the handlebars… I was APRS bicycle mobile again (with a small passenger). I kept the power setting at EL (50mW) and had good luck getting digipeated by N7FTM, which is nearby. To get a little better coverage and maintain the low draw on the battery, I configured the home TM-D710A to digipeat only the packets from my TH-D7A. I hope the weather improves soon so I can do some more bicycle mobile testing. A speaker-mic would also be a great addition to the setup.
I have been doing a little more reading on APRS (when I should be working on homework). One item that I found very intriguing was CQSRVR. There is a good run down of that feature here and Bob “Mr. APRS” Bruninga’s, WB4APR, recent article in QST. What amazes me is that the CQSRVR feature is not used more often. I have also had a great time playing with aprs.fi. I am a long time user of findu.com, but aprs.fi is just a wonderful tool to use in looking at APRS data.
It is time to get ready for Field Day. The plan is to road trip out California and link up with my dad, KD6EUG, at his cabin in Mi-Wuk (near Sonora, up in the Sierra Nevada Mountains. We will be a 2A operation. My rig will consist of my resurrected ARSIB (Amateur Radio Station In a Box). The ARSIB is based around the FT-817ND. To give the FT-817ND a boost, I’ve paired it with a 100W Tokyo HyPower amplifier. The tuner remains the LDG Z-11 PRO. I would like to have both a rig control interface and control cable from the radio to the amp but the the FT-817 has only one ACC input. Enter the CAT MATE – I am hoping this will solve the ACC input limitation. For a logging program I think we will go with the N3FJP logging software. It offers the ability to have two (or more) seperate stations have a combined log. It also features a software-based voice and CW keyer, which may come in handy. The downside is it is a Windows only program and it does not have integrated PSK-31. This will require a manual work around to add PSK-31 QSOs. I need to get all the pieces and parts together and start testing everything out to make sure there are no surprises. We will be busy enough stringing antennas and I want to minimize any adjustments I need to make to my own equipment during actual operation.
It’s time to dust off the Amateur Radio Station In a Box (ARSIB) and get it ready for field day.
Back in 2006 I was inspired by other hams who had put together portable stations that were built inside waterproof containers, capable of multimode (phone, CW, digital) HF, VHF, or UHF operation, easily powered by 110v/220v AC or a 12v source, able to carry with one hand, and ready for immediate operation with minimal setup.
My prototype was the ARSIB which I used on several occasions.
The ARSIB was based around my FT-817 to provide complete flexibility of a minimalist operation on AA batteries if need be. For normal operations, the 100W Tokyo HyPower amplifier gets me were I need to be. I had a lot of fun with the ARSIB using it during an RV DXpedition and for a lighthouse activation.
I now want to take the ARSIB to the next level – fine tune the design a bit. In searching around I have found several sources of inspiration:
For my second generation ARSIB, I would like to improve the inner shelving structure supporting the radio equipment. Another goal of mine is not to put any holes in the waterproof container, which has limited some of my arrangements inside the box. I also want all the equipment to be able to travel well, without worry of damage. I also need to clean up the wiring; power, audio, and antenna. Some more ascetically pleasing, but functional.
I think the Dell Mini will serve as the perfect companion for the eARSIB.
Ultimately I hope to use the eARSIB (“e” is for enhanced) for Field Day 2009. The plan now is to link with KD6EUG, Larry, up in the Sierra Nevada’s for Field Day. In addition to participating in the event, we will string up an antenna or two for his cabin/shack… and maybe even get an APRS weather station operational as well.
I enjoyed AB9RF and KE9Vs recent postings concerning the ending of the “era of the communicator” – I am a big fan of both blogs. Kelly (AB9RF) argues that to continue to attract new hams, we need to focus the image of ham radio not as a means to talk to far away place (as this can be accomplished with any cell phone) but as a means to explore the latest computer technology. I understand her point but disagree with her premise. The best refute is Dave Bushong’s blog 99 hobbies (although not updated recently). As the title of his blog indicates, ham radio is a multifaceted hobby… DX QSOs is just one element. Kelly further argues that the ham community is in danger of loosing some of its spectrum privileges if the community is mired in the past by an aging population of hams who have failed to contribute any innovation to the radio art in recent memory. D*Star, Echolink, WinLink2000, APRS, PSK31, and Olivia immediately come to mind. Look at usage of 2M repeaters in your area – chances are if you wanted to set a repeater up yourself, you couldn’t because all the bandwidth is already filled. As hams, we are communicators, we are innovators and ham radio is what we make of it. Unfortunately, I’d say the key argument to maintaining our amateur spectrum is not in innovation but in disaster and emergency communications support. Now I am not an orange-vest wearing, special badge and whoopy-lights on the top of my truck guy… but from my perspective, emcomm has earned us respect from the general public in the past (… just look at Katrina). I for one am glad there is a devoted following of hams who support emcomm, although I do not fall in that category. I do believe that all hams must maintain a basic capability to use their equipment to provide support in an emergency…. nothing fancy, just the basic ability to pass traffic or relay a message. But I truly believe that the hobby will continue to survive due to the vast variety that is available to we hams, the practitioners of the radio arts. The ionosphere’s the limit… oh, no wait – now you can reach out to the Sun as well.