TerriKennedy

I'm not involved with that product (I do the BF-F8HP Pro handheld and the GMRS-RPT50), but BTECH seems to be committed to providing features people request, as upgrades. The BF-F8HP shipped with firmware V29, went to V33 about a month and a half later, and V44 which just came out. A bunch of the enhancements in that firmware were due to requests from Facebook, here, to me directly or to BTECH. So the radio you bought the week it was released in October 2024 can be upgraded to the same functionality as the units currently shipping. The only difference is that new V44 radios will come with a somewhat updated v44 manual which describes the new features. The GMRS-RPT50 got a bunch of features people asked for, like being able to used the microphone to use the radio as a base station, to get rid of the annoying (if you're the only person with physical access to the repeater) password prompt, etc. * Please bear in mind that I'm a contractor working with BTECH, so noothing II say should be construed as the official position of BTECH. vers-old.pdf

That's because you have radios from a vendor who either feels that a) what you got was good enough, b) you don't need to know what was fixed, and/or c) if we deign to provide firmware to you out of the goodness of our hearts and it bricks your radio, tough - buy another one. For a look at what REAL firmware release notes look like, and the sorts of new features that can be provided: vers.pdf

You will likely have better results with CTCSS as it is analog tones instead of digital codes. For a somewhat strained comparison, consider an over-used VHS tape (if you're old enough to remember such things) - it's analog and when there's a worn spot on the tape you get streaks of the wrong color on the screen, or the picture rolls, or something similar that usually clears up. Compare that to a scratched DVD where the picture will just turn into a bunch of digital blocks and freeze, and you can't even fast-forward your way out of it. That's digital.

I hate updates that either just appear with no documentation whatsoever, or with something that says "fixed some bugs, added features". That's why the firmware release notes for the BTECH BF-F8HP Pro list every single thing that was changed, even if it is something the user will never encounter (how often do people go into the power-up diagnostic info menu?). Unfortunately, the only radio I have that level of control over is the BF-F8HP Pro.

The payment should be associated with a FRN and show up as unused funds. If you apply for a new license using that FRN, instead of paying through the payment portal you should see your $35 there and a balance due of $0.

Like my grammar school history teacher taught us, any country that has the words "Democratic" in its official name, isn't.

I'll let you in on a secret - if a Lovense toy is turned on but a) isn't connected to a controlling Bluetooth phone / etc. and b) doesn't have a password set (no password is the default and they don't explain why setting one is a good idea), they're discoverable via BLE (they will all be named "LVS", the firmware version, and the short product code for the device). Get a BLE scanner app for your phone and you'd be surprised how many of these are around and broadcasting. Since they're broadcasting, it's OK to monitor them with a BLE app. Installing the Lovense app and actually connecting to one of them would most definitely NOT be OK.

The single-chip RF chips in radios like the ones from Baofeng are going to produce harmonics that are 2x the main frequency (and other multiples). Those are so far out-of-band that no GMRS repeater is even going to "hear" them, let alone act on them. Early Baofeng (and other models) used to have terrible harmonics. Their designs have gotten much better. There are people with TinySA's (an amazing piece of design - I'm not knocking it) but who cable them up through an attenuator directly to the radio's antenna connector. That is not the FCC's prescribed test methodology, so it's comparing apples and turtles (not even oranges). I can explain why some tri-band radios appear "dirty" on 136-174 direct-connect test, but since this is a GMRS group that isn't relevant here.

In the 1980's I was exposed to an unshielded Cobalt-60 source. I got the heck out of there quickly and called the appropriate people who came ASAP, put it in a cask, and took it away. I'm still kicking at age 66, though some people might say that explains a number of things about me. I never planned on having kids, anyway. I describe it as "You know it's going to be a bad day when you can sense the ozone forming in your mouth". Sue and I were watching HBO's Chernobyl mini-series, and in the first episode one of the firefighters says "Why does it taste like metal?" which is probably the same thing.

There shouldn't be any in the firmware. I hate release notes that say "here's 2 new features and we fixed some other stuff". If you look at the V33 release notes, it covers everything, including stuff most users will never see (like fixing the diagnostic screen you get if you hold "8" while powering-on). There are some manufacturing keypress combos, and I know some, but not all of them (and can't tell). In the CPS, what you see is what's there. The only "secret" (which I've previously mentioned) is that 1.2.5m will eventually (1-2 months after the BTECH release) become available in my "Modified UV-17 Pro GPS (and similar models)" CPS, and will include BF-F8HP Pro support along with all of the other models. It won't have the BTECH branding or the BTECH-exclusive features like the firmware update utility. The most recent UV-17/"Generic" release was 1.2.5k (1.25l was for the BF-F8HP Pro only) and you can get it here.

Since you're talking about receiving and not transmitting (the BF-F8HP Pro is not type approved for Tx on GMRS - it's an amateur licensed hand-held)... Wait for the next release of the BF-F8HP Pro firmware. I can't say when it will happen, other than "probably this month". Then look on the BTECH web site for highlights in the new firmware, or download the "Firmware update bundle" which has the firmware, quick installation instructions, and a detailed list of changes in each firmware version.

