Raspberry and FR24 problems

[alexis_maria]

Good evening:

I have a raspberry pi4 that has started giving me intermittent problems a few months ago. When I connect my raspberry to monitor I see the following image.

WhatsApp Image 2022-05-16 at 2.05.46 AM.jpeg

Can you help me?. Looking at FR24 I know that this card has software 1.0.29.8

Since I have 2 raspberries, when I use the Pi 2 with the new card everything works fine. On the new card I have a V 1.0.28.1

[wiedehopf]

Most likely issue is insufficient power or an SDR that is going bad.

But the fr24 logs are hard to deal with, i'd recommend getting readsb and graphs1090 linked here: https://github.com/wiedehopf/adsb-wi...ADS-B-receiver


Otherwise ... the page you show already has a show logs action .... that seems like a good place to start.

[alexis_maria]

Most likely issue is insufficient power or an SDR that is going bad.

But the fr24 logs are hard to deal with, i'd recommend getting readsb and graphs1090 linked here: https://github.com/wiedehopf/adsb-wi...ADS-B-receiver


Otherwise ... the page you show already has a show logs action .... that seems like a good place to start.

with the other raspberry and new microsd, same rtl is perfect.

I'm going to try what you tell me

be patient with me I'm very new

[alexis_maria]

THANK´S

