Misconduct and Consequences

Larry, W2LJ, recently wrote about a topic that all of us can identify with, the LID in a DX station pileup who ignores protocol and has no sense of manners.  They ignore DX requests for specific stations to respond and just blast the frequency, often with high power, until they get their contact.  The problem has existed for decades and is nothing new.  It’s one reason why I get turned off by DXing (despite dreaming of going on a high profile DXpedition someday), and it’s especially frustrating for a QRPer where timing and skill are much more important due to the power disadvantage.  Conversely, RF power often makes up for a lack of skill or manners, and the DX pileup LID makes a nuisance of himself to the point where the DX station can’t ignore him, and rewards him with a QSO.

The problem has been going on too long.  The reason it continues to exist is much like why we have email spam after nearly 20 years of the “mainstream” Internet.  There’s no cost associated it, and the bad behavior is rewarded.  The DX Code of Conduct is a great model for people to follow, but unfortunately it’s only the honest and polite people who follow it.  There must be consequences for bad behavior.

First off, DX stations need to stop rewarding these LIDs with contacts.  They need to call them out and let them know they’re not getting a contact during the DXpedition.  Perhaps we could create a specific Q signal that says “you’re blacklisted” to keep it short and sweet and avoid long on the air explanations.  Or they can work the station and not QSL the contact and let the station know through some means they got a non-QSL for their bad behavior.

Second, DX organizations and organizations like ARRL, CQ,  and perhaps RSGB need to maintain a “three strikes” policy.  If they receive evidence, such as recordings, of bad on the air behavior three times within a given period, the offender has awards stripped and they’re identified on a blacklist that can be accessed by high profile DXpeditions.  The minutia of appeals and reinstatement and the level of public notification can be debated, but I think the basic idea is sound and something that needs to be done.

This all may sound harsh, but in order to change bad behavior there needs to be consequences. All too often in amateur radio we don’t call out bad behavior and it affects the enjoyment of the hobby for the rest of us.  It’s time for the organizations who have the power to enforce consequences, to take action, rather than continue to provide rewards.

Don’t Fear the Penguin

penguinIt’s day four of my hopefully last Windows-to-Linux migration, and so far so good.  I have my HRD log imported into CQRLog and it’s talking to both my Arduino Keyer and Yaesu FT-897.  The Keyer is happily sending CW and CQLog is reading the rig frequency.  The rig control function is very simple and utilitarian compared to HRD’s, but it works.  What I cannot get working is controlling the Kenwood TS-850.  This appears to be a problem with Hamlib, which CQRLog uses via rigctld.

I found that Linux re-enumerates USB /dev/ devices if you unplug one.  For example, I had my Arduino Keyer at /dev/ttyUSB0, my TS-850 interface at /dev/ttyUSB1, and my FT-897 interface at /dev/ttyUSB2.  Upon unplugging the Arduino Keyer and TS-850 interface, the FT-897 became /dev/ttyUSB0, and with nary a mention in syslog.  I find this behavior strange.  But I’m really pleased Linux handles USB device insertions and ejections so well.  Back in the day to do stuff like this you’d have to edit some text file, recompile your kernel, and walk uphill in snow both ways.

To run N1MM I installed Virtualbox and within that installed a very bare bones Windows XP installation.  This enables me to run Windows XP as a virtual machine within Linux, without rebooting.  N1MM installed and ran without a hitch in the virtual machine. I was reminded N1MM likes to install in C: root, like it’s 1994 on Windows 3.1.  But I digress.  Attaching host USB devices to virtual machines in Virtualbox is a piece of cake and I had N1MM talking with the 850.  So I’ve got my contesting needs covered.

It occurred to me that it wouldn’t take much to get CQRlog to do basic contest logging.  It already has cw interface keying and function key definitions and macros.  All it really needs is serial number generation with corresponding function key macros, previous QSO report lookup, and perhaps a little more field customization.  This would cover the basics.  One can handle scoring outside the program, but a band map with the DX cluster integrated would be the next feature on the list.  I may just look at the source code and see if I can make sense of it and maybe play around with some customizations.  I sense another project I’m going to get sucked into.

