[chirp_users] FT-65 cable - any aftermarket work?

[David Ranch]

Last time I checked, RT Systems cables use FTDI USB to Serial chips but 
they are programmed with non-standard USB VID:PID to make them 
"proprietary".  If you look at http://www.linux-usb.org/usb.ids and 
search for "RT Systems", you can see a short list of some known VID:PID 
combinations that Linux will then load the FTDI kernel module and treat 
the USB device as a serial port.  For unknown ports, I don't know if you 
can fake out Windows to recognize RT System cables as a standard serial 
cable but you CAN do this with Linux for ANY VID:VID using either some 
USB or UDEV tricks.

I wrote the following up some time ago to either temporarily or 
permanently recognize the RT Cable and create a /dev/ft857_prog serial 
device instead of a generically named /dev/ttyUSB0 device:


Temporary USB recognition (this example does this for a Timewave 
Navigator device):
https://www.trinityos.com/HAM/CentosDigitalModes/hampacketizing-centos.html#2c.kernelnavigatorudev


Permanent USB recognition across reboots (this example is for one of RT 
Systems cables for a Yaesu FT857):

https://www.trinityos.com/HAM/CentosDigitalModes/hampacketizing-centos.html#1d.presetup-udevusbserial
    --
          #Device #3 - RT Systems CT-62B 1-port USB to serial adapter 
for FT817/857/897 (FTDI-based)
          #
          #NOTE: This adapter is NOT recognized by the Linux kernel as a 
valid
          #      serial device.  RT System does this ON PURPOSE so their 
programming
          #      software will only work with their cables!  You can 
change these IDs
          #      if you wish with 
http://www.ftdichip.com/Support/Utilities.htm#FT_Prog
          #
          #      Alternatively, the following will run a script to poke 
the RT Systems
          #      USB IDs into the kernel FTDI driver so it can recognize 
the new
          #      device as a serial port.
          #
          BUS=="usb", SYSFS{idVendor}=="2100", SYSFS{idProduct}=="9e56", 
ENV{ID_MM_DEVICE_IGNORE}="1", RUN+="/usr/local/sbin/RTSystems-addports.sh &"
          SUBSYSTEM=="tty", ATTRS{idVendor}=="2100", 
ATTRS{idProduct}=="9e56", SYMLINK+="ft857_prog"
    --

--David
KI6ZHD



On 08/22/2022 11:34 AM, Dave Matthews wrote:
> Trying to avoid RT systems.  Not sure if they will work with CHIRP or 
> if it is only for their software.
>
> Dave
> W2IJL
>
> On Mon, Aug 22, 2022 at 2:32 PM KE5EOT <ke5eot at gmail.com 
> <mailto:ke5eot at gmail.com>> wrote:
>
>     Gigaparts shows the RT Systems cable to be in stock.
>
>     https://www.gigaparts.com/usb-55-programming-and-data-cable.html?msclkid=ebfffb88e3301f63459a988b29a1dcfa
>
>     Randy (KE5EOT)
>        ARRL, QCWA, ARES, RACES, ROWH
>           http://ke5eot.webs.com
>
>     On 8/22/22 1:18 PM, Dave Matthews wrote:
>>     Looking at picking up a ft-65 but the scu-35 cable looks to be
>>     out of stock with no eta.  Anyone using any of the Amazon clones
>>     successfully?  I will be using Ubuntu so most of the driver
>>     issues are not a problem.
>>
>>     Dave
>>     W2IJL
>>
>>     _______________________________________________
>>     chirp_users mailing list
>>     chirp_users at intrepid.danplanet.com
>>     <mailto:chirp_users at intrepid.danplanet.com>
>>     http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>     This message was sent to Randy Morton atke5eot at gmail.com <mailto:ke5eot at gmail.com>
>>     To unsubscribe, send an email tochirp_users-unsubscribe at intrepid.danplanet.com
>>     <mailto:chirp_users-unsubscribe at intrepid.danplanet.com>
>>     To report this email as off-topic, please emailchirp_users-owner at intrepid.danplanet.com
>>     <mailto:chirp_users-owner at intrepid.danplanet.com>
>>     Searchable archive:https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
>
>     _______________________________________________
>     chirp_users mailing list
>     chirp_users at intrepid.danplanet.com
>     <mailto:chirp_users at intrepid.danplanet.com>
>     http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>     This message was sent to W2IJL at n36078 at gmail.com
>     <mailto:n36078 at gmail.com>
>     To unsubscribe, send an email to
>     chirp_users-unsubscribe at intrepid.danplanet.com
>     <mailto:chirp_users-unsubscribe at intrepid.danplanet.com>
>     To report this email as off-topic, please email
>     chirp_users-owner at intrepid.danplanet.com
>     <mailto:chirp_users-owner at intrepid.danplanet.com>
>     Searchable archive:
>     https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
>
>
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to David Ranch at chirp at trinnet.net
> To unsubscribe, send an email to chirp_users-unsubscribe at intrepid.danplanet.com
> To report this email as off-topic, please email chirp_users-owner at intrepid.danplanet.com
> Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20220822/f231b7b0/attachment.html