Bug #7813

Error setting memory tuning step 12.50 is not supported(UV5R)

Added by Joshua Storms about 1 month ago. Updated about 1 month ago.

Status:Closed Start date:04/21/2020
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:All
Model affected:Baofeng UV-5R

Description

Tried to put some new Freq's into the radio today (via Import from stock config) and I got this error "Error setting memory tuning step 12.50 is not supported", Chirp About window shows "CHIRP daily-20200409". Was trying to load the FRS and GMRS in and that was when I continued to get the error.

History

Updated by Jim Unroe about 1 month ago

  • Status changed from New to Feedback
  • Priority changed from High to Normal
  • Platform changed from Windows to All

Joshua Storms wrote:

Tried to put some new Freq's into the radio today (via Import from stock config) and I got this error "Error setting memory tuning step 12.50 is not supported", Chirp About window shows "CHIRP daily-20200409". Was trying to load the FRS and GMRS in and that was when I continued to get the error.

Hi Joshua,

Are you sure you are running CHIRP daily-20200409? Are you sure you are entering the frequencies into a tab that is compatible with a Baofeng UV-5R (or UV-82) style radio?

To test, I just updated to CHIRP daily-20200409. Then I opened the US FRS and GMRS Channels stock config file into CHIRP. No issues. Next I loaded a CHIRP Radio Images (*.img) file that was saved earlier from a UV-5R. This created a tab in CHIRP that is compatible with a UV-5R radio. This time I imported the US FRS and GMRS Channels stock config file into this tab. No issues. I then manually keyed in all 22 FRS frequencies (the GMRS frequencies are the same) into this tab. All entered 100% with no error messages or issues.

A regression that "broke" tuning steps for many drivers occurred early last year when fixing a CHIRP bug related to tuning steps. A patch to fix the issue in the uv5r.py driver (used for most Baofeng UV-5R and UV-82 style radio models) was applied back on 02/17/2019. I could see where there may be a small number of other radio drivers that may still need to be patched for this issue, but not the uv5r.py driver.

Unless you can show the steps you are taking to reproduce this error, or show that this error is actually for different radio series, I believe this issue should be closed.

Jim KC9HI

Updated by Joshua Storms about 1 month ago

I had done exactly what you described yesterday and it didn't work. Tried it on a second radio same model and everything and it worked just fine. I was probably missing a step yesterday. I appreciate the help.

Updated by Bernhard Hailer about 1 month ago

  • Model affected changed from UV5R to Baofeng UV-5R

Hi Joshua, I'm unsure: are you saying the problem has been resolved, or do you still have a problem with one out of two radios?
If so, then you should provide a debug log as described in the Wiki: "How To Report Issues"? Thanks!

Updated by Joshua Storms about 1 month ago

Yes problem is resolved.

Updated by Bernhard Hailer about 1 month ago

  • Status changed from Feedback to Closed

Thanks for the feedback!

Also available in: Atom PDF