[chirp_devel] Initial Yaesu FT-857 testing

[Marco IZ3GME]

Hi David

> This might be a worthwhile popup on Chirp. Once the download is
> complete, post a dialog box saying something like "Download Complete!
> Did the FT857 finish it's upload? Yes | No". If yes, the the program
> goes to the main menu. If No, post a text box saying "Something must
> have gone wrong. Please review what memories were downloaded into Chirp
> and send an email to the Chirp email list about this. DO NOT use Chirp
> to upload memories to your radio if the download failed. You risk
> resetting all your memories otherwise though the radio will be fine"

This is something we can do, let's see what Dan think about that.
BTW it would be MUCH better having yaesu make a robust and public protocol.

> So are you saying that if I have a set of fully altered Main menu
> settings (color, power levels, CW ID, etc), I download it with Chirp, I
> then factory reset my radio, and then upload from Chirp to the radio,
> I'll get back all my Main menu settings?

This is what I suppose even if I didn't had a look at the rest of the 
data (yet), the clone operation should replicate all setting of the radio.
Having a full backup of the radio is one of the reasons for which I 
decided to use the clone protocol instead of peeking and poking in memory.

>>> This seems to be the same behavior that Kurt KC9LDH saw with his FT-817
>>>
>>
>> Right: seems that in both case we have clone protocol errors.
>> I will investigate Kurt log and see if I found something interesting.
>>
> Ok... Let me know if you need anything else on my side.
>

Please run the attached script and send me the output:
- copy the file to your chirp-devel directory in the chirp subdir (the 
same where the ft857.py file is)
- cd to that dir
- prepare the radio for the clone operation
- run it with
     python ./dump857.py /dev/ft857_prog 2>&1 >/tmp/857dump
- start radio clone tx
wait for the clone to complete, the radio should complain "as usual" and 
the program should take a few seconds to finish after the actual data 
transfer is ended.
Send the generated /tmp/857dump file.
Plese send also an image of the white label on the radio (the one with 
model, serial number etc): we have to find not only the protocol details 
but also a way to recognize the various radio sub models.

Thank for your help

73 de IZ3GME Marco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dump857.py
Type: text/x-python
Size: 873 bytes
Desc: not available
Url : http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20120128/88a6d43c/attachment-0001.py