K3 switching to split freq question

[K9RBorowski]

I noticed this evening that after working a station on 18 meter SSB, I saw a spot on the DX packet reflector for XW1B on 20 meter CW. Curious if I could hear him, I double clicked on the spot and DX4WIN sent the rig to his frequency, which was stated to be 14,005.00 QSX 14,006.20 perfectly, or so I thought....When XW1B finished the present QSO, he said QRZ NA UP. He was S9 at my QTH and I thought I would see if I could work him. Imagine my surprise when my keying was doing nothing! Upon a bit of further observation, I found that the QSY frequency on VFO B was in the SSB mode. To correct this I pressed the A=B button and then the A/B button and dialed the QSX frequency back to VFO B, where the mode was now stated to be CW. I used A/B once more to return to listening to the A VFO just as I heard "NA UP" sent my callsign once and worked him on the first call. Is it something that I am doing wrong or is this a bug in the PC control of the K3 ?  I am using a conventional serial po
 rt and DX4WIN software. I've only had the rig a couple of weeks and this is the first problem I have encountered. Anyone else experience this or have a solution?
Thanks for your time and vy 73, Rog-K9RB
______________________________________________________________
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

[Don Wilhelm-4]

Rog,

I can't say what DX4WIN did or did not do, but I would think if it sets
up split operation, it would also set the correct mode for both the A
and B VFOs.  The K3 handles the mode separately for each VFO (you found
out the hard way).

There is a more direct method than the one you used.
Press BSET ("Set VFO B") and then use the MODE button, tap the A/B
button to exit BSET - that will retain the frequency for you.
Alternately, tap the A/B button to swap VFOs and then tap the MODE
button to change the VFO B (now in VFO A position)  mode - tap A/B to
return the VFOs to their original positions.

73,
Don W3FPR

K9RBorowski wrote:
> I noticed this evening that after working a station on 18 meter SSB, I saw a spot on the DX packet reflector for XW1B on 20 meter CW. Curious if I could hear him, I double clicked on the spot and DX4WIN sent the rig to his frequency, which was stated to be 14,005.00 QSX 14,006.20 perfectly, or so I thought....When XW1B finished the present QSO, he said QRZ NA UP. He was S9 at my QTH and I thought I would see if I could work him. Imagine my surprise when my keying was doing nothing! Upon a bit of further observation, I found that the QSY frequency on VFO B was in the SSB mode. To correct this I pressed the A=B button and then the A/B button and dialed the QSX frequency back to VFO B, where the mode was now stated to be CW. I used A/B once more to return to listening to the A VFO just as I heard "NA UP" sent my callsign once and worked him on the first call. Is it something that I am doing wrong or is this a bug in the PC control of the K3 ?  I am using a conventional serial
 po
>  rt and DX4WIN software. I've only had the rig a couple of weeks and this is the first problem I have encountered. Anyone else experience this or have a solution?
> Thanks for your time and vy 73, Rog-K9RB
>  

______________________________________________________________
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

[Gary Hinson]

> There is a more direct method than the one you used.
> Press BSET ("Set VFO B") and then use the MODE button, tap the A/B
> button to exit BSET - that will retain the frequency for you.
> Alternately, tap the A/B button to swap VFOs and then tap the MODE
> button to change the VFO B (now in VFO A position)  mode - tap A/B to
> return the VFOs to their original positions.

Hey, it might be good to be able to hold the REV button with one hand,
change VFO B's mode, band, antenna, NR or whatever with the other, then
release the REV.  At present, holding REV seems to lock out band, mode and
most other changes except QSYing VFO B using the main A dial.

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

[K9RBorowski]

Thanks for the info, Don. Your method is more direct than mine and also
saves the VFO B frequency, which was not a big deal in this case. If I were
operating a big split, it would have been more cumbersome. I'm somewhat
surprised that this "bug" has gone uncorrected but maybe eventually it will
be addressed. I'm sure DX4WIN has the capabilities of doing splits right on
my Omni VI Plus as well as my TS-950SDX but it is conceivable that it could
still be a software problem as each rig uses a different "rig file" in
DX4WIN. I shall investigate more and find out exactly what is happening
before placing blame on the K3 or DX4WIN with this issue. Thanks for your
help. Knowing that the K3 handles the mode separately for each VFO should
make it easier to troubleshoot. Thanks for your speedy reply, Don. I shall
let you know what I find out and where the problem is generated.
73, Rog-K9RB

----- Original Message -----
From: "Don Wilhelm" <[hidden email]>
To: "K9RBorowski" <[hidden email]>
Cc: <[hidden email]>
Sent: Thursday, April 30, 2009 8:29 PM
Subject: Re: [Elecraft] K3 switching to split freq question


Rog,

I can't say what DX4WIN did or did not do, but I would think if it sets
up split operation, it would also set the correct mode for both the A
and B VFOs.  The K3 handles the mode separately for each VFO (you found
out the hard way).

