Elecraft › [K2]

K2 LSB Modulation issue

Classic

List

Threaded

20 messages Options

Michael Jensen

K2 LSB Modulation issue

Hi all

I have noticed an issue on my trusty K2 #5111. Might have been there since
I build it several years ago or it might have come during the years

The issue are the modulation on LSB. The audio are not very good and do
sound "funny" Could maybe be described as nasal or some one knowing my voice
call it "like the audio was being frequency modulated".

USB are ok or at least so much better that no one notices.

There are no difference between running high power or low power and have
tested using different power supplies.

The reason for going un detected is that I in the past not often was below
20 on SSB. When I used 40 or 80 it was mainly PSK but running USB. So no
issue seen. When I was made aware of the issue I first put the blamed on a
power supply for my PA as beeing the reason. (the magnetic field issue
discussed here several years back). Now having tested for that it do not
seem to be the problem.

Any of you that would have experience or comments on a TX audio issue that
effect only LSB.

Thanks in advance

73 de OZ1BZJ

Michael

______________________________________________________________
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

Re: K2 LSB Modulation issue

Michael,

I suspect that the BFO for LSB is not correctly for your KSB2 OP1 filter.
First check to be certain the SSB FL1 is set to OP1. The BFO frequency
for LSB using the OP1 filter will be between 4913.48 and 4913.65
depending on your particular filter center, and the USB BFO will be in
the vicinity of 4916.5. You can check with the internal frequency
counter probe in TP2, enter CAL FIL and tap the BAND- button.

Then go to my website www.w3fpr.com and read part 3 of the article
dealing with K2 Dial Calibration - that is the section that explains the
filter setting using Spectrogram.
If you do not have a copy of Spectrogram and or need information about
how to set it up on your computer, download it from Tom Hammond's
website www.n0ss.net.

If you have not set up your K2 filters before using Spectrogram, you may
want to align all your filters.

73,
Don W3FPR

On 10/10/2010 5:36 PM, Michael Jensen wrote:

> Hi all
>
>
>
> I have noticed an issue on my trusty K2 #5111. Might have been there since
> I build it several years ago or it might have come during the years
>
> The issue are the modulation on LSB. The audio are not very good and do
> sound "funny" Could maybe be described as nasal or some one knowing my voice
> call it "like the audio was being frequency modulated".
>
> USB are ok or at least so much better that no one notices.
>
> There are no difference between running high power or low power and have
> tested using different power supplies.
>
> The reason for going un detected is that I in the past not often was below
> 20 on SSB. When I used 40 or 80 it was mainly PSK but running USB. So no
> issue seen. When I was made aware of the issue I first put the blamed on a
> power supply for my PA as beeing the reason. (the magnetic field issue
> discussed here several years back). Now having tested for that it do not
> seem to be the problem.
>
> Any of you that would have experience or comments on a TX audio issue that
> effect only LSB.
>
>

Michael Jensen

Re: K2 LSB Modulation issue

Hi Don

Thanks for your answer.

I have now done a realignment using Spectrogram as I did originally. I
believe using the exact same instruction.

I might have asked this 4-5 years back but maybe without prober explanation,
any way I do not recall the answer.

Setting the LSB FL4 for PSK to a bandwidth of 0.7 I struggle to reach a
center of 1KHz. I can get to about 800 with a BFO of 4912.99 and a dac of 16
going further then that the signal fade. Is that a problem....??

The tuned values for FL2 OPT1 are 4913.52 dac 001 and FL3 of 1.8 is 4912.94
dac 001...

I have not yet had the possibility for some one that know me to listen to my
tx audio, so I could tune FL1

For reference the setting on USB are FL2 OPT1 4916.36 dac 212, FL3 1.8
4915.90 dac 195 FL4 0.7 4915.08 dac 164

Thanks in advance

73 de OZ1BZJ

Michael

-----Oprindelig meddelelse-----
Fra: Don Wilhelm [mailto:[hidden email]]
Sendt: 11. oktober 2010 00:49
Til: Michael Jensen
Cc: [hidden email]
Emne: Re: [Elecraft] K2 LSB Modulation issue

Michael,

I suspect that the BFO for LSB is not correctly for your KSB2 OP1 filter.
First check to be certain the SSB FL1 is set to OP1. The BFO frequency
for LSB using the OP1 filter will be between 4913.48 and 4913.65
depending on your particular filter center, and the USB BFO will be in
the vicinity of 4916.5. You can check with the internal frequency
counter probe in TP2, enter CAL FIL and tap the BAND- button.

Then go to my website www.w3fpr.com and read part 3 of the article
dealing with K2 Dial Calibration - that is the section that explains the
filter setting using Spectrogram.
If you do not have a copy of Spectrogram and or need information about
how to set it up on your computer, download it from Tom Hammond's
website www.n0ss.net.

If you have not set up your K2 filters before using Spectrogram, you may
want to align all your filters.

73,
Don W3FPR

On 10/10/2010 5:36 PM, Michael Jensen wrote:
> Hi all
>
>
>
> I have noticed an issue on my trusty K2 #5111. Might have been there
since
> I build it several years ago or it might have come during the years
>
> The issue are the modulation on LSB. The audio are not very good and do
> sound "funny" Could maybe be described as nasal or some one knowing my
voice

> call it "like the audio was being frequency modulated".
>
> USB are ok or at least so much better that no one notices.
>
> There are no difference between running high power or low power and have
> tested using different power supplies.
>
> The reason for going un detected is that I in the past not often was below
> 20 on SSB. When I used 40 or 80 it was mainly PSK but running USB. So no
> issue seen. When I was made aware of the issue I first put the blamed on a
> power supply for my PA as beeing the reason. (the magnetic field issue
> discussed here several years back). Now having tested for that it do not
> seem to be the problem.
>
> Any of you that would have experience or comments on a TX audio issue that
> effect only LSB.
>
>

Don Wilhelm-4

Re: K2 LSB Modulation issue

Michael,

First a comment - why use SSB FL4 set to 700 Hz width for PSK and have
to remember to turn the compression off when using digital modes? It is
much easier (IMHO) to go to the secondary menu and turn the RTTY filter
set on. That gives you a compression setting independent of that used
for SSB - just set it to 1:1 for the RTTY filters and be done with it.

I usually set RTTY FL1 the same as SSB FL1 OP1 filter and the BFOs the
same. That gives you a full width passband for normal point and click
in the waterfall. Then I set FL2 to 1.00, FL3 to 0.70 and FL4 to 0.40
to give narrow RTTY filters when QRM shows up - yes you have to tune to
the filter center with the VFO, but at least you can continue
operating. Center the narrow RTTY filters at 1000 Hz, and easy number
to remember and it works well with MMTTY when the mark frequency is set
to 915 Hz.

Now on to your question - yes, that is a problem - the low end of your
BFO range is too high. You can increase both C173 and 174 keeping the
ratio close to 3:1, or you can try an easier fix first, solder a small
value capacitor from the juction of the crystals to ground (U11 pins 6
and 3 maje nice anchor points). I would not exceed 27 pF with this
added capacitor because it can decrease the BFO RF voltage level. Check
both the high and low end of the BFO range after making this change (see
manual page 62). The high must be greater than 4916.3 and the low less
than 4912.7. If you cannot achieve the correct range with this single
capacitor addition, you will have to change both C173 and C174. I would
try 100 pF and 330 pF to see if that brings it into range.

You may want to write down the frequencies (not the DAC values) of the
BFOs that you already have set because all the BFO settings will be
shifted and you will have to do the filters over again.

73,
Don W3FPR

On 10/11/2010 6:33 PM, Michael Jensen wrote:

> Hi Don
>
> Thanks for your answer.
>
> I have now done a realignment using Spectrogram as I did originally. I
> believe using the exact same instruction.
>
> I might have asked this 4-5 years back but maybe without prober explanation,
> any way I do not recall the answer.
>
> Setting the LSB FL4 for PSK to a bandwidth of 0.7 I struggle to reach a
> center of 1KHz. I can get to about 800 with a BFO of 4912.99 and a dac of 16
> going further then that the signal fade. Is that a problem....??
>
> The tuned values for FL2 OPT1 are 4913.52 dac 001 and FL3 of 1.8 is 4912.94
> dac 001...
>
> I have not yet had the possibility for some one that know me to listen to my
> tx audio, so I could tune FL1
>
>
> For reference the setting on USB are FL2 OPT1 4916.36 dac 212, FL3 1.8
> 4915.90 dac 195 FL4 0.7 4915.08 dac 164
>
>
> Thanks in advance
>
> 73 de OZ1BZJ
>
> Michael
>
>
>
> -----Oprindelig meddelelse-----
> Fra: Don Wilhelm [mailto:[hidden email]]
> Sendt: 11. oktober 2010 00:49
> Til: Michael Jensen
> Cc: [hidden email]
> Emne: Re: [Elecraft] K2 LSB Modulation issue
>
> Michael,
>
> I suspect that the BFO for LSB is not correctly for your KSB2 OP1 filter.
> First check to be certain the SSB FL1 is set to OP1. The BFO frequency
> for LSB using the OP1 filter will be between 4913.48 and 4913.65
> depending on your particular filter center, and the USB BFO will be in
> the vicinity of 4916.5. You can check with the internal frequency
> counter probe in TP2, enter CAL FIL and tap the BAND- button.
>
> Then go to my website www.w3fpr.com and read part 3 of the article
> dealing with K2 Dial Calibration - that is the section that explains the
> filter setting using Spectrogram.
> If you do not have a copy of Spectrogram and or need information about
> how to set it up on your computer, download it from Tom Hammond's
> website www.n0ss.net.
>
> If you have not set up your K2 filters before using Spectrogram, you may
> want to align all your filters.
>
> 73,
> Don W3FPR
>
>
> On 10/10/2010 5:36 PM, Michael Jensen wrote:
>> Hi all
>>
>>
>>
>> I have noticed an issue on my trusty K2 #5111. Might have been there
> since
>> I build it several years ago or it might have come during the years
>>
>> The issue are the modulation on LSB. The audio are not very good and do
>> sound "funny" Could maybe be described as nasal or some one knowing my
> voice
>> call it "like the audio was being frequency modulated".
>>
>> USB are ok or at least so much better that no one notices.
>>
>> There are no difference between running high power or low power and have
>> tested using different power supplies.
>>
>> The reason for going un detected is that I in the past not often was below
>> 20 on SSB. When I used 40 or 80 it was mainly PSK but running USB. So no
>> issue seen. When I was made aware of the issue I first put the blamed on a
>> power supply for my PA as beeing the reason. (the magnetic field issue
>> discussed here several years back). Now having tested for that it do not
>> seem to be the problem.
>>
>> Any of you that would have experience or comments on a TX audio issue that
>> effect only LSB.
>>
>>
> ______________________________________________________________
> 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
>

Michael Jensen

Re: K2 LSB Modulation issue

Don your are the man

Once again you have helped a Elecraft product on it´s way

15pF across pin 3 and 6 of U11 pulling the crystals did make the difference.
Now the BFO range are within the window given in the manual.
Also the reports on my LSB modulation are way better. Not in the prefect
level, but way better then it was... I would say with some more filter
tuning on the FL1 for TX and the Smaller bandwidth filters for SSB. #5111
are fit for fight for more qso.

Looking back in the manual at my own notes it is now clear, that I ignored
the warning signs when the limits of the BFO was tested. One end are indeed
not within the window. Properly intoxicated from the solder fumes and the
eagerness to build you get from a K2 made me never to readdressed that fact.

Thanks
Don I owe you a beer.. Maybe in Dayton

73 de OZ1BZJ

Michael

-----Oprindelig meddelelse-----
Fra: [hidden email]
[mailto:[hidden email]] På vegne af Don Wilhelm
Sendt: 12. oktober 2010 01:22
Til: Michael Jensen
Cc: 'Elecraft'
Emne: Re: [Elecraft] K2 LSB Modulation issue

Michael,

First a comment - why use SSB FL4 set to 700 Hz width for PSK and have
to remember to turn the compression off when using digital modes? It is
much easier (IMHO) to go to the secondary menu and turn the RTTY filter
set on. That gives you a compression setting independent of that used
for SSB - just set it to 1:1 for the RTTY filters and be done with it.

I usually set RTTY FL1 the same as SSB FL1 OP1 filter and the BFOs the
same. That gives you a full width passband for normal point and click
in the waterfall. Then I set FL2 to 1.00, FL3 to 0.70 and FL4 to 0.40
to give narrow RTTY filters when QRM shows up - yes you have to tune to
the filter center with the VFO, but at least you can continue
operating. Center the narrow RTTY filters at 1000 Hz, and easy number
to remember and it works well with MMTTY when the mark frequency is set
to 915 Hz.

Now on to your question - yes, that is a problem - the low end of your
BFO range is too high. You can increase both C173 and 174 keeping the
ratio close to 3:1, or you can try an easier fix first, solder a small
value capacitor from the juction of the crystals to ground (U11 pins 6
and 3 maje nice anchor points). I would not exceed 27 pF with this
added capacitor because it can decrease the BFO RF voltage level. Check
both the high and low end of the BFO range after making this change (see
manual page 62). The high must be greater than 4916.3 and the low less
than 4912.7. If you cannot achieve the correct range with this single
capacitor addition, you will have to change both C173 and C174. I would
try 100 pF and 330 pF to see if that brings it into range.

You may want to write down the frequencies (not the DAC values) of the
BFOs that you already have set because all the BFO settings will be
shifted and you will have to do the filters over again.

73,
Don W3FPR

______________________________________________________________
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

W4CCS

New Firmware Issues with K3

Loaded the new firmware updates for the K3 and P3 and now have issues
(until I reverted back) with HRD..

With the older versions, while looking at the DX cluster (HRD), I could
mouse click on a spot and the K3 would QSY and stay there..

Now (again) when I click it jumps to the new spot and right back to the
original frequency.. Re-loaded 4.12 on the K3 and 0.31 P3 and everything
worked OK.. Anyone else experiencing this..??

de W4CCS
______________________________________________________________
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

Chester Alderman

Re: New Firmware Issues with K3

I'm running 4.14 and just tested my K3 with my ancient YPlog. I clicked on a
17m spot, the K3 went there and stayed; I then clicked on a 15m spot, my K3
went there and stayed. So I would say your firmware on the K3 is not the
problem?

73,
Tom - W4BQF

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of W4CCS
Sent: Wednesday, October 13, 2010 4:23 PM
To: [hidden email]
Subject: [Elecraft] New Firmware Issues with K3

Loaded the new firmware updates for the K3 and P3 and now have issues
(until I reverted back) with HRD..

With the older versions, while looking at the DX cluster (HRD), I could
mouse click on a spot and the K3 would QSY and stay there..

Now (again) when I click it jumps to the new spot and right back to the
original frequency.. Re-loaded 4.12 on the K3 and 0.31 P3 and everything
worked OK.. Anyone else experiencing this..??

de W4CCS
______________________________________________________________
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

Ken Wagner K3IU

Re: New Firmware Issues with K3

I forgot to say that I am NOT using the P3... just the K3.
73, Ken K3IU

On 10/13/2010 5:05 PM, Ken K3IU wrote:

