RTTY
[Top] [All Lists]

Re: [RTTY] RTTY DX'ing tutorial (was: VK0EK RTTY Update)

To: <rtty@contesting.com>
Subject: Re: [RTTY] RTTY DX'ing tutorial (was: VK0EK RTTY Update)
From: "WW3S" <ww3s@zoominternet.net>
Date: Sun, 10 Apr 2016 19:00:33 -0400
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>
you were not , LOL !!!!!! and accidents happen, been there myself.....but when 
the same station does it over and over again, thats no accident......on my 
FT-2000 I reverse the vfos to find the qsx.......takes some getting used to , 
especially if your fingers are as fat as mine....

> On 4/10/2016 6:50:11 PM, Art (K5FNQ) (k5fnq@lusfiber.net) wrote:
> > OK group (and hopefully I was not the K5### that WW3S wrote about - I 
> never do that other than the few times that NAP3 automatically reset my 
> split as off but that was another dxpedition and I am embarrassed over 
> it) - anyway as to RTTY and split opreation am I not using the software 
> correctly (MMTY) to find the calling station being worked by the DX?
> 
> On a DXpedition RTTY split mode, unlike CW where it is possible to 
> listen for and read the frequency of the calling station being worked, 
> RTTY on split does not provide that option to print the station on VFOB, 
> at least not that I can see.  No way to print from VFOB to try and find 
> the station being worked.  It becomes a crapshoot (using NAP3 and LP PAN 
> to try and see the signal of the RTTY station being worked is impossible 
> with the "call all of the time" crowd.)  Is there any way around this?
> 
> Hopefully I have overlooked some command or system to read both VFOA and 
> VFOB on my FT5000 on any RTTY program???
> 
> Art K5FNQ
> 
> 
> On 4/10/2016 15:29, Don Hill AA5AU wrote:
> > Jamie wrote: " Don AA5AU is an accomplished web author, I havent checked 
> > his site, but that would be a good place to start with
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty

<Prev in Thread] Current Thread [Next in Thread>