CHIRP

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

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

Jim

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

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

Applied in changeset commit:41517fac5241.