Automatically defaults to wrong mode on 14.115

PoLo - Issues & Ideas
1

Hey there, just wanted to document an issue showing up in PoLo. When setting my CW frequency during an activation to 14.115 the mode defaults to SSB. It could be that that was on purpose for worldwide appeal but in the US that is in the CW portion of 20 meters. Logged a bunch of contacts this weekend only realize this default after I submitted my logs. If it’s on purpose, no problem, If it’s accidental, I just wanted to bring it to your attention. :slight_smile:

2

Looks like a regressive bug in the band plan file - this should be fixed/returned to normal in the next update.

Alan

3

Awesome, thank you Alan.

4

Hi Alan,

I’ve been digging into lib-operation-data and I think I can see the issue.

The Phone segment at 14,112–14,350 kHz currently has “regions”: [1, 2]. This is correct for Region 1 (Europe), where SSB is permitted from 14.112 MHz
upwards, but Region 2 (the Americas) is included in the same segment. In the US, 14.112–14.150 is still the CW portion of 20m; SSB doesn’t begin until
14.150.

The fix should be straightforward:

  1. Change “regions”: [1, 2] → “regions”: [1] for the 14,112–14,350 Phone segment.
  2. Add a Region 2 Phone entry from 14,150–14,350 (currently only covered by the US-specific countries: [“us”] segment, which leaves other Region 2
    countries without an explicit SSB entry above the CW band).
  3. Update the existing test for modeForFrequency(14140, { ituRegion: 2 }) — it currently expects ‘SSB’ but should expect ‘CW’ after the fix.

Happy to raise a PR against ham2k/lib-operation-data if that would be helpful. Just wanted to check first rather than duplicate any work already in
progress.

73 de Chris, 2E0FRU