> I'm also running 4.14 and when using HRD, I see the same
> thing W3CCS reports. The radio jumps to the frequency that
> was double clicked and then almost immediately returns to
> the original frequency on the radio before double clicking.
> 73,
> Ken K3IU
>
> On 10/13/2010 4:55 PM, Tommy Alderman wrote:
>> I'm running 4.14 and just tested my K3 with my ancient YPlog. I clicked on a
>> 17m spot, the K3 went there and stayed; I then clicked on a 15m spot, my K3
>> went there and stayed. So I would say your firmware on the K3 is not the
>> problem?
>>
>> 73,
>> Tom - W4BQF
>>
>>
>> -----Original Message-----
>> From:[hidden email]
>> [mailto:[hidden email]] On Behalf Of W4CCS
>> Sent: Wednesday, October 13, 2010 4:23 PM
>> To:[hidden email]
>> Subject: [Elecraft] New Firmware Issues with K3
>>
>> Loaded the new firmware updates for the K3 and P3 and now have issues
>> (until I reverted back) with HRD..
>>
>> With the older versions, while looking at the DX cluster (HRD), I could
>> mouse click on a spot and the K3 would QSY and stay there..
>>
>> Now (again) when I click it jumps to the new spot and right back to the
>> original frequency.. Re-loaded 4.12 on the K3 and 0.31 P3 and everything
>> worked OK.. Anyone else experiencing this..??
>>
>> de W4CCS
>> ______________________________________________________________
>> 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
>>

Ken Wagner K3IU

Re: New Firmware Issues with K3

Oops... the report below was with the K3 on 10m and the
frequency being clicked on was on 15m. I just tried clicking
on a 10m spot with the radio on 10m and it works correctly.
73, Ken K3IU
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On 10/13/2010 5:06 PM, Ken K3IU wrote:

> I forgot to say that I am NOT using the P3... just the K3.
> 73, Ken K3IU
>
> On 10/13/2010 5:05 PM, Ken K3IU wrote:
>> I'm also running 4.14 and when using HRD, I see the same
>> thing W3CCS reports. The radio jumps to the frequency
>> that was double clicked and then almost immediately
>> returns to the original frequency on the radio before
>> double clicking.
>> 73,
>> Ken K3IU
>>
>> On 10/13/2010 4:55 PM, Tommy Alderman wrote:
>>> I'm running 4.14 and just tested my K3 with my ancient
>>> YPlog. I clicked on a
>>> 17m spot, the K3 went there and stayed; I then clicked
>>> on a 15m spot, my K3
>>> went there and stayed. So I would say your firmware on
>>> the K3 is not the
>>> problem?
>>>
>>> 73,
>>> Tom - W4BQF
>>>
>>>
>>> -----Original Message-----
>>> From:[hidden email]
>>> [mailto:[hidden email]] On Behalf Of
>>> W4CCS
>>> Sent: Wednesday, October 13, 2010 4:23 PM
>>> To:[hidden email]
>>> Subject: [Elecraft] New Firmware Issues with K3
>>>
>>> Loaded the new firmware updates for the K3 and P3 and
>>> now have issues
>>> (until I reverted back) with HRD..
>>>
>>> With the older versions, while looking at the DX cluster
>>> (HRD), I could
>>> mouse click on a spot and the K3 would QSY and stay there..
>>>
>>> Now (again) when I click it jumps to the new spot and
>>> right back to the
>>> original frequency.. Re-loaded 4.12 on the K3 and 0.31
>>> P3 and everything
>>> worked OK.. Anyone else experiencing this..??
>>>
>>> de W4CCS
>>> ______________________________________________________________
>>>
>>> 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
>>>

Jim Rogers, W4ATK

Re: New Firmware Issues with K3

In reply to this post by Ken Wagner K3IU

I first tested the CAT command "FAxxxxxxxxxxx;" (xs being the
frequency to QSY to) using the K3 Utility and it worked like a champ,
no problems. I then went to HRD's command tester and was able to send
the same commands successfully, but HRD reported a ERROR in the
response back from the K3 and I think that what might be happening is
the HRD ERROR handler might be saying "bad command" and restores the
previous band and frequency.

Jim, W4ATK
On Oct 13, 2010, at 4:06 PM, Ken K3IU wrote:

> I forgot to say that I am NOT using the P3... just the K3.
> 73, Ken K3IU
>
> On 10/13/2010 5:05 PM, Ken K3IU wrote:
>> I'm also running 4.14 and when using HRD, I see the same
>> thing W3CCS reports. The radio jumps to the frequency that
>> was double clicked and then almost immediately returns to
>> the original frequency on the radio before double clicking.
>> 73,
>> Ken K3IU
>>
>> On 10/13/2010 4:55 PM, Tommy Alderman wrote:
>>> I'm running 4.14 and just tested my K3 with my ancient YPlog. I
>>> clicked on a
>>> 17m spot, the K3 went there and stayed; I then clicked on a 15m
>>> spot, my K3
>>> went there and stayed. So I would say your firmware on the K3 is
>>> not the
>>> problem?
>>>
>>> 73,
>>> Tom - W4BQF
>>>
>>>
>>> -----Original Message-----
>>> From:[hidden email]
>>> [mailto:[hidden email]] On Behalf Of W4CCS
>>> Sent: Wednesday, October 13, 2010 4:23 PM
>>> To:[hidden email]
>>> Subject: [Elecraft] New Firmware Issues with K3
>>>
>>> Loaded the new firmware updates for the K3 and P3 and now have
>>> issues
>>> (until I reverted back) with HRD..
>>>
>>> With the older versions, while looking at the DX cluster (HRD), I
>>> could
>>> mouse click on a spot and the K3 would QSY and stay there..
>>>
>>> Now (again) when I click it jumps to the new spot and right back
>>> to the
>>> original frequency.. Re-loaded 4.12 on the K3 and 0.31 P3 and
>>> everything
>>> worked OK.. Anyone else experiencing this..??
>>>
>>> de W4CCS
>>> ______________________________________________________________
>>> 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
>>>
> ______________________________________________________________
> 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

