[chirp_users] Puxing PX-2R "not responding"

[Dave B]

Hi Christoph.

If you look in the bug report page:-

https://chirp.danplanet.com/issues/6389 that I instigated a while ago...

(Probably needs a login, begin at https://chirp.danplanet.com/login )

It seems from what one of the dev's has said:-

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.

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.

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.)

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.

73 All.

Dave G0WBX.


On 11/01/2021 20:00, chirp_users-request at intrepid.danplanet.com wrote:
> Date: Mon, 11 Jan 2021 11:56:18 +0100
> From:christoph at grothesque.org
> Subject: [chirp_users] Puxing PX-2R "not responding"
> To:chirp_users at intrepid.danplanet.com
> Message-ID: <878s8z214d.fsf at 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

-- 
Created on and sent from a Unix like PC running and using free and open source software:

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20210112/b732072b/attachment.html