Why Rig Control? Amateur Radio Presentation - Full Presentation Outline

Inspirational: first steps
- No rig control yet
Aspirational: further steps
- Connected, but not getting value
Primarily for HF
- Techs not left out
  - Principles/techniques same
  - Brief coverage of VHF/UHF-specific items

Digital modes
- Hat tip to Dennis with digital modes!
- Easy button
  - Extensive automation, even more than CW
  - Pan adapter with automatic decode
- Person-to-person: full keyboard to keyboard
  - RTTY is great intro
  - PSK31
  - JS8CALL
- Messaging
  - HF Packet is still a thing!
  - Winlink
- Automated signal reporting
  - PSA about gatekeeping/sad ham
  - FT8
    - Unparalleled QSO generator
    - Or just PSKReporter!
  - WSPR
    - Great for system analysis
    - Experimentation: A/B, quantitative measurements, etc.
Voice modes: FreeDV
- Longer range and much better audio quality!

Even more options!
SSB-capable, all of the above!
FM
- APRS
- Packet
  - Extensive in-state network!
  - Run your own BBS!
- Winlink
- Analog to digital gateway
  - Fusion/DMR/DStar
- Hotspots
  - MMDVM
  - AllStarLink
    - Your own private repeater network!

Computer control does not have to change the way you work with your radio: it just makes the way you work better
- But it can change the way you work if you want it to
Spin the dial: Makes manipulating your radio easier: bigger buttons, better control
Control your radio from anywhere: better chair, better view, bigger (and quieter!) antennas
Assist you with logging, DX hunting, spotting
Improve traditional modes: CW from keyboard, RTTY, etc.
Add new modes:
- Digital voice
- Digital chat
- Digital messaging
- And yes, automated signal reporting
  - Or, an exciting way to reach new DX around the globe with cool new features!
VHF/UHF has its own new areas
- Packet/APRS
- Analog/Digital gateway
- Completely new digital RF/Internet gateway capabilities

Terms are confusing!
Layers of complexiety

“Rig control” is common term, but confusingi
- Often includes two unrelated parts: radio management and audio management
  - Radio management: Spin the dial, see the display, log the data
  - Audio management: computer can send/receive RF/Audio
- To avoid confusion: I'll stick with the above terms
- Don't need both! Start with radio control, but want to plan for both

For each type of management, multiple layers
- Physical: How do the items actually connect?
  - Radio port, computer port and cable between
- Tools: Software you actually use
  - Logging software, radio control, audio encode/decode (new mode)
- Middleware: manage multiple tools at the same time

Physical connection (hardware)
- What does your radio provide?
  - Remember: radio control and audio control are separate!
- Vast majority: serial port
User tools
- What does your logging software want?
  - Probably serial port and radio
Technically all we need
- Log talks to serial, serial connects to radio
- Does work, and maybe OK for initial testing
- Dead end, because…
Sharing
- Vast majority radios I'm familiar with (midrange Big 3): Serial port
  - Exclusive access: only one program can talk to the radio!
  - True if proprietary, RS-232/DB9 or USB; to computer, same thing
- Logging *and* spin dials? Other modes? Won't work!
  - Most logging includes rudimentary radio management
  - Probably want better – don't limit yourself
Middleware: Third layer to share radio management
- Driven largely by what supports your radio and tools, use cases
  - Just logging to modern, popular radio? Doesn't matter much
  - Full radio use from remote location, multiple logs (contesting), SO2R: matters a lot!
- Important decision, but likely needs to be made last/iterative
  - Ignore direct-to-radio
  - Spoiler: If in doubt, use Hamlib

Physical connection (hardware)
- Once again, start with radio
  - How do you get line-level (not mic) level audio from radio to PC?
    - Mic can work, but absolute last resort
- Vast majority radios I'm familiar with (midrange Big 3): back-panel ports to sound card
  - True if proprietary, audio jacks or USB; to computer, same thing
  - Gets audio into the computer (mic) and out of computer (speakers)
