[chirp_devel] Driver Testing by Non-developer Users

Dan Smith
Fri Nov 18 10:53:10 PST 2016


> I am trying to work with a user to get his radio supported by CHIRP.
> The model (Baofeng UV-6R) is a supported model, but it is a different
> firmware version and it behaves a little different in the cloning
> process.
> 
> I can send him modified uv6r.py files that he can use the "Load
> module" feature to test the changes. The issue is that this driver
> depends on the baofeng_common.py driver for the cloning process
> itself. I can modify this driver and send it to him, but even after
> loading it using the "Load module" feature, the original driver
> continues to be used.

The original driver? Or the original baofeng_common.py code?

> My question is what do I have to do to be able to allow this user to
> use a modified baofeng_common.py driver?

You can probably send him both, as long as he loads the common piece first.

--Dan



More information about the chirp_devel mailing list