AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Fldigi on raspberry pi9/8/2023 If you do an internet search for "Raspberry Pi PSK31" you will get a few results, most of which bemoan the Raspberry Pi's lack of processor power for running " Fldigi" which is probably the most popular Linux application for PSK31. The possibility of using the Raspberry Pi for operating PSK31 has intrigued me because it would offer a low cost, low power, silent and potentially mobile station setup - the only other alternative is to use a desktop or laptop computer. To do this requires an audio input to and output from the Raspberry Pi (see my previous post) and a suitable application to encode and decode the PSK31 signal, as well as a radio transceiver and antenna. This keeps it simple and repeatable.As I mentioned in my last post, I am a radio amateur and I'm interested in using the Raspberry Pi to operate using various digital modes, including PSK31. At the moment, I have a couple of bare wires that I short to start PTT, which I want to connect to a (or 6 as appropriate) that I would like to trigger with RTS.Īnyone have some idea how to set this up? The reason I am wanting to use RTS is so that ANY Ham software can operate PTT by using the "serial port" RTS line. This particular radio has no line in/out, not any sort of data interface, so I must assert PTT by shorting the SLEEVE and RING on the microphone input jack. Not that I am NOT using a signal link, but am using the cmedia audio USB adaptor and directly coupling the audio in/out to the radio (5-watt X1M) which likes the levels very well. As such I cannot assign RTS nor CTS to one of the GPIO pins. I installed bw_tools and the git programs but I cannot use gpio_? as the system tells me it is not installed. I am successfully using then Raspberry Pi model 2 with both fldigi and qsstv but I still need to get PTT working. I added the singalink explicitly as a device listed in /etc/nf. I tried a million things, but I think I know what fixed it. I wasn't getting any signal in fldigi, no waterfall. I fired up fldigi and could suddenly select port audio devices - and my signalink was in there as the USB Audio CODEC as a playback and capture device. So I installed the portaudio packages and recompiled fldigi with portaudio support (your working package probably has this already). But once I got it loaded, I saw I couldn't select any devices in the soundcard config.Īfter reading the fldigi linux recommendations I figured using the portaudio library on top of ALSA was the way to go. If the package loads for you I'm jealous. I had to add a bunch of packages as you'd expect but finally it compiled and worked. The fldigi package didn't fire up for me, I'm not sure why, so I ended up compiling it from source. Turns out I got it working and never had the capture device show in alsamixer so that was no biggie. I don't see a capture device in alsamixer though, and that's freaking me out. The program 'alsamixer' is showing both cards, and I can select between them. The internal soundcard does not have a capture device, so just card 1 is showing up. Code: Select all 0 : BRCM bcm2835 ALSbcm2835 ALSA - bcm2835 ALSAīurr-Brown from TI USB Audio CODEC at usb-bcm2708_usb-1.3, full speed
0 Comments
Read More
Leave a Reply. |