[Feature proposal] Radio spectrum visualization
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- embedded-iot
Research direction
Read the linked spectrum-stream companion firmware branch and the Meshcore-Open spectrum demo sources to understand the RSSI sweep, firmware changes, and protocol changes being proposed. The issue presents this as a tech demo for evaluating a feature, with no settled implementation scope or acceptance criteria. Done would need to be defined after the project evaluates the proposal.
Written by the indexing model from the issue text.
Description
Hi :)
I'v been playing with SX126x internals for a while, and I have some progress that I'd like to share.
I implemented a fast RSSI sweep that can be used for searching LoRa transmissions and generally for spectrum visualizations.
It can be ported to any device having a mainstream SX126x radio, so I think, hardware support is wide enough to have this feature in a main branch.
A branch with a companion patch is here: https://github.com/sleeply4cat/MeshCore/tree/spectrum-stream
A demo Meshcore-Open app sources with a spectrum viewer is here: https://github.com/sleeply4cat/meshcore-open/tree/spectrum-demo
Alternatively, it's possible to connect from a browser using page that I attached. You may need to enable experimental platform features in your browser flags to access bluetooth api.
It's a tech demo, pointing to evaluate relatively small changes in a companion firmware and protocol allowing this feature implementation, not a MeshCore-open patch. But picky comments are welcome anyway :)
Also, I can share pre-built apk and fw via any acceptable way if it's allowed.
And yes, it's AI-assisted ;)
Finally, what does it look like:
Browser: https://youtu.be/8xdYArmG_Bc
Mobile:
- 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
-
[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
-
area:docs help wanted type:enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day