Project

General

Profile

Actions

Bug #11148

open

Baofeng UV-9R Pro squelch issues

Added by Deuterous Ino 10 months ago. Updated 7 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/07/2024
Due date:
% Done:

0%

Estimated time:
Chirp Version:
next
Model affected:
UV-9R Pro
Platform:
Linux
I read the instructions above:
Yes

Description

Hello,

I've noticed odd carrier squelch behavior from a couple of UV-9R Pros I programmed with CHIRP, and am wondering if it's a common experience.

Both of the UV-9R Pros were bought at the same time.

One of them was programmed in June or July 2023, I understand there may be some question of whether the manufacturer changed firmware around that timeframe.

The other was programmed today (Feb 8 2024) with latest CHIRP-next. And then eventually reprogrammed with the backup .img file made when first downloading the radio.

I uploaded a video of the UV-9R Pro units with glitchy squelch, in between a UV-5R and a GT-3WP which are receiving the signal fine. Note also (if you can see it) that when the UV-9R Pros are not squelching the signal, their signal strength indicator is high, not low: https://imgur.com/a/Vp7Jt5H

My other models rarely (GT-3WP, once in a blue moon) or never (UV-5R) squelch the local weather channel without significant fade, static, etc.

Both of the UV-9R Pro units are set to SQL 1, which was programmed to a value of 1 in the Service Settings tab. Interestingly, both of them seem to exhibit the behavior, regardless of the fact that one was programmed with mid-2023 CHIRP (and possibly starting from a .img file from a different model?), and one was programmed with Feb 2024 CHIRP and pasting channel records over a copy of the .img downloaded from the radio, and then reset by re-uploading the initial .img downloaded from the radio, to see if re-uploading the initial .img would make a difference to the squelch problem (it didn't).

Could this be the result of bugs in the beta driver, or is the hardware or firmware bad?

I've included a debug.log of programming both units, unit questionably programmed in 2023 comes first, unit not touched til today comes second. I included the initial backup of the unit first touched today, but sadly not the initial backup of the unit from 2023 because I managed to overwrite that one in the process of making this bug report, sigh.


Files

Baofeng_UV-9R Pro_stock_2nd_unit_newer_chirp_20240208.img (8.2 KB) Baofeng_UV-9R Pro_stock_2nd_unit_newer_chirp_20240208.img the only initial backup still available, from the 2nd of the 2 units Deuterous Ino, 02/07/2024 10:36 PM
Baofeng_UV-9R Pro_was_stock_now_overwritten.img (8.2 KB) Baofeng_UV-9R Pro_was_stock_now_overwritten.img what was uploaded to the 1st radio in debug.log Deuterous Ino, 02/07/2024 10:37 PM
Baofeng_UV-9R Pro_2nd_unit_20240207_work2.img (8.2 KB) Baofeng_UV-9R Pro_2nd_unit_20240207_work2.img what was uploaded to the 2nd radio in debug.log Deuterous Ino, 02/07/2024 10:37 PM
Baofeng_UV-9R Pro_20240210_radio1.img (8.2 KB) Baofeng_UV-9R Pro_20240210_radio1.img Deuterous Ino, 02/10/2024 05:02 PM
Baofeng_UV-9R Pro_20240210_radio2.img (8.2 KB) Baofeng_UV-9R Pro_20240210_radio2.img Deuterous Ino, 02/10/2024 05:02 PM
Actions

Also available in: Atom PDF