https://chirpmyradio.com/https://chirpmyradio.com/favicon.ico?16699092072018-09-27T01:02:35ZCHIRPCHIRP - Bug #6115: Radio did not enter clone modehttps://chirpmyradio.com/issues/6115?journal_id=165252018-09-27T01:02:35ZJim Unroejru.chirp@kc9hi.net
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul><p>Did you happen to mistakenly plug the programming cable into the speaker/mic port instead of the data port? They are both side by side on the back of the radio.</p>
<p>Jim KC9HI</p>
CHIRP - Bug #6115: Radio did not enter clone modehttps://chirpmyradio.com/issues/6115?journal_id=165632018-10-14T22:02:40ZDave Gombergdave2@sfwcf.com
<ul></ul><p>I set up the cable directly and reloaded the driver, all seems well from the POV of device manager BUT<br>
when I try to download from radio, no error msg, nothing happens.\<br>
Any idea what I am doing wrong? Device manager seems happy with COM5, but I see no way to tell chirp about COM5.</p>
CHIRP - Bug #6115: Radio did not enter clone modehttps://chirpmyradio.com/issues/6115?journal_id=212932020-02-26T23:18:08ZBernhard Hailerae6yn@arrl.net
<ul><li><strong>Target version</strong> set to <i>chirp-legacy</i></li><li><strong>Model affected</strong> changed from <i>Baofeng UV25-X4</i> to <i>UV25-X4</i></li></ul><p>Have you been able to resolve this on your own since you submitted this? Did you try Jim's suggestion?</p>
CHIRP - Bug #6115: Radio did not enter clone modehttps://chirpmyradio.com/issues/6115?journal_id=243732020-05-12T03:51:37ZBernhard Hailerae6yn@arrl.net
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li><li><strong>Model affected</strong> changed from <i>UV25-X4</i> to <i>BTech UV25-X4</i></li></ul><p>No more feedback by submitter.</p>