So far I haven’t had to go back to my native Windows installation for anything, other than to steal more disk partition space.  Maybe I cheated a little by installing an instance of Windows XP on Virtualbox, but hey, whatever gets the job done!

(Update: I just found the CQRLog band map window and it is integrated with the DX cluster!)

Migrating to Linux (Again)

I’m no stranger to Linux. I’ve run numerous distributions since about 1995, even venturing into BSD territory, running FreeBSD and some other Berkeley variants. I’ve also used Linux quite a bit in my professional life for servers. However, I’ve never made the jump to using it as my primary desktop operating system at home; it’s always been a novelty to play with and never a desktop workhorse that I would use to actually get things done.

Linux Mint is a Linux distribution that has become more popular recently. It’s based on the venerable Ubuntu distribution and appears to be taking some market share from Ubuntu. Ubuntu in my opinion went off the tracks with its migration to the Unity desktop.  For the first time recently I hit a brick wall trying to install the latest Ubuntu within a virtual machine.  While Ubuntu was quite polished and arguably had the best usability in the Linux world, I still felt that I was often fighting the operating system to make it work.

ScreenshotLinux Mint seems to have taken care of those issues. Last night I made the plunge and partitioned off some space on my hard disk and installed it so I could dual boot between Windows and Linux. The installation went extremely well and within two hours I was able to browse the web, play videos and hear sound, send email, work on Kicad schematics, compile Arduino code, open Excel and Word docs, do my banking with the same program I used on Windows, and I had amateur radio logging and digital programs installed. The only speed bump was getting my wireless working. I was able to fix that in five minutes after Googling and finding one command line to run. On previous distributions, items like this would take hours to resolve and there would be several of them to deal with. For the first time I feel I have something equivalent to what I had on Windows, and it doesn’t look goofy and didn’t require days of tweaking with arcane command line syntax to make it acceptable. The browser actually renders things like they look on Windows. You install a program and it actually appears in the menu. Quite simply, Linux Mint isn’t a compromise like previous desktop installations.

I’ve often complained about the state of amateur radio open source software. I stand by my previous statements as I think we still don’t have a suite of amateur radio open source software that compares with offerings in Windows, mainly in the areas of logging and contest programs. However, CQRLog has evolved quite a bit and I’ve decided to take a more minimalist approach and see if I can make it work. I still think Ham Radio Deluxe is the gold standard, but lately I’ve become annoyed with its bloat and the commercialization and marketing of it.

I’m still keeping my Windows partition, mainly to run one particular contest program and store my documents (which I access from Linux), but I may eventually run Virtual Box on Linux and have a small Windows installation virtualized to run the contest program rather than booting back into Linux.

Will this be the time I finally run my shack on Linux?  I hope.

I Was A Radio Pirate

skullBack when I was a young radio artisan I would eagerly await my monthly copy of Popular Communications to arrive.  My favorite column was Pirates Den which covered the latest happenings in pirate radio such as new stations, signal reports, programming, and stations shutting down, either voluntarily or involuntarily at the hands of FCC enforcement.  The often grainy black and white images of stations with masked DJs seemed like a glamorous and exciting thing at the time.  Back then you couldn’t just setup your own audio stream on the Internet and broadcast to the world.  As a pirate you could say whatever you wanted, play whatever music you liked, and all the while stick it to the “man”, the brutal, authoritarian FCC.  Fines at the time were only a few hundred dollars, paltry by today’s standards.

There were basically two pirate “worlds”, local broadcast and shortwave.  Shortwave stations would operate just above the 40m amateur band.  In later years the pirate band moved to below 40m.  Other frequencies on other international shortwave bands were used, but the neighborhood around 40m seemed to have the most action.  Local broadcast would be done mainly on FM radio.  I actually can’t recall a report of an AM broadcast pirate, but I assume there were a few out there.  But considering the effort and equipment one had to put into an AM broadcast band operation, those people with the skills and inclination to go to that effort probably did shortwave pirating.

