I ran my K3 with the K3IOB upgrade card installed. I also have a P3 and set it to a 10 KHz span. Before, when I used the line out as an input to Fldigi, it seemed like there was a little more tolerance in how I tuned in on the space signal. Now, I notice that the K3 decodes text when I get reasonably close to the space signal, but Fldigi still needs a little more finagling to get it decoding at all. I may be back to using the Xonar sound card and cables unless I can establish a more consistent tuning procedure on the RTTY signals. vy 73,Dave N4KD
On Monday, February 15, 2016 12:22 AM, Rick Prather <[email protected]> wrote: I used RUMlogNG for WPX and it worked very well. My set up though is a bit different than your's I think. I use the K3 set to FSK D and cocoaModem as a back up. I tune the signals using my P3 set to about 15 Khz span and tune to the Right (space) signal. The only repeats I needed to give didn't surprise me since I am running only 100W to a wire. I found that cocoaModem was slightly better at decoding but most of my decodeing and therefore grabbing call signs, etc. was from the RUMlogNG display with cocoaModem used mostly as an occasional backup. Interestingly enough, I found a few situations, especially on weak and/or fluttery signals, where the K3 did a much better job of decoding than cocoaModem. I also spent some time running FLDIGI on the side but found it was not nearly as good as cocoaModem or the K3 in decoding. Rick K6LE ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [email protected]
