Project

General

Profile

Actions

New Model #9784

closed

Baofeng BF-V8 (UHF CB)

Added by mik t about 2 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
03/11/2022
Due date:
% Done:

100%

Estimated time:
Equipment Loan/Gift Offered:
No
I read the instructions above:

Description

Apparently a software exists (however I could be wrong):
https://www.rtsystemsinc.com/BAO-V8-Programming-Software-Only-for-the-Baofeng-BF-V8_p_252.html

BF-V8 (BFV8) is not directly supported by CHIRP.
It is a FM UHF CB radio in the 400-470mhz range.

What the BF-V8 looks like:
http://www.security-twowayradios.com/sale-13300705-2020-hot-selling-baofeng-bf-v8-long-range-fm-uhf-400-470mhz-ham-portable-two-way-radiotransicver-wal.html

All help is truly appreciated,
Regards,

Mik


Files

Baofeng_BF-V8A_20230206.img (1.17 KB) Baofeng_BF-V8A_20230206.img Dai John, 02/06/2023 09:14 AM
Capture.PNG (17 KB) Capture.PNG Dai John, 02/06/2023 09:14 AM

Related issues

Related to New Model #10045: BFtech BF-V8SClosed09/17/2022

Actions
Actions #1

Updated by Bernhard Hailer about 1 year ago

Actions #2

Updated by Dai John about 1 year ago

I can confirm that the BF-V8 is fully supported using the BF-888 option in the latest build of CHIRP-next. The BF-V8 has the exact same functionality as the BF-888.
Can the BF-V8 be added to the home page, under Baofeng, as BF-V8 (use BF-888) ?

Actions #3

Updated by Jim Unroe about 1 year ago

Dai John wrote in #note-2:

I can confirm that the BF-V8 is fully supported using the BF-888 option in the latest build of CHIRP-next. The BF-V8 has the exact same functionality as the BF-888.
Can the BF-V8 be added to the home page, under Baofeng, as BF-V8 (use BF-888) ?

This ticket should probably have already been closed. The BF-V8A is already a CHIRP supported model (probably from a similar/suplicate ticket). Would you quickly verify this?

Jim KC9HI

Actions #4

Updated by Dai John about 1 year ago

The BF-V8A appears to be a different radio. When I programmed my BF-V8 (same radio as the link in the OP) using the BF-V8A option it did not save the CTCSS or DCS correctly which led to the squelch not opening even though the correct tone was used.

Actions #5

Updated by Jim Unroe about 1 year ago

Dai John wrote in #note-4:

The BF-V8A appears to be a different radio. When I programmed my BF-V8 (same radio as the link in the OP) using the BF-V8A option it did not save the CTCSS or DCS correctly which led to the squelch not opening even though the correct tone was used.

Same radio. Maybe you've discovered a bug. Attach an image with a channel that has an incorrectly saved tone.

Jim KC9HI

Actions #6

Updated by Dai John about 1 year ago

This fails to open the squelch on another radio set to the same tone.

Actions #7

Updated by Jim Unroe about 1 year ago

Dai John wrote in #note-6:

This fails to open the squelch on another radio set to the same tone.

Thanks for the CHIRP image and screen capture. Both the RX and TX tone are set to the same frequency in the image. My guess is that what is being experienced is a bug in the radio. It wouldn't be the first time that I've seen this. You could verify this but programming the same values using the factory software. I am pretty sure that if you download this from your radio to the factory software, you will see that 103.5 will show up for both encode and decode. The if you program a second channel with the same settings and upload it to the radio, it will behave the same on this new channel.

I will attempt to locate my BF-V8 later today to see how it behaves for me.

Jim KC9HI

Actions #8

Updated by Jim Unroe about 1 year ago

  • Status changed from New to In Progress
  • Assignee set to Jim Unroe
  • Target version set to chirp-py3

After digging out my Baofeng BF-V8A I was able to duplicate the issue and figure out what was causing the CTCSS tone to get suppressed. I will be submitting a patch that should solve the problem.

Jim KC9HI

Actions #9

Updated by Anonymous about 1 year ago

  • Status changed from In Progress to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF