Tried a new SD card install for 3.5 no dice


#1

My old sd card works fine but when I installed 3.5 according to the setup page the feedback I get from the device on my adsb page is
no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2017-09-19 17:21 EDT] no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s

Im not sure what i missed. I downloaded the sip file and the etcher program to flash image to sd card no luck and for some reason the wifi wont work even when i set it up as instructed on the sd card and saved it there.


#2

I went back 2.15 for now from old sd card


#3

Are you using the same unique identifier as the old site? If it’s a totally new site then you need to claim it so it will show up on your stats page.


#4

I tried to keep it all the same. It worked the time i tried with 3.0 but I spent a couple of hours playing with the sd card with reinstalls after clean formats and nothing.I folloed the install instructions but appears all i get is the no ADSB program error


#5

You have posted status as seen on your stats page. Can you SSH to your Pi from your Desktop/Laptop/Tablet/Phone?

If ‘yes’, please give following commands one by one, and post here output for each command.

sudo lsusb

sudo systemctl status dump1090-fa -l

sudo apt-cache policy dump1090-fa

#6

Ill try and look at it tomorrow or later today if i can some time on my hands…summer weather is back and trying to get outdoor stuff done before winter


#7

0005 for 370 seconds, trying to start it…
[2017-09-26 19:39 EDT] attempting to start dump1090…
[2017-09-26 19:39 EDT] attempting to start dump1090-fa using ‘systemctl --no-block restart dump1090-fa.service < /dev/null’…
[2017-09-26 19:39 EDT] dump1090 start appears to have been successful
[2017-09-26 19:39 EDT] no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s

I keep getting this from the stat window. I have not saved the ssh file yet so i can get to it to via putty. Annoying security step.

I am hard wired while doing this. Ill have to add the ssh file i guess.


#8

pi@piaware:~$ sudo lsusb
Bus 001 Device 006: ID 214b:7000
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

pi@piaware:~$ sudo systemctl status dump1090-fa -l
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2017-09-27 00 :34:47 UTC; 21s ago
Docs: https://flightaware.com/adsb/piaware/
Process: 1549 ExecStart=/usr/bin/dump1090-fa $RECEIVER_OPTIONS $DECODER_OPTION S $NET_OPTIONS $JSON_OPTIONS $PIAWARE_DUMP1090_LOCATION_OPTIONS --write-json /ru n/dump1090-fa --quiet (code=exited, status=1/FAILURE)
Main PID: 1549 (code=exited, status=1/FAILURE)

Sep 27 00:34:47 piaware systemd[1]: dump1090-fa.service: main process exited, co de=exited, status=1/FAILURE
Sep 27 00:34:47 piaware systemd[1]: Unit dump1090-fa.service entered failed stat e.

pi@piaware:~$ sudo apt-cache policy dump1090-fa
dump1090-fa:
Installed: 3.5.1
Candidate: 3.5.1
Version table:
*** 3.5.1 0
500 http://flightaware.com/adsb/piaware/files/packages/ jessie/piaware armhf Packages
100 /var/lib/dpkg/status


#9

Your Pi cannot see the rtlsdr dongle (or any wifi adaptor, for that matter). Check your connections. 214b:7000 appears to be a USB hub of some type, try it without the hub?


#10

Your Pi did not detect DVB-T, as there is no mention of it in output of lsusb command.

Below is the output of my Pi on lsusb command

pi@piaware:~$ lsusb
Bus 001 Device 004: ID 0bda:2832 Realtek Semiconductor Corp. RTL2832U DVB-T
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


#11

Why does the version that’s currently running right now 2. Something is connected with no problems I will check back tomorrow


#12

Those sats from my feeder were while it was hardwired and not wifi


#13

Try one more test

#first stop dump1090-fa to free the dvb-t 
sudo systemctl stop dump1090-fa

#now test the dvb-t
sudo rtl_test -t

#after test, restart dump1090-fa
sudo systemctl restart dump1090-fa

.
.
When I ran this test on Pro Stick, I got following output:

sudo systemctl stop dump1090-fa
sudo rtl_test -t
Found 1 device(s):
  0:  Realtek, RTL2832U, SN: 00001000

Using device 0: Generic RTL2832U
Found Rafael Micro R820T tuner
Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
Sampling at 2048000 S/s.
No E4000 tuner found, aborting.

#14

Thanks so much to the both of you guys. Obj (Oliver) had it nailed it was the USB hub causing the issues. Removed the hub and it works fine. I dont know why Flightaware 2.1-5 had no issues with the hub. I had the hub there for more usb ports. This is the SDR dongle I use RTL-SDR Blog R820T2 RTL2832U 1PPM TCXO SMA its in a metal case. seems to get more planes than the Flightaware orange colored one with built in Amp. So I still have the Sat amp for the dongle I use.

I plan on moving this set up ti a Rpi 3 Will that reset everything and would i then need to claim it as a new device.

Oh could either of you please help me with installing flightradar24. Somebody in the forum use to have an easy install script for that and it doesn’t seem to work with 3.0 and up.

Thanks

Chris


#15

Go to thread Bake a Pi, and scroll down to “ADDITIONAL DATA FEEDERS” and click over it. It will take you to the post which contains current bash script for installation of FR24 feeder, as well as configuration & signup instructions. I have installed fr24feed using this bash script last week.


#16

Thanks much appreciated