Bug #8039

Radioddity QB25 not going into clone mode when downloading from the radio

Added by Greg T 4 months ago. Updated 16 days ago.

Status:Feedback Start date:07/03/2020
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:Windows
Model affected:Radioddity QB25

Description

This is similar to the Bug #5983 which has a similar issue on a Mac. I'm currently using CHIRP daily-20200622 with three different cables. One official FTDI cable with the D2xx driver installed. The second is the cable provided from Radioddity with the QB25 which was just purchased in June 2020. I have also tried their specific drivers for the Radioddity cable with no success. I also have a no-name cable that uses the FTDI chipset to program my GreCom scanner without issue.

Everytime I use the "Download From Radio" or the "Upload to Radio" feature, the message will appear after the progress bar show some promise and moves along, but returns with a possibility of two messages depending on the driver used.

Message Under the FTDI driver and an of the cables:
"Radio Identification Failed"

Message Under the Radioddity driver and an of the cables:
"Radio did not go into clone mode"

I'm currently using the FTDI driver version 2.12.28.0, but I have tried the Radioddity driver 1.02

I would be more than willing to try and build version that you may want to try out to see if it will fix the issue.

Radio Identification Fialed.JPG (21.8 kB) Greg T, 07/03/2020 05:34 pm

Com Port 4 Properties.JPG (47.1 kB) Greg T, 07/03/2020 05:34 pm

FDTI Driver & Cable - Radio 1 debug.log (27 kB) Greg T, 07/13/2020 09:19 pm

FDTI Driver & Cable - Radio 2 debug.log (27 kB) Greg T, 07/13/2020 09:19 pm

FDTI Driver & Radioddity Cable - Radio 1 debug.log (27 kB) Greg T, 07/13/2020 09:19 pm

FDTI Driver & Radioddity Cable - Radio 2 debug.log (27 kB) Greg T, 07/13/2020 09:19 pm

Radioddity Driver & Cable - Radio 1 debug.log (26.6 kB) Greg T, 07/13/2020 09:19 pm

Radioddity Driver & Cable - Radio 2 debug.log (27 kB) Greg T, 07/13/2020 09:19 pm

Radioddity Driver & FDTI Cable - Radio 1 debug.log (27 kB) Greg T, 07/13/2020 09:19 pm

Radioddity Driver & FDTI Cable - Radio 2 debug.log (27 kB) Greg T, 07/13/2020 09:19 pm


Related issues

related to Bug #5983: QYT 7900D/Radioddity QB25 Closed 07/29/2018

History

Updated by Jim Unroe 4 months ago

Attach a debug.log file.

Jim KC9HI

Updated by Greg T 4 months ago

I will have to run the process again and I will get the logs uploaded in a little bit. I did not have the developer tools turned on in CHIRP and the log only has the current open and close from after being selected.

Updated by Jim Unroe 4 months ago

  • Status changed from New to Feedback

Greg T wrote:

I will have to run the process again and I will get the logs uploaded in a little bit. I did not have the developer tools turned on in CHIRP and the log only has the current open and close from after being selected.

You don't need to enable "Enable Developer Functions". Just create a "clean" debug.log file (close CHIRP, open CHIRP, cause error, close CHIRP) and then get it per the instructions here.

Jim

Updated by Greg T 3 months ago

Sorry it took me a while longer than I expected to get some time to do the testing and gather the logs. I have two of the Radioddity QB25 Radios, so I thought I would try them both in order to see if there was a difference.

Updated by Bernhard Hailer 16 days ago

Ok, all logs listed this:

Incorrect model ID, got this:

000: 01 03 00 01 07 09 00 01   ........
008: 00 00 20 20 51 42 32 35   ....QB25
016: 02 00 00 02 07 00 00 01   ........
024: 00 00 56 43 35 32 35 34   ..VC5254
032: 04 00 00 05 02 00 00 01   ........
040: 03 05 00 03 09 00 00 01   ........
048: 55 00 00 00 00 00 00 00   U.......

It means that your radio uses a firmware version Chirp doesn't know about yet. This requires that a developer looks into it.

Also available in: Atom PDF

prevent spam