CHIRP

Issues like this are almost always cause by the device driver installed in Windows not being compatible with the USB-to-Serial chip used in the programming cable (or sometimes the radio itself). It has noting to do with the CHIRP application itself.

I would suggest that you use the Windows Device Manager application to determine which chip is being used, then download and install the latest device driver from that chip vendor's website. The exception would be if it is a Prolific type chip. In that case, you must download, install and select the older Prolific v3.2.0.0 device driver.

See the "Miklor":https://www.miklor.com/ website's "Drivers and USB Cables":https://www.miklor.com/COM/UV_Drivers.php page for links to the various chip vendors drivers and related instructions.

Jim KC9HI

Jim,

You do understand that ICOM supply's the USB Serial Drivers for this Radio.
I have the latest USB Drivers and Firmware from Icom installed.
The drivers are from Silicon Labs. I don't know if they are written specifically for Icom.
I have POSTED this info on the IC-7300 Groups.io Website.

               73 de Steve KB6HOH

Hi Steve,

Do you understand that the ICOM IC-7300 has a CI-V port and a USB port. You didn't mention which method you were using. Access to the CI-V port would be through a cable with a USB-to-Serial adapter. Mine has a CH340 chip which uses a Windows driver from WCH.

I would speculate from your reply that you are connecting via the radio's USB port. That being the case, I went ahead and disconnected my Raspberry Pi to get it out of the way and then hooked up my Windows laptop to my IC-7300. I then upgraded CHIRP to the latest CHIRP daily build. My laptop has never been hooked up to my IC-7300 before, but it has programmed many radios using a programming cables that were manufactured with the Silicon Labs CP210x chip. That being the case I let Windows use the Silicon Labs driver that has been previously installed and didn't bother with installing the one that ICOM hosts on their website. I used Device Manager to determine that the IC-7300 was assigned COM5.

My first attempted download from the IC-7300 resulted in the same errors that you experienced. Since I was using the same USB cable that I use for FT8 I knew the USB cable was OK and I assumed that the SilLabs driver was OK, I speculated that the problem most likely was do to an incorrect setting in the IC-7300. I went through the IC-7300 settings one-by-one and decided it might be...

MENU -> (2) -> SET -> Connectors -> CI-V -> CI-V USB Port and changed its selection to *Link To [REMOTE]
*

After making that change, CHIRP read the memories from the IC-7300. I had never enter any memories before so all 99 were empty. I was able to key frequencies into CHIRP and they would show up in the IC-7300. Unfortunately if I keyed frequencies into the IC-7300 they didn't automatically show up in CHIRP. I had to close the IC-7300 tab and read from the radio again. So it appears that CHIRP's ICOM IC-7300 driver only offers very minimal support, it does work.

If you had to change CI-V USB Port to get this to work like I had to, don't forget to change it back when you are done. My digital modes won't work until I do.

Jim KC9HI

Jim,

Tnx for the info. I got the same results as you did BUT it does work.

Since I don't have a whole lot of freqs to load I guess I can suffer thru going from Link to Unlink.
I'm guessing NOT a whole lot of support for the IC-7300.

               73 de Steve KB6HOH