search

jvde-github / AIS-catcher

AIS receiver for RTL SDR dongles, Airspy R2, Airspy Mini, Airspy HF+, HackRF, SDRplay and SoapySDR
https://aiscatcher.org
GNU General Public License v3.0
468 stars 76 forks source link

New problem, hardware related? #174

Closed tkreyche closed 11 months ago

tkreyche commented 11 months ago

Jasper, I've been running on the same hardware for months. The web site cannot be accessed and data is no longer sent out. If I just restart AIS-Catcher it starts working again just fine...no indication of hardware problem, although that what it seems like

It started showing up a month or so ago, and now I've seen it more frequently. It's happened with the last few versions of AIS-Catcher. I can try swapping out my Pi for a different one. I've running with the same Airspy HF+ Discovery and only have one of them.

See ouput below. Any suggestions?

thanks, Tom Kreyche

pi@raspberrypi:~ $ AIS-catcher -C config.json -p 1 -v 60 -o 0 -go AFC_WIDE off AIS-catcher (build Sep 11 2023) v0.53-2-g0302208c (C) Copyright 2021-2023 jvde-github and other contributors This is free software; see the source for copying conditions.There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. UDP: open socket for host: 5.9.207.224, port: 5943, filter: OFF, JSON: OFF UDP: open socket for host: 144.76.105.244, port: 2261, filter: OFF, JSON: OFF UDP: open socket for host: 54.204.25.151, port: 7127, filter: OFF, JSON: OFF UDP: open socket for host: 195.201.71.220, port: 6233, filter: OFF, JSON: OFF UDP: open socket for host: hub.shipxplorer.com, port: 36081, filter: OFF, JSON: OFF Server: reading statistics from stat.bin TCP Server: start thread at port 8100 HTML Server running at port 8100 Server: starting backup service every 10 minutes. Device : AIRSPYHF Settings : rate 192K freqoffset 1.000000 format CF32 preamp OFF threshold LOW Model #0 -> (Src: 1, Grp: 1): [AIS engine v0.50] ps_ema ON afc_wide OFF droop ON fp_ds OFF dsk OFF [AIS engine v0.50 #0-0] received: 378 msgs, total: 378 msgs, rate: 6.29522 msg/s [AIS engine v0.50 #0-0] received: 330 msgs, total: 708 msgs, rate: 5.49825 msg/s [AIS engine v0.50 #0-0] received: 370 msgs, total: 1078 msgs, rate: 6.16469 msg/s [AIS engine v0.50 #0-0] received: 377 msgs, total: 1455 msgs, rate: 6.28129 msg/s [AIS engine v0.50 #0-0] received: 365 msgs, total: 1820 msgs, rate: 6.08134 msg/s [AIS engine v0.50 #0-0] received: 373 msgs, total: 2193 msgs, rate: 6.21491 msg/s ... [AIS engine v0.50 #0-0] received: 328 msgs, total: 101917 msgs, rate: 5.46501 msg/s [AIS engine v0.50 #0-0] received: 304 msgs, total: 102221 msgs, rate: 5.06524 msg/s Server: initiate backup. Server: writing statistics to file stat.bin [AIS engine v0.50 #0-0] received: 323 msgs, total: 102544 msgs, rate: 5.38146 msg/s [AIS engine v0.50 #0-0] received: 305 msgs, total: 102849 msgs, rate: 5.08173 msg/s [AIS engine v0.50 #0-0] received: 337 msgs, total: 103186 msgs, rate: 5.61511 msg/s

[AIS engine v0.50 #0-0] total: 103277 msgs Server: writing statistics to file stat.bin Server: stopping backup service. TCP Server: thread ending. UDP: close socket for host: 5.9.207.224, port: 5943 UDP: close socket for host: 144.76.105.244, port: 2261 UDP: close socket for host: 54.204.25.151, port: 7127 UDP: close socket for host: 195.201.71.220, port: 6233 UDP: close socket for host: hub.shipxplorer.com, port: 36081

jvde-github commented 11 months ago

Tom, thanks for checking.

The log you share shows that the program ends gracefully without a message. The question is what has triggered this event

I had a look at the code for the airspy HF+ and it checks with the core driver whether the device is still running (ie connected and streaming), and if not, stops the program. Key thing is that in this case there does not seem to be a message printed.

So if that is the case, it might be a hardware issue, for example with the USB port, power supply fluctuation, the HF+ or the cable.

I have added an extra message to the program: "AIRSPYHF: device stopped streaming.". This is printed if the program stops itself because the connection with the dongle is lost as per check with the native driver.

I will give it another think if there are other program exits without printing a reason. Thanks for sharing. Hope the above fix gives us some direction to see if it is hardware or software.

Please let me know if it happens again with the above fix.

Thanks for flagging, Jasper

ps 1 you might want to edit out your ports in the log fragment (or just delete the log now you shared). ps 2 you can check the message in case of a hardware issue by unplugging the device and see how the program responds.

tkreyche commented 11 months ago

Turned out to be an easy problem diagnosis...the Airspy just died completely...replace it with a v3 SDR-RTL dongle for now