[Elecraft] Sending AFSK RTTY--FIXED

[Peter Dougherty]

Hi all,
Just a quick note to thank everybody here for their suggestions and help. There were some things in the K3s that needed to be changed, but that still left some serious issues that were definitely related to DX Labs WinWarbler. 

DX Labs works by storing app settings in the registry, and the registry settings for all related apps are stored in a “workspace.” Somehow the settings for WinWarbler had gotten corrupted. On a whim, I restored an old known-good workspace, changed the parameters to the new hardware configuration and after a couple of bumpy starts, everything worked fine. I saved a new workspace with these settings, and then I went back to the original profile, and it remained screwed up. Once again I shut everything down, loaded the new profile that I’d just created and it’s all good. The bad profile has now been deleted off the system and all is once again right.

I would definitely like to thank Barry, K3NDM for helping me out one-on-one, ironing out the needed K3s settings, and getting RTTY working in FLDIGI and N1MM (proving this was a DX Labs problem).

FOUR DAYS to get this done, but at least now, with very limited testing, I seem to have all the functionality I had previously with the MicroKeyer-II in line—but without the extra cabling, risk of RF ingress, and multiple virtual COM ports. 

Again, a big thank you to everybody who lent a hand to this. One final question, does the USB audio connection from the K3s separate out the main and sub receiver audio in the same manner as using a physical audio breakout cable two and 3.5mm plugs? I would like to have a second instance of MMTTY set up to receive the sub RX audio, with the primary using only the main VFO. I used to be able to accomplish this using left- and right-channels in the MMTTY setup, but that doesn’t seem to work using USB. Not a major issue now that FT8 Dxpedition Mode seems to be all the rage, but I would still like to have this functionality if possible.

 

- pjd