<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Ok James.</div><div class="">If you like, we can try to collaborate on it. </div><div class="">I have already looked at the serial transfer protocol.</div><div class="">It’s 38400 bps and looks like its almost identical to th_uvf8d.py logic.</div><div class="">(I dont know how many other TYT radios use this logic - it might be a chance to factor out some common logic into a generic tyt radio class in the future…)</div><div class=""><br class=""></div><div class="">I see Tom already implemented a file-backed driver from the oem software.</div><div class="">The radio memory seems to be about 10000h (64 k) bytes.</div><div class="">The oem software stores the actual radio image almost exactly in the oem data files.</div><div class="">The oem file format seems to have a 1000h (4096) bytes header, then the radio image starts and goes to EOF.</div><div class="">However, the oem software does not fetch the first 100h (256) bytes of the radio image during normal transfer, but request at offset 0100h.</div><div class="">So this is where Tom started reading the image at 1100h.</div><div class="">(I suspect that the first 100h might be a calibration storage area, etc - we’ll see later on).</div><div class=""><br class=""></div><div class="">So one step will probably just get chirp to download the radio image.</div><div class="">Another step will probably be to start mapping out the image. With the knowledge that the oem file format has the complete radio image, this step can be done independently of the other. Also, looks like Tom has already given us a jump start on the channels.</div><div class="">The settings can be tackled as another later step also.</div><div class=""><br class=""></div><div class="">We can do a skype session, irc chat, or just email back and forth.</div><div class=""><br class=""></div><div class="">Jens</div><div class=""><a href="mailto:af5mi@yahoo.com" class="">af5mi@yahoo.com</a><span class="Apple-tab-span" style="white-space:pre"> </span></div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 11, 2014, at 11:50 AM, James Lee <<a href="mailto:jml@jmlzone.com" class="">jml@jmlzone.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">I have not yet successfully contributed anything, but I was planning<br class="">on trying my hand at this. I have the radio and the pc software and<br class="">cable. I have the hg repo cloned to my macwhere I will be attempting<br class="">development.<br class=""><br class="">James N1DDK.<br class="">All hints and help welcomed.<br class=""><br class=""><br class="">On Thu, Dec 11, 2014 at 11:26 AM, Dan Smith <<a href="mailto:dsmith@danplanet.com" class="">dsmith@danplanet.com</a>> wrote:<br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">Just wanted to check to see if anyone else was working on radio<br class="">(cloning) support, so that we aren't working in isolation possibly<br class="">duplicating work.<br class=""></blockquote><br class="">I'm not and I don't know of anyone that is. I say wait 24 hours, assign<br class="">yourself to the issue, and consider the mutex yours :)<br class=""><br class="">--Dan<br class=""><br class=""><br class="">_______________________________________________<br class="">chirp_devel mailing list<br class=""><a href="mailto:chirp_devel@intrepid.danplanet.com" class="">chirp_devel@intrepid.danplanet.com</a><br class="">http://intrepid.danplanet.com/mailman/listinfo/chirp_devel<br class="">Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers<br class=""></blockquote>_______________________________________________<br class="">chirp_devel mailing list<br class=""><a href="mailto:chirp_devel@intrepid.danplanet.com" class="">chirp_devel@intrepid.danplanet.com</a><br class="">http://intrepid.danplanet.com/mailman/listinfo/chirp_devel<br class="">Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers<br class=""></div></blockquote></div><br class=""></body></html>