I had dreams of becoming a real DJ and perhaps owning my own commercial FM station one day, but luckily I realized that the broadcast industry had a rather low pay to frustration ratio and steered clear of it professionally.  In college I finally got the gumption to attempt to become a radio pirate.  I didn’t have two nickels to rub together at the time, so any purchase was a big decision.  I sent away for a mail order FM radio kit.  It was mono, not stereo, but it boasted a phase-locked loop (PLL) and a clean 1 watt output.  Paradoxically, being a licensed radio amateur I wanted a very clean and professional pirate FM signal.  I assembled the kit, however, much to my dismay after weeks of trying to get the PLL to lock up, I gave up and tossed the unit in the closet.

Two years later I was working professionally in the RF world, working on TV transmitters around the globe.  I learned a lot in this new world.  Being a field engineer in the middle of nowhere like South America or the Middle East with a minimal assortment of parts and people staring over your shoulder expecting you to fix their only transmitter in the village makes you learn quickly and think on your feet.  This is something they don’t teach in college or outline in an ARRL Handbook.  It was a rough job that no one wanted but I came into the company bright eyed and bushy-tailed and commanded more pay than some of the travel-adverse bench techs with years of experience under their belts.

One day I got bit by the pirate bug again and snuck a spectrum analyzer out of work to my bachelor pad.  I got the bright idea of bypassing the PLL and just driving the voltage controlled oscillator with a multi-turn pot, also borrowed from work.  The unit would drift but after a few hours warmup it didn’t require much adjustment to stay on frequency.  Later I found an old low band VHF TV amplifier rated for 25 watts at work.  It was a design that apparently was a bit unstable, but we had several of them lying around at work, destined for the dumpster.  I took one home and tweaked it up and found I could get 40 watts cleanly out of the unit.  Now I was in business.

I assembled a station, acquiring an audio mixing board and other components.  I built a ground plane antenna and got four 5′ Radio Shack masts to elevate it.  My third floor apartment was in a great location, in the middle of a nine mile long heavily populated valley in northeastern PA.

A college friend would come over Friday night and stay over for a pirate broadcast weekend.  We would do a few two hour shows and identify as WMRX, “the station jamming the nation.”  Though a bit kooky now, it sounded pretty cool back then.  We spun mostly records and a few CDs, and we augmented our programming with supermixes or song medleys recorded from a commercial station in Philadelphia.  We even did a ten minute fake news report with some comedy thrown in.  For a phone line we announced the phone number of the pay telephone across the street.  One of us would stand at the phone while the other announced the number on the air.   We never did have anyone call in.

One show ended early when my co-host got intoxicated and fell over.  Another show had to be cut short when a guest DJ announced my name over the air.  After each broadcast we disassembled everything, including the antenna and mast and hid it, naively assuming this would minimize our chances of getting caught.  Eventually work and life got too busy and complicated and the pirate operation stopped.  Every few years I fired up the transmitter, put a CD on, and just drove around to hear the signal and admire the coverage.  Although it wasn’t stereo and it didn’t fill every nook and cranny in the valley with RF, it was my signal, my station, built with my own hands, and to me it sounded wonderful.

Today FM pirate broadcasting lives on, as regular reports of FCC enforcement would attest with fines in the neighborhood of $10K to $20K.  It’s hard to tell if shortwave pirating is still alive.  It’s certainly not at the level it was in the 80s.  I get the feeling anyone with a desire to get a message out rather than just spin records or taunt the FCC has moved to Internet broadcasting or perhaps uses a blog to get their message out, though it lacks the mystique and excitement that pirate radio once had.

Review: Hamshop.cz Open Keyer

keyer2

The Hamshop.cz Open Keyer is a cute little keyer kit that is Arduino based and runs my open source keyer software.  It features a menu button, three memory buttons, a speed control, a PS2 keyboard connector, and a USB port.  The unit can be powered either through the USB connector or an internal 3 AAA battery pack.  A 1/8″ (3.5 mm) stereo jack is provided to connect your paddle and two phono connectors are for keying your transmitter key and PTT lines.