I'm glad you found it informative/helpful. I think I'm likely the only programming software author on here, except perhaps the CHIRP folks. I can't tell you what will be in future firmware, sometimes because I have beta firmware but am under a non-disclosure agreement or because I don't have a specific firmware yet and sometimes there are surprises. I'm a contractor to BTECH for the CPS, firmware features/testing, and reviewing ad copy among a few other things, not an employee, so there can be ideas floated within BTECH that I only hear about when I see new firmware with them. With that out of the way, I can say that you will get one of the things you asked for in the next public firmware release. To address some of your other points: 1) I'll add it to the feature request list. For technical reasons, it will likely only be for the duration of the scan in progress, not until the next power cycle. 2) Answered above. 3&4) There are 10 levels in the radio. The radio just offers "every other one" because there isn't much difference between steps. The VHF table is currently 0, 16, 18, 20, 22, 24, 26, 28, 30, 32. These can be adjusted, but they live in the "calibration area" and we'd rather not access that with the CPS. There's too much other stuff nearby that the CPS would have to re-write that is radio-specific as tuned by the factory. Don't hold your breath, but some sort of unsupported utility might eventually appear. 5) This is very unlikely to appear in the CPS. However, you can write a radio with CHIRP and read it back with the CPS, or vice versa. So pick which one does a particular job best. CHIRP manages the regular settings for a huge number of radio models, while the CPS is specific to the BF-F8HP Pro and supports all of the other radio features - startup picture, voices, firmware updates, and so on.

FWIW, I've never declined an access request to my repeater (detailed on the previous page). The only reason I don't publish the tones and label it as "open" is because word will get out (beyond the members here) and I'll have people on the repeater who won't respect either FCC regulations or my own rules. With request "by access request", I know that whoever is asking at least has a GMRS license and I have their contact info should I need to make operational changes to the repeater that need to be announced.

These and other fixes will be in 1.2.5m. Unfortunately, I can't make some changes to the CPS until I get firmware that's close to the release version, and then I deliver the CPS to BTECH and they validate it before releasing it. With the original V29 firmware and CPS 1.2.5l, new features in pre-release test firmware were pretty well set and the remaining firmware versions were bug fixes or UI improvements that didn't affect the CPS. Firmware V33 was released while I was out in the Mojave Desert - the reason that elevation now works properly instead of telling you you're at an altitude that requires supplemental oxygen is because I took a radio to Badwater Basin (282 feet below sea level) as well as other locations (see picture) to verify the accuracy of the reported altitude. The firmware change notes were written by me at my campsite and uploaded via satcom ($$$) to BTECH because I was in the middle of nowhere. The changes to enable SK1 and add NOAA were felt to be minor enough to wait for 1.2.5m. 1.2.5m should release either with or within a few weeks after the next firmware update is released. That isn't entirely under my control. It adds the SK1 and NOAA changes as well as many other changes - both bugfixes and improvements to the CPS and its manual, as well as support for the new features coming in the next firmware release. One complicating factor is that Baofeng won't give BTECH certain critical information I need to make some CPS updates until BTECH says "this firmware is good - put it in new radios". Then it's a mad scramble for me to finish the CPS and get it to BTECH for testing. I can't tell you about new features or other things in the upcoming firmware release, but I will say that 1.2.5l was my internal build number 290 (since 2023). The forthcoming 1.25m is now up to build number 319 and I still have 5 critical pending items and another 10 WIBNI (Wouldn't It Be Nice If...) feature requests that won't hold up the release of 1.2.5m if I don't get to them. 2 of the 5 critical ones can't be addressed until BTECH approves the next firmware release and I get the data I need from Baofeng.

CHIRP's idea of zones is very different from zoned Baofeng (and similar) brands. I think it may be based on some high-end radio. Anyway, to CHIRP, zones are a table where you can use a checkbox to put a channel into one (or more, or zero) zones. On the Baofeng radios, zone names are basically text strings that live in the settings menu and channels go into zones based on channel number as someone described above. Regarding your issues with the BTECH CPS, I'd be very interested in hearing about them, since I wrote that software. Assuming you are using CPS version 1.2.5l, can you give me more details (via DM if you like). In particular, were the unexpected channels created on the radio after a write, or did the duplicates appear in the programming software? If you have a .dat file that causes the problem, I'd like to see it. You can either DM me here or email BTECH support (not putting the email address here to foil spam crawlers) and just put "Terri asked me to have you forward this to her" near the top of your email if you don't want to reach out to me directly (just because I say I wrote it is no proof that I did, although the "About" box will provide a hint). Before we get that far, can you load your .dat file and just click "[Next]" at the bottom of the channel window to go through all 10 zones? You might get a message about corrupted data when moving to a new zone. The CPS assumes that if it's in a .dat file it can load, it's valid. But paging through each zone does additional checks to make sure all the settings are valid.