Bug #9687

Radioddity QB25 Error

Added by Marcus Wensyel 11 months ago. Updated 11 months ago.

Status:Closed Start date:01/08/2022
Priority:Normal Due date:
Assignee:Jim Unroe % Done:

100%

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

Description

I just received a new Radioddity QB25. I am able to read/write to it using their program, but when I try with CHIRP I get Radio Identification Failed. I am using CHIRP daily-20220103.

debug.log (39.5 kB) Marcus Wensyel, 01/08/2022 01:33 pm

btech_vc9204.py (158 kB) Jim Unroe, 01/08/2022 04:11 pm

Associated revisions

Revision 3650:41517fac5241
Added by Jim Unroe 11 months ago

[QB25] Add additional MCU Version for Radioddity QB25

This patch adds an additional MCU version (VC9204) for the
Radioddity QB25 (QYT KT7900D variant).

Fixes #9687

History

Updated by Jim Unroe 11 months ago

  • Platform changed from Windows to All

Hi Marcus,

According to the debug.log you provided (thanks), your radio has an MCU version that CHIRP is unaware of. It needs to be added to the driver module used for your radio.

I see that you assigned this issue to yourself. Were you planning to do the work to address this issue?

Jim KC9HI

Updated by Marcus Wensyel 11 months ago

No, that was an error. I also recreated the issue by mistake attempting to remove the assignment. Please let me know when/how to resolve.

Mark KB8TAC

Updated by Jim Unroe 11 months ago

  • Status changed from New to In Progress
  • Assignee changed from Marcus Wensyel to Jim Unroe

OK. I am on it. I will have something for you to try after supper.

Jim

Updated by Jim Unroe 11 months ago

Mark,

Give this test driver module a try. Below are the instructions for how you use it...

1. Save the test driver module (btech_vc9204.py) to a convenient location. Note: Do not right-click the link to download.
2. Click Help in the menu bar and then enable Enable Developer Functions.
3. Click File in the menu bar and then choose Load Module.
4. Locate and load the test driver that was saved in step 1.

CHIRP should now have a red background to indicate that it is running with an externally loaded driver module. Note: This does not permanently change your CHIRP installation in any way. Once you close and then re-open CHIRP, you will have to load the test driver again in order to have support for the VC9204 MCU version.

Try to download from your radio. Report back with your results.

Jim KC9HI

Updated by Marcus Wensyel 11 months ago

That worked, I was able to download from the radio, make a change, and update back to the radio.

Mark KB8TAC

Updated by Jim Unroe 11 months ago

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

Marcus Wensyel wrote:

That worked, I was able to download from the radio, make a change, and update back to the radio.

Mark KB8TAC

Mark,

Patch submitted. Support for MCU: VC9204 will be in the next CHIRP daily build following acceptance. In the mean time, just continue to use the temporary test driver module. Once CHIRP has been updated you can stop using the test driver module and set Enable Developer Functions back to disabled.

Jim KC9HI

Updated by Jim Unroe 11 months ago

This will likely resolve issue #9681 as well.

Jim KC9HI

Updated by Anonymous 11 months ago

  • Status changed from Resolved to Closed

Applied in changeset 41517fac5241.

Also available in: Atom PDF