The brains inside the box is an Atmel ATMega chip running the Arduino bootloader, along with a USB chip.  Essentially it’s an Arduino and the normal Arduino development IDE can talk to it and program it.  As mentioned before it’s intended to run my open source keyer code, but it can be used with any Arduino code including your own keyer implementation. If you don’t need a PTT line for your transmitter, you can easily modify the source code to use the PTT port and a second transmitter keying port.

Most of the circuit is surface mount technology (SMT).  I hadn’t soldered SMT components for several years.  Last year I got my first set of reading glasses, and I found myself cursing the little parts, which in my more youthful years I’d have no problem working with.  This is no fault of Hamshop, just me whining about my age.  Luckily Hamshop pre-installs the ATMega and USB chips, so the most difficult components are taken care of for you.  The enclosure is a very simple but effective extruded aluminum two-piece clamshell or channel with two end pieces for the front and back.  Vinyl decals are provided for the front and back, and an instruction decal is provided for the top.  (Although my callsign is on the front of the unit, note that I did not design the hardware or kit.)

keyer1

The unit performs well, though I accidentally left it on battery power for a few days and totally drained the batteries.  This prompted me to add a sleep mode feature to my code which is in beta testing and should solve this problem.  One minor issue with the Open Keyer kit is the front speed knob.  On my unit it does not fit well, with not enough of the potentiometer shaft exposed for the knob to grab on to. Ondra, OK1CDJ, at Hamshop tells me that they’re adjusting the alignment of the potentiometer in the next revision to address this problem.

I won’t review the actual keyer software as the documentation for this is here, and naturally I’m a bit biased about it, but it does about anything a CW aficionado would want to do.  All in all the Hamshop Open Keyer is a nice little kit that can be assembled in an evening or two, and is reasonably priced.

(Full disclosure / disclaimer: I do not have a financial interest in Hamshop, and I can’t provide support for this keyer hardware.  Support for the open source code is available on the Radio Artisan discussion group.)

Obligatory New Years Post

Greetings and Happy New Year!  Our celebration last night was one that married 40-somethings with kids often have — a night spent at home watching Dick Clark’s New Years Rockin’ Eve.

On the amateur radio front, this past weekend I participated in the Stew Perry Challenge, a 160m all CW contest.  I debated whether to go QRP or 100 watts and decided to go with 100 watts.  Although I can’t brag about the amazing performance that QRP and a rather modest inverted L would have given, I certainly had as much if not more fun than last year’s event.  I netted over 180 contacts in my casual operating effort, even bagging about six west coast stations.  I think the Stew Perry Challenge is a cool little contest, perhaps underrated.  Its uncommon exchange for an HF contest, grid squares, and its unique scoring that takes into account distance and worked station transmitter power makes for an interesting contest.  I wrote in my notes for 2013 that I have make a serious effort and do all 14 hours in the test next year.

I can’t say I have any hardcore amateur radio News Years resolutions, other than “do what I like and like what I do”.  I started following this mantra three years ago and it has served me well. I tend to avoid getting into rituals but one I do want to start after authoring one last year is getting at least one amateur radio article published each year in a mainstream magazine (i.e. QST or CQ). I also tend to avoid competition, but I want to “up my game” in the PA QSO Party and also make more than a casual effort in one of the big contests.

In the Radio Artisan lab there are two main projects in progress. I have a working prototype of the Arduino based balanced antenna tuner. It’s been a technically challenging project, but very interesting. I still need to improve the SWR sensor performance and develop some shortcuts in the tuning algorithm to lessen the tune time. The other project is learning KiCad, an open source EDA program for developing schematics and PC boards. In the next week or two I will publish a post on my experiences. It’s not perfect but it’s definitely a viable replacement for the venerable and popular Eagle program.

Here’s to a healthy and prosperous 2013. Work, eat, sleep, and play radio.

Windows 8 Presents Opportunity

Brian Boyko, a freelance IT author, created this informational and rather entertaining video on Windows 8.

