[Feature Request] Add regional frequency preset for South Korea (KR920-923)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- embedded-iot, networking
Research direction
Start by locating the existing regional frequency presets and how their radio parameters are represented. Compare those presets with the proposed KR920 range, center frequency, bandwidth, spreading factor, coding rate, and transmit power. The issue gives no file or test names; done means adding a South Korea preset consistent with the project’s preset conventions and checking its parameter values.
Written by the indexing model from the issue text.
Description
-
Proposed Region Name & Identifier
Region / Country Name: South Korea (KR or KR920)
Intent: Provide out-of-the-box compliance, efficient airtime usage, and ease of use for local South Korean mesh communities without requiring manual frequency calibration. -
Core Radio Parameters (Optimized Technical Array)
Frequency Range: 917.0 MHz – 923.5 MHz
Center Frequency / Channel 0: 921.9 MHz (aligned with standard local sub-band deployment)
Bandwidth (BW): 125 kHz
Spreading Factor (SF): SF7 or SF8 (optimized for lower packet airtime, faster network responsiveness, and strict adherence to local duty cycle/channel occupancy limits)
Coding Rate (CR): 4/5
Max Transmit Power: 10 dBm to 14 dBm (approx. 10mW–25mW EIRP limit compliance) -
Legal Justification & Regulatory Citation
Governing Body: MSIT (Ministry of Science and ICT / 과학기술정보통신부) of South Korea.
Legal Framework: South Korea Radio Waves Act (전파법).
Specific Standard: Technical Standards for Radio Equipment for Radio Stations That Can Be Established Without Notice (신고하지 아니하고 개설할 수 있는 무선국용 무선설비의 기술기준), specifically under RFID/USN and Data Transmission Low-Power Devices.
- Dominant language
- C
- Stars
- 3.9k
- Forks
- 1.5k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 26
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from meshcore-dev/MeshCore
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
meshcore-dev/MeshCore#3622 ·
Maintainers usually reply within 1 day
-
[Feature Request] Set Australia (Mid) Preset to automatically enable 2 byte default path hash sizeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
meshcore-dev/MeshCore#3571 · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
meshcore-dev/MeshCore#3567 · 1 comment ·
Maintainers usually reply within 1 day
-
RTC_RX8130CE writes and reads the one-hot WEEK register as a numberPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
meshcore-dev/MeshCore#3549 ·
Maintainers usually reply within 1 day
-
Repeater: CLI reply to 'setperm <key> 0' is lost when the removed ACL entry sits before the requester (stale ClientInfo* after array shift)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
meshcore-dev/MeshCore#3513 ·
Maintainers usually reply within 1 day
All issues in meshcore-dev/MeshCore
Similar issues
-
v9.6.0: CMake incorrectly enforces presence of libevdevPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
IoTSDK
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Azure/azure-iot-sdk-c#2776 ·
Maintainers usually reply within 2 days
-
[Bug] Unhandled ValueError terminates watchdog thread when GISRC value contains multiple colonsOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug Component component: net
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
RT-Thread/rt-thread#11913 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
contiki-ng/contiki-ng#3289 ·
Maintainers usually reply within 3 days