[chirp_devel] Yaesu FTM-400
Johan Adler
Sat Mar 8 07:54:11 PST 2014
Thank you, Tom,
In fact I just made a rough memory map earlier today, just studying the
memory dump file from the memory card with a hex editor. When comparing my
guesses with the mapping used by the FTM-350 module most major stuff seems
to be in the same places. There are new features and settings, of course,
and I will have to sort those out, but I think I can use the FTM-350 module
as a starting point.
Of course, one difference is the two different ways of accessing the
memory, cable or card.
I have not found any way of making the radio save more than one incarnation
of the memory dump, alas.
One possible interesting (non Chirp related thing) about it is the optional
camera microphone, which connects (for the camera) to what looks a lot like
a mini USB B, and where such a cable also fits. What if it would be
possible to connect some simple webcam instead of the more expensive Yaesu
cam mic. :-)
On Sat, Mar 8, 2014 at 4:41 PM, Tom Hayward <esarfl at gmail.com> wrote:
> On Sat, Mar 8, 2014 at 12:54 AM, Johan Adler <johan.adler at gmail.com>
> wrote:
> > I have cloned the development tree and try to find how the FTM-350 module
> > works regarding memory download to see if can start there. I can also
> start
> > analyzing the memory image saved to µSD, but it will be a bit tedious to
> > change one setting, turn the thing off, take the µSD card to the
> computer,
> > copy the settings file, compare it to the previous version, put the card
> > back, turn on the radio, change another setting, and so on. :-)
>
> How many memory images does it allow you to store on the µSD card? You
> make it sound like just one, unfortunately. If you can store more than
> one, you could batch a number of changes into respective files before
> copying to the computer for analysis.
>
> Yaesus are pretty simple (actually, most all ham radios are). If you
> upload the memory image and include a few details like what frequency
> and PL are in the first three channels, I could probably tell you at
> least where the channel data starts and how long each record is.
>
> Tom KD7LXL
> _______________________________________________
> 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/20140308/bd8534b3/attachment-0001.html
More information about the chirp_devel
mailing list