<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>Hi Marcus. I received a few attachments with a lot of numbers. <br>
<br>
<div class="x_acompli_signature">Get <a href="https://aka.ms/o0ukef">Outlook for iOS</a></div>
<br>
</div>
<br>
<br>
<br>
<div class="x_gmail_quote">On Sat, Aug 6, 2016 at 3:51 PM +0100, "Marcus van Dam"
<span dir="ltr"><<a href="mailto:marcus@marcusvandam.nl" target="_blank">marcus@marcusvandam.nl</a>></span> wrote:<br>
<br>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi,<br>
<br>
I recently bought a Baofeng UV-6 at the 409shop, which I all exited<br>
hooked up and figured out that it gave the dreaded 'Radio did not<br>
respond' and 'Refused to clone' messages.<br>
<br>
After some digging and comparing to the Baofeng windows tool<br>
(UV6UV7_CPS) I found the following;<br>
<br>
When you try to read the radio with Chirp, the magic is send (50 bb ff<br>
20 12 08 23 00), the ACK is received, 0x02 is send, and from here, Chirp<br>
seems to expect 8 bytes of data as ident (ident = serial.read(8)), but<br>
looking at the serial traffic of the BF software, the radio sends 12<br>
bytes (AA 01 01 36 01 74 01 04 00 05 20 DD).<br>
As Chirp only read 8, the next write and read will not return the<br>
expected results and the clone fails.<br>
<br>
I tried to increase that initial ident read size in Chirp to 12 bytes<br>
(ident = serial.read(12)), which got me to the "Incorrect 'Model'<br>
selected" error, saying in the debug, that the model is actually ' Ver<br>
UV6S83 '.<br>
<br>
In a desperate attempt I added "UV6S83" to the array "BASETYPE_UV6",<br>
which allowed Chirp to read the data, but in the end it could not make<br>
sense of the content.<br>
<br>
This is where my debug skills ended and I hope your expertise comes in.<br>
<br>
I have attached a couple of captures to this email;<br>
UV6S83-CHIRP_8bytes-ident.txt = Chirp, all default trying to read the UV-6<br>
UV6S83-CHIRP_12bytes-ident.txt = Chirp, modified the ident length and<br>
added the basetype as an UV-6<br>
UV6S83-UV6UV7.txt = Original Baofeng software doing a full dump.<br>
<br>
The modified Chirp dump contains an interesting snippet in the first<br>
memory block: BAOFENG UV-5R .. Ver UV6S83<br>
Would the have build a Frankenstein device?<br>
<br>
Let me know if there is anything I can do to help debugging.<br>
<br>
// Marcus<br>
<br>
</div>
</span></font>
</body>
</html>