I’m trying to get my new RTL-SDR v.3 running with a ADS-B 1090 MHz LNA (from RTL-SDR as well).
The receiver alone runs great, albeit with fewer flight data received compared to the FlightAware Pro stick, but once I put the LNA in line and activate BiasT per documentation at Getting the V3 Bias Tee to Activate on PiAware ADS-B Images, I can’t get any more connections, albeit I did not change any other settings in my setup:
2023-09-01 19:37:22 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to tcp://localhost:30005
2023-09-01 19:37:22 | [reader][i]Connecting to unknown receiver via (tcp://localhost:30005)
2023-09-01 19:37:17 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to tcp://localhost:30005
2023-09-01 19:37:17 | [reader][i]Connecting to unknown receiver via (tcp://localhost:30005)
2023-09-01 19:37:12 | [reader][i]Connection terminated
2023-09-01 19:36:56 | [feed][n]syncing stream result: 1
2023-09-01 19:36:55 | [feed][n]ping 1
2023-09-01 19:36:44 | [reader][i]Configured, processing messages
2023-09-01 19:36:44 | [reader][i]Connected to the receiver, configuring
2023-09-01 19:36:44 | [reader][i]Connecting to unknown receiver via (tcp://localhost:30005)
2023-09-01 19:36:39 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to tcp://localhost:30005
2023-09-01 19:36:39 | [reader][i]Connecting to unknown receiver via (tcp://localhost:30005)
2023-09-01 19:36:34 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to tcp://localhost:30005
2023-09-01 19:36:34 | [reader][i]Connecting to unknown receiver via (tcp://localhost:30005)
2023-09-01 19:36:29 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to tcp://localhost:30005
2023-09-01 19:36:29 | [reader][i]Connecting to unknown receiver via (tcp://localhost:30005)
2023-09-01 19:36:25 | [feed][n]working
2023-09-01 19:36:25 | [feed][n]connected via UDP (fd 24)
The only reason I could think fo might be a too high power consumption on the Raspberry Pi 4 USB ports, but to be quite honest, I doubt that the modules pull that much power…
The method of enabling Bias-T on dump1090-fa given in RTL-SDR web page (linked in opening post of this thread) is based on the method originally found by @obj, and was posted by him in Flighaware forum in May 2017 here:
VARIENT #1: Enabling Bias-T on Flightradar24 image Pi24
The method to switch on biast on dump1090-fa does not work with Flightradar24’s Pi24 image which has an integral dump1090-mutability, whose start is controlled by the data feeder software “fr24feed”. Therefore I have added a line ExecStartPre= in file fr24feed.service. This line runs bias-t start and logging script before fr24feed and its associated dump1090-mutability are started.
I have posted method to turn-on bias-t on Pi24 image in my following post dated April 30, 2018 in Flightradar24 forum:
VARIAENT #2: Enabling Bias-T on dump1090-mutability (stand-alone, and NOT an integral part of Pi24 image)
The method to switch-on bias-t through dump1090-fa.service does not apply to dump1090-mutability, as the dump1090-mutability.service files are automatically generated by systemd-sysv-generator, and all the changes made by user are overwritten at restart / reboot.
However as the systemd-SysV-generator generates dump1090-mutability.service by reading from file /etc/init.d/dump1090-mutability, I have added Bias-T start and logging script in file `/etc/init.d/dump1090-mutability, and it works OK.
Please see my post dated May 01, 2018 in Flightaware forum:
Which filter/amp are you considering?
The OP is using the triple filtered RTLSDR blog amp, but as far as I can see, thepihut only stocks the uptronics unit.
