[chirp_users] More baofeng woes (UV-B5)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hey, all.
I picked up a UV-B5 and am unable to program it with chirp. The console output is as follows:
%chirpw
ERROR: -- Exception: -- ERROR: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/chirp/ui/clone.py", line 238, in run self.__radio.sync_in() File "/usr/lib64/python2.7/site-packages/chirp/drivers/uvb5.py", line 315, in sync_in self._mmap = do_download(self) File "/usr/lib64/python2.7/site-packages/chirp/drivers/uvb5.py", line 202, in do_download do_ident(radio) File "/usr/lib64/python2.7/site-packages/chirp/drivers/uvb5.py", line 181, in do_ident raise errors.RadioError("Radio did not ack programming mode") RadioError: Radio did not ack programming mode
ERROR: ---------------- ERROR: Clone failed: Radio did not ack programming mode ERROR: --- Exception Dialog: Radio did not ack programming mode --- ERROR: None
ERROR: ----------------------------
I've tried two different cables to no avail, and yes I had them seated. Not a windows environment so I don't think the IP hindrance is the issue. The radio's xmit light comes on but it seams to not be able to communicate with chirp.
How can I provide more information to be helpful?
Thanks in advance.
Be well, Scott
Also, props to all the dev's and users whom have helped make chirp what it is!
What driver did you use for the cables? Try the ones here: http://www.miklor.com/COM/UV_Drivers.php
-Daniel
On Wed, May 27, 2015 at 12:22 PM, Scott Martin scott@kc9qen.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hey, all.
I picked up a UV-B5 and am unable to program it with chirp. The console output is as follows:
%chirpw
ERROR: -- Exception: -- ERROR: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/chirp/ui/clone.py", line 238, in run self.__radio.sync_in() File "/usr/lib64/python2.7/site-packages/chirp/drivers/uvb5.py", line 315, in sync_in self._mmap = do_download(self) File "/usr/lib64/python2.7/site-packages/chirp/drivers/uvb5.py", line 202, in do_download do_ident(radio) File "/usr/lib64/python2.7/site-packages/chirp/drivers/uvb5.py", line 181, in do_ident raise errors.RadioError("Radio did not ack programming mode") RadioError: Radio did not ack programming mode
ERROR: ---------------- ERROR: Clone failed: Radio did not ack programming mode ERROR: --- Exception Dialog: Radio did not ack programming mode --- ERROR: None
ERROR: ----------------------------
I've tried two different cables to no avail, and yes I had them seated. Not a windows environment so I don't think the IP hindrance is the issue. The radio's xmit light comes on but it seams to not be able to communicate with chirp.
How can I provide more information to be helpful?
Thanks in advance.
Be well, Scott
Also, props to all the dev's and users whom have helped make chirp what it is! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQEcBAEBAgAGBQJVZhmGAAoJEMHo5RVayTw1mrYH/3GvTPwK/+OuOQZCZWN+6zNV bMvdA6um4TY48BvWH/bmcx0SEb2kfl5aiQSZy8ahlwNbpnxHSXMFaTzEb8QyNvpD 6tbWq11Znz9Dd4WT0/8HA63pi0GwF3Wk+1YYtsg19ro2qXveszDBZhsyPFRGox8b mM0JLs6yBfjOp/MBLhOq6xTzq+Lw1KPVAHZ3Xbg+PZ5oeZoBAoSvGF6HS7HHKRU6 nyGOybUyU8hk8bGgKtUrLwqEDejnjDtS5z+pDkHlAg3ggnL8m2Eu2nv6XBs8vtj7 08YvoFVE2RZe9DUebDoJB+IhBauDsAj/d6EIw6xf50pe5T58wJIS1gxqeMN0bHE= =8dnB -----END PGP SIGNATURE----- _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 05/27/2015 02:49 PM, Daniel Lichterman wrote:
What driver did you use for the cables? Try the ones here: http://www.miklor.com/COM/UV_Drivers.php
-Daniel
I'm using the prolific drivers in the Linux kernel. The serial device info is below:
Bus 002 Device 027: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port [1576/2752] Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x067b Prolific Technology, Inc. idProduct 0x2303 PL2303 Serial Port bcdDevice 3.00 iManufacturer 1 Prolific Technology Inc. iProduct 2 USB-Serial Controller iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x000a 1x 10 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 can't get device qualifier: Resource temporarily unavailable can't get debug descriptor: Resource temporarily unavailable Device Status: 0x0000 (Bus Powered)
Like I said, the radio's xmit light comes on for a second, but then chirp throws the error I posted in my previous message. I don't think it's a hub power issue as I've tried it in all the ports available, and it isn't throwing errors in dmesg. I'm due for a kernel upgrade but haven't dedicated time to that, yet...
Be well, Scott
http://mailformat.dan.info/quoting/top-posting.html
On Wed, May 27, 2015 at 3:22 PM, Scott Martin scott@kc9qen.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hey, all.
I picked up a UV-B5 and am unable to program it with chirp. The console output is as follows:
%chirpw
ERROR: -- Exception: -- ERROR: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/chirp/ui/clone.py", line 238, in run self.__radio.sync_in() File "/usr/lib64/python2.7/site-packages/chirp/drivers/uvb5.py", line 315, in sync_in self._mmap = do_download(self) File "/usr/lib64/python2.7/site-packages/chirp/drivers/uvb5.py", line 202, in do_download do_ident(radio) File "/usr/lib64/python2.7/site-packages/chirp/drivers/uvb5.py", line 181, in do_ident raise errors.RadioError("Radio did not ack programming mode") RadioError: Radio did not ack programming mode
ERROR: ---------------- ERROR: Clone failed: Radio did not ack programming mode ERROR: --- Exception Dialog: Radio did not ack programming mode --- ERROR: None
ERROR: ----------------------------
I've tried two different cables to no avail, and yes I had them seated. Not a windows environment so I don't think the IP hindrance is the issue. The radio's xmit light comes on but it seams to not be able to communicate with chirp.
How can I provide more information to be helpful?
Thanks in advance.
Be well, Scott
Also, props to all the dev's and users whom have helped make chirp what it is!
Scott,
Leave the programming cable unplugged from the radio and attempt a download. You will get the same error. This is most likely a cable problem or cable/radio connection problem.
Jim KC9HI
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 05/27/2015 05:43 PM, Jim Unroe wrote:
On Wed, May 27, 2015 at 3:22 PM, Scott Martin scott@kc9qen.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hey, all.
I picked up a UV-B5 and am unable to program it with chirp. The console output is as follows:
%chirpw
ERROR: -- Exception: -- ERROR: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/chirp/ui/clone.py", line 238, in run self.__radio.sync_in() File "/usr/lib64/python2.7/site-packages/chirp/drivers/uvb5.py", line 315, in sync_in self._mmap = do_download(self) File "/usr/lib64/python2.7/site-packages/chirp/drivers/uvb5.py", line 202, in do_download do_ident(radio) File "/usr/lib64/python2.7/site-packages/chirp/drivers/uvb5.py", line 181, in do_ident raise errors.RadioError("Radio did not ack programming mode") RadioError: Radio did not ack programming mode
ERROR: ---------------- ERROR: Clone failed: Radio did not ack programming mode ERROR: --- Exception Dialog: Radio did not ack programming mode --- ERROR: None
ERROR: ----------------------------
I've tried two different cables to no avail, and yes I had them seated. Not a windows environment so I don't think the IP hindrance is the issue. The radio's xmit light comes on but it seams to not be able to communicate with chirp.
How can I provide more information to be helpful?
Thanks in advance.
Be well, Scott
Also, props to all the dev's and users whom have helped make chirp what it is!
Scott,
Leave the programming cable unplugged from the radio and attempt a download. You will get the same error. This is most likely a cable problem or cable/radio connection problem.
Jim KC9HI
Thats actually what I was afraid of. I sourced two cables to try and rule it out. I was hoping it was a frimware issue... For the price I'm sure there are more than a few lemons out there.
Thanks for everyones time.
Be well, Scott
participants (3)
-
Daniel Lichterman
-
Jim Unroe
-
Scott Martin