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.
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
David,
AFSK A is optimized for use with RTTY. It defaults to LSB and the
frequency displayed is the frequency of the Mark tone. The latter
feature does not make too much sense to me when using a waterfall
display, but it makes a lot of sense when using narrow filters and
tuning to a RTTY
Joe,
Is there something else that might explain the actions of the signal in
the waterfall of MixW?
I have tried DATA A in REV sideband, (I thought that would fix the
issue), and the signal does not stay pinned to the same frequency under
the MixW calibration marks... As I tune up, MixW moves
*I don't use MixW* but it sounds like MixW is in the wrong sideband.
73,
... Joe, W4TV
On 2014-07-16 10:54 AM, David Cole wrote:
Joe,
Is there something else that might explain the actions of the signal in
the waterfall of MixW?
I have tried DATA A in REV sideband, (I thought that would
Hi Joe,
I was thinking that as well, but MixW is using USB. As a test I
reversed the sideband by pressing the mode until I saw REV pop up. I
would have expected that to correct the issue if the software were on
the wrong sideband, but it just makes it fail the opposite
direction...
My belief
looks like the mixw pdf help file(s)
MixW 2.19 Help File by Scott Hill, K6IX
http://k6ix.net/MixW.html
is more complete than the one found in the actual mixw 2.20 pgm
On 7/16/2014 1:57 PM, Joe Subich, W4TV wrote:
*I don't use MixW* but it sounds like MixW is in the wrong sideband.
73,
It's been quite a few years since I used MixW, but here goes:
1. Last time I tried it, MixW did not understand the K3's digital
sub-modes. Basically it acted as if they were all the same (either FSK D
or AFSK A), i.e. on LSB. Even when I put the rig in DATA A, MixW still
acted as though the
8 matches
Mail list logo