Bug #2903
closedFreqs between 145.200 and 145.500 Default to Mode=NFM
0%
Description
Although the 2 meter band is by default Wide Mode the last 2 Daily Builds of Chrip (and maybe more) for Windows Installers default frequencies between and including 145.200 and 145.500 as narrow mode (NFM). You can manually change them, but it seems they should default to FM mode as those outside this range do. This is with the Baofeng UV82 models and maybe more.
Files
Updated by Tom Hayward over 8 years ago
This comes from the bandplan: http://chirp.danplanet.com/projects/chirp/repository/entry/chirp/bandplan_na.py#L134
I have no idea why it's set that way, but that's the culprit. Sean Burford contributed this code as part of #681.
Updated by Cecil Rendon over 8 years ago
There are coordinated repeaters using that frequency range. Example: N6NA, enter into Chrip 145.250 for an offset of -.6 and Chirp wants it to TX on 144.410 NFM. It should be FM. Just an example of how the default would cause issues.
Updated by Bernhard Hailer over 3 years ago
- Status changed from New to Closed
- Model affected changed from Baofeng UV82 to (all models)
- Platform changed from Windows to All
I've reviewed the band plan, and it actually defines this region as "FM repeater outputs", with no restrictions on bandwidth.
When I double-checked on the Chirp band plan, it's set to "FM", not "NFM" - looks like someone fixed it.