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.
The drivers in the OS make the USB chip look like a standard serial port and CHIRP interfaces with that.
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).
On 1/13/19 11:38 AM, Glenn At Home wrote:
I did not think you could use a cable that was made for another radio. That is interesting if you have done this in the past. I figured that the chip was specific to the radio. Glenn ----- Original Message ----- *From:* Pat Anderson mailto:anderson5420@gmail.com *To:* Discussion of CHIRP mailto:chirp_users@intrepid.danplanet.com *Sent:* Sunday, January 13, 2019 11:18 AM *Subject:* [chirp_users] Problem with CHIRP under Ubuntu Linux
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.
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.
What cable would you recommend, or what else could I try in Ubuntu if it is not the cable?
Thanks!
Pat Anderson KD7OAC
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Glenn at glennervin@cableone.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Aubrey Turner at aubrey.c.turner@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com