Phil,

Someone gave you this command, but they forgot to start it with "sudo" and if you didn't use sudo the command will not work.

sudo chmod 777 /dev/ttyUSB0

Check the ownership of this:

ls -l /dev/ttyUSB0

This will list the owners of /dev/ttyUSB0.

See if you're in the group that is listed.

Enter this command:

groups

It will return the groups your a member of. You have to belong to the group that is listed when you gave the command: ls -l /dev/ttyUSB0

If you disconnect the USB cable then reconnect it. You can confirm the device name by this command:

sudo dmesg | tail

You should see lines that says "new device" and it will give the address of the new device, that's the device CHIRP needs to use in order to work .

Try that,

David N1EA

On Mon, Dec 23, 2019, 00:20 Phil <phillor9@gmail.com> wrote:

On 9/12/19 3:51 am, Jim Unroe wrote:

Hello everyone,

I said I'd report back after I received another programming cable. This
one contains an FTDI chip and, of course, the radio is still not recognised.

The cable connectors must not be making proper contact. I've read
suggestions that the cable needs to be pressed in firmly. If I press any
harder then I'll surly break something.

What a pain!
--

Regards,
Phil

_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com