New channel Tx plugin modchirpmodem, built on libchirpmodem (format v1),
modelled on modpacket: plugin, settings, baseband, source, GUI, web API
adapter, readme.
- A transmission is the message's frames, separated by a gap, then a CW ID
with the source callsign. It is generated in full on a one-thread
generator pool, never on the DSP thread, and posted back to the baseband;
the source plays it out at the channel rate. A result made for an old
channel rate or offset is generated again; one on air when the rate or
offset changes is cut off and reported.
- Policy is libchirpmodem's: a licensed frame without a source callsign is
refused (EPOLICY) and CW ID above 20 WPM is rejected; no encryption
option. CW ID can be turned off in the licensed profile, with a warning in
the GUI and the report. The unlicensed profile is shown in red.
- Settings: SF, BW, payload mode, profile, src, dst, message, repeat, gap,
amplitude, CW ID and its speed. The GUI shows airtime per frame and the
largest body that fits (chirpmodem_frame_seconds, chirpmodem_max_body).
- Web API / MCP: ChirpModemMod.yaml (settings, report, actions), SWG
classes, ChannelSettings/Report/Actions and model factory entries cloned
from PacketMod (plain setters, safe in the request mapper's reset lists),
webapiutils, webapirequestmapper, webapi.qrc. Action {"tx": 1} with
optional src, dst and message for one transmission.
- Channelizer asked for 4 x BW, as chirpmodem_tx_new needs fs >= 2.2 x
(BW/2 + |IF|) and the channelizer leaves a residual offset.
Verified: FileOutput -> cm_rx 3/3 frames, +17.4 dB, 0.0 Hz; FileOutput ->
FileInput -> demodchirpmodem 3/3 in get_packets; over the air (Pluto at
-30 dB through 40 dB to an RTL-SDR, 223.58 MHz) 15/15 frames received by
demodchirpmodem, matching cm_rx on SDRangel's recording of the same signal
(+17.0 dB, -2713 Hz).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
New channel Rx plugin demodchirpmodem, built on libchirpmodem (format v1),
modelled on demodselcal: plugin, settings, baseband, sink, GUI, web API
adapter, readme. Rx only.
- The channel is decimated to at least 2 x BW; the library is given the
delivered rate and the signal's residual offset in it (if_offset).
- The chirpmodem_rx handle lives in the sink and is used only on the
baseband thread under the baseband mutex. Settings changes mark it stale;
it is rebuilt once per message, never during chirpmodem_rx_push().
- Frames are copied in the callback and posted to the channel, which
forwards them to the GUI and publishes OK frames (whole MAC frame) on the
"packets" pipe.
- GUI: SF, BW, effort, auto effort, report failures, max bytes; frames table
(UTC, status, profile, src, dst, SNR, offset Hz/ppm, mode, length, text,
hex) with licensed-profile policy flag; channel spectrum.
- libchirpmodem found with find_package(chirpmodem 0.1 REQUIRED), hint
CHIRPMODEM_DIR or ~/.local; linked statically. Builds in SERVER_MODE.
Web API / MCP support:
- ChirpModemDemod.yaml (settings and report), SWG model classes, entries
in SWGChannelSettings/SWGChannelReport/SWGModelFactory, webapiutils,
webapirequestmapper and webapi.qrc.
- MCP data feed: listen to sdrangel.channel.chirpmodemdemod and decode the
MAC frame (flags, base-40 callsigns, body) for get_packets.
Verified on the 2026-10-23 OTA capture (ota.cu8 -> .sdriq, FileInput):
49/49 frames, identical to cm_rx in order, source and body; last-frame SNR
and offset match (-10.1 dB, -2651.5 Hz, -11.86 ppm).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Fix TX scaling bug that was costing 10dB of output power at max gain.
Improve performance on Windows to reduce overruns at high sample rates.
Add underrun stats.
Display temperature.
Improve error handling.
Move setting device settings off GUI thread. For #1522
GET .../spectrum/history reads the history the spectrum display keeps
for scrolling and reports, over the last seconds and a frequency range
reduced to bins, the per bin maximum, mean and occupancy against a
floor taken as the median of the per bin means, and the signals: each
run of bins above the threshold with its frequency, width, peak, duty
cycle and first and last seen. GET .../spectrum/history/image renders
the same history as a greyscale PNG with its extents in headers.
GLSpectrumInterface gains getSpectrumHistory, which GLSpectrumView
answers from its scroll buffer under its mutex, folding consecutive
rows together by maximum so that at most the rows asked for span the
whole period, since every FFT is a row. Rows taken at another centre or
rate are skipped and counted.
SpectrumVis reads the display while holding its mutex, so the display
is now attached and detached under it, and each side clears the other
on destruction.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
GET /sdrangel/windows lists every device, spectrum, channel and feature
window with its workspace, title and whether it is hidden; the workspace
PUTs take a hidden field alongside the index.
The Web API has no access to the GUI, so MainCore keeps a table of what
the GUI has published for each window, keyed by the DeviceAPI,
SpectrumVis, ChannelAPI or Feature it belongs to. The GUI side is a new
WorkspaceWindow base for the four window classes, which publishes on
every show and hide, on a retitle and when the workspaces are renumbered,
and takes the workspace from the window's Workspace ancestor rather than
the plugin's settings, which a settings message from the channel can
reset.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
POST /sdrangel/workspace/{workspaceIndex}/actions with a WorkspaceActions body whose action
is one of cascade, tile, stackVertical, stack, autostack or tab, doing what the workspace
toolbar buttons do. The one-shot arrangements switch tabbed windows off first; autostack and
tab set the corresponding option. The SWG class is written by hand to match the yaml, as the
code generator was not run.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Server side for the spectrum paths added to the spec: GET spectrum/report
returns whichever measurement is switched on, POST spectrum/actions
carries autoscale, clearSpectrum, resetMeasurements, freeze and
gotoMarker, and GET spectrum/data returns the power values reduced to a
number of bins. The display actions reach the spectrum through new
GLSpectrumInterface methods that default to doing nothing, so an instance
without a GUI ignores them rather than every caller having to know.
The measurement results are kept as plain values behind a lock and
published once per displayed frame, so a report costs nothing until one is
asked for, and the figures match what is on screen.
Also completes the main spectrum settings, which were only partly carried
over the API, and adds reports that had no way to be read at all: vessels
for AIS, stations for APRS, sondes for Radiosonde, the programme list for
DAB, the RDS programme service name for BFM, and validity flags for the
ADS-B aircraft report so a caller can tell a missing position from one at
zero. Map settings are exposed through their generated setters.
Two fixes found while testing: the frequency scanner dropped the frequency
list because the API calls it "frequencies" and everything downstream
keys it as "frequencySettings", and the spectrum adapters bound a
reference to the error message before init() had allocated one, so every
error path returned no response at all.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The MeshCore mod plugin references SWGMeshcoreModActions in
meshcoremod.cpp, but MeshcoreMod.yaml had no MeshcoreModActions
section. When swagger files are regenerated, the auto-generated
SWGChannelActions.h/cpp lose the meshcore_mod_actions member and
accessors, which would break compilation of meshcoremod.cpp.
Changes across five files:
- MeshcoreMod.yaml: add MeshcoreModActions definition (sendNow
field, matching existing hand-authored SWGMeshcoreModActions)
- ChannelActions.yaml: add MeshcoreModActions pointing to
the new section
- SWGModelFactory.h: add #include and create() registration
block for SWGMeshcoreModActions (was missing despite
SWGMeshcoreModSettings/MeshcoreDemod* being registered)
- webapirequestmapper.cpp: add channelActionsKey routing branch
for MeshcoreModActions (was completely absent)
- webapiutils.cpp: add m_channelURIToSettingsKey and
m_channelTypeToSettingsKey entries for both MeshcoreDemod and
MeshcoreMod (were missing, unlike ChirpChat and Meshtastic
which have entries for their channel types)
Problem: It's not possible to select channel in Demod Analyzer feature
via api.
Solution:
Add new "action" into
POST /sdrangel/featureset/feature/{featureIndex}/actions
endpoint
Editing FrequencyScanner via api fails due to null pointer.
Failure happens when swagger generated setValue method is called for
complicated/nested structure on the object with is created by
constructor, but not initialized by the ::init method.
Solution:
1. Call init on newly created object
2. Proactively fix this for all types of settings objects