Hi Matthew, here is my attached output from chirpw...
Kindly,
Robert
On 4/6/21 9:49 PM, Matthew Poletiek wrote:
> Hi Robert,
>
> I see Linux sees the device just fine, and you should be in the right
> groups. I'd add the 'usb' group just in case as well.
>
> If that doesn't work then maybe the output of CHIRP run in the command
> line might hint at whats going wrong.
>
> Also, how did you install this? You might be missing some Python 2
> dependencies. Personally I use Gentoo and they ditched Python 2 a
> while back and we lost CHIRP due to lack of Python 3 support so I
> forked and use this version instead:
> https://github.com/mpoletiek/py3-CHIRP
>
> But before you try that, let's add rabbit to the usb group if there is
> one and see what CHIRP is outputting when run from a terminal.
> -------------------------------------------
> Matthew Poletiek
> 303.810.9082
> [email protected]
> www.matthewpoletiek.com
>
>
> On Tue, Apr 6, 2021 at 7:20 PM Robert <[email protected]> wrote:
>> Hi Matthew, user is in the dialout group, which is the correct group for
>> /dev/ttyUSB0.
>>
>> rabbit@ganymede:~$ cat /etc/group | grep -i rabbit
>> adm:x:4:syslog,rabbit
>> dialout:x:20:rabbit
>> cdrom:x:24:rabbit
>> sudo:x:27:rabbit
>> dip:x:30:rabbit
>> plugdev:x:46:rabbit
>> lpadmin:x:120:rabbit
>> lxd:x:131:rabbit
>> rabbit:x:1000:
>> sambashare:x:132:rabbit
>> rabbit@ganymede:~$ ll /dev/ttyUSB0
>> crw-rw---- 1 root dialout 188, 0 Apr 6 19:10 /dev/ttyUSB0
>>
>> I wasn't sure that there may be a new graphical device manager I did not
>> know about in Ubuntu. And why not? I don't think there is a System menu,
>> either! So back to the command line...I started with Slackware 0.96, so not
>> a noob to Linux, but it has been awhile since serious sysadmin hacking and
>> never before any serial work. I am a noob to Chirp. As I mentioned earlier,
>> my ham radio appears to be on /dev/ttyUSB0:
>>
>> rabbit@ganymede:~$ dmesg | grep tty
>> [ 0.108706] printk: console [tty0] enabled
>> [ 0.396467] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a
>> 16550A
>> [ 0.418518] 0000:00:16.3: ttyS4 at I/O 0xf0e0 (irq = 19, base_baud =
>> 115200) is a 16550A
>> [ 3.348131] usb 1-1.1.3: FTDI USB Serial Device converter now attached to
>> ttyUSB0
>>
>> Kindly,
>> Robert
>>
>> . .. ... ‘...^,^
>>
>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>
>> On Tuesday, April 6th, 2021 at 7:21 PM, Matthew Poletiek
>> <[email protected]> wrote:
>>
>>> I'll just add you can see your current groups with;
>>>
>>> `cat /etc/group | grep -i <username>`
>>>
>>> Matthew Poletiek
>>>
>>> 303.810.9082
>>>
>>> [email protected]
>>>
>>> www.matthewpoletiek.com
>>>
>>> On Tue, Apr 6, 2021 at 6:20 PM Matthew Poletiek
>>>
>>> [email protected] wrote:
>>>
>>>> Hi Robert,
>>>>
>>>> You might want to check to make sure your user has proper permissions.
>>>>
>>>> In linux, typically the groups you might need for this kind of
>>>>
>>>> operation include `dialout`, `usb`, and while you're at it you might
>>>>
>>>> as well include `plugdev`.
>>>>
>>>> The command to add your user to a group might be `sudo gpasswd -a <user>
>>>> group`.
>>>>
>>>> Once thats finished you might need to refresh your profile. Either try
>>>>
>>>> opening CHIRP in a new terminal, or log out and log back in.
>>>> ------------------------------------------------------------------------------------------------------------------------------------
>>>>
>>>> Matthew Poletiek
>>>>
>>>> 303.810.9082
>>>>
>>>> [email protected]
>>>>
>>>> www.matthewpoletiek.com
>>>>
>>>> On Tue, Apr 6, 2021 at 5:56 PM Robert via chirp_users
>>>>
>>>> [email protected] wrote:
>>>>
>>>>> Nigel,
>>>>>
>>>>> Here is some more info, I think this is saying it is attached to
>>>>> /dev/ttyUSB0, but same issue.
>>>>>
>>>>> rabbit@ganymede:/dev$ dmesg | grep tty
>>>>>
>>>>> [ 0.108543] printk: console [tty0] enabled
>>>>>
>>>>> [ 0.396294] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a
>>>>> 16550A
>>>>>
>>>>> [ 0.418318] 0000:00:16.3: ttyS4 at I/O 0xf0e0 (irq = 19, base_baud =
>>>>> 115200) is a 16550A
>>>>>
>>>>> [ 9667.132474] usb 1-1.1.3: FTDI USB Serial Device converter now attached
>>>>> to ttyUSB0
>>>>>
>>>>> [10669.642560] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now
>>>>> disconnected from ttyUSB0
>>>>>
>>>>> [10670.495576] usb 1-1.1.3: FTDI USB Serial Device converter now attached
>>>>> to ttyUSB0
>>>>>
>>>>> Kindly,
>>>>>
>>>>> Robert
>>>>>
>>>>> . .. ... ‘...^,^
>>>>>
>>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>>>>
>>>>> On Tuesday, April 6th, 2021 at 5:51 PM, Nigel A. Gunn G8IFF/W8IFF
>>>>> [email protected] wrote:
>>>>>
>>>>>> Usually /dev/ttyUSB0 unless you already have another serial device
>>>>>> already plugged in to a USB port.
>>>>>>
>>>>>> Go to file manager and look in /dev/ and see what appears and disappears
>>>>>> when you plun in and unplug the cable.
>>>>>>
>>>>>>> On 06/04/2021 17:34 Robert via chirp_users
>>>>>>> [email protected] wrote:
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> Total noob, here. Taking my exams on Thursday. Got my TIDRADIO UV-5R
>>>>>>> and the FTDI cable. How can I detect which /dev/tty is being used for
>>>>>>> the FTDI connection to my radio? I tried /dev/ttyS0 and /dev/ttyUSB0
>>>>>>> which resulted in the error 'Radio did not respond'.
>>>>>>>
>>>>>>> Kindly,
>>>>>>>
>>>>>>> Robert
>>>>>>>
>>>>>>> . .. ... ‘...^,^
>>>>>>>
>>>>>>> _______________________________________________ chirp_users mailing
>>>>>>> list [email protected]
>>>>>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message
>>>>>>> was sent to Nigel Gunn, W8IFF at [email protected] To unsubscribe, send
>>>>>>> an email to [email protected]
>>>>>> Nigel A. Gunn, ///shoulders.outwards.resolutions tel +1-937-971-0366
>>>>>>
>>>>>> Amateur Radio G8IFF W8IFF and GMRS WRBV701, e-mail [email protected] www
>>>>>> http://www.ngunn.net
>>>>> chirp_users mailing list
>>>>>
>>>>> [email protected]
>>>>>
>>>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>>>>
>>>>> This message was sent to Matthew Poletiek at [email protected]
>>>>>
>>>>> To unsubscribe, send an email to
>>>>> [email protected]
rabbit@ganymede:~/Downloads$ chirpw --version
WARNING: python-future package is not available; chirp.drivers.anytone778uv
requires it
WARNING: python-future package is not available; chirp.drivers.ga510 requires it
WARNING: python-future package is not available; chirp.drivers.ic2730 requires
it
WARNING: python-future package is not available; chirp.drivers.tk8180 requires
it
WARNING: python-future package is not available; chirp.drivers.tmd710 requires
it
CHIRP daily-20210406 on Linux - Ubuntu 20.04.2 LTS (Python 2.7.18)
rabbit@ganymede:~/Downloads$ chirpw
WARNING: python-future package is not available; chirp.drivers.anytone778uv
requires it
WARNING: python-future package is not available; chirp.drivers.ga510 requires it
WARNING: python-future package is not available; chirp.drivers.ic2730 requires
it
WARNING: python-future package is not available; chirp.drivers.tk8180 requires
it
WARNING: python-future package is not available; chirp.drivers.tmd710 requires
it
(process:8238): Gtk-WARNING **: 10:35:41.446: Locale not supported by C library.
Using the fallback 'C' locale.
ERROR: uv5r._ident_radio: Radio did not respond
ERROR: uv5r._ident_radio: Radio did not respond
ERROR: -- Exception: --
ERROR: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/chirp/ui/clone.py", line 255, in run
self.__radio.sync_in()
File "/usr/lib/python2.7/dist-packages/chirp/drivers/uv5r.py", line 817, in
sync_in
self._mmap = _do_download(self)
File "/usr/lib/python2.7/dist-packages/chirp/drivers/uv5r.py", line 539, in
_do_download
data = _ident_radio(radio)
File "/usr/lib/python2.7/dist-packages/chirp/drivers/uv5r.py", line 534, in
_ident_radio
raise error
RadioError: Radio did not respond
ERROR: ----------------
ERROR: Clone failed: Radio did not respond
ERROR: --- Exception Dialog: Radio did not respond ---
ERROR: None
ERROR: ----------------------------
_______________________________________________
chirp_users mailing list
[email protected]
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to [email protected] at [email protected]
To unsubscribe, send an email to [email protected]
