[Elecraft] K3/Logger 32 Interface issue

[mikefurrey at att.net]

--------------------------------------------------
From: <mikefurrey at att.net>
Sent: Friday, November 22, 2013 5:21 PM
Cc: "Elecraft Reflector" <elecraft at mailman.qth.net>
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 <radio at modesgate.com> 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:Elecraft at mailman.qth.net
>>>
>>> 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:Elecraft at mailman.qth.net
>>
>> This list hosted by: http://www.qsl.net
>> Please help support this email list: http://www.qsl.net/donate.html
>