[Elecraft] K3s not transmitting AFSK
Here I am in the middle of WAE RTTY, and suddenly my K3s is not transmitting RF on AFSK A. Here's my configuration: * Built-in USB sound card * N1MM+ with MMTTY engine * MODE is set to DATA * DATA MD set to AFSK A * PWR is set to 100W * LCD and MMTTY decode RTTY signals correctly * TEST mode is off Everything was working perfectly five hours ago when I turned off the rig. Now I turned on the rig again and launched N1MM+. If I press F4 (my call) the transmitter keys (TX light is on) and produces RTTY tones that I hear and that MMTTY decodes and displays. But no RF comes out of the rig. The RF meter has one bar at 0. Does anyone have any idea what's going on? Should I reload the firmware? Thanks --- Mike N4CF __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] K3s not transmitting AFSK
It's all working now, and I can't explain why. Rich VE3KI sent me a suggestion off-list to try the Windows 10 Sound Control Panel. The ONLY thing I did there was select the USB CODEC, check that the playback level was not 0, and click the Test Device button. That produced a few tones, and the K3 produced 100W into a dummy load in the DATA mode, just as it should. I launched N1MM with the Digital window open, and pressing F4 sent my call, and the K3 again produced RF. So I switched back to the Carolina Windom antenna and worked LA1TV on 15M with the KPA500 pumping out 300W. Bottom line: The K3 was not producing RF in DATA mode when I started this morning, then produced RF after I tested the USB CODEC in Sound Control Panel. I have no clue why. Thanks again to everyone who offered advice. --- 73, Mike N4CF Louisa County, VA USA Elecraft K3s / P3 / KPA500 / KAT500 Carolina Windom up 45' http://n4cf.mdodd.com __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] K3s not transmitting AFSK
Yes, Windows 10 is wonderful at keeping our blood pressure up. On Sun, Nov 14, 2021 at 12:14 PM Mike Dodd wrote: > It's all working now, and I can't explain why. > > Rich VE3KI sent me a suggestion off-list to try the Windows 10 Sound > Control Panel. > > The ONLY thing I did there was select the USB CODEC, check that the > playback level was not 0, and click the Test Device button. That > produced a few tones, and the K3 produced 100W into a dummy load in the > DATA mode, just as it should. > > I launched N1MM with the Digital window open, and pressing F4 sent my > call, and the K3 again produced RF. > > So I switched back to the Carolina Windom antenna and worked LA1TV on > 15M with the KPA500 pumping out 300W. > > Bottom line: The K3 was not producing RF in DATA mode when I started > this morning, then produced RF after I tested the USB CODEC in Sound > Control Panel. I have no clue why. > > Thanks again to everyone who offered advice. > > --- > 73, Mike N4CF > Louisa County, VA USA > Elecraft K3s / P3 / KPA500 / KAT500 > Carolina Windom up 45' > http://n4cf.mdodd.com > > __ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:Elecraft@mailman.qth.net > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to jimk...@gmail.com > -- Jim K0XU j...@rhodesend.net __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
