I hadn't seen anyone that had successfully installed dl-fldigi on the Pi, so I figured I would go with fldigi for this system.I’ve recently introduced a Raspberry PI 4 as main remote RTX controller for my Kenwood TS-590s. That would be awesome if you could post a guide once you get it figured out! The main reason I went with using plain fldigi was that I saw a few people saying that they had installed it on the Pi. If/When I have success I'll try and write it up on the ukhas wiki. I have got most of the way towards getting dl-fldigi compiled on a Pi, I just need to solve the last library issues and hope there's a balloon flight to test with. Plain fldigi will give you a decent fall back, but it might be worth trying to get dl-fldigi working as well. You should also be able to integrate a GPS and have it show your position as well (useful if you've got someone back at base following progress and also good for the community). It also means you won't get the auto-configurtion, direction and distance or let you upload data online - so no landing data on the map which can be useful for you and anyone else. All we really need are the GPS coordinates so that we can recover the balloon. We're using fldigi for this system since we don't need features such a SSDV since we are using this simply as a tracking system once the HAB hits the ground. If you havn't found it already there's an active irc channel #highaltitude on freenode where you might find some help, and lots of tips that will help your flight a success. It's something I've been meaning to try out.

(The original Pi1 wasn't powerful enough to run it). I'm not sure if anyone has tried dl-fldigi on a Pi2/Pi3 although I see no reason for it to not work. Quick point to make, fldigi and dl-fldigi are subtly different things the subtle difference being that dl-fldigi has the extensions needed for HAB (I'm assuming the fldigi above is just a typo). So I was wondering if anyone might have any suggestions for fixing this? Or if there is some sort of incompatibility between RTTY, fldigi, and the raspberry pi 3? But when it gets plugged back into the pi, fldigi on the pi cannot decode, even though all the RTTY settings are the same across the pi and my PC. When I unplug the radio from the pi and plug it into my PC, fldigi can decode everything just fine. We were getting a waterfall from the radio, the issue is that it will not decode the RTTY data coming in.

So I was able to get fldigi on the pi and it seemed to be working. With this success we thought it would be cool to use a raspberry pi to perform this decoding, making the whole system more portable. We were running dl-fldigi on the laptop to do the decoding, but we also performed successful tests with fldigi. We were able to get this working and we were able to decode the data on a laptop connected to the radio with a Signalink USB. The Pi in the Sky board is broadcasting telemetry data at 434 MHz which we then receive with a Yaesu FT-817 radio. I'm working on a high altitude balloon project using a raspberry pi and a Pi in the Sky board.

Raspberry pi 3 fldigi