Mike,

 From what you are  saying here, I think you are not tuning fine enough. 
   Going from 14.085 to 14.085.5  may be  too wide a jump.   I don't 
know your rig or how fine you can set the tuning.  You need to get this 
down to the smallest increment you can..   The fact that you can grab 
some text is a good sign.   When you stop tuning  on a signal and the 
text goes back to garbage, you need to go back ever so slightly, but if 
your tuning step is too wide, you  will jump over it..

There are 2 different scopes on MMTTY. A x-y scope and a ft scope.   You 
really need to read the docs on these.   Use one or the other, which 
ever one she is more comfortable with.  When I had some sight, I used 
the FT type scope.   There are either 1 or 2 vertical lines on the 
scope.   As you tune across the signal you will see 2  peaks come into 
view.    If I rememver right, you need to line the tip of the peak(s) 
with the  vertical line(s).   I think the xy scope has some lines that 
will cross when tuned, but it's been a long time.  Read the docs.  There 
are menu settings for width, sensitivity, etc. for the scopes.  I hate 
to say it again, but read the docs. If she can help you by using the 
scope, it will make it easier for you to know what to listen for and how 
to tune by ear.

BTW,  after being ticked off about not having mine working for WPX and 
the back and forth e- mails on rtty, I tried to get mine working on 
Monday.  Still have some problems, but monday night while looking for a 
rtty signal to  try and tune on 20 meters, I heard the TJ9PF operation 
from Cameroon.   Too good to pass up, so I jumped into the pile and 
worked him.

Good luck, I think you've almost got it.

On 2/16/2011 9:07 AM, Michael Ryan wrote:
> Hi all:=20
> I'm still struggling with decoding RTTY signals and its not going well.=20=
>
> I've got everything narrowed down as tight as I can get it and I'm =
> slowly tuning across RTTY signals, some of which are vary strong, 59 and =
> higher.=20
> I tried both Jaws and Window Eyes and didn't find a difference in how =
> the scrolling text was presented and as I'm more acquainted with WE, =
> decided to stick with that and set the reader to speak all to listen to =
> the scrolling gibberish. =20
> I did manage to hit pieces of QSOs in english and when I did, =
> immediately stopped tuning. However, once the text was read and a new =
> piece of data was received, it would be back to gibberish and I wouldn't =
> try and fine tune.=20
> I use MTTY and I don't know if I'm supposed to have the scope on the =
> screen, didn't make a difference in the gibberish when turned it off and =
> as well, I got my XYL to assist me and she didn't know what to look for =
> while I was tuning except the english of course. Are there supposed to =
> be any indicators that I could tell my XYL to line up for me?=20
> As well, are there any spoken clews to listen out for?  I mainly fine =
> tune across the signals and the gibberish doesn't change to english for =
> the most part.=20
> Mostly fluke that I managed to get pieces thus far. Example: I'd tune =
> from 14.085 to 14.086 in probably .05 increments. IE: one tap of my up =
> arrow would give me a freq of 14.08505. =20
> I do have my interface set properly for receive, no overflows.  Filter =
> setting of my rig: Narrows filter engaged, about 2.4KHZ I'm guessing, IF =
> Shift 2 -1000 which I'm thinking takes 1000 from that thus give me 1.4. =20=
>
>
> 73:=20
>
> Michael De VO1RYN=20
>