Geeze! What is he up to now? Cool stuff - Solar - Ham Radio - Linux - DIY - Antennas - Raspberry Pi - Arduino
What is going on here is that there is no vendor ID or product ID for the CT68 cable. 2100 is the Vendor ID (first entry) and the 9068 is the Product ID which needs to be implemented as described above.
Not only does this workaround work on Linux systems such as Ubuntu, but it also works on Raspberry Pi computers as well.
Now that I finally have my FT5 DR programmed, I can start delving into the world of C4FM.
73’s — Mike WB8ERJ
This site uses Akismet to reduce spam. Learn how your comment data is processed.
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
Manage your cookie preferences below:
Essential cookies enable basic functions and are necessary for the proper function of the website.
These cookies are needed for adding comments on this website.
These cookies are used for managing login functionality on this website.
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Service URL: policies.google.com (opens in a new window)
You can find more information in our Cookie Policy and Privacy Policy.
Mike, this was a great compilation. It got me out of the ditch trying to program a new FT5DR on a new computer with latest Linux MINT 21.2 Victoria built on Ubuntu 22.04 Jammy. I did discover a few more things along the way which you might consider adding to your excellent set of instructions.
1) When the RT USB-68 cable was first plugged in, it was detected using “lsusb” but no ttyUSB* VCD as you mention. Check.
2) Adding the file “/etc/udev/rules.d/99-ftdi.rules” fixed problem 1) and creates a ttyUSB0 device. It did take a couple attempts due to making a typo and missing a ” … Check.
3) Now tried to use CHIRP (from the MINT repository) to download from the radio but it would time out with a communications error.
4) To check that the driver was working I used gtkterm to connect to /dev/ttyUSB0. It wouldn’t connect unless I was root. Solution was to add “dialout” to my groups.
> sudo gpasswd –add username dialout
5) CHIRP (the version in the MINT repository) now starts downloading data from the radio rather than just hanging. But, at the very end, spits out an error “module ‘collections’ has no attribute ‘Callable’. Not knowing what this actually means, I downloaded the latest version of CHIRP next-20231217 and now the radio can be downloaded.
Anyway, just wanted to add in the “gotchas” that I ran into, to save someone else trying to figure it out.
Thanks again for documenting this Mike!
Darrell — AF5FX
Glad it all worked out for you Darrell. Yes, I too was using the latest version of Chirp next. For me,upgrading to the latest version was the first thing I did when I ran into troubles thinking that since the FT5DR was a new radio, it just wasn’t in the list. Well it still wasn’t in the list so I had to go down the rabbit hole to figure it out.
Thanks for your input – enjoy your FT5DRi Its a great radio.
— Mike WB8ERJ
Mike, Darrel,
Thank you for documenting! I followed along, but I am not seeing the /dev/ttyUSB0 appear.
Using dmesg I see I am getting this error: “MMU error from client L2T (0) at 0x5001000, pte invalid”
Do you have any suggestions?
Raspberry pi 400 (the one with the white keyboard)
Best Regards,
Mark – KC1JZH
73
OK, Mark here again.
Beyond the error msg I posted before (I don’t see my comment about that posted yet) I have been poking around some more, and I have the following to report and ask:
1. upon running “udevadm control –-reload” the file “/sys/bus/usb-serial/drivers/ftdi_sio/new_id” remains empty, but file size is unchanged at 4096 bytes
2. after plugging in the ct68 cable, lsusb shows the RT Systems cable as usual, dmesg shows something happening, as before, but file “/sys/bus/usb-serial/drivers/ftdi_sio/new_id” remains empty still (using “sudo cat /sys/bus/usb-serial/drivers/ftdi_sio/new_id”), but still file size 4096.
As before, do you have any suggestions?
Best Regards,
Mark – KC1JZH
73
Hello,
Sorry for not getting back to you. For some reason I’m not getting an email notification when a comment is posted.
Unfortunately I don’t know what is going on. KM4ACK posted a video based on this blog post. He wrote a script that does all this automatically.
Here is a link to his video. Hopefully this will get you going.
https://youtu.be/N40yRdFBr-E?si=BayVpYXeYi_RxOM4
— Mike