OpenGD77

Ummm

Possibly something defective in the radio.

But its difficult to know how the USB firmware update would work and the CPS USB connection not work.

Or perhaps it would no longer be possible to update the firmware, if you tried that again. e.g. broken cable or some internal connection problem on the sockets etc

davetheoldguy wrote: ↑

Tue Feb 09, 2021 2:21 am

**FIXED**

I believe it was the cable. I held down on the Kenwood connector and it must push it in a step farther. If I don't hold down on it, the connector pops out a step, obviously fouling the connection. Holding the cable in I am able to send codeplugs, etc. I will get new cable. Thanks for your help and sorry for the goose chase.

I am euphoric.

OK.

I've heard other people say they had to cut something away, I presume on the plug, rather than the radio, to make sure the cable fitted correctly.
And I know someone who has a loose internal connection on one of the sockets in the radio.

If its a dry joint on the socket, then a new cable isn't going to help.

You could dissassemble the radio and get to the back of the sockets fairly easily.
The only tricky part is the ribbon cable to the display.

You may even be able to get a soldering iron onto the back of the sockets without removing the ribbon cable etc, if someone else can help you hold the 2 halves of the radio.

I have a code plug write failure which is persistent.
Windows 10 - uninstalled the driver, re-installed (no difference). I am running the 3 Jan CPS.
I have updated the firmware without an issue to 19th Jan. I have made a couple of successful codeplug writes but I keep getting this error and the write fails. If I persevere, I finally get the write to work. I turn off the radio and turn it back on, I restart the CPS etc etc but I needed about 20 attempts to finally write the code plug (i.e. not get this error).
So it works finally but not reliable after this CPS update.
Further subsequent attempts to write (after a successful one) fail..

Umm.

I vaguely recall seeing an error a bit like that, a long time ago.

Did you try a uploading a blank codeplug to see if its related to your specific codeplug

hmm, well I have the radio the way I want ATM so I'd like not to be left with an empty radio. I will try that method next time I need to update the code plug.
Alan

what happens when you read the codeplug?

no problem reading - I can do it over and over no issue

Is the USB port USB 2 or 3 ?

How old is the radio? I recall some old ones having Write speed problems on the EEPROM

USB 3, Com Port is COM9
The radio is less than a year

the error message suggests a thread crash to me - one thread is getting ahead of where another expects it to be. Just something I tend to try in my thread code.. I look at the syncing and try a pause to test..