Baofeng UV5 squelch problem, any solutions?

[joeuser]

Oh! OK, I didn't understand that (as you can clearly tell). So these wayward IMG files... Are people sharing them or something? I mean, I can't mess up my own IMG file when I use CHIRP to change my current setup & upload it back to my rig, can I? This was an issue with CHIRP itself, correct?

 

[wa1nic]

Did you enable tone or digital squelch for receive by any chance, and are the tone or digital codes correct? If not, you wont hear anything unless you push the button on the side.

 

[jonwienke]

As long as you download from the radio, change settings, and then upload back to the radio, you're fine.

Unless your radio has the keybeep bug, in which case turning off keybeep will disable receive, regardless of whether you do it with CHIRP or from the keypad.

 

[joeuser]

Right, I left mine on. Glad I did, although I may not be effected... OK TYVM!

 

[KC9HI]

Oh! OK, I didn't understand that (as you can clearly tell). So these wayward IMG files... Are people sharing them or something? I mean, I can't mess up my own IMG file when I use CHIRP to change my current setup & upload it back to my rig, can I? This was an issue with CHIRP itself, correct?

Well at least a CHIRP issue caused by Baofeng. You could download from your radio and upload to your radio all day long and there would never have been a problem.

From BFB231 firmware through BFS313 firmware, the "main" memory layout has always been the same. CHIRP has always allowed sharing .img files amongst all of these firmware versions as a convenience to the CHIRP user. When Baofeng released the N5R-20 firmware they changed the memory layout and loading a .img file from a radio with an older firmware version would overwrite the changed memory and this caused the receive issue. The same would be true if a .img file from a radio with N5R-20 firmware was uploaded to a radio with a previous firmware version.

Now that CHIRP knows about that memory layout change, it has been updated to not allow the cross loading of .img files between radios with these different memory layouts. Just be sure to use a CHIRP daily build dated 20140714 or later with a UV-5R or UV-5R variant radio.

Jim KC9HI

 

[joeuser]

Well at least a CHIRP issue caused by Baofeng. You could download from your radio and upload to your radio all day long and there would never have been a problem.

From BFB231 firmware through BFS313 firmware, the "main" memory layout has always been the same. CHIRP has always allowed sharing .img files amongst all of these firmware versions as a convenience to the CHIRP user. When Baofeng released the N5R-20 firmware they changed the memory layout and loading a .img file from a radio with an older firmware version would overwrite the changed memory and this caused the receive issue. The same would be true if a .img file from a radio with N5R-20 firmware was uploaded to a radio with a previous firmware version.

Now that CHIRP knows about that memory layout change, it has been updated to not allow the cross loading of .img files between radios with these different memory layouts. Just be sure to use a CHIRP daily build dated 20140714 or later with a UV-5R or UV-5R variant radio.

Jim KC9HI

And, let me guess, this is why you (IIRC), were looking for a specific IMG file couple months back?

 

[KC9HI]

And, let me guess, this is why you (IIRC), were looking for a specific IMG file couple months back?

Yes. Exactly.

I never mess with any new CHIRP supported radio until after I make a backup .img file from it. But in this case, I still don't have one of these radios with N5R-20 or N5R-30 firmware in my possession, so I never got a chance to save my own "factory" N5R-20 .img file.

For around 2 years, it has never been an issue for anyone to swap CHIRP .img files between their various UV-5R and UV-5R variant radios. So someone purchasing a set of 5 new radios immediately uploaded a .img file made for the radios that he already owned and never thought twice about needing to make a backup .img first. That was the first time that I had ever heard about N5R-20 firmware and my quest for getting a .img file from a working radio with N5R-20 firmware began.

Fortunately, a working CHIRP .img file was sent to me, I forwarded it on and the 5 radio were recovered to working order.

Jim KC9HI

 

[ScottPerry]

UPDATE: Baofeng Squelch Problem CAN BE FIXED

I was able to RECOVER a failed Baofeng BF-F8+ to which I caused squelch problems.

CHIRP will allow a user who is ignorant of the firmware versions to mix versions and cause radio errors.
I am glad that CHIRP development will look into adding a feature to check for version mismatching.

My 1st Baofeng BF-F8+ was indeed defective. The monitor button was supposed to illuminate the LED light on a quick press. Instead of cycling through either a constant-on mode, a flashing mode, or off, the light flickered. The light was sporadic and symptomatic of loose wiring or insufficient LED power. Soon after, the speaker output halted completed but the headphone audio worked. I sent it back for a replacement.

My 2nd Baofeng BF-F8+ worked out of the box. I immediately applied my image through CHIRP from my 1st radio and then I ended up with the squelch issue. I could only hear audio if I held the monitor button down but never checked this before I applied the image through CHIRP.

My 3rd Baofeng BF-F8+ was tested out of the box. All functions worked. I applied the image from the 1st radio and then this one also was unable to receive audio unless the monitor button was held in.
This is where I obtained the information about how to find the firmware version.
This is where I also obtained the original image for that firmware version.
I opened this correct firmware image in CHIRP, then I manually copied over each setting from my old profile, then I uploaded this to the radio. The squelch problem was fixed and the radio works perfectly.

I fixed the squelch issue with CHIRP and a correct original version of the correct image for my radio.

I had no idea that these IMG files were something more than just preferences. I was unaware that it was the firmware image (or something like that) and my setting preferences.
Yes, it would be wonderful if *somehow* CHIRP could warn me that I was about to apply a version "x" image to a version "y" radio, but then again, how would it know if it is only uploading without downloading and then checking and THEN uploading.

