Bug #10560
closed
Added by Raul R. about 1 year ago.
Updated about 1 year ago.
Model affected:
kenwood TH-F7
I read the instructions above:
Description
the walky kenwood th-f7 only works with chirp for windows if legacy chirp is used. Checked on windows 11, lenovo t480s laptop, cable with wch340 chip and corresponding driver. If used with Chirp Next, at least in this computer, there is no communication and finally chirp get stuck :-( No problem using this same laptop, cable, and Chirp Next with other walkies like BF888, etc. This same cable and same TH-F7 works OK with Chirp Next in Mac. The issue seems to affect only windows Chirp Next because if using chirp legacy no problem at all. Also, own's manufacturer software (kenwood memory control for thf6/thf7) works OK in this Lenovo using same cable and driver.
Thanks for your help
Regards
Raul
Raul R. wrote:
the walky kenwood th-f7 only works with chirp for windows if legacy chirp is used. Checked on windows 11, lenovo t480s laptop, cable with wch340 chip and corresponding driver. If used with Chirp Next, at least in this computer, there is no communication and finally chirp get stuck :-( No problem using this same laptop, cable, and Chirp Next with other walkies like BF888, etc. This same cable and same TH-F7 works OK with Chirp Next in Mac. The issue seems to affect only windows Chirp Next because if using chirp legacy no problem at all. Also, own's manufacturer software (kenwood memory control for thf6/thf7) works OK in this Lenovo using same cable and driver.
Thanks for your help
Regards
Raul
Hi Raul,
I have the same issue with a Kenwood TH F7E - see Bug #10520. I also found legacy Chirp under Windows !0 solves this issue.
Alan
- Is duplicate of Bug #10520: Kenwood TH F7E Memory Errors added
Closing this in favor of the earlier one, please follow status there.
- Status changed from New to Rejected
Also available in: Atom
PDF