Project

General

Profile

Actions

Bug #8145

closed

QB25 - Radio Not Identified

Added by Neal Sacon over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
07/31/2020
Due date:
% Done:

100%

Estimated time:
Chirp Version:
daily
Model affected:
Radioddity QB25
Platform:
All

Description

Radiodity QB25 - Chirp v20200718

Vendor Radioddity
Model QB25
Download from radio
Clone process...
Radio not Identified
Radio shuts off and turns back on again

Not sure what to do about that error - using the vendor supplied cable and driver - I don't think it's a driver error.

No problem d/l from Baofeng UV-5R (different cable / comport)

Actions #1

Updated by Neal Sacon over 2 years ago

Note also that the vendor cable works with the vendor software...able to R/W to radio. Seems to be a Chirp bug for this radio/cable set-up.

Actions #2

Updated by Jim Unroe over 2 years ago

  • Status changed from New to Feedback
  • Platform changed from Windows to All

Most likely the radio has an MCU-Version that CHIRP doesn't know about. Either provide the MCU-Version from the bottom status display area of the OEM software or attach the CHIRP debug.log file.

Jim KC9HI

Actions #3

Updated by Neal Sacon over 2 years ago

MCU VC4254 -- loaded the btech_vc4254.py module -- all is well -- thanks!

Actions #4

Updated by Jim Unroe over 2 years ago

Hi Neal,

Ahhh... I see. I didn't recognize the "Radio Not Identified" as being the error message. Sorry. I should have asked you to attach a debug.log file. Anyway, sounds like the issue #8199 activity will also resolve this issue so I will close this issue.

Jim KC9HI

Actions #5

Updated by Jim Unroe over 2 years ago

  • Status changed from Feedback to Closed
  • Assignee set to Jim Unroe
  • Target version set to chirp-daily
  • % Done changed from 0 to 100

Closing this issue. It is being resolved along with issue #8199. Follow that issue for anything further.

Thanks,
Jim KC9HI

Actions

Also available in: Atom PDF