Release an idle device so a forgotten connect can't hold the shared radio
A client that calls bladerf_connect and never disconnects kept the USB claim until the server exited, blocking every other tool on the shared bladeRF. A watchdog thread now releases the device after MCBLADERF_IDLE_TIMEOUT seconds without a tool call (default 600, 0 disables). Middleware counts tool calls in flight, so a release never lands mid-call, and it also skips while a capture runs. The RX/TX settings are saved first; the next device call reconnects and restores them, sample rate included, since the radio resets that to 4 MHz on open. bladerf_status reports auto_released in between. Version 2026.11.15.
This commit is contained in:
+1
-1
@@ -1,6 +1,6 @@
|
||||
[project]
|
||||
name = "mcbladerf"
|
||||
version = "2026.10.25"
|
||||
version = "2026.11.15"
|
||||
description = "MCP server for Nuand BladeRF SDR control via SoapySDR"
|
||||
authors = [{name = "Ryan Malloy", email = "ryan@supported.systems"}]
|
||||
readme = "README.md"
|
||||
|
||||
Reference in New Issue
Block a user