World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Control fldigi (amateur-radio digital modes) over XML-RPC: modem, frequency, rig, log, transmit.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Fldigi MCP. Follow https://mcp.popnx.com/i/sbrunner-atx-fldigi-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
1 setting(s) to fill in (FLDIGI_CALLSIGN) · Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Fldigi MCP for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "fldigi": { "command": "uvx", "args": [ "fldigi-mcp" ], "env": { "FLDIGI_CALLSIGN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For FLDIGI_CALLSIGN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Fldigi MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
FLDIGI_CALLSIGN Operator callsign. Required to enable transmit; leave blank to stay receive-only.Descriptions are as written by the maker.
SettingsDeveloperEdit Config
{
"mcpServers": {
"fldigi": {
"command": "uvx",
"args": [
"fldigi-mcp"
],
"env": {
"FLDIGI_CALLSIGN": "your-value"
}
}
}
}Use Fldigi MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using Fldigi MCP or shows a Fldigi MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
FLDIGI_HOST fldigi XML-RPC host. · default 127.0.0.1FLDIGI_PORT fldigi XML-RPC port. · default 7362FLDIGI_BAND_GUIDANCE Enable experimental advisory band guidance (on/off). · default offFLDIGI_REGION IARU region for band guidance: 1, 2, or 3. · default 2Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Fldigi MCP yet
Fldigi MCP runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Fldigi MCP
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
1 setting(s) to fill in (FLDIGI_CALLSIGN) · Install Python (uv) on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Fldigi MCP for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user fldigi --env FLDIGI_CALLSIGN=your-value -- uvx fldigi-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For FLDIGI_CALLSIGN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Fldigi MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
FLDIGI_CALLSIGN Operator callsign. Required to enable transmit; leave blank to stay receive-only.Descriptions are as written by the maker.
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user fldigi --env FLDIGI_CALLSIGN=your-value -- uvx fldigi-mcpYou should see Fldigi MCP listed as connected
Use Fldigi MCP and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Fldigi MCP or shows a Fldigi MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
FLDIGI_HOST fldigi XML-RPC host. · default 127.0.0.1FLDIGI_PORT fldigi XML-RPC port. · default 7362FLDIGI_BAND_GUIDANCE Enable experimental advisory band guidance (on/off). · default offFLDIGI_REGION IARU region for band guidance: 1, 2, or 3. · default 2Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
1 setting(s) to fill in (FLDIGI_CALLSIGN) · Install Python (uv) on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Fldigi MCP for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "fldigi": { "command": "uvx", "args": [ "fldigi-mcp" ], "env": { "FLDIGI_CALLSIGN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For FLDIGI_CALLSIGN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Fldigi MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
FLDIGI_CALLSIGN Operator callsign. Required to enable transmit; leave blank to stay receive-only.Descriptions are as written by the maker.
In the Fldigi MCP settings, FLDIGI_CALLSIGN is empty; add your key and save
Use Fldigi MCP and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Fldigi MCP or shows a Fldigi MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
FLDIGI_HOST fldigi XML-RPC host. · default 127.0.0.1FLDIGI_PORT fldigi XML-RPC port. · default 7362FLDIGI_BAND_GUIDANCE Enable experimental advisory band guidance (on/off). · default offFLDIGI_REGION IARU region for band guidance: 1, 2, or 3. · default 2Descriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
1 setting(s) to fill in (FLDIGI_CALLSIGN) · Install Python (uv) on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Fldigi MCP for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "fldigi": { "type": "stdio", "command": "uvx", "args": [ "fldigi-mcp" ], "env": { "FLDIGI_CALLSIGN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For FLDIGI_CALLSIGN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Fldigi MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
FLDIGI_CALLSIGN Operator callsign. Required to enable transmit; leave blank to stay receive-only.Descriptions are as written by the maker.
In the Fldigi MCP settings, FLDIGI_CALLSIGN is empty; add your key and save
Use Fldigi MCP and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Fldigi MCP or shows a Fldigi MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
FLDIGI_HOST fldigi XML-RPC host. · default 127.0.0.1FLDIGI_PORT fldigi XML-RPC port. · default 7362FLDIGI_BAND_GUIDANCE Enable experimental advisory band guidance (on/off). · default offFLDIGI_REGION IARU region for band guidance: 1, 2, or 3. · default 2Descriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user fldigi --env FLDIGI_CALLSIGN=your-value -- uvx fldigi-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"fldigi": {
"command": "uvx",
"args": [
"fldigi-mcp"
],
"env": {
"FLDIGI_CALLSIGN": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"fldigi": {
"command": "uvx",
"args": [
"fldigi-mcp"
],
"env": {
"FLDIGI_CALLSIGN": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"fldigi": {
"type": "stdio",
"command": "uvx",
"args": [
"fldigi-mcp"
],
"env": {
"FLDIGI_CALLSIGN": "your-value"
}
}
}
}FLDIGI_CALLSIGN required envFLDIGI_HOST envFLDIGI_PORT envFLDIGI_BAND_GUIDANCE envFLDIGI_REGION envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account sbrunner-atx, which owns the repo
Code last changed 6 days ago
Uses GPL-3.0
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for fldigi-mcp@0.4.1
Checks only this package version, not every dependency · checked Nov 16, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/sbrunner-atx-fldigi-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 6 days ago, and the latest version (0.4.1) reached the registry 6 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Fldigi MCP | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | GPL-3.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Project page: ae5vg.com/products/fldigi-mcp
An MCP server for controlling fldigi, the popular amateur-radio digital-modem application, from MCP-aware clients such as Claude Desktop.
fldigi ships a built-in XML-RPC control interface. fldigi-mcp connects to it and exposes the whole API as a small set of logically-grouped MCP tools, so an assistant can read the radio's state and drive the modem, rig, log, and transmitter through plain language.
Status: beta. Signal hunting (find, name and tune to a station from the
receiver audio, 0.2.0) and full API coverage (every one of fldigi's 174 XML-RPC methods
is reachable through a named operation, enforced by a test), callsign-gated
transmit, and an optional experimental Band Guidance feature. Supports the
current fldigi release, 4.2.13, verified live on 2026-09-09.
Building this server meant mapping fldigi's entire XML-RPC interface and verifying every method against a live build — so we've written it all up and are sharing it freely, whether or not you ever use this MCP server:
Verified live against fldigi 4.2.13 via fldigi.list on 2026-09-09 (the method list is identical to 4.2.11, first verified 2026-06-23). It's more complete and current than the public wiki (it documents methods the wiki omits, e.g. TxID, and flags deprecated ones). Independent project — not affiliated with the fldigi / W1HKJ project. Corrections welcome via issues / PRs.
tests/test_coverage.py fails the build if a method of the shipped catalog is not wired or an argument type disagrees with fldigi's signature. The fldigi_call escape hatch remains for methods a newer build may add.xmlrpc.client. The only third-party runtime deps are the MCP SDK and PyYAML (for the optional band-plan data).fldigi's XML-RPC interface is its official, OS-independent control API. This project talks to it directly rather than through an unmaintained wrapper, keeping the moving parts to Python's standard library and fldigi's own API.
To install the desktop connector (.mcpb) all you need is:
127.0.0.1:7362).Claude Desktop's uv runtime supplies Python and the dependencies, so end users do not install Python or uv themselves. (That runtime is currently marked experimental, so a recent Claude Desktop is recommended.)
For development from source you additionally need Python 3.10+ and [uv](https://docs.astral.sh/uv/) (and Node.js, only for the MCP Inspector).
Download fldigi-mcp.mcpb from the latest release, then in Claude Desktop open Settings → Desktop app, click Manage next to Extensions, and drag the file onto that page (or use Advanced settings → Install extension). It then shows as a connector under Settings → Customize → Connectors. A short settings form asks for your callsign (everything else has a default). No terminal, no Python, no uv to install.
👉 New to this? Follow the simple [step-by-step install guide](https://github.com/sbrunner-atx/fldigi-mcp/blob/main/docs/INSTALL.md). Also see the install & safety model.
The desktop connector installs only the server. Its operating skills are separate downloads: fldigi-operating.skill and signal-hunting.skill, from the latest release or ae5vg.com/downloads.html. In Claude, open Customize → Skills, click Add, then Upload skill, and choose all the files at once.
For Claude Code or another MCP client, copy the folders under skills/ into the client's skills folder, for Claude Code ~/.claude/skills/.
To run the server itself in Claude Code, Codex, Cursor or VS Code, see Other AI assistants for the command or configuration block to copy.
git clone https://github.com/sbrunner-atx/fldigi-mcp.git
cd fldigi-mcp uv sync
Then add it to Claude Desktop's config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": { "fldigi": { "command": "uv", "args": ["--directory", "/absolute/path/to/fldigi-mcp", "run", "fldigi-mcp"], "env": { "FLDIGI_CALLSIGN": "AE5VG" } } } }
Restart Claude Desktop and ask *"What's fldigi's status?"*. Omit the env block to run receive-only.
uv run mcp dev src/fldigi_mcp/server.py
patches/) — proposed, not yet mergedStatus: offered to fldigi's maintainer on 11 September 2026 (w1hkj/fldigi issue 55). Until it is merged, the method names and fields below are a proposal and may change.
fldigi's Signal Browser, the left-hand panel that decodes up to 30 PSK, RTTY or CW stations at once, is not on its XML-RPC API. patches/fldigi-4.2.13-browser-xmlrpc.patch touches four files (psk_browser.h/.cxx, viewpsk.cxx, xmlrpc.cxx) and adds two methods, browser.get_channels (array of {channel, freq, active, text}, text untrimmed, line breaks kept, accumulated since the last clear) and browser.clear. The browser tool and signal_hunt method="browser" use them and say so when fldigi is unpatched. A second patch, patches/fldigi-4.2.13-rsid-hits.patch (applies on top of the first), adds rsid.get_hits and rsid.clear: the RSID bursts the detector accepted, as {utc, mode, hz}. With RSID set to notify-only, fldigi then names the modes on the band without ever switching the modem; the rsid tool reads the list. Both patches are proposed, not merged. Tested on 4.2.13 (macOS, four synthetic PSK31 stations from 0 to -26 dB: all four copied in full). The patch applies to the fldigi git HEAD on SourceForge and is prepared for upstream submission; until it lands, build fldigi from source with it:
tar xf fldigi-4.2.13.tar.gz && cd fldigi-4.2.13
patch -p1 < /path/to/fldigi-mcp/patches/fldigi-4.2.13-browser-xmlrpc.patch ./configure --prefix=$HOME/.local/fldigi && make -j8 && make install
Each tool is one permission and takes an operation argument, so e.g. "change the mode" is a single permission regardless of which underlying method runs.
| Tool | Controls (fldigi area) |
|---|---|
status | quick snapshot: version, mode, frequency, T/R, callsign, band |
diagnostics | host/network info for connectivity troubleshooting (no fldigi connection) |
application | program info + launch/stop the fldigi process (fldigi.*) |
modem | Op Mode / modem select, carrier, bandwidth, AFC range, Olivia |
frequency | dial frequency and waterfall sideband |
controls | AFC, SQL, Rev, Lock, RxID, TxID, status fields |
transmit | T/R, Tune, abort, disable/enable Tx, macros, send — callsign-gated |
rig | CAT control: mode, frequency, bandwidth, notch, QSY, meters |
log | Logbook / contest fields; ADIF last/all records |
text | RX/TX text and data streams |
spot | spotting / PSK Reporter |
wefax | WEFAX (weather fax) mode |
navtex | NAVTEX / SitorB mode |
flmsg | flmsg (message forms) interworking |
io | ARQ / KISS I/O port selection |
legacy | deprecated methods fldigi still serves, each with its current equivalent named |
band_guidance | advisory band/watering-hole help (experimental) |
signal_hunt | find and name the signals in the receiver audio; rank CQing stations (experimental, [hunt] extra) |
tune_to | set modem and carrier to a signal_hunt candidate, receive only |
browser | fldigi's Signal Browser: every station the decoder bank holds, with its text (needs the fldigi patch in patches/) |
rsid | RSID bursts heard in the passband, mode and frequency, without switching the modem (needs the rsid-hits patch in patches/) |
fldigi_call | escape hatch — call any method by name, incl. future ones |
Use application → list_methods to enumerate every method the running build supports. On 4.2.13 all of them are surfaced in a group; fldigi_call is for methods a newer fldigi may add before this connector catches up.
| Variable | Default | Purpose |
|---|---|---|
FLDIGI_HOST | 127.0.0.1 | fldigi XML-RPC host |
FLDIGI_PORT | 7362 | fldigi XML-RPC port |
FLDIGI_CALLSIGN | _(empty)_ | Operator callsign. The single transmit gate — set it to enable transmit; blank keeps the station receive-only |
FLDIGI_BAND_GUIDANCE | off | Experimental advisory band guidance. on to enable |
FLDIGI_REGION | 2 | IARU region for band guidance: 1, 2, or 3 |
FLDIGI_PATH | _(auto)_ | Explicit path to the fldigi executable (for application launch) |
FLDIGI_AUDIO_DEVICE | _(system default)_ | Input device the signal hunt taps: the name (or part of it) of the device fldigi listens on, e.g. iMic |
FLDIGI_HUNT_URL | _(empty)_ | URL of a fldigi-mcp-tap running beside fldigi, e.g. http://127.0.0.1:7365, for when this server cannot open the sound card (sandbox, or fldigi on another machine). Blank taps the local input device |
In the packaged desktop connector these appear as a settings form — most users only ever fill in the callsign.
The callsign is the single transmit gate. Keying operations (transmit tx/tune/run_macro/send, and the wefax/navtex send operations, and any keying method via fldigi_call) refuse unless FLDIGI_CALLSIGN is set. With it blank, the station is receive-only. rx, abort, and disable_tx are always allowed because they take the station *off* the air. Any non-blank value is accepted (club, event, vanity, portable, and international calls all work). See docs/install-and-safety.md.
An optional, advisory feature that suggests a mode's customary "watering hole" and warns when a frequency falls outside the digital band segment — guidance and defaults, never hard locks. Region-aware (IARU R1/R2/R3), covering