Re: [chirp_users] programming Yaesu FT2D
I have a FT1D and had similar problem. Cable would not work with RT systems software.. had to use a micro sd card with RT program. Put card in radio after programming and then uploaded the program from sd card to radio.. worked well
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Robert Carter Sent: Sunday, November 13, 2016 8:49 AM To: chirp_users@intrepid.danplanet.com Subject: [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/ _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Bob Boehme at w2iri@cox.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
RT Software will ONLY work with their custom programmed FTDI cables. With that said, it's very simple to reprogram FTDI devices to have the RT Systems VID:PID and that should work just fine. Once done, you can program back the standard FTDI serial port VID:PID numbers.
Btw, I was reading the FT2 manual closer and on page 161, it seems the radio can be upgraded with a basic micro-USB cable or via the SCU-19 cable. I don't know if the radio can be programmed with the plain USB cable though.
--David KI6ZHD
On 11/13/2016 07:19 PM, Bob Boehme wrote:
I have a FT1D and had similar problem. Cable would not work with RT systems software.. had to use a micro sd card with RT program. Put card in radio after programming and then uploaded the program from sd card to radio.. worked well
I believe RT software checks for a genuine RT cable and doesn't work with other cables.
On 13 November 2016 at 22:19 Bob Boehme w2iri@cox.net wrote:
I have a FT1D and had similar problem. Cable would not work with RT systems software.. had to use a micro sd card with RT program. Put card in radio after programming and then uploaded the program from sd card to radio.. worked well
People,
If you look at the HRO FT2 page http://www.hamradio.com/detail.cfm?pid=H0-013899
You will find this:
*_Supplied Accessories: _* SAD-14B charger YHA-72 antenna SBR-14Li battery USB cable - for data transfer only, programming cable is optional Belt clip, and manual
Carefully note the USB cable supplied in the box and note that it's a DATA cable, not a programming cable.
This whole thread is based on a mistaken assumption that the cable is a programming cable.
IT's NOT...
John - K9IJ
On 11/13/2016 10:04 PM, Nigel A. Gunn G8IFF/W8IFF wrote:
I believe RT software checks for a genuine RT cable and doesn't work with other cables.
On 13 November 2016 at 22:19 Bob Boehme w2iri@cox.net wrote:
I have a FT1D and had similar problem. Cable would not work with RT systems software.. had to use a micro sd card with RT program. Put card in radio after programming and then uploaded the program from sd card to radio.. worked well
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to johnr@k9ij.net at johnr@k9ij.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Many thanks for all the responses. Let me try to hit them all.
John in his response below has a BINGO and nailed my misunderstanding. The in-the-box cable supplied with the FTD2R is apparently a USB cable with a configured PID/VID to allow for only firmware updates to the unit -- page 161 of the manual. This cable's configured PID/VID don't allow it to recognize either of the Windows or Linux pl2303 drivers.
Clearly from the information posted to Yeasu's website the in-the-box supplied cable is a Prolific chipset. However, Yeasu appears to have tweaked the PID/VID to 'cripple' the cable and limit its use.
Coming from ground zero, the radio and manual is daunting. There are a lot of nuances and frankly, the manual isn't well written, so I'm not surprised that I missed the difference between a 'data' cable and a 'programming' cable.
Late yesterday, I was able to figure out how to program it via uploading to the microSD card. But pulling the card out, loading the data to it, then putting the microSD card back into the FT2DR is extremely time consuming and inefficient. (And if not careful you can fat finger the microSD card and break it or the slot. I've had to use tweezers to pull the card out -- I can't get my fingers in grab the card.) The Yeasu ADMS-8 software appears to have limited functionality.
Programming via the radio UI is also possible, but slow and inefficient. But, I did 6 or 7 local repeaters yesterday.
So my next question is does the list have a recommendation on a 'programming' cable that I should get?
Has anyone updated the firmware for either the FT1D or FT2D with the supplied cable? Any failures?
And yes, I was mistaken but I'm trying to figure this all out!
Bob FC1FAC
On 11/14/2016 12:29 AM, John Rice wrote:
People,
If you look at the HRO FT2 page http://www.hamradio.com/detail.cfm?pid=H0-013899
You will find this:
*_Supplied Accessories: _* SAD-14B charger YHA-72 antenna SBR-14Li battery USB cable - for data transfer only, programming cable is optional Belt clip, and manual
Carefully note the USB cable supplied in the box and note that it's a DATA cable, not a programming cable.
This whole thread is based on a mistaken assumption that the cable is a programming cable.
IT's NOT...
John - K9IJ
Hello Bob,
Clearly from the information posted to Yeasu's website the in-the-box supplied cable is a Prolific chipset. However, Yeasu appears to have tweaked the PID/VID to 'cripple' the cable and limit its use.
That's not correct. The USB cable Yaesu provided for the FT2 is just a vanilla USB cable. The VID:PID you're seeing is coming from the Yaesu FT2D radio itself. I bet this is a MUXed USB chip (maybe similar to the CP-102) chips that can do multiple things (this is how say the Kenwood TS590SG works too). That's just a guess and there is very little information out there on this port, how say the Camera MIC accessory works with it, etc. Yaesu has not offered any details though people have been asking for years.
Coming from ground zero, the radio and manual is daunting. There are a lot of nuances and frankly, the manual isn't well written, so I'm not surprised that I missed the difference between a 'data' cable and a 'programming' cable.
It's also a change in behavior as the FT1D didn't support direct USB connectivity for firmware updates like this.
Late yesterday, I was able to figure out how to program it via uploading to the microSD card. But pulling the card out, loading the data to it, then putting the microSD card back into the FT2DR is extremely time consuming and inefficient. (And if not careful you can fat finger the microSD card and break it or the slot. I've had to use tweezers to pull the card out -- I can't get my fingers in grab the card.) The Yeasu ADMS-8 software appears to have limited functionality.
Yaesu provided a microSD card extration tool as part of the FT1D radio for this very reason (it's just a set of plastic tweasers).
Programming via the radio UI is also possible, but slow and inefficient. But, I did 6 or 7 local repeaters yesterday.
So my next question is does the list have a recommendation on a 'programming' cable that I should get?
Sounds like the RT Systems cable and software is your only option today. Maybe in the future, someone will be willing to reverse engineer the FT2 programming signalling via the SCU-19 cable. Btw, some time ago, RT Systems was recommending to write to the FT2 memories file to the SD card (via a USB card reader). You would then upload to the radio via the SD import on the radio itself. They might have added support for the programming cable since then. I would reach out to them and see if that's still the case.
Has anyone updated the firmware for either the FT1D or FT2D with the supplied cable? Any failures?
I've upgraded my FT1 with the SCU-19 cable w/o any issues. It's critical you follow every step (must be connected to a power source), flipping the programming switch, etc. The FT2 might be different so you need to read the instructions.
--David KI6ZHD
Thanks David. I stand corrected. I have some work ahead of me to get this all figured out.
I'm willing to support some experimentation with the FT2DR. Just so long as I don't brick it! Just another embedded system to play with.
On 11/14/2016 12:37 PM, David Ranch wrote:
Hello Bob,
Clearly from the information posted to Yeasu's website the in-the-box supplied cable is a Prolific chipset. However, Yeasu appears to have tweaked the PID/VID to 'cripple' the cable and limit its use.
That's not correct. The USB cable Yaesu provided for the FT2 is just a vanilla USB cable. The VID:PID you're seeing is coming from the Yaesu FT2D radio itself. I bet this is a MUXed USB chip (maybe similar to the CP-102) chips that can do multiple things (this is how say the Kenwood TS590SG works too). That's just a guess and there is very little information out there on this port, how say the Camera MIC accessory works with it, etc. Yaesu has not offered any details though people have been asking for years.
Coming from ground zero, the radio and manual is daunting. There are a lot of nuances and frankly, the manual isn't well written, so I'm not surprised that I missed the difference between a 'data' cable and a 'programming' cable.
It's also a change in behavior as the FT1D didn't support direct USB connectivity for firmware updates like this.
Late yesterday, I was able to figure out how to program it via uploading to the microSD card. But pulling the card out, loading the data to it, then putting the microSD card back into the FT2DR is extremely time consuming and inefficient. (And if not careful you can fat finger the microSD card and break it or the slot. I've had to use tweezers to pull the card out -- I can't get my fingers in grab the card.) The Yeasu ADMS-8 software appears to have limited functionality.
Yaesu provided a microSD card extration tool as part of the FT1D radio for this very reason (it's just a set of plastic tweasers).
Programming via the radio UI is also possible, but slow and inefficient. But, I did 6 or 7 local repeaters yesterday.
So my next question is does the list have a recommendation on a 'programming' cable that I should get?
Sounds like the RT Systems cable and software is your only option today. Maybe in the future, someone will be willing to reverse engineer the FT2 programming signalling via the SCU-19 cable. Btw, some time ago, RT Systems was recommending to write to the FT2 memories file to the SD card (via a USB card reader). You would then upload to the radio via the SD import on the radio itself. They might have added support for the programming cable since then. I would reach out to them and see if that's still the case.
Has anyone updated the firmware for either the FT1D or FT2D with the supplied cable? Any failures?
I've upgraded my FT1 with the SCU-19 cable w/o any issues. It's critical you follow every step (must be connected to a power source), flipping the programming switch, etc. The FT2 might be different so you need to read the instructions.
--David KI6ZHD
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to KC1FAC at carterrj@verizon.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Not sure what cable you have, but according to Yaesu website, you need the SCU-19.
On 11/14/2016 01:33 PM, Robert Carter wrote:
Thanks David. I stand corrected. I have some work ahead of me to get this all figured out.
I'm willing to support some experimentation with the FT2DR. Just so long as I don't brick it! Just another embedded system to play with.
On 11/14/2016 12:37 PM, David Ranch wrote:
Hello Bob,
Clearly from the information posted to Yeasu's website the in-the-box supplied cable is a Prolific chipset. However, Yeasu appears to have tweaked the PID/VID to 'cripple' the cable and limit its use.
That's not correct. The USB cable Yaesu provided for the FT2 is just a vanilla USB cable. The VID:PID you're seeing is coming from the Yaesu FT2D radio itself. I bet this is a MUXed USB chip (maybe similar to the CP-102) chips that can do multiple things (this is how say the Kenwood TS590SG works too). That's just a guess and there is very little information out there on this port, how say the Camera MIC accessory works with it, etc. Yaesu has not offered any details though people have been asking for years.
Coming from ground zero, the radio and manual is daunting. There are a lot of nuances and frankly, the manual isn't well written, so I'm not surprised that I missed the difference between a 'data' cable and a 'programming' cable.
It's also a change in behavior as the FT1D didn't support direct USB connectivity for firmware updates like this.
Late yesterday, I was able to figure out how to program it via uploading to the microSD card. But pulling the card out, loading the data to it, then putting the microSD card back into the FT2DR is extremely time consuming and inefficient. (And if not careful you can fat finger the microSD card and break it or the slot. I've had to use tweezers to pull the card out -- I can't get my fingers in grab the card.) The Yeasu ADMS-8 software appears to have limited functionality.
Yaesu provided a microSD card extration tool as part of the FT1D radio for this very reason (it's just a set of plastic tweasers).
Programming via the radio UI is also possible, but slow and inefficient. But, I did 6 or 7 local repeaters yesterday.
So my next question is does the list have a recommendation on a 'programming' cable that I should get?
Sounds like the RT Systems cable and software is your only option today. Maybe in the future, someone will be willing to reverse engineer the FT2 programming signalling via the SCU-19 cable. Btw, some time ago, RT Systems was recommending to write to the FT2 memories file to the SD card (via a USB card reader). You would then upload to the radio via the SD import on the radio itself. They might have added support for the programming cable since then. I would reach out to them and see if that's still the case.
Has anyone updated the firmware for either the FT1D or FT2D with the supplied cable? Any failures?
I've upgraded my FT1 with the SCU-19 cable w/o any issues. It's critical you follow every step (must be connected to a power source), flipping the programming switch, etc. The FT2 might be different so you need to read the instructions.
--David KI6ZHD
I have access to the FT-1d and used the cable that came with it for programming. No problems.
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 14, 2016, at 08:49, Robert Carter carterrj@verizon.net wrote:
Many thanks for all the responses. Let me try to hit them all.
John in his response below has a BINGO and nailed my misunderstanding. The in-the-box cable supplied with the FTD2R is apparently a USB cable with a configured PID/VID to allow for only firmware updates to the unit -- page 161 of the manual. This cable's configured PID/VID don't allow it to recognize either of the Windows or Linux pl2303 drivers.
Clearly from the information posted to Yeasu's website the in-the-box supplied cable is a Prolific chipset. However, Yeasu appears to have tweaked the PID/VID to 'cripple' the cable and limit its use.
Coming from ground zero, the radio and manual is daunting. There are a lot of nuances and frankly, the manual isn't well written, so I'm not surprised that I missed the difference between a 'data' cable and a 'programming' cable.
Late yesterday, I was able to figure out how to program it via uploading to the microSD card. But pulling the card out, loading the data to it, then putting the microSD card back into the FT2DR is extremely time consuming and inefficient. (And if not careful you can fat finger the microSD card and break it or the slot. I've had to use tweezers to pull the card out -- I can't get my fingers in grab the card.) The Yeasu ADMS-8 software appears to have limited functionality.
Programming via the radio UI is also possible, but slow and inefficient. But, I did 6 or 7 local repeaters yesterday.
So my next question is does the list have a recommendation on a 'programming' cable that I should get?
Has anyone updated the firmware for either the FT1D or FT2D with the supplied cable? Any failures?
And yes, I was mistaken but I'm trying to figure this all out!
Bob FC1FAC
On 11/14/2016 12:29 AM, John Rice wrote: People,
If you look at the HRO FT2 page http://www.hamradio.com/detail.cfm?pid=H0-013899
You will find this:
*_Supplied Accessories: _* SAD-14B charger YHA-72 antenna SBR-14Li battery USB cable - for data transfer only, programming cable is optional Belt clip, and manual
Carefully note the USB cable supplied in the box and note that it's a DATA cable, not a programming cable.
This whole thread is based on a mistaken assumption that the cable is a programming cable.
IT's NOT...
John - K9IJ
_______________________________________________ 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
Many thanks. Looks like that is what I'll have to do for the time being.
On 11/13/2016 10:19 PM, Bob Boehme wrote:
I have a FT1D and had similar problem. Cable would not work with RT systems software.. had to use a micro sd card with RT program. Put card in radio after programming and then uploaded the program from sd card to radio.. worked well
participants (7)
-
Bob Boehme -
David Ranch -
Jardy Dawson -
John Rice -
Nigel A. Gunn G8IFF/W8IFF -
Robert Carter -
W Paul Mills