Someone was nice enough to publish IMG files for each version.
I researched a document which showed me how to hold in the 3 button when powering the unit on. The display briefly showed the version, in my case BFS297, for one second before continuing with the powering on sequence as normal. I then grabbed the generic blank version 297 image file, opened it with CHIRP, typed my preferences and settings into that profile manually, then uploaded it to the radio. It worked!

Baofeng BF-F8+ Squelch Problem FIX After Version Mismatch
(1) Determine the device version by turning on the radio while holding down the 3 button.
(2) Obtain a clean or functional image of that version for the radio.
(3) Upload that correct firmware version image via CHIRP to the radio.
(4) Test and ensure that the radio squelch problem is now fixed.
(5) Continue to make changes to this specific image file or settings file via CHIRP. Remember not to take an image or version file downloaded from another Baofeng radio and upload to another Baofeng radio -- instead download the ORIGINAL image from each and work within each separately -- they could be different firmware versions even through they look the same on the outside and are the same model.

 

[KC9HI]

I had no idea that these IMG files were something more than just preferences. I was unaware that it was the firmware image (or something like that) and my setting preferences.

It is a dump of the state of the memory of the radio in 2 sections. The "main" memory area and the "aux" memory area. Basically everything.

Yes, it would be wonderful if *somehow* CHIRP could warn me that I was about to apply a version "x" image to a version "y" radio, but then again, how would it know if it is only uploading without downloading and then checking and THEN uploading.

CHIRP has been doing this since CHIRP daily-20140717. If the .img file is not compatible with the radio, the upload is aborted with a message saying so.

I researched a document which showed me how to hold in the 3 button when powering the unit on. The display briefly showed the version, in my case BFS297, for one second before continuing with the powering on sequence as normal. I then grabbed the generic blank version 297 image file, opened it with CHIRP, typed my preferences and settings into that profile manually, then uploaded it to the radio. It worked!

This is only correct for firmware versions up to and including BFB297. All firmware versions after BFB297 all report BFB297 in the [3] + Power-On message (except for BFS313 which reports BFS297). So the [3] + Power-On message is no longer useful for finding the firmware version of these radios.

The only way to know the "real" firmware version is to download from the radio to CHIRP and look on the Settings -> Other Settings menu. The "real" firmware version is shown in "Firmware Message 1" unless it is shown as "VER" (in that case it would be "Firmware Message 2". It is the "real" firmware version that your downloaded "factory" or "reset" .img file must match.

(1) Determine the device version by turning on the radio while holding down the 3 button

As I mentioned before, this statement is incorrect. Your firmware version could be BFB299, BFB301, BFS311 or N5R-20 and you would never know it.

Remember not to take an image or version file downloaded from another Baofeng radio and upload to another Baofeng radio -- instead download the ORIGINAL image from each and work within each separately -- they could be different firmware versions even through they look the same on the outside and are the same model.

If you are using the latest CHIRP daily build, you won't have to remember because it won't let you cross-load an incompatible .img file.

You can still safely transfer the memory channels from another .img file. It doesn't have to be the same firmware version, same radio model or even the same brand. Just use the File -> Import feature of CHIRP and change the file mask to "Chirp Radio Iimages (*.img)". Doing this I have imported the channels of my 2 year old UV-5R into my Baofeng UV-B5, UV-82, BF-F8HP and Icom IC-Q7a.

Jim KC9HI

 

[KD9CNK]

I have the same problem with my UV-5RA. One of my local EMA members upload the wrong firmware due to an old version of CHIRP. I understand how to fix this but I can not locate a copy of the N5R-20 image on any of the recovery lists.

If you have a copy, can you forward it or post it?

John KD9CNK

 

[KC9HI]

I have the same problem with my UV-5RA. One of my local EMA members upload the wrong firmware due to an old version of CHIRP. I understand how to fix this but I can not locate a copy of the N5R-20 image on any of the recovery lists.

If you have a copy, can you forward it or post it?

John KD9CNK

The Miklor website has the procedure for recovery and a link to my stash of "factory" .img files.

UV5R F8HP Recovery Baofeng Pofung UV5R

Jim KC9HI

 

[AC2KW]

I have several UV5s types with firmware 297
and none of the units have a working squelch.
I have not joined the CHIRP mail list but use daily builds.
Have not found any bugs reported or fixed about this issue

any solutions

Use the latest version of Chirp (1-11-2015) to modify squelch settings from a system settings menu.

 

[mehran_o0o]

I fixed it

so I had this issue and nowhere I found any answers. I found out in one weblog that the squelch setting in baofeng is garbage. so get your chirp ready and download the file from radio. then go to settings and in service setting change your squelch setting to higher value. 36 worked for me. so instead of the default ones change them to other value starting from around theirs and go up to 70ish. this way you definitely will get working squelch. and to the friend who said throw it out and get a real ham, not everyone has the money to buy a good radio. baofeng is good for the price but yes you get what you pay for. as of now Im doing many mods on mine, making it waterproof and stuff, I paid 30 bucks for my uv5r and so far its a good lil thing.

I hope that works for you as it did for me.

 

[Leelorr]

RE: Squelch settings

I read a post somewhere by a user that was very happy with the settings when he started at 0, then added 24 to every higher setting, like:
0
24
48
etc.