-
Notifications
You must be signed in to change notification settings - Fork 314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dw stops collecting packets after 2-6 hrs, needs restart #183
Comments
We need more details about your setup. What version of Raspbian? Is it fully patched? Which version of Direwolf? What version of rtl_fm? You should be running the newest of all of these to really be able to help you as no one else has reported an issue like this. When you start Direwolf, where are you sending the logs? Can you send a tgz of the logs lines from the transition when it's working to when it starts to fail? Can you also start Direwolf with the strace command and log to a USB pen drive or something large and send us just some examples of the longs when it's failed? You'll have to prune that file WAY back as it will be extremely huge. --David |
Thank you David for the reply. The only thing I could find out myself was the version of Raspbian? version 9 (Stretch). As for patch level, Direwolf and rtf_fm version, I couldn't find a way on the net on how to extract the information. Yves vk2auj |
When you start Direwolf, it will print out it's version to STDOUT. If you're redirecting that output to a log file, look in there. As for the rtl_fm program, that's not clear to me. I have an old version here.. 0.5.2 which doesn't have a command line option to give the version nor does it seem to be found using the "strings" program. How did you install it? If you installed it via a package, you can run "dpkg -l | grep -i rtl" and see if it's listed there. |
David. Hold on ... it was suggested it could be a PSU issue, so I've disconnected the TV and USB dongle for wireless keyboard and will let it running to test. I'll also try to find a 3amp PSU. |
After investigations, it appeared that the RTL dongle was getting too hot and one of the processor was probably shutting itself off. By simply removing the dongle from the metal case, I was a able to do an uninterrupted run of 28hrs, and then 40hrs and still running after relocating to its permanent location. I'll try to design a heatsink for the regulator and the 2 main chips of the RTL dongle. |
Which RTL dongle do you have? Instead of trying to retrofit something that probably won't go well, buy something better. On the lower end, consider say something like: https://www.nooelec.com/store/sdr/sdr-receivers/nesdr/nesdr-smart-sdr.html Or if you want something with a LOT better receiver, no DC spike, and full open sourced software, try: #The mini supports a 6Mhz passband, the v2 supports a 10Mhz passband --David |
Wow.. that's a pretty massive heat sink but I think you're investing way too much money into cheap, low performance SDRs. Consider looking at better units like Airspy, etc. and while they might also have issues with high temps, your time investment to cool them off will be more worth it. :-) Anyway, I think you've demonstrated that your issue isn't with Direwolf so please close this issue |
All working fine in the first 2 to 6 hrs after startup, then eventually, dw still beaconing but packets are not longer collected and/or sent to the internet.
A workaround for now is a timer that shuts down the device for 1 min every hour.
Raspberry PI 3, wifi, RTL dongle.
See attached a ps- al done:
The text was updated successfully, but these errors were encountered: