Elecraft

K3/Logger 32 Interface issue

Classic

List

Threaded

7 messages Options

Denis Jackson-2

K3/Logger 32 Interface issue

Just installed a new shack PC, with I7 processor, Haswel chipset,, and WIN 7
64 Bit OS.

Using an older KUSB, with the Prolific chip set. K3 has a SteppIR
controller connected to it, using a Y cable. This combination works fine,
on my old PC, which has a COM port on the motherboard.

When I first set it up, the K3 communicated with Logger 32 without any
problems. However, after a few miniutes, (or a couple of band-changes on
the K3, Logger32 appears to no longer be receiving data from the K3. I can
control the k3 from Logger32, i.e. I can change bands etc, but I have no
indication of mode or frequency back from the radio. The only way I can get
it working again, is to unplug/re-plug the KUSB and the PC.

I don't think that this is a configuration options issue (although would be
happy for someone to tell me that it is), and suspect this is just another
manifestation of the endless USB/serial adaptor problems that seem to be all
too frequent. I will probably order myself a PCI serial card, but in the
meantime, if anyone has any ideas of what I could try, I would be very
grateful. I've already tried disabling the power management features on the
internal USB hub, with no luck.

Thanks in advance

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

Fred Smith-2

Re: K3/Logger 32 Interface issue

The processor and Win 7 64 isn't a problem I would guess the Prolific chip
set or your software are the most suspect. I have been using nothing but USB
inputs for the last 6 to 8 yrs if not more and no issues except for software
and drivers.

73,
Fred/N0AZZ
K3 Ser # 6730--KX3 # 5210--K2/100 # 6470-KAT100
P3/SVGA--KAT500--W2
Amps Elecraft KPA500 HF/6m--Alpha's 9500 HF--87A HF--Mirage B-5030-G
300+w--(2) B-5016-G's 165w 2m

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Denis Jackson
Sent: Friday, November 22, 2013 1:31 PM
To: [hidden email]
Subject: [Elecraft] K3/Logger 32 Interface issue

Just installed a new shack PC, with I7 processor, Haswel chipset,, and WIN 7
64 Bit OS.

Using an older KUSB, with the Prolific chip set. K3 has a SteppIR
controller connected to it, using a Y cable. This combination works fine,
on my old PC, which has a COM port on the motherboard.

When I first set it up, the K3 communicated with Logger 32 without any
problems. However, after a few miniutes, (or a couple of band-changes on
the K3, Logger32 appears to no longer be receiving data from the K3. I can
control the k3 from Logger32, i.e. I can change bands etc, but I have no
indication of mode or frequency back from the radio. The only way I can get
it working again, is to unplug/re-plug the KUSB and the PC.

I don't think that this is a configuration options issue (although would be
happy for someone to tell me that it is), and suspect this is just another
manifestation of the endless USB/serial adaptor problems that seem to be all
too frequent. I will probably order myself a PCI serial card, but in the
meantime, if anyone has any ideas of what I could try, I would be very
grateful. I've already tried disabling the power management features on the
internal USB hub, with no luck.

Thanks in advance

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
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.3426 / Virus Database: 3629/6854 - Release Date: 11/21/13

______________________________________________________________
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

Mike Reublin

Re: K3/Logger 32 Interface issue

In reply to this post by Denis Jackson-2

Ditch the Prolific adapter and get one with the FTDI chip. And of course the proper driver.

73, Mike NF4L

On Nov 22, 2013, at 2:31 PM, Denis Jackson <[hidden email]> wrote:

> Just installed a new shack PC, with I7 processor, Haswel chipset,, and WIN 7
> 64 Bit OS.
>
>
>
> Using an older KUSB, with the Prolific chip set. K3 has a SteppIR
> controller connected to it, using a Y cable. This combination works fine,
> on my old PC, which has a COM port on the motherboard.
>
>
>
> When I first set it up, the K3 communicated with Logger 32 without any
> problems. However, after a few miniutes, (or a couple of band-changes on
> the K3, Logger32 appears to no longer be receiving data from the K3. I can
> control the k3 from Logger32, i.e. I can change bands etc, but I have no
> indication of mode or frequency back from the radio. The only way I can get
> it working again, is to unplug/re-plug the KUSB and the PC.
>
>
>
> I don't think that this is a configuration options issue (although would be
> happy for someone to tell me that it is), and suspect this is just another
> manifestation of the endless USB/serial adaptor problems that seem to be all
> too frequent. I will probably order myself a PCI serial card, but in the
> meantime, if anyone has any ideas of what I could try, I would be very
> grateful. I've already tried disabling the power management features on the
> internal USB hub, with no luck.
>
>
>
> Thanks in advance
>
>
>
> 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

______________________________________________________________
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

Mike Furrey

Re: K3/Logger 32 Interface issue

What Mike and Fred said. Also look for cables that are shielded. I
unknowingly started with a prolific chipset and after loading the driver,
the laptop with Win7 functioned so bad, I had to reload the OS. I found a
FTDI unit and it works fine BUT the noise level dramatically increased until
I replaced them with shielded units. BTW, I have noted that when the
prolific chipset is used, it rarely mentioned on the box or by the
manufacture. I have also noted that when the FTDI chipset is used, the
box/manufacture always does indicate such! Hmmmmmm ...

My Experiences ...

73, Mike WA5POK

--------------------------------------------------

> Ditch the Prolific adapter and get one with the FTDI chip. And of course
> the proper driver.
>
> 73, Mike NF4L
>
> On Nov 22, 2013, at 2:31 PM, Denis Jackson <[hidden email]> wrote:
>
>> Just installed a new shack PC, with I7 processor, Haswel chipset,, and
>> WIN 7
>> 64 Bit OS.
>>
>>
>>
>> Using an older KUSB, with the Prolific chip set. K3 has a SteppIR
>> controller connected to it, using a Y cable. This combination works
>> fine,
>> on my old PC, which has a COM port on the motherboard.
>>
>>
>>
>> When I first set it up, the K3 communicated with Logger 32 without any
>> problems. However, after a few miniutes, (or a couple of band-changes on
>> the K3, Logger32 appears to no longer be receiving data from the K3. I
>> can
>> control the k3 from Logger32, i.e. I can change bands etc, but I have no
>> indication of mode or frequency back from the radio. The only way I can
>> get
>> it working again, is to unplug/re-plug the KUSB and the PC.
>>
>>
>>
>> I don't think that this is a configuration options issue (although would
>> be
>> happy for someone to tell me that it is), and suspect this is just
>> another
>> manifestation of the endless USB/serial adaptor problems that seem to be
>> all
>> too frequent. I will probably order myself a PCI serial card, but in the
>> meantime, if anyone has any ideas of what I could try, I would be very
>> grateful. I've already tried disabling the power management features on
>> the
>> internal USB hub, with no luck.
>>
>>
>>
>> Thanks in advance
>>
>>
>>
>> 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
>
>
> ______________________________________________________________
> 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

Mike Furrey

Re: K3/Logger 32 Interface issue

In reply to this post by Denis Jackson-2

--------------------------------------------------
From: <[hidden email]>
Sent: Friday, November 22, 2013 5:21 PM
Cc: "Elecraft Reflector" <[hidden email]>
Subject: Re: [Elecraft] K3/Logger 32 Interface issue

