[chirp_users] CHIRP Not Communicating With ComputerS

[D.J.J. Ring, Jr.]

Congrats, Tom.  Good luck with the licensing.

You have to reboot after adding yourself to a group.

You must have rebooted, then once you did, it worked.

73

David N1EA


On Mon, May 14, 2018 at 5:39 PM, Tom Balaban <mototom800 at gmail.com> wrote:
> Thanks D.J.J. Ring, Jr.
>
> I show the same ownership. I added my user name to the TTY group. Still
> didn't work. I then tried running as root (sudo chirpw). Still no joy.
>
>
> ... Six hours later ...
>
> OK. It's now working. How? I haven't the faintest idea. I tried using
> CHIRP-Live but could get it to boot from a USB on any of my EUFI boxes so I
> burned a CD and that booted and I was able to download using both serial
> cables from my Yeasu's and my Baofengs. After adding the 2 new frequencies
> to my seven handhelds I tried it on three laptops, one LinuxLite and two
> Windows 10. All three worked just like they had been working for years. Go
> figure.
>
> Now as to my call sign. I don't have one ... yet. I am working to get my
> Technician Class license, hopefully this summer. In the meantime, all I use
> these radios for is officiating bicycle races from a motorcycle. We always
> use a commercial frequency provided by our sanctioning body of the local
> organizers radio rental service.
>
> Again, many thanks for helping me with this issue.
>
> Best,
> Tom
>
> ------ Original Message ------
> From: "D.J.J. Ring, Jr." <n1ea at arrl.net>
> To: "Discussion of CHIRP" <chirp_users at intrepid.danplanet.com>
> Sent: 5/13/2018 11:11:33 PM
> Subject: Re: [chirp_users] CHIRP Not Communicating With ComputerS
>
> Tom on the Linux computer, send a listing of the /dev/tty*
>
> ls -l /dev/tty*
>
> My tty devices are owned by root and in the tty group.  I'm running Arch
> Linux.
>
> $ groups
>
> sys adm wheel tty uucp games video audio users vboxusers
>
> What's your ham Callsign?
>
> 73
>
> DR
> N1EA
>
>
>
> On Sun, May 13, 2018 at 4:00 PM, Tom Balaban <mototom800 at gmail.com> wrote:
>> I have not had to do anything with my Baofeng and Yaesu radios for quite a
>> while but our group has added some new frequencies so it time to update.
>>
>> Neither my Yaesu VX-6Rs nor my Baofeng UV-5Rs will communicate with either
>> my Linux Netbook or my WIndows 10 computers. In the case of the Linux box,
>> I
>> have added my user name to the Dialout group then rebooted. In the case of
>> the Windows machines I have changed the Baofeng cable to the Prolific
>> 3.2.0.0 driver that I downloaded today from the Miklor site. The Yaesu
>> cable
>> is an FTDI cable and was always recognized previously. The cables are
>> fully
>> inserted in each case and the volume is maxed out. Device Manager shows
>> both
>> cables as working. The Baofeng cable reports as COM7 and the Yaesu cable
>> as
>> COM6
>>
>> I'm never surprised with the Windows machines need some tinkering to work
>> but CHIRP and Linux have always worked will in the past.
>>
>> What am I missing. I suspect it's something simple.
>>
>> Many thanks for reading.
>>
>> Tom
>>
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users at intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>> This message was sent to D.J.J. Ring, Jr. at n1ea at arrl.net
>> To unsubscribe, send an email to
>> chirp_users-unsubscribe at intrepid.danplanet.com
>
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to D.J.J. Ring, Jr. at n1ea at arrl.net
> To unsubscribe, send an email to
> chirp_users-unsubscribe at intrepid.danplanet.com