<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
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 <a class="moz-txt-link-freetext" href="http://www.linux-usb.org/usb.ids">http://www.linux-usb.org/usb.ids</a> 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. <br>
<br>
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:<br>
<br>
<br>
Temporary USB recognition (this example does this for a Timewave
Navigator device):<br>
<a class="moz-txt-link-freetext" href="https://www.trinityos.com/HAM/CentosDigitalModes/hampacketizing-centos.html#2c.kernelnavigatorudev">https://www.trinityos.com/HAM/CentosDigitalModes/hampacketizing-centos.html#2c.kernelnavigatorudev</a><br>
<br>
<br>
Permanent USB recognition across reboots (this example is for one of
RT Systems cables for a Yaesu FT857):<br>
<br>
<a class="moz-txt-link-freetext" href="https://www.trinityos.com/HAM/CentosDigitalModes/hampacketizing-centos.html#1d.presetup-udevusbserial">https://www.trinityos.com/HAM/CentosDigitalModes/hampacketizing-centos.html#1d.presetup-udevusbserial</a><br>
--<br>
#Device #3 - RT Systems CT-62B 1-port USB to serial adapter
for FT817/857/897 (FTDI-based)<br>
#<br>
#NOTE: This adapter is NOT recognized by the Linux kernel
as a valid<br>
# serial device. RT System does this ON PURPOSE so
their programming<br>
# software will only work with their cables! You can
change these IDs<br>
# if you wish with
<a class="moz-txt-link-freetext" href="http://www.ftdichip.com/Support/Utilities.htm#FT_Prog">http://www.ftdichip.com/Support/Utilities.htm#FT_Prog</a><br>
#<br>
# Alternatively, the following will run a script to
poke the RT Systems<br>
# USB IDs into the kernel FTDI driver so it can
recognize the new <br>
# device as a serial port. <br>
#<br>
BUS=="usb", SYSFS{idVendor}=="2100",
SYSFS{idProduct}=="9e56", ENV{ID_MM_DEVICE_IGNORE}="1",
RUN+="/usr/local/sbin/RTSystems-addports.sh &"<br>
SUBSYSTEM=="tty", ATTRS{idVendor}=="2100",
ATTRS{idProduct}=="9e56", SYMLINK+="ft857_prog"<br>
--<br>
<br>
--David<br>
KI6ZHD<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 08/22/2022 11:34 AM, Dave Matthews
wrote:<br>
</div>
<blockquote
cite="mid:CACNsWt9_sYmH37foEAwUrRs4Zs=RYJP6F-cyHDLLHUcbEj0G2w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Trying to avoid RT systems. Not sure if they will work
with CHIRP or if it is only for their software. <br>
</div>
<div><br>
</div>
<div>Dave</div>
<div>W2IJL<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Aug 22, 2022 at 2:32
PM KE5EOT <<a moz-do-not-send="true"
href="mailto:ke5eot@gmail.com">ke5eot@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div> Gigaparts shows the RT Systems cable to be in stock.<br>
<br>
<a moz-do-not-send="true"
href="https://www.gigaparts.com/usb-55-programming-and-data-cable.html?msclkid=ebfffb88e3301f63459a988b29a1dcfa"
target="_blank">https://www.gigaparts.com/usb-55-programming-and-data-cable.html?msclkid=ebfffb88e3301f63459a988b29a1dcfa</a><br>
<pre cols="72">Randy (KE5EOT)
ARRL, QCWA, ARES, RACES, ROWH
<a moz-do-not-send="true" href="http://ke5eot.webs.com" target="_blank">http://ke5eot.webs.com</a>
</pre>
<div>On 8/22/22 1:18 PM, Dave Matthews wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>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.</div>
<div><br>
</div>
<div>Dave</div>
<div>W2IJL<br>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
chirp_users mailing list
<a moz-do-not-send="true" href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a>
<a moz-do-not-send="true" href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a>
This message was sent to Randy Morton at <a moz-do-not-send="true" href="mailto:ke5eot@gmail.com" target="_blank">ke5eot@gmail.com</a>
To unsubscribe, send an email to <a moz-do-not-send="true" href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a>
To report this email as off-topic, please email <a moz-do-not-send="true" href="mailto:chirp_users-owner@intrepid.danplanet.com" target="_blank">chirp_users-owner@intrepid.danplanet.com</a>
Searchable archive: <a moz-do-not-send="true" href="https://www.mail-archive.com/chirp_users@intrepid.danplanet.com" target="_blank">https://www.mail-archive.com/chirp_users@intrepid.danplanet.com</a></pre>
</blockquote>
<br>
</div>
_______________________________________________<br>
chirp_users mailing list<br>
<a moz-do-not-send="true"
href="mailto:chirp_users@intrepid.danplanet.com"
target="_blank">chirp_users@intrepid.danplanet.com</a><br>
<a moz-do-not-send="true"
href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users"
rel="noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to W2IJL at <a moz-do-not-send="true"
href="mailto:n36078@gmail.com" target="_blank">n36078@gmail.com</a><br>
To unsubscribe, send an email to <a moz-do-not-send="true"
href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com"
target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a><br>
To report this email as off-topic, please email <a
moz-do-not-send="true"
href="mailto:chirp_users-owner@intrepid.danplanet.com"
target="_blank">chirp_users-owner@intrepid.danplanet.com</a><br>
Searchable archive: <a moz-do-not-send="true"
href="https://www.mail-archive.com/chirp_users@intrepid.danplanet.com"
rel="noreferrer" target="_blank">https://www.mail-archive.com/chirp_users@intrepid.danplanet.com</a></blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
chirp_users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a>
<a class="moz-txt-link-freetext" href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a>
This message was sent to David Ranch at <a class="moz-txt-link-abbreviated" href="mailto:chirp@trinnet.net">chirp@trinnet.net</a>
To unsubscribe, send an email to <a class="moz-txt-link-abbreviated" href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@intrepid.danplanet.com</a>
To report this email as off-topic, please email <a class="moz-txt-link-abbreviated" href="mailto:chirp_users-owner@intrepid.danplanet.com">chirp_users-owner@intrepid.danplanet.com</a>
Searchable archive: <a class="moz-txt-link-freetext" href="https://www.mail-archive.com/chirp_users@intrepid.danplanet.com">https://www.mail-archive.com/chirp_users@intrepid.danplanet.com</a></pre>
</blockquote>
<br>
</body>
</html>