K3 CW bug-ettes

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

K3 CW bug-ettes

Gary Hinson

Hi!

I've noticed some weeny bugs - or rather things that don't seem quite right
to me - in K3 firmware v4.03, DVR v1.03:

1.  The new QRQ QSK mode works nicely aside from the known limitation of no
RIT.  However, this limitation still seems to apply when I change from full
break in to semi break in using the band/QSK button.  I have to go into the
menu and de-select the QRQ option as well to get RIT back.  

2.  When in SSB mode, I can send CW just by hitting the paddle but if I
assert the PTT first (e.g. using my footswitch), the rig goes into TX but
won't key.

3.  In SSB mode, if I accidentally hit the DVR voice-box message replay
button twice, or if it bounces, the second replay interrupts the first but
there is an extended silent delay at the end after playing the message,
before the rig drops back to receive.  [In CW mode, the second press chains
another message as expected, but there is no extended hang at the end.]

These are so minor, they hardly qualify as bugs.  Just quirks really.
Features if you will.

73
Gary  ZL2iFB  K3 #2887

______________________________________________________________
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 CW bug-ettes

Vic K2VCO
On 8/1/2010 5:59 PM, Gary Hinson wrote:

> I've noticed some weeny bugs - or rather things that don't seem quite right
> to me - in K3 firmware v4.03, DVR v1.03:
>
> 1.  The new QRQ QSK mode works nicely aside from the known limitation of no
> RIT.  However, this limitation still seems to apply when I change from full
> break in to semi break in using the band/QSK button.  I have to go into the
> menu and de-select the QRQ option as well to get RIT back.

The QRQ option works in semi-QSK mode as well. It allows you (or some machine!) to send
clean code at higher speeds. I've noticed that without the QRQ option -- even in semi-QSK
mode -- when the speed gets above about 35 wpm it starts to have timing issues. After
about 45, it is really bad. At slower speeds, although it is acceptable, you can notice
the difference.

I assigned the QRQ menu item to one of the PFK's on my K3. It is too much of a hassle to
go to the menu!

I don't use RIT that much, but SPLIT is a necessity for dx pileups. I know there is a way
to operate split with the subreceiver, using VFO B to listen, but I haven't been able to
get used to it.


--
Vic, K2VCO
Fresno CA
http://www.qsl.net/k2vco/
______________________________________________________________
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 CW bug-ettes

Cookie
Vic, the method that I use is to tune with the main receiver to find the DX
transmit freq.  When I have the DX tuned in, I tap the A>B button and the SUB
button then turn up the AF gain on the SUB.  Then I select my transmit
frequency with the main receiver and make my call.  It is very convenient and is
my preferred technique for working split.  If I have to call for a while to make
my contact it lets me listen for other callers with the main receiver and try to
find a good call frequency.  This is my main reason for buying the sub receiver.
Willis 'Cookie' Cooke
K5EWJ




________________________________
From: Vic K2VCO <[hidden email]>
To: [hidden email]
Sent: Sun, August 1, 2010 8:54:48 PM
Subject: Re: [Elecraft] K3 CW bug-ettes

On 8/1/2010 5:59 PM, Gary Hinson wrote:

> I've noticed some weeny bugs - or rather things that don't seem quite right
> to me - in K3 firmware v4.03, DVR v1.03:
>
> 1.  The new QRQ QSK mode works nicely aside from the known limitation of no
> RIT.  However, this limitation still seems to apply when I change from full
> break in to semi break in using the band/QSK button.  I have to go into the
> menu and de-select the QRQ option as well to get RIT back.

The QRQ option works in semi-QSK mode as well. It allows you (or some machine!)
to send

clean code at higher speeds. I've noticed that without the QRQ option -- even in
semi-QSK

mode -- when the speed gets above about 35 wpm it starts to have timing issues.
After

about 45, it is really bad. At slower speeds, although it is acceptable, you can
notice

the difference.

I assigned the QRQ menu item to one of the PFK's on my K3. It is too much of a
hassle to

go to the menu!

I don't use RIT that much, but SPLIT is a necessity for dx pileups. I know there
is a way

to operate split with the subreceiver, using VFO B to listen, but I haven't been
able to

get used to it.


--
Vic, K2VCO
Fresno CA
http://www.qsl.net/k2vco/
______________________________________________________________
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 CW bug-ettes

Gary Hinson
In reply to this post by Vic K2VCO
> The QRQ option works in semi-QSK mode as well. It allows you
> (or some machine!) to send
> clean code at higher speeds. I've noticed that without the
> QRQ option -- even in semi-QSK
> mode -- when the speed gets above about 35 wpm it starts to
> have timing issues. After
> about 45, it is really bad.

??  I'm surprised to hear that, Vic.  I thought the QRQ+ thing was all about
making the TX-RX changeovers as slick as possible for QSK, so I don't know
how it would affect semi-break-in since the rig is mostly held in TX.  I
seldom send above about 32 or 34wpm though, so perhaps there's some issue at
the high end that I just haven't noticed yet?

73,
Gary  ZL2iFB

______________________________________________________________
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 CW bug-ettes

Vic K2VCO
It's easy to test. Just program a memory keyer (etc.) and crank up the speed. In my
opinion it has to do with the CPU being busy.

On 8/1/2010 8:12 PM, Gary Hinson wrote:

>> The QRQ option works in semi-QSK mode as well. It allows you
>> (or some machine!) to send
>> clean code at higher speeds. I've noticed that without the
>> QRQ option -- even in semi-QSK
>> mode -- when the speed gets above about 35 wpm it starts to
>> have timing issues. After
>> about 45, it is really bad.
>
> ??  I'm surprised to hear that, Vic.  I thought the QRQ+ thing was all about
> making the TX-RX changeovers as slick as possible for QSK, so I don't know
> how it would affect semi-break-in since the rig is mostly held in TX.  I
> seldom send above about 32 or 34wpm though, so perhaps there's some issue at
> the high end that I just haven't noticed yet?
>
> 73,
> Gary  ZL2iFB

--
Vic, K2VCO
Fresno CA
http://www.qsl.net/k2vco/
______________________________________________________________
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 CW bug-ettes

Gary Hinson
> It's easy to test. Just program a memory keyer (etc.) and
> crank up the speed. In my
> opinion it has to do with the CPU being busy.

Mmmm, I hear what you mean by toggling QRQ mode on/off while sending.
Around 44wpm and up, the dots become shortened in normal mode but sound fine
in QRQ+ mode.  I hadn't noticed that before.  Tnx.

73
Gary  ZL2iFB

______________________________________________________________
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 CW bug-ettes

GW0ETF
In reply to this post by Vic K2VCO
But if you want to use the VFO A-B switching facility in eg N1MM for running on A, S&P on B (or SO2R?) you need the standard Split function of the K3.

Perhaps it's possible to create some (N1MM) macros for the 'alternative' split method using Autohotkeys etc but it would be a real pain I'm sure....

73,

Stewart, GW0ETF

Vic K2VCO wrote
I assigned the QRQ menu item to one of the PFK's on my K3. It is too much of a hassle to
go to the menu!

I don't use RIT that much, but SPLIT is a necessity for dx pileups. I know there is a way
to operate split with the subreceiver, using VFO B to listen, but I haven't been able to
get used to it.