[chirp_devel] FT2D quasi-success (meaning I simply had to try it and it partially worked)

[NNN Wx]

I can read the Yaesu FT2D into chirp by telling chirp it’s an FT-1D. The memory “Name” field displayed by chirp is wrong, although the Browser shows correctly-encoded characters. The “Name” field looks more like a data field printed as ASCII (entries like “:”, “@“, “@p ;”, “^?q&#!W:;”) Has anybody any clue what may be causing that, or how I can start a debug process?

— a few more details. I’m doing this on Macintosh OS X;
I finally gave up using the straight USB cable (Yaesu had told me, in writing, that it wouldn’t work) and got the appropriate cable for FT2D (SCU-19). Using Prolific drivers on my Macintosh allows the serial port to show as 
/dev/cu.usbserial.

The distributed chirp (not the daily build) reads my FT2D by telling chirp to use [now old] FT-1D model. The basic memory functions are there in the correct order and meaning. It does not get the memory location name correctly, nor does it correctly handle memory banks. I may simply be able to do much as was done with the FTM3200D, and clone Ainslie and others' good work with only a few amendments in memory model to get the banks to decipher correctly. I’ve not gone very far into other settings, but it’s clear to me that most of the APRS data structures are already handled correctly as well.

Declan Rieb WD5EQY