FR24 Feeder Logs
< Newer Older >
2022-05-16 03:02:28 | [main][i]Terminating child process 655 with SIGTERM
2022-05-16 03:02:28 | [reader][i]Connection terminated
2022-05-16 03:02:28 | [reader][i]Configured, processing messages
2022-05-16 03:02:28 | [reader][i]Connected to the receiver, configuring
2022-05-16 03:02:28 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw --mlat)
2022-05-16 03:02:23 | [main][i]Terminating child process 653 with SIGTERM
2022-05-16 03:02:23 | [reader][i]Connection terminated
2022-05-16 03:02:23 | [reader][i]Configured, processing messages
2022-05-16 03:02:23 | [reader][i]Connected to the receiver, configuring
2022-05-16 03:02:23 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw --mlat)
2022-05-16 03:02:17 | [feed][n]working
2022-05-16 03:02:17 | [feed][n]connected via TCP (fd 31)
2022-05-16 03:02:17 | [main][i]Terminating child process 651 with SIGTERM
2022-05-16 03:02:17 | [reader][i]Connection terminated
2022-05-16 03:02:17 | [reader][i]Configured, processing messages
2022-05-16 03:02:17 | [reader][i]Connected to the receiver, configuring
2022-05-16 03:02:17 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw --mlat)
2022-05-16 03:02:12 | [main][i]Terminating child process 649 with SIGTERM
2022-05-16 03:02:12 | [reader][i]Connection terminated
2022-05-16 03:02:12 | [reader][i]Configured, processing messages
2022-05-16 03:02:12 | [reader][i]Connected to the receiver, configuring
2022-05-16 03:02:12 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw --mlat)
2022-05-16 03:02:06 | [main][i]Terminating child process 647 with SIGTERM
2022-05-16 03:02:06 | [reader][i]Connection terminated
2022-05-16 03:02:06 | [reader][i]Configured, processing messages
2022-05-16 03:02:06 | [reader][i]Connected to the receiver, configuring
2022-05-16 03:02:06 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw --mlat)
2022-05-16 03:02:01 | [main][i]Terminating child process 645 with SIGTERM
2022-05-16 03:02:01 | [reader][i]Connection terminated
2022-05-16 03:02:01 | [reader][i]Configured, processing messages
2022-05-16 03:02:01 | [reader][i]Connected to the receiver, configuring
2022-05-16 03:02:01 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw --mlat)
2022-05-16 03:01:57 | [feed][n]connecting
2022-05-16 03:01:57 | [feed][n]**********
2022-05-16 03:01:57 | info | Network thread connecting to ***********
2022-05-16 03:01:57 | info | Configured ReceiverACSender: ********, send_interval: 5s/1s, max age: 15s, send metadata: true, mode: 1, filtering: true
2022-05-16 03:01:57 | info | Stopping ReceiverACSender threads for feed
2022-05-16 03:01:57 | info | [stats]Stats thread started
2022-05-16 03:01:57 | [feed][c]Timestamps: optional
2022-05-16 03:01:57 | [feed][i]defined 3 servers
2022-05-16 03:01:57 | [feed][i]configuration changed
2022-05-16 03:01:57 | [feed][c]Max range GND: 100.0nm
2022-05-16 03:01:57 | [feed][c]Max range AIR: 350.0nm
2022-05-16 03:01:57 | [feed][i]configuring decoder
2022-05-16 03:01:56 | [feed][d]fetching configuration
2022-05-16 03:01:56 | [feed][i]Downloading configuration
2022-05-16 03:01:56 | [main][i]Feed Network client started
2022-05-16 03:01:56 | [time][i]Time synchronized correctly, offset -0.002 seconds
2022-05-16 03:01:56 | [time][i]Synchronizing time via NTP
2022-05-16 03:01:55 | [main][i]Terminating child process 636 with SIGTERM
2022-05-16 03:01:55 | [reader][i]Connection terminated
2022-05-16 03:01:55 | [reader][i]Configured, processing messages
2022-05-16 03:01:55 | [reader][i]Connected to the receiver, configuring
2022-05-16 03:01:55 | [mlat][i]Waiting for MLAT configuration
2022-05-16 03:01:55 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw --mlat)
2022-05-16 03:01:55 | [reader][i]Initializing reader
2022-05-16 03:01:55 | [main][i]MLAT data feed started
2022-05-16 03:01:55 | [master][i]Starting processing thread
2022-05-16 03:01:55 | [main][i]Reader thread started
2022-05-16 03:01:55 | [d]TLSConnection::ctor(): Enable verify_peer in production code!
2022-05-16 03:01:55 | [i]PacketSenderConfiguration::fetch_config(): Yoda configuration for this receiver is disabled
2022-05-16 03:01:55 | info | [httpd]Server started, listening on :::8754
2022-05-16 03:01:55 | ERROR: rmmod: ERROR: Module dvb_usb_rtl28xxu is not currently loaded
2022-05-16 03:01:55 | [main][i]Automatic updates are ENABLED
2022-05-16 03:01:55 | [main][i]DNS mode: PING
2022-05-16 03:01:55 | [main][i]https://www.flightradar24.com
2022-05-16 03:01:55 | [main][i]Copyright 2012-2022 Flightradar24 AB
2022-05-16 03:01:55 | [main][i]Local IP(s): 192.168.1.79
2022-05-16 03:01:55 | [main][i]Running on: pi24-raspbian10
2022-05-16 03:01:55 | [main][i]Built on Feb 2 2022 12:34:09 (HEAD-2331de4.git/Linux/static_armel)
2022-05-16 03:01:55 | [main][i]Version: 1.0.29-8/generic
2022-05-16 03:01:55 | [main][i]FR24 Feeder/Decoder
2022-05-16 03:01:55 | |___/
2022-05-16 03:01:55 | __/ |
2022-05-16 03:01:55 | \_| |_||_| \__, ||_| |_| \__||_| \__,_| \__,_| \__,_||_| \_____/ |_/
2022-05-16 03:01:55 | | | | || || (_| || | | || |_ | | | (_| || (_| || (_| || | ./ /___\___ |
2022-05-16 03:01:55 | | _| | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / / / /_| |
2022-05-16 03:01:55 | | |_ | | _ __ _ | |__ | |_ _ __ __ _ __| | __ _ _ __`' / /' / /| |
2022-05-16 03:01:55 | | ___|| |(_) | | | | | | / __ \ / |
2022-05-16 03:01:55 | ______ _ _ _ _ _ _____ ___

[wiedehopf]

Yeah the log is completely unusable, install readsb / graphs1090 to have some actually useful logs to look at.


This command will indicate if you have power supply issues, check it:
sudo dmesg --ctime | grep voltage

[alexis_maria]

Yeah the log is completely unusable, install readsb / graphs1090 to have some actually useful logs to look at.


This command will indicate if you have power supply issues, check it:
sudo dmesg --ctime | grep voltage

good morning:

-bash: voltaje: command not found

i,m going to install readsb/graphs1090

thank´s

[wiedehopf]

Seems you didn't type that command correctly, it would be best to copy / paste the entire line. (if you don't know how to paste into putty, google it)

Once you have installed readsb, check the log: https://github.com/wiedehopf/adsb-sc...-check-the-log

[alexis_maria]

I have installed what you told me. I get this

May 16 11:37:57 raspberrypi readsb[3293]: Using lat: 28.2114, lon: -14.0226
May 16 11:37:57 raspberrypi readsb[3293]: 30002: Raw TCP output port 30005: Beast TCP output port rtlsdr: no supported devices found.
May 16 11:37:57 raspberrypi readsb[3293]: Mon May 16 11:37:57 2022 BST sdrOpen() failed, exiting!
May 16 11:37:57 raspberrypi readsb[3293]: 30003: SBS TCP output ALL port 30001: Raw TCP input port
May 16 11:37:57 raspberrypi readsb[3293]: 30004: Beast TCP input port 30104: Beast TCP input port
May 16 11:37:57 raspberrypi readsb[3293]: Mon May 16 11:37:57 2022 BST Abnormal exit.
May 16 11:37:57 raspberrypi systemd[1]: readsb.service: Main process exited, code=exited, status=1/FAILURE
May 16 11:37:57 raspberrypi systemd[1]: readsb.service: Failed with result 'exit-code'.

that was without having the SDR connected


when i connect it it looks like this

May 16 11:42:26 raspberrypi systemd[1]: readsb.service: Scheduled restart job, restart counter is at 3.
May 16 11:42:26 raspberrypi systemd[1]: Stopped readsb ADS-B receiver.
May 16 11:42:26 raspberrypi systemd[1]: Started readsb ADS-B receiver.
May 16 11:42:26 raspberrypi readsb[1511]: Mon May 16 11:42:26 2022 BST readsb starting up.
May 16 11:42:26 raspberrypi readsb[1511]: readsb version: wiedehopf git: e29d835 (committed: Sun Apr 24 09:51:04 2022 0200)
May 16 11:42:26 raspberrypi readsb[1511]: Using lat: 28.2114, lon: -14.0226
May 16 11:42:26 raspberrypi readsb[1511]: 30002: Raw TCP output port 30005: Beast TCP output port rtlsdr: no supported devices found.
May 16 11:42:26 raspberrypi readsb[1511]: Mon May 16 11:42:26 2022 BST sdrOpen() failed, exiting!
May 16 11:42:26 raspberrypi readsb[1511]: 30003: SBS TCP output ALL port 30001: Raw TCP input port
May 16 11:42:26 raspberrypi readsb[1511]: 30004: Beast TCP input port 30104: Beast TCP input port
May 16 11:42:26 raspberrypi readsb[1511]: Mon May 16 11:42:26 2022 BST Abnormal exit.
May 16 11:42:26 raspberrypi systemd[1]: readsb.service: Main process exited, code=exited, status=1/FAILURE
May 16 11:42:26 raspberrypi systemd[1]: readsb.service: Failed with result 'exit-code'.

[wiedehopf]

rtlsdr: no supported devices found.

Yeah the SDR is dead.

[alexis_maria]

rtlsdr: no supported devices found.

Yeah the SDR is dead.

okay. I put that same sdr in the other raspberry and it's perfect

[wiedehopf]

That could mean the USB on the pi is the problem or possibly insufficient voltage.
Already posted the command to check for the voltage, run it and don't mistype or use copy paste.

Or it could be that the SDR is degrading and with full voltage it's still running but not at all with lower voltage.
Try different USB ports / try a different SDR on that pi.

[alexis_maria]

That could mean the USB on the pi is the problem or possibly insufficient voltage.
Already posted the command to check for the voltage, run it and don't mistype or use copy paste.

Or it could be that the SDR is degrading and with full voltage it's still running but not at all with lower voltage.
Try different USB ports / try a different SDR on that pi.

pi@raspberrypi:~ $ sudo dmesg --ctime | grep voltage
pi@raspberrypi:~ $


I'm sorry, I'm boring you today

[wiedehopf]

No that's fine, no output means the power should be fine.

Have you tried all the ports? Sounds like the USB on the pi (making the pi a bit useless) might have failed somehow if it's not the SDR.
You could try connecting an USB stick and chekc if you find it in
lsusb
Just check
lsusb
before and after plugging a USB device in.

I doubt that's the issue but you could always try and install a current Raspbian image from scratch:

https://github.com/wiedehopf/adsb-wiki/wiki/Raspbian-Lite:-ADS-B-receiver

[alexis_maria]

Now that you mention it, before my keyboard and mouse didn't recognize me. I do not know if it would be the cause that the usb did not work.

Day ago when it started to fail me it was suddenly blocked and when I restarted the SDR worked again

I'm going to reload the image from 0, I already did it 2 or 3 times today to see what I get. The thing is that since it doesn't recognize my keyboard/mouse, I can't continue except through the network.

[wiedehopf]

Yeah that sounds like the RPi isn't working correctly, not sure you can really do anything.
The pi might just be a lost cause in regards to USB.
Try all the ports though.