HackerGadgets AIO Board Package

uConsole
,
613

yes I tried but they are same

615

Did you use the aiov2_ctl.py script to make sure to turn on the devices?

616

no i m not understand how to use it.there is not doc for this board so i m handless.

bored99 <notifications@clockworkpi.discoursemail.com>于2026年1月10日 周六下午11:07写道：

617

can u tell me how to use it and where is this script？thx

Blaze Hu <blazehu314@gmail.com>于2026年1月10日 周六下午11:11写道：

618

check it out here.

1 Like
619

Howdy, Just installed Trixie with the new AIO 2 goodies w/NVME. Install went fine. OS up and running. Youtube with audio just fine. Added Rex’a Hacker Gadgets AIO package using script above. SDR++ came with up, tunes and receives fine. No audio though. I followed:

“If you’re using Trixie you’ll need to add an audio sink. On the left side scroll down to Module Manager. At the bottom of Module Manager type audio and select linux_pulseaudio_sinkthen click the + symbol. Then add the audio sink in the Sinks menu on the left side back up towards the top.“

I select “linux_pulseaudio_sink“ theb try to click the “+” symbol and nothing happens. No “audio sink” appears in the “Sinks” menu. Any suggestions? Thx.

620

Did you name the sink?

621

Not sure what you mean, I followed the instruction. A little unclear on “type audio”

622

Got it now! Actually typed audio into the empty box. Works now. On another note, PyGPSClient, unable to get it to work after selection /dev/ttyAMA0. The box shows n/a next to the selection. Thx

623

There’s a place to name the audio sink and then pick the device that newly name sink goes to.

624

Got it now thanks!

On another note, unable to get PyGPSClient to work after selection /dev/ttyAMA0. The box shows n/a next to the selection. The device is shown in terminal when I ls -l /dev/ttyAMA*.

625

if you are on the AIOv2 board, make sure you have turned on the GPS chip using the aiov2_ctl.py script.

626

Hi, I have a huge problem. I installed my AIO2 board, but it doesn’t seem to be recognized at all. None of the installed programs are running. Everything is installed as described in the first post. The only thing is that both LEDs on the RJ45 port are constantly lit. I don’t need the RJ45 port. It’s not supported even without the new adapter board, which I haven’t installed. I used a freshly installed image from Bookworm and Trixie for this. Does anyone have any ideas?

627

the AIOv2 is different from the V1 and requires an additional script to turn everything on

628

here you go. GitHub - hackergadgets/aiov2_ctl: This is a client for controll the aiov2

1 Like
629

Thank you for the link. I’ll test it. Vileer expanded the description this morning. Unfortunately, I’m a complete noob when it comes to Linux…

630

IMG_2276
IMG_22761920×2560 1000 KB
I received my AIO V2 board yesterday, this forum and ChatGPT5.2 helped me get it up and running this morning. Like others here lsusb command did not show the RTL-SDR device. Here’s a summary that may be helpful from others. This direct command from a ssh session on my desktop to my Clockworkpi device at 132 to tune 101.9 FM was very interesting. rtl_fm -f 101.9M -M wbfm -s 200k -r 48k - | aplay -r 48000 -f S16_LE

Absolutely — here’s a clean, durable summary you (and others) can follow to reach a known-good RTL-SDR operating point on ClockworkPi 132 with AIO V2 + SDR++ Brown.

:white_check_mark: KNOWN-GOOD OPERATING SEQUENCE (IMPORTANT)

Order matters. Always do this in order:

  1. Turn SDR power ON (AIO V2)
cd ~/aiov2_ctl
python3 aiov2_ctl.py SDR on
  1. Then start SDR++ Brown from the local desktop

  • Do not start SDR++ before SDR power is enabled

  • Do not start from plain SSH (no DISPLAY)

:control_knobs: BEST INITIAL SDR++ SETTINGS (FM Broadcast – proven)

Source (RTL-SDR)

  • Driver: RTL-SDR (Native / Soapy RTL)

  • Frequency: 101.900000 MHz

  • Sample Rate: 2.048 MSPS

  • Gain: Auto (or Manual ~25–35 dB)

  • Direct Sampling: OFF

