[chirp_users] programming Yaesu FT2D

[Robert Carter]

I picked up my general license this year due to an incident I was 
involved in -- remote accident with no communications. Just sucked. 
Should have studied for the extra license too and gotten them all over 
on the same day.

Anyway, I picked up a new Yaesu FT2D yesterday. I'm trying to get over 
the programming hump. In the box with the FT2D was a USB programming cable.

Win7:

Yeasu in-the-box supplied Prolific cable and driver from Yeasu's web 
site won't run. v1.8 driver fails to install. I downloaded and the 
latest v1.16 driver from Prolific's web site, still no love.

Ubutnu 14.04 LTS:

Now it gets interesting. lsubb reports PID/VID for this cable:

    Bus 005 Device 016: ID 26aa:0001

The pl2303 kernel module doesn't recognize this PID/VID as a serial 
device. When the cable is inserted, the kernel doesn't load the serial 
USB module. "modinfo pl2303" doesn't list this Yeasu cable's PID/VID.

When inserting the USB-serial cable, while the FT2D is in "clone" mode, 
syslog reports:

Nov 13 10:20:53 booger kernel: [ 4471.004031] usb 5-1: new full-speed 
USB device number 16 using uhci_hcd
Nov 13 10:20:58 booger kernel: [ 4476.361065] usb 5-1: New USB device 
found, idVendor=26aa, idProduct=0001
Nov 13 10:20:58 booger kernel: [ 4476.361073] usb 5-1: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
Nov 13 10:20:58 booger mtp-probe: checking bus 5, device 16: 
"/sys/devices/pci0000:00/0000:00:1d.3/usb5/5-1"
Nov 13 10:20:58 booger mtp-probe: bus: 5, device: 16 was not an MTP device

I tried manually to force load the kernel modules and force the PID/VID 
into the drivers -- but still nada:

   sudo modprobe pl2303 vendor=0x26aa product=0x0001
   sudo modprobe usbserial vendor=0x26aa product=0x0001

I looked over the CHIRP source code and with the kernel modules "forced" 
and the FT2D still in "clone' mode, then launched minicom on 
/dev/ttyUSB0. Set the baud rate to 38400 8N1 -- nada. Nothing to/from 
the FD2R.

I'm willing to guinea pig here and run some experiments. If anyone has 
any ideas, I'd like to hear them.

This should be this hard (well, except for windows).

I checked over the last year of the CHIRP mailing list and didn't find 
any posts relative to the FT1D or FT2D, so I guess I'm breaking new ground.

/KC1FAC/