Sorry to have to lead with this, but this post assumes you’re a licensed Ham user. If you’re not, you can’t run this rig. Rules/Restrictions where I am located might be different for where you are. Know the rules applicable to you, stick to them.
Well I’ve been meaning to post this for a while. Below is a how-to for what I think is a really good choice for a basic minimalist HF comms setup for all of the Be Prepared people out there on the internets.
Before I start, I need to get a few things out of the way. There are a few keywords written above that I’d like to define for our purposes:
WHAT YOU NEED.
You need some gear. Get this stuff:
HOW TO SET UP.
In the “Comms” definition above, I mentioned the word “Easily.” Well, that’s intentional - If something isn't easily implemented, people won't bother to use it. I don't want that to happen here, so this setup is designed to be easy to set up. Here’s how to get it all working:
HOW TO USE IT.
Alright so you want to talk to check in with your buddies and see how TEOTWAWKI is going in their neck of the woods. Let’s get started:
That’s it. You have a simple, easy, portable setup that allows HF comms. Good luck with TEOTWAWKI and/or zombies.
For Fun:
Here's the setup in action, running a software called WSJTX, using a digital mode called FT8. Left side of the screen shows all of the signals that the laptop/4020 are picking up.
The point to be made is that a laptop + speaker wire + a bagel-sized radio = range of 2000+ miles. I don't have any pics handy of FLDigi/Olivia contacts, but I'll get something put together later that'll show everything in action.
***
That’s it for the practical application part. There’s some fluff posted below detailing the theory behind this build, if anyone cares.
THEORY/COMMENTS
Because I know there will be a bunch of “But ackshually…..” stuff pop up, I’m going to try and head those off here:
Digital? Fight me Millenial, voice is king. Yes, I picked digital on purpose. This is intentional. Digital allows for two very important things:
(1) Keeps things small. Don’t need to worry about handsets or speakers or audio or any other auxiliary bits of gear. Just a couple 3.5mm audio cables and that’s it.
(2) Digital modes allow “Comms” at low power levels/long distances.
#2 is critical. Again, my definition of Comms is having the ability to easily send/receive information between specific 3rd parties (ie. Your pals.) From a technical standpoint, voice modes (at low power) suck for that. I won’t get into the nerd stuff, but digital modes smack the crap out of voice in a ‘Distance vs Power’ comparison. It’s essentially why a 1-watt Morse code rig can compete with (and often do better) than 100-watt voice rigs in terms of long distance comms. (Yes, Morse is the OG digital mode.)
So if you want to make consistent, deliberate comms with specific people, to relay specific information, using a small (read: low-watt) rig, Digital is king. If you want to voice-chat with 80 year olds about your various aches and pains, this is definitely not the rig for that.
Just learn Morse Code. Sure. But when Digital modes rival or exceed CW in weak signal environments, why? (Reference here.) Everyone these days can write a text message or an email. That’s why this rig uses a laptop interface: You can get your non-prepper kid sister on the laptop, and she will intuitively understand what to do. You can’t easily do that with a Mountain Topper and a notepad. (There’s that pesky “easily” word popping up again.)
Well you can’t scan/listen to voice with this setup. It sucks. True, no classical voice or voice scanning. But, back to my definition of Comms: “The ability to easily send/receive information to specific 3rd parties.” Keywords here are Specific Parties. What this rig does is allow a person the ability to send/receive information to/from specific people. (Ham world generally calls this a “Net”.) In theory, all the appropriate people involved will have a shared comms plan, detailing times/frequencies that people will check in, protocols, etc. As long as everyone is dialed in to the right frequencies at the right times, you’ll have a very high chance of making contact.
What this means is that a person needs to have all of this stuff in place prior to the world ending. Same with your pals/buddies. Get a plan in place so that everyone knows what to do if you have to start using the radio.
What it doesn't involve is scanning the airwaves for stuff. The intention here is deliberate comms between specified users. You know, like calling mom.
Toughbook? Really? It’s maybe overkill, and a guy could get by with a regular laptop. However, because this rig is “Portable”, I’m assuming that the user is going to throw the gear into a pack or a truck, transport it somewhere, and get some work done. Electronics are no good if they won’t work. Rugged laptops are a hedge against Murphy.
Side-benefit: the CF19 has an onboard soundcard – No need for external USB soundcards/dongles. Just plug your 3.5mm cables in, and done. Pro-tip: colour-code your cables.
DR4020 is commie crap. Maybe. But, it’s the simplest digital rig I’ve found. No usb sound cards, no hamlib or Flrig or Omnirig CAT-Control troubleshooting, no software settings or tweaks involved, nothing. Literally plug in your 3.5mm connections, and that’s it. Nothing else required. If you colour-code the connections, it’s the easiest thing to set up. I can talk my kid sister through setting it up over the phone without breaking a sweat. Simple is good, and this little DR4020 rig is dead-nuts simple (Not sure how rugged it is, but it’s been holding steady so far. Get a Pelican case if you're worried.)
Olivia sucks and is too slow. That’s, like, your opinion, man. I’m not going to get into a huge technical analysis here. (Go read NBEMS theory for background if you want.) In summary, Olivia 8/500 gets decoded consistently, pretty much every single time, by all users and regardless of band conditions. Copy rates are easily 80%+ no matter what. For intentionally sharing accurate information with specific parties over HF, the Olivia modes nail it. It’s not perfect, but for my purposes it fills the role it’s supposed to: get info to people every time, without having to pray to sun cycle gods or other such nonsense.
I'm sure I missed something, but I think the above gives pretty good context into the purpose of this build. So that's all I have for now.
Well I’ve been meaning to post this for a while. Below is a how-to for what I think is a really good choice for a basic minimalist HF comms setup for all of the Be Prepared people out there on the internets.
Before I start, I need to get a few things out of the way. There are a few keywords written above that I’d like to define for our purposes:
- Minimalist = Small, portable, no overly-technical drama required to set up.
- Comms = Ability to easily send/receive accurate information to/from a specific 3rd party.
WHAT YOU NEED.
You need some gear. Get this stuff:
- Rugged laptop (Mine’s a CF19 Toughbook.)
- Venus DR4020 here.
- 2x 3.5mm male-to-male audio cables (already come with DR4020.)
- 12v power supply. I like this one here.
- Antenna (Here if you want to build your own.)
- FLDigi download here. (If you're running Windows, get the .exe one.)
- Beverage of your choice.

HOW TO SET UP.
In the “Comms” definition above, I mentioned the word “Easily.” Well, that’s intentional - If something isn't easily implemented, people won't bother to use it. I don't want that to happen here, so this setup is designed to be easy to set up. Here’s how to get it all working:
- Install FLDigi on the laptop.
- Plug the laptop HEADPHONES output to the DR4020’s data IN port.
- Plug the laptop MIC output to the DR4020’s data OUT port.
- Connect the antenna to the DR4020. (Assuming you’ve already set up the antenna.)
- Connect your 12v power supply to the DR4020.
- Turn on laptop, fire up FLDigi.
- Turn on DR4020.
- Done. (Remember to configure soundcard options on FLDigi - This is beyond the scope of this how-to, as it'll depend on stuff like Windows Vs Linux, onboard soundcard vs USB dongle, etc.)
HOW TO USE IT.
Alright so you want to talk to check in with your buddies and see how TEOTWAWKI is going in their neck of the woods. Let’s get started:
- Power up everything, get FLDigi open, etc.
- Physically dial the DR4020 to your frequency of choice (limited to 20m or 40m bands.) If the country you’re in has digital restrictions, stick to the appropriate frequencies. (Note: Ignore the frequency on the sceen in FLDigi – it isn’t linked to your radio, and has no effect on your operations. Dial your DR4020 to make the magic happen.)
- On the FLDigi top menu, click on “Op Mode” and select the digital mode you want to operate on. There’s a bunch of options/modes here, with hours and hours of cool reading and analysis avaialbe for all of them. To skip to it, in my opinion pick an “Olivia” mode.
- Navigate to the “Blue Box” part of FLDigi. Type your message into the Blue box section the screen, and then click the “TX >|” button in the bottom-right. (There’s more on this later.)
That’s it. You have a simple, easy, portable setup that allows HF comms. Good luck with TEOTWAWKI and/or zombies.
For Fun:
Here's the setup in action, running a software called WSJTX, using a digital mode called FT8. Left side of the screen shows all of the signals that the laptop/4020 are picking up.

The point to be made is that a laptop + speaker wire + a bagel-sized radio = range of 2000+ miles. I don't have any pics handy of FLDigi/Olivia contacts, but I'll get something put together later that'll show everything in action.
***
That’s it for the practical application part. There’s some fluff posted below detailing the theory behind this build, if anyone cares.
THEORY/COMMENTS
Because I know there will be a bunch of “But ackshually…..” stuff pop up, I’m going to try and head those off here:
Digital? Fight me Millenial, voice is king. Yes, I picked digital on purpose. This is intentional. Digital allows for two very important things:
(1) Keeps things small. Don’t need to worry about handsets or speakers or audio or any other auxiliary bits of gear. Just a couple 3.5mm audio cables and that’s it.
(2) Digital modes allow “Comms” at low power levels/long distances.
#2 is critical. Again, my definition of Comms is having the ability to easily send/receive information between specific 3rd parties (ie. Your pals.) From a technical standpoint, voice modes (at low power) suck for that. I won’t get into the nerd stuff, but digital modes smack the crap out of voice in a ‘Distance vs Power’ comparison. It’s essentially why a 1-watt Morse code rig can compete with (and often do better) than 100-watt voice rigs in terms of long distance comms. (Yes, Morse is the OG digital mode.)
So if you want to make consistent, deliberate comms with specific people, to relay specific information, using a small (read: low-watt) rig, Digital is king. If you want to voice-chat with 80 year olds about your various aches and pains, this is definitely not the rig for that.
Just learn Morse Code. Sure. But when Digital modes rival or exceed CW in weak signal environments, why? (Reference here.) Everyone these days can write a text message or an email. That’s why this rig uses a laptop interface: You can get your non-prepper kid sister on the laptop, and she will intuitively understand what to do. You can’t easily do that with a Mountain Topper and a notepad. (There’s that pesky “easily” word popping up again.)
Well you can’t scan/listen to voice with this setup. It sucks. True, no classical voice or voice scanning. But, back to my definition of Comms: “The ability to easily send/receive information to specific 3rd parties.” Keywords here are Specific Parties. What this rig does is allow a person the ability to send/receive information to/from specific people. (Ham world generally calls this a “Net”.) In theory, all the appropriate people involved will have a shared comms plan, detailing times/frequencies that people will check in, protocols, etc. As long as everyone is dialed in to the right frequencies at the right times, you’ll have a very high chance of making contact.
What this means is that a person needs to have all of this stuff in place prior to the world ending. Same with your pals/buddies. Get a plan in place so that everyone knows what to do if you have to start using the radio.
What it doesn't involve is scanning the airwaves for stuff. The intention here is deliberate comms between specified users. You know, like calling mom.
Toughbook? Really? It’s maybe overkill, and a guy could get by with a regular laptop. However, because this rig is “Portable”, I’m assuming that the user is going to throw the gear into a pack or a truck, transport it somewhere, and get some work done. Electronics are no good if they won’t work. Rugged laptops are a hedge against Murphy.
Side-benefit: the CF19 has an onboard soundcard – No need for external USB soundcards/dongles. Just plug your 3.5mm cables in, and done. Pro-tip: colour-code your cables.
DR4020 is commie crap. Maybe. But, it’s the simplest digital rig I’ve found. No usb sound cards, no hamlib or Flrig or Omnirig CAT-Control troubleshooting, no software settings or tweaks involved, nothing. Literally plug in your 3.5mm connections, and that’s it. Nothing else required. If you colour-code the connections, it’s the easiest thing to set up. I can talk my kid sister through setting it up over the phone without breaking a sweat. Simple is good, and this little DR4020 rig is dead-nuts simple (Not sure how rugged it is, but it’s been holding steady so far. Get a Pelican case if you're worried.)
Olivia sucks and is too slow. That’s, like, your opinion, man. I’m not going to get into a huge technical analysis here. (Go read NBEMS theory for background if you want.) In summary, Olivia 8/500 gets decoded consistently, pretty much every single time, by all users and regardless of band conditions. Copy rates are easily 80%+ no matter what. For intentionally sharing accurate information with specific parties over HF, the Olivia modes nail it. It’s not perfect, but for my purposes it fills the role it’s supposed to: get info to people every time, without having to pray to sun cycle gods or other such nonsense.
I'm sure I missed something, but I think the above gives pretty good context into the purpose of this build. So that's all I have for now.