Alan Bloom-2

Re: New Firmware Issues with K3

In reply to this post by W4CCS

I don't see it here. Running P3 firmware 00.36, K3 version 04.14 and
HRD version 5.0. I can mouse-click on a frequency in HRD and the K3
QSYs normally and stays there. I can also QSY using the P3 markers and
both the K3 and HRD are happy.

Which software versions are you running?

Does is only do it when you click on a DX cluster spot or does it also
do it when you click on a frequency on the "dial" in the HRD screen?

Alan N1AL

On Wed, 2010-10-13 at 16:23 -0400, W4CCS wrote:

> Loaded the new firmware updates for the K3 and P3 and now have issues
> (until I reverted back) with HRD..
>
> With the older versions, while looking at the DX cluster (HRD), I could
> mouse click on a spot and the K3 would QSY and stay there..
>
> Now (again) when I click it jumps to the new spot and right back to the
> original frequency.. Re-loaded 4.12 on the K3 and 0.31 P3 and everything
> worked OK.. Anyone else experiencing this..??
>
> de W4CCS
> ______________________________________________________________
> 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

Jim Rogers, W4ATK

Re: New Firmware Issues with K3

Alan,

You have to double click on a HRD DX cluster spot that will change
the band to see it. That is the only way I can reproduce it here. It
will change the band and display the new frequency, then return to the
old band/frequency. I am running the latest firmware in the P3 and K3
(00.36 and 04.14). I tested with HRD's command tester (Tools-Command
Tester) and HRD reports an error response to the FA command.

Jim, W4ATK

On Oct 13, 2010, at 7:44 PM, Alan Bloom wrote:

> I don't see it here. Running P3 firmware 00.36, K3 version 04.14 and
> HRD version 5.0. I can mouse-click on a frequency in HRD and the K3
> QSYs normally and stays there. I can also QSY using the P3 markers
> and
> both the K3 and HRD are happy.
>
> Which software versions are you running?
>
> Does is only do it when you click on a DX cluster spot or does it also
> do it when you click on a frequency on the "dial" in the HRD screen?
>
> Alan N1AL
>
>
>
> On Wed, 2010-10-13 at 16:23 -0400, W4CCS wrote:
>> Loaded the new firmware updates for the K3 and P3 and now have issues
>> (until I reverted back) with HRD..
>>
>> With the older versions, while looking at the DX cluster (HRD), I
>> could
>> mouse click on a spot and the K3 would QSY and stay there..
>>
>> Now (again) when I click it jumps to the new spot and right back to
>> the
>> original frequency.. Re-loaded 4.12 on the K3 and 0.31 P3 and
>> everything
>> worked OK.. Anyone else experiencing this..??
>>
>> de W4CCS
>> ______________________________________________________________
>> 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

Bob Naumann W5OV

Re: New Firmware Issues with K3

Which VFO is active when you do this?

FA is the VFO A set / read frequency command.

Any chance you're on VFO B?

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of JAMES ROGERS
Sent: Thursday, October 14, 2010 5:31 AM
To: [hidden email]
Cc: Elecraft Reflector
Subject: Re: [Elecraft] New Firmware Issues with K3

Alan,

You have to double click on a HRD DX cluster spot that will change
the band to see it. That is the only way I can reproduce it here. It
will change the band and display the new frequency, then return to the
old band/frequency. I am running the latest firmware in the P3 and K3
(00.36 and 04.14). I tested with HRD's command tester (Tools-Command
Tester) and HRD reports an error response to the FA command.

Jim, W4ATK

On Oct 13, 2010, at 7:44 PM, Alan Bloom wrote:

______________________________________________________________
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

Alan Bloom

Re: New Firmware Issues with K3

In reply to this post by Jim Rogers, W4ATK

Jim,

Thanks for the clarification. So it only does it when changing bands
using a DX cluster. Unfortunately the computer that I use for testing
does not have an Internet connection. (For security reasons - it's has
all my P3 development code which I really don't want to risk getting
hacked.) So I can't test with a DX cluster. Does the problem occur if
you change bands in HRD by clicking on a band button?

> I tested with HRD's command tester (Tools-Command
> Tester) and HRD reports an error response to the FA command.

I think that's just the way HRD works. Any time you send a command that
has no response (most set commands) it reports an "Error" in the
received column. I checked and it still does it with older K3 firmware
(04.12) and no P3 connected.

Alan N1AL

On Thu, 2010-10-14 at 05:31 -0500, JAMES ROGERS wrote:

