The FCC says you have a new callsign. Now what?

Once I knew that I had a new callsign, I sat down a wrote down a list of what I needed to do…

(1) 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 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 and register as a new user. I made a posting in the 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 If you get on the air before 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:

/home/EchoIRLP/ custom/tbd. conf
ConferenceCall =
ConferencePass =

/home/EchoIRLP/ custom/echo_ environment

/home/EchoIRLP/ custom/userdata. txt

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:

NI0L…. Happy Trails!

I have a new, bright, and shiny callsign!

When I made the decision back in 2013 to stay in Kansas after retiring from the military, I decided I would try to get a callsign for zero-land (or ten-land, if you like). It was time to leave my 7-land callsign and fully embrace being a citizen of the sunflower state. NI0L was available and I applied for it without much thought. After having the callsign for a while, I noticed many hams were confused with the 2×1 call. The most common mistake was flip flopping the zero and the “i”. Another common mistake was interpreting the “i” as one and then the zero would become an “o” (N1OL). All very confusing.

The hunt for a new callsign was on. I determined that a new callsign would still be from zero-land, thus greatly reducing the pool of available calls. In an effort to avoid callsign confusion, I further resolved that the call would be a 1×2 call. The good news was that the vanity callsign fee was no more. The bad news was that everybody and their brother was applying for vanity calls. For the last few months I kept at it – watching which calls became available and then submitting applications. Waiting. The odds where never in my favor. Often there would be 10 or twelve applying, all in competition.

Perseverance finally paid off. Last week the FCC said that I was now the proud holder of N0ZB. It is a 1×2 call, that should alleviate some confusion. The “zero” and the “zulu” may prove to be a bit of a tongue twister, but I think it will be far less of an issue and having the “zero” and an “i” next to one another.

The Day The Computer Died

I have been using small footprint computers in ham shack for a while. It started with the Dell Zino. Always a bit under powered, but enough to get the hamming done. The latest computer driving everything was one of those barebones models that was the size of a shoe box. The first sign of decline was when the fan kept getting louder and LOUDER. The the drive (500GBs of SATA) then decided to give up the ghost.

An immediate lesson learned… back up my log. I have been good at uploading my logs (almost daily, when on the air) to LOTW,, and eQSL. But I would only export that days contacts, consistently replacing the previous days exported log.

I choose not to abandon the small footprint computer and went back to the Shuttle. was my one stop shopping:

The case and motherboard: Shuttle XH81 Intel Core i7 / i5 / i3 / Pentium / Celeron 65W Intel H81 1 x HDMI Barebone system
– small form factor, fits neatly underneath monitor.
– 2x RS-232 connections on the back. Perfect for connecting to the Elecraft amp and tuner.
– Plenty of USB connections

Intel Core i7-4770S Haswell Quad-Core 3.1 GHz LGA 1150 65W BX80646I74770S Desktop Processor Intel HD Graphics
– not the fastest, but fast enough.
– comes with a super quiet fan.

Transcend JetRam 8GB 204-Pin DDR3 SO-DIMM DDR3 1600 (PC3 12800) Laptop Memory Model JM1600KSH-8G
– I got two DIMMs to keep things moving… 16GBs = snappy!

SAMSUNG 850 EVO 2.5″ 250GB SATA III 3-D Vertical Internal Solid State Drive (SSD) MZ-75E250B/AM
– Good bye disk, hello solid state. Faster. Silent.

The actual build was plug and play. The Shuttle line has come a long way since my last experience with their product. I think these specific computers are designed to operate older types of technology (hint…. 2x RS-232 connections?) which works great with most amateur radio needs.

The next step was loading the OS. LiLi USB Creator is my go to solution for installing linux when I don’t have an optical drive (which is more often the case). This allows you to load the OS through booting directly from the USB stick.

The linux flavor of the day: Mint with the MATE edition. I was an Ubuntu man until Unity. Then made the jump to Mint. The OS loaded without issue and I was off and running.

Amazingly enough, I was able to install TQSL-2.2. In the past, I have been able to install TQSL from the Software Manager. But this has been an older version of TQSL. The newer versions ALWAYS gave my problems with dependency issues during attempted installs. I stayed with it this time and finally got it working. Phew!

The install of fldigi went smoothe, but configuring it to work with my Elecraft K3 was giving me fits. In my past setup, I’ve always used hamlib for rig control and the trick was just finding which USB number was being used for my USB Microham III. But this time, the USB Microham III was identified by name as a choice. Great! But it didn’t initialize. I tried USB0 (…. nothing), combed over the results of lsusb…. not… working. After some intense Googling, I ran across a command I had never seen before:

sudo adduser [username] dialout

Dialout!? Who knew? But that did the trick.

Now, here is something funny. We all have our junk boxes. As hams, we are pack rats. We hang on to stuff that has no current use, but may someday. I had a box RS-232 cables. When Fall Cleaning swept through the ham shack, I looked at the RS-232 cables. I am really going to need 15 RS-232 cables ranging in length between two and 15 feet? The box headed to the dump.

Now, with my growing K-Line, I can use Elecraft software (linux versions available) to monitor data from the amp and tuner. But the connections are serial. SERIAL. I turned the ham shack upside down and not an RS-232 cable to be found. I really don’t want to have to actually go out and BUY a serial cable.