readsb with mode-s beast problem

vatprcyq commented 2 years ago

I have a modesbeast board but have problem with readsb It seems readsb can't set baudrate to 1000000? Test with microcom and same baudrate is normal output beast message. But if not add --beast-baudrate=1000000 readsb will abnormal exit Test: sudo readsb --device-type modesbeast --beast-serial=/dev/ttyUSB1 --beast-baudrate=1000000 Mon Aug 22 02:41:40 2022 CST readsb starting up. readsb version: wiedehopf git: 365daf3 (committed: Fri Aug 12 02:36:00 2022 0200) Beast cfsetispeed(/dev/ttyUSB1, 1000000): Invalid argument Mon Aug 22 02:41:40 2022 CST sdrOpen() failed, exiting! Mon Aug 22 02:41:40 2022 CST Abnormal exit. tianyi@BPI-M2:~ $ sudo readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --beast-baudrate=1000000 Mon Aug 22 02:41:52 2022 CST readsb starting up. readsb version: wiedehopf git: 365daf3 (committed: Fri Aug 12 02:36:00 2022 0200) Beast cfsetispeed(/dev/ttyUSB0, 1000000): Invalid argument Mon Aug 22 02:41:52 2022 CST sdrOpen() failed, exiting! Mon Aug 22 02:41:52 2022 CST Abnormal exit. tianyi@BPI-M2:~ $ tianyi@BPI-M2:~ $ microcom -p /dev/ttyUSB0 -s 1000000 connected to /dev/ttyUSB0 Escape character: Ctrl-\ Type the escape character to get to the prompt. +0000B00000000000000000000000; +0000B00000000000000000000000; +0000B00000000000000000000000; +00FFB00000000000000000000000; +0000B00000000000000000000000; +0000B00000000000000000000000; +00FFB00000000000000000000000; +00FFB00000000000000000000000; +0001B00000000000000000000000; +00FFB00000000000000000000000; +0000B00000000000000000000000; +0000B00000000000000000000000; +0000B00000000000000000000000; +0000B00000000000000000000000; +0001B00000000000000000000000; +0000B00000000000000000000000; +0001B00000000000000000000000; +0000B00000000000000000000000; +0000B00000000000000000000000; +0000B00000000000000000000000; +0000B00000000000000000000000; +0000B00000000000000000000000; +0000B00000000000000000000000; +0000B00000000000000000000000; +0000B00000000000000000000000; +0000B00000000000000000000000; +0000B00000000000000000000000; +00FFB00000000000000000000000; +00FFB00000000000000000000000; +0000B00000000000000000000000; +0001B00000000000000000000000; +0000B00000000000000000000000; +0000B00000000000000000000000; +0001B00000000000000000000000; +0000B00000000000000000000000; +0000B00000000000000000000000; +0000B00000000000000000000000; +0000B00000000000000000000000; +00FFB00000000000000000000000;

Enter command. Try 'help' for a list of builtin commands exiting tianyi@BPI-M2:~ $ sudo readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 Mon Aug 22 02:43:54 2022 CST readsb starting up. readsb version: wiedehopf git: 365daf3 (committed: Fri Aug 12 02:36:00 2022 0200) Running Mode-S Beast via USB.

<3>FATAL: removeStale() interval 60.1 seconds! Trying for an orderly shutdown as well as possible! <3> priorityTasksRun didn't run for 60.1 seconds! <3> removeStale didn't run for 59.1 seconds! Mon Aug 22 02:44:54 2022 CST Abnormal exit. tianyi@BPI-M2:~ $ Try stty -F /dev/ttyUSB0 ispeed 1000000 ospeed 1000000 but not work for me. tianyi@BPI-M2:~ $ lsusb Bus 001 Device 005: ID 10c4:ea70 Silicon Labs CP2105 Dual UART Bridge Bus 001 Device 004: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub readsb with RTLSDR is working.

wiedehopf commented 2 years ago

I don't have a modes beast to debug.

I'd recommend running https://github.com/flightaware/beast-splitter and connect to that using readsb.

Otherwise ... it doesn't seem you set the baudrate using the command line when using readsb ... check the help for that.

vatprcyq commented 2 years ago

I don't have a modes beast to debug.

I'd recommend running https://github.com/flightaware/beast-splitter and connect to that using readsb.

Otherwise ... it doesn't seem you set the baudrate using the command line when using readsb ... check the help for that.

Not working sudo readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --beast-baudrate=1000000 Mon Aug 22 03:27:07 2022 CST readsb starting up. readsb version: wiedehopf git: 365daf3 (committed: Fri Aug 12 02:36:00 2022 0200) Beast cfsetispeed(/dev/ttyUSB0, 1000000): Invalid argument Mon Aug 22 03:27:07 2022 CST sdrOpen() failed, exiting! Mon Aug 22 03:27:07 2022 CST Abnormal exit.

wiedehopf commented 2 years ago

Try the most recent commit please.

vatprcyq commented 2 years ago

Try the most recent commit please.

Use readsb-install.sh can't use new ver,showing ver is Aug 19 HEAD 现在位于 37865ea better spread full trace writes after startup rm -f .o compat/clock_gettime/.o compat/clock_nanosleep/*.o readsb viewadsb cprtests crctests convert_benchmark cc -std=c11 -W -D_GNU_SOURCE -D_DEFAULT_SOURCE -Wall -Werror -fno-common -O2 -DMODES_READSB_VERSION=\""wiedehopf git: 37865ea (committed: Fri Aug 19 19:18:45 2022 0200)"\" -Wdate-time -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wformat -Werror=format-security -Wno-format-truncation -DSC16Q11_TABLE_BITS=8 -DAIRCRAFT_HASH_BITS=16 -DENABLE_RTLSDR -g -O3 -march=native -c readsb.c -o readsb.o

Unable make manually: make -j3 RTLSDR=yes cc -std=c11 -W -D_GNU_SOURCE -D_DEFAULT_SOURCE -Wall -Werror -fno-common -O2 -DMODES_READSB_VERSION=\""wiedehopf git: d345be4 (committed: Sun Aug 21 22:10:23 2022 0200)"\" -Wdate-time -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wformat -Werror=format-security -Wno-format-truncation -DSC16Q11_TABLE_BITS=8 -DENABLE_RTLSDR -g -c readsb.c -o readsb.o cc -std=c11 -W -D_GNU_SOURCE -D_DEFAULT_SOURCE -Wall -Werror -fno-common -O2 -DMODES_READSB_VERSION=\""wiedehopf git: d345be4 (committed: Sun Aug 21 22:10:23 2022 0200)"\" -Wdate-time -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wformat -Werror=format-security -Wno-format-truncation -DSC16Q11_TABLE_BITS=8 -DENABLE_RTLSDR -g -c globe_index.c -o globe_index.o cc -std=c11 -W -D_GNU_SOURCE -D_DEFAULT_SOURCE -Wall -Werror -fno-common -O2 -DMODES_READSB_VERSION=\""wiedehopf git: d345be4 (committed: Sun Aug 21 22:10:23 2022 0200)"\" -Wdate-time -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wformat -Werror=format-security -Wno-format-truncation -DSC16Q11_TABLE_BITS=8 -DENABLE_RTLSDR -g -c api.c -o api.o globe_index.c: In function ‘load_blob’: globe_index.c:2772:25: error: comparison of integer expressions of different signedness: ‘int’ and ‘uint32_t’ {aka ‘unsigned int’} [-Werror=sign-compare] 2772 | if (end - p < compressed_len) { | ^ cc -std=c11 -W -D_GNU_SOURCE -D_DEFAULT_SOURCE -Wall -Werror -fno-common -O2 -DMODES_READSB_VERSION=\""wiedehopf git: d345be4 (committed: Sun Aug 21 22:10:23 2022 0200)"\" -Wdate-time -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wformat -Werror=format-security -Wno-format-truncation -DSC16Q11_TABLE_BITS=8 -DENABLE_RTLSDR -g -c minilzo/minilzo.c -o minilzo.o cc -std=c11 -W -D_GNU_SOURCE -D_DEFAULT_SOURCE -Wall -Werror -fno-common -O2 -DMODES_READSB_VERSION=\""wiedehopf git: d345be4 (committed: Sun Aug 21 22:10:23 2022 0200)"\" -Wdate-time -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wformat -Werror=format-security -Wno-format-truncation -DSC16Q11_TABLE_BITS=8 -DENABLE_RTLSDR -g -c threadpool.c -o threadpool.o cc -std=c11 -W -D_GNU_SOURCE -D_DEFAULT_SOURCE -Wall -Werror -fno-common -O2 -DMODES_READSB_VERSION=\""wiedehopf git: d345be4 (committed: Sun Aug 21 22:10:23 2022 0200)"\" -Wdate-time -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wformat -Werror=format-security -Wno-format-truncation -DSC16Q11_TABLE_BITS=8 -DENABLE_RTLSDR -g -c sdr_rtlsdr.c -o sdr_rtlsdr.o cc1: all warnings being treated as errors make: *** [Makefile:120：globe_index.o] 错误 1

