<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>The vast majority of radios just use serial protocol. The chip
in the cable just converts from USB to the older serial
protocols. I have a multi-radio USB cable that has different tips
for different radios. It will work across the Baofeng, Wouxun,
and Yaesu radios that I have. <br>
</p>
<p>The drivers in the OS make the USB chip look like a standard
serial port and CHIRP interfaces with that.</p>
<p>As to this issue... if you don't see the cable in Ubuntu using
'lsusb' after plugging it in, then you have a potential bad
cable. You might try comparing the output of lsusb from before
and after plugging in the cable to see if it's recognized and, if
so, what the Chromebook is seeing it as (the USB ID is what it
uses to determine which driver to load).<br>
</p>
<div class="moz-cite-prefix">On 1/13/19 11:38 AM, Glenn At Home
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:5B4F4F48CDE84D898707A2E7FDF71188@NUCPPYH">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<meta name="GENERATOR" content="MSHTML 11.00.9600.19236">
<style></style>
<div><font size="2" face="Arial">I did not think you could use a
cable that was made for another radio.</font></div>
<div><font size="2" face="Arial">That is interesting if you have
done this in the past.</font></div>
<div><font size="2" face="Arial">I figured that the chip was
specific to the radio.</font></div>
<div><font size="2" face="Arial">Glenn</font></div>
<div style="FONT: 10pt arial">----- Original Message -----
<div style="BACKGROUND: #e4e4e4; font-color: black"><b>From:</b>
<a title="anderson5420@gmail.com"
href="mailto:anderson5420@gmail.com" moz-do-not-send="true">Pat
Anderson</a> </div>
<div><b>To:</b> <a title="chirp_users@intrepid.danplanet.com"
href="mailto:chirp_users@intrepid.danplanet.com"
moz-do-not-send="true">Discussion of CHIRP</a> </div>
<div><b>Sent:</b> Sunday, January 13, 2019 11:18 AM</div>
<div><b>Subject:</b> [chirp_users] Problem with CHIRP under
Ubuntu Linux</div>
</div>
<div><br>
</div>
<div dir="ltr">I have CHIRP installed on an Asus C302 Chromebook
with Ubuntu 16.04 (Xenial) installed with crouton, I live in
Washington State but am in Arizona for the winter, and just
bought another BaoFeng UV-5R to use here ($24.99 on Amaqzon, how
could I not). I had no programming cable, so I borrowed one from
a friend here at the RV Park, it is a labelled "TYT." I also
have a 2011 MacBook Pro with CHIRP installed which I have used
successfully many times before. What is happening is that when I
connect the BaoFeng via the cable (turned off), and go toe
"Download from Radio," I can put "BaoFeng" and" UV-5R" in the
dialog box from the dropdown lists but the in Port dialog,
nothing shows up. Naturally, when I turn the radio on and press
the button to download, it gives a "Device not found" error.
There is a /dev/tty file that I have CHMODed to 777, and I tried
typing "/dev/tty" in the box same error. The cable is pushed
fully into the radio, so that is not the problem. When I connect
to the MacBook, and do the same thing, the only device that
shows up is the Bluetooth device.
<div><br>
</div>
<div>I have deduced it must be the cable. I have several
programming cables back home that I know work - and they were
cheap generic cables that would make Windows choke (fake
Prolific chips). I don't want to buy a cable on Amazon or
Cheapham without knowing whether it will work or not.I don't
know if Linux cares about the chip. I don't think MacOS cares.</div>
<div><br>
</div>
<div>What cable would you recommend, or what else could I try in
Ubuntu if it is not the cable?</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div>Pat Anderson</div>
<div>KD7OAC</div>
</div>
<p>
</p>
<hr>
_______________________________________________<br>
chirp_users mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br>
<a class="moz-txt-link-freetext" href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Glenn at <a class="moz-txt-link-abbreviated" href="mailto:glennervin@cableone.net">glennervin@cableone.net</a><br>
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>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-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 Aubrey Turner at <a class="moz-txt-link-abbreviated" href="mailto:aubrey.c.turner@gmail.com">aubrey.c.turner@gmail.com</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></pre>
</blockquote>
</body>
</html>