Airspy - Readsb Combo error messages

I’ve rebuilt my Airspy driven device recently.

So far it works, but i have a reconnect every 65 seconds from readsb to airspy_adsb on Port 30004. This is the default port in airspy config, i’ve set readsb to net-only to 127.0.0.1, 30004

This is what is in the logs:

Mar 23 17:07:12 Raspi44 readsb[5944]: Beast TCP input: No data or heartbeat received for 65 seconds, reconnecting: 127.0.0.1 port 30004
Mar 23 17:07:12 Raspi44 readsb[5944]: Beast TCP input: Connection established: 127.0.0.1 port 30004
Mar 23 17:08:17 Raspi44 readsb[5944]: Beast TCP input: No data or heartbeat received for 65 seconds, reconnecting: 127.0.0.1 port 30004
Mar 23 17:08:17 Raspi44 readsb[5944]: Beast TCP input: Connection established: 127.0.0.1 port 30004
Mar 23 17:09:22 Raspi44 readsb[5944]: Beast TCP input: No data or heartbeat received for 65 seconds, reconnecting: 127.0.0.1 port 30004
Mar 23 17:09:22 Raspi44 readsb[5944]: Beast TCP input: Connection established: 127.0.0.1 port 30004
Mar 23 17:10:27 Raspi44 readsb[5944]: Beast TCP input: No data or heartbeat received for 65 seconds, reconnecting: 127.0.0.1 port 30004
Mar 23 17:10:27 Raspi44 readsb[5944]: Beast TCP input: Connection established: 127.0.0.1 port 30004
Mar 23 17:11:32 Raspi44 readsb[5944]: Beast TCP input: No data or heartbeat received for 65 seconds, reconnecting: 127.0.0.1 port 30004
Mar 23 17:11:32 Raspi44 readsb[5944]: Beast TCP input: Connection established: 127.0.0.1 port 30004

and my readsb config

# readsb configuration
# This is sourced by /etc/systemd/system/default.target.wants/readsb.service as
# daemon startup configuration.

RECEIVER_OPTIONS="--net-only --net-connector 127.0.0.1,30004,beast_in"
DECODER_OPTIONS="--lat 49.8617 --lon 7.81344 --max-range 720 --write-json-every 1"
NET_OPTIONS="--net --net-heartbeat 60 --net-ro-size 1250 --net-ro-interval 0.05 --net-ri-port 30001 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005"
JSON_OPTIONS="--json-location-accuracy 2 --range-outline-hours 24"

I’ve tried to remove the --net-bi-port statement, but then get a “connection refused” warning

Any ideas?

I think i fixed it by using the default readsb config again and adjusted the location. Obviously my fault during installation.

This one works

# readsb configuration
# This is read by the systemd service file as an environment file.

RECEIVER_OPTIONS="--net-only --write-json-every 1"

DECODER_OPTIONS="--max-range 500"

NET_OPTIONS="--net --net-heartbeat 60 --net-ro-size 1280 --net-ro-interval 0.05 --net-ri-port 0 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005"

JSON_OPTIONS="--json-location-accuracy 2"

airspy_adsb doesn’t listen on 30004 … it pushes into 30004.

I’m not sure where you got the net-connector from, the airspy-conf doesn’t add that.

So you were you trying to get data from a port that’s made for pushing data into it.
It connects and then complains after a bit about not getting any data on the channel because the other side isn’t sending but also waiting to receive data.

Lucky you didn’t net-connector to 30005,beast_in … that would result in a data loop which is ugly.

1 Like

Don’t ask, what i did before. But i identified that immediately. :slight_smile:
Thanks for explaining, that was exactly my thought starting with a new config.

I have a seperate readsb instance running which catches the data from my AirSquitter. where the net-connecter is required to gather the data from the specific IP/Port, maybe that was the moment where i messed my thoughts up.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.