Project

General

Profile

Actions

Bug #10568

closed

Puxing PX888K can't be read

Added by Mike Williams about 1 year ago. Updated about 1 year ago.

Status:
Not a bug
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
05/09/2023
Due date:
% Done:

0%

Estimated time:
Chirp Version:
next
Model affected:
Puxing PX888K
Platform:
Linux
Debug Log:
I read the instructions above:

Description

I have tried several times and still can not download from this radio.
Help? Thanks.

[2023-05-09 18:50:56,972] chirp.logger - DEBUG: CHIRP next-20230427 on Linux - Linux Mint 21 Vanessa (Python 3.10.6)
Traceback (most recent call last):
File "/usr/bin/chirpw", line 21, in
from chirp.wxui import main
File "/home/mike/.local/lib/python3.10/site-packages/chirp/wxui/main.py", line 45, in
from chirp.wxui import bankedit
File "/home/mike/.local/lib/python3.10/site-packages/chirp/wxui/bankedit.py", line 24, in
from chirp.wxui import memedit
File "/home/mike/.local/lib/python3.10/site-packages/chirp/wxui/memedit.py", line 270, in
class ChirpChoiceColumn(ChirpMemoryColumn):
File "/home/mike/.local/lib/python3.10/site-packages/chirp/wxui/memedit.py", line 272, in ChirpChoiceColumn
_TITLE1 = _('Tuning Step')
NameError: name '
' is not defined
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 153, in apport_excepthook
with os.fdopen(os.open(pr_filename,
FileNotFoundError: [Errno 2] No such file or directory: '/var/crash/_usr_bin_chirpw.1000.crash'

Original exception was:
Traceback (most recent call last):
File "/usr/bin/chirpw", line 21, in
from chirp.wxui import main
File "/home/mike/.local/lib/python3.10/site-packages/chirp/wxui/main.py", line 45, in
from chirp.wxui import bankedit
File "/home/mike/.local/lib/python3.10/site-packages/chirp/wxui/bankedit.py", line 24, in
from chirp.wxui import memedit
File "/home/mike/.local/lib/python3.10/site-packages/chirp/wxui/memedit.py", line 270, in
class ChirpChoiceColumn(ChirpMemoryColumn):
File "/home/mike/.local/lib/python3.10/site-packages/chirp/wxui/memedit.py", line 272, in ChirpChoiceColumn
_TITLE1 = _('Tuning Step')
NameError: name '
' is not defined

Actions #1

Updated by Dan Smith about 1 year ago

  • Status changed from New to Feedback

Mike, this is yet a third presentation of an issue. I'm not sure what is going on that is causing you to have such varied results. However, your log looks to indicate that you've got a combination of old and new chirp on the same system. "chirpw" is only from legacy chirp, and there's really no reasonable install path that would get any part of chirp-next installed in /usr/bin. It's also running from /usr/bin but importing modules from your ~/local directory. Further, the actual error message (in this report) indicates an error on a line of code that can't possibly be correct, which makes me think that you've got some stale pyc files somewhere.

So I think you need to work on cleaning up all the places you've got chirp installed on that system and then follow ChirpOnLinux to start fresh.

Actions #2

Updated by Mike Williams about 1 year ago

Thanks!
My understanding of linux is pretty much limited to operating the GUI,
Could the installation instructions be updated? It seems to me that pkunzip is a necessity, yet it is not mentioned. Further, Linux seems to distribute files across the drive in ways that I don't understand. Do all chirp files have 'chirp' in there name? Where may I expect to find them?
Is it safe for me to delete all PYC files in the system?

Actions #3

Updated by Tony Fuller about 1 year ago

Hi Mike,

You shouldn't need pkunzip this day in age. Don't delete any the pyc files on your system! The ChirpOnLinux page is up to date.
Your log indicates you are on Linux Mint 21 which is a variant on Debian/Ubuntu. CHIRP-next works great on all of these operating systems. Best bet is to start with a fresh operating system install if you can. It's hard to say exactly where things have gone wrong in your existing installation.

Step 1 will be exactly as shown in the ChirpOnLinux page:
sudo apt install git python3-wxgtk4.0 python3-serial python3-six python3-future python3-requests python3-pip

For step 2 you can skip the download step and just run
pip install https://trac.chirp.danplanet.com/chirp_next/next-20230510/chirp-20230510-py3-none-any.whl

Then step 3 is the same as seen in the wiki
~/.local/bin/chirp

Tony

Actions #4

Updated by Mike Williams about 1 year ago

Huge thanks to Tony. That went well. Here is the new debug log:

[2023-05-09 18:50:56,972] chirp.logger - DEBUG: CHIRP next-20230427 on Linux - Linux Mint 21 Vanessa (Python 3.10.6)
Traceback (most recent call last):
File "/usr/bin/chirpw", line 21, in
from chirp.wxui import main
File "/home/mike/.local/lib/python3.10/site-packages/chirp/wxui/main.py", line 45, in
from chirp.wxui import bankedit
File "/home/mike/.local/lib/python3.10/site-packages/chirp/wxui/bankedit.py", line 24, in
from chirp.wxui import memedit
File "/home/mike/.local/lib/python3.10/site-packages/chirp/wxui/memedit.py", line 270, in
class ChirpChoiceColumn(ChirpMemoryColumn):
File "/home/mike/.local/lib/python3.10/site-packages/chirp/wxui/memedit.py", line 272, in ChirpChoiceColumn
_TITLE1 = _('Tuning Step')
NameError: name '
' is not defined
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 153, in apport_excepthook
with os.fdopen(os.open(pr_filename,
FileNotFoundError: [Errno 2] No such file or directory: '/var/crash/_usr_bin_chirpw.1000.crash'

Original exception was:
Traceback (most recent call last):
File "/usr/bin/chirpw", line 21, in
from chirp.wxui import main
File "/home/mike/.local/lib/python3.10/site-packages/chirp/wxui/main.py", line 45, in
from chirp.wxui import bankedit
File "/home/mike/.local/lib/python3.10/site-packages/chirp/wxui/bankedit.py", line 24, in
from chirp.wxui import memedit
File "/home/mike/.local/lib/python3.10/site-packages/chirp/wxui/memedit.py", line 270, in
class ChirpChoiceColumn(ChirpMemoryColumn):
File "/home/mike/.local/lib/python3.10/site-packages/chirp/wxui/memedit.py", line 272, in ChirpChoiceColumn
_TITLE1 = _('Tuning Step')
NameError: name '
' is not defined

Actions #5

Updated by Tony Fuller about 1 year ago

Hey Mike,

I should have taken note of your first post where you already had CHIRP-next installed, so the pip command in step 2 did nothing.

Can you run pip again but in upgrade mode?

pip install --upgrade https://trac.chirp.danplanet.com/chirp_next/next-20230510/chirp-20230510-py3-none-any.whl

I'm not understanding how _TITLE1 = _('Tuning Step') could produce the error NameError: name '' is not defined unless somehow the underscore function was mapped to an empty string somewhere.

Does this happen with any other radios you own? (Assuming you have another radio you can read...)

Tony

Actions #6

Updated by Mike Williams about 1 year ago

WOW this is fascinating!
I am now running the correct version!
Sadly, it does not work.
Here are the results of reading Puxing which has never worked in -next, and the results of reading a UV-5r whch has always worked before.

Thanks for looking into this Tony!

$ pip install --upgrade https://trac.chirp.danplanet.com/chirp_next/next-20230510/chirp-20230510-py3-none-any.whl
Defaulting to user installation because normal site-packages is not writeable
Collecting chirp==20230510
Using cached https://trac.chirp.danplanet.com/chirp_next/next-20230510/chirp-20230510-py3-none-any.whl (1.4 MB)
Requirement already satisfied: pyserial in /usr/lib/python3/dist-packages (from chirp==20230510) (3.5)
Requirement already satisfied: future in /usr/lib/python3/dist-packages (from chirp==20230510) (0.18.2)
Requirement already satisfied: six in /usr/lib/python3/dist-packages (from chirp==20230510) (1.16.0)
Requirement already satisfied: yattag in ./.local/lib/python3.10/site-packages (from chirp==20230510) (1.15.1)

Requirement already satisfied: requests in /usr/lib/python3/dist-packages (from chirp==20230510) (2.25.1)

I attempted to read my UV5R:

[2023-05-12 09:23:53,753] chirp.logger - DEBUG: CHIRP next-20230510 on Linux - Linux Mint 21 Vanessa (Python 3.10.6)
[2023-05-12 09:23:54,007] chirp.wxui - DEBUG: Using locale: en_US (60)
[2023-05-12 09:23:54,091] chirp.wxui - DEBUG: Translation loaded=True for CHIRP: en_US (el,es,uk_UA,nl,ru,pl,zh_CN,de,hu,pt_BR,fr,tr_TR,en_US,it) from /home/mike/.local/lib/python3.10/site-packages/chirp/locale
[2023-05-12 09:23:54,095] chirp.wxui - DEBUG: Translation loaded=False for wxstd: en_US (el,es,id,af,sv,nl,tr,ru,pl,eu,ta,zh_CN,ca@valencia,de,hi,gl_ES,lt,ko_KR,uk,hu,pt_BR,fr,cs,fi,nb,da,vi,lv,pt,ca,sq,ja,ar,an,it,ne,ro,sl,ms,sk,zh_TW)
[2023-05-12 09:23:54,246] main - INFO: Python/3.10.6 // Linux/Linux-5.15.0-71-generic-x86_64-with-glibc2.35 // CHIRP/next-20230510 // wx/4.0.7 gtk3 (phoenix) wxWidgets 3.0.5
[2023-05-12 09:23:54,570] chirp.wxui.main - INFO: Server reports next-20230510 is latest
[2023-05-12 09:24:10,419] chirp.wxui.clone - DEBUG: Selected
[2023-05-12 09:24:10,422] chirp.wxui.clone - DEBUG: Showing experimental prompt
[2023-05-12 09:24:12,794] chirp.wxui.clone - DEBUG: Setting flag for prompt experimental
[2023-05-12 09:24:21,293] chirp.wxui.clone - DEBUG: Using port '/dev/ttyS0'
[2023-05-12 09:24:21,293] chirp.wxui.clone - DEBUG: Selected
[2023-05-12 09:24:21,296] chirp.wxui.clone - DEBUG: Showing pre_download prompt
[2023-05-12 09:24:23,058] chirp.wxui.clone - DEBUG: Setting flag for prompt pre_download
[2023-05-12 09:24:23,059] chirp.wxui.clone - DEBUG: Serial opened: Serial(port='/dev/ttyS0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=0.25, xonxoff=False, rtscts=False, dsrdtr=False) (rts=True dtr=True)
[2023-05-12 09:24:23,059] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 20 12 07 25 P.....%.

[2023-05-12 09:24:24,130] chirp.drivers.uv5r - ERROR: uv5r._ident_radio: Radio did not respond
[2023-05-12 09:24:26,132] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 01 25 98 4d P...%.M.

[2023-05-12 09:24:27,204] chirp.drivers.uv5r - ERROR: uv5r._ident_radio: Radio did not respond
[2023-05-12 09:24:29,206] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 0d 0c 20 16 03 28 P.....(.

[2023-05-12 09:24:30,278] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 20 12 06 25 P.....%.

[2023-05-12 09:24:31,350] chirp.wxui.clone - ERROR: Failed to clone: Radio did not respond
Traceback (most recent call last):
File "/home/mike/.local/lib/python3.10/site-packages/chirp/wxui/clone.py", line 66, in run
self._fn()
File "/home/mike/.local/lib/python3.10/site-packages/chirp/drivers/uv5r.py", line 845, in sync_in
self._mmap = _do_download(self)
File "/home/mike/.local/lib/python3.10/site-packages/chirp/drivers/uv5r.py", line 554, in _do_download
data = _ident_radio(radio)
File "/home/mike/.local/lib/python3.10/site-packages/chirp/drivers/uv5r.py", line 549, in _ident_radio
raise error
File "/home/mike/.local/lib/python3.10/site-packages/chirp/drivers/uv5r.py", line 526, in _ident_radio
data = _do_ident(radio, magic)
File "/home/mike/.local/lib/python3.10/site-packages/chirp/drivers/uv5r.py", line 421, in _do_ident
raise errors.RadioError("Radio did not respond")
chirp.errors.RadioError: Radio did not respond
[2023-05-12 09:24:36,756] chirp.wxui.clone - DEBUG: Using port '/dev/ttyS0'
[2023-05-12 09:24:36,756] chirp.wxui.clone - DEBUG: Selected
[2023-05-12 09:24:36,758] chirp.wxui.clone - DEBUG: Showing pre_download prompt
[2023-05-12 09:24:38,718] chirp.wxui.clone - DEBUG: Setting flag for prompt pre_download
[2023-05-12 09:24:38,718] chirp.wxui.clone - DEBUG: Serial opened: Serial(port='/dev/ttyS0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=0.25, xonxoff=False, rtscts=False, dsrdtr=False) (rts=True dtr=True)
[2023-05-12 09:24:38,718] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 20 12 07 25 P.....%.

[2023-05-12 09:24:39,790] chirp.drivers.uv5r - ERROR: uv5r._ident_radio: Radio did not respond
[2023-05-12 09:24:41,792] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 01 25 98 4d P...%.M.

[2023-05-12 09:24:42,864] chirp.drivers.uv5r - ERROR: uv5r._ident_radio: Radio did not respond
[2023-05-12 09:24:44,867] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 0d 0c 20 16 03 28 P.....(.

[2023-05-12 09:24:45,939] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 20 12 06 25 P.....%.

[2023-05-12 09:24:47,011] chirp.wxui.clone - ERROR: Failed to clone: Radio did not respond
Traceback (most recent call last):
File "/home/mike/.local/lib/python3.10/site-packages/chirp/wxui/clone.py", line 66, in run
self._fn()
File "/home/mike/.local/lib/python3.10/site-packages/chirp/drivers/uv5r.py", line 845, in sync_in
self._mmap = _do_download(self)
File "/home/mike/.local/lib/python3.10/site-packages/chirp/drivers/uv5r.py", line 554, in _do_download
data = _ident_radio(radio)
File "/home/mike/.local/lib/python3.10/site-packages/chirp/drivers/uv5r.py", line 549, in _ident_radio
raise error
File "/home/mike/.local/lib/python3.10/site-packages/chirp/drivers/uv5r.py", line 526, in _ident_radio
data = _do_ident(radio, magic)
File "/home/mike/.local/lib/python3.10/site-packages/chirp/drivers/uv5r.py", line 421, in _do_ident
raise errors.RadioError("Radio did not respond")
chirp.errors.RadioError: Radio did not respond
[2023-05-12 09:24:52,012] chirp.wxui.clone - WARNING: Stopping clone thread

Actions #7

Updated by Tony Fuller about 1 year ago

DEBUG: Serial opened: Serial(port='/dev/ttyS0',

Could you tell us a little about your serial port? When I see ttyS0 I usually think that's going to be a "real" hardware-backed serial port (the 9-pin ones on the backs of computers).

You're not using a USB to serial adapter are you?

Tony

Actions #8

Updated by Mike Williams about 1 year ago

I have no extra hardware installed.
It is just a run of the mill USB. And again, it used to program UV-5R's.

Actions #9

Updated by Jim Unroe about 1 year ago

Mike Williams wrote in #note-8:

I have no extra hardware installed.
It is just a run of the mill USB. And again, it used to program UV-5R's.

What Tony is getting at is that you may be selecting the wrong port. If you are using a USB style programming cable that contains as USB-to-Serial chip, then you should scroll all the way down the list of available ports until you see /dev/ttyUSB0 and select it.

Jim KC9HI

Actions #10

Updated by Mike Williams about 1 year ago

OMG! That make a difference Jim!
I was able to read my UV5r!
Feeling lucky so I tried to read my Puxing. It worked!
Thank you so much folks!
Wow I am so happy!

Actions #11

Updated by Dan Smith about 1 year ago

  • Status changed from Feedback to Not a bug
Actions

Also available in: Atom PDF