Bug #8103
closedTK-7102/7108 "Radio refused at block 0000"
0%
Description
Refusing to read radio. I'm so happy that this, along with the TK-7180/8180 is now supported. But chirp won't read the 7102/7108. If we could also put in a "Reverse" feature for listening on input of repeater, I'd be willing to test it out and report back as well. I wish I knew how to do this stuff, as I could see me making this radio accept 16 channels (I believe the radio is capable of it.)
Related issues
Updated by Bernhard Hailer almost 4 years ago
- Status changed from New to Feedback
- Priority changed from High to Normal
- Model affected changed from tk-7102/7108/8102/8108 to Kenwood TK-7102/7108/8102/8108
This type of problem is usually caused by a cable / driver / connector issue. Please refer to these Wiki articles:
CableGuide
CableGuide FTDI OEM Cables
[RTSystemsCablesAndMavericks]
If there's no solution to be found in any of them, please read: How To Report Issues and provide a debug log. Thank you!
Windows notes: If you are using a generic cable with a Prolific chip, you will very likely need to downgrade your driver to version 3.2.0.0.
It can be found at http://www.miklor.com/COM/UV_Drivers.php
MacOS notes: this OS is apparently very picky about USB to Serial cables. From what I heard, only (genuine) FTDI-based cables can be made work.
You must have the KK7DS Python runtime for Mac OSX installed.
Also see MacOS Tips!
Linux notes: Linux generally is quite good with USB to Serial converter drivers. The most likely cause for grief is a connector which doesn't provide good electrical contact.
Bluetooth notes: connections often suffer from timing issues, please try a cable instead.
Updated by Nicholas Mitzuk almost 4 years ago
This is not a cable issue, as it works fine with the kenwood kpg-70d software and the cable is a genuine kenwood kpg-46x in uart mode.
Updated by Bernhard Hailer almost 4 years ago
Still, the debug log is what we need.
Updated by Bernhard Hailer over 3 years ago
Nicholas, do you still have this problem, or can we close the ticket?
If you still have the problem, then please read: How To Report Issues and provide a debug log. Thank you!
Updated by Bernhard Hailer about 3 years ago
- Status changed from Feedback to Closed
No more feedback by submitter.