Demodulator

  • Mode: WFM

  • Bandwidth: 200 kHz :white_check_mark: (critical)

  • De-emphasis: 75 µs (US standard)

  • Stereo: OFF initially (enable later if signal is strong)

Audio

  • Audio Rate: 48,000 Hz

  • AGC: OFF

  • Noise Reduction: OFF

  • Squelch: OFF

Waterfall / Zoom

  • Zoom so the FM signal fills ~180–200 kHz

  • Too wide = distortion

  • Too narrow = noisy / thin audio

:brain: WHY THIS WORKS

These settings match exactly what this proven CLI command does:

rtl_fm -f 101.9M -M wbfm -s 200k -r 48k - | aplay -r 48000 -f S16_LE

Anything that deviates (bandwidth, AGC, stereo, DSP) causes:

  • choppy audio

  • static

  • CPU overruns

  • SDR++ instability

:stop_sign: ONE-PROGRAM-AT-A-TIME RULE

The RTL-SDR cannot be shared unless using rtl_tcp.

  • SDR++ Play ON → CLI tools will FAIL

  • rtl_fm running → SDR++ will FAIL

Always stop one before starting the other.

:toolbox: CRITICAL DIAGNOSTIC COMMANDS (KEEP THESE)

Is the SDR physically present?

lsusb | grep -i 2838

Is the kernel stealing it as DVB? (bad)

dmesg -T | egrep -i "dvb|rtl283|rtl28xx"

If yes → blacklist required.

Blacklist DVB drivers (one-time fix)

sudo tee /etc/modprobe.d/rtl-sdr-blacklist.conf >/dev/null <<'EOF'
blacklist dvb_usb_rtl28xxu
blacklist rtl2832
blacklist rtl2830
blacklist rtl2832_sdr
EOF

Is something already using the SDR?

sudo fuser -v /dev/bus/usb/001/008

If you see:

  • readsb

  • dump1090

  • rtl_*

→ they must be stopped.

Stop ADS-B service (common blocker)

sudo systemctl stop readsb
sudo systemctl disable readsb

Can librtlsdr open the device? (gold test)

rtl_test -t

:white_check_mark: Should list device and tuner with no usb_claim_interface error

:collision: COMMON FAILURE CAUSES (WHAT WE HIT)

Symptom Root Cause
Device shows but no waterfall DVB driver attached
usb_claim_interface error -6 Another program owns SDR
SDR++ crashes from SSH No DISPLAY (GUI app)
Static / choppy FM Wrong bandwidth, AGC, stereo
SDR++ won’t start SDR power not enabled first

and for manually tuning 101.9 FM on SDR++ Brown on Clockworkpi

Your SSH command is giving clean audio because it is very specific about bandwidth, demodulation, and filtering. SDR++ defaults are not equivalent, which causes the choppy/static sound.

Set only these settings in SDR++:

Source (RTL-SDR)

  • Frequency: 101.900000 MHz

  • Sample Rate: 2.048 MSPS

  • Gain: Auto (for now)

  • Direct Sampling: OFF

Radio / Demodulator

  • Mode: WFM (Wide FM)

  • WFM Bandwidth: 200 kHz ← critical

  • De-emphasis: 75 µs (US FM standard)

  • Stereo: OFF (turn ON later if signal is strong)

rtl_fm -M wbfm -s 200k
:up_arrow: this is why 200 kHz matters

Audio

  • Audio Sample Rate: 48,000 Hz

  • Audio Output: Default (same device aplay uses)

  • Audio Buffer: leave default

DSP / Filtering

  • Squelch: OFF

  • Noise Reduction: OFF

  • AGC: OFF (important — rtl_fm does its own leveling)

Zoom / Waterfall

  • Zoom in so the FM signal fully fills ~180–200 kHz

  • If the signal spills wider → distortion

  • If it’s narrower → audio will sound thin or noisy

I hope this helps others. Great product!

Ed

6 Likes
631

Cheers for the writeup. Going to see if I can hear CH19 on the CB a little later (I have proper antennas and adapters for that).

632

Just an FYI that enabling power on the usbc rail does not provide enough power for the Wifi/Bluetooth chip, if you also ordered that.

More info here: HackerGadgets' uConsole Upgrade Kit - adding NVME SSD(PCIe), RJ45 Ethernet and USB 3.0 to your Uconsole - #527 by AceMedia

1 Like