The video echos a lot of my experiences, albeit brief ones with Windows 8.  A few weeks ago I attempted to use a Windows 8 Surface tablet at a mall kiosk and left in frustration.  Last week while Christmas shopping I happened to venture into the computer section of a department store and played with a Windows 8 laptop.  After ten minutes of trying to make sense of the Metro interface, I again left in frustration.  I should mention I’m not a computer newbie. I’ve been using computers for over 30 years, and have worked with them in a professional capacity for over 20.  I used Linux before it was sexy and my first GUI based OS was Windows 3.1.  I’ve never owned a piece of Mac hardware (I have an iPad and an iPhone), but if you drop me in an Apple store and put me in front of a Mac, I can be web browsing, viewing pictures, and creating documents in moments.   I just can’t do it with Windows 8.

User interface changes are always stressful to end users.  The last major one Microsoft made was the ribbon bar in Microsoft Office replacing the venerable and admittedly long-in-the-tooth menu bar.  At first I hated it and customized all my Office applications to have the buttons I needed in the quick bar which sits up in the title bar.  Eventually I got used to the ribbon bar, but being a fan of minimalist interfaces I think the quick bar is much more efficient.  But, OK, I admit Microsoft was right with the ribbon bar and it’s a valid step in the evolution of user interfaces.

I won’t repeat everything in Boyko’s video, but he’s absolutely right on all points.  The Windows 8 Metro interface is a massive departure from the old interface.  The revolutionary change would be a good one if it was actually an improvement.  But similar to when Microsoft tried to put a desktop OS on a mobile device (Windows Mobile/CE), now they’re trying to shoehorn a mobile phone and tablet OS on to a PC, and it just doesn’t work.

This video goes into the desktop mode a bit more and shows the discontinuity between Metro and the desktop:

The changes in Windows 8 presents an opportunity for anyone who uses Windows, including amateur radio operators and software authors.  While Windows 8 has a compatibility mode that essentially lets you run legacy apps in a legacy pre-Windows 8 style desktop, it’s problematic.  If Microsoft doesn’t abandon Metro, they’re likely going to push application authors to the Metro interface, perhaps at some point even eliminating the legacy user interface.  With such a revolutionary change to this tool and its steep learning curve, it may be just as easy to migrate to Linux, Mac, or a Chromebook and learn something totally new that is actually going to be productive and useful.  With Windows 8, essentially Microsoft has increased the pain of upgrading to the point where it is equal or less pain to migrate to a different platform.  I suspect many people will horde old or bootleg copies of Windows 7 and XP, storing them away like a rare wine or expensive cigar, for use when getting a new piece of hardware.  It’s going to be interesting.

Why Are You Here?

The Newtown, Connecticut tragedy has naturally been dominating the news and conversation here in the US the past several days.  As happens after any horrific event like this, debates arise over the cause and how we can prevent such atrocities from occurring again.  Similar to previous school tragedies, this recent event involved guns and a troubled soul.  Predictably the media and the public debate homes in on gun control and mental health diagnosis and care.

I had a discussion with several of my amateur radio friends, all advocates of weapon ownership.  I own several weapons myself, though I limit my activities to sporting and don’t really get into personal protection.  One of my friends took the position that we need to equip teachers with weapons to prevent or lessen these now more frequent violent events we’re seeing in schools.  I countered that it’s not practical, besides raising a host of day-to-day safety issues, equipping teachers would require massive amounts of training to really be effective.  Weapons in the hands of the untrained are statistically more dangerous than beneficial, and training needs to go well beyond merely being able to hit a target.  Most people, myself included, just don’t have the time or inclination to get this training and maintain it.  It’s essentially a lifestyle, and one that I don’t care to live.  I don’t want to continually be preparing for the worst and have to carry a weapon in my daily activities.  To me it’s quite honestly a deplorable and depressing existence, one that we shouldn’t have to live in this day and age.

