K-Line on digital modes

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

K-Line on digital modes

Elecraft mailing list
I have a full K-line setup (K3, P3, KPA500, KAT500) and I've been trying
to get the K3 working on digital modes.  I can't seem to get it to
transmit.  Using the K3 Utility, I can verify the K3 at a particular com
port.  Firmware updates work fine.  I can read PSK in terminal mode.  
But, when I click on the transmit button, the K3 doesn't switch to
transmit.  I have the PTT menu option set to DTR and, in fact tried
every variation of DTR and RTS with no difference.  I have tried both
FTDI USB-to-Serial adapters and a genuine, built-in serial port - all of
which work on everything else.  I'm missing something I guess.  I just
don't see it.

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

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: K-Line on digital modes

Don Wilhelm-4
Doug,

Are you attempting to send PSK31 from the K3 Utility Terminal window?  
Or from another application?

If from the K3 Utility, there is no need for DTR or RTS because K3
Utility sends the TX command via the RS-232 com port as a command.

If you are using some other computer application, you will have to set
things up in that application to properly key the K3 - the number of
applications and the way they initiate transmit is too wide and varied
for an easy email answer, consult the help file and on-line information
for your application.

73,
Don W3FPR


On 5/20/2014 9:19 PM, Doug Person via Elecraft wrote:

> I have a full K-line setup (K3, P3, KPA500, KAT500) and I've been
> trying to get the K3 working on digital modes.  I can't seem to get it
> to transmit.  Using the K3 Utility, I can verify the K3 at a
> particular com port.  Firmware updates work fine.  I can read PSK in
> terminal mode.  But, when I click on the transmit button, the K3
> doesn't switch to transmit.  I have the PTT menu option set to DTR
> and, in fact tried every variation of DTR and RTS with no difference.  
> I have tried both FTDI USB-to-Serial adapters and a genuine, built-in
> serial port - all of which work on everything else.  I'm missing
> something I guess.  I just don't see it.
>

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

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: K-Line on digital modes

Jim Brown-10
On 5/20/2014 7:13 PM, Don Wilhelm wrote:
> If you are using some other computer application, you will have to set
> things up in that application to properly key the K3

All digital modes work just fine on a K3 in VOX mode. I've never used
anything else. Thus, the only need for a serial port is for logging
software. I use computer software to generate and decode all forms of
digital signals. For RTTY, use AFSK RTTY, set the baud rate in the rig
the same as the in the computer software, and set both computer and rig
to the same tone frequencies. For all other modes, use DIG A.

Things that can go wrong, in no particular order:

1) The sound card in your computer may be sending to the wrong channel,
may even be muted. Many programs manipulate the Windoze mixer, and
sometimes fail to put controls back where they found them. The N1MM
Logger is notorious for doing that.

2) If you have more than one sound card, the wrong one may be selected.

3) The Line Input gain may be too low, and/or the VOX Gain may be too
low. The Mic Gain pot becomes Line Input Gain in AFSK and DIG A modes.

73, Jim K9YC
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: K-Line on digital modes

jh3sif
In reply to this post by Elecraft mailing list
With the K3 Utility, it seems that clicking on the transmit button on the utility screen without any message in the message box does not switch K3 to transmit mode.
K3 Utility is not a good tool to extensively operate digital mode. I would recommend some other tools such as MMTTY for RTTY and MMVali for PSK, although they need an additional interface device or cable to interconnect your K3 and PC. Of course, you cannot use either of them in parallel to K3 Utility.
I prefer touch-typing operation on RTTY and PSK. So, I do not use K3 Utility for these modes.

Keith - JH3SIF

2014/05/21 10:19、Doug Person via Elecraft <[hidden email]> のメッセージ:

> I have a full K-line setup (K3, P3, KPA500, KAT500) and I've been trying to get the K3 working on digital modes.  I can't seem to get it to transmit.  Using the K3 Utility, I can verify the K3 at a particular com port.  Firmware updates work fine.  I can read PSK in terminal mode.  But, when I click on the transmit button, the K3 doesn't switch to transmit.  I have the PTT menu option set to DTR and, in fact tried every variation of DTR and RTS with no difference.  I have tried both FTDI USB-to-Serial adapters and a genuine, built-in serial port - all of which work on everything else.  I'm missing something I guess.  I just don't see it.
>
> Doug -- K0DXV
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: K-Line on digital modes

Wes (N7WS)
In reply to this post by Jim Brown-10
I second every bit of this.  It's exactly how I do it.

Wes  N7WS

On 5/20/2014 7:58 PM, Jim Brown wrote:

> All digital modes work just fine on a K3 in VOX mode. I've never used anything
> else. Thus, the only need for a serial port is for logging software. I use
> computer software to generate and decode all forms of digital signals. For
> RTTY, use AFSK RTTY, set the baud rate in the rig the same as the in the
> computer software, and set both computer and rig to the same tone frequencies.
> For all other modes, use DIG A.
>
> Things that can go wrong, in no particular order:
>
> 1) The sound card in your computer may be sending to the wrong channel, may
> even be muted. Many programs manipulate the Windoze mixer, and sometimes fail
> to put controls back where they found them. The N1MM Logger is notorious for
> doing that.
>
> 2) If you have more than one sound card, the wrong one may be selected.
>
> 3) The Line Input gain may be too low, and/or the VOX Gain may be too low. The
> Mic Gain pot becomes Line Input Gain in AFSK and DIG A modes.
>
> 73, Jim K9YC
> _

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

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