I think the device manager only looks at the USB "manufacture ID" value of the chip in the product, while the driver looks for a particular serial number sequence or something similar.  The chip manufacturers, like FTDI and Prolific, are just trying to protect their IP (intellectual property) so the cloners don't rip them off.  I was an embedded systems and software engineer for 40 years, retiring last year.  There is a software tool that FTDI used to have on their website that could be used to check if the product was using a genuine FTDI or clone chip.  I've had the Linux version of the tool for many years, so haven't had a reason to see if it's still available.

Larry AC8YE

On Mon, Jul 23, 2018 at 5:19 PM, randy true <w4rttrandy@outlook.com> wrote:

If device manager says it is an FTDI chip, is it genuineb but maybe older?

Is this what a genuine chips shows as?

I assume something like an RT cable is the best?


Randy W4RTT



From: chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com> on behalf of Larry Howell <larry.howell.47@gmail.com>
Sent: Monday, July 23, 2018 9:57 AM

To: Discussion of CHIRP
Subject: Re: [chirp_users] ft897
 
Randy,

A similar situation also exists with cable using FTDI USB-to-serial chips.  This is another case of a cable manufacturer using a clone (counterfeit) chip instead of a genuine FTDI chip, and FTDI drivers for several years have not worked with the clone chips.  I don't know if an older FTDI driver can be found that will use the clone chip, but other Chirp users may be able to guide you.  As soon as I receive a new cable I check it to be sure it used a genuine FTDI chip.  If it's a clone chip, I return the cable to the vendor.

Larry AC8YE

On Sun, Jul 22, 2018 at 11:33 PM, randy true <w4rttrandy@outlook.com> wrote:

Device manager says FTDI.


Randy W4RTT



From: chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com> on behalf of Larry Howell <larry.howell.47@gmail.com>
Sent: Sunday, July 22, 2018 11:03 PM
To: Discussion of CHIRP
Subject: Re: [chirp_users] ft897
 
When and why Microsoft chooses to do things is a great mystery.  If Device Manager shows your cable to be a Prolific cable, try rolling your driver back to 3.2.0.0. Info found at www.miklor.com.
Miklor Radio Information Site - Miklor
www.miklor.com
outdoors hunting camping SHTF GMRS radio communications antenna battery electronics scanners digital computer software hardware laptop iPad iPhone eBay music radio


Larry AC8YE

On Sun, Jul 22, 2018 at 10:22 PM, randy true <w4rttrandy@outlook.com> wrote:

The OS is Win 7 with updates enabled, but I have been using Chirp for over a year with no hassles. What should the correct driver be?


Randy W4RTT



From: chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com> on behalf of Larry Howell <larry.howell.47@gmail.com>
Sent: Sunday, July 22, 2018 7:01 PM
To: Discussion of CHIRP
Subject: Re: [chirp_users] ft897
 
Hi Randy,

You didn't say which OS your computer runs, so I''l assume it's Windows.  If you have it set to install updates automatically, or the OS is Windows 10, then Microsoft has probably replaced the driver with a different one that doesn't like the cable.  This typically occurs with cables that use the Prolific USB-serial chips.  Many cheap cable use clone chips that newer drivers detect and will ignore because they aren't Prolific chips.

Larry AC8YE

On Sun, Jul 22, 2018 at 6:27 PM, randy true <w4rttrandy@outlook.com> wrote:

Chirp has suddenly stopped communicating with my 897.

I have checked all com port settings in the program/computer/and radio All are OK.

The 897 will still work with other programs on the same com port.

Rebooted, no jot.

Should I try and reset the radio?


Randy W4RTT


_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to larry.howell.47@gmail.com at larry.howell.47@gmail.com
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com


_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to larry.howell.47@gmail.com at larry.howell.47@gmail.com
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com


_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to larry.howell.47@gmail.com at larry.howell.47@gmail.com
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com


_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to larry.howell.47@gmail.com at larry.howell.47@gmail.com
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com