> What Mike and Fred said. Also look for cables that are shielded. I
> unknowingly started with a prolific chipset and after loading the driver,
> the laptop with Win7 functioned so bad, I had to reload the OS. I found a
> FTDI unit and it works fine BUT the noise level dramatically increased
> until I replaced them with shielded units. BTW, I have noted that when the
> prolific chipset is used, it rarely mentioned on the box or by the
> manufacture. I have also noted that when the FTDI chipset is used, the
> box/manufacture always does indicate such! Hmmmmmm ...
>
> My Experiences ...
>
> 73, Mike WA5POK
>
> --------------------------------------------------
>
>> Ditch the Prolific adapter and get one with the FTDI chip. And of course
>> the proper driver.
>>
>> 73, Mike NF4L
>>
>> On Nov 22, 2013, at 2:31 PM, Denis Jackson <[hidden email]> wrote:
>>
>>> Just installed a new shack PC, with I7 processor, Haswel chipset,, and
>>> WIN 7
>>> 64 Bit OS.
>>>
>>>
>>>
>>> Using an older KUSB, with the Prolific chip set. K3 has a SteppIR
>>> controller connected to it, using a Y cable. This combination works
>>> fine,
>>> on my old PC, which has a COM port on the motherboard.
>>>
>>>
>>>
>>> When I first set it up, the K3 communicated with Logger 32 without any
>>> problems. However, after a few miniutes, (or a couple of band-changes
>>> on
>>> the K3, Logger32 appears to no longer be receiving data from the K3. I
>>> can
>>> control the k3 from Logger32, i.e. I can change bands etc, but I have no
>>> indication of mode or frequency back from the radio. The only way I can
>>> get
>>> it working again, is to unplug/re-plug the KUSB and the PC.
>>>
>>>
>>>
>>> I don't think that this is a configuration options issue (although would
>>> be
>>> happy for someone to tell me that it is), and suspect this is just
>>> another
>>> manifestation of the endless USB/serial adaptor problems that seem to be
>>> all
>>> too frequent. I will probably order myself a PCI serial card, but in
>>> the
>>> meantime, if anyone has any ideas of what I could try, I would be very
>>> grateful. I've already tried disabling the power management features on
>>> the
>>> internal USB hub, with no luck.
>>>
>>>
>>>
>>> Thanks in advance
>>>
>>>
>>>
>>> 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
>>
>>
>> ______________________________________________________________
>> 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
>

Joe Subich, W4TV-4

Re: K3/Logger 32 Interface issue

In reply to this post by Mike Furrey

One can search Prolific's support site for alternate drivers and
try them all until finding one that works. There is no guarantee
that one will find a solution but I would start here:

Others have reported some success by getting drivers directly from
Prolific:
http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41

It may be necessary to log into the support site and try multiple
drivers until finding one that works with your cable/computer.

An alternate driver mentioned on the N1MM list at one time was:
http://www.valley-ent.com/soft/radio/PL2303Vista3200.exe
I have no idea if it is still available or is applicable to your
particular operating system.

The entire issue is *timing* - the nonfunctional drivers issue the
"character received" interrupt before making the character ready for
the application. The application (Microsoft Communications Toolbox)
then faults with the 8020 error. Software such as N1MM Logger,
Logger32, DXLab Suite, etc. are written in VB6 - one of those languages
that is part of the Microsoft "Visual" development environment and uses
the Microsoft Communications Toolbox. Other compilers - most notably
some of the independent C and C++ packages - are either slower to read
characters from the USB driver or perform multiple reads to get the
data when receiving a "no data available" error.

73,

... Joe, W4TV

On 11/22/2013 5:21 PM, [hidden email] wrote:

> What Mike and Fred said. Also look for cables that are shielded. I
> unknowingly started with a prolific chipset and after loading the
> driver, the laptop with Win7 functioned so bad, I had to reload the OS.
> I found a FTDI unit and it works fine BUT the noise level dramatically
> increased until I replaced them with shielded units. BTW, I have noted
> that when the prolific chipset is used, it rarely mentioned on the box
> or by the manufacture. I have also noted that when the FTDI chipset is
> used, the box/manufacture always does indicate such! Hmmmmmm ...
>
> My Experiences ...
>
> 73, Mike WA5POK
>
> --------------------------------------------------
>
>> Ditch the Prolific adapter and get one with the FTDI chip. And of
>> course the proper driver.
>>
>> 73, Mike NF4L
>>
>> On Nov 22, 2013, at 2:31 PM, Denis Jackson <[hidden email]> wrote:
>>
>>> Just installed a new shack PC, with I7 processor, Haswel chipset,,
>>> and WIN 7
>>> 64 Bit OS.
>>>
>>>
>>>
>>> Using an older KUSB, with the Prolific chip set. K3 has a SteppIR
>>> controller connected to it, using a Y cable. This combination works
>>> fine,
>>> on my old PC, which has a COM port on the motherboard.
>>>
>>>
>>>
>>> When I first set it up, the K3 communicated with Logger 32 without any
>>> problems. However, after a few miniutes, (or a couple of
>>> band-changes on
>>> the K3, Logger32 appears to no longer be receiving data from the K3.
>>> I can
>>> control the k3 from Logger32, i.e. I can change bands etc, but I have no
>>> indication of mode or frequency back from the radio. The only way I
>>> can get
>>> it working again, is to unplug/re-plug the KUSB and the PC.
>>>
>>>
>>>
>>> I don't think that this is a configuration options issue (although
>>> would be
>>> happy for someone to tell me that it is), and suspect this is just
>>> another
>>> manifestation of the endless USB/serial adaptor problems that seem to
>>> be all
>>> too frequent. I will probably order myself a PCI serial card, but in
>>> the
>>> meantime, if anyone has any ideas of what I could try, I would be very
>>> grateful. I've already tried disabling the power management features
>>> on the
>>> internal USB hub, with no luck.
>>>
>>>
>>>
>>> Thanks in advance
>>>
>>>
>>>
>>> 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
>>
>>
>> ______________________________________________________________
>> 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
>

