Fw: K3 - Can't seem to make LINE-OUT work properly

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

Fw: K3 - Can't seem to make LINE-OUT work properly

Denis Jackson-2
Forget that last mail...I worked out what I was doing wrong!

73

Denis MW0CBC / GW8OQV


----- Original Message -----
From: Denis Jackson
To: [hidden email]
Sent: Sunday, October 25, 2009 5:56 PM
Subject: K3 - Can't seem to make LINE-OUT work properly


Hi Chaps,

Fairly new K3 owner here - just getting set up for digimodes.  I'm probably doing something stupid but...

I can't seem to make line-out do what it should.  I have visited "lin out" in the Config menu and set a value (10) rather than =phones and yet the level on the line-out jack is still dependent on the front panel AF Gain control.

Any ideas what I've missed?

73

Denis MW0CBC / GW8OQV
______________________________________________________________
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
Reply | Threaded
Open this post in threaded view
|

k3-- problems with direct freq entry

Andy Faber
Wayne, et al,
  I'm using 3.44, and experiencing odd results on direct freq entry from the
keypad, all when using the decimal point, e.g.:
1)  entering 21225.5 gives 21225.0.  In general, all such are rounded off to
the whole kHz.
2)  entering 7025.5 gives 25500.00!!
3)  entering 21226 works ok.  If I then enter 28425.5, it goes again to
21226.
  This is very strange.
  73, andy, ae6y, K3 #076

______________________________________________________________
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
Reply | Threaded
Open this post in threaded view
|

Re: k3-- problems with direct freq entry

N5GE
On Sun, 25 Oct 2009 12:32:46 -0700, "Andy Faber"
<[hidden email]> wrote:

>Wayne, et al,
>  I'm using 3.44, and experiencing odd results on direct freq entry from the
>keypad, all when using the decimal point, e.g.:
>1)  entering 21225.5 gives 21225.0.  In general, all such are rounded off to
>the whole kHz.
>2)  entering 7025.5 gives 25500.00!!
>3)  entering 21226 works ok.  If I then enter 28425.5, it goes again to
>21226.
>  This is very strange.
>  73, andy, ae6y, K3 #076
[snip]

Andy,

Direct entry has one KHz resolution.  The decimal point should be
after the MHz.

18330 KHz = 1.833
7025.5 = 7.025 (entering 7025.5 on K3 #806 puts 7.025 on VFOA.

To my knowledge it has always been that way.

Page 15 of the users manual rev D5....

______________________________________________________________
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
Amateur Radio Operator N5GE
Reply | Threaded
Open this post in threaded view
|

Re: k3-- problems with direct freq entry

Andy Faber
Well, maybe that's just something I never noticed.  That would explain why
7025.5 becomes 25500 (i.e., the radio assumes the mHz are 25, not 7.
  But it seems peculiar to me, particularly because under software control
you can use decimal points.  For example, if I send the radio 7025.345 from
my logging program, it does take the radio to that exact  frequency.
  73, andy, ae6y

----- Original Message -----
From: "Radio Amateur N5GE" <[hidden email]>
To: <[hidden email]>
Sent: Sunday, October 25, 2009 1:05 PM
Subject: Re: [Elecraft] k3-- problems with direct freq entry


> On Sun, 25 Oct 2009 12:32:46 -0700, "Andy Faber"
> <[hidden email]> wrote:
>
>>Wayne, et al,
>>  I'm using 3.44, and experiencing odd results on direct freq entry from
>> the
>>keypad, all when using the decimal point, e.g.:
>>1)  entering 21225.5 gives 21225.0.  In general, all such are rounded off
>>to
>>the whole kHz.
>>2)  entering 7025.5 gives 25500.00!!
>>3)  entering 21226 works ok.  If I then enter 28425.5, it goes again to
>>21226.
>>  This is very strange.
>>  73, andy, ae6y, K3 #076
> [snip]
>
> Andy,
>
> Direct entry has one KHz resolution.  The decimal point should be
> after the MHz.
>
> 18330 KHz = 1.833
> 7025.5 = 7.025 (entering 7025.5 on K3 #806 puts 7.025 on VFOA.
>
> To my knowledge it has always been that way.
>
> Page 15 of the users manual rev D5....
>
> ______________________________________________________________
> 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 

______________________________________________________________
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
Reply | Threaded
Open this post in threaded view
|

Re: k3-- problems with direct freq entry

Julian, G4ILO

Andrew Faber-2 wrote
  But it seems peculiar to me, particularly because under software control
you can use decimal points.  For example, if I send the radio 7025.345 from
my logging program, it does take the radio to that exact  frequency.
Yeah, but the logging program knows what format the K3 wants, and converts it.
Julian, G4ILO. K2 #392  K3 #222 KX3 #110
* G4ILO's Shack - http://www.g4ilo.com
* KComm - http://www.g4ilo.com/kcomm.html
* KTune - http://www.g4ilo.com/ktune.html