[chirp_users] programming Yaesu FT2D
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/
Make sure you're a member of the "dialout" and "serial" groups.
On 13 November 2016 at 11:49 Robert Carter carterrj@verizon.net wrote:
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.
On 11/13/2016 12:28 PM, Nigel A. Gunn G8IFF/W8IFF wrote:
Make sure you're a member of the "dialout" and "serial" groups.
Yep. Did that long ago. See below.
The first hurtle is whether this Yeasu in-the-box supplied prolific cable works with ANY operating system.
Finally figured out -- after eight hours of pouring over the FT2D radio to get the PL ton configured to hit the local repeater. Way too painful. Documentation is horrible.
Have to figure out how to get the GPS RX up and running on it too.
= = = = = =
bob@booger:~$ groups bob adm dialout cdrom sudo dip plugdev lpadmin sambashare kismet
One of my Ubuntu installations required me to be a member of the "serial" group.
On 13 November 2016 at 12:56 Robert Carter carterrj@verizon.net wrote:
On 11/13/2016 12:28 PM, Nigel A. Gunn G8IFF/W8IFF wrote:
Make sure you're a member of the "dialout" and "serial" groups.
Yep. Did that long ago. See below.
The first hurtle is whether this Yeasu in-the-box supplied prolific cable works with ANY operating system.
Finally figured out -- after eight hours of pouring over the FT2D radio to get the PL ton configured to hit the local repeater. Way too painful. Documentation is horrible.
Have to figure out how to get the GPS RX up and running on it too.
= = = = = =
bob@booger:~$ groups bob adm dialout cdrom sudo dip plugdev lpadmin sambashare kismet
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
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.
Does Win7 detect this as a Prolific based cable? If it does and the driver thinks it is a counterfeit Prolific chip, it will not work. You must download, install and select the older Prolific v3.2.0.0 driver.
I have several installed and switch between them to determine if the Prolific chip is genuine or not (most are not), so I usually have the v3.2.0.0 driver selected.
Jim KC9HI
For Windows, try rolling your Prolific driver back to 3.2.0.0. Also, make sure cable is FIRMLY pushed in.
Jardy Dawson WA7JRD Ham Radio
Message relayed from secret Hillary Clinton server, located in the basement of her house. OOPS, you aren't supposed to know that!
On Nov 13, 2016, at 08:49, Robert Carter carterrj@verizon.net wrote:
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/ _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jardy at jardy72@yahoo.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Try not using Windows. No driver problems with Linux.
On 13 November 2016 at 15:19 Jardy Dawson via chirp_users chirp_users@intrepid.danplanet.com wrote:
For Windows, try rolling your Prolific driver back to 3.2.0.0. Also, make sure cable is FIRMLY pushed in.
Jardy Dawson WA7JRD Ham Radio
Message relayed from secret Hillary Clinton server, located in the basement of her house. OOPS, you aren't supposed to know that!
On Nov 13, 2016, at 08:49, Robert Carter carterrj@verizon.net wrote:
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/ _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jardy at jardy72@yahoo.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
I don't know anything about Linux and have no problems with the many cables I have with the fake Prolific chips in them. Not that hard to roll back the driver if need be.
Jardy Dawson WA7JRD Message sent through sub space hailing frequencies using the Universal Translator.
On Nov 13, 2016, at 12:37, Nigel A. Gunn G8IFF/W8IFF nigel@ngunn.net wrote:
Try not using Windows. No driver problems with Linux.
On 13 November 2016 at 15:19 Jardy Dawson via chirp_users chirp_users@intrepid.danplanet.com wrote:
For Windows, try rolling your Prolific driver back to 3.2.0.0. Also, make sure cable is FIRMLY pushed in.
Jardy Dawson WA7JRD Ham Radio
Message relayed from secret Hillary Clinton server, located in the basement of her house. OOPS, you aren't supposed to know that!
On Nov 13, 2016, at 08:49, Robert Carter carterrj@verizon.net wrote:
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/ _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jardy at jardy72@yahoo.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jardy at jardy72@yahoo.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Sun, Nov 13, 2016 at 3:37 PM, Nigel A. Gunn G8IFF/W8IFF nigel@ngunn.net wrote:
Try not using Windows. No driver problems with Linux.
You must not have read the original post. It goes into much detail about how the attempt to use Ubuntu Linux failed.
Jim KC9HI
At this point I'd question whether it's actually a Prolific cable. Is it a Yaesu cable? Or is it aftermarket? Do you have a model number or link to it online somewhere?
I recall reading on the sales listing at Universal Radio that this radio comes with a USB cable that isn't for programming.
Just FYI... I could not find any clues online as to the identity of the cable using Google and the info from lsusb. Which is telling me you may have an unknown cable.
On Nov 13, 2016 2:58 PM, "Jim Unroe" rock.unroe@gmail.com wrote:
On Sun, Nov 13, 2016 at 3:37 PM, Nigel A. Gunn G8IFF/W8IFF nigel@ngunn.net wrote:
Try not using Windows. No driver problems with Linux.
You must not have read the original post. It goes into much detail about how the attempt to use Ubuntu Linux failed.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Aubrey Turner at aubrey.c.turner@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com
Linux failed or operator error?
On 13 November 2016 at 15:58 Jim Unroe rock.unroe@gmail.com wrote:
On Sun, Nov 13, 2016 at 3:37 PM, Nigel A. Gunn G8IFF/W8IFF nigel@ngunn.net wrote:
Try not using Windows. No driver problems with Linux.
You must not have read the original post. It goes into much detail about how the attempt to use Ubuntu Linux failed.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
I am using Ubuntu 14.10. The last time i used, the cable and my Baofeng radio were working just fine with my Linux box. In the meantime I have had many Linux updates. Well, now when I use Chirp my radio does not stop transmitting and I receive a Chirp message that the radio is not available. I did a counter check with another (Windows XP) machine, and determined that all components were working fine. So, the problem seems to be in Linux somewhere. Permissions were not (unknowingly) altered, ttyusb port is available. what driver version should I be using? Maybe it got damaged during one of these many updattes.
Am 13.11.2016 um 22:37 schrieb Nigel A. Gunn G8IFF/W8IFF:
Linux failed or operator error?On 13 November 2016 at 15:58 Jim Unroe rock.unroe@gmail.com wrote:
On Sun, Nov 13, 2016 at 3:37 PM, Nigel A. Gunn G8IFF/W8IFF nigel@ngunn.net wrote:
Try not using Windows. No driver problems with Linux.
You must not have read the original post. It goes into much detail about how the attempt to use Ubuntu Linux failed.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to david at dm3bc@darc.de To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
The standard linux drivers should work fine. If you have nothing else other than your radio cable plugged into USB then the port you use should be /dev/ttyUSB0. I recomment you check that you are a member of 'dialout' and 'serial' groups. Generally dialout is correct but I have a copy of Ubuntu running on a Chromebook that put the ports in the serial group. Ubuntu 14.10 should be OK but 16.04 is the current LTS release.
On 13 November 2016 at 17:33 David Widmayer DM3BC@DARC.DE wrote:
I am using Ubuntu 14.10. The last time i used, the cable and my Baofeng radio were working just fine with my Linux box. In the meantime I have had many Linux updates. Well, now when I use Chirp my radio does not stop transmitting and I receive a Chirp message that the radio is not available. I did a counter check with another (Windows XP) machine, and determined that all components were working fine. So, the problem seems to be in Linux somewhere. Permissions were not (unknowingly) altered, ttyusb port is available. what driver version should I be using? Maybe it got damaged during one of these many updattes.
Am 13.11.2016 um 22:37 schrieb Nigel A. Gunn G8IFF/W8IFF:
Linux failed or operator error?On 13 November 2016 at 15:58 Jim Unroe rock.unroe@gmail.com wrote:
On Sun, Nov 13, 2016 at 3:37 PM, Nigel A. Gunn G8IFF/W8IFF nigel@ngunn.net wrote:
Try not using Windows. No driver problems with Linux.
You must not have read the original post. It goes into much detail about how the attempt to use Ubuntu Linux failed.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to david at dm3bc@darc.de To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- Technology will not save us. We have to change the way we live.
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
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.
What makes you think this is a Prolific driver? Is it printed on the CD or something? I did look at Yaesu's website, their driver installation, etc. and I would agree.. it looks like a Prolific 2303 based cable. Now the question is.. is it a REAL prolific, a knock-off, maybe an RT System's cable, or it's fried?
Ubutnu 14.04 LTS:
Now it gets interesting. lsubb reports PID/VID for this cable:
Bus 005 Device 016: ID 26aa:0001The 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.
That's not a recognized Vendor ID for Linux:
http://www.linux-usb.org/usb.ids
Looking at my Yaesu cables via my LInux box (kernel is 4.8.4):
FT1D -- usb 2-1.3.3: new full-speed USB device number 13 using ehci-pci usb 2-1.3.3: New USB device found, idVendor=067b, idProduct=2303 usb 2-1.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 2-1.3.3: Product: USB-Serial Controller usb 2-1.3.3: Manufacturer: Prolific Technology Inc. pl2303 2-1.3.3:1.0: pl2303 converter detected usb 2-1.3.3: pl2303 converter now attached to ttyUSB8 --
FTM400 -- usb 2-1.3.3: new full-speed USB device number 14 using ehci-pci usb 2-1.3.3: New USB device found, idVendor=067b, idProduct=2303 usb 2-1.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 2-1.3.3: Product: USB-Serial Controller usb 2-1.3.3: Manufacturer: Prolific Technology Inc. pl2303 2-1.3.3:1.0: pl2303 converter detected usb 2-1.3.3: pl2303 converter now attached to ttyUSB8 --
I borrowed a neighbor's FT2's cable and it's just that.. a plain USB cable. He says it's the right one.. but its not the SCU-19 cable as the manual shows. I can't try the radio itself as his radio is back at Yaesu for a battery drain issue (8 weeks and counting).
When inserting the USB-serial cable, while the FT2D is in "clone" mode, syslog reports:
The cable needs to be identified as a serial port (which your's isn't). As such, this won't work.
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 don't think you need the second line above. From my notes at http://www.trinityos.com/HAM/CentosDigitalModes/hampacketizing-centos.html#2... . Try this approach (assuming your cable really is a Prolific or Prolific emulated serial chip):
modprobe pl2303 vendor=0x26aa product=0x0001 /bin/echo "26aa 0001" > /sys/bus/usb-serial/drivers/pl2303/new_id
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.
Either the FT2D nor the FTM400 is supported by Chirp today - http://chirp.danplanet.com/projects/chirp/wiki/Wiki
This should be this hard (well, except for windows).
No.. It's usually quite simple unless you're using proprietary cables likt RT System cables. Fortunately, those are using FTDI based chips and the VID/PIDs can be re-programmed to look like a standard serial cable.
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.
The FT1 is supported and I've used it with my SCU-19 cable.
--David KI6ZHD
participants (8)
-
Aubrey Turner -
David Ranch -
David Widmayer -
Jardy -
Jardy Dawson
-
Jim Unroe -
Nigel A. Gunn G8IFF/W8IFF -
Robert Carter