Repository navigation
Section 6 settings
Everything that configures sdroxide lives in one window, opened with the ⚙ SETTINGS button in the System module (the ⚙ SETUP button in the SPOTS window opens the same dialog on its Spots tab). Fourteen tabs run across the top:
| Tab | What it holds |
|---|---|
| General | Which version this is, your callsign, grid, IARU region and channel plan (11M/CB), the sound devices, and who may connect remotely. 6.1 |
| Radio | Which rig sdroxide talks to, and how. 6.2 |
| UI | Frame rate, waterfall palette, spectrum background, spot label colours, 3D cloud rendering, and the spoken announcements. 6.3 |
| Alerts | Sounds that ring when a decode matters: a station calling you, a new DXCC entity or grid. Audible alerts |
| Controls | Keyboard, mouse and MIDI bindings. 6.4 |
| Spots | DX cluster, POTA, SOTA and PSK Reporter feeds, and the broadcast station list. 6.5 |
| FreeDV | FreeDV Reporter (qso.freedv.org). 6.6 |
| Uploads | Callsign lookup, QSL upload, confirmation download. 6.7 |
| Winlink | The radio-email account, and whether it forwards over the internet or on the air. 6.8 |
| Servers | Hamlib rigctld, the built-in TCI server, and the WSJT-X UDP broadcast. 6.9 |
| T/R switch | The relay that grounds the SDR's antenna while the station transmits, and the sequencer around it. 6.11 |
| TLE | Satellites to track beyond the amateur set, and their frequencies. 6.10 |
| Profiles | Named snapshots of how the station is set up, put back on in one click. 6.12 |
Most settings take effect the moment you change them. The ones that open or rebind a connection — the radio itself, the spot feeds, FreeDV Reporter, and the two servers — have their own APPLY or Apply / reconnect button, noted in each section below, and so does Winlink, whose account is read by the next forwarding session rather than the moment you type it. Nothing here needs a restart.
Settings are written to the per-user config directory (§13):
display preferences to config.toml, the radio to radio.json, key/mouse/MIDI
bindings to input.json, feeds and credentials to net.json, the two servers
to rigctld.json, tciserver.json and wsjtx.json, the satellite
additions to satellites.json, the transmit/receive switch to relay.json,
and the saved setups to profiles.json.
Most of those files describe the station, not the screen: the feeds it
connects to, the servers it offers, the satellites it tracks, the radio it has.
They live on the machine the radio engine runs on, and the engine tells every
client what they say — so the Radio, Spots, FreeDV, Uploads,
Winlink, Servers, TLE and Profiles tabs show, and change, the real thing
whether you are at the shack machine, on a native remote client or in a browser tab. The T/R switch
tab is the same kind of thing — the relay is bolted to the antenna, not to your
desk — with one difference worth knowing before you use it from away: its
TEST buttons operate real hardware in a room you are not in. (The Radio tab
keeps back the parts that are about a machine rather than about the radio:
which interface to open, and the buttons that scan a bus or test an address. See
8.4.) input.json and the [ui], [speech] and [alerts]
tables of config.toml are the exception, and belong to the screen in front of you: a
display preference and a knob on your desk have nothing to do with the radio in
the other room — and so does the [remote_server] address on the General
tab, which is where this screen goes rather than anything about the station it
arrives at. The rest of config.toml — including the [remote_access]
sign-in — belongs to the engine's machine, which is why the Remote access
section of the General tab is only shown there.
From the User Manual. Home.