[RTTY] afsk vs fsk spotting

[Mike]

Hello Art,

You are right about the AFSK off-set, it happens unless the S/W has a 
means of correcting for the off-set.   MixW2 has a place to set in 
the off-set.  Writelog doesn't.  Those are the two programs I'm familiar with.

I use AFSK with a 1 KHz off-set so I can use my narrow 
filters.  MixW2 automatically computes a 1 KHz offset and that is 
what is used in all the spots, etc.  WL using MMTTY, to my knowledge, 
doesn't have a place to enter the off-set.

At 12:56 PM 9/22/2007, Art Searle W2NRA wrote:
>Hi Bill,
>
>If ops configure AFSK or FSK properly there would be no difference.
>Unfortunately AFSKers often don't!
>
>73 Art W2NRA
>"Keep to the Code!"
>w2nra.com
>----- Original Message -----
>From: "FireBrick" <w9ol at billnjudy.com>
>To: "RTTY List" <rtty at contesting.com>
>Sent: Saturday, September 22, 2007 12:33 PM
>Subject: [RTTY] afsk vs fsk spotting
>
>
> > It was quite evident that many many afsk users were in the hunt for 3B7C
> > on
> > 40 rtty last night.
> >
> > I am 'mathamatically challenge' but didn't need to resort to a calculator
> > to
> > interpret cluster spots.
> >
> > Listening to the first cluster spot freq a few moments and hearing
> > 'nuttin'
> > I adjusted 2.1 and found a signal.
> >
> > I would like to remind others though, when you adjust vfoA for the
> > difference between an afsk spot and fsk use and vice versa, you need to
> > adjust vfoB the same way.
> >
> > When the dx station say 'up 2' and you don't remember that effects vfoB
> > also....well you may have a tough time working them....
> >
> > -----------------------------------------------------
> > "Sects, sects, sects!  That's all you religion majors ever think about."
> > -----------------------------------------------------
> >
> > Bill H. in Chicagoland
> > webcams at http://76.16.160.118:8080/
> > weather at http://hhweather.webhop.org
>_______________________________________________
>RTTY mailing list
>RTTY at contesting.com
>http://lists.contesting.com/mailman/listinfo/rtty

         73,
         Mike, K4GMH