Enable BiasT on RTL-SDR v3 before Dump-FA/Piaware start

Yes but you will need to provide the full path to rtl_biast

Thanks for the help - will give it a try in a while :smiley:

No joy I’m afraid :frowning:

I created the directory /etc/systemd/system/dump1090-fa.service.d (no dump1090-fa.service.d directory in system) and then in the new directory created the bias-t.conf file with ‘ExecStartPre=/home/pi/rtl_biast/build/src/./rtl_biast -b 1’ as the only line in the file - rebooted and no voltage on the dongle output.

I tried running ‘/home/pi/rtl_biast/build/src/./rtl_biast -b 1’ from the command line and the error message came up as my first post.

I want to place the amp in my attic where the cable comes in, so would be great to get this biast option working.

Any other ideas??

Oh, you might need a [Service] header in the file:


You can check if systemd is picking it up correctly by “sudo systemctl cat dump1090-fa.service”
“sudo systemctl status dump1090-fa” and “sudo journalctl -u dump1090-fa” are also useful for working out what it’s doing.

1 Like

OK will try that cheers - Have had another play and your option 1 is working, but would be nice to get it to survive an update :smiley:

Bingo!!! That got it - putting the [Service] into that config file :slight_smile:

VMT for your assistance and patience - much appreciated.

OBJ: Your instructions were great. Thank you!


Hey Obj, I’m trying to enable this feature but I’m getting an error. I have created the directory /etc/systemd/system/dump1090-fa.service.d. Then I created the file bias-t.conf within that directory. in the bias-t.conf file I have the following:

ExecStartPre=/home/pi/rtl-bias-tee/rtl_biast/build/src/rtl_biast -b 1

On reboot, dump1090-fa is not running (webpage is not loading) and "systemctl cat dump1090-fa.service
responds with this:

root@piaware:~# systemctl status dump1090-fa.service
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/dump1090-fa.service.d
Active: activating (auto-restart) (Result: exit-code) since Sun 2017-11-05 13:12:47 PST; 10s ago
Docs: https://flightaware.com/adsb/piaware/
Process: 713 ExecStartPre=/home/pi/rtl-bias-tee/rtl_biast/build/src/rtl_biast -b 1 (code=exited, status=6)

Nov 05 13:12:47 piaware systemd[1]: dump1090-fa.service: Unit entered failed state.
Nov 05 13:12:47 piaware systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.

Any thoughts?

What happens if you run the command by hand?

if I issue “sudo service dump1090-fa stop"
”/home/pi/rtl-bias-tee/rtl_biast/build/src/rtl_biast -b 1"

it works fine

If I don’t first stop dump1090, I get this error
"usb_claim_interface error -6"

but following a reboot its not working.

Well… I may have had some issues with blacklists… for the hell of it, after I wrote my last reply, I rebooted again just to verify if things were as I said they were. Sure enough, things were now different. Now I was getting this:

Kernel driver is active, or device is claimed by second instance of librtlsdr.
In the first case, please either detach or blacklist the kernel module
(dvb_usb_rtl28xxu), or enable automatic detaching at compile time.

usb_claim_interface error -6

I re-did the modprobe blacklist file, rebooted, and now things are working as expected… I’ll keep an eye on things but for now at least, things seem to be working.

Also, thank you for all that you do on these forums. I get that for the most part you wouldn’t do it if you didn’t like it, but none the less, I for one appreciate all that you do here. Sometimes people forget that there is REALLY a lot of things going on behind the scenes with piaware/dump1090-fa, and everything has to work in unison for things to work at all. All anyone has to do is search the forums and see that you show a greal of patients with all of us… Thank you.


Also, adding the LNA almost doubled my messages/second, I love it. My distance increased, but not by as much as I would have thought.

Well same dongle but working with 1090 mutability, but same error message when trying to turn on bias t, suggestions??

hi jib56

if error is usb_claim_interface error -6 usually has to do with blacklisting the device OR
another app has taken over the device.
if error is by bias T, means you have to run first the bias T and then the decoder (-mutability, -fa etc),
provided that you have followed the tutorial [https://www.rtl-sdr.com/rtl-sdr-blog-v-3-dongles-user-guide/] to the letter.

any reboot will reset (turn off) the bias T feature.



Screenshot below is that of lower part of the following page:

The link under “Credits” points to one of the posts in the thread you are browsing now:

I tried to follow the instructions on here today which are based on this thread I understand:

Thank you for the information and for most part it worked, but I had to do one more thing at the end:

sudo systemctl daemon-reload

Without that the service would not start but complained that the service had “changed on disk”. After issuing that command (which came up as an instruction included in the error message), the service started and bias-t was enabled and working.

I am not using the Piaware image, just the light Raspian image and following the instructions here to install dump1090-fa:

Infact it is the other way round. If you scroll to bottom of the rtl-sdr . com page, under Credits you will find link to this thread. The method in rtl-sdr . com is based on @obj’s method given in post #2 of this thread.

You’ll get better results with lower gain, at least for airplanes flying close by and low.
In the second post of the thread linked below there is some practical advice on setting gain:
Thoughts on optimizing gain

With your LNA/dongle combination try 28 as a start.

Here is a short summary how to change the gain depending on your installation:
For Beginners - How to Set / Change Gain

Thank you. I will experiment a bit with that.