Control reference

Use this chapter to locate common commands and distinguish which part of the station they affect. Menu paths name the desktop command first; iPhone/iPad routes use tab names. For operating procedures, see receive, slices, transmit, and shared Core operation.

Common paths

iPhone and iPad operator procedures

Change the radio a connected Core runs

With the phone connected to the Core you intend to change, open Radio > More > Manage Radios. The page asks the Core for its radio list while the page is open. Read each card's name (or MAC if unnamed), model, protocol, IP address and MAC; In use identifies the radio it currently runs. Scan again requests a fresh LAN scan. Wait for The Core is looking for radios and the refreshed list. An empty-list message or a greyed action states when the Core is offline, too old, on air, or this session did not use a paired device key.

To switch radios, choose an inactive radio, review the confirmation, then tap Choose. The confirmation says the Core switches and every connected device, including this phone, reconnects. After the phone reconnects, read the Core/link and radio identity before continuing; do not assume a successful tap changed the selected radio. If the Core refuses the request, its words appear in Refusal. A disconnect or missing capability disables the action with its reason. Choosing the current In use radio is not a switch.

Use Change model only to change the model saved for a listed radio. Pick one of the Core-provided models; the checkmark marks the model the Core currently reports. The Core saves that choice for its next connection to that radio, so it does not switch the Core immediately. When the older Core does not list model choices, or lists only one, the page gives the reason instead of guessing. To remove an inactive saved radio from the Core, tap Forget, read the confirmation that also removes that radio's saved model, then tap Forget to confirm. A later scan may list the radio again while it is on the network. Check the resulting list or the Core's refusal before proceeding. These actions affect the Core's station, not just the phone's saved Your Cores list.

Adjust the Core's VAX levels from the phone

Open Tools > VAX Audio. This page controls VAX channels on the Core's computer, not audio devices on the phone. Each of VAX 1–4 identifies its virtual device and feeding slice or slices, then provides Level, a 0–100% slider, a level meter, and Mute. Set a channel level to change what digital-mode apps receive from that VAX channel. Mute silences that channel for its applications; it does not mute the speakers. Watch the meter and device/slice labels to make sure the intended receive path is selected. The VAX microphone section identifies the transmit slice and has its own Level slider and meter. That level changes the Core's VAX microphone input, not this phone's microphone route. Wait for values/meters to refresh; if a request is refused, the page displays the Core's reason. The TX-level slider is disabled unless this phone may transmit. Missing channel or meter data shows an older-Core/unavailable reason rather than a zero value. VAX application routing and platform availability are in Digital audio and external applications.

Use iPad screen arrangements and the meter

Follow the two-slice iPad listening session for the operating order. The details below explain the layout and meter choices used by that session.

On an iPad, the band screen uses three arrangements. With a regular-width window whose shorter side is at least 600 points, landscape uses the applet column: the band on the left and a 320-point column on the right, with the S-meter at the top and RX then TX controls below in one scroll view. Use the toolbar corner button to hide or show that column. In portrait at that size, the band stays full width and the S-meter, RX and TX are three columns below it; RX and TX scroll separately. Turning the iPad to landscape switches back to the applet column. A narrow split-view window or compact-width environment falls back to the phone arrangement, even on an iPad.

The analog S-meter shows the active slice's RX reading while receiving and the selected TX reading while on air. Tap the meter title bar's menu button, or press and hold the meter face, to open its menu. RX Mode offers Signal, Sig Avg, Signal Peak and Max Bin; TX Mode offers Power, SWR, Level and Compression. A mode whose required Core reading is unavailable is disabled with a reason. Peak Hold contains Enabled, Decay, and Reset. Meter Face selects one of the offered vintage faces or Classic. Check the needle/readout after a mode change; a disabled option is not a zero meter reading.

Edit a Core-described phone Setup control