> Alan,
>
> You have to double click on a HRD DX cluster spot that will change
> the band to see it. That is the only way I can reproduce it here. It
> will change the band and display the new frequency, then return to the
> old band/frequency. I am running the latest firmware in the P3 and K3
> (00.36 and 04.14). I tested with HRD's command tester (Tools-Command
> Tester) and HRD reports an error response to the FA command.
>
> Jim, W4ATK
>
> On Oct 13, 2010, at 7:44 PM, Alan Bloom wrote:
>
> > I don't see it here. Running P3 firmware 00.36, K3 version 04.14 and
> > HRD version 5.0. I can mouse-click on a frequency in HRD and the K3
> > QSYs normally and stays there. I can also QSY using the P3 markers
> > and
> > both the K3 and HRD are happy.
> >
> > Which software versions are you running?
> >
> > Does is only do it when you click on a DX cluster spot or does it also
> > do it when you click on a frequency on the "dial" in the HRD screen?
> >
> > Alan N1AL
> >
> >
> >
> > On Wed, 2010-10-13 at 16:23 -0400, W4CCS wrote:
> >> Loaded the new firmware updates for the K3 and P3 and now have issues
> >> (until I reverted back) with HRD..
> >>
> >> With the older versions, while looking at the DX cluster (HRD), I
> >> could
> >> mouse click on a spot and the K3 would QSY and stay there..
> >>
> >> Now (again) when I click it jumps to the new spot and right back to
> >> the
> >> original frequency.. Re-loaded 4.12 on the K3 and 0.31 P3 and
> >> everything
> >> worked OK.. Anyone else experiencing this..??
> >>
> >> de W4CCS
> >> ______________________________________________________________
> >> 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

W4CCS

Re: New Firmware Issues with K3

Hi Allen:

No, when I click on just a band change, all work as designed.. Problem
exist when I click on the spot in the DX cluster..

The problem started with the P3 roll out and I was able to adjust the
com port polling to get it to work but after the last firmware update,
nothing I adjust on the com port allowed it to work.

I reverted back to the older firmware and it started working OK again.
Something in the last version made it unhappy..

THANKS

de W4CCS

On 10/14/2010 12:36 PM, Alan Bloom wrote:

> Jim,
>
> Thanks for the clarification. So it only does it when changing bands
> using a DX cluster. Unfortunately the computer that I use for testing
> does not have an Internet connection. (For security reasons - it's has
> all my P3 development code which I really don't want to risk getting
> hacked.) So I can't test with a DX cluster. Does the problem occur if
> you change bands in HRD by clicking on a band button?
>
>
>> I tested with HRD's command tester (Tools-Command
>> Tester) and HRD reports an error response to the FA command.
>>
> I think that's just the way HRD works. Any time you send a command that
> has no response (most set commands) it reports an "Error" in the
> received column. I checked and it still does it with older K3 firmware
> (04.12) and no P3 connected.
>
> Alan N1AL
>
>
>
> On Thu, 2010-10-14 at 05:31 -0500, JAMES ROGERS wrote:
>
>> Alan,
>>
>> You have to double click on a HRD DX cluster spot that will change
>> the band to see it. That is the only way I can reproduce it here. It
>> will change the band and display the new frequency, then return to the
>> old band/frequency. I am running the latest firmware in the P3 and K3
>> (00.36 and 04.14). I tested with HRD's command tester (Tools-Command
>> Tester) and HRD reports an error response to the FA command.
>>
>> Jim, W4ATK
>>
>> On Oct 13, 2010, at 7:44 PM, Alan Bloom wrote:
>>
>>
>>> I don't see it here. Running P3 firmware 00.36, K3 version 04.14 and
>>> HRD version 5.0. I can mouse-click on a frequency in HRD and the K3
>>> QSYs normally and stays there. I can also QSY using the P3 markers
>>> and
>>> both the K3 and HRD are happy.
>>>
>>> Which software versions are you running?
>>>
>>> Does is only do it when you click on a DX cluster spot or does it also
>>> do it when you click on a frequency on the "dial" in the HRD screen?
>>>
>>> Alan N1AL
>>>
>>>
>>>
>>> On Wed, 2010-10-13 at 16:23 -0400, W4CCS wrote:
>>>
>>>> Loaded the new firmware updates for the K3 and P3 and now have issues
>>>> (until I reverted back) with HRD..
>>>>
>>>> With the older versions, while looking at the DX cluster (HRD), I
>>>> could
>>>> mouse click on a spot and the K3 would QSY and stay there..
>>>>
>>>> Now (again) when I click it jumps to the new spot and right back to
>>>> the
>>>> original frequency.. Re-loaded 4.12 on the K3 and 0.31 P3 and
>>>> everything
>>>> worked OK.. Anyone else experiencing this..??
>>>>
>>>> de W4CCS
>>>> ______________________________________________________________
>>>> 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
>>>
>
> ______________________________________________________________
> 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
>

The Smiths

Re: New Firmware Issues with K3

In reply to this post by Jim Rogers, W4ATK

