In simple terms:

AFSK A is LSB, AFSK TX filter (MENU: AFSK TX) is available and
controlled by PITCH (Mark), audio input uses data selection.
TX and RX EQ are disabled.  Receive dual tone (dual peak) filter
is available.  Frequency (VFO) display reflects *MARK*

DATA A is USB, AFSK TX filter is not available, default center
frequency is set by FC (shift), audio input uses data selection,
TX and RX EQ are disabled.  Receive dual tone filter (dual peak)
filter is not available. Frequency (VFO) display reflects *carrier*.

73,

   ... Joe, W4TV


On 2014-07-16 10:03 AM, David Cole wrote:
Hi all,

What EXACTLY is the difference between "AFSK A", and "DATA A".

Here is why I ask:

In AFSK A Mode:
While using MixW, and looking at the MixW screen, and in USB on the K3,
as I tune using the knob, the MixW screen shows the signal stuck to a
frequency on the top calibration marks on MixW.  The signal never moves
from the frequency indicated on the MixW software in the waterfall.

In DATA A Mode:
All settings the same with the exception of switching from AFSK A to
DATA A.  The signal moves relative to the frequency marks on MixW.  i.e.
if the signal started at 14.0000, as I tune the knob, MixW tracks the
frequency, moving the scale above the waterfall, while the signal
appears to move independently of the waterfall calibration marks...

I have tried REV sideband on the K3, and the same thing still
happens...

Is there a resource I can read telling me EXACTLY what each data mode
does?  I have KE7X's book, and that does not explain why I am seeing
what I am seeing...  At least not to me...  I am putting my macros
together, and need to get my head around EXACTLY what the two modes do,
as they set up the radio.


______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected]

Reply via email to