Currently, none of the settings load in under the UV3-R radio since these settings fail.
They do look resolvable, however without a radio I cannot test. It appears that the memory block at the location which chirp is reading these settings from has the memory bits all set (0xFF) where it expects to find a valid frequency. I compared this to the free UV3-R tool (old) and it appears to set the bits correctly, wears the image in the tests does not. It may be a possible that the image is a diff. model or variant of the previous uv3r.
I will put a patch together with only the test code if you would like to try resolving it as I believe the settings test still remains useful.
Date: Wed, 28 Jan 2015 17:37:32 -0800
From: dsmith@danplanet.com
To: chirp_devel@intrepid.danplanet.com
Subject: Re: [chirp_devel] [PATCH] Add Support for Settings UnitTest
> [PATCH] Add Support for Settings UnitTest
> Add a basic unit test coverage of the radio Settings API.
> Currently, all but one image passes the test (UV3R).
> Commented out offending code in uv3r module.
This is great, thanks! I'd rather not just disable the settings in the
UV3R driver to add this. Do the failures look resolvable?
Also, the commit message says "commented out" but actually remove the code.
If you want to send just a patch with the test bit, I'll see if I can
fix the UV3 driver and then apply it.
--Dan
_______________________________________________
chirp_devel mailing list
chirp_devel@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers