Bug #9461
KENWOOD TK732G
Status: | Feedback | Start date: | 10/20/2021 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% |
|
Category: | - | |||
Target version: | chirp-daily | |||
Chirp Version: | daily | Platform: | Windows | |
Model affected: | Kenwood TK-372G |
Description
CHIRP DOESN´T READ THE RADIO IDENTIFIES IT CORRECTLY BUT AT THE END OF THE READING PROCEDURE SENDS AN ID ERROR
History
Updated by MICHEL ANTOINE DRIVET AMADOR 7 months ago
- File debug.log added
Wrong Kenwood radio, ID or unknown variant, see LOG output. THIS ERROR SHOWS ON SCREEN
Updated by MICHEL ANTOINE DRIVET AMADOR 7 months ago
- File debug.log added
Updated by MICHEL ANTOINE DRIVET AMADOR 7 months ago
- File debug.log added
WITH THE NEW VERSION SAME ERROR
Updated by Bernhard Hailer 10 days ago
- Priority changed from High to Normal
- Model affected changed from TK372G to Kenwood TK-372G
Updated by Pavel Milanes 10 days ago
Hi OM, thanks for the debug log. (driver's author here)
The operation fails as the last byte of the ident string are not the same, look it for yourself:
DEBUG: Full ident string is: DEBUG: 000: 50 33 37 32 30 06 fb *f1* P3720... DEBUG: Starting the download from radio DEBUG: Wrong Kenwood radio, ID or unknown variant DEBUG: 000: 50 33 37 32 30 06 fb *00* P3720...
That means that the radio has the TRUNKING addon board installed. Reviewing the drivers identification schema:
"P3720\x06": (32, 450, 470, "K") "P3720\x07": (32, 470, 490, "K1") "P3720\x08": (32, 490, 512, "K2") "P3720\x09": (32, 403, 430, "K3")
You can see it's like a "K" variant and must work from 450 to 470 Mhz, it's supported.
Also, the driver does not support radios with the TRUNKING addon installed (last f1 byte means that) as it changes the memory handling a bit.
If you can access the OEM software please read it, deactivate the TRUNKING option and upload the programing again.
I must work with chirp then.
Cheers, Pavel CO7WT.
Updated by Pavel Milanes 10 days ago
- Status changed from New to Feedback