Bug #3211
closedKenwood TK-260G bug
0%
Description
Hello,
When I try to read the Kenwood TK-260G ht radio I am getting this error:
Block Checksum Error! real 00, calculated 26
I am currently using the Daily build 20160116.
Files
| IMG_1748.JPG (587 KB) IMG_1748.JPG | Name plate to verify model. | ||
| how to portmon.doc (17 KB) how to portmon.doc | Simple procedure to get the serial communications logs between radio and PC | ||
| TK-360G.jpg (585 KB) TK-360G.jpg | |||
| TK-360G Error.jpg (22.5 KB) TK-360G Error.jpg |
Updated by Pavel Milanes almost 9 years ago
- Status changed from New to Feedback
- Assignee set to Pavel Milanes
Please re-check your cable connection and answer this questions to me:
1 - Try to read the radio with the original software, up on success and without touching the radio or cable, close the software and try to read it on chirp, what is the result?
2 - Does the radio put " - PC - " in the display just after this error arise.
3 - Try several times and see if the error is consistent: aka it occurs every time.
Cheers
Updated by John Reinhart almost 9 years ago
Ok I with the factory s/w the radio read fine. I closed the program and loaded chirp and tried 7 times to read the radio and here is the results:
#1 Block Checksum Error! real 00, calculated 26
#2 Block Checksum Error! real 00, calculated 16
#3 Block Checksum Error! real 00, calculated 26
#4 string index out of range
#5 The radio doesn't accept program mode
#6 Block Checksum Error! real 10, calculated 06
#7 Block Checksum Error! real 20 calculated 26
This radio does not have an LCD display, only a volume knob and channel knob.
Updated by Pavel Milanes almost 9 years ago
Sorry for the confusion about the 270G/260G and the display.
I managed to re-borrow a TK-272G and a TK-270G and re-tested the code both in linux and windows PC; and found no problem here.
Can you being possibly mistaken the model? it's easy.
Take into account that there are ending in G and not ending in G models, and this are two completely different radios.
The portables 260/270/272/278 ending in G are the only supported by Chirp for the moment.
Please remove the battery and check your models in the factory label, if they are the ending in G ones.
If you have the correct models please drop me an email to make further test (my user data here [[http://chirp.danplanet.com/users/6427]])
73.
Updated by John Reinhart almost 9 years ago
- File IMG_1748.JPG IMG_1748.JPG added
Yes it is a TK-260G-1 (I think the -1 designates USA model maybe). I am attaching a pic of the serial/model plate.
On another note regarding the TK-272G-1 apparently it is flashed to a TK-270G-1 so I do not want to test or do any reporting with it.
The 260G-1 is stock and has not been messed with though so this is what I am reporting with.
Updated by Pavel Milanes almost 9 years ago
- File how to portmon.doc how to portmon.doc added
Ok I see. (nice picture BTW)
Can you make a log of the communication between the radio and the original programmer, and then between radio and chirp. A simple procedure is attached, feel free to ask to my mail for any details. (there are other - free for a limited time - serial sniffers if portmon is not an option, google is your friend)
Let's concentrate on the TK-260G for now (As the name of this issue state)
I need only the download (radio to PC) logs from the original software (KPG-56d) and the one for chirp, to spot the problem.
As for the TK-272G-1 programming on the TK-270G-1, it's not a problem, early on the life cycle of the "Series 60G" radios, Kenwood "make the ring" (just one firmware to rule them all)
So portables in the G family are "hackable" as other models just by overwriting the programming and they do work fine.
A known and documented hack is to program the 260/270/272 G models as a 278G one to get access to the true "Reverse" function in a button, not just the "Turn Around" one.
As per my chirp driver, I discovered and fixed that, so this is no longer needed, BTW, with my driver in the mobile family you can access a "Low Power" in a button just like the portables ones do.
All the above works if you have the "ring power" firmware or beyond, in the night I will send instructions to check that.
73.
Updated by Pavel Milanes almost 9 years ago
- Status changed from Feedback to Closed
Confirmed: It's a firmware incompatibility problem, I will close this to not duplicate efforts, please follow the issue #3349 for details and progress.
Updated by Al Mellon almost 9 years ago
- File TK-360G.jpg TK-360G.jpg added
Hello, I noticed CHIRP supports Kenwood TK-260G. I tried to read my TK-360G as a test. Saw an error something like 'Model type P3600 not P2600'. Is it possible to update CHIRP to work with TK-360G? I do not have the commercial software. My model is TK-360G -1 the USA UHF version.
Updated by Al Mellon almost 9 years ago
- File TK-360G Error.jpg TK-360G Error.jpg added
Screen shot of CHIRP error when reading. TK-360G CHIRP daily-20160316.
Updated by Pavel Milanes almost 9 years ago
Hi Al, This issue is closed, please make the request of the new model in a new issue.
I'm the developer of the Series 60G from Kenwood, I will check this afternoon if that model is a member of the family to give support for it, but I need you to open a new issue specifically for this new model.