<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div style="color:#000; background-color:#fff; font-family:Helvetica
Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px">
<div id="yui_3_16_0_ym19_1_1508736215257_66779">Who has tested the
FT2DR radio with linux?</div>
<div id="yui_3_16_0_ym19_1_1508736215257_66779"><br>
</div>
<div id="yui_3_16_0_ym19_1_1508736215257_66779">What USB cable did
you use?<br>
<br>
My spidey senses are telling me no one has tested this
combination.</div>
<div id="yui_3_16_0_ym19_1_1508736215257_66779"><br>
</div>
<div id="yui_3_16_0_ym19_1_1508736215257_66779">Chirp works fine
with my FT7900 and a FTDI cable.</div>
<div id="yui_3_16_0_ym19_1_1508736215257_66779"><br>
</div>
<div id="yui_3_16_0_ym19_1_1508736215257_66779">It appears the
cable provided with the FT2DR is not a 232 converter.</div>
<div id="yui_3_16_0_ym19_1_1508736215257_66779"><br>
</div>
<div id="yui_3_16_0_ym19_1_1508736215257_66779">I am also guessing
that there is a PL2303 chip in the radio. (Yaesu provides PL2303
drivers for windows.)</div>
<div id="yui_3_16_0_ym19_1_1508736215257_66779"><br>
</div>
<div id="yui_3_16_0_ym19_1_1508736215257_66779">Problem is it does
not identify itself as such so Linux does not know what to do
with it.<br>
<br>
this is the output of lsusb with the radio plugged in and turned
on<br>
<br>
rick@rick-ham ~ $ lsusb<br>
Bus 001 Device 002: ID 0bda:0111 Realtek Semiconductor Corp.
RTS5111 Card Reader Controller<br>
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br>
Bus 002 Device 002: ID 0c45:7412 Microdia <br>
Bus 002 Device 004: ID 26aa:0001
<<<<<<<<<<<<<<<
this is the radio, no ID<br>
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
<br>
NOTE - This device disappears when the send button on the radio
is activated and the radio reports an Error.<br>
<br>
<br>
<br>
This is the output of lsusb with the cord unplugged at the radio
(cord still plugged into computer)<br>
<br>
rick@rick-ham ~ $ lsusb<br>
Bus 001 Device 002: ID 0bda:0111 Realtek Semiconductor Corp.
RTS5111 Card Reader Controller<br>
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br>
Bus 002 Device 002: ID 0c45:7412 Microdia <br>
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
<br>
Given this, I conclude this is an "empty" straight through USB
cable.<br>
<br>
I can't use
<a class="moz-txt-link-freetext" href="https://github.com//torvalds/linux/blob/master/drivers/usb/serial/pl2303.c">https://github.com//torvalds/linux/blob/master/drivers/usb/serial/pl2303.c</a><br>
because the chip does not identify.<br>
<br>
Am I trying to use the wrong cable? It's possible I mixed up the
cable with another or I received a defective cable.<br>
Yaesu does not offer a cable as an accy, so I can't buy a new
one retail.<br>
<br>
<br>
<br>
This is the output of isusb with my FT7900 cable connected<br>
<br>
lsusb<br>
Bus 001 Device 002: ID 0bda:0111 Realtek Semiconductor Corp.
RTS5111 Card Reader Controller<br>
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br>
Bus 002 Device 002: ID 0c45:7412 Microdia <br>
Bus 002 Device 007: ID 0403:6001 Future Technology Devices
International, Ltd FT232 USB-Serial (UART) IC
<<<<This is it<br>
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
<br>
This is my RT Systems cable connected <br>
<br>
rick@rick-ham ~ $ lsusb<br>
Bus 001 Device 002: ID 0bda:0111 Realtek Semiconductor Corp.
RTS5111 Card Reader Controller<br>
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br>
Bus 002 Device 002: ID 0c45:7412 Microdia <br>
Bus 002 Device 008: ID 2100:9068 RT Systems <br>
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
<br>
rick@rick-ham ~ $ ls /dev | grep tty<br>
tty tty0 tty1 tty10 tty11
tty12 tty13 tty14 tty15 tty16
tty17<br>
tty18 tty19 tty2 tty20 tty21
tty22 tty23 tty24 tty25 tty26
tty27<br>
tty28 tty29 tty3 tty30 tty31
tty32 tty33 tty34 tty35 tty36
tty37<br>
tty38 tty39 tty4 tty40 tty41
tty42 tty43 tty44 tty45 tty46
tty47<br>
tty48 tty49 tty5 tty50 tty51
tty52 tty53 tty54 tty55 tty56
tty57<br>
tty58 tty59 tty6 tty60 tty61
tty62 tty63 tty7 tty8 tty9
ttyprintk<br>
ttyS0 ttyS1 ttyS10 ttyS11 ttyS12 ttyS13
ttyS14 ttyS15 ttyS16 ttyS17 ttyS18<br>
ttyS19 ttyS2 ttyS20 ttyS21 ttyS22 ttyS23
ttyS24 ttyS25 ttyS26 ttyS27 ttyS28<br>
ttyS29 ttyS3 ttyS30 ttyS31 ttyS4 ttyS5
ttyS6 ttyS7 ttyS8 ttyS9<br>
<br>
Not recognised<br>
<br>
Also I see that Yaesu has different ADMS software for the new
firmware version that was just released.<br>
My spidey senses tell me that Chirp won't work with the new
firmware. So this may all be for naught.<br>
<br>
</div>
</div>
</body>
</html>