[chirp_devel] Yaesu FTM-400

[Johan Adler]

I found this thread:
http://www.4x4ham.com/showthread.php?3776-Yaesu-FTM-400D-Programming while
reading opinions about it at
http://forums.qrz.com/showthread.php?406455-FTM-400DR-is-a-flop-so-disappointed

The thread at 4x4ham shows that they found similar memory layout as did,
and similar to the ftm350 module in Chirp.

I have also learned about how to activate cross band repeater mode.





2014-03-10 9:07 GMT+01:00 Johan Adler <johan.adler at gmail.com>:

> I used xxd, cut and meld to compare and analyze the three dumps. Results:
>
>
> Yaesu FTM-400D
>
> Comparison of memory dumps to SD card, CLN (assumed to be full memory
> dump),
> MEM (memory/channel settings) and SYS (system settings).
>
> Johan Adler, 2014-03-10 (March 10, 2014)
>
>
> 0x0000 to 0x007f: Unknown, identical in all dumps
> 0x0080 to 0x017f: Settings
> 0x0180 to 0x01ff: Present in both settings (same address) and memories (at
> 0x0080 to 0x00ff).
> 0x0200 to 0x027f: Memories (0x0100 to 0x017f)
> 0x0280 to 0x02ff: Settings (0x0200 to 0x027f)
>
> 0x0300 to 0x03ff: Unknown, 0xff in my dump.
> 0x0400 to 0x047f: Contains data, APRS-related settings?
>
> 0x0480 to 0x04ff: Memories (0x0180 to 0x01ff)
> 0x0500 to 0x057f: Settings (0x0280 to 0x02ff)
>
> 0x0580 to 0x05ff: Unknown, 0xca and 0xff in my dump.
> 0x0600 to 0x067f: Contains data, likely APRS-related.
> 0x0680 to 0x07ff: Unknown, 0xca in my dump.
>
> 0x0800 to 0x69ff: Memories (0x0200 to 0x63ff), I guess the two main banks.
>
> 0x7800 to 0x780f: Unknown, 'ALL' padded with ASCII space in my dump.
> APRS-related?
>
> 0x7c00 to 0x7dff: Unknown, looks like data, maybe settings.
>
> 0x8000 to 0x????: APRS reports/contacts, full messages received, 0x80
> bytes each.
>
> 0xe400 to 0x????: APRS contacts, 0x20 bytes each.
>
>
>
>
>
>
>
> On Mon, Mar 10, 2014 at 7:06 AM, Johan Adler <johan.adler at gmail.com>wrote:
>
>> The radio can save different backups to the card, either a full memory
>> dump (76800 bytes, 0c12c00), only the settings (1024 bytes, 0x400), or
>> only the memories (25600 bytes, 0x6400).
>>
>> Filenames and paths, relative to SD card root:
>>
>> Full memory dump ("clone"): FTM400D/BACKUP/CLONE/CLNFTM400D.dat
>> Memories (channel data, I presume): FTM400D/BACKUP/MEMORY/MEMFTM400D.dat
>> Settings: FTM400D/BACKUP/SETUP/SYSFTM400D.dat
>>
>> The size of the full memory dump minus memories and settings is 50176
>> bytes, 0xc400, but I guess it is not all empty. I have noticed that
>> for example incoming APRS messages are stored in memory, but I guess
>> those would not be saved with settings or memories. Still, having
>> separate dumps of the settings area and the channel data area should
>> make it easier to locate those areas in the complete memory dump.
>>
>> I will have a look at the three files, compare them and verify the
>> locations in the full memory dump.
>>
>>
>> A closer look on the Yaesu MH-85A11U shows that it connects with a
>> (probably modified and non standard) mini USB B only. The female
>> connector on the radio has the usual five pins of a mini USB B, and
>> another six pins. Since the DTMF mic that comes with the radio uses
>> six pins I would guess that those six pins are the same as the regular
>> mic. If I was developing hardware I would not create new stuff but
>> rather reuse existing technology, in this case a standard USB webcam
>> interface combined with the six pin microphone interface already in
>> use.
>>
>>
>> I opened the SCU-20 USB data cable, confirmed the presence of a
>> PL2303. It connects using five leads both to the radio and to the USB,
>> and I did not at this time remove the shrink tubing to check if the
>> radio connector cable has all 10 leads or if it is a cheaper five lead
>> cable. It would probably be quite easy to just remove the PL2303 side
>> and make a connector for an FTDI interface instead, though. I took
>> some photos of the inside of the interface cable before putting it
>> back together.
>>
>> On Sat, Mar 8, 2014 at 4:54 PM, Johan Adler <johan.adler at gmail.com>
>> wrote:
>> > 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/20140314/7f33f79b/attachment-0001.html