Hello MeshCore Team,
I am drafting a proposal and tracking issue for a significant architectural experiment I plan to undertake. I want to introduce the ability to script new functionality and live-update nodes entirely Over-The-Air (OTA). This would allow a MeshCore client to dynamically adapt its behavior to almost any imagined use case without requiring a full firmware re-flash over USB.
The Plan
- The Target Environment: I will be re-purposing a few of my DIY FakeTec nodes (nRF52840 + Heltec HT-RA62/SX1262) currently running in my Meshtastic network.
- The Execution: I plan to dedicate a private MeshCore channel named
mecrisp exclusively to handle these interactive scripting payloads.
- The Language Layer: The core MeshCore stack and the low-level LoRa radio interface on these nodes will be entirely implemented and exposed via Mecrisp (Mecrisp-Stellaris Forth).
Hardware Constraints
Don't worry—I have no intention of breaking the airwaves. I plan to strictly retain and respect all underlying low-level hardware and regional regulatory constraints for the LoRa radio (duty cycles, bandwidth limits, and power ceilings) within the Forth environment.
Community Feedback Welcome
I know this is a highly unconventional and ambitious approach to mesh firmware. Feel free to wish me luck, warn me of the architectural dragons ahead, criticize the approach, or even make fun of it! All technical comments, ideas, and pushback are warmly welcomed.
--
Kind regards,
c-:
PS: If anyone has already attempted to map a Forth interactive loop over an asymmetric, packet-based LoRa link, I would love to hear about your edge cases!
Hello MeshCore Team,
I am drafting a proposal and tracking issue for a significant architectural experiment I plan to undertake. I want to introduce the ability to script new functionality and live-update nodes entirely Over-The-Air (OTA). This would allow a MeshCore client to dynamically adapt its behavior to almost any imagined use case without requiring a full firmware re-flash over USB.
The Plan
mecrispexclusively to handle these interactive scripting payloads.Hardware Constraints
Don't worry—I have no intention of breaking the airwaves. I plan to strictly retain and respect all underlying low-level hardware and regional regulatory constraints for the LoRa radio (duty cycles, bandwidth limits, and power ceilings) within the Forth environment.
Community Feedback Welcome
I know this is a highly unconventional and ambitious approach to mesh firmware. Feel free to wish me luck, warn me of the architectural dragons ahead, criticize the approach, or even make fun of it! All technical comments, ideas, and pushback are warmly welcomed.
--
Kind regards,
c-:
PS: If anyone has already attempted to map a Forth interactive loop over an asymmetric, packet-based LoRa link, I would love to hear about your edge cases!