Project

General

Profile

Actions

Bug #6765

open

keypad/menu changes will not take after programming with PC/Chirp. Baofeng UV-5RTP and BF-F9V2+ affected.

Added by Brian Budlong over 5 years ago. Updated over 5 years ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
05/02/2019
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Baofeng UV-5RTP and BF-F9V2+
Platform:
Windows
Debug Log:
I read the instructions above:

Description

As mentioned above, I'm unable to get a "permanent" change to settings on the above radios, particularly when changing CTCSS on the fly (Menu items 11 and 13). If I make the changes from the keypad (and hear "confirmed"), pressing any key afterwards discards those changes. If, after making the changes, the menu mode is allowed to "time out" and return to normal mode, those changes are retained until the channel is changed or you re-enter Menu mode. In other words, saving the changes doesn't take, permanently, from the keypad. After initially programming about 12 different radios, 9 UV-5RTPs and 3 BF-F9V2+, +all but three+ exhibited this behavior. These 9 radios didn't function and accept changes as the manuals suggest (while the others were working correctly). Of those 9 that weren't working as expected, these were re-flashed with their original factory programming, and additional attempts to upload the custom programs was re-attempted - with about 6 of those radios now working correctly. The remaining radios (1 BF-F9v2+ and 2 UV-5RTPs) still retain this errant behaviour, even after several attempts to reprogram them with slight changes in method. All other aspects of channel programming appear to have uploaded correctly.

I've been unable to find any references in the manuals that hint this to be anything near normal behaviour.

This behaviour was present whether the radio menu was entered from VFO or MR mode (a suggestion I noted in another similar bug report), in either case (ie, VFO or MR mode) the programming via keyboard (at least on the described functions) wouldn't take. Additional, when this behaviour was observed, the power setting within the menu would also fail to accept a 'permanent' change, while a temporary change (toggling the # key) worked as it should.

Comparisons between the settings of the factory img vs the custom img (built off the factory imgs) revealed no differences that appeared significant.

The BF-F9V2+ radios were purchased in 2016. The UV-5RTPs were all purchased in April 2019 (different vendors, but same firmware).

Actions

Also available in: Atom PDF