Bug #8527
openKenwood TK760G-1 Cannot read and program
0%
Description
Hello , i have a Kenwood TK760G-1 got a KPG-46 cable for it , the drivers are fine , so when im trying to read it in Chirp and i get an error : Incorrect model ID , got M7600, it not contains M7600
I came across a thread here "https://chirp.danplanet.com/issues/3349" , and applied the "tk760g.py" fix in developer mode but i get another error : The radio doesn't accept program mode
I tried to find some firmware files for this unit , but searched on everywhere and cannot find a single firmware, i thougt it will help...
I just dont know what else to do :(
Files
| debug ( with custom driver ).log (29.9 KB) debug ( with custom driver ).log | |||
| debug ( without custom driver).log (27.5 KB) debug ( without custom driver).log | |||
| 20201209_015212.jpg (1.09 MB) 20201209_015212.jpg | |||
| tk760g(m7600).py (54 KB) tk760g(m7600).py | Hacked driver to recognize TK760G-1 | ||
| ERROR 52.JPG (167 KB) ERROR 52.JPG |
Updated by Jim Unroe over 3 years ago
- Status changed from New to Feedback
It would assist if you would attach a debug.log file saved after trying to download from the radio without the custom driver. And another debug.log file saved after trying to download from the radio with the custom driver.
Jim KC9HI
Updated by Ortan Roland over 3 years ago
- File debug ( with custom driver ).log debug ( with custom driver ).log added
- File debug ( without custom driver).log debug ( without custom driver).log added
- File 20201209_015212.jpg 20201209_015212.jpg added
Hello and thankyou for the reply , i have uploaded now the 2 debug files you asked one without custom drive and one with , also a picture with the back of the Kenwood TK760G
Updated by Jim Unroe over 3 years ago
- File tk760g(m7600).py tk760g(m7600).py added
- Platform changed from Windows to All
Ortan Roland wrote:
Hello and thankyou for the reply , i have uploaded now the 2 debug files you asked one without custom drive and one with , also a picture with the back of the Kenwood TK760G
Thank you for the debug.log files and the picture. They were all helpful.
First things first, I don't know what the changes were in the "custom" driver, but whatever they are, the driver does not communicate with your radio. So there is no need for you to mess with it any further.
The good news is the current driver does "talk" to your radio. The problem is that your radio responds to the request to begin cloning with the TYPE "m7600" and CHIRP expects the TYPE "M7600" (upperCASE "M").
So what would be nice would be if Pavel Milanes, CO7WT, (the driver author) would take on this issue and update this driver to support your radio. He would be more qualified to make the permanent changes necessary to support your radio.
In the mean time, I think I have hacked the driver so that if you load it as a "driver module", it will (I hope) recognize your radio. At least you can give it a try. I always recommend that you save the first successful download, unedited, as a CHIRP Radio Images (*.img) file to be kept in a safe place as a backup.
Let me know what happens.
Jim KC9HI
Updated by Ortan Roland over 3 years ago
- File ERROR 52.JPG ERROR 52.JPG added
Hello sir ,the driver that you modified i confim indeed that it works, good job !!! , now i can connect to the radio , i can modify , but when i upload to the radio it gives me an error " Bad checksum in block 52 write "
But it does save the stuff that i add to the radio , is that error a problem or i can ignore it ?
Uploaded another picture with the error.
Updated by Jim Unroe over 3 years ago
Ortan Roland wrote:
Hello sir ,the driver that you modified i confim indeed that it works, good job !!! , now i can connect to the radio , i can modify , but when i upload to the radio it gives me an error " Bad checksum in block 52 write "
But it does save the stuff that i add to the radio , is that error a problem or i can ignore it ?
Uploaded another picture with the error.
Hi Ortan,
I'm sorry, but I wouldn't have any idea what the issue is. I don't own or otherwise have any experience with using or programming commercial Kenwood radios. My recommendation would be to contact Pavel and see if he would take on this issue and make the required modifications to the current driver to properly support your radio. Load the downloaded driver into a text editor and you will find Pavel's email address at the top.
Jim KC9HI