i use HRD 5 beta with the latest version 3236 (I think, haven't looked) and I jump around the bands double clicking on both the cluster Text window, and the Graphic display window. I've never had any issues with it. Just used it last night too...

> From: [hidden email]
> To: [hidden email]
> Date: Thu, 14 Oct 2010 05:31:23 -0500
> CC: [hidden email]
> Subject: Re: [Elecraft] New Firmware Issues with K3
>
> Alan,
>
> You have to double click on a HRD DX cluster spot that will change
> the band to see it. That is the only way I can reproduce it here. It
> will change the band and display the new frequency, then return to the
> old band/frequency. I am running the latest firmware in the P3 and K3
> (00.36 and 04.14). I tested with HRD's command tester (Tools-Command
> Tester) and HRD reports an error response to the FA command.
>
> Jim, W4ATK
>
> On Oct 13, 2010, at 7:44 PM, Alan Bloom wrote:
>
> > I don't see it here. Running P3 firmware 00.36, K3 version 04.14 and
> > HRD version 5.0. I can mouse-click on a frequency in HRD and the K3
> > QSYs normally and stays there. I can also QSY using the P3 markers
> > and
> > both the K3 and HRD are happy.
> >
> > Which software versions are you running?
> >
> > Does is only do it when you click on a DX cluster spot or does it also
> > do it when you click on a frequency on the "dial" in the HRD screen?
> >
> > Alan N1AL
> >
> >
> >
> > On Wed, 2010-10-13 at 16:23 -0400, W4CCS wrote:
> >> Loaded the new firmware updates for the K3 and P3 and now have issues
> >> (until I reverted back) with HRD..
> >>
> >> With the older versions, while looking at the DX cluster (HRD), I
> >> could
> >> mouse click on a spot and the K3 would QSY and stay there..
> >>
> >> Now (again) when I click it jumps to the new spot and right back to
> >> the
> >> original frequency.. Re-loaded 4.12 on the K3 and 0.31 P3 and
> >> everything
> >> worked OK.. Anyone else experiencing this..??
> >>
> >> de W4CCS
> >> ______________________________________________________________
> >> 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
>
> ______________________________________________________________
> 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

The Smiths

Re: New Firmware Issues with K3

In reply to this post by Alan Bloom

Alan,

Even if you have no internet connection, you can still double click on the graphical display DX Cluster window. This is the one that sits Vertically in the window, as opposed to the Text version that sits horz. in the window pane. If you point and double click on the Freq. you want to QSY to, regardless if there's a DX station listed or not, you will QSY there. I use this all the time just to jump from band to band. However with all the newest software loaded I haven't found that it ever jumps back on me.
There are settings regarding the way you click to QSY with HRD's DX Cluster windows, maybe it has to do with a Single click Vs' double click mode???

> From: [hidden email]
> To: [hidden email]
> Date: Thu, 14 Oct 2010 09:36:36 -0700
> CC: [hidden email]
> Subject: Re: [Elecraft] New Firmware Issues with K3
>
> Jim,
>
> Thanks for the clarification. So it only does it when changing bands
> using a DX cluster. Unfortunately the computer that I use for testing
> does not have an Internet connection. (For security reasons - it's has
> all my P3 development code which I really don't want to risk getting
> hacked.) So I can't test with a DX cluster. Does the problem occur if
> you change bands in HRD by clicking on a band button?
>
> > I tested with HRD's command tester (Tools-Command
> > Tester) and HRD reports an error response to the FA command.
>
> I think that's just the way HRD works. Any time you send a command that
> has no response (most set commands) it reports an "Error" in the
> received column. I checked and it still does it with older K3 firmware
> (04.12) and no P3 connected.
>
> Alan N1AL
>
>
>
> On Thu, 2010-10-14 at 05:31 -0500, JAMES ROGERS wrote:
> > Alan,
> >
> > You have to double click on a HRD DX cluster spot that will change
> > the band to see it. That is the only way I can reproduce it here. It
> > will change the band and display the new frequency, then return to the
> > old band/frequency. I am running the latest firmware in the P3 and K3
> > (00.36 and 04.14). I tested with HRD's command tester (Tools-Command
> > Tester) and HRD reports an error response to the FA command.
> >
> > Jim, W4ATK
> >
> > On Oct 13, 2010, at 7:44 PM, Alan Bloom wrote:
> >
> > > I don't see it here. Running P3 firmware 00.36, K3 version 04.14 and
> > > HRD version 5.0. I can mouse-click on a frequency in HRD and the K3
> > > QSYs normally and stays there. I can also QSY using the P3 markers
> > > and
> > > both the K3 and HRD are happy.
> > >
> > > Which software versions are you running?
> > >
> > > Does is only do it when you click on a DX cluster spot or does it also
> > > do it when you click on a frequency on the "dial" in the HRD screen?
> > >
> > > Alan N1AL
> > >
> > >
> > >
> > > On Wed, 2010-10-13 at 16:23 -0400, W4CCS wrote:
> > >> Loaded the new firmware updates for the K3 and P3 and now have issues
> > >> (until I reverted back) with HRD..
> > >>
> > >> With the older versions, while looking at the DX cluster (HRD), I
> > >> could
> > >> mouse click on a spot and the K3 would QSY and stay there..
> > >>
> > >> Now (again) when I click it jumps to the new spot and right back to
> > >> the
> > >> original frequency.. Re-loaded 4.12 on the K3 and 0.31 P3 and
> > >> everything
> > >> worked OK.. Anyone else experiencing this..??
> > >>
> > >> de W4CCS
> > >> ______________________________________________________________
> > >> 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
>
>
> ______________________________________________________________
> 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

