<div dir="ltr"><div class="gmail_default" style="font-size:large">You need the SCU-19 cable to use FT-2D with Chirp </div><div class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" style="font-size:large">Roger G8XAN </div></div><div class="gmail_extra"><br><div class="gmail_quote">On 27 October 2017 at 23:12, Tom Henderson <span dir="ltr">&lt;<a href="mailto:Tom@henderson4.us" target="_blank">Tom@henderson4.us</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    <p>I&#39;ve used the FT1XD with the stock cable and chirp on ubuntu. I&#39;d
      be surprised if there was any significant difference that would
      keep the ft2dr from working, but don&#39;t have one to test with. <br>
    </p>
    <pre class="m_2635809698227527843moz-signature" cols="72">Tom Henderson</pre>
    <div class="m_2635809698227527843moz-cite-prefix">On 10/27/2017 03:06 PM, rick via
      chirp_users wrote:<br>
    </div>
    <blockquote type="cite">
      
      <div style="color:#000;background-color:#fff;font-family:Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:13px">
        <div id="m_2635809698227527843yui_3_16_0_ym19_1_1508736215257_66779">Who has tested
          the FT2DR radio with linux?</div>
        <div id="m_2635809698227527843yui_3_16_0_ym19_1_1508736215257_66779"><br>
        </div>
        <div id="m_2635809698227527843yui_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="m_2635809698227527843yui_3_16_0_ym19_1_1508736215257_66779"><br>
        </div>
        <div id="m_2635809698227527843yui_3_16_0_ym19_1_1508736215257_66779">Chirp works fine
          with my FT7900 and a FTDI cable.</div>
        <div id="m_2635809698227527843yui_3_16_0_ym19_1_1508736215257_66779"><br>
        </div>
        <div id="m_2635809698227527843yui_3_16_0_ym19_1_1508736215257_66779">It appears the
          cable provided with the FT2DR is not a 232 converter.</div>
        <div id="m_2635809698227527843yui_3_16_0_ym19_1_1508736215257_66779"><br>
        </div>
        <div id="m_2635809698227527843yui_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="m_2635809698227527843yui_3_16_0_ym19_1_1508736215257_66779"><br>
        </div>
        <div id="m_2635809698227527843yui_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                 
          &lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;
          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 &quot;empty&quot; straight through USB
          cable.<br>
          <br>
          I can&#39;t use
          <a class="m_2635809698227527843moz-txt-link-freetext" href="https://github.com//torvalds/linux/blob/master/drivers/usb/serial/pl2303.c" target="_blank">https://github.com//torvalds/<wbr>linux/blob/master/drivers/usb/<wbr>serial/pl2303.c</a><br>
          because the chip does not identify.<br>
          <br>
          Am I trying to use the wrong cable? It&#39;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&#39;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  
          &lt;&lt;&lt;&lt;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&#39;t work with the new
          firmware. So this may all be for naught.<br>
          <br>
        </div>
      </div>
      <br>
      <fieldset class="m_2635809698227527843mimeAttachmentHeader"></fieldset>
      <br>
      <pre>______________________________<wbr>_________________
chirp_users mailing list
<a class="m_2635809698227527843moz-txt-link-abbreviated" href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.<wbr>danplanet.com</a>
<a class="m_2635809698227527843moz-txt-link-freetext" href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/<wbr>mailman/listinfo/chirp_users</a>
This message was sent to Tom KM4UQB at <a class="m_2635809698227527843moz-txt-link-abbreviated" href="mailto:tom@henderson4.us" target="_blank">tom@henderson4.us</a>
To unsubscribe, send an email to <a class="m_2635809698227527843moz-txt-link-abbreviated" href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank">chirp_users-unsubscribe@<wbr>intrepid.danplanet.com</a></pre>
    </blockquote>
    <br>
  </div>

<br>______________________________<wbr>_________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.<wbr>danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/<wbr>mailman/listinfo/chirp_users</a><br>
This message was sent to Roger Woods at <a href="mailto:woodsrb@gmail.com">woodsrb@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@<wbr>intrepid.danplanet.com</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><p style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Roger Woods<u></u><u></u></p><p style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Assistant Group Scout Leader  1<sup>st</sup> Sawley (All Saints) Scout Group<u></u><u></u></p><p style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">District Cub Scout Leader Long Eaton<u></u><u></u></p><p style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Training Advisor </p><p style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></p><p style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">GNAS Archery Leader<u></u><u></u></p><p style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">County Archery assessor</p><p style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">NSRA Air Rifle Instructor<u></u><u></u></p><p style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></p><p style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Chairman, Chesterfield and District Scout Radio Club (G8XAN) </p><p style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><br></p><p style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">IRC op ScoutLink<u></u><u></u></p><p style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></p><p style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">0777 4022761</p></div></div></div></div></div></div></div></div></div></div>
</div>