There is a more direct method than the one you used.
Press BSET ("Set VFO B") and then use the MODE button, tap the A/B
button to exit BSET - that will retain the frequency for you.
Alternately, tap the A/B button to swap VFOs and then tap the MODE
button to change the VFO B (now in VFO A position)  mode - tap A/B to
return the VFOs to their original positions.

73,
Don W3FPR

K9RBorowski wrote:

> I noticed this evening that after working a station on 18 meter SSB, I saw
> a spot on the DX packet reflector for XW1B on 20 meter CW. Curious if I
> could hear him, I double clicked on the spot and DX4WIN sent the rig to
> his frequency, which was stated to be 14,005.00 QSX 14,006.20 perfectly,
> or so I thought....When XW1B finished the present QSO, he said QRZ NA UP.
> He was S9 at my QTH and I thought I would see if I could work him. Imagine
> my surprise when my keying was doing nothing! Upon a bit of further
> observation, I found that the QSY frequency on VFO B was in the SSB mode.
> To correct this I pressed the A=B button and then the A/B button and
> dialed the QSX frequency back to VFO B, where the mode was now stated to
> be CW. I used A/B once more to return to listening to the A VFO just as I
> heard "NA UP" sent my callsign once and worked him on the first call. Is
> it something that I am doing wrong or is this a bug in the PC control of
> the K3 ?  I am using a conventional serial po
>  rt and DX4WIN software. I've only had the rig a couple of weeks and this
> is the first problem I have encountered. Anyone else experience this or
> have a solution? Thanks for your time and vy 73, Rog-K9RB
>

... [show rest of quote]

______________________________________________________________
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

[N5GE]

On Thu, 30 Apr 2009 20:05:06 -0400, "K9RBorowski" <[hidden email]>
wrote:

>I noticed this evening that after working a station on 18 meter SSB, I saw a spot on the DX packet reflector for XW1B on 20 meter CW. Curious if I could hear him, I double clicked on the spot and DX4WIN sent the rig to his frequency, which was stated to be 14,005.00 QSX 14,006.20 perfectly, or so I thought....When XW1B finished the present QSO, he said QRZ NA UP. He was S9 at my QTH and I thought I would see if I could work him. Imagine my surprise when my keying was doing nothing! Upon a bit of further observation, I found that the QSY frequency on VFO B was in the SSB mode. To correct this I pressed the A=B button and then the A/B button and dialed the QSX frequency back to VFO B, where the mode was now stated to be CW. I used A/B once more to return to listening to the A VFO just as I heard "NA UP" sent my callsign once and worked him on the first call. Is it something that I am doing wrong or is this a bug in the PC control of the K3 ?  I am using a conventional serial p
 o
> rt and DX4WIN software. I've only had the rig a couple of weeks and this is the first problem I have encountered. Anyone else experience this or have a solution?
>Thanks for your time and vy 73, Rog-K9RB
>______________________________________________________________
[snip]

If you tap A>B twice the B VFO  will be set exactly the same as the
MAIN RX, but the B VFO frequency will also be set to the A VFO
Frequency.

It sounds like DX4WIN is not setting the mode on the B VFO correctly.

You didn't say if you have the SUB RX installed.

 
Tom, N5GE
K3 #806, K3 #1055
XV144, XV432
W1 and other small kits.
http://www.n5ge.com

______________________________________________________________
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

[Jerry_N8BM]

Rob,

I'm not saying that some logging programs and K3 control programs are not in need of some changes but your problem could have at least been avoided/circumvented by something that I reported to K3 support some time back.  CONFIG parameter CW WGHT was enhanced to provide a SSB+CW function which allows CW keying in SSB mode.  Works great when not in SPLIT but does not work while in SPLIT.  The response from support was that this was on the 'fix' list but again that was quite a while ago.  If this would have resolved your problem perhaps another note to support would help.
Jerry  N8BM
 

K9RBorowski wrote

I noticed this evening that after working a station on 18 meter SSB, I saw a spot on the DX packet reflector for XW1B on 20 meter CW. Curious if I could hear him, I double clicked on the spot and DX4WIN sent the rig to his frequency, which was stated to be 14,005.00 QSX 14,006.20 perfectly, or so I thought....When XW1B finished the present QSO, he said QRZ NA UP. He was S9 at my QTH and I thought I would see if I could work him. Imagine my surprise when my keying was doing nothing! Upon a bit of further observation, I found that the QSY frequency on VFO B was in the SSB mode. To correct this I pressed the A=B button and then the A/B button and dialed the QSX frequency back to VFO B, where the mode was now stated to be CW. I used A/B once more to return to listening to the A VFO just as I heard "NA UP" sent my callsign once and worked him on the first call. Is it something that I am doing wrong or is this a bug in the PC control of the K3 ?  I am using a conventional serial po
 rt and DX4WIN software. I've only had the rig a couple of weeks and this is the first problem I have encountered. Anyone else experience this or have a solution?
Thanks for your time and vy 73, Rog-K9RB
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[e-mail]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

... [show rest of quote]

... [show rest of quote]