Another thing to check:
In your sound devices find the signalink USB codecs and open the playback
mixer. The slider needs to be at 100all the way to the top.
Also, there are jumpers in the SL. One is for low output or high output.
Make sure the jumpers are set to the high positions.
Be very careful ... Signalink USB lacks sufficient bypassing on
the internal 5V distribution, lacks regulation on the CODEC and
op-amp V/2 reference, and lacks sufficient filtering on the USB
power line.
Most sound card show increased distortion with Playback gain above
80%. Cranking the audio
Understood...thanks.
I had a similar problem when I first got a SL USB. The manufacturer said
the slider must be at max and then use the front panel pot and radio line
in control to manage the desired audio level. When I did that I was able
to get the desired output. I did not mean to crank
The manufacturer said the slider must be at max and then use the
front panel pot and radio line in control to manage the desired audio
level.
The problem is that when the Windows slider is at max the USB CODEC is
running rail to rail on its output. With the improper filtering and
lack of
I didn't read the op so I'll add on here.
Make sure that the transmit mark frequency is the same as the receive
frequency. I've been bitten by this several times. I like to use lower tones
(915) because I listen to the incoming signal and the high tone drives me nuts.
MMTTY defaults to
On Tue,10/14/2014 5:17 AM, Wes (N7WS) wrote:
I like to use lower tones (915) because I listen to the incoming
signal and the high tone drives me nuts. MMTTY defaults to 2125. If
you use profiles then it's best to edit the .ini file directly and set
these.
I do the same, and for the same
Thanks for all the inputs on my question.I have made some progress. I changed
the K3 mode from AFSK to Data A, and in MMTTY haveRev selected. I am now upon
TX getting power out, movement on the ALC meter (4 bars with 5th flickering,
mic line set at 31) and hearing Diddles. So MMTTY is working
Also as I understand it Signalink does AFSK, so why
does it appear to be working in DATA A. Does the Data A mode
selection have something to do with the reduced power out?
AFSK A has a very narrow *transmit* filter on the Mark/Space tones to
prevent distortion and hum. If the MARK in MMTTY
I do the same, and for the same reason. But it's not only the .ini
file that must be edited -- there's another file that defines the
various decoder settings that can be selected from a pull-down menu
or cycled through.
userpara.ini - it only comes into play if one uses the Profiles (S)
menu.
Paul,
There are subtle differences between DATA A and AFSK A. You may want to
review the K3 manual section on data modes for additional information.
First, DATA A sets the K3 to USB mode by default where AFSK A uses LSB
by default.
DATA A can transmit and receive anywhere within the audio
/MMTTY/Signalink Problem
Paul,
There are subtle differences between DATA A and AFSK A. You may want to
review the K3 manual section on data modes for additional information.
First, DATA A sets the K3 to USB mode by default where AFSK A uses LSB by
default.
DATA A can transmit and receive
Paul,
I fear there is something in your setup between the K3 and MMTTY that is
causing your problems.
In addition to the K3 manual, review the MMTTY help file to see if you
can discover what that may be.
We can only guess about what your problem may be - what I can say is
that if the tones
On Tue,10/14/2014 2:56 PM, paul ecker via Elecraft wrote:
But the question remains, if I set K3 mode to AFSK I get no power out or no
Diddles. With Data A I do get power out and Diddles. Why is that ??
One possibility is that MMTTY and the radio are set to different tones.
Another is that
It is an .ini file... userpara.ini :-)
On 10/14/2014 9:26 AM, Jim Brown wrote:
On Tue,10/14/2014 5:17 AM, Wes (N7WS) wrote:
I like to use lower tones (915) because I listen to the incoming signal and
the high tone drives me nuts. MMTTY defaults to 2125. If you use profiles
then it's best to
On Tue,10/14/2014 10:16 PM, Wes (N7WS) wrote:
It is an .ini file... userpara.ini :-)
That sounds familiar. Thanks, Wes.
73, Jim
__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help:
I am having problems getting MMTTY to transmitproperly using K3 with a
Signalink USB interface.
Currently, when I go to TX in MMTTY, I get red TXlight on Signalink, a red TX
light on K3, I hear diddles coming out of theSignalink rear monitor jack, and
I seemovement on Vu meter in Windows
Hi Paul,
Although I do not use MMTTY , the fact that you have the lights and TX on the
k3 working suggests that the ptt function (or VOX) is correct.
The fact that all of the other software is working suggests that something
related to the sound card settings in MMTTY is incorrect. Perhaps it
Paul,
How many bars are being illuminated on the K3 ALC meter? If you do not
have 4 bars illuminated with the 5th bar flickering, you do not have
enough audio drive.
If you are using the K3 Line In, you will have to set the SignaLink for
high audio output (see the SL instructions).
The K3
18 matches
Mail list logo