Next, user tools
- Almost no worry: they are highly likely to be just fine with a sound card
- Start with what interests you
  - Expand capabilities of existing mode?
  - Add new ways of communicating?
  - Focus on DX? Awards? Experimentation?
Need third layer for audio sharing?
- Yes, but not for actual audio!
  - Sharing built into the OS for the last couple of decades… Happens for free!
- Audio needs one very large item: PTT!
  - Audio not enough: need to push that button!
- OS doesn't help with this, so we do need a third layer here
- Advantage: practically, only one thing sends data at a time
  - Sharing audio much smaller issue than radio control, but must be aware!
  - Spoiler: While not best, Radio Management middleware can fill in here, too

“Rig control” includes two things: radio management and audio management
Each of radio management and audio management includes three layers:
- Physical connection (hardware): literal cables/converters needed to connect radio to PC
- Tools (software): Actual radio tasks (logging, radio control, data encode/decode, etc.)
- A layer in between to share radio with multiple tools and manage PTT
Start with your radio
- What does it provide for radio control?
- How do you get line-level audio in and out? For PTT?
Next look at your current tools
- What do they support for radio management?
Finally, what are you excited about right now?
- Maybe more than just most excited: Plan for near- or medium-term now!
Now begin to decide how to put them together

At this point, for non-computer users: aspirational
- Hopefully given you lots of reasons to want to
- Given you areas to investigate
  - What you have
  - What you want
For time, only review takeaways for next section
- Could do a whole presentation!
- And Dale is planning one! :)
Focus on general concepts to help look for next step
- How does the hardware work?
- What hardware is available?
- How to take what you have and get to what you want?
Want to cover aspirational for those already connected!

Focused on Big 3: Icom / Yaesu / Kenwood
Less about specific models (too many!); focus on features to keep in mind
Big takeaway: likely nothing here that money can't solve
- With money, you don't need the details
- For DIY cheapskates (like myself!) the details matter
  - For DIY, you need to learn the details for yourself!
Spoiler: Newest USB radios are all set!

Includes both hardware spec and logical command language/protocol
Amateurs way ahead of the curve on radio control
- Early 1980's, maybe earlier?
  - As times change, hardware adapted, but language largely continues
    - Sometimes extended, sometimes duplicated
    - Some concepts important to calculator-sized computers are now… in the way
Special note for most modern radios with USB: IC-7300 FT-Something??
- Good news: much simpler!
- Practically: plug in USB and go (again: more money, less details!)
Identify: How does radio provide?
- Icom CI-V, maybe DB9, otherwise a bunch of different connectors…
  - watch for really old (pre 1990's?) non-RS232 interfaces
    - Wrong voltages, usually
    - Converter outlined in manual likely rare / really expensive
    - Becomes challenging DIY: likely not great first attempt

Icom CI-V

Probably the farthest from modern requirements
- Designed for literal network of radios, with calculator-sized PC just a small part of comms
  - SO2R before it was cool!
  - Modern interfaces usually dispense with multipoint (even for SO2R)
- Older (pre-millenium) radios very difficult unless maybe top-of-the-line
Hardware: 3.5mm headphone jack
- Obviously, needs interface
- At least it’s consistent

Kenwood

Status: Godfather of CAT
- TS2000 lingua franca, esp. virtual serial
Simple, reasonably human/script friendly
Even early and low-end radios highly functional
Hardware: Varies by radio
- DB9: No interface needed (except USB/Serial)
- 6-pin DIN: TTL-level RS-232
  - Modern TTL-capable UART works fine
- Older radios (TS-140, TS-440, etc.) need IF-10 internal interface!

Yaesu CAT

Not sure of history, but seems blatant ripoff of Kenwood! :)
Same advantages/disadvantages
Very similar hardware situation (but different connectors of course)

Much more variation here: harder to be specific
- No real manufacturer 'style': more variation between models than makers
Best to understand concepts and requirements
- As usual, what does the radio require?

PTT

