search

F5OEO / rpitx

RF transmitter for Raspberry Pi
GNU General Public License v3.0
4.02k stars 531 forks source link

Rpitx keeps crashing my PI #165

Closed Slayingripper closed 1 year ago

Slayingripper commented 5 years ago

first time i run Rpitx it was working fine but after a 2nd restart it started freezing the pi making me have to force restart it .

phantomdennis commented 5 years ago

I am having the same issue, I can run NFM for about 1 minutes, anything else and it crashes the PI. The PI 2B is crashing as soon as I start transmitting.

I checked and the PI is only pulling .34mA so I do not think it is not a power issue.

NicholasBlackburn1 commented 5 years ago

did you try reinstalling the rpitx software

phantomdennis commented 5 years ago

I removed it and cloned the git again and the same result. Is there something special I need to do to remove the installation beyond removing the directory?

r1bnc commented 5 years ago

Mine crashes after transmitting POCSAG, can you play some music with mplayer then use rpitx. Mine says "Audio device got stuck" and I am unable to play music until I rebooted the Pi.

Hysteria1212 commented 5 years ago

Hi,

did you overclock your raspi? I had this problem with my raspberry pi 1 when using the maximum cpu clock.

Am Mo., 29. Apr. 2019 um 22:58 Uhr schrieb gr01d notifications@github.com:

Mine crashes after transmitting POCSAG, can you play some music with mplayer then use rpitx. Mine says "Audio device got stuck" and I am unable to play music until I rebooted the Pi.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/F5OEO/rpitx/issues/165#issuecomment-487741395, or mute the thread https://github.com/notifications/unsubscribe-auth/AGATUSRQXPVHBHU46XUMFPLPS5OPTANCNFSM4G6RYTGA .

phantomdennis commented 5 years ago

I do not overclock my pi. It says 250Mhz when the rpitx finishes installing. I did re-install. I ran these tests both over SSH (which disconnects when the transmissions start) and from the terminal in front of the device. I rebooted between tests and found this:

~/rpitx$ ./easytune.sh

I leave the default frequency: 434.0 Tune - Screen immediately turns off and the system fails - the signal stays up at a low power until the pi is turned off Chirp - Screen immediately turns off and the system fails - the signal pops up and starts to move for about 2 seconds then stops and the signal stays at one frequency with low power until the pi is rebooted. Spectrum - Nothing happens - The system fails and nothing is transmitted. RfMyFace - I did not try this, I do not have a camera installed. FMRDS - Screen immediately turns off and the system fails - the signal pops up lasts about 3 seconds then turns off. NFM - Screen immediately turns off and the system fails - the signal pops up and stays up until the pi is rebooted. When spanned all the way in on the signal there is frequency modulation. But when tuned on the radio it sounds like a demon breathing. SSB - Screen immediately turns off and the system fails - Then a small signal pops up. I cannot demod SSB at the moment but there is a signal.

~$./rpitx/easytune.sh - The menus pop up, I press transmit, it says transmitting, but there is no RF. IT does not fail, the pi does not reboot.

Update I downloaded stretch again and started fresh on a new SD card. The pi transmits all but the spectrum paint function. The spectrum paint does not transmit at all, but they system does not fail. It just does not do anything.

dachshund-digital commented 4 years ago

Same for me on buster, RPiTx and buster combo, kills my Pi ZeroW.

r1bnc commented 4 years ago

Mine works now, it is Rpi 3B+ with the current buster updated to latest packages. The/boot/config.txthas the gpu_freq=250. The only problem is if you are streaming music with mplayer, the music stops when you use rpitx. Debug log shows audio device got stuck errors. A full reboot will restore the music playing capability of the pi.

dachshund-digital commented 4 years ago

I also finally got only an older 3B, not even a 3B+, with buster working randomly... It still fails more often than not. I am explicitly using sendiq to emulate RF remote signals. I often have to run the same sendiq command 3 to 10 times, sometimes more, to actually get any transmission broadcast. Looking at the code a bit, it is not clear where the issue is, because the software does so little error reporting, and has no verbose mode. Although I have written software in C, I have never done it on Linux, only on Windows and Macintosh OSes. Walking though the code suggests since the sendiq program is not reporting any errors, it might be the transmit buffer is corrupted, so the signal plays incorrectly, randomly. Or some error is being encountered that is just never being reported. I suspect what happens, depends on only on the OS distribution but also the make/model of Pi.

Fattcat commented 1 year ago

For me still get freezed whenever I start transmitting freq for example tune or fmrds it just transmit and it freezing my RPi4 model B with 8GB ram memory. And stuck it.

Jibun-no-Kage commented 1 year ago

RPiTx was fun while it lasted. But clearly it is done, either because the newer hardware just does not have the ability to support the idea, or the desire to resolve the issues with it and the Pi 4 are not present. It has for me only worked so-so on a Pi Zero as well. Can't get a Pi Zero 2, so can't test that as yet either.

The truth is, RPiTx was taking advantage of a flexibility in the device that was never part of the design. I finally just got a USB SDR module, and use that for most of what I used RPiTx for. The only thing that bugs me is that no one seems to want to create a breakout board that explicitly supports 303.875 MHz, which is what a lot of my remotes use. You can find 433 MHz break out boards all over the place on the net, but not 303.875 MHz.