My friend responded that to an extent as an amateur radio operator, I do live that existence, preparing for disaster.  He saw amateur radio as part of a regime of self protection and preparation for bad times, and presumably got his license for just that purpose.  The difference between our perception of amateur radio immediately struck me, to the point that I had difficulty formulating a response.  I’m in amateur radio because I enjoy radio, not because it may help me get through a disaster or combat an enemy.

There is a sort of society that has developed in the US over the past several decades, one of a combination of “preppers”, doomsday-ers, cynicists and political prognosticators.  They have a rather apocalyptic outlook on life, where no one can be trusted, especially the government.  The ills of life can be tracked back to legislation, taxes, freeloaders, or merely those with opposing viewpoints.  These people seem to make it their mission to inject their mantra into day-to-day conversation, whether it’s at work, at church, or even on the air.  You often hear this tuning across the phone portions of our bands.  Often they feel some need to “educate” others, fire up outrage, or just spread their narrative of negativity, a tapestry of plausible but often incorrect quotes and statistics.

I sometimes think of my estranged father who past away two years ago at 62.  He often complained about the course of the country. His death was untimely and unexpected.  I don’t know whether he’s with a creator now, or if such a creator exists, but his death made me aware of the futility of agonizing over bad scenarios when our time here is so limited.  While we certainly want to make this a better place for future generations, does this agonizing over what is possible but not probable serve a purpose?  Looking at this another way, what good is stocking up on guns and ammo if you’re very overweight and you get taken out by a heart attack?

I’m here to enjoy life.  We’re beyond feudal societies, the threat of barbarians invading, and drinking out of lead cups.  The world is not coming to an end, not from this tragedy in Connecticut, not from whether I may have to register my weapons, not because we don’t teach religion in schools, not because I have to pay taxes, not because any particular person is President, not because some state legalized smoking a plant or allows any two adults to marry, and certainly not because someone says Happy Holidays instead of Merry Christmas.  I don’t want to spend my life as though everything is going to hell in a handbasket or live in continual fear or disdain of some enemy, real or manufactured.  But we seem to have a segment of our society living in this bubble or abyss, determined to pull the rest of us into it.

Why are you here, here on Earth?  Is it to live or just survive?  Perhaps you are concerned about the world, but are you concerned about it for everyone, or just for yourself, your wealth, and your rights?  We have a problem that needs fixed.  Venturing further into the darkness that led to it won’t solve it.  We need to focus on living, and not just survival.

Freeware versus Open Source

Today I was getting caught up on my reading of QST.  I had gotten two issues behind for various reasons, and was browsing the November issue.  In the editorial there was a quote from a popular contest logging program author implying that their software is open source.  I was really puzzled by this as I know for a fact that the software isn’t open source and I re-verified on the web that the source code isn’t freely available and is only given to select people upon request.  This software quite simply isn’t open source, it’s freeware.

There seems to be a lot of confusion within amateur radio over just what is open source,  and I’ve even seen amateurs berate others for wanting open source software because it’s thought someone wants a free lunch or wants to copy a product.  This couldn’t be further from the truth and it really shows an ignorance of the modern software world.  Amateur radio collectively has never really understood or embraced open source, opting for freeware offerings since the days of DOS.   Freeware software authors are often put on a pedestal in the community as selfless contributors doing a great service.  Most have good intentions, but freeware is not necessarily a good thing.

Freeware is not free and is a technological dead end.  Now that I’ve lost half my readers and puzzled the rest, please stick around and I’ll explain.  But first, what is freeware? Freeware is software that you can install without paying any licensing fee.  You can use it all you want and share it with others, but you can’t sell it, reverse engineer it, or modify it.   Freeware is not open source software.  You do not get the source code for freeware.

So how could freeware not be a good thing, or even a great thing?  It’s written by someone, one person or perhaps a team of people, giving their time and energy to a project that they derive no income from and get only satisfaction and accolades for providing a free tool to a group of users.  And, did I mention it’s free?  So, we should really be thanking them and indebted to them, right?  To an extent, yes, but long term they’re doing a disservice to the community.

Freeware “sits” in between commercial and open source software.  It’s my belief that commercial software is more beneficial to amateur radio than freeware.  With commercial software there is a motivation (revenue) to keep the product up to date and functional and not let it whither on the vine like some freeware projects have over the years.  With a commercial product, the desire for revenue drives quality and responsiveness to the user community.  With open source, quality drives usage and community participation.  If the product is popular, but quality later suffers, the community can fork a new initiative to maintain and improve the software based on the original project’s source code.  With open source there is a built-in mechanism to bypass lousy or absent code writers, or unfriendly supporters of software like we’ve sometimes seen in the freeware world.

Development of new features in the freeware world is usually at the whim of one person.  This can also be said of open source software, however because the source is available, anyone with the requisite motivation and skill can modify the code and not involve the original developers at all if needed.  Living within the walled garden of freeware is great until the gardener decides to stop maintaining the flowers. The same could be said of commercial software, but for better or worse money is a great motivator.

Often de facto standards develop around a piece of software.  This isn’t really the case with a logging program, but there’s a least one digital mode and one messaging system that have developed proprietary standards around them.  To interoperate with these standards one has to reverse engineer the standard based on the behavior of the application.  In the case of a messaging system, and one that is centralized, a homogeneous software environment can fall apart when a latent bug rears its ugly head.

So what is the reason for someone to offer freeware and not open source applications?  I’ve often pondered this question and can come to only one conclusion, a desire to someday go commercial with the product.  With open source, the intentions of the author are quite clear and in the open.  When a freeware software author refuses to open source their project for fear of it being copied and a competing product being created, they don’t quite understand that this sometimes happens in the open source world and as mentioned above, is known as a fork.  It usually occurs when someone feels they can do a better job improving the software and meeting the needs of the community.  Forks are often short-lived but in some cases a fork will become more popular than the parent it was spawned from and it becomes the de facto parent project.  This is a risk, but ultimately it’s a better process as it results in a sort of software Darwinism.  Forking is not plagiarism, as long as the original code is attributed to the original authors, and forking is an accepted practice in the open source community.  Nit-picky “armchair programmers” who are often the bane of freeware authors have nothing to complain about with open source as they can improve the software themselves or be put in their place when they discover they’re not really skilled programmers.

Open source enables collaboration.   I had to put considerable time into developing a specific feature on my open source Arduino keyer project.  If I would have had the source for a logging program that implemented this particular protocol, it would have saved me much time in developing this feature, or I could have even written and contributed a module for a logging program to implement the feature rather than having to write what I did for the Arduino in a roundabout way.  Arguably the Internet wouldn’t be what it is today, or perhaps not even exist, without open source software and the collaboration it creates.  Undoubtedly amateur radio has missed out on some collaborative opportunities over the years due to a lack of open source software.

I think it’s time for amateur radio freeware authors to take their commitment to the community a step further, embrace what became popular in the mainstream software development world two decades ago and open source their code for a long term benefit to amateur radio.

Lucky

Last night was a rather sleepless night.  As Larry W2LJ mentioned, the rain wasn’t so bad, but the wind was downright scary.  Up until about midnight I periodically went outside and walked around the house looking for damage, keeping my back and weight to the wind in order to not get pelted in the face or get blown over.  The wind sounded like a freight train coming over the ridge.  I was so glad I put temporary guy lines on the tower.  Other than some siding on corners popping out, there was no permanent damage occurring, however I noticed my HF tribander and 6 meter beam misaligned on the tower.  Under the force of the wind the tribander was beginning to turn and go off azimuth.  I rotated the antennas in an attempt to use the wind to true up the tribander.

About 3 AM I awoke to metal banging against the house.  I got dressed, went outside and found a 10 foot piece of aluminum flashing or trim dangling from the roof eave which shortly fell to the ground.  Other than that, no more damage.  Amazingly we still had electricity.

This morning when I awoke it was still quite windy and blowing the rain sideways, though not as violent as last night.  There was no further damage to the house, but the antennas were more misaligned than before.  So we were lucky here in Pennsylvania, and are thankful for having power and a home.  A lot of people in New York, New Jersey, and to the south and west of us in PA did not fare so well.