Biggest obstacle!
- What can the computer generate as a signal?
- What will the radio accept as a signal?
- And do those two line up?
Obvious PTT: signal via serial status pin
- Computer: Steal wire from radio management port (RTS/DTR)
  - Using single port for radio management and PTT: sharing issues
  - Using multiple ports: gets cumbersome
  - Either way: software configuration hassles
    - Each software, each port, each time
- Radio: Wire serial port signal to radio PTT pin
  - Maybe PTT in same DIN port as audio in/out
  - Or maybe steal from separate linear port, or automatic tuner port, or…
  - Either way, can be cabling hassle
- Works, but annoyingly cumbersome
Simple/Cheap PTT: Command via radio management
- No sharing issues (beyond radio management sharing)
- Needs radio support (practically any recent radios)
- Needs software support
  - Each software must also already be doing radio management (fairly common)
- Must configure each tool (but easier than serial PTT)
- Can be sluggish (hang time before and after)
Easiest/Most Effective PTT: VOX
- Needs either radio support or separate external circuit
- Either way, just works
  - No sharing issues: have audio, you have PTT
  - No config issues: transparent to tools
- Only downside: might cost money
  - Though cool DIY VOX PTT ciruit from NF4RC guys!

Audio Connection

Usually straightforward
Radio side: usually some sort of back-panel line-level in and out
- Almost always hidden in some sort of DIN port
Avoid: mic/external speaker into analog soundcard
- Either within actual mic port or pair of 3.5mm jacks
- Level issues, tone issues, etc.
- Yes, you really need to use those DIN ports…
- Very basic radio (VHF/UHF): might be only option
Better: separate audio inputs via back-panel
- Line-level (not mic/speaker level)
- Fixed-volume in and out (not changed by knobs)
- Ideally dedicated audio path (no DSP, bandpass, etc.)
- Watch out! Sometimes just rerouted mic/speaker…
  - with exactly same issues…
Best: Dedicated data-specific port
- Everything you need – and radio expects
- Recent radios: 6-pin mini-DIN (same as PS/2 keyboard/mouse: good for DIY cables!)
- And of course, USB…
- Pay attention to unexpected differences on certain radios!
  - Radio may need to be in specific mode (DATA-L/DATA-U vs LSB/USB)
  - Back-panel audio must use back-panel PTT
  - Back-panel audio can't use PTT at all – must use radio VOX!
- Lots of ways to make a subtle mistake: read your manual! Multiple times!
  - Google searches your friend: learn from mistakes of others!
PC side much easier: practically always sound card
Avoid: using main/internal sound card!
- Don't care how many extra mic/line-in ports you have
- Biggest issue: system sounds over air
  - Don't be that guy…
