Icom: ICOM IC-2730; problem loading a Sillicon Labs USB driver

[videobruce]

I called Icom and they are claiming the problem loading the driver(s) then using a 3rd party USB cable (supposed using a different 'chip') inside the USB plug end is the problem.

Problem with that claim, I did this 2 years ago using W7 and it worked. Same PC, this time I have both O/S's (on different SSD's, I'm tiring to stay away from W7, but I did try it, same thing.

The .exe goes thru it's steps, shows the driver is loaded, but Device Manage doesn't shoe it. When I connect the radio, the entry for Com 1 gives me a error. I even tried a .inf file (which I prefer using) within DM, bur the O/S claims the current driver (which is a M$ driver) is up to date.

One question; when will DM show the SI driver? before the radio is connected, or after? It's been over 2 years since I when thru this mess. I am using Icom's software!

 

[K6GBW]

For mine I downloaded the USB drive directly from Icom, went to device manager and pointed it to the new driver. I had no issues after that, but then this is on W11.

 

[videobruce]

I did go to Icom's Japan site (which was the one the support guy recommend and get the program and the drivers.
The .exe claimed was loaded (which wasn't), the.inf failed using DM.

Did you confirm that using DM? If so, did you look before you connected the radio or after? Also, what cable did you use?
Under what entry did the driver show?

I should of added, I was using W10.

 

[K6GBW]

CS-2730 | Firmware Download | Icom America.

Icom,America,Land Mobile,Marine,Aviation,Amateur,Network,Systems

www.icomamerica.com

If you are using a US version make sure you get the software from here and make sure to read the installation instructions. You can print it and it walks you through installation. If you follow it exactly it shouldn't be a problem.

 

[videobruce]

This is what DM shows.
The support guy told me to get the drivers from the Japan site! When I ran the S/W, Assigning the Com Port was the issue. Com1 was the only choice, but I forgot what the screen showed.

 

[AK9R]

If you are using a 3rd party cable, you will have to use the driver for that cable. AFAIK the driver on Icom's website is for the Silicon Labs chip that is in Icom radios that have a USB port.

ETA: The only software on the Icom America site for the IC-2730 is the cloning software. There is no driver software because that radio does not have an internal USB chip.

More ETA: For reliable programming cables, go to Blue Max 49ers or Valley Enterprises.

 

[videobruce]

I have no idea what/where I got the cable from, it's not Icoms, all I remember 2 years ago it worked on W7 which it doesn't now. And it's thew same Tower other than the SSD's. The support guy did say there is a chip in the USB connector. It seemed that he stated the 3rd party cables don't have any chip, unless I misunderstood him.

But by question still stands; when do you 'see' this driver in DM, or does it only show when the radio is connected??

 

[AK9R]

I have no idea what/where I got the cable from

If it were me, I'd get a programming cable for your radio from a known source who can provide you with the proper driver.

ICOM IC-2730A FTDI Programming Cable OPC-i478

https://www.valley-ent.com/store/ic...y-radio-programming-cable.html?search=Ic-2730

Since the chip is in the cable, the port will not appear in Device Manager until the driver is installed and the cable is plugged in.

 

[kg4ehv]

Hard to beat the RT systems cable and SW.

 

[videobruce]

Then why did it work 2 years ago??

 

[AK9R]

Don't know. Don't care. I wouldn't spend a lot of time trying to get an old cable from an unknown source working. Cut your losses and get a new cable.

 

[videobruce]

AFAIC, it's not the cable, it's the lack of the correct driver. Windows sees the cable and correctly ID's what it is.
Thanks for you answering my question;

Since the chip is in the cable, the port will not appear in Device Manager until the driver is installed and the cable is plugged in.

Then why when I do try to install that SL driver, the installer claims it's installed?

The real problem is Icom not providing a true internal USB port instead of using some ancient 'stereo audio' socket which is all that 3 pin jack is, then forcing one to spend another $40 or so dollars for their cable.

 

[devicelab]

Then why did it work 2 years ago??

Microsoft started enforcing developers to write better drivers for Windows.

 

[videobruce]

M$, the "driver police"?? They need to 'police' their own house first and stop changing things that have been around for years and actually worked.

After some additional snooping around, the apparent reason it worked is did have the correct driver which was not SL and loaded that for the 3rd party USB cable.

 

[videobruce]

I looked over my older files for this and found reference to Prolific which rang a bell.
That was/is the chipset that is in the cable. I looked for the driver, but for some reason it wasn't there.

I did a search and found a few different versions. It took me a while, the result is attached.
Also, I found this article;

Cables & Drivers - Prolific & FTDI

Cables & Drivers - Prolific & FTDI

www.miklor.com

THERE IS NOTHING WRONG WITH THE CABLE, never was !!!!

AFA all of this crap with M$ and updates locking out the certain driver versions, that doesn't happen when one turns/disables off auto updates!! Proof is in the attachment. BTW, this is W10 Pro x64 if that matters.
So far I 'read' the radio and have the programed frequencies in my Desktop, working on adding another set of frequencies (business, not Amateur).

 

[AK9R]

Problem solved. Thread locked.