Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BW (Menu 2) is not stored #25

Closed
OE1MWW opened this issue Jan 2, 2024 · 4 comments
Closed

BW (Menu 2) is not stored #25

OE1MWW opened this issue Jan 2, 2024 · 4 comments

Comments

@OE1MWW
Copy link

OE1MWW commented Jan 2, 2024

Changing BW (Menu 2) to another value (for example from 25k to 12.5k) and cycle Power off/on, it will be - as in the example - 25K again.

@ErikS-web
Copy link
Collaborator

Indeed, When power off/on it's back to 25.

Also when switching from VFO to a Memory Channel

@OE1MWW
Copy link
Author

OE1MWW commented Jan 2, 2024

unfortunately does this bug still exist in v16.2

@kamilsss655
Copy link
Owner

It is not a bug.

If you want the changes made to the memory channel saved, you need to save them with menu 17 ChSave function.

NOTE: New filter BWs 8.33k, 6.25k, 5k will not be saved due to CHIRP EEPROM convention that allows to store channel BW with only 1 bit, allowing to store only 2 possible BW values. In the future, once this convention changes or I modify the CHIRP driver we can store new BWs as well.

@sparky93a
Copy link

ahh this relates to my issue logged today. will see if i can close/delete #32

VA7FGT pushed a commit to VA7FGT/uv-k5-firmware-custom that referenced this issue Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants