[SECC] SECC Digest, Vol 165, Issue 37

[Michael Zolno]

Hi Jeff,

I cannot not speak to the K3, as I have an ICOM. I am fairly certain all these add-on boxes rig blaster, signalink, etc are AFSK where the audio tones are injected into the microphone at 200Hz spacing. My understanding of this setup and any audio injected RTTY is that it is dependent on software timing. 

I use a simple transistor switch as related on Don, AA5AU site and his rttycontesting.com site. This is hardware dependent and is FSK where audio tones is AFSK. I know this wont help today, unless you can solder up a resistor, 2N2222 in a db9 connector pretty quick.

For software I use the MMTTY, 2Tone and GRITTY, only MMTTY transmits and requires the plug-in extfsk.dll download from the MMTTY site or rttycontesting.com; save t MMTTY directory. Gritty is RX only but works well where folks stepping on each other garble transmission. Install MMTTY to its own directory of C:\ and install 2Tone there as well. In N1MM, I setup the Digital Interface (DI) by pointing to the install directory and once running, MMTTY opens automatically when you open and RTTY contest log. This setup allows you to run up to 4 decode windows at once and with GRTTY you can tailor the RX algorithm separately per RX window. This works FB for me, though I am no RTTY expert. 

Hit me back with anything.

73 Mike WH6YH

Sent from my iPad

> On Sep 25, 2016, at 12:00 PM, secc-request at contesting.com wrote:
> 
> Send SECC mailing list submissions to
>    secc at contesting.com
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>    http://lists.contesting.com/mailman/listinfo/secc
> or, via email, send a message with subject or body 'help' to
>    secc-request at contesting.com
> 
> You can reach the person managing the list at
>    secc-owner at contesting.com
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of SECC digest..."
> 
> 
> Today's Topics:
> 
>   1. RTTY Help (Jeffrey Clarke)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Sun, 25 Sep 2016 03:14:28 +0000 (UTC)
> From: Jeffrey Clarke <ku8e at bellsouth.net>
> To: "secc at contesting.com" <secc at contesting.com>
> Subject: [SECC] RTTY Help
> Message-ID: <912503400.4192504.1474773268273 at mail.yahoo.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Hi,
> Playing in CQWW RTTY this weekend and need some help setting up my RTTY interface. Right now I'm using the CW to RTTY function on my Elecraft K3. It's kind of a pain to send with the CW paddle all the time. Plus I can't seem to get the 4 second delay after ending a transmission to go away. The only way I have found to get around this is to program the CW memories in the K3 and send by pushing those buttons. If you program a "|" in the CW memory it disables the 4 second delay in the CT to RTTY mode. For some reason when I send "IM" with the paddle it's not disabling the delay like it should.
> I have a Rigblaster Advantage I've been just using for sending CW from the computer. I've unhooked the cable that goes from my computer the to the? RS232 on the back - The one you use to do updates to a K3 - and have plugged in the RS232 from the Rigblaster to the K3 RS232 and it works fine doing radio control and sending CW. I also have a cable going from the headphone jack ?of the K3 to the Line IN of the Rigblaster. I know I'm getting audio to the Rigblaster because I hear it when I hookup my headphones to the speaker out.
> For some reason when I start MMTTY or N1MM I can't seem to receive or transmit RTTY. Can someone help? Am I missing something?
> Thanks, ?Jeff
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.contesting.com/pipermail/secc/attachments/20160925/760fd99b/attachment-0001.html>
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> SECC mailing list
> SECC at contesting.com
> http://lists.contesting.com/mailman/listinfo/secc
> 
> 
> ------------------------------
> 
> End of SECC Digest, Vol 165, Issue 37
> *************************************