Assuming you are using FSK keying,  MMTTY should be set to Com3 since WinKey is the device that is keying your rig.   Try that first. Rich

Is it a K3 or K3S? I use AFSK with my K3S. TX is set at none, Misc. is set at Sound, and Sound card is set at USB audio codec in the MMTTY program. In the K3S use AFSK A for the data mode and VOX

Hey all: I'd like to get a hold of a XV432 transverter. Elecraft discontinued it awhile back, and it looks like the international distributors are out of stock as well. Thanks/73 Steve KL7SB

I am running a K3s and trying to set up MMTTY using WIN 10 OS without success. (I had it working once) My device manager shows that Com 3, Com 9 and Com198 available. Regardless which com port I use

Tnx to all who replied. I now have a better idea of I need to move forward. Jeff W7JW

I have a Top Ten Devices Band Aide decoder picking up band data from the AUX/ACC connector (15 pin D-Sub) on my K3. I use the internal jumper pad in the Band Aide so that multiple bands select the

See Ad in QTH.com. All gear is in excellent condition and operated in a smoke free environment. Joe W7UV

I can't see how mike gain has anything to do with using a bug on CW mode. In SSB operation the ALC and / or Speech Processor does have an attack time of a defined small number. It can be that

For the P3 problem you might try changing the setting of "TX SensEn" in the TX Monitor menu.  This changes the method by which the P3 switches between transmit and receive mode: either by RS-232

Hello again Don. What I forgot to mention is: I use QSK. The weird stuff only happened in QSK and I did not experience it in semi auto delayed break. de Mike K8NS

I am just guessing, so take it for whatever it is worth. One problem with high speed digital is key bounce. It is sometimes so fast that it is a pain to catch and fix. You are using a system that

Don, the K3 seem to not like a bug. With my K3S i use always a bug (a Vibroplex Presentation or a Begali Intrepid). In the past, when keying with the bug, the K3 displey become blank and

Hello Don. I have a K3s, P3, KPA500 combo and also use bugs, I have experienced some strange things, as u did. My fix was to insert either my bug descratcher (Jackson Harbor Press) or my old MFJ

Bob, I have a peak reading meter on the output of my K3, with the output set at 60 watts. I will see some peaks at 70. Some people think it has to do with how hard you drive the mic gain. I haven't

Best way to take care of RF problems is to use Common Chokes. I use them at the antenna feed point, before entering the house and if need at the rig. I make mine using FT240-43 cores with 17 turns of

I would check for warm PL-259 connectors. Make sure to snug them with 4" Channel lock pliers. Finger tight is not good enough. And any PL-259 which is warm along with the coax jumper is suspect.

Jeff, I use an SM-8 band decoder and a 2 x 8 antenna switch by Hamation (available via Array Solutions) to switch my antennas remotely. The band decoder has two modes -- Auto and Manual. In auto

Don, Regarding your number 3: I recently experienced problems with my KPA1500 tripping on a high reflected power fault on 160 meters. To assist in my troubleshooting process I modified my freeware

I have had three instances of unexplained events, using a Bug key with the K3s. I am 100 % cw and only use a bug. My speed is about 26-27 wpm on the key. 1. Event one: I added the TXMON to

I built my own - a remote Raspberry Pi controller that uses 4 of its GPIO ports for BCD band decoding, and SainSmart relays for antenna control. A Windows console communicates with the Raspberry Pi