Denis Jackson-2

Re: K3/Logger 32 Interface issue

In reply to this post by Mike Reublin

Hi to all,

In addition to the replies sent via the reflector, Sam, K5OAI sent me some
interesting info on USB power save settings. I had adjusted some USB power
settings, but some of those in the links he sent were new to me. The bad
news is that they didn't actually make any difference, but I learned a
little more about Win 7 so worthwhile just for that.

I have though made a little progress. All the RS232 cables are shielded.
It's something to do with having the SteppIR controller in the mix. If I
disconnect the RS232 Y cable, from the controller, the problem goes away. I
put the whole lot back on the old PC and it still works fine, so I'm pretty
sure it's something about the new PC that's causing the problems. If I
don't change bands, Logger will quite happily report accurate frequency and
mode as I tune around. If I change bands a few times, and specifically, if
I change bands using the band switch on the K3, Logger32 will stop reporting
frequency. Using the RS232 monitor utility in Logger, I can see the If;
polling message going to the K3/SteppIR controller, but nothing being
received.

Anyhow, on the basis that my PC has plenty of spare slots, I've ordered a
Serial card. I'd quite like to get the USB combination working though, so I
will try the various alternative Prolific drivers, as several folks have
kindly suggested, and then maybe try an FTDI adaptor and see whether that
works.

Thanks for all the help and advice. Very much appreciated.

73

Denis

MW0CBC / GW8OQV

-----Original Message-----
From: Mike Reublin [mailto:[hidden email]]
Sent: 22 November 2013 20:54
To: Denis Jackson
Cc: Elecraft Reflector
Subject: Re: [Elecraft] K3/Logger 32 Interface issue

Ditch the Prolific adapter and get one with the FTDI chip. And of course the
proper driver.

73, Mike NF4L

On Nov 22, 2013, at 2:31 PM, Denis Jackson <[hidden email]> wrote:

> Just installed a new shack PC, with I7 processor, Haswel chipset,, and
> WIN 7
> 64 Bit OS.
>
>
>
> Using an older KUSB, with the Prolific chip set. K3 has a SteppIR
> controller connected to it, using a Y cable. This combination works
> fine, on my old PC, which has a COM port on the motherboard.
>
>
>
> When I first set it up, the K3 communicated with Logger 32 without any
> problems. However, after a few miniutes, (or a couple of band-changes
> on the K3, Logger32 appears to no longer be receiving data from the
> K3. I can control the k3 from Logger32, i.e. I can change bands etc,
> but I have no indication of mode or frequency back from the radio.
> The only way I can get it working again, is to unplug/re-plug the KUSB and

the PC.

>
>
>
> I don't think that this is a configuration options issue (although
> would be happy for someone to tell me that it is), and suspect this is
> just another manifestation of the endless USB/serial adaptor problems
> that seem to be all too frequent. I will probably order myself a PCI
> serial card, but in the meantime, if anyone has any ideas of what I
> could try, I would be very grateful. I've already tried disabling the
> power management features on the internal USB hub, with no luck.
>
>
>
> Thanks in advance
>
>
>
> 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