Basic: External generic USB sound card with serial/command PTT (or DIY VOX PTT)
- USB radios already have this!
- Otherwise: $5 USB sound card with in and out from AdaFruit! ($8 next-day from Amazon)
- Protip: Rename those sound card inputs! (“USB Audio” doesn't help…)
  - Another protip: Do this before you start, so you know what you won't be using!
Good: External radio USB sound card
- Look for VOX PTT capability – highly recommended
  - Otherwise, limited to serial/command PTT
- Likely easier to connect to radio
- Possibly with front-mounted audio controls
Great: Combined external radio USB sound card and radio management interface
- Likely easiest connection to both PC and radio
- Can make serial-based PTT more streamlined and manageable
  - Not any easier to share, though
- Look for same features as Even Better above: VOX, front-mounted control
Differentiators: much more variation
- Fixed for a particular radio or reconfigurable for others
- USB Sound card built-in
- Physical front-panel controls
- Multiple audio paths/routing (headphones, external speakers, computer audio, etc.)
- Integrated radio management
- PTT options
  - VOX in interface or in radio
  - PTT shared with radio management serial
  - PTT separate serial

DIY

Lots of examples online
- Because it's pretty easy
  - Often just wiring up custom DIN patch cords will work
- Because each radio is different!
- Because some people are more picky than others
  - Pin-to-wire-to-socket, or
  - Transistor level shifting, coupling capacitors, diode protection, etc…..
Serial is usually just wire into RS-232
- Watch for non-standard (non-RS232) serial port signalling
- C-IV: needs additional circuitry
Audio connection is usually just wire into USB sound card
PTT biggest issue
- Steal signal pin from radio management serial, or
- Use radio management command, or
- Use radio VOX, or
- DIY VOX PTT in external USB sound card
Typical cost: $ 15 USB/Serial; $10 USB soundcard; $10-$20 DIN patch cables
- Time/effort/supplies for wiring, circuitry, case, etc.

Least expensive purchase

Almost always eparate radio / audio management
- Price out better solution: might be cheaper combined
Lots of Chinese / Amazon cables
- Basically pre-made USB-to-serial directly to DIN patch cord
Pay attention to PTT!
- May not include it at all: left with command only!
$25 radio control (USB to radio); $10 USB soundcard; $25 DIN to audio cable (3.5mm)
- No more expensive than DIY, and probably no different, either

Simplest purchase

XGGComms.com: Radio-specific solutions for Icom/Kenwood/Yaesu/Xiegu
Integrated radio / audio management available
VOX PTT in interface
Single USB to PC
Proper connectors for your radio – but only your radio
No user-adjustment (levels, VOX sensitivity/delay, routing, etc.)
Digimode-4: $75 for everything you need
- Literally only a few dollars more than DIY/least-expensive

Bells and Whistles

SignaLink USB

VOX PTT in interface
Easy-to-build cables for virtually any radio
Easy-to-buy (but pricey!) cables for lots of radios
User-exposed level and VOX controls
Everything you need in an audio interface – but only audio
- Add whatever basic radio management cable you need
$150 / $200 with pre-made cables
- Less than $100 on eBay

RigBlaster Advantage

Extended audio configuration, including switchable audio paths
Configurable PTT options
FSK/CW serial keying
Integrated radio and audio management via USB
- Supports C-IV
Everything you need in a radio and audio interface
$200 / $250 with pre-made cables
- $400 for DXpro (SO2R!)
For more technical cheapskates: check out discontinued RigBlaster / RigBlaster Pro
- Less than $50 on eBay: no USB serial/sound card, but most of the other capabilities
- Maybe not a first interface unless you like challenges

If you have a USB radio, you already have what you need
- Except maybe a USB cable… Plug it in and go!
If you don't want to care about the details, a relatively small amount of money will solve these issues
- XGGComms.com for most Icom/Kenwood/Yaesu (and others)
- Signalink and simple computer cable for your radio
- RigBlaster Advantage if you have to have the best
If you spend the money, that's basically all you have to know!
- For the rest of us… all this other detail!
Radio management includes hardware connection and language used to change the radio settings
- Identify what your radio provides
- No alternative: that's what you'll have to use
Audio management includes audio connection and PTT
- Much variation between radios, often several options within a single radio
PTT options
- Computer serial port
  - Difficult to configure and share, but straightforward
- Radio management command
  - Slightly cumbersome but cheap and reasonably effective
- VOX
  - Needs radio support or external circuit
  - Simple, reliable, effective
Audio connection options
- PC side easy: some sort of external USB sound card
  - Never use main/internal sound card
- Radio side trickier
  - Find some sort of fixed-volume line-level signal (ideally dedicated)
  - Pay attention to unexpected limitations or configurations
    - Check that manual!
- Generic USB sound card can work
  - Just have to figure out PTT
- Radio-specific USB sound card can work better
  - Should help with that PTT – but confirm!
- Radio-specific with VOX works best
- Combined radio-management/audio-management might be simpler or have more features
Differentiators: radio specific or generic; front-panel controls; audio routing; PTT options
DIY options available
- Simple radio- and audio-management cables
- Complete all-in-one solutions including VOX PTT!

Talked about all that we can do! But what does it take?
- Tools do the fun (user-facing) part
- Need to talk to radio in background
How do we give the tools what they need?

“Rig Control” overloaded: Each will have its own expectations
- Read-only radio management: Logging (HRD, N1MM, Log4OM2), Display (HamClock)
- Read/write radio management: Rig Control (HRD, flRig, Win4Icom/Yaesu, RigPi)
- Listen audio management: CW Decoding (flRig), Pan Adapter/Waterfall (flRig, WSJT-X)
- Listen/Transmit audio management: New digital modes (HRD, flDigi, WSJT-X, JS8Call)
  - These don't absolutely require radio management but often greatly benefit

Start with what you're already using
- Many start with FT8, but better to start where comfortable
- What does it support? Start there!
Next consider what you want to add
- FT8? Maybe. But maybe smaller, too
- Rig control: flRig
  - Spoiler: might make next steps easier, too!
- FT8: WSJT-X (Plus GridTracker, and maybe JTAlert)
- Everything else: flDigi

How do you meed all these needs?

Huge variety of radios, huge variety of connection types, huge variety of tools
- Huge variety of needs
- Huge variety of choices
- Where to begin?
Biggest issue: Sharing
- One radio, one connection – one tool.
  - Something has to own the serial port/radio!
Two ways to fix
- “One tool to rule them all”
  - One tool, one owner, one place for everything
- Add a radio “Office Manager”
  - Person everyone delegates tasks to that “just get done”

Some things just decide they'll just do everything
- No need to share if you never need anything else…
- Examples: HRD, N1MM
Advantages
- If it does it, you're done
  - HRD: What can't it do?
    - FT8: but they have a workaround…
  - N1MM: it's narrow but deep…
Disadvantages
- When it doesn't do it, it's a real problem
  - “It's great, but I just wish it did…”
  - Ways around, but painful
- Can be poorly supported, or take a long time to support
  - Eggs and basket
Won't discuss too much here
- Too easy: connect and done!
- If already using, you win!

“Middleware”: sits in the middle of radio and tools
Tools only have to talk to one thing (middleware), gets all the radios for free!
Advantages
- Much broader choices
  - Not locked into “my way or the highway”
  - Can mix and match tools without (much) issue
Disadvantages
- Not everything will always play nice together
- Sometimes tools you wan't don't all support same manager!
More to discuss here
- More choices!
- More steps

Programmers face same limitations
- Programmers users too: they want everything to work
- Programmers lazy too: Let someone else do the work
Middleware gives them both:
- Share single radio among multiple tools
- Tools support nearly all radios all at once
Three common options: Virtual Serial, OmniRig and Hamlib

Virtual Serial

Not really a specific piece of software, but more a technique
If problem is single serial port for single tool, why not make more?
- Literally what it does: split single port like a power strip
- Old technique leveraged for Amateur Radio
Advantages
- Easy to understand: start with one port, duplicate the port
Disadvantages
- Easy to overwhelm: lots of ports, tools step on each other
Best used when no other alternative
- But useful to fill in gaps
- Especially for “do it all” solutions for that one extra item

OmniRig

Intentional separation of radio (and serial port) and tools
- Literally does
Advantages
- Very simple program: easy to run, easy to configure
- Put in your radio details once, and all tools just work
Disadvantages
- Two versions, and the older (1.x) is the more popular
  - License change for 2.x, which most programmers are avoiding!
- Limited tool support, especially for rig control
  - For me, that was the dealkiller
Best used if your needs are modest and simplicity is paramount

Hamlib

Programmer-centric middleware
- Easy for programmers; not as easy for users!
Advantages
- Extensive radio support
- Extensive networking support
- Extensive tool support
Disadvantages
- Absolutely no GUI
- Complex command-line parameters
Best option – if you can make it work!
- User friendly – just picky about its friends

flRig

Technically not middleware: Rig control
- But rig control and middleware!
Hamlib will talk to flRig!
- Only use the painful tools when and where you need it
Advantages
- GUI (of sorts)
- Rig control and middleware
  - Great first step for a new user!
- Tight flDigi integration (same author)
  - Even better second step for a new user!
- Very good coverage of tools and radios
Disadvantages
- Makes Hamlib easier, but not easy
  - Protip: Log4OM2 makes the painful easy…

Best first step: include what you already have!
- Still want to make choices that let you add in the future
  - If two can't cooperate, decide sooner rather than later

Serial tips

Not technical presentation, but suggestions to consider:
Protip: Document your serial ports in advance!
- Right-click on “Start”/Device Manager/Ports (Parallel and Serial)
- If using USB, these are not your new USB (before you plug in!)
  - AMM, motherboard without header, etc.
- If using actual, physical port, then one of these is your port
  - Still have to find it…
Pro's Protip: Serial ports much harder to rename, but worth it for the technically inclined!
- Must modify Registry entry (but first you have to find the right setting…)

Do-it-all

If you want it easy (and you're not that picky): HRD
- National Chain Restaurant of solutions
  - You'll probably be mostly content most of the time
- Almost nothing it can't do – to some degree
- Zillions of users can't be wrong
- Costs a few dollars a year for support: worth it for the simplicity
- Imagine if you use HRD with IC-7300: You're already done! :)
Contester: N1MM
- It's laser-focused on contesting
- Might not be a good solution when not contesting
  - Maybe switch between N1MM and something else?
Dishonorable mention: N3FJP
- Dale will no doubt kill me afterward… :)
- Just. So. Disorganized.
  - Separate programs?!?
  - And breaks standards (esp. ADIF!)

Separate Components with Middleware

Lots going on! Need to start from somewhere

Radio Management ("Rig Control")

Radio management probably offers fewest choices
- Everything might change the dials a bit, but true full-function control is rare
If you want this, pick it first!
Recommended: flRig
- Strong radio support
- Strong tool support (esp. when paired with Hamlib)
- Straightforward setup (with a little GUI)
- Strong capability (with an awkward GUI)
  - Missing items can be added as buttons/macros
    - I use this quite a bit!
- Sharing-ready middleware included
Not recommended: dead-end tools
- Manufacturer tools: usually single-trick tools
  - Won't share, don't do anything else
  - Could be paired with virtual serial ports but why bother?
Alternative: OmniRig 1.x
- Provides simplest radio sharing option
- Could not find supported Rig Control!
  - If you don't want that, you might be just fine

Logging

Next up: connect your logging to your middleware
First choice: What you're using! :)
- If it supports flRig or Hamlib, you're fine!
- If it doesn't, I hope you picked the right choice above!
Recommended: Log4OM2
- First, great documentation and active forum
- For logging side it does a lot
  - Logging, data lookup, clustering, awards, propagation analysis, etc.
  - Push/pull logs to QRZ/LOTW automatically
- For rig control, just about all the options
  - For flRig: https://forum.log4om.com/viewtopic.php?t=6555
    - Gives you full Hamlib rigctld setup as well!
  - Supports OmniRig as well
- Quick downsides
  - So. Many. Settings.
    - Easy to forget where!
    - Documentation really helps!
  - Can be really slow
    - Need recent (< 4 years) computer
  - Windows only
Alternative: N1MM
- Cover separately (virtual serial)

Radio Audio

Before we jump into a new mode, let's hear some audio first
Need to adjust sound card settings
- Protip: Even with Windows 11, you want Control Panel/Hardware/Sound
- Protip: Adjust Playback/Properties (or Recording/Properties):
  - General: Rename the port! (Speakers → Out to FT-450D via SignaLink)
  - Levels: Move levels to 0dB
    - Protip: Right-click on graph to select dB
  - Protip: Turn off all other fancy things: 3D, Dolby, Spatial, etc.
Recommended: Spectran
- Setup/Select sound card/Pick your radio's speaker/mic
  - You did rename the sound card ports to make it easy to find, right?
  - Click “Start” on bottom row: you should hear your radio!
Worth the quick test: this will help you resolve so many isuses along the way!
- Also allows you to see spectrum/waterfall with dB mesurements
- Looking for ~-40dB on average – nowhere near 0dB!

New Digital Mode

The exciting part – pulling it all together!
- Old favorites quick and easy (RTTY, PSK31)
- New favorites waiting to be tried (FT8, FreeDV)
Recommended (brain rot): FT8
- WSJT-X
- Zillions of users can't be wrong
- Someone to communicate with 24/7 (no matter the band conditions!)
- Supports flRig directly: Select it once and done!
  - Same true for OmniRig
- Has level meter and full waterfall
- Supports variety of logging options
  - Push FT8 QSO's directly to your log
    - This really is its own presentation…
    - Protip: Start with Multicast from the beginning
- Protip: Reset your clock right now!
  - Cant be close: must be exact (sub 1 sec)
Recommended (old geezer): RTTY (or lots of others!)
- flDigi
- Zillions of modes is great, too…
- Somebody somewhere is using something flDigi can do…
  - If you can find them!
  - But not so hard if you schedule with someone…
- Has waterfall…
  - Poor GUI is a constant theme with fl*…
- Logging is simple: it logs to a file
  - You get to move it elsewhere: ADIF to the rescue

Virtual Serial Middleware

Not recommended as main, but great for small additions
- All-in-ones that aren't
  - N1MM
Use virtual serial to “wiretap” between radio and e.g. AIO
- Like wiretap, can cause interference
- Great for switching between tools without conflict or reconfigure
- Not great for heavy simultaneous use
Another option: Hamlib can create virtual radios!
- Presents serial port that pretends connected to Kenwood TS-2000
- Tool think it's talking exclusively to (virtual) radio!
- Hamlib manages radio and data for all tools
  - Much less conflict!
- Not easy setup, but only has to be done once
- Great for AIO you don't want to commit to
  - N1MM for contests, something else for causal
Again, not recommended as starting point
- If you're using multiple tools, really try to use Hamlib from beginning!
  - You can add virtual radios when you need to
- If you're using AIO, really try to use all of AIO
  - Avoid complexity of virtual serial until you truly need it
- If you're using something other than Hamlib or AIO, why?
  - If you have a really good reason, then virtual serial is there to help you

Understand Needs of Tool
- Does it need to change the radio or just read? (Rig Control vs. Logging)
- Does it need audio to and from the radio (New modes need both, plus Rig Control)
Understand Needs of You!
- What can your current tools work with?
- What are you excited to add?
Understanding sharing issues
- Radios don't share: you need a manager (or one tool to do it all)
Suggestions for tools
- I'm not picky and I just want it to work!
  - N1MM for your die-hard contesters
  - HRD for everything else
- I'm picky and I'm willing to put in the effort!
  - Rig control: flRig
    - Also middleware!
  - Logging: Log4OM2
    - Also adds Hamlib for extra middleware!
  - First new mode: FT8 or flDigi
    - Go for both!
- Other radio sharing options available, but need a real good reason to choose
  - OmniRig: Simple, easy, but less tool support
    - Hamlib has new mindshare: FreeDV supports only it (or direct serial…)
  - Virtual Serial: Can work with almost anything, but complex and has its own issues

Why Rig Control? Amateur Radio Presentation - Full Presentation Outline

Overview

Purpose

Contents

Focus

Why not?

Why you need rig control

Spin the Dial

In and near the shack

Remote control

Radio personal assistant

On the air

CW

SSB

New modes

VHF/UHF

Takeaways

How does it work?

Terms to understand

Layers to understand

Radio management

Audio management

Takeaways

Aspirational Presentation

Hardware Options

Radio Management

Icom CI-V

Kenwood

Yaesu CAT

Audio Management

PTT

Audio Connection

Examples

DIY

Least expensive purchase

Simplest purchase

Bells and Whistles

SignaLink USB

RigBlaster Advantage

Takeaways

Tools

Understand Needs of Tool

Understand Needs of You!

How do you meed all these needs?

Do-it-all Solutions

Manager Solutions

Middleware Options

Virtual Serial

OmniRig

Hamlib

flRig

Example Solutions

Serial tips

Do-it-all

Separate Components with Middleware

Radio Management ("Rig Control")

Logging

Radio Audio

New Digital Mode

Virtual Serial Middleware

Takeaways