[chirp_devel] Yaesu FT-897D support

[VK3NAF]

Hi all,

On 08/02/2012, at 9:56 PM, IZ3GME Marco wrote:

> Yes, we know that there are undocumented cat commands to peek and poke directly in memory but we considered safer to use the clone protocol.

Indeed, and the bonus is that the settings are backed up also. :-)

In my enthusiasm, I have decided to quickly try the latest daily build to test whether the FT-857 option works with my FT-897D. Things are looking damn good.

Using the "ft857" option (not "ft857-us") I cloned from the radio to Chirp. There were no errors and everything looked okay within the application - i.e. the frequencies, tags, offsets, mode, etc). I saved the image and it can be found in the attached zip file as "ft897d.img".

I turned the radio off and on again just to make sure none of the memories disappeared. All looked good. To be on the safe side, I quit Chirp and restarted it. I cloned the saved image back to the radio and there were no errors. I turned the radio off and on again and nothing seemed to have changed from before. For the sake of comparison, I cloned from the radio to Chirp again and saved this image in the attached zip file as "ft897d-reread.img".

I ran both files through diff and it reported that the two files differ although, having a look in a hex editor, I couldn't see where. Maybe I should figure out diff's advanced features or I'm using the wrong tool.

Once I get out of bed in the morning, as it's almost 1:30am here, I'll see if there's any difference if I choose "ft857-us" instead from the drop-down list. Please don't hesitate to let me know if there is anything else you'd like me to try.

Have fun!
Emil - VK3NAF

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 897d_imgs.zip
Type: application/zip
Size: 2133 bytes
Desc: not available
Url : http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20120209/989feae6/attachment-0001.zip