*sigh* OK. I’ll try to start. I’ve been reading the instructions.
I’ve already dumped the microSD-based file (“BACKUP.DAT”) and have some inkling of at least the gross features of memory format.
The Yaesu-supplied ADMS-8 software can build files, so I don’t need to have the radio in the loop all the time. I suspect it possible to get a basic memory map within a shortish time. I’ll try to compare and contrast the FT1 based upon the template in the source code. I’m so new to the VHF world that I don’t understand most of the options that are accessible to the programmable capability, so it’ll probably only be a beginning.
Unfortunately for me, the FT2D data connection has been impossible to use. I believe that the FT2D uses a straight USB cable with an internal UART-to-USB connection, and no driver I’ve tried allows serial ports to connect to the radio. I conjecture that multiple serial ports* are multiplexed over the same USB) I am able to move the BACKUP.dat file between radio and computer by using the microSD card. So a sine qua non for me to use chirp for now is to be able to send the erstwhile serial data to and from a file. Having scanned the template, I’m guessing that do_upload(radio) and do_download(radio) will need to support file-based rather than serial I/O based. That may be A Big Deal for chirp.
* microphone/speaker/camera, memory programming, and software update all seem to be included. The FT2D has a separate microphone/speaker connector, but the USB connector takes priority: completing a USB connection stops the audio to internal or external speaker.
<snip>
I'm pretty sure no one has done significant work on the FT2D.I did do a lot of work on the FT1D and I'm assuming it's not that different. Unfortunately I don't have a FT2D to work with.With the origiinal FT1D driver it was hundreds ( it not thousands ) of memory dumps to get the correct offsets for the settings.Angus