No signals

Hello
Newbie here. I am using a Raspberry PI 3 with this dongle : shop.jetvision.de/epages/64807909.sf/en_...07909/Products/53199 to feed Flightradar24 and its working good. I¨m using FR24:s Raspian Image.
Now I would like also to feed OpenSky.
So I followed the instructions here : opensky-network.org/community/projects/30-dump1090-feeder
And I also created an account here. I can see my position and my uptime on the Receiver Profile. So at least this information is sent from my Raspberry Pi to my OpenSky account.
But I cant see any signals received.
Any help would be appreciated.

Did you check the log output? The feeder has indeed a connection to our servers but it doesn't seem to stream any data. This is either the case when the setup is broken and doesn't receive anything (which I assume is not the case) or when the feeder cannot connect to your local dump1090.

Can you check the log messages by running "sudo journalctl -b 0 -u opensky-feeder" if there are any errors?

schaefer wrote:

Did you check the log output? The feeder has indeed a connection to our servers but it doesn't seem to stream any data. This is either the case when the setup is broken and doesn't receive anything (which I assume is not the case) or when the feeder cannot connect to your local dump1090.

Can you check the log messages by running "sudo journalctl -b 0 -u opensky-feeder" if there are any errors?

Here is the output. Can it be a firewall issue?

-- Logs begin at Thu 2016-11-03 17:16:42 UTC, end at Sun 2018-03-11 09:38:47 UTC. --
Mar 08 06:49:57 raspberrypi systemd[1]: Started OpenSky Daemon.
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [COMP] Initialize STAT
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [COMP] Initialize POS
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [COMP] Initialize NET
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [COMP] Initialize TB
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [COMP] Initialize SERIAL
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [COMP] Initialize BUF
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [COMP] Initialize RELAY
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [COMP] Initialize RC
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [COMP] Initialize FILTER
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [COMP] Initialize RECV
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [COMP] Start STAT
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [COMP] Start POS
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [COMP] Start NET
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [COMP] Start TB
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [COMP] Start SERIAL
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [COMP] Start RELAY
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [COMP] Start RC
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [COMP] Start FILTER
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [COMP] Start RECV
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] Trying to connect to 'localhost': [127.0.0.1]:8754
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] connected to 'localhost'
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [NET] Trying to connect to 'collector.opensky-network.org': [194.209.200.4]:10004
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [NET] connected to 'collector.opensky-network.org'
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [LOGIN] Sending Device ID 5, Version 2.1.6
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [LOGIN] Sending Serial Number -1408236984
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [GPS] Sending position +58.4680°, +16.3200°, +65.00m
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [LOGIN] Sending Username 'stehul'
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [TB] Setting sync filter: 0
Mar 08 06:49:57 raspberrypi openskyd-dump1090[693]: [INFO] [TB] Setting ext squitter only filter: 0
Mar 08 06:50:01 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] Trying to connect to 'localhost': [127.0.0.1]:8754
Mar 08 06:50:01 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] connected to 'localhost'
Mar 08 06:50:05 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] Trying to connect to 'localhost': [127.0.0.1]:8754
Mar 08 06:50:05 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] connected to 'localhost'
Mar 08 06:50:09 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] Trying to connect to 'localhost': [127.0.0.1]:8754
Mar 08 06:50:09 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] connected to 'localhost'
Mar 08 06:50:13 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] Trying to connect to 'localhost': [127.0.0.1]:8754
Mar 08 06:50:13 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] connected to 'localhost'
Mar 08 06:50:17 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] Trying to connect to 'localhost': [127.0.0.1]:8754
Mar 08 06:50:17 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] connected to 'localhost'
Mar 11 08:26:26 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] Trying to connect to 'localhost': [127.0.0.1]:8754
Mar 11 08:26:26 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] connected to 'localhost'
Mar 11 08:26:30 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] Trying to connect to 'localhost': [127.0.0.1]:8754
Mar 11 08:26:30 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] connected to 'localhost'
Mar 11 08:26:34 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] Trying to connect to 'localhost': [127.0.0.1]:8754
Mar 11 08:26:34 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] connected to 'localhost'
Mar 11 08:26:38 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] Trying to connect to 'localhost': [127.0.0.1]:8754
Mar 11 08:26:38 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] connected to 'localhost'
Mar 11 08:26:42 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] Trying to connect to 'localhost': [127.0.0.1]:8754
Mar 11 08:26:42 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] connected to 'localhost'
Mar 11 08:26:46 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] Trying to connect to 'localhost': [127.0.0.1]:8754
Mar 11 08:26:46 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] connected to 'localhost'
Mar 11 08:26:51 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] Trying to connect to 'localhost': [127.0.0.1]:8754
Mar 11 08:26:51 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] connected to 'localhost'
Mar 11 08:26:55 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] Trying to connect to 'localhost': [127.0.0.1]:8754
Mar 11 08:26:55 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] connected to 'localhost'
Mar 11 08:26:59 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] Trying to connect to 'localhost': [127.0.0.1]:8754
Mar 11 08:26:59 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] connected to 'localhost'
Mar 11 08:27:03 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] Trying to connect to 'localhost': [127.0.0.1]:8754
Mar 11 08:27:03 raspberrypi openskyd-dump1090[693]: [INFO] [INPUT] connected to 'localhost'