Open Setup, choose a category, then a page the connected Core describes. The page uses the Core's labels, help text, choices, units and ranges. Native controls operate the shared Core/radio setting described by that page, not a private phone copy. A toggle or choice sends its selected value; a number control uses its step buttons; a slider sends when you release it; a text field sends when you submit it. A button or a particular value can ask for a confirmation. Read the control name and question, then select Yes to send or No to leave the value unchanged. Wait for the Core's updated value before treating an edit as accepted. If the Core refuses or the link is lost, the page shows its refusal or unavailable reason and retains the last accepted readback. Controls can be disabled for missing Core capability, stale/not-ready settings, transmit ownership, or on-air state. Do not retry until that displayed condition is addressed.

Some tables have native panels rather than generic rows: Notch Table edits an existing notch's center/width, active state and delete action; use receiver DSP notch procedures. Settings Validation lists severity, problem and detail and provides Re-validate, Repair, and Forget with Core confirmations where offered; use settings recovery. Antenna Rows selects per-band physical paths; see hardware and antennas. PA Telemetry is read-only and marks stale/unreported readings unavailable with their age; see PA readings. CFC Bands edits the transmit compressor/EQ curves on the Core; see voice processing. If a specialized control says it is unavailable on this phone, do not infer that its generic table placeholder is editable.

Desktop Setup page map

Open File > Settings... and select a leaf in the left-hand tree. Category names group pages; selecting a category is not the same as selecting an editable page. Read page/group scope and disabled reasons. In a remote window, some values arrive asynchronously from the Core and can remain unavailable until that readback is ready.

The phone Setup tree combines native phone pages with pages described by the connected Core. Therefore this desktop tree is not a promise of an identical phone tree. A Core can omit an unsupported page, or show it with a version or capability reason. Native phone Navigation, Audio, Display, Battery and sessions, Data use, PTT buttons, Devices, Logs and About pages are covered in phone session care and the phone chapters.

Menus and applets at a glance

The Containers menu's Applets section and the panel ☰ menu show registered applets. Availability can depend on connected hardware, an enabled service or the desktop build. An amplifier panel will not become functional merely because it is checked. Use window controls to show/float/dock an applet, and the relevant subject chapter to configure it.

What is personal and what is shared

Mixed or Both means inspect the individual group. It does not mean every field affects both places equally. A requested change, a pending confirmation and an accepted readback are different states.

Verified desktop shortcuts

These actions are present in the desktop menus of the source build covered by this draft. The current build has no shortcut-remapping page. macOS may display the platform's Command modifier in place of Ctrl; use the shortcut shown in the menu.

Gesture reference

Notch hit areas take precedence over ordinary band gestures. Locked, listened-to or on-air controls can refuse a request. See desktop gestures and phone operation for the full context.

Availability in this edition

This manual covers a development checkout, with real desktop figures from a separately identified development GUI. Check your installed build and connected Core rather than treating the manual as a public release compatibility list. The operator-facing exclusions below explain common missing controls.

Capability-held features such as PureSignal, diversity, PA profiles, specific antenna controls and neural noise processors require their compatible hardware, Core or installed assets. TCI/Client Chain availability also depends on the desktop build. Those are different from the explicit unbuilt surfaces above.

Abbreviations used on operating controls

Find a worked procedure

Terms

Core: The NereusSDR service connected to a radio. In phone operation it runs on the station computer and performs signal processing.

Device: A desktop window or paired phone connecting to a Core. Device-local audio and display choices do not automatically change another device.

Slice: A receiver channel with its own frequency, mode, filter, and receive controls. It may be owned by one device and shown read-only on another.

Panadapter: A frequency display containing one or more slices. A panadapter is a display arrangement; it is not itself a receiver.

TCI: The interface through which compatible programs can exchange radio control and audio with NereusSDR. A connected client needs transmit ownership before it can key.

VAX: Virtual audio channels for routing receive and transmit sound to digital-mode software on the computer running those channels.

RADE: A digital voice mode with receive decoding and a Core transmit vocoder. Select RADE-U or RADE-L for the appropriate sideband, then use the RADE applet for profile and decode status.

TXcontrol: Ownership held by the desktop window that is allowed to control transmit. TCI transmit requires this ownership.