I have seen several different people make suggestions (often the same ones others have suggested) but I have not seen anyone with a similar setup tell what their experience is. I do have a similar setup but am not currently living near home due to temporary work location. I will be home over the weekend and will try to duplicate the issue. I have always used FSK when running RTTY but use DATA A of course when using FT modes so I have no comparison until I try AFSK in RTTY. K3 is currently boxed up since returning from a portable op, so will attempt to find time to set it all back up and give AFSK a try. (Why do we call it "wireless"?)
On Fri, Mar 20, 2020 at 8:06 PM <[email protected]> wrote: > Joe, > Have you selected LINE-IN in the MIC-SEL config-menu? > 73 Gernot DF5RF > > Am 20.03.2020 um 13:40 schrieb Joe N9OK: > > I've reached out to Elecraft Tech Support on this issue. With their > locale > > on lockdown, I think they have their hands full just trying to maintain > > some sense of normalcy. So I'm hoping someone here can point me in the > > right direction. > > > > I've recently upgraded my K3 with numerous "last time buy" options (KAT3A > > antenna tuner, 2 KSUN3A synthesizers, and KIO3B usb board). One goal was > to > > remove the Microkeyer II and simplifying the setup. > > > > What I'm finding now is that I can't make RTTY work correctly. I use > MMTTY > > to generate a simple warble signal, which is sent to my K3. The K3 is set > > to AFSK-A, VOX enable, audio levels set correctly. What happens is that > the > > K3 TX LED illuminates, but nothing is heard with the Monitor (ie, thru > the > > K3 speaker), and there is no RF transmitted. However, when I use DATA-A, > I > > do hear tones using Monitor, and there is RF power. > > > > I get the same results using either the K3 internal sound card, or > > externally-generated audio (fed from my PC soundcard to Line-In on the > K3). > > > > Hoping there was a configuration issue, I factory reset my K3. That > didn't > > help. > > > > It's probable this issue has been there since I first purchased my K3 > new 8 > > years ago, but I never noticed. My MKII was used as my interface, and I > was > > running FSK for RTTY. I did have many configuration issues with my MKII > > setup, which in retrospect might well be related to the AFSK issue that's > > now obvious. > > > > I'm suspecting this is a hardware issue. I have the 59 pages of > schematics, > > and am going thru them to see if I can identify the issue so I can fix > it. > > I would appreciate comments / suggestions / ideas to point me in the > right > > direction. > > > > 73, Joe N9OK > > > > 73, Joe N9OK > > ______________________________________________________________ > > 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] > ______________________________________________________________ > 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] > -- Jim K0XU [email protected] ______________________________________________________________ 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]
