Bug #9701
closedCurrent daily lacks support for my particular DB25-G
100%
Description
I have a DB25-G that is identified as "VC7062" and is unrecognized by the current daily. I used the btech_vc9204.py module I found in a similar thread and it works great with: DB25G_fp = "VC7062"
With that tweak I have zero issues.
Files
Updated by Jim Unroe over 2 years ago
- File btech_vc7062.py btech_vc7062.py added
- Status changed from New to In Progress
- Assignee set to Jim Unroe
- Target version set to chirp-legacy
Hi Dave,
Give this draft driver module a quick test and let me know how it goes.
Jim KC9HI
Updated by Dave T over 2 years ago
Jim Unroe wrote:
Hi Dave,
Give this draft driver module a quick test and let me know how it goes.
Jim KC9HI
Works just fine Jim! I was able to download then upload a config without issue using that module.
Updated by Dave T over 2 years ago
Interesting to note that even the Radioddity software does not recognize this unit.
Updated by Jim Unroe over 2 years ago
Dave T wrote:
Interesting to note that even the Radioddity software does not recognize this unit.
I'm not surprised. The MCU version is a duplicate of a QYT KT8900D variant. Makes me wonder if it has the wrong electronics on the inside, the wrong labeling on the outside or the MCU version was just reused by the factory.
If it was mine, I would program it using Vendor: QYT / Model: KT8900 and see what I could make it do!
Jim KC9HI
Updated by Jim Unroe over 2 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Patch submitted. Support for MCU: VC7062 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 Anonymous over 2 years ago
- Status changed from Resolved to Closed
Applied in changeset commit:7a091d4e2dc9.