开云体育

Ray . . .


On Fri, 9 Aug 2024 14:20:21 -0400, "Ray, W4BYG" <w4byg@...> wrote:

Not sure how to proceed from here. Is there anyone who can help me get the radio talking to the PC?

We'll wait for someone who has had problem with that particular radio
to reply, but is the radio supported in CHIRP-Next? If so, do you get
the same error using it instead?

I've had no problems with legacy CHIRP with my Baofeng HT not
CHIRP-Next with my older Icom HT. Knowing it works fine for me is of
no help to you, other than indicating the legacy and the next versions
is working with some radios.

Let me ask some questions that you likely would check all the boxes on
and agree that you did it correctly. Some of these you already said
you did, if I read it correctly.

I'm going with the directions I can easily find online:



You indicated that you identified the radio in the software and
selected Com4.

Do you know that the driver is using COM 4 for a certainty?

What does Device Manager show under PORTS and that are the properties
for the Prolific driver for your Prolific cable?

Did your driver get installed by Windows or did you do it manually?

Are you sure you don't have a FDTI or a WCH (CH340/314) cable and
you're using the wrong driver?

If you have a Prolific cable, is it a fake or a real Prolific? Fake
ones are recognized by the driver software and won't work. I've had no
problems with any FDTI or WCH cable. The latter ones are cheaper but
you have to search for the driver if it doesn't come with it, but it's
not hard to find. I have one with maybe 10 connectors that allow me to
program nearly any radio by choosing the correct end(s).

You can reassign the COM port if there's a conflict, and once you get
it working you can assign it to a COM port of 15 or higher to keep
Windows Update from reassigning your port during an update.
Lower-numbered COM ports are somewhat dynamic in this respect;
otherwise they will remain unchanged until something changes it,
either Windows Update or you, or possibly some other event. If you
reassign a COM port to a device driver, you will need to restart your
software, and possibly restart everything.

COM port is everything here. If you're using a COM port that's
different than the one the cable driver is using, it may say CLONING
but it won't be able to do it. I think I've seen that happen before
with the wrong COM port.

Did you put the RADIO into CLONE mode? I have to do that on my mobile
FT-8800R. (You said you did this.)

You said, "I rebooted the PC with the radio connected, but off." The
YouTube video has the radio on at the beginning of the video.

Near the end of your email you agreed with what you said earlier and
said you have a Prolific cable:

" 'Devices and Printers' and 'Device manager' both confirm the
Prolific is recognized at port 4 and reported as working OK. I checked
to see if there was an update for the driver. It is current."

Current or not, if this is the case (a possible alternative solution
is shown below), I recommend getting an FDTI cable and trying with
that one. There are reports of many fake Prolific cables that don't
work with the official driver. You can research and possibly find the
old driver that does work with the fake cables, as I understand they
changed the driver after a certain date. I've also read where FDTI was
doing the same thing, so here's what I can find on the Prolific
chip/cables:

===========================================
Prolific Chipset

Nearly every programming cable that is detected by Windows as having a
Prolific chip was manufactured with an unauthorized or cloned copy of
the Prolific PL2303HXA chip. The latest driver installed by Windows
(Vista, 7, 8.1 and 10) is not compatible with these chips. The last
compatible Prolific driver was v3.3.2.105 [27/10/2008].

Windows may attempt to automatically load the Prolific driver
3.6.xx.xxx when inserting your cable. When opening Device Manager, the
Yellow Caution Triangle may not appear, however, when the cable is
inserted into the radio, the transmitter will turn on. This should not
occur. It was done to prevent use of the cloned chip. More detail can
be found Here.

If this occurs, you Must backdate your driver to 3.2.0.0
============================================



According to the web page above, you can try this PL driver version
3.2.0.0:



Check for viruses. I installed it and got no viruses found by my AV
software. Keep a copy of it handy if you use it since Windows Update
likely will "update" it to the current version.

Some more information on the overall FAKE chipset problem in those
cables:



(pl2303)-usb-serial-adapters/
You may need to copy and paste the above link since my email client
doesn't recognize anything from the "(" onward. The link to the
Prolific FAQ from that web page is broken but the #3 part under the
FAQ said at one time that this was their chip validity and support
issue. My take on that is that they don't want to have to support fake
chips, but it also is a way to encourage buying the real thing.



So since you already have what purports to be a Prolific chip in your
cable, try the old driver and see if the Windows-Vista-era drivers
will work with your cable If it does, then you likely have a rip-off
fake cable. But if it works, then why not keep it? Make the driver use
COM port 15 or higher and hope Windows won't update it. Use the old
driver again if it does indeed update it anyway.

The type of cable I have is what I call the octopus:



I also have the official Baofeng cable and one for my FT-8800R. The
latter came with the RT Systems programming software and cable when I
bought the radio used.

Hope you get it working.


Donald KX8K


----------------------------------------------------
Some ham radio groups you may be interested in:
/g/ICOM /g/Ham-Antennas
/g/HamRadioHelp /g/Baofeng
/g/CHIRP