Hello
I just brought a Retevis RA89 with the 2 Pin Cable from retevis too
I use Arch Linux / Debian. I installed chirp without issue
But now when I connect my radio to my computer I am unable to get it work
I contact the seller who tell me to use windows …
I've got this in the dmesg log
[sam. 17 août 11:22:17 2024] usb 1-9.4: new full-speed USB device number 11 using xhci_hcd [sam. 17 août 11:22:17 2024] usb 1-9.4: device descriptor read/64, error -32 [sam. 17 août 11:22:17 2024] usb 1-9.4: device descriptor read/64, error -32 [sam. 17 août 11:22:17 2024] usb 1-9.4: new full-speed USB device number 12 using xhci_hcd [sam. 17 août 11:22:17 2024] usb 1-9.4: device descriptor read/64, error -32 [sam. 17 août 11:22:17 2024] usb 1-9.4: device descriptor read/64, error -32 [sam. 17 août 11:22:17 2024] usb 1-9-port4: attempt power cycle [sam. 17 août 11:22:18 2024] usb 1-9.4: new full-speed USB device number 13 using xhci_hcd [sam. 17 août 11:22:18 2024] usb 1-9.4: Device not responding to setup address. [sam. 17 août 11:22:18 2024] usb 1-9.4: Device not responding to setup address. [sam. 17 août 11:22:18 2024] usb 1-9.4: device not accepting address 13, error -71 [sam. 17 août 11:22:18 2024] usb 1-9.4: new full-speed USB device number 14 using xhci_hcd [sam. 17 août 11:22:18 2024] usb 1-9.4: Device not responding to setup address. [sam. 17 août 11:22:19 2024] usb 1-9.4: Device not responding to setup address. [sam. 17 août 11:22:19 2024] usb 1-9.4: device not accepting address 14, error -71 [sam. 17 août 11:22:19 2024] usb 1-9-port4: unable to enumerate USB device
Have you any idea how can I get the communication between my computer and the radio is possible with Linux ?
I find this topic https://vk2.net/articles/Retevis-RT3S-on-a-Mac-or-Linux-PC
I am not reassure …
I also checked https://chirpmyradio.com/projects/chirp/wiki/CableGuide and i think i need a specific cable but not sure to understand well ?
Regards
[sam. 17 août 11:22:17 2024] usb 1-9.4: new full-speed USB device number 11 using xhci_hcd [sam. 17 août 11:22:17 2024] usb 1-9.4: device descriptor read/64, error -32 [sam. 17 août 11:22:17 2024] usb 1-9.4: device descriptor read/64, error -32 [sam. 17 août 11:22:17 2024] usb 1-9.4: new full-speed USB device number 12 using xhci_hcd [sam. 17 août 11:22:17 2024] usb 1-9.4: device descriptor read/64, error -32 [sam. 17 août 11:22:17 2024] usb 1-9.4: device descriptor read/64, error -32 [sam. 17 août 11:22:17 2024] usb 1-9-port4: attempt power cycle [sam. 17 août 11:22:18 2024] usb 1-9.4: new full-speed USB device number 13 using xhci_hcd [sam. 17 août 11:22:18 2024] usb 1-9.4: Device not responding to setup address. [sam. 17 août 11:22:18 2024] usb 1-9.4: Device not responding to setup address. [sam. 17 août 11:22:18 2024] usb 1-9.4: device not accepting address 13, error -71 [sam. 17 août 11:22:18 2024] usb 1-9.4: new full-speed USB device number 14 using xhci_hcd [sam. 17 août 11:22:18 2024] usb 1-9.4: Device not responding to setup address. [sam. 17 août 11:22:19 2024] usb 1-9.4: Device not responding to setup address. [sam. 17 août 11:22:19 2024] usb 1-9.4: device not accepting address 14, error -71 [sam. 17 août 11:22:19 2024] usb 1-9-port4: unable to enumerate USB device
Have you any idea how can I get the communication between my computer and the radio is possible with Linux ?
This means the drivers in linux are not recognizing the chip in your cable. That makes this not a CHIRP problem.
Many of the chinese manufacturers (yes even the radio OEMs) use counterfeit or otherwise undesirable chipsets in their cables, and are a constant challenge.
I also checked https://chirpmyradio.com/projects/chirp/wiki/CableGuide and i think i need a specific cable but not sure to understand well
Regardless of the OS, you want an FTDI-based cable from BlueMax49ers and all your problems will go away. This cable will work for almost all the chinese radios out there that use the kenwood style plug:
https://bluemax49ers.com/product-explorer/retevis-ra89-ftdi-programming-cabl...
--Dan
I've had issues using a Retevis-branded programming cable, too, although in my case, the problem was on Windows! It's always been a bit of a challenge to find a Prolific USB/Serial driver version that actually works with a given Prolific-based programming cable, but under Windows 11, it pretty much seems none of the drivers work. I would have expected you to have had more success under Linux than Windows!
Regardless, using a FTDI-based cable should be much more reliable. I've had no issues with mine. I would imagine that using BlueMax49ers from France won't be particularly easy or cheap, but you should be able to find a few FTDI programming cables on Amazon (I got mine from Amazon UK). Yes, they are approaching twice the price of the Prolific cables, but they do work....which makes them a lot more valuable in my opinion. The cable I bought had the description "DTech USB Programming Cable FTDI Chip for BaoFeng UV-5R BF-F8HP UV-82HP UV-82 BF-888S H777 TH Series K1 Kenwood 2 Pin Connector Two Way Ham Radio Cord" - just ensure it states that it uses the FTDI USB to serial converter chip.
Good luck.
Adam
On Sat, 17 Aug 2024 at 15:39, Dan Smith via Users < users@lists.chirpmyradio.com> wrote:
[sam. 17 août 11:22:17 2024] usb 1-9.4: new full-speed USB device number
11 using xhci_hcd
[sam. 17 août 11:22:17 2024] usb 1-9.4: device descriptor read/64, error
-32
[sam. 17 août 11:22:17 2024] usb 1-9.4: device descriptor read/64, error
-32
[sam. 17 août 11:22:17 2024] usb 1-9.4: new full-speed USB device number
12 using xhci_hcd
[sam. 17 août 11:22:17 2024] usb 1-9.4: device descriptor read/64, error
-32
[sam. 17 août 11:22:17 2024] usb 1-9.4: device descriptor read/64, error
-32
[sam. 17 août 11:22:17 2024] usb 1-9-port4: attempt power cycle [sam. 17 août 11:22:18 2024] usb 1-9.4: new full-speed USB device number
13 using xhci_hcd
[sam. 17 août 11:22:18 2024] usb 1-9.4: Device not responding to setup
address.
[sam. 17 août 11:22:18 2024] usb 1-9.4: Device not responding to setup
address.
[sam. 17 août 11:22:18 2024] usb 1-9.4: device not accepting address 13,
error -71
[sam. 17 août 11:22:18 2024] usb 1-9.4: new full-speed USB device number
14 using xhci_hcd
[sam. 17 août 11:22:18 2024] usb 1-9.4: Device not responding to setup
address.
[sam. 17 août 11:22:19 2024] usb 1-9.4: Device not responding to setup
address.
[sam. 17 août 11:22:19 2024] usb 1-9.4: device not accepting address 14,
error -71
[sam. 17 août 11:22:19 2024] usb 1-9-port4: unable to enumerate USB
device
Have you any idea how can I get the communication between my computer
and the radio is possible with Linux ?
This means the drivers in linux are not recognizing the chip in your cable. That makes this not a CHIRP problem.
Many of the chinese manufacturers (yes even the radio OEMs) use counterfeit or otherwise undesirable chipsets in their cables, and are a constant challenge.
I also checked https://chirpmyradio.com/projects/chirp/wiki/CableGuide
and i think i need a specific cable but not sure to understand well
Regardless of the OS, you want an FTDI-based cable from BlueMax49ers and all your problems will go away. This cable will work for almost all the chinese radios out there that use the kenwood style plug:
https://bluemax49ers.com/product-explorer/retevis-ra89-ftdi-programming-cabl...
--Dan _______________________________________________ Users mailing list users@lists.chirpmyradio.com https://lists.chirpmyradio.com/postorius/lists/users.lists.chirpmyradio.com To unsubscribe, send an email to users-leave@lists.chirpmyradio.com To report this email as off-topic, please email users-owner@lists.chirpmyradio.com List archives: https://lists.chirpmyradio.com/hyperkitty/list/users@lists.chirpmyradio.com/
On Sun, Aug 18, 2024 at 7:50 PM Adam Parsons via Users users@lists.chirpmyradio.com wrote:
I've had issues using a Retevis-branded programming cable, too, although in my case, the problem was on Windows! It's always been a bit of a challenge to find a Prolific USB/Serial driver version that actually works with a given Prolific-based programming cable, but under Windows 11, it pretty much seems none of the drivers work. I would have expected you to have had more success under Linux than Windows!
Regardless, using a FTDI-based cable should be much more reliable. I've had no issues with mine. I would imagine that using BlueMax49ers from France won't be particularly easy or cheap, but you should be able to find a few FTDI programming cables on Amazon (I got mine from Amazon UK). Yes, they are approaching twice the price of the Prolific cables, but they do work....which makes them a lot more valuable in my opinion. The cable I bought had the description "DTech USB Programming Cable FTDI Chip for BaoFeng UV-5R BF-F8HP UV-82HP UV-82 BF-888S H777 TH Series K1 Kenwood 2 Pin Connector Two Way Ham Radio Cord" - just ensure it states that it uses the FTDI USB to serial converter chip.
Good luck.
Adam
In order to use a Prolific chip based programming cable with Windows, the chip in the cable must be the latest PL2303GS version to be used with the latest driver. For the older (considered end-of-life by Prolific) PL2303HX and PL2303TA chip, you must use the v3.2.0.0 driver (Windows 7, 8, 10 and 11) or v2.0.2.1 (Windows XP). Links to the needed drivers are available on the Miklor website.
https://www.miklor.com/COM/UV_Drivers.php
Jim KC9HI
Yeah, but where can you buy a cable with a guaranteed PL2303GS chipset? Chances are, you'll get an older one (or clone thereof) and be stuffed. And to be honest, it's pretty poor that the latest Prolific drivers don't recognise the older chipset and do their thing the way the older driver versions managed to. It's all a bit of a mess, and the only way to really avoid the problem is to go FTDI - a company that seems to have got their act together. A shame, as several years ago, Prolific were the trusted name in USB to Serial converters. How times change.
Adam
On Mon, 19 Aug 2024 at 00:58, Jim Unroe via Users < users@lists.chirpmyradio.com> wrote:
On Sun, Aug 18, 2024 at 7:50 PM Adam Parsons via Users users@lists.chirpmyradio.com wrote:
I've had issues using a Retevis-branded programming cable, too, although
in
my case, the problem was on Windows! It's always been a bit of a
challenge
to find a Prolific USB/Serial driver version that actually works with a given Prolific-based programming cable, but under Windows 11, it pretty much seems none of the drivers work. I would have expected you to have
had
more success under Linux than Windows!
Regardless, using a FTDI-based cable should be much more reliable. I've
had
no issues with mine. I would imagine that using BlueMax49ers from France won't be particularly easy or cheap, but you should be able to find a few FTDI programming cables on Amazon (I got mine from Amazon UK). Yes, they are approaching twice the price of the Prolific cables, but they do work....which makes them a lot more valuable in my opinion. The cable I bought had the description "DTech USB Programming Cable FTDI Chip for BaoFeng UV-5R BF-F8HP UV-82HP UV-82 BF-888S H777 TH Series K1 Kenwood 2
Pin
Connector Two Way Ham Radio Cord" - just ensure it states that it uses
the
FTDI USB to serial converter chip.
Good luck.
Adam
In order to use a Prolific chip based programming cable with Windows, the chip in the cable must be the latest PL2303GS version to be used with the latest driver. For the older (considered end-of-life by Prolific) PL2303HX and PL2303TA chip, you must use the v3.2.0.0 driver (Windows 7, 8, 10 and 11) or v2.0.2.1 (Windows XP). Links to the needed drivers are available on the Miklor website.
https://www.miklor.com/COM/UV_Drivers.php
Jim KC9HI _______________________________________________ Users mailing list users@lists.chirpmyradio.com https://lists.chirpmyradio.com/postorius/lists/users.lists.chirpmyradio.com To unsubscribe, send an email to users-leave@lists.chirpmyradio.com To report this email as off-topic, please email users-owner@lists.chirpmyradio.com List archives: https://lists.chirpmyradio.com/hyperkitty/list/users@lists.chirpmyradio.com/
You don't. FTDI adaptors are available direct from the FTDI website and attach your own cable.
On 18/08/2024 20:22 EDT Adam Parsons via Users users@lists.chirpmyradio.com wrote:
Yeah, but where can you buy a cable with a guaranteed PL2303GS chipset? Chances are, you'll get an older one (or clone thereof) and be stuffed. And to be honest, it's pretty poor that the latest Prolific drivers don't recognise the older chipset and do their thing the way the older driver versions managed to. It's all a bit of a mess, and the only way to really avoid the problem is to go FTDI - a company that seems to have got their act together. A shame, as several years ago, Prolific were the trusted name in USB to Serial converters. How times change.
Adam
On Mon, 19 Aug 2024 at 00:58, Jim Unroe via Users < users@lists.chirpmyradio.com> wrote:
On Sun, Aug 18, 2024 at 7:50 PM Adam Parsons via Users users@lists.chirpmyradio.com wrote:
I've had issues using a Retevis-branded programming cable, too, although
in
my case, the problem was on Windows! It's always been a bit of a
challenge
to find a Prolific USB/Serial driver version that actually works with a given Prolific-based programming cable, but under Windows 11, it pretty much seems none of the drivers work. I would have expected you to have
had
more success under Linux than Windows!
Regardless, using a FTDI-based cable should be much more reliable. I've
had
no issues with mine. I would imagine that using BlueMax49ers from France won't be particularly easy or cheap, but you should be able to find a few FTDI programming cables on Amazon (I got mine from Amazon UK). Yes, they are approaching twice the price of the Prolific cables, but they do work....which makes them a lot more valuable in my opinion. The cable I bought had the description "DTech USB Programming Cable FTDI Chip for BaoFeng UV-5R BF-F8HP UV-82HP UV-82 BF-888S H777 TH Series K1 Kenwood 2
Pin
Connector Two Way Ham Radio Cord" - just ensure it states that it uses
the
FTDI USB to serial converter chip.
Good luck.
Adam
In order to use a Prolific chip based programming cable with Windows, the chip in the cable must be the latest PL2303GS version to be used with the latest driver. For the older (considered end-of-life by Prolific) PL2303HX and PL2303TA chip, you must use the v3.2.0.0 driver (Windows 7, 8, 10 and 11) or v2.0.2.1 (Windows XP). Links to the needed drivers are available on the Miklor website.
https://www.miklor.com/COM/UV_Drivers.php
Jim KC9HI _______________________________________________ Users mailing list users@lists.chirpmyradio.com https://lists.chirpmyradio.com/postorius/lists/users.lists.chirpmyradio.com To unsubscribe, send an email to users-leave@lists.chirpmyradio.com To report this email as off-topic, please email users-owner@lists.chirpmyradio.com List archives: https://lists.chirpmyradio.com/hyperkitty/list/users@lists.chirpmyradio.com/
Users mailing list users@lists.chirpmyradio.com https://lists.chirpmyradio.com/postorius/lists/users.lists.chirpmyradio.com To unsubscribe, send an email to users-leave@lists.chirpmyradio.com To report this email as off-topic, please email users-owner@lists.chirpmyradio.com List archives: https://lists.chirpmyradio.com/hyperkitty/list/users@lists.chirpmyradio.com/
Nigel A. Gunn, ///shoulders.outwards.resolutions tel +1-937-971-0366 Amateur Radio G8IFF W8IFF and GMRS WRBV701, e-mail nigel@ngunn.net www http://www.ngunn.net
On 18/8/24 00:37, Dan Smith via Users wrote:
I know my reply won't help Windows users.
I bought the cheapest cable that I could find on Ebay and it works without any problems at under Linux. The cable contains a Chinese chip, (I cannot remember what it's identified as) and from previous discussions I imagine that it wouldn't work under Windows.
participants (6)
-
Adam Parsons -
Anael Cyberjinh -
Dan Smith -
Jim Unroe -
Nigel A. Gunn G8IFF/W8IFF -
Phil