https://chirpmyradio.com/https://chirpmyradio.com/favicon.ico?16699092072014-12-17T00:06:24ZCHIRPCHIRP - Bug #2109: Error message programming UV-B5 27 menu versionhttps://chirpmyradio.com/issues/2109?journal_id=58732014-12-17T00:06:24ZJim Unroejru.chirp@kc9hi.net
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul><p>Henk,</p>
<p>From what I can tell, the UV-B5/B6 radios with only 27 menus don't allow editing of the "Test Mode Settings". Once the upload gets to the Test Mode Settings (0xF010), the radio decides it needs no more data and stops ACKing the remaining data transfer and CHIRP lets you know.</p>
<p>As far as I know all of the channels as setting were successfully uploaded. It is only the Test Mode Settings that don't get transferred, and they are only useful in a radio with 29 menus anyway.</p>
<p>Jim KC9HI </p>
CHIRP - Bug #2109: Error message programming UV-B5 27 menu versionhttps://chirpmyradio.com/issues/2109?journal_id=58772014-12-17T08:57:07ZHenk Groningenhenk@mijneigen.net
<ul></ul><p>Hi Jim,</p>
<p>You're right. I couldn't adjust squelch and tx power for out-of-limit bands.<br>
So I bought ( without knowing .. ) the wrong HT.</p>
<p>regards,<br>
Henk</p>
CHIRP - Bug #2109: Error message programming UV-B5 27 menu versionhttps://chirpmyradio.com/issues/2109?journal_id=58792014-12-17T10:49:04ZJim Unroejru.chirp@kc9hi.net
<ul></ul><p>Henk,</p>
<p>I didn't realize that the band limits were also affected. You are right, they are. The radios with 27 menus stop ACKing the transfer at 0x0F10 and the band limits are at 0x0F30 followed by the squelch and power level settings at 0x0FF0.</p>
<p>Jim KC9HI</p>
CHIRP - Bug #2109: Error message programming UV-B5 27 menu versionhttps://chirpmyradio.com/issues/2109?journal_id=58812014-12-17T20:13:44ZHenk Groningenhenk@mijneigen.net
<ul></ul><p>Just to clarify things: <br>
I can program the bandlimits, and the HT does recieve according to the new limits.<br>
I cannot program the test-values ( squelch and power ). This doesn't work with the original software either.</p>
<p>The thing is that after extending the limits chirp does not display the normal settings-tab anymore, instead the tab is empty. The advanced tree-view is still available.</p>
<p>By the way: the specific log is attached to the other issue, <a class="issue tracker-1 status-1 priority-4 priority-default" title="Bug: 'hacked' UV-B5 settings not read back (New)" href="https://chirpmyradio.com/issues/2111">#2111</a>.<br>
The first error during readback is " Exception running RadioJob: Value 100 not in range 136-174". So it seems the limits are read back in but during the valuecheck it throws an exception.</p>
<p>regards </p>
<p>Henk</p>
CHIRP - Bug #2109: Error message programming UV-B5 27 menu versionhttps://chirpmyradio.com/issues/2109?journal_id=58852014-12-18T04:00:49ZJim Unroejru.chirp@kc9hi.net
<ul></ul><p>Correct. I create a file that would match your band limits this morning and almost sent it to you to try, but I loaded it here and the settings were still missing. So the problem is more than just the band limits. I didn't get a chance to look into it this evening. It is past my bed time now, so maybe I can find time to look into it tomorrow.</p>
<p>Jim KC9HI</p>
CHIRP - Bug #2109: Error message programming UV-B5 27 menu versionhttps://chirpmyradio.com/issues/2109?journal_id=58892014-12-18T08:33:36ZHenk Groningenhenk@mijneigen.net
<ul></ul><p>If I can be of any assistance in testing or other way please let me know.<br>
( it is of course a shame that Baofeng removed these important options in the HT )</p>
<p>regards</p>
<p>Henk</p>
CHIRP - Bug #2109: Error message programming UV-B5 27 menu versionhttps://chirpmyradio.com/issues/2109?journal_id=127032017-02-12T12:51:48ZJim Unroejru.chirp@kc9hi.net
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li><li><strong>Assignee</strong> set to <i>Jim Unroe</i></li><li><strong>Target version</strong> set to <i>0.5.0</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li><li><strong>Platform</strong> changed from <i>Windows</i> to <i>All</i></li></ul><p>CHIRP daily-20170212 should resolve this issue.</p>
<p>Jim KC9HI</p>
CHIRP - Bug #2109: Error message programming UV-B5 27 menu versionhttps://chirpmyradio.com/issues/2109?journal_id=129472017-02-13T02:42:42ZJonathan Roen6atf@cox.net
<ul></ul><p>Confirmed, no more error.</p>
CHIRP - Bug #2109: Error message programming UV-B5 27 menu versionhttps://chirpmyradio.com/issues/2109?journal_id=132872017-03-24T18:34:28ZBryan Daviesbryan.e.davies@gmail.com
<ul></ul><p>Please forgive a question from a complete newbie to this.</p>
<p>I have today purchased a UV-B6 complete with manufacturer's download cable. This connects to my Windows 10 PC via COM3. I have downloaded the latest version of CHIRP - 20170324.</p>
<p>Chirp doesn't offer a UV-B6 option, but from reading the various issue reports I have used UV-B5 however I am getting the much reported "Radio did not ack programming mode" error when I attempt a download. I note that there is a patch mentioned above - do I need to install this manually, and if so how?</p>
CHIRP - Bug #2109: Error message programming UV-B5 27 menu versionhttps://chirpmyradio.com/issues/2109?journal_id=132952017-03-24T20:51:37ZJim Unroejru.chirp@kc9hi.net
<ul></ul><p>Leave the programming cable unplugged from the radio and try it. You will get the same error. You do not have a fully working connection between the radio and the computer.</p>
<p>This is usually caused by to (unrelated to CHIRP) issues.</p>
<ol>
<li><p>The computer is using Windows and the programming cable has a counterfeit Prolific chip. The device driver auto-installed by Windows when a Prolific chip is detected is intentionally incompatible with counterfeit chips. In this case the driver has to be downgraded to v3.2.0.0 (v2.0.2.1 for Windows XP). See "USB Cables and Drivers":<a href="http://www.miklor.com/COM/UV_Drivers.php">http://www.miklor.com/COM/UV_Drivers.php</a> at "miklor.com":<a href="http://www.miklor.com">http://www.miklor.com</a></p></li>
<li><p>The 2=pin plug is not fully inserted/connected to the radios socket.</p></li>
</ol>
<p>My guess is that it is #1.</p>
<p>Jim KC9HI</p>
CHIRP - Bug #2109: Error message programming UV-B5 27 menu versionhttps://chirpmyradio.com/issues/2109?journal_id=133072017-03-25T08:18:30ZHenk Groningenhenk@mijneigen.net
<ul><li><strong>File</strong> <a href="/attachments/3347">levelB5.jpg</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/3347/levelB5.jpg">levelB5.jpg</a> added</li></ul><p>Bryan, Jim is right: This is not a chirp issue.<br>
Just to give some additonal hints..</p>
<p>To test your driver/setup connect the middle ring of the 2.5 mm connector to the ground sleeve of the 3.5 mm connector, creating a serial loop. Use any terminal program to see if serial data is echo'd.</p>
<p>--<br>
There is a very, very! slight change that the handset is defective, like mine. My handset was not able to pull down the RX from the the adapter to zero ( measured and confirmed with a scope ), and could not be programmed whatever adapter was used.<br>
I had to work around this by building a level adjuster. But this seems very rare, I haven't heard anyone else about it. I've attached a schematic, but it involves cutting the cable or using a set of male/female connectors and should only be a last resort. Of course at your own risk ... </p>
CHIRP - Bug #2109: Error message programming UV-B5 27 menu versionhttps://chirpmyradio.com/issues/2109?journal_id=133112017-03-26T16:18:06ZBryan Daviesbryan.e.davies@gmail.com
<ul></ul><p>Thanks Jim and Henk - I'm getting something from the radio now, although I'm still not sure what I'm doing with it!</p>
<p>For the benefit of anyone else with this problem, it was the device driver and it does seem to work with one called CH341S64.sys.</p>
<p>The cable was supplied by Baofeng so I'd be disappointed if it was a 'counterfeit Prolific chip' but I guess you never know. </p>
CHIRP - Bug #2109: Error message programming UV-B5 27 menu versionhttps://chirpmyradio.com/issues/2109?journal_id=211832020-02-25T23:01:48ZBernhard Hailerae6yn@arrl.net
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>