usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-2: New USB device found, idVendor=0403, idProduct=6001 usb 1-2: new full-speed USB device number 4 using xhci_hcd If there is enough detail here to work here. I fired up a copy of Debian Jessie live CD, and did a grep of dmesg for attached USB devices, and this is what I came up with. If there is a specific drop down, I should grab the details from let me know. Unable to get anything identifying the chip set though. It knows it is a FTDI manufactured device, and it knows it is a USB device. I couldn't find anything of any use via Windows device manager. I wasn't any more successful getting the client to talk to the radio. I tried the Linux Live CD version of the CHIRP product.
I wasn't sure who touch it before me, thought it might repair the communications problem no change. I also did a firmware reset on the radio. After rebooting in Safe Mode, I was able to remove the driver and get the OS back up. I tried using a Prolific driver that I had seen used with these cables before on some forums, but it crash Windows 7 Blue Screen. Hopefully the Debug log will have those details. Is there a way to get the firmware version off of the radio menu, without CHIRP? I read that sometimes, with newer sets, the firm ware code may be designed with a slightly different offset, that CHIRP can match up with.As noted in item 4, there was not software for the cable or any identifying marks on the cable. Driver date: 3/9/16, Driver version: 2.12.1.0, Digital Signer: Microsoft Windows Compatibility PublisherĦc. When Windows 7 detected the cable, it was identified as a serial cable on port COM3.Ħb. The FTDI cable was purchased from the Baofeng Radio webpage.There was no accompanying OEM software with either the radio or the FTDI cable.Selecting UV-82HP results in a error: "Radio refused to send block - 0x1f00"
Error I am getting when selecting the U-82 driver, is "Incorrect model selected".ġb. Responses to your questions, and some additional details.ġa. This is the first time working with you folks.
0 kommentar(er)
