How to use an RTL2832U with a Chromebook

An RTL2832U is an inexpensive software-defined radio (SDR) dongle available for $30 or less. A Chromebook is a relatively inexpensive laptop running Chrome OS. Together you can build a radio receiver capable of receiving everything from longwave to UHF communications. It can also be used to monitor P25 trunked radio systems.

This guide assumes a base level of knowledge, including:

  • How to enable Linux on a Chromebook.

  • How to use the Linux CLI.

  • How to install software and edit files on Linux.

What you need

Hardware

  • RTL2832U dongle (only 1 is required)

  • A Chromebook with Linux enabled

Software

  • gnuradio

  • OP25

  • rtl-sdr

Note, everytime you plug your dongle into your Chromebook, you have to allow Linux to have access to your SDR device.

Install necessary software and drivers

Install packages

sudo apt install -y alsa-utils cmake git gnuradio libusb-1.0-0-dev rtl-sdr

Install drivers

cd rtl-sdr/
mkdir build
cd build
cmake ../ -DINSTALL_UDEV_RULES=ON
make
sudo make install
sudo cp ../rtl-sdr.rules /etc/udev/rules.d/
sudo ldconfig

Now restart your Chromebook to assure the drivers load.

Try it out!!

Open the Terminal window.

rtl_fm -f 162.4e6 -M nbfm -s200000 -r 48000 - | aplay -r 48000 -f S16_LE

You should hear the familiar sounds of NOAA Weather Radio or Weatheradio Canada playing. You will need to change to frequency to match your local weather radio station. If you’re outside of the US or Canada, try a local FM broadcast station.

rtl_fm -f 93.7e6 -M wbfm -s200000 -r 48000 - | aplay -r 48000 -f S16_LE

The above command will tune 93.7 MHz, in my case, KLBJ-FM.

HF communication

In order to enable reception below 28 MHz, bias trees must be enabled.

Install packages

mkdir -p ~/git && cd ~/git
git clone https://github.com/rtlsdrblog/rtl-sdr-blog
cd rtl-sdr-blog
mkdir build
cd build
cmake .. -DDETACH_KERNEL_DRIVER=ON
make
sudo make install

Enable bias trees

rtl_biast -b 1

Disable bias trees

rtl_biast -b 0

Using an RTL2832U for monitoring trunked systems

Install op25

The software can be installed anywhere a user has write access. I prefer to keep all git installed software under ~/git.

mkdir -p ~/git && cd ~/git
git clone https://github.com/boatbod/op25.git && cd op25
./install.sh

Install gr-osmosdr

mkdir -p ~/git && cd ~/git
git clone git://git.osmocom.org/gr-osmosdr && cd gr-osmosdr/
mkdir build
cd build/
cmake ../
make
sudo make install
sudo ldconfig

How to configure software

Before we get too in depth, let’s verify things are working. Since I live in Austin, I will use the Greater Austin/Travis Regional Radio System (GATRRS) as my example.

The best way to confirm your installation is to monitor the control channel frequency of a local system. And the easiest way to find that information is from the good folks over at RadioReference.com.

Software verification

All commands should be run from the apps directory. So let’s cd into that directory and go from there. If you installed your software in a different location I have to assume you know how to find it.

cd ~/git/op25/op25/gr-op25_repeater/apps

This is the command that will launch the software and start tracking.

./rx.py --args 'rtl' -N 'LNA:47' -S 2500000 -x 2 -f 851.2875e6 -o 17e3 -q 0

Here’s an explanation of that line.

Command/flag

Meaning

./rx.py

The python script you’re running

–args ‘rtl’

You’re using an RTL device

-N ‘LNA:47’

Gain setting, 47 should be fine

-S 2500000

Sample rate, 2500000 should be fine

-x 2

Audio gain, 2 should be fine

-f 851.2875e6

Control channel frequency in scientific notation

-o 17e3

Offset, 17e3 should be fine

-q 0

Frequency correction and this will likely need to be changed

If you selected the correct q value, you should see a screen similar to this after a few seconds.

If you get something like this, your q value isn’t correct. Try a different one, an integer between -5 and +5 inclusive.

Time to listen

You probably noticed you’re not hearing anything. This is because we haven’t told the software to do this. Now we will tell the computer to give us some audio.

cd ~/git/op25/op25/gr-op25_repeater/apps
./rx.py --args 'rtl' -N 'LNA:47' -x 2 -o 17e3 -q 0 -f 851.2875e6 -V -2 -U -n 2> stderr-stream0.2

Wait, all I see are talkgroup numbers? Have I gone back in time to the original Uniden Trunktracker scanner? We need data and the best source of this data is, again, RadioReference.com. You need to be a premium member to be able to download files. It’s well worth it, and keeps the crew who run the site fed. If you’re not a member, you’ll have to enter this info by hand or copy and paste.

Click on Download

Both of these files will download into your Chromebook’s Downloads folder.

You cannot simply copy them over to your apps directory. I have created a Perl script that creates the required files and places them in the appropriate directories.

The site file contains information about the site(s) for your system along with control channel frequencies. The tg file has the talkgroup information.

The software will scan through the control channels until it finds one. If there’s a site you prefer to monitor, then list that line first. If you prefer to monitor each site individually then create unique site files. They can all reference the same tg file.

In all honesty this is the hardest part and I hope my Perl script eases some of the pain.

Now it’s really time to listen

cd ~/git/op25/op25/gr-op25_repeater/apps
./rx.py --args 'rtl' -N 'LNA:47' -x 2 -o 17e3 -q 0 -T ~/.local/pisdr/sites/trs_site_2.tsv -V -2 -U -n 2> stderr-stream0.2

Be aware that the filename after the -T will vary depending on your local system.

Dashboard

Simply adding -l 'http:0.0.0.0:8080' to your rx.py command string, you can enjoy a web-based dashboard.

./rx.py -2 --args 'rtl=0' --gains 'lna:49' --nocrypt -l 'http:0.0.0.0:8080' -o 17e3 -q 0 -U -V -v 1 -X -T ~/.local/pisdr/sites/trs_site_2.tsv 2> /dev/null &

Now open your web browser and visit http://127.0.0.1:8080.

Closing remarks

I hope this helped. If something isn’t clear, feel free to email me about it. Also please, please read John’s (not me) article that I reference below. It’s written for installing on Ubuntu and gives a broader explanation than I give.