<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Christoph.</p>
<p>If you look in the bug report page:-</p>
<p><a class="moz-txt-link-freetext" href="https://chirp.danplanet.com/issues/6389">https://chirp.danplanet.com/issues/6389</a> that I instigated a while
ago...<br>
</p>
<p>(Probably needs a login, begin at
<a class="moz-txt-link-freetext" href="https://chirp.danplanet.com/login">https://chirp.danplanet.com/login</a> )</p>
<p>It seems from what one of the dev's has said:-<br>
</p>
<p><font size="+1"><tt>Looks like the number of DCS codes reported
by the radio exceeds what Chirp expects or can handle. Guess
we have to look into this.</tt></font></p>
<p>That was 8 months ago, and as I was the only one reporting a
problem, I guess it's a low priority. If you could login and add
your voice to the report, maybe, something might happen.</p>
<p>But, I suspect most of the dev's are working to get CHIRP working
on Python3.x rather than fixing low profile bugs like this. (NOT
a flame, just how it goes, and I understand why that is hopefully
a priority.)</p>
<p>I can do a little Python programming, but CHIRP is a huge
codebase, and trying to understand one model of radio's back end,
in isolation of the rest, is nigh on impossible for me. Else I'd
have a go, but from Bernhard's comment, the problem could be
deeper within CHIRP, rather than the radio's driver/backend code.<br>
</p>
<p>73 All.</p>
<p>Dave G0WBX.</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 11/01/2021 20:00,
<a class="moz-txt-link-abbreviated" href="mailto:chirp_users-request@intrepid.danplanet.com">chirp_users-request@intrepid.danplanet.com</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:mailman.1.1610395202.20765.chirp_users@intrepid.danplanet.com">
<pre class="moz-quote-pre" wrap="">Date: Mon, 11 Jan 2021 11:56:18 +0100
From: <a class="moz-txt-link-abbreviated" href="mailto:christoph@grothesque.org" moz-do-not-send="true">christoph@grothesque.org</a>
Subject: [chirp_users] Puxing PX-2R "not responding"
To: <a class="moz-txt-link-abbreviated" href="mailto:chirp_users@intrepid.danplanet.com" moz-do-not-send="true">chirp_users@intrepid.danplanet.com</a>
Message-ID: <878s8z214d.fsf@drac>
Content-Type: text/plain; charset=utf-8
Hello,
I?m trying to download the config from a Puxing PX-2R using Chirp
1:20190104-1 on Debian stable with the result that the "Radio is not
responding".
I searched the available information (wiki, bug reports, list archive)
without finding a solution. Maybe someone here has a suggestion?
The cable I use is shown by lsusb as
Bus 002 Device 007: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
When I connect the radio to the computer with this cable and switch it
on, an orange LED lights above the active display. Since the radio does
not react to key presses when connected in this way it seems to detect
the connection. (When disconnected it reacts normally.)
In chirpw, I select "Download from Radio" and
Port: /dev/ttyUSB0 (the only one, read/write rights are OK)
Vendor: Puxing
Model: PX-2R
Then I press "OK" and an error dialog appears together with the
following message in the terminal:
ERROR: -- Exception: --
ERROR: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/chirp/ui/clone.py", line 256, in run
self.__radio.sync_in()
File "/usr/lib/python2.7/dist-packages/chirp/drivers/puxing.py", line 441, in sync_in
self._mmap = puxing_2r_download(self)
File "/usr/lib/python2.7/dist-packages/chirp/drivers/puxing.py", line 374, in puxing_2r_download
raise errors.RadioError("Failed to communicate with radio: %s" % e)
RadioError: Failed to communicate with radio: Radio is not responding
ERROR: ----------------
ERROR: Clone failed: Failed to communicate with radio: Radio is not responding
ERROR: --- Exception Dialog: Failed to communicate with radio: Radio is not responding ---
ERROR: None
ERROR: ----------------------------
I can reproduce the above with both PX-2R devices that I have access to.
I read that PL-2303 cables normally do work on Linux. Does anyone have
an idea what the problem could be?
Thanks
Christoph</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Created on and sent from a Unix like PC running and using free and open source software:
</pre>
</body>
</html>