wiedehopf commented 2 years ago

try once more ....

You can change the automatic script to use a different branch, it's not complicated.

vatprcyq commented 2 years ago

readsb now running with no error but no plane showing use beast-splitter is OK and beast-splitter show this is Radarcape-style ? sudo beast-splitter --serial /dev/beast --listen 37193:B Listening on 0.0.0.0:37193 Listening on [::]:37193 serial(/dev/beast): opening port at 3000000bps serial(/dev/beast): configured with settings: BCDfgHIjk serial(/dev/beast): configured with settings: RCDfgHIjk serial(/dev/beast): opening port at 1000000bps serial(/dev/beast): configured with settings: BCDfgHIjk serial(/dev/beast): autobaud failed, trying again (consider specifying --fixed-baud) serial(/dev/beast): opening port at 3000000bps serial(/dev/beast): configured with settings: BCDfgHIjk 0.0.0.0:37193: accepted a connection from 127.0.0.1:58704 with settings B serial(/dev/beast): configured with settings: BCdfgHijk serial(/dev/beast): opening port at 1000000bps serial(/dev/beast): configured with settings: BCdfgHijk serial(/dev/beast): autobaud selected 1000000 bps serial(/dev/beast): configured with settings: RCdfgHijk serial(/dev/beast): connected to a Radarcape-style receiver 127.0.0.1:58704: connection closed serial(/dev/beast): configured with settings: RCDfgHIjk 0.0.0.0:37193: accepted a connection from 127.0.0.1:56562 with settings B serial(/dev/beast): configured with settings: RCdfgHijk

vatprcyq commented 2 years ago

sudo beast-splitter --serial /dev/beast --listen 37193:B ./readsb --net-connector=127.0.0.1,37193,beast_in --net-only --interactive is OK

wiedehopf commented 2 years ago

I don't know what hardware you have.

Honestly i'm not sure i have interest in further debugging this ... without the hardware it's kinda complicated. Don't know what it needs beyond selecting 1000000 baud.

wiedehopf commented 2 years ago

Ok ... shot in the dark, try the most recent version of readsb with the baudrate specified.

dchaplinsky commented 1 month ago

Hi. I have the very similar issue.

I can see the device attached:

# dmesg | grep ttyUSB
[   10.658695] usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0

# lsusb
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

microcom can connect to the beast, and at baudrate 1000000 I can see the help et cetera.

readsb seems to connect okay on that speed (I can see it with lsof), but nothing happens and in 60 seconds it throws the error like this:

# sudo readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --beast-baudrate=1000000
invoked by: readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --beast-baudrate=1000000
[2024-09-15 21:23:55.768 EEST] readsb starting up.
readsb version: 3.14.1639 wiedehopf git: 123fbf1 (committed: Sun Aug 25 20:16:54 2024 0200)
Running Mode-S Beast via USB.
<3>FATAL: removeStale() interval 60.1 seconds! Trying for an orderly shutdown as well as possible!
misc thread: threadSignalJoin timed out after 30.0 seconds, undefined behaviour may result!
upkeep thread: threadSignalJoin timed out after 15.0 seconds, undefined behaviour may result!
decode thread: threadSignalJoin timed out after 7.5 seconds, undefined behaviour may result!
<3>FATAL: thread upkeep could not be joined, calling abort()!
Aborted

root@adsb:~# lsof | grep ttyUSB
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
      Output information may be incomplete.
readsb    1772                            root    5u      CHR      188,0      0t0        271 /dev/ttyUSB0
readsb    1772 1773 readsb                root    5u      CHR      188,0      0t0        271 /dev/ttyUSB0
readsb    1772 1774 readsb                root    5u      CHR      188,0      0t0        271 /dev/ttyUSB0
readsb    1772 1775 readsb                root    5u      CHR      188,0      0t0        271 /dev/ttyUSB0
readsb    1772 1776 readsb                root    5u      CHR      188,0      0t0        271 /dev/ttyUSB0
readsb    1772 1777 readsb                root    5u      CHR      188,0      0t0        271 /dev/ttyUSB0

The readsb is installed using quick install script. The version of the board is Mode-S Beast 1.30, the version of the RPI is RPI 2.

OS is

# lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

@wiedehopf If you willing to debug it, I can add you to the tailscale and give an access to the device.

wiedehopf commented 1 month ago

Install the sid branch like this:

 wget -O readsb-install.sh https://github.com/wiedehopf/adsb-scripts/raw/master/readsb-install.sh
 bash readsb-install.sh sid

Add this option, it might produce a lot of output:

--devel=debugSerial

The issue is probably is that it's reading from the device and not getting anything (and blocking on the read). I set it non blocking with that debug option but i'm not sure that's a good idea really. So ... with non blocking it might not crash but i don't think it'll work either.

dchaplinsky commented 1 month ago

Hi @wiedehopf, thanks for prompt reply.

no real change here:

root@adsb:~# sudo readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --beast-baudrate=1000000 --devel=debugSerial
invoked by: readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --beast-baudrate=1000000 --devel=debugSerial
[2024-09-16 09:06:42.095 EEST] readsb starting up.
readsb version: 3.14.1639 wiedehopf git: e6c2edb (committed: Sun Sep 15 22:10:44 2024 0200)
Running Mode-S Beast via USB.
06:06:42.111 event count 0 wait_ms 20
<3>FATAL: removeStale() interval 60.1 seconds! Trying for an orderly shutdown as well as possible!
misc thread: threadSignalJoin timed out after 30.0 seconds, undefined behaviour may result!
upkeep thread: threadSignalJoin timed out after 15.0 seconds, undefined behaviour may result!
decode thread: threadSignalJoin timed out after 7.5 seconds, undefined behaviour may result!
<3>FATAL: thread upkeep could not be joined, calling abort()!
Aborted

dchaplinsky commented 1 month ago

I can see some binary data with microcom tho:

wiedehopf commented 1 month ago

This does tell us something though.

Try again please, sid branch has been changed. Hopefully using the correct setting now to at least have a timeout for the reads from serial.

If you just want to get going i'd recommend this software which is better tested due to the amount of users and persons maintaining it having the hardware in question: https://github.com/flightaware/beast-splitter To avoid having to compile it, you can install it from the flightaware repository like this:

wget -O /tmp/piaware-repo.deb https://flightaware.com/adsb/piaware/files/packages/pool/piaware/f/flightaware-apt-repository/flightaware-apt-repository_1.2_all.deb
sudo apt purge -y piaware-repository &>/dev/null
sudo rm -f /etc/apt/sources.list.d/piaware-*.list
sudo dpkg -i /tmp/piaware-repo.deb
sudo apt update
sudo apt install -y beast-splitter

You can set it to listen on some port and have readsb connect via TCP to get the data from it.

readsb --net --net-connector 127.0.0.1,37232,beast_in
beast-splitter --serial /dev/beast --listen 37232:R

Possibly with this timeout i just put into the code readsb will work normally when possibly before it wasn't working properly when there was nothing being received. beast-splitter should allow you at least to confirm if it's working.

dchaplinsky commented 1 month ago

