Using fldigi as a voice keyer
Hi folks. I would like to configure fl didi to seve as a voice keyer
Just installed fldigi-3.23.10_i386 on my Mac running OS X El Capitan.
Open fldigi-3.23.10. The application starts but is not responding.
73 de Jose (KP4FMD)
I've been using FLDIGI with an ICOM 7200 direct USB connection and Linux OS in a portable Go box.
The last time I set everything up at home after a field trip with the gear, there has been a dark band in the waterall a hundred KHz wide on all frequencies. Before I start trial and error from scratch tracking down the source of this issue, any thoughts what might be causing it? I'm guessing something in a connection has filtere d the center of the frequency. Anybody seen this before?
I'm working on a high altitude balloon project using a Raspberry Pi and a Pi in the Sky board. The Pi in the Sky board is broadcasting telemetry data at 434 MHz which we then receive with a Yaesu FT-817 radio. 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. We were running dl-fldigi on the laptop to do the decoding, but we also performed successful tests with fldigi.
With this success we thought it would be cool to use a Raspberry Pi to perform this decoding, making the whole system more portable. So I was able to get fldigi on the Pi and it seemed to be working. We were getting a waterfall from the radio, the issue is that it will not decode the RTTY data com ing in. The text that we are getting is just gibberish. When I unplug the radio from the Pi and plug it into my PC, fldigi can decode everything just fine. But when it's plugged into the Pi, fldigi on the Pi cannot decode, even though all the RTTY settings are the same across both the Pi and my PC. I have tried reversing the signal using the Rv button, as well as changing my squelch setting but neither of these seem to have any effect.
As a further test I set up Direwolf on the Raspberry Pi, because our high altitude balloon setup also transmits APRS packets. With the same radio and the signalink connected to the Pi I was able to receive and decode APRS packets. So I think the issue must be in some setting I have wrong in fldigi or possibly an incompatibility between the Raspberry Pi 3 and fldigi. I am really at a loss for what the issue could be, since we are getting the input from the radio to fldigi, and fldigi is configured with the same settings for RTTY decoding on the Pi as it is on my PC. Any help you can provide would be greatly appreciated.