[chirp_devel] TYT TH-9800

[Jens Jensen]

Ok James.
If you like, we can try to collaborate on it. 
I have already looked at the serial transfer protocol.
It’s 38400 bps and looks like its almost identical to th_uvf8d.py logic.
(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…)

I see Tom already implemented a file-backed driver from the oem software.
The radio memory seems to be about 10000h (64 k) bytes.
The oem software stores the actual radio image almost exactly in the oem data files.
The oem file format seems to have a 1000h (4096) bytes header, then the radio image starts and goes to EOF.
However, the oem software does not fetch the first 100h (256) bytes of the radio image during normal transfer, but request at offset 0100h.
So this is where Tom started reading the image at 1100h.
(I suspect that the first 100h might be a calibration storage area, etc - we’ll see later on).

So one step will probably just get chirp to download the radio image.
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.
The settings can be tackled as another later step also.

We can do a skype session, irc chat, or just email back and forth.

Jens
af5mi at yahoo.com <mailto:af5mi at yahoo.com>	


> On Dec 11, 2014, at 11:50 AM, James Lee <jml at jmlzone.com> wrote:
> 
> I have not yet successfully contributed anything, but I was planning
> on trying my hand at this.  I have the radio and the pc software and
> cable. I have the hg repo cloned to my macwhere I will be attempting
> development.
> 
> James N1DDK.
> All hints and help welcomed.
> 
> 
> On Thu, Dec 11, 2014 at 11:26 AM, Dan Smith <dsmith at danplanet.com> wrote:
>>> Just wanted to check to see if anyone else was working on radio
>>> (cloning) support, so that we aren't working in isolation possibly
>>> duplicating work.
>> 
>> I'm not and I don't know of anyone that is. I say wait 24 hours, assign
>> yourself to the issue, and consider the mutex yours :)
>> 
>> --Dan
>> 
>> 
>> _______________________________________________
>> chirp_devel mailing list
>> chirp_devel at intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
>> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20141211/94573958/attachment-0001.html