root@adsb:~# sudo readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --beast-baudrate=1000000 --devel=debugSerial
invoked by: readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --beast-baudrate=1000000 --devel=debugSerial
[2024-09-16 13:05:11.028 EEST] readsb starting up.
readsb version: 3.14.1639 wiedehopf git: 17fac8d (committed: Mon Sep 16 09:49:29 2024 0200)
Running Mode-S Beast via USB.
10:05:11.043 event count 0 wait_ms 20
10:05:11.063 serial read ... fd: 0 maxbytes: 262140
<3>FATAL: removeStale() interval 60.1 seconds! Trying for an orderly shutdown as well as possible!

I've tried beast splitter yesterday, but I'm not sure if it works properly. Not so many planes around me (I'm from Ukraine). I had the hope that there might be some over south of Belarus, but apparently those is no-fly zone:

# sudo beast-splitter --serial /dev/ttyUSB0 --listen 37232:R --fixed-baud 1000000
Listening on 0.0.0.0:37232
Listening on [::]:37232
serial(/dev/ttyUSB0): opening port at 1000000bps
serial(/dev/ttyUSB0): configured with settings: BCDfgHIjk
0.0.0.0:37232: accepted a connection from 127.0.0.1:52404 with settings R
serial(/dev/ttyUSB0): configured with settings: BCdfGHijk

Beast TCP input: Connection established: 127.0.0.1 port 37232
Beast TCP input: No data or heartbeat received for 120 seconds, reconnecting: 127.0.0.1 port 37232
Beast TCP input: Connection established: 127.0.0.1 port 37232
Beast TCP input: No data or heartbeat received for 120 seconds, reconnecting: 127.0.0.1 port 37232
Beast TCP input: Connection established: 127.0.0.1 port 37232
Beast TCP input: No data or heartbeat received for 120 seconds, reconnecting: 127.0.0.1 port 37232
Beast TCP input: Connection established: 127.0.0.1 port 37232
Beast TCP input: No data or heartbeat received for 120 seconds, reconnecting: 127.0.0.1 port 37232
Beast TCP input: Connection established: 127.0.0.1 port 37232
Beast TCP input: No data or heartbeat received for 120 seconds, reconnecting: 127.0.0.1 port 37232
Beast TCP input: Connection established: 127.0.0.1 port 37232

wiedehopf commented 1 month ago

Might just be that the receiver isn't working. fr24 somewhat has the best coverage. Your reception range will depend heavyily on geography and where the antenna is. This should give you some hints: https://github.com/wiedehopf/tar1090?tab=readme-ov-file#heywhatsthatcom-range-outline

Anyhow this gives me some idea possibly:

10:05:11.063 serial read ... fd: 0 maxbytes: 262140

I don't think fd == 0 can be correct ... i suspect it's a race with the logic initializing the SDR. Could you run readsb-install.sh sid once more and try again, ty.

wiedehopf commented 1 month ago

Oh actually i think that's still not correct ... let me change the code once more.

Code changed on sid branch.

dchaplinsky commented 1 month ago

Looks the same to my eye:

pi@adsb:~ $ sudo lsof | grep ttyUSB
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
      Output information may be incomplete.
readsb    4152                            root    5u      CHR      188,0      0t0        273 /dev/ttyUSB0
readsb    4152 4153 readsb                root    5u      CHR      188,0      0t0        273 /dev/ttyUSB0
readsb    4152 4154 readsb                root    5u      CHR      188,0      0t0        273 /dev/ttyUSB0
readsb    4152 4155 readsb                root    5u      CHR      188,0      0t0        273 /dev/ttyUSB0
readsb    4152 4156 readsb                root    5u      CHR      188,0      0t0        273 /dev/ttyUSB0
readsb    4152 4157 readsb                root    5u      CHR      188,0      0t0        273 /dev/ttyUSB0

root@adsb:~# sudo readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --beast-baudrate=1000000 --devel=debugSerial
invoked by: readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --beast-baudrate=1000000 --devel=debugSerial
[2024-09-16 13:53:53.487 EEST] readsb starting up.
readsb version: 3.14.1639 wiedehopf git: d0b3135 (committed: Mon Sep 16 12:29:22 2024 0200)
Running Mode-S Beast via USB.
10:53:53.504 event count 0 wait_ms 20
10:53:53.524 serial read ... fd: 0 maxbytes: 262140
<3>FATAL: removeStale() interval 60.1 seconds! Trying for an orderly shutdown as well as possible!
misc thread: threadSignalJoin timed out after 30.0 seconds, undefined behaviour may result!
upkeep thread: threadSignalJoin timed out after 15.0 seconds, undefined behaviour may result!
decode thread: threadSignalJoin timed out after 7.5 seconds, undefined behaviour may result!
<3>FATAL: thread upkeep could not be joined, calling abort()!
Aborted

Let me try newest commit

dchaplinsky commented 1 month ago

Newer build:

root@adsb:~# sudo readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --beast-baudrate=1000000 --devel=debugSerial
invoked by: readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --beast-baudrate=1000000 --devel=debugSerial
[2024-09-16 13:58:40.931 EEST] readsb starting up.
readsb version: 3.14.1639 wiedehopf git: 2a5e8b9 (committed: Mon Sep 16 12:56:14 2024 0200)
10:58:40.947 event count 0 wait_ms 0
Running Mode-S Beast via USB.
10:58:40.947 event count 0 wait_ms 0
10:58:40.947 serial: creating socket client ...
10:58:40.947 serial: creating socket client ... done
10:58:40.947 serial read ... fd: 5 maxbytes: 262140
10:58:40.947 serial read return value: 64
10:58:40.962 event count 0 wait_ms 20
10:58:40.982 serial read ... fd: 5 maxbytes: 262076
<3>FATAL: removeStale() interval 60.1 seconds! Trying for an orderly shutdown as well as possible!
misc thread: threadSignalJoin timed out after 30.0 seconds, undefined behaviour may result!
upkeep thread: threadSignalJoin timed out after 15.0 seconds, undefined behaviour may result!
decode thread: threadSignalJoin timed out after 7.5 seconds, undefined behaviour may result!
<3>FATAL: thread upkeep could not be joined, calling abort()!
Aborted

dchaplinsky commented 1 month ago

Wait! Different (default) baudrate gave me this:

root@adsb:~# sudo readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --devel=debugSerial
invoked by: readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --devel=debugSerial
[2024-09-16 14:03:11.717 EEST] readsb starting up.
readsb version: 3.14.1639 wiedehopf git: 2a5e8b9 (committed: Mon Sep 16 12:56:14 2024 0200)
11:03:11.729 event count 0 wait_ms 0
11:03:11.729 event count 0 wait_ms 0
11:03:11.729 event count 0 wait_ms 0
11:03:11.729 event count 0 wait_ms 0
11:03:11.730 event count 0 wait_ms 0
11:03:11.731 event count 0 wait_ms 0
11:03:11.731 event count 0 wait_ms 0
11:03:11.731 event count 0 wait_ms 0
11:03:11.732 event count 0 wait_ms 0
11:03:11.732 event count 0 wait_ms 0
Running Mode-S Beast via USB.
11:03:11.732 event count 0 wait_ms 0
11:03:11.733 serial: creating socket client ...
11:03:11.733 serial: creating socket client ... done
11:03:11.733 serial read ... fd: 5 maxbytes: 262140
11:03:11.733 serial read return value: 16
<3>High load: modesNetPeriodicWork() elapsed1/2/3/interval 13328/0/0/1 ms, suppressing for 5 seconds!
<3> priorityTasksRun didn't run for 13.3 seconds!
<3> removeStale didn't run for 12.3 seconds!
11:03:25.062 event count 0 wait_ms 20
*00e89072dfea05;
hex:  8fbeec   CRC: 8fbeec fixed bits: 0 decode: reject unknown hex
RSSI:    -18.6 dBFS   reduce_forward: 0
receiverId: e003af09-e8dd-77da
receiverTime:               1447605841.67us
utcTime: 11:03:11.733 epoch: 1726484591.733
DF:  0 addr: 8fbeec   VS:0 CC:0 SL:7 RI:1 AC:4210
 Short Air-Air Surveillance
  ICAO Address:  8FBEEC (mode_s)
  Air/Ground:    airborne?

11:03:25.083 serial read ... fd: 5 maxbytes: 262140

dchaplinsky commented 1 month ago

And then:

# sudo readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --devel=debugSerial
invoked by: readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --devel=debugSerial
[2024-09-16 14:03:11.717 EEST] readsb starting up.
readsb version: 3.14.1639 wiedehopf git: 2a5e8b9 (committed: Mon Sep 16 12:56:14 2024 0200)
11:03:11.729 event count 0 wait_ms 0
11:03:11.729 event count 0 wait_ms 0
11:03:11.729 event count 0 wait_ms 0
11:03:11.729 event count 0 wait_ms 0
11:03:11.730 event count 0 wait_ms 0
11:03:11.731 event count 0 wait_ms 0
11:03:11.731 event count 0 wait_ms 0
11:03:11.731 event count 0 wait_ms 0
11:03:11.732 event count 0 wait_ms 0
11:03:11.732 event count 0 wait_ms 0
Running Mode-S Beast via USB.
11:03:11.732 event count 0 wait_ms 0
11:03:11.733 serial: creating socket client ...
11:03:11.733 serial: creating socket client ... done
11:03:11.733 serial read ... fd: 5 maxbytes: 262140
11:03:11.733 serial read return value: 16
<3>High load: modesNetPeriodicWork() elapsed1/2/3/interval 13328/0/0/1 ms, suppressing for 5 seconds!
<3> priorityTasksRun didn't run for 13.3 seconds!
<3> removeStale didn't run for 12.3 seconds!
11:03:25.062 event count 0 wait_ms 20
*00e89072dfea05;
hex:  8fbeec   CRC: 8fbeec fixed bits: 0 decode: reject unknown hex
RSSI:    -18.6 dBFS   reduce_forward: 0
receiverId: e003af09-e8dd-77da
receiverTime:               1447605841.67us
utcTime: 11:03:11.733 epoch: 1726484591.733
DF:  0 addr: 8fbeec   VS:0 CC:0 SL:7 RI:1 AC:4210
 Short Air-Air Surveillance
  ICAO Address:  8FBEEC (mode_s)
  Air/Ground:    airborne?

11:03:25.083 serial read ... fd: 5 maxbytes: 262140
<3>FATAL: priorityTasksRun() interval 60.7 seconds! Trying for an orderly shutdown as well as possible!
<3>lockThreads() probably hung on decode
<3>FATAL: removeStale() interval 61.7 seconds! Trying for an orderly shutdown as well as possible!
11:03:25.083 serial read return value: 16
<3>High load: modesNetPeriodicWork() elapsed1/2/3/interval 81279/0/0/21 ms, suppressing for 5 seconds!
<3> priorityTasksRun didn't run for 81.3 seconds!
<3> removeStale didn't run for 80.3 seconds!
[2024-09-16 14:04:46.367 EEST] Abnormal exit. uptime:  0d  0h  1m 34.651s

wiedehopf commented 1 month ago

Well that's much better.

New version that hopefully doesn't block.

dchaplinsky commented 1 month ago

Ping me when you want me to do another test run.

wiedehopf commented 1 month ago

let's go ahead and do another test.

If this works, it will print a lot of info now, you can just stop it after 10 or 15 seconds and try again without --devel=debugSerial

dchaplinsky commented 1 month ago

That is with debugSerial:

root@adsb:~# sudo readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --devel=debugSerial
invoked by: readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --devel=debugSerial
[2024-09-16 15:06:18.347 EEST] readsb starting up.
readsb version: 3.14.1639 wiedehopf git: 50cc9de (committed: Mon Sep 16 13:30:59 2024 0200)
Running Mode-S Beast via USB.
12:06:18.381 event count 0 wait_ms 20
12:06:18.381 serial: creating socket client ...
12:06:18.382 serial: creating socket client ... done
12:06:18.382 serial read return value: 1148
12:06:18.402 event count 0 wait_ms 20

 Survelliance, Identity Reply
  ICAO Address:  9345D4 (mode_s)
  Air/Ground:    airborne?
  Squawk:        4330

*83046cae03b7f7ea6c36966841db;
hex:  01fc4f   CRC: 01fc4f fixed bits: 0 decode: reject unknown hex
RSSI:    -20.5 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4020866435.58us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF: 16 addr: 01fc4f   VS:0 SL:0 RI:8 AC:3246 MV:03B7F7EA6C3696
 Long Air-Air ACAS
  ICAO Address:  01FC4F (mode_s)
  Air/Ground:    airborne?
  Baro altitude:             100000 ft

*23c1eb7d3841e5;
hex:  8db015   CRC: 8db015 fixed bits: 0 decode: reject unknown hex
RSSI:    -20.2 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4044409329.42us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF:  4 addr: 8db015   FS:3 DR:24 UM:15 AC:2941
 Survelliance, Altitude Reply
  ICAO Address:  8DB015 (mode_s)
  Air/Ground:    ground

*83107b8fb80ea144164487d6db5c;
hex:  ea10a1   CRC: ea10a1 fixed bits: 0 decode: reject unknown hex
RSSI:    -19.8 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4237237568.08us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF: 16 addr: ea10a1   VS:0 SL:0 RI:0 AC:7055 MV:B80EA144164487
 Long Air-Air ACAS
  ICAO Address:  EA10A1 (mode_s)
  Air/Ground:    airborne?

*2160c59e610322;
hex:  b10dba   CRC: b10dba fixed bits: 0 decode: reject unknown hex
RSSI:    -19.8 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4272597138.08us

utcTime: 12:06:18.382 epoch: 1726488378.382
DF:  0 addr: 72ebc1   VS:0 CC:1 SL:7 RI:1 AC:2220
 Short Air-Air Surveillance
  ICAO Address:  72EBC1 (mode_s)
  Air/Ground:    airborne?

*2fdc80a713dd3c;
hex:  041bd8   CRC: 041bd8 fixed bits: 0 decode: reject unknown hex
RSSI:    -18.6 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4467545726.75us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF:  5 addr: 041bd8   FS:7 DR:27 UM:36 ID:167
 Survelliance, Identity Reply
  ICAO Address:  041BD8 (mode_s)
  Squawk:        4506

*0341cdc983f295;
hex:  401700   CRC: 401700 fixed bits: 0 decode: reject unknown hex
RSSI:    -20.5 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4545257623.50us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF:  0 addr: 401700   VS:0 CC:1 SL:2 RI:3 AC:3529
 Short Air-Air Surveillance
  ICAO Address:  401700 (mode_s)
  Air/Ground:    airborne?

*27654a515287b2;
hex:  187ac9   CRC: 187ac9 fixed bits: 0 decode: reject unknown hex
RSSI:    -20.5 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4565143913.58us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF:  4 addr: 187ac9   FS:7 DR:12 UM:42 AC:2641
 Survelliance, Altitude Reply
  ICAO Address:  187AC9 (mode_s)

*204cf854ab4328;
hex:  d01d98   CRC: d01d98 fixed bits: 0 decode: reject unknown hex
RSSI:    -19.8 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4597966393.33us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF:  4 addr: d01d98   FS:0 DR:9 UM:
  ICAO Address:  818449 (mode_s)
  Air/Ground:    airborne?
  Squawk:        4423

*06145591863bca;
hex:  c658b7   CRC: c658b7 fixed bits: 0 decode: reject unknown hex
RSSI:    -20.2 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4742735383.83us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF:  0 addr: c658b7   VS:1 CC:1 SL:0 RI:8 AC:5521
 Short Air-Air Surveillance
  ICAO Address:  C658B7 (mode_s)
  Air/Ground:    ground
  Baro altitude:              33425 ft

*054cb10f1db7a6;
hex:  9c9502   CRC: 9c9502 fixed bits: 0 decode: reject unknown hex
RSSI:    -19.5 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4771088023.67us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF:  0 addr: 9c9502   VS:1 CC:0 SL:2 RI:9 AC:4367
 Short Air-Air Surveillance
  ICAO Address:  9C9502 (mode_s)
  Air/Ground:    ground

*25236c8d16e39d;
hex:  b3a1bf   CRC: b3a1bf fixed bits: 0 decode: reject unknown hex
RSSI:    -20.2 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4772799602.42us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF:  4 addr: b3a1bf   FS:5 DR:4 UM:27 AC:3213
 Survelliance, Altitude Reply
  ICAO Address:  B3A1BF (mode_s)
  Air/Ground:    airborne?
  Baro altitude:              88500 ft

*04a67208943e33;
hex:  06350a   CRC: 06350a fixed bits: 0 decode: reject unknown hex
RSSI:    -20.5 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4843227737.83us
utcTime: 12:06:18.382 epoch:
DF:  5 addr: 00c960   FS:0 DR:13 UM:1 ID:3104
 Survelliance, Identity Reply
  ICAO Address:  00C960 (mode_s)
  Air/Ground:    airborne?
  Squawk:        1120

*0007abf00ee464;
hex:  8f43c6   CRC: 8f43c6 fixed bits: 0 decode: reject unknown hex
RSSI:    -18.0 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4934415708.50us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF:  0 addr: 8f43c6   VS:0 CC:0 SL:0 RI:15 AC:3056
 Short Air-Air Surveillance
  ICAO Address:  8F43C6 (mode_s)
  Air/Ground:    airborne?

*265f04a9fc5c25;
hex:  5d7308   CRC: 5d7308 fixed bits: 0 decode: reject unknown hex
RSSI:    -17.0 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4936592261.00us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF:  4 addr: 5d7308   FS:6 DR:11 UM:56 AC:1193
 Survelliance, Altitude Reply
  ICAO Address:  5D7308 (mode_s)
  Baro altitude:              57000 ft

*2f7039bbf269f4;
hex:  4a61b7   CRC: 4a61b7 fixed bits: 0 decode: reject unknown hex
RSSI:    -18.9 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4939787679.00us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF:  5 addr: 4a61b7   FS:7 DR:14 UM:1 ID:6587
 Survelliance, Identity Reply
  ICAO Address:  4A61B7 (mode_s)
  Squawk:        5755

*2fe1c76eeb8049;
hex:  9df08e   CRC: 9df08e fixed bits: 0 decode: reject unknown hex
RSSI:    -15.7 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4942719102.33us
utcTime: 12:06:18.382 epoch: 1726488378.382
 Survelliance, Identity Reply
  ICAO Address:  8AF1FD (mode_s)
  Squawk:        0277

*2f79d2991575f9;
hex:  1670e7   CRC: 1670e7 fixed bits: 0 decode: reject unknown hex
RSSI:    -20.2 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4948505869.92us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF:  5 addr: 1670e7   FS:7 DR:15 UM:14 ID:4761
 Survelliance, Identity Reply
  ICAO Address:  1670E7 (mode_s)
  Squawk:        6215

*2cb12578d378b8;
hex:  29b002   CRC: 29b002 fixed bits: 0 decode: reject unknown hex
RSSI:    -17.8 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4948870229.00us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF:  5 addr: 29b002   FS:4 DR:22 UM:9 ID:1400
 Survelliance, Identity Reply
  ICAO Address:  29B002 (mode_s)
  Air/Ground:    airborne?
  Squawk:        0361

*a31f2d00c1e03605457fafad48dd;
hex:  4c00ec ? CRC: 4c00ec fixed bits: 0 decode: reject unknown hex
RSSI:    -17.5 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4949890040.17us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF: 20 addr: 4c00ec ? FS:3 DR:3 UM:57 AC:3328 MB:C1E03605457FAF
 Comm-B, Altitude Reply
  Comm-B format: unknown format
  Air/Ground:    ground
  Baro altitude:              30600 ft

*2320f5db15b347;
hex:  3a6c7d   CRC: 3a6c7d fixed bits: 0 decode: reject unknown hex
RSSI:    -19.5 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4952872281.50us
utcTime: 12:06:18.382 epoch: 1726488
  ICAO Address:  AACDCE (mode_s)
  Air/Ground:    airborne?

*262f92878a7bf3;
hex:  05e460   CRC: 05e460 fixed bits: 0 decode: reject unknown hex
RSSI:    -19.5 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4967539407.83us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF:  4 addr: 05e460   FS:6 DR:5 UM:60 AC:4743
 Survelliance, Altitude Reply
  ICAO Address:  05E460 (mode_s)
  Baro altitude:              71300 ft

*2978da027cf2f5;
hex:  023e26   CRC: 023e26 fixed bits: 0 decode: reject unknown hex
RSSI:    -17.0 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4970079676.08us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF:  5 addr: 023e26   FS:1 DR:15 UM:6 ID:6658
 Survelliance, Identity Reply
  ICAO Address:  023E26 (mode_s)
  Air/Ground:    ground
  Squawk:        3410

*8545b6aaa5d012686fe26d4b7ede;
hex:  070eee   CRC: 070eee fixed bits: 0 decode: reject unknown hex
RSSI:    -18.6 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4970393930.83us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF: 16 addr: 070eee   VS:1 SL:2 RI:11 AC:5802 MV:A5D012686FE26D
 Long Air-Air ACAS
  ICAO Address:  070EEE (mode_s)
  Air/Ground:    ground
  Baro altitude:               9400 ft

*80f64a05532bf7f379abe4504846;
hex:  58499f   CRC: 58499f fixed bits: 0 decode: reject unknown hex
RSSI:    -20.2 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4971404244.42us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF: 16 addr: 58499f   VS:0
  ICAO Address:  C0B2B2 (mode_s)
  Air/Ground:    ground
  Baro altitude:             108800 ft

*032ae283be31b7;
hex:  ad690c   CRC: ad690c fixed bits: 0 decode: reject unknown hex
RSSI:    -18.6 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4984153505.08us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF:  0 addr: ad690c   VS:0 CC:1 SL:1 RI:5 AC:643
 Short Air-Air Surveillance
  ICAO Address:  AD690C (mode_s)
  Air/Ground:    airborne?

*a69880bef9c21ba79ba234efc2f4;
hex:  11ec8f ? CRC: 11ec8f fixed bits: 0 decode: reject unknown hex
RSSI:    -18.9 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4986558896.58us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF: 20 addr: 11ec8f ? FS:6 DR:19 UM:4 AC:190 MB:F9C21BA79BA234
 Comm-B, Altitude Reply
  Comm-B format: unknown format
  Baro altitude:                550 ft

*0347461e159c18;
hex:  9a5ff3   CRC: 9a5ff3 fixed bits: 0 decode: reject unknown hex
RSSI:    -18.9 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4987368147.83us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF:  0 addr: 9a5ff3   VS:0 CC:1 SL:2 RI:14 AC:1566
 Short Air-Air Surveillance
  ICAO Address:  9A5FF3 (mode_s)
  Air/Ground:    airborne?
  Baro altitude:               8950 ft

*2d1921d19ce1e7;
hex:  4d7b97   CRC: 4d7b97 fixed bits: 0 decode: reject unknown hex
RSSI:    -19.5 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4989525568.83us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF:  5 addr: 4d7b97   FS:5 DR:3 UM:9 ID:465
 Survelliance, Identity Reply
  ICAO Address:  4D7B97 (mode_s)
  Air/Ground:    airborne?
  Squawk:        4045

*8155bc04e330a9e67e22f078ce0b;
hex:  f64253   CRC: f64253 fixed bits: 0 decode: reject unknown hex
RSSI:    -14.9 dBFS   reduce_forward: 0
receiverId: 2ad03ec3-bb62-4396
receiverTime:               4993594709.83us
utcTime: 12:06:18.382 epoch: 1726488378.382
DF: 16 addr: f64253   VS:0 SL:2 RI:11 AC:7172 MV:E330A9E67E22F0
 Long Air-Air ACAS
  ICAO Address:  F64253 (mode_s)
  Air/Ground:    airborne?
  Baro altitude:              95100 ft

12:06:18.421 serial read return value: 0
Get client socket error failed.
Shutdown client socket failed.
Serial client closed unexpectedly, exiting!
12:06:18.421 event count 1 wait_ms 20
Serial client closed unexpectedly, exiting!
[2024-09-16 15:06:18.428 EEST] Abnormal exit. uptime:  0d  0h  0m 0.081s

Prints a lot indeed and then dies almost immediatelly.

With no flag it looks like this:

root@adsb:~# sudo readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0
invoked by: readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0
[2024-09-16 15:07:31.037 EEST] readsb starting up.
readsb version: 3.14.1639 wiedehopf git: 50cc9de (committed: Mon Sep 16 13:30:59 2024 0200)
Running Mode-S Beast via USB.
Get client socket error failed.
Shutdown client socket failed.
Serial client closed unexpectedly, exiting!
[2024-09-16 15:07:31.080 EEST] Abnormal exit. uptime:  0d  0h  0m 0.044s

wiedehopf commented 1 month ago

Ok so i checked the documentation and zero isn't an error condition with these settings. That should be fixed, overall this is looking promising. Give it another go.

The data you're getting looks pretty much like noise but at least it's alive.

dchaplinsky commented 1 month ago

Loud and clear! Let me try interactive mode!

Yeah, it is probably noise, as antenna is not even connected.

dchaplinsky commented 1 month ago

When in --interactive mode, does it record caught vehicles somewhere?

wiedehopf commented 1 month ago

No. It'll display them for 60 seconds.

Really you want to modify /etc/default/readsb and make sure the systemd service is working. Then use the tar1090 webinterface. (/tar1090/?pTracks by default will show you traces collected over the last 8h) Once the systemd service is running you can also install graphs1090.

Before you do that, can you run update to sid branch once more and run this:

sudo readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --quiet --stats --devel=debugSerial

Maybe 10 or 20 seconds should be enough. Just to give me some info if epoll_wait works.

dchaplinsky commented 1 month ago

Here you go:

root@adsb:~# sudo readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --quiet --stats --devel=debugSerial
invoked by: readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --quiet --stats --devel=debugSerial
[2024-09-16 17:15:12.444 EEST] readsb starting up.
readsb version: 3.14.1639 wiedehopf git: 66857d3 (committed: Mon Sep 16 15:02:37 2024 0200)
Running Mode-S Beast via USB.
14:15:12.557 serial: creating socket client ...
14:15:12.559 serial: creating socket client ... done
14:15:12.560 serial read return value: 32
14:15:12.662 serial read return value: 0
14:15:12.764 serial read return value: 0
14:15:12.866 serial read return value: 0
14:15:12.968 serial read return value: 0
14:15:13.073 serial read return value: 0
14:15:13.173 serial read return value: 0
14:15:13.274 serial read return value: 0
14:15:13.374 serial read return value: 0
14:15:13.474 serial read return value: 0
14:15:13.575 serial read return value: 0
14:15:13.675 serial read return value: 0
14:15:13.775 serial read return value: 0
14:15:13.875 serial read return value: 0
14:15:13.976 serial read return value: 0
14:15:14.076 serial read return value: 0
14:15:14.176 serial read return value: 0
14:15:14.277 serial read return value: 0
14:15:14.377 serial read return value: 0
14:15:14.477 serial read return value: 0
14:15:14.578 serial read return value: 0
14:15:14.678 serial read return value: 0
14:15:14.778 serial read return value: 0
14:15:14.879 serial read return value: 0
14:15:14.979 serial read return value: 0
14:15:15.079 serial read return value: 0
14:15:15.180 serial read return value: 0
14:15:15.280 serial read return value: 0
14:15:15.380 serial read return value: 0
14:15:15.481 serial read return value: 0
14:15:15.581 serial read return value: 0
14:15:15.681 serial read return value: 0
14:15:15.782 serial read return value: 0
14:15:15.882 serial read return value: 0
14:15:15.982 serial read return value: 0
14:15:16.083 serial read return value: 0
14:15:16.183 serial read return value: 0
14:15:16.283 serial read return value: 0
14:15:16.384 serial read return value: 0
14:15:16.484 serial read return value: 0
14:15:16.584 serial read return value: 0
14:15:16.685 serial read return value: 0
14:15:16.785 serial read return value: 0
14:15:16.885 serial read return value: 0
14:15:16.986 serial read return value: 0
14:15:17.086 serial read return value: 0
14:15:17.186 serial read return value: 0
14:15:17.287 serial read return value: 0
14:15:17.387 serial read return value: 0
14:15:17.487 serial read return value: 0
14:15:17.588 serial read return value: 0
14:15:17.688 serial read return value: 0
14:15:17.788 serial read return value: 0
14:15:17.889 serial read return value: 0
14:15:17.989 serial read return value: 0
14:15:18.089 serial read return value: 0
14:15:18.190 serial read return value: 0
14:15:18.290 serial read return value: 0
14:15:18.390 serial read return value: 0
14:15:18.491 serial read return value: 0
14:15:18.591 serial read return value: 0
14:15:18.691 serial read return value: 0
14:15:18.792 serial read return value: 0
14:15:18.892 serial read return value: 0
14:15:18.992 serial read return value: 0
14:15:19.093 serial read return value: 0
14:15:19.193 serial read return value: 0
14:15:19.293 serial read return value: 0
14:15:19.394 serial read return value: 0
14:15:19.494 serial read return value: 0
14:15:19.594 serial read return value: 0
14:15:19.695 serial read return value: 0
14:15:19.795 serial read return value: 0
14:15:19.895 serial read return value: 0
14:15:19.996 serial read return value: 0
14:15:20.096 serial read return value: 0
14:15:20.196 serial read return value: 0
14:15:20.297 serial read return value: 0
14:15:20.397 serial read return value: 0
14:15:20.497 serial read return value: 0
14:15:20.598 serial read return value: 0
14:15:20.698 serial read return value: 0
14:15:20.798 serial read return value: 0
14:15:20.899 serial read return value: 0
14:15:20.999 serial read return value: 0
14:15:21.099 serial read return value: 0
14:15:21.200 serial read return value: 0
14:15:21.300 serial read return value: 0
14:15:21.401 serial read return value: 0
14:15:21.501 serial read return value: 0
14:15:21.601 serial read return value: 0
14:15:21.702 serial read return value: 0
14:15:21.802 serial read return value: 0
14:15:21.902 serial read return value: 0
14:15:22.003 serial read return value: 0
14:15:22.103 serial read return value: 0
14:15:22.203 serial read return value: 0
14:15:22.304 serial read return value: 0
14:15:22.404 serial read return value: 0
14:15:22.504 serial read return value: 0
14:15:22.605 serial read return value: 0
14:15:22.705 serial read return value: 0
14:15:22.805 serial read return value: 0
14:15:22.906 serial read return value: 0
14:15:23.006 serial read return value: 0
14:15:23.106 serial read return value: 0
14:15:23.207 serial read return value: 0
14:15:23.307 serial read return value: 0
14:15:23.407 serial read return value: 0
14:15:23.508 serial read return value: 0
14:15:23.608 serial read return value: 0
14:15:23.708 serial read return value: 0
14:15:23.809 serial read return value: 0
14:15:23.909 serial read return value: 0
14:15:24.009 serial read return value: 0
14:15:24.110 serial read return value: 0
14:15:24.210 serial read return value: 0
14:15:24.310 serial read return value: 0
14:15:24.411 serial read return value: 0
14:15:24.511 serial read return value: 0
14:15:24.611 serial read return value: 0
14:15:24.712 serial read return value: 0
14:15:24.812 serial read return value: 0
14:15:24.912 serial read return value: 0
14:15:25.013 serial read return value: 0
14:15:25.113 serial read return value: 0
14:15:25.214 serial read return value: 0
14:15:25.314 serial read return value: 0
14:15:25.414 serial read return value: 0
14:15:25.515 serial read return value: 0
14:15:25.615 serial read return value: 0
14:15:25.715 serial read return value: 0
14:15:25.816 serial read return value: 0
14:15:25.916 serial read return value: 0
14:15:26.016 serial read return value: 0
14:15:26.117 serial read return value: 0
14:15:26.217 serial read return value: 0
14:15:26.317 serial read return value: 0
14:15:26.418 serial read return value: 0
14:15:26.518 serial read return value: 0
14:15:26.618 serial read return value: 0
14:15:26.719 serial read return value: 0
14:15:26.819 serial read return value: 0
14:15:26.919 serial read return value: 0
14:15:27.020 serial read return value: 0
14:15:27.120 serial read return value: 0
14:15:27.221 serial read return value: 0
14:15:27.321 serial read return value: 0
14:15:27.421 serial read return value: 0
14:15:27.522 serial read return value: 0
14:15:27.622 serial read return value: 0
14:15:27.722 serial read return value: 0
14:15:27.823 serial read return value: 0
14:15:27.923 serial read return value: 0
14:15:28.023 serial read return value: 0
14:15:28.124 serial read return value: 0
14:15:28.224 serial read return value: 0
14:15:28.324 serial read return value: 0
14:15:28.425 serial read return value: 0
14:15:28.525 serial read return value: 0
14:15:28.625 serial read return value: 0
14:15:28.726 serial read return value: 0
14:15:28.826 serial read return value: 0
14:15:28.926 serial read return value: 0
14:15:29.027 serial read return value: 0
14:15:29.127 serial read return value: 0
14:15:29.228 serial read return value: 0
14:15:29.328 serial read return value: 0
14:15:29.428 serial read return value: 0
14:15:29.529 serial read return value: 0
14:15:29.629 serial read return value: 0
14:15:29.729 serial read return value: 0
14:15:29.830 serial read return value: 0
14:15:29.930 serial read return value: 0
14:15:30.030 serial read return value: 0
14:15:30.131 serial read return value: 0
14:15:30.231 serial read return value: 0
14:15:30.331 serial read return value: 0
14:15:30.432 serial read return value: 0
14:15:30.532 serial read return value: 0
14:15:30.632 serial read return value: 0
14:15:30.733 serial read return value: 0
14:15:30.833 serial read return value: 0
14:15:30.933 serial read return value: 0
14:15:31.034 serial read return value: 0
14:15:31.134 serial read return value: 0
14:15:31.235 serial read return value: 0
14:15:31.335 serial read return value: 0
14:15:31.435 serial read return value: 0
14:15:31.536 serial read return value: 0
14:15:31.636 serial read return value: 0
14:15:31.736 serial read return value: 0
14:15:31.837 serial read return value: 0
14:15:31.937 serial read return value: 0
14:15:32.037 serial read return value: 0
14:15:32.138 serial read return value: 0
14:15:32.238 serial read return value: 0
14:15:32.338 serial read return value: 0
14:15:32.439 serial read return value: 0
14:15:32.539 serial read return value: 0
14:15:32.639 serial read return value: 0
14:15:32.740 serial read return value: 0
14:15:32.840 serial read return value: 0
14:15:32.940 serial read return value: 0
14:15:33.041 serial read return value: 0
14:15:33.141 serial read return value: 0
14:15:33.241 serial read return value: 0
14:15:33.342 serial read return value: 0
14:15:33.442 serial read return value: 0
14:15:33.542 serial read return value: 0
14:15:33.643 serial read return value: 0
14:15:33.743 serial read return value: 0
14:15:33.844 serial read return value: 0
14:15:33.944 serial read return value: 0
14:15:34.044 serial read return value: 0
14:15:34.145 serial read return value: 0
14:15:34.245 serial read return value: 0
14:15:34.345 serial read return value: 0
14:15:34.446 serial read return value: 0
14:15:34.546 serial read return value: 0
14:15:34.646 serial read return value: 0
14:15:34.747 serial read return value: 0
14:15:34.847 serial read return value: 0
14:15:34.947 serial read return value: 0
14:15:35.048 serial read return value: 0
14:15:35.148 serial read return value: 0
14:15:35.248 serial read return value: 0
14:15:35.349 serial read return value: 0
14:15:35.449 serial read return value: 0
14:15:35.549 serial read return value: 0
14:15:35.650 serial read return value: 0
14:15:35.750 serial read return value: 0
14:15:35.850 serial read return value: 0
14:15:35.951 serial read return value: 0
14:15:36.051 serial read return value: 0
14:15:36.151 serial read return value: 0
14:15:36.252 serial read return value: 0
14:15:36.352 serial read return value: 0
14:15:36.453 serial read return value: 0
14:15:36.553 serial read return value: 0
14:15:36.653 serial read return value: 0
14:15:36.754 serial read return value: 0
14:15:36.854 serial read return value: 0
14:15:36.954 serial read return value: 0
14:15:37.055 serial read return value: 0
14:15:37.155 serial read return value: 0
14:15:37.255 serial read return value: 0
14:15:37.356 serial read return value: 0
14:15:37.456 serial read return value: 0
14:15:37.556 serial read return value: 0
14:15:37.657 serial read return value: 0
14:15:37.757 serial read return value: 0
14:15:37.857 serial read return value: 0
14:15:37.958 serial read return value: 0
14:15:38.058 serial read return value: 0
14:15:38.158 serial read return value: 0
14:15:38.259 serial read return value: 0
14:15:38.359 serial read return value: 0
14:15:38.459 serial read return value: 0
14:15:38.560 serial read return value: 0
14:15:38.660 serial read return value: 0
14:15:38.760 serial read return value: 0
14:15:38.861 serial read return value: 0
14:15:38.961 serial read return value: 0
14:15:39.061 serial read return value: 0
14:15:39.162 serial read return value: 0
14:15:39.262 serial read return value: 0
14:15:39.363 serial read return value: 0
14:15:39.463 serial read return value: 0
14:15:39.563 serial read return value: 0
14:15:39.664 serial read return value: 0
14:15:39.764 serial read return value: 0
14:15:39.864 serial read return value: 0
14:15:39.965 serial read return value: 0
14:15:40.065 serial read return value: 0
14:15:40.165 serial read return value: 0
14:15:40.266 serial read return value: 0
14:15:40.366 serial read return value: 0
14:15:40.466 serial read return value: 0
14:15:40.567 serial read return value: 0
14:15:40.667 serial read return value: 0
14:15:40.767 serial read return value: 0
14:15:40.868 serial read return value: 0
14:15:40.968 serial read return value: 0
14:15:41.068 serial read return value: 0
14:15:41.169 serial read return value: 0
14:15:41.269 serial read return value: 0
14:15:41.370 serial read return value: 0
14:15:41.470 serial read return value: 0
14:15:41.570 serial read return value: 0
14:15:41.671 serial read return value: 0
14:15:41.771 serial read return value: 0
14:15:41.871 serial read return value: 0
14:15:41.972 serial read return value: 0
14:15:42.072 serial read return value: 0
14:15:42.172 serial read return value: 0
14:15:42.273 serial read return value: 0
14:15:42.373 serial read return value: 0
14:15:42.474 serial read return value: 0
14:15:42.574 serial read return value: 0
14:15:42.674 serial read return value: 0
14:15:42.775 serial read return value: 0
14:15:42.875 serial read return value: 0
14:15:42.975 serial read return value: 0
14:15:43.076 serial read return value: 0
14:15:43.176 serial read return value: 0
14:15:43.276 serial read return value: 0
14:15:43.377 serial read return value: 0
14:15:43.477 serial read return value: 0
14:15:43.577 serial read return value: 0
14:15:43.678 serial read return value: 0
14:15:43.778 serial read return value: 0
14:15:43.878 serial read return value: 0
14:15:43.979 serial read return value: 0
14:15:44.079 serial read return value: 0
14:15:44.179 serial read return value: 0
14:15:44.280 serial read return value: 0
14:15:44.380 serial read return value: 0
14:15:44.480 serial read return value: 0
14:15:44.581 serial read return value: 0
14:15:44.681 serial read return value: 0
14:15:44.782 serial read return value: 0
14:15:44.882 serial read return value: 0
14:15:44.982 serial read return value: 0
^C[2024-09-16 17:15:45.021 EEST] Caught SIGINT, shutting down...
14:15:45.021 event count 1 wait_ms 100
14:15:45.022 serial read return value: 0
Get client socket error failed.
Shutdown client socket failed.

Statistics: Mon Sep 16 17:15:12 2024 EEST - Mon Sep 16 17:15:45 2024 EEST
Local receiver:
  0 samples processed
  0 samples dropped
  0 samples lost
  0 Mode A/C messages received
  2 Mode-S message preambles received
    0 with bad message format or invalid CRC
    2 with unrecognized ICAO address
    0 accepted with correct CRC
    0 accepted with 1-bit error repaired
  -20.3 dBFS mean signal power
  -20.2 dBFS peak signal power
  0 messages with signal power above -3dBFS

 Phase stats
         3        4        5        6        7
         0        0        0        0        0
         4        5        6        7        8
         0        0        0        0        0

Network:
  0.000032 MBytes received
  0.000000 MBytes sent
Messages from network clients:
  0 Mode A/C messages received
  0 Mode A/C messages received
  0 Mode S messages received
    0 with bad message format or invalid CRC
    0 with unrecognized ICAO address
    0 accepted with correct CRC
    0 accepted with 1-bit error repaired
2 total usable messages
0 surface position messages received
0 airborne position messages received
0 global CPR attempts with valid positions
0 global CPR attempts with bad data
  0 global CPR attempts that failed the range check
  0 global CPR attempts that failed the speed check
0 global CPR attempts with insufficient data
0 local CPR attempts with valid positions
  0 aircraft-relative positions
  0 receiver-relative positions
0 local CPR attempts that did not produce useful positions
  0 local CPR attempts that failed the range check
  0 local CPR attempts that failed the speed check
0 CPR messages that look like transponder failures filtered
0 non-ES altitude messages from ES-equipped aircraft ignored
0 unique aircraft tracks
0 aircraft tracks where only one message was seen
CPU load: 0.2%
  0 ms for demodulation
  0 ms for reading from USB
  59 ms for network input and background tasks
[2024-09-16 17:15:45.037 EEST] Normal exit. uptime:  0d  0h  0m 32.594s

wiedehopf commented 1 month ago

Yeah that's not quite conclusive as there were no messages coming in i suppose.

Can you recompile one last time and run it for a couple of minutes, it should be less spammy now :) Not sure what you changed when it was emitting all those messages, you got an antenna connected now?

