Baofeng uv5r Not Receiving?

[k8ble]

Yeah that looks ok.
The only major difference I see with my file is you have skip turned on.
I understand it should not matter in theory, have you tired turning it off?
Most all your other settings are similar to mine.... so......???

mine won't scan or break squelch. uv 5r v2+.but look under skip he has all (S's) doesn't S mean skip..my chirp program are all blank under (skip). and do you know the correct ver#. thanks

 

[budmanny5554]

There is a bug.

mine won't scan or break squelch. uv 5r v2+.but look under skip he has all (S's) doesn't S mean skip..my chirp program are all blank under (skip). and do you know the correct ver#. thanks

Had same problem after using Chirp, Here is what you do.: After setting up radio completely run stock software. Read the radio, Set the RX squelch to off. Just click each box it defaults to OFF. Drop to next one and click it. After all are set to off write it back to the radio. You may need to MANUALLY adjust your Squelch level on the radio to 2 or 3. If you read the radio again with Chirp and write it back DO NOT TOUCH THE COLUMN UNDER RX SQUELCH. I purposely read made changes to other things and wrote back to both my radios and they were fine. I did not touch anything under that header.There is a bug but it did not fry your radios.

 

[Nomad26Wrecker]

I have a F8+ (Sticker says "BF-F8+") Radio worked for almost a year as a spare work radio. I mostly used it for convention security and the like, Have never been rough with it.

However when i got it out today to program my new jobs freqs into it I noticed that the Rx function is botched. When I hold the MON key all I get is a faint clicking sound. However when I Tx I can hear the radio loud and clear on other units. Even the Local NOAA channel I can only hear clicks with this radio while my other baofeng and 2 wouxun radios hear it loud and clear. I have already checked programming and swapped a number of antennas to exclude that as the problem.

My Radio seems to be a Std Uv-5r in a newer case. My other BF-F8 has the blackout screen where this one has a normal 5r screen.

Anyone have any ideas on what is going on or is this little cheap radio just need to be by APRS nonRX Beacon Station?

 

[Nomad26Wrecker]

Well to update I found a glitch that is likely the cause.
Menu 8 must be enabled (beep=on)
Then I Booted radio holding 3 key to show firmware version and the radio is receiving again.

Weird fix but it worked.

 

[SpugEddy]

The menu 8 option has been addressed either here or in
another forum. Yes indeed a strange bug in the firmware
and an even stranger fix.

Are the F8 radios able to be firmware flashed? I'd like to think
there is an actual fix available rather than just a band-aid.

I have 5 Baofeng BF-F9+TP radios. So far, no real problems.
Fingers crossed

 

[nd5y]

You can't update the firmware in any Baofeng radio.

 

[jwc082]

Having the same problem, although I haven't tried programming this radio with a cable (don't even own one) so the issue can't be related to CHIRP or firmware, best I can tell.

I don't receive a signal on Ham frequencies unless I press MONI or also Menu. Each will give me a few seconds of output, and then go back to not receiving anything.

Interestingly, it receives fine on the AWOS and the FM channels, but not on the local ham stations.

Factory resets, trying the squelch on different settings, turning BEEP on and off, switching FM stations in case it was being confused by interference, nothing seems to work.

Had the radio since February and haven't gotten to use it that much, shame if I had to send it back.

Any thoughts or guidance? Thanks in advance.

 

[khaytsus]

Having the same problem, although I haven't tried programming this radio with a cable (don't even own one) so the issue can't be related to CHIRP or firmware, best I can tell.

I don't receive a signal on Ham frequencies unless I press MONI or also Menu. Each will give me a few seconds of output, and then go back to not receiving anything.

Interestingly, it receives fine on the AWOS and the FM channels, but not on the local ham stations.

Factory resets, trying the squelch on different settings, turning BEEP on and off, switching FM stations in case it was being confused by interference, nothing seems to work.

Had the radio since February and haven't gotten to use it that much, shame if I had to send it back.

Any thoughts or guidance? Thanks in advance.

Are you SURE you don't have PL Decode enabled? If so, you'll only receive when you hold MON.

 

[jwc082]

Are you SURE you don't have PL Decode enabled? If so, you'll only receive when you hold MON.

Hey, thanks for asking. I've got all the CTCSS and DCS settings switched to OFF, full factory settings. Still won't receive, even when I know there's a signal because I can pick it up by tapping MENU or the MONI button.

Thanks all the same, though. If not the PL decoder, what else could it be? I'm dumbfounded....

 

[KC4RAF]

Also, have you checked to see if Menu 8

