[chirp_users] MP-300

Jim Unroe
Thu Jan 19 02:22:29 PST 2017


On Wed, Jan 18, 2017 at 10:06 PM, Eric Chopin <echopin27 at gmail.com> wrote:
> Hello Jim,
>
> Yes, I also have a single cable unlike the Baofeng double variety, and I
> still get the same message... I have also tried with the manufacturers
> software that I downloaded from their website, in-fact they have 2
> versions..and no luck with either.
>
> I have just ordered ANOTHER cable that is specified as THE ONE for this
> radio...has not arrived yet... lets see what happens with this one! I am
> getting to the stage of introducing this radio to my friend...Winchester!!!
> ..If you know what I mean!!! Grrr
>
> 73's
> Eric

Eric,

Being it is a different cable than your working cable(s), there is a
chance that it has a different chip, and therefor the device driver
that is installed for it is incompatible. The programming cable can be
wired wrong (TXD and RXD are swapped).

The device driver is easy to check by going into Device Manager. If
the chip is recognized as a Prolific type chip, then the device driver
need to be v2.0.2.1 (XP) or v3.2.0.0 (Vixta, 7, 8.x and 10). If it
isn't any you had previously downgraded it, you just have to reselect
it.

I have multiple Prolific device driver versions installed in my
Windows 7 computer and switch between at will to determine if the the
chips in my cables are genuine or not (most are not).

If you new programming cable as an FTDI based chip, you can use the
latest driver from the ftdichip.com website. If you purchased another
Prolific chip based programming, the Windows device driver must be
rolled back to the older, compatible device driver. Links to the
required older, compatible Prolific driver are available on the
miklor.com website.

Jim KC9HI
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ProlificDrivers2.jpg
Type: image/jpeg
Size: 161541 bytes
Desc: not available
Url : http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20170119/82de5898/attachment.jpg 


More information about the chirp_users mailing list