Bug #8199

Radioddity QB25

Added by Dave Smith about 1 month ago. Updated about 1 month ago.

Status:Closed Start date:08/24/2020
Priority:Normal Due date:
Assignee:Jim Unroe % Done:

100%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:All
Model affected:QB-25

Description

Hello,

I get the error "Radio Identification Failed" from a newly purchase Radioddity QB25.
I see from past reported issues on this radio, that the issue might be due to an updated MCU-Version.

Version: VC4254
I included the debug.log
I'm running chirp-daily-20200807

debug.log (27 kB) Dave Smith, 08/24/2020 03:52 pm

btech_VC4254.py - Custom driver module for testing radios with MCU Version VC4254 (141.7 kB) Jim Unroe, 08/25/2020 06:44 am

debug - After Driver Module Update.log (610.7 kB) Dave Smith, 08/25/2020 08:58 am

Associated revisions

Revision 3400:1a099246467b
Added by Jim Unroe about 1 month ago

[QB25] Add MCU Version for Radioddity QB25

This patch adds an additional MCU version to support the Radioddity QB25
quad-band mobile radio.

fixes #8199

History

Updated by Jim Unroe about 1 month ago

  • File btech_VC4254.py added
  • Status changed from New to In Progress
  • Assignee set to Jim Unroe
  • Target version set to chirp-daily
  • Model affected changed from (All models) to QB-25
  • Platform changed from Windows to All

Dave Smith wrote:

Hello,

I get the error "Radio Identification Failed" from a newly purchase Radioddity QB25.
I see from past reported issues on this radio, that the issue might be due to an updated MCU-Version.

Version: VC4254
I included the debug.log
I'm running chirp-daily-20200807

Hi Dave,

Thank you for checking for other issues first and then providing everything needed to resolve this issue.

Give this custom driver module a test and let me know if it works. If it does, I will submit it as a formal patch. Here is how you use it to program your radio until support is officially added to CHIRP.

1 Save "btech_VC4254.py" to a convenient location
2 Click "Help" in the menu bar and enable "Enable Developer Functions
3 Click "File" in the menu bar and choose "Load Module"
4 Locate and load the custom driver module saved in step 1

That's it. Now you should be able to download from and upload to your radio.

Note: This test driver module does not permanently change your CHIRP installation in any way. If you close CHIRP, you will have to load this custom driver module again before you can clone your radio.

I am looking forward to your feedback.

Jim KC9HI

Updated by Dave Smith about 1 month ago

Hi Jim,

I loaded that module you uploaded and it worked fine.
I was able to download and load from the QB25.
From Log: Positive ident, this is a Radioddity QB25

Not that you asked for it, but I did include the debug log after I applied your test driver and modified the data on the QB25.

Hope to see this applied to CHIRP soon.

Thanks for the help,

Dave

Updated by Jim Unroe about 1 month ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

Hi Dave,

Thanks for the quick feedback. I have submitted the patch. We are now waiting for it to be accepted.

With the current Covid 19 situation, it can take some time between submitting a patch and having it accepted into a new CHIRP daily build. So in the mean time, keep using the temporary driver module. Once a new build is released that includes the patch, you will no longer need the driver module and you can disable "Enable Developer Functions".

Jim KC9HI

Updated by Anonymous about 1 month ago

  • Status changed from Resolved to Closed

Applied in changeset 1a099246467b.

Also available in: Atom PDF

prevent spam