[Feature request] Dual radio support
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- c
- Domain
- embedded-iot, networking
Research direction
Start by identifying how MeshCore configures radio hardware and selects frequencies for companion and router transmissions; the issue names SX1280 and dual-radio support but gives no files or tests to follow. Clarify the switching and fallback behavior for dense and low-traffic environments, then define tests for those scenarios before implementation.
Written by the indexing model from the issue text.
Description
Dear Meshcore Enthusiasts,
as meshcore is very crowded in dense areas and SX1280 exists, the following proposal:
- add the option for dual radio
companion:
- In dense areas first send with 2.4GHz (companion) and only if there is no repeat heard switch to lower frequency
- In low traffic areas allow to send directly with lower frequency
router:
- allow for dual radio
- In high traffic situtation use 2.4GHz for near-field communication with companions and high capacity link of traffic to other repeaters
- fallback to lower frequencies for long range DMs or in low traffic environments
- Dominant language
- C
- Stars
- 3.9k
- Forks
- 1.5k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 25
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
-
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
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
containers/crun#2415 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
zephyrproject-rtos/zephyr#123423 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
dspromote: /etc/exports uses -alldirs on non-mount-point directories, so mountd exports nothingOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
nextbsd/nextbsd-userland#434 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day