Sam,
You are doing it right.
DATA A mode is like SSB with the following exceptions:
1) TX EQ is disabled in DATA A mode
2) Audio compression is disabled in DATA A mode.
3) one can set the audio input to LINE IN for DATA A mode - no need to
change it from MIC audio when using data modes.
Either of those conditions may be present in SSB mode, and the first 2
will distort a data mode signal. So the answer is to use DATA A mode
instead of SSB so you do not have to manually turn off those 2
conditions when running data modes in SSB mode.
Unfortunately, some data mode software does not include recognition of
the K3/KX3 DATA A mode and will force the rig to SSB mode. Be watchful
of that condition and respond accordingly.
The K3 offers a seamless solution to the use of both SSB and Data modes
and is beneficial as long as you do not have to "fight" with the data
mode software application to get that to happen.
73,
Don W3FPR
On 3/16/2015 8:43 PM, Sam Morgan wrote:
I have been running DATA A with my SignaLink USB for JT65 & JT9 using
WSJT-X. However I am now having some problems (interfacing with other
rig control software) that are making me question why I settled on
DATA A rather than USB?
Other than the fact DATA A inherently eliminates all potential audio
settings that might cause problems if USB was used, which seems like a
big plus to me.
Are there any other reasons why DATA A is preferred for the data modes?
I have run DATA A successfully for at least 5-6 years and being a
creature of habit, I hate to switch to USB unless I am forced to.
Anyone have convincing arguments pro or con about this question I am
willing to hear them.
P.S.
I also use DATA A with Fldigi for PSK/RTTY/Olivia/etc
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com