This looks to me like a software/configuration problem. Two questions:

* Which dump1090 fork are you using? We're recommending the mutability fork.
* Why is the feeder trying to connect to port 8754? Dump1090's Beast Output is usually on port 30005

I have the same problem:
Trying to connect to '192.168.0.132': [192.168.0.132]:30005
Could not connect: Connection refused (111)

originally had localhost, but had the same problem.

I see /usr/bin/openskyd-dump1090 is running

Opened port forwarding for 192.168.0.132 8080 and 30005 on router.

Had this working on flightaware and flightradar24 previously, but no go with opensky today.

Would appreciate any help. thanks!

adsb132 wrote:

I have the same problem:
Trying to connect to '192.168.0.132': [192.168.0.132]:30005
Could not connect: Connection refused (111)

originally had localhost, but had the same problem.

I see /usr/bin/openskyd-dump1090 is running

Hi adsb132,

is dump1090 running on your device? You could check at which port it is listening with
If it is, which version/fork are you using?

Cheers,
Markus

Markus,

Thanks for your reply. I have version 1.14
I see this running:
/usr/bin/openskyd-dump1090
/usr/bin/dump1090-mutability --net --ppm --fix and a whole bunch of other configuration items.

But in syslog, I still see the same error as before about trying to connect; connection refused.

Thanks,

Rich

/usr/bin/dump1090-mutability --net --ppm 0 --fix --lat 21.3939 --lon -157.9358 --max-range 300 --net-http-port 0 --net-ri-port 30001 --net-ro-port 30002 --net-bi-port 30004 --net-bo-port 30005 --net-sbs-port 30003 --net-fatsv-port 0 --net-heartbeat 60 --net-ro-size 500 --net-ro-interval 1 --net-buffer 2 --net-bind-address 127.0.0.1 --stats-every 300 --write-json /run/dump1090-mutability --write-json-every 1 --json-location-accuracy 2 --quiet
root 4573 906 0 22:33 pts/0 00:00:00 grep dump

I also see:

Tue Jun 5 22:40:34 2018 UTC dump1090-mutability v1.14 starting up.
Found 1 device(s):
0: Realtek, RTL2832U, SN: 00001000 (currently selected)
usb_claim_interface error -6
Error opening the RTLSDR device: Device or resource busy

adsb132 wrote:

Tue Jun 5 22:40:34 2018 UTC dump1090-mutability v1.14 starting up.
Found 1 device(s):
0: Realtek, RTL2832U, SN: 00001000 (currently selected)
usb_claim_interface error -6
Error opening the RTLSDR device: Device or resource busy

This means, that dump1090 is not running properly as it cannot access the RTLSDR dongle. It might be caused by another process using the SDR hardware. You can try to find out more with lsof ('apt-get install lsof' if command is not found) as root. Here is an example from my Pi running other SDR software:

Using libusb is a good sign that the process 'es_sensor' is using our RTLSDR. To find out more about the process:

To see if it is the right one, we can kill it, restart dump1090 and see what happens to dump1090 and opensky-feeder:

Results may of course differ for you and the interfering process might be started automatically by an init script, cron job or systemd . Maybe it's another dump1090 installation or SDR application?

/usr/bin/dump1090-mutability ... --net-bo-port 30005 ... --net-bind-address 127.0.0.1

This is correct. The OpenSky feeder connects to the dump1090 Beast protocol port and forwards data to the network. There is no need for port forwarding on your router due to the outbund connection. Note that dump1090 is bound to 127.0.0.1, so the host for opensky-feeder needs to be localhost.

Looking forward to see your progress!

Hi...the Pi outputs a relatively weak HDMI signal. Some devices may not immediately notice the Pi's HDMI or may not do the negotiation.
Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.
You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

turnkey pcb