is on? (that's the beep menu). A few posts above yours describes that issue.

 

[jwc082]

Beep is turned on, and still nothing. I've tried with the Beep setting both on and off, and neither seems to make a difference. It still won't receive.

I didn't used to have this problem... Makes me wonder if something went bad within the unit.

 

[KC9HI]

is on? (that's the beep menu). A few posts above yours describes that issue.

The BEEP bug was an issue about 2 years ago and was fixed in about a month. Unless someone sells you a very old radio, the BEEP shouldn't be an issue.

Jim KC9HI

 

[KC9HI]

Having the same problem, although I haven't tried programming this radio with a cable (don't even own one) so the issue can't be related to CHIRP or firmware, best I can tell.

I don't receive a signal on Ham frequencies unless I press MONI or also Menu. Each will give me a few seconds of output, and then go back to not receiving anything.

Interestingly, it receives fine on the AWOS and the FM channels, but not on the local ham stations.

Factory resets, trying the squelch on different settings, turning BEEP on and off, switching FM stations in case it was being confused by interference, nothing seems to work.

Had the radio since February and haven't gotten to use it that much, shame if I had to send it back.

Any thoughts or guidance? Thanks in advance.

Have you programmed a value in menu 10 (R-DCS) or menu 11 (R-CTCS) that doesn't match the station that you are listening to. Setting these menus to OFF always works.

Also it isn't unusual for receive a radio sold as new that was a return. If the previous owner made the mistake of cross-loading an incompatible CHIRP Radio Images (*.img) file into that radio, then that would cause the issue.

Find someone with a programming cable and download from the radio and send email the *.img file to me. I will be able to tell if the radio has an incompatible image installed. Or just upload a "factory" image with the same firmware version and upload it to your radio to get it working.

Jim KC9HI

 

[jwc082]

Fixed it! Found out the problem was the Antenna.

I switched out the antenna with another I had as a spare and it worked fine. Strange problem, and very similar to what others have described, so take this as another possible solution.

Thanks for your help all the same!

 

[Cameramonkey2]

One update that is REALLY bizarre. Another issue could be bad FTDI drivers under WIN7. This affects ANY radio that is plugged into the cable, not just downloaded configs.

I bought a unit a week ago. worked great after programming on my win8 work laptop. plugged the cable in and win8 grabbed the drivers immediately and I was off to the races. I listened successfully to the skywarn folks reporting in on tornadoes, including one that went right past my office yesterday within a 1/4 mile.

Bought a second unit last weekend, and it was delivered to my office today but from a different amazon seller. My programming cable was at home so I couldnt dupe the config. Listened again to the hams shooting the breeze on my way home tonight on the first radio. No problems. Radio worked perfectly.

Got home and plugged in the cable to my personal win7 box. It wouldnt find the drivers via windows update like my win8 work laptop. (forgot it at the office) I googled the drivers and after avoiding the scam sites I found the drivers and they appeared to install correctly from the factory site.

I pulled the config from my original radio. I set that radio aside and after a few admin tweaks I uploaded the config to the new radio. (both report the same firmware in CHIRP)


From this point, neither radio will receive transmissions from the hams without pressing the mon button. I see the green light come on., the display shows solid receive but no audio. And the menu 8 beep is on.

It appears that simply plugging in the cable to the radio and initiating communication is enough to corrupt the data on the radio.(even if you arent changing anything.)


So it could be a bad cable driver as well causing the issue.

I will report back as soon as I can re-flash a known good config from my work laptop to the first radio.

 

[KC9HI]

One update that is REALLY bizarre. Another issue could be bad FTDI drivers under WIN7. This affects ANY radio that is plugged into the cable, not just downloaded configs.

No software will work unless there is working connection between the radio and computer.

I bought a unit a week ago. worked great after programming on my win8 work laptop. plugged the cable in and win8 grabbed the drivers immediately and I was off to the races. I listened successfully to the skywarn folks reporting in on tornadoes, including one that went right past my office yesterday within a 1/4 mile.

Bought a second unit last weekend, and it was delivered to my office today but from a different amazon seller. My programming cable was at home so I couldnt dupe the config. Listened again to the hams shooting the breeze on my way home tonight on the first radio. No problems. Radio worked perfectly.

Got home and plugged in the cable to my personal win7 box. It wouldnt find the drivers via windows update like my win8 work laptop. (forgot it at the office) I googled the drivers and after avoiding the scam sites I found the drivers and they appeared to install correctly from the factory site.

Are you sure your programming cable has and FTDI chip? Device Manager can be used to determine this.

It is rare that Windows will not supply the driver for an FTDI chip, but it does happen. What I notice here is that it sometimes takes 8 minutes for the driver to be fully installed. The only place I would get an FTDI driver from would be the chip vendor's website, ftdichip.com

I pulled the config from my original radio. I set that radio aside and after a few admin tweaks I uploaded the config to the new radio. (both report the same firmware in CHIRP)


From this point, neither radio will receive transmissions from the hams without pressing the mon button. I see the green light come on., the display shows solid receive but no audio. And the menu 8 beep is on.

Sounds like a radios that has been cross loaded by an incompatible image such as in uploading an image from a radio with BFB firmware into a radio with N5R firmware (or the reverse). This shouldn't be possible to do with a CHIRP daily build from around March of last year or after.

I would be happy to look at them. Make a fresh download from both radios and email them to me: uv5r [at] kc9hi [dot] net

It appears that simply plugging in the cable to the radio and initiating communication is enough to corrupt the data on the radio.(even if you arent changing anything.)

I've plugged and unplugged cables into these types of radios for over 4 years and have never had this happen.

So it could be a bad cable driver as well causing the issue.

It could be but it sounds more like a cross loaded image. Send me the images and we will know for sure.

I will report back as soon as I can re-flash a known good config from my work laptop to the first radio.

Jim KC9HI

 

[Cameramonkey2]

I let windows update run until it decided it couldnt find a driver. I then went to that site and grabbed the drivers which appeared to cause the cable to work. (CHIRP would see the radio and seemingly communicated fine)


I was able to reload the last known good config on my laptop to my primary radio successfully. I was also able to tweak that config and upload to the new seemingly identical radio and both work now.

I still see the issue, but not as bad. It only does it when the signal is weak, so I think I just need to tweak the squelch settings.

I'll email that faulty config for you to look into. as well as the config that works well. I dont think its a cross load issue because on my win8 box it works fine to share configs between radios. (that report the same firmware in CHIRP)

Thanks for helping a noob Jim!