dchaplinsky commented 1 month ago

Nope, not yet. Will try it tonight, quite busy with my work now and antenna mounting require some manual intervention.

wiedehopf commented 1 month ago

It will work with the noise as well i suppose if you just leave it running for long enough.

Anyhow no rush. Think this is mostly resolved as i expect epoll_wait should work just fine. So i pushed to dev, not yet to stale.

Good day and glad i could get it fixed.

dchaplinsky commented 1 month ago

Connected the antenna and changed the service settings like this:

RECEIVER_OPTIONS="--device-type modesbeast --beast-serial=/dev/ttyUSB0"
DECODER_OPTIONS="--lat xxxx --lon xxxx --max-range 450 --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 dropped also the ppm and gain parameters which was there. ppm I think is rtlsdr only, but not sure about gain.

wiedehopf commented 1 month ago

Yeah that's good.

journalctl -u readsb -e

That looking reasonable?

/tar1090 working?

Also note you might want to remove the location just because. But it doesn't really matter i suppose.

There is also GPS spoofing / GPS jamming going on you can check https://map.adsbexchange.com/mlat-map/ https://globe.adsbexchange.com/ Now it's not known which range these receivers have, but yeah i wouldn't expect a lot of signals. Flight paths in Belarus are probably 200 nmi away from Ukraine, at least what's visible on most trackers.

