Project

General

Profile

Actions

Bug #8733

closed

Boafeng BF-888s squelch problem

Added by Charles Hall about 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
01/26/2021
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Baofeng BF-888S
Platform:
All
Debug Log:
I read the instructions above:

Description

After programing the BF-888s all si fine except there is no squelch just open static.


Related issues

Related to Bug #7255: Problem with Baofeng BF-888SFeedback11/12/2019

Actions
Has duplicate Bug #8923: Boafeng BF-888s squelch problemClosed01/26/202104/22/2021

Actions
Has duplicate Bug #9497: Baofeng 888S-Squelch levelClosed10/29/2021

Actions
Actions #1

Updated by Bernhard Hailer about 3 years ago

  • Model affected changed from (All models) to Baofeng BF-888S
  • Platform changed from Windows to All

Please refer to #7255 and see whether the tips there help. Please let us know here! Thanks.

Actions #2

Updated by Bernhard Hailer about 3 years ago

  • Status changed from New to Feedback
Actions #3

Updated by Charles Hall about 3 years ago

Bernhard Hailer wrote:

Please refer to #7255 and see whether the tips there help. Please let us know here! Thanks.

Programed using OEM software same results no squelch. I know these are cheap radios but this makes them useless.

Actions #4

Updated by Rudolph Gutzerhagen about 3 years ago

I don't have this particular model, just a UV-5R, but will try to help with some basics.

I see your account is "new". Are you "new" to the radio? to Chirp? If so, let's do the basic questions:

  • do you have more than one of these radios? If so, did you check that the firmware is the same on each or alternatively, always do download for each radio and match that modified image when uploading to that radio?
  • what is the squelch setting on the radio?
  • what is the squelch setting in chirp?
  • if the squelch setting on the radio is non-zero, can you please attach the image file used to update the radio, and attach a debug log from the session where you did the upload to the radio. If the debug log is there from the download session, that would be great too. If all of that is in one log file, you do not need to separate out the information.

Let's go from there, unless someone more experienced has some guidance...

Actions #5

Updated by Bernhard Hailer almost 3 years ago

  • Status changed from Feedback to Closed

No more feedback by submitter.
A related ticket (#7255) lets me suspect that this is a firmware problem on these radios.

Actions

Also available in: Atom PDF