File: README.freqranges

package info (click to toggle)
hamlib 4.6.5-5
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 17,984 kB
  • sloc: ansic: 262,996; sh: 6,135; cpp: 1,578; perl: 876; makefile: 855; python: 148; awk: 58; xml: 26
file content (20 lines) | stat: -rw-r--r-- 673 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Frequency ranges are being changed to reflect rig capabilities instead of
region restrictions

As of 2020-05-05 the behavior is:

#1 Any range which shows ITU# or TBD has not been modified to this convention
#2 Ranges on the backends are being change to USA/EUR/KOR/TPE/ITR per the
 IC-9700 convention.  So if you see one of those monikers on a rig's freq
 range it should accurately reflect the rig's capabilities.

Note that most rigs will have just USA or USA/EUR models.  Not too many rigs
have more than 2 models but it appears at least Icom is headed that way.

USA - United States of America
EUR - Europe
KOR - Korea
TPE - Japan
ITR - ??
AUS - Australia
CHN - China