Thanks for the video, great as always. I used Crossover from Codeweavers on my Ubuntu 22.04 Laptop with the ADMS-14 Software from Yaesu. Installation with no further trbls. I used a SD Card for Backup Exchange between the FT5 and the software. No problems so far. 73

man, i directly subscribed, you explain everything so fine! even me, the slowest of the slowest could understand it!

First of all thank you for the excellent video! Without going in to too many boring details, I’ll try to keep this short, yeah right. I’ve been using Linux Mint Cinnamon for about 4 years. Everything works great, except Chirp. I obtained Chirp using the Software Manager. As I understand that the Software Manager is supposed to have programs that work with the version of Linux using it’s Software Manager. I have no reason to doubt this. While it could be any of the three cables I use, I know one of the cables worked on my friend’s (SK) Windoze machine because he was showing me how easy Chirp was to use. I strongly suspect I have a similar USB driver problem as shown in your video. I’ll be trying your technique when I have a day or two or three (and plenty of bourbon) just to play with the computer. From looking around on KZfaq, I see I’m not the only one in the world having problems getting the later versions of Linux Mint to work with Chirp. I will try to use the command line to see if the technique you show for the Yaesu will work for me using Linux Mint. I’m not sure when I will try this, depending on other projects. I haven’t used the command line function much. Reminds me of using DOS over 45 years ago. Would you consider a KZfaq video for us old timers on getting Chirp, or the USB Drivers, to work with Linux Mint Cinnamon? So far, using lsusb I’ve found out that the OEM Baofeng cable (which worked on my friend’s Windoze machine) is a QinHeng CH340, the 8-in-1 cable is alaso a QinHeng CH340 & the Maxton cable is a Prolific PL2303. If these cables are fake is, or not, anybody’s guess. I suspect the Baofeng is real, but can’t be 100% sure. Getting the proper drivers for Linux Mint Cinnamon appears to be my problem. I feel I’m real close to a solution & I will keep plugging away at it. 73 Dave

After using Chirp with Yaesu HT's, please make sure your channels are "on frequency" afterwards using a rtl_sdr. In my case, about 10% of my memories were off-frequency about 10Khz. Yah, I wouldn't belive me either. I had to restore and old backup to move forward. Fantastic video! as usual!

Awesome video

The same RT systems cable is used for FT2/3/5. 73

Using an SD card to move changes is way better (always had issues with my FT-1D & a cable). I stopped using CHIRP on the Mac since I got my FT-5D.

As airplane pilot I would like to use the Yaesu FT5D as backup emergency radio but aviation frequencies are TX inhibited. Can the TX be enabled for aviation frequencies? thanks

Which Linux are you using? While I like Mint, if it ain't cutting it for drivers, I'll switch.

Yaesu recommends not using chirp. I personally know few people that have and bricked their radios. And yaesu will not cover repair under warranty. Just be careful

If you are going to give RT systems $30 for a cable why not just buy the RT Systems software for the $30 and program the radio with the SD card. No worries about bricking your radio

People are commenting on not using chirp with Yaesu. I have tried the free Yaesu software and had trouble getting it to work. I want to like Yaesu and have two of their radios but my goodness they make themselves especially difficult to like sometimes.

Could you use an SD card and pretend you are writing an FT3?

Using CHIRP has damaged Yaesu radios beyond repair and voided the warranty. Yaesu does not recommend using CHIRP for any programming and to use the free ADMS software.

I wish all amateur radio manufacturers, particularly Yaesu, would stop developing their own proprietary (often Windows only) software to program their radios, and instead contribute to CHIRP to ensure that CHIRP can program their radios before releasing the hardware. It's VERY handy to cut and paste from one radio to the other in CHIRP, as opposed to manually entering all of those repeaters and custom frequencies into a new program.

I get up to the verify by typing in ls /dev | grep ttyUSB* and the red ttyUSB0 does not show up. Did the procedure about 10 times with the same results. I'll keep plugging away at it, while hoping for a solution.