Alan Bloom

Re: New Firmware Issues with K3

In reply to this post by Alan Bloom

I finally got HRD set up on a computer connected to the Internet so I
can connect to a DX cluster. I was able to confirm the bug.

Turns out it has nothing to do with the P3 or the new K3 firmware. It
does it with no P3 connected and K3 version 04.12. Probably older
versions as well although I didn't try them.

The problem is that in HRD, when you double-click on a DX cluster spot
that is in a different band, HRD sends an FA command to change the K3
VFO A to the new band/frequency (which is fine) but then for some reason
it sends an FB command to re-set the VFO B to the old band/frequency.
That causes the K3 to do a band change back to the old band.

A work-around is to go into the K3 CONFIG menu and set VFO IND to YES.
That allows VFO A and VFO B to be on separate bands so that a band
change on VFO B does not cause VFO A to switch bands.

I'm going to contact the HRD designer to see if maybe there's some
setting in HRD to make it not do that.

Alan N1AL

On Thu, 2010-10-14 at 09:36 -0700, Alan Bloom wrote:

> Jim,
>
> Thanks for the clarification. So it only does it when changing bands
> using a DX cluster. Unfortunately the computer that I use for testing
> does not have an Internet connection. (For security reasons - it's has
> all my P3 development code which I really don't want to risk getting
> hacked.) So I can't test with a DX cluster. Does the problem occur if
> you change bands in HRD by clicking on a band button?
>
> > I tested with HRD's command tester (Tools-Command
> > Tester) and HRD reports an error response to the FA command.
>
> I think that's just the way HRD works. Any time you send a command that
> has no response (most set commands) it reports an "Error" in the
> received column. I checked and it still does it with older K3 firmware
> (04.12) and no P3 connected.
>
> Alan N1AL
>
>
>
> On Thu, 2010-10-14 at 05:31 -0500, JAMES ROGERS wrote:
> > Alan,
> >
> > You have to double click on a HRD DX cluster spot that will change
> > the band to see it. That is the only way I can reproduce it here. It
> > will change the band and display the new frequency, then return to the
> > old band/frequency. I am running the latest firmware in the P3 and K3
> > (00.36 and 04.14). I tested with HRD's command tester (Tools-Command
> > Tester) and HRD reports an error response to the FA command.
> >
> > Jim, W4ATK
> >
> > On Oct 13, 2010, at 7:44 PM, Alan Bloom wrote:
> >
> > > I don't see it here. Running P3 firmware 00.36, K3 version 04.14 and
> > > HRD version 5.0. I can mouse-click on a frequency in HRD and the K3
> > > QSYs normally and stays there. I can also QSY using the P3 markers
> > > and
> > > both the K3 and HRD are happy.
> > >
> > > Which software versions are you running?
> > >
> > > Does is only do it when you click on a DX cluster spot or does it also
> > > do it when you click on a frequency on the "dial" in the HRD screen?
> > >
> > > Alan N1AL
> > >
> > >
> > >
> > > On Wed, 2010-10-13 at 16:23 -0400, W4CCS wrote:
> > >> Loaded the new firmware updates for the K3 and P3 and now have issues
> > >> (until I reverted back) with HRD..
> > >>
> > >> With the older versions, while looking at the DX cluster (HRD), I
> > >> could
> > >> mouse click on a spot and the K3 would QSY and stay there..
> > >>
> > >> Now (again) when I click it jumps to the new spot and right back to
> > >> the
> > >> original frequency.. Re-loaded 4.12 on the K3 and 0.31 P3 and
> > >> everything
> > >> worked OK.. Anyone else experiencing this..??
> > >>
> > >> de W4CCS

ab2tc

Re: New Firmware Issues with K3

Hi,

This is interesting. I don't have this problem whether I have "VFO IND" turned on or not (normally I always have it on but turned it off just to test this. Now, I use an older version of HRD (4.1 build 2321) but I thought the rig control part hadn't changed at all). Also just for the record, I don't double click a DX spot, just a single click will do.

AB2TC - Knut

Alan Bloom wrote

I finally got HRD set up on a computer connected to the Internet so I
can connect to a DX cluster. I was able to confirm the bug.

Turns out it has nothing to do with the P3 or the new K3 firmware. It
does it with no P3 connected and K3 version 04.12. Probably older
versions as well although I didn't try them.

The problem is that in HRD, when you double-click on a DX cluster spot
that is in a different band, HRD sends an FA command to change the K3
VFO A to the new band/frequency (which is fine) but then for some reason
it sends an FB command to re-set the VFO B to the old band/frequency.
That causes the K3 to do a band change back to the old band.

A work-around is to go into the K3 CONFIG menu and set VFO IND to YES.
<snip>

ab2tc

Re: New Firmware Issues with K3

I forgot to mention that I have LP-Bridge v.9.980 between K3 and HRD and PowerSDR. Maybe that makes a difference.

AB2TC- KNut

ab2tc wrote

Hi,

This is interesting. I don't have this problem whether I have "VFO IND" turned on or not <snip>