dchaplinsky commented 1 month ago

I wasn't using the correct coordinates just in case, but yeah, good catch, didn't mean to post even those.

Previously I've been able to track flights in Belarus, but it was rather high floor, now I just stick antenna out of my window.

/tar1090 works good, but nothing is recorded.

dchaplinsky commented 1 month ago

24 hours so far, I think it is working, but catching nothing, which is understandable

wiedehopf commented 1 month ago

When you have time can you maybe re-run the readsb-install.sh sid and add to /etc/default/readsb with the other options:

--devel=debugSerial

And restart the service. It shouldn't spam the log too much. And the log should give me confirmation that the code is correct.

dchaplinsky commented 1 month ago

Did that, will report if anything fancy caught

dchaplinsky commented 1 month ago

I can see a lot of records like this:

Sep 18 18:42:56 adsb readsb[25507]: 15:42:56.919 event count 1 wait_ms 1000
Sep 18 18:42:56 adsb readsb[25507]: 15:42:56.919 serial read return value: 16
Sep 18 18:43:04 adsb readsb[25507]: 15:43:04.765 event count 1 wait_ms 1000
Sep 18 18:43:04 adsb readsb[25507]: 15:43:04.766 serial read return value: 16
Sep 18 18:43:04 adsb readsb[25507]: 15:43:04.845 event count 1 wait_ms 1000
Sep 18 18:43:04 adsb readsb[25507]: 15:43:04.845 serial read return value: 23
Sep 18 18:43:10 adsb readsb[25507]: 15:43:10.949 event count 1 wait_ms 1000
Sep 18 18:43:10 adsb readsb[25507]: 15:43:10.949 serial read return value: 16
Sep 18 18:43:20 adsb readsb[25507]: 15:43:20.632 event count 1 wait_ms 1000
Sep 18 18:43:20 adsb readsb[25507]: 15:43:20.632 serial read return value: 16
Sep 18 18:43:28 adsb readsb[25507]: 15:43:28.766 event count 1 wait_ms 1000
Sep 18 18:43:28 adsb readsb[25507]: 15:43:28.766 serial read return value: 16
Sep 18 18:43:28 adsb readsb[25507]: 15:43:28.893 event count 1 wait_ms 1000
Sep 18 18:43:28 adsb readsb[25507]: 15:43:28.893 serial read return value: 16
Sep 18 18:44:27 adsb readsb[25507]: 15:44:27.488 event count 1 wait_ms 1000
Sep 18 18:44:27 adsb readsb[25507]: 15:44:27.488 serial read return value: 17
Sep 18 18:44:29 adsb readsb[25507]: 15:44:29.646 event count 1 wait_ms 1000
Sep 18 18:44:29 adsb readsb[25507]: 15:44:29.646 serial read return value: 17
Sep 18 18:44:33 adsb readsb[25507]: 15:44:33.689 event count 1 wait_ms 1000
Sep 18 18:44:33 adsb readsb[25507]: 15:44:33.689 serial read return value: 16

