[Elecraft] Sending AFSK RTTY--FIXED

Joe Subich, W4TV lists at subich.com
Thu Mar 21 15:52:15 EDT 2019


On 2019-03-21 1:52 PM, Peter Dougherty wrote:
 > 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?

Yes, the K3/KIO3B or K3S USB Audio CODEC behaves exactly like the K3
with analog Line In/Line Out.  The USB Audio CODEC is essentially
"grafted on" to the Line In/Line Out.  In fact "Speaker (USB AUDIO
CODEC)" is connected in parallel with the analog Line Out jack.

Please refer to the K3S Owners Manual and the K3S schematic package
on-line.

> I seem to have all the functionality I had previously with the 
 > MicroKeyer-II in line

Not by a long shot ... you no longer have a hardware based FSK, a
K1EL WinKey keyer, support for multiple CAT connections (for syncing
an external SDR panadapter), the ability to mute the microphone when
playing an SSB voice file, access to dedicated CI-V and/or SteppIR
control channel, etc.  While you may not have used all those features
you certainly do not have the same functionality as you had with the
microKEYER II.

73,

    ... Joe, W4TV


On 2019-03-21 1:52 PM, Peter Dougherty wrote:
> 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
> 



More information about the Elecraft mailing list