Apparent from them:

Sep 17 23:46:20 adsb systemd[1]: Started readsb ADS-B receiver.
Sep 17 23:46:20 adsb readsb[25507]: invoked by: /usr/bin/readsb --device-type modesbeast --beast-serial=/dev/ttyUSB0 --devel=debugSerial --lat xxxxx --lon xxxxxx --max-range 450 --write-json-every 1 --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-location-accuracy 2 --range-outline-hours 24 --write-json /run/readsb --quiet
Sep 17 23:46:20 adsb readsb[25507]: [2024-09-17 23:46:20.659 EEST] readsb starting up.
Sep 17 23:46:20 adsb readsb[25507]: readsb version: 3.14.1640 wiedehopf git: 4b18685 (committed: Mon Sep 16 17:11:25 2024 0200)
Sep 17 23:46:20 adsb readsb[25507]: Using lat: xxxxxx, lon: xxxxxx
Sep 17 23:46:20 adsb readsb[25507]: 30002: Raw TCP output port
Sep 17 23:46:20 adsb readsb[25507]: Running Mode-S Beast via USB.
Sep 17 23:46:20 adsb readsb[25507]: 30005: Beast TCP output port
Sep 17 23:46:20 adsb readsb[25507]: 30003: SBS TCP output ALL port
Sep 17 23:46:20 adsb readsb[25507]: 30001: Raw TCP input port
Sep 17 23:46:20 adsb readsb[25507]: 30004: Beast TCP input port
Sep 17 23:46:20 adsb readsb[25507]: 30104: Beast TCP input port
Sep 17 23:46:21 adsb readsb[25507]: 20:46:21.682 serial: creating socket client ...
Sep 17 23:46:21 adsb readsb[25507]: 20:46:21.682 serial: creating socket client ... done

wiedehopf commented 1 month ago

Thank you that pretty much confirms that epoll_wait is working fine, really no reason it would not i suppose.

Appreciate sticking with it taking the time to fix this. (i pretty obviously broke this at some point ... oh well)

dchaplinsky commented 1 month ago

Thanks for your time and patience!

wiedehopf / readsb

readsb with mode-s beast problem #21