Форк репозитария VBart для meshcoretel.ru с моими добавками

Andy Shinn fb726e48c2 Allows us to have custom PlatformIO envs and configs (#2234) 4 mēneši atpakaļ
.devcontainer 0ac33479d3 fix: update devcontainer features to use node instead of bun 4 mēneši atpakaļ
.github bcfe001370 Have our github PR sanity check also run against main and dev for every merge 5 mēneši atpakaļ
.vscode 6c7efdd0f6 Initial commit 1 gadu atpakaļ
arch 1a3f7a7ea9 Fix BLE semaphore leak in Bluefruit library 8 mēneši atpakaļ
bin 13bc6e4178 setup automated firmware builds with github actions 1 gadu atpakaļ
boards f6cfed66b3 add heltec_mesh_node_t096 board. 4 mēneši atpakaļ
docs 856df241ee Merge pull request #2138 from MGJ520/dev_GAT562_Mesh_Watch13 4 mēneši atpakaļ
examples 08de3fb01f Make sendNodeDiscoverReq() public for post-boot discovery 4 mēneši atpakaļ
include 6c7efdd0f6 Initial commit 1 gadu atpakaļ
lib 03458269ac moved nrf sdk headers to ./lib/ and added Repeater envs for t114 & t-echo 1 gadu atpakaļ
logo 22058c0ee5 add logo files 1 gadu atpakaļ
src 27f732653b Added RAK12035 Soil Moisture and Temperature Sensor (#2223) 4 mēneši atpakaļ
variants 0afd5a9336 Merge pull request #2244 from jirogit/fix/generic-espnow-advert-name 4 mēneši atpakaļ
.clang-format 4e2786c516 Re-applying 73a7a96, formatting, MyMesh reformat 1 gadu atpakaļ
.envrc 21564ae494 add default.nix/.envrc for automagic platformio dev environment on NixOS 1 gadu atpakaļ
.gitignore fb726e48c2 Allows us to have custom PlatformIO envs and configs (#2234) 4 mēneši atpakaļ
CNAME 384e482052 Create CNAME 6 mēneši atpakaļ
CONTRIBUTING.md 42db60bc26 * markdown changes 4 mēneši atpakaļ
README.md 42db60bc26 * markdown changes 4 mēneši atpakaļ
RELEASE.md bb8082d966 add release docs 1 gadu atpakaļ
build.sh 5df139f3d6 update build.sh to support RP2040 and STM32 6 mēneši atpakaļ
build_as_lib.py 0959e64d11 lib_build: add UI_FLAVOR and some cleanup 11 mēneši atpakaļ
create-uf2.py 24ed5b377f added custom pio task "Create UF2 file" 9 mēneši atpakaļ
default.nix 24ef375fc7 default.nix: add python3 to the shell 1 gadu atpakaļ
library.json 7829c51898 Bump to RadioLib 7.6.0 4 mēneši atpakaļ
license.txt e4ec9aec0b * tidy ups 1 gadu atpakaļ
merge-bin.py e58d866949 * merge-bin.py script 1 gadu atpakaļ
mkdocs.yml a87c0fe2d6 separate table of contents 6 mēneši atpakaļ
platformio.ini fb726e48c2 Allows us to have custom PlatformIO envs and configs (#2234) 4 mēneši atpakaļ

README.md

About MeshCore

MeshCore is a lightweight, portable C++ library that enables multi-hop packet routing for embedded projects using LoRa and other packet radios. It is designed for developers who want to create resilient, decentralized communication networks that work without the internet.

🔍 What is MeshCore?

MeshCore now supports a range of LoRa devices, allowing for easy flashing without the need to compile firmware manually. Users can flash a pre-built binary using tools like Adafruit ESPTool and interact with the network through a serial console. MeshCore provides the ability to create wireless mesh networks, similar to Meshtastic and Reticulum but with a focus on lightweight multi-hop packet routing for embedded projects. Unlike Meshtastic, which is tailored for casual LoRa communication, or Reticulum, which offers advanced networking, MeshCore balances simplicity with scalability, making it ideal for custom embedded solutions., where devices (nodes) can communicate over long distances by relaying messages through intermediate nodes. This is especially useful in off-grid, emergency, or tactical situations where traditional communication infrastructure is unavailable.

⚡ Key Features

  • Multi-Hop Packet Routing
    • Devices can forward messages across multiple nodes, extending range beyond a single radio's reach.
    • Supports up to a configurable number of hops to balance network efficiency and prevent excessive traffic.
    • Nodes use fixed roles where "Companion" nodes are not repeating messages at all to prevent adverse routing paths from being used.
  • Supports LoRa Radios – Works with Heltec, RAK Wireless, and other LoRa-based hardware.
  • Decentralized & Resilient – No central server or internet required; the network is self-healing.
  • Low Power Consumption – Ideal for battery-powered or solar-powered devices.
  • Simple to Deploy – Pre-built example applications make it easy to get started.

🎯 What Can You Use MeshCore For?

  • Off-Grid Communication: Stay connected even in remote areas.
  • Emergency Response & Disaster Recovery: Set up instant networks where infrastructure is down.
  • Outdoor Activities: Hiking, camping, and adventure racing communication.
  • Tactical & Security Applications: Military, law enforcement, and private security use cases.
  • IoT & Sensor Networks: Collect data from remote sensors and relay it back to a central location.

🚀 How to Get Started

For developers;

The Simple Secure Chat example can be interacted with through the Serial Monitor in Visual Studio Code, or with a Serial USB Terminal on Android.

⚡️ MeshCore Flasher

We have prebuilt firmware ready to flash on supported devices.

  • Launch https://flasher.meshcore.co.uk
  • Select a supported device
  • Flash one of the firmware types:
    • Companion, Repeater or Room Server
  • Once flashing is complete, you can connect with one of the MeshCore clients below.

📱 MeshCore Clients

Companion Firmware

The companion firmware can be connected to via BLE, USB or WiFi depending on the firmware type you flashed.

Repeater and Room Server Firmware

The repeater and room server firmwares can be setup via USB in the web config tool.

They can also be managed via LoRa in the mobile app by using the Remote Management feature.

🛠 Hardware Compatibility

MeshCore is designed for devices listed in the MeshCore Flasher

📜 License

MeshCore is open-source software released under the MIT License. You are free to use, modify, and distribute it for personal and commercial projects.

Contributing

Please submit PR's using 'dev' as the base branch! For minor changes just submit your PR and we'll try to review it, but for anything more 'impactful' please open an Issue first and start a discussion. Is better to sound out what it is you want to achieve first, and try to come to a consensus on what the best approach is, especially when it impacts the structure or architecture of this codebase.

Here are some general principals you should try to adhere to:

  • Keep it simple. Please, don't think like a high-level lang programmer. Think embedded, and keep code concise, without any unnecessary layers.
  • No dynamic memory allocation, except during setup/begin functions.
  • Use the same brace and indenting style that's in the core source modules. (A .clang-format is prob going to be added soon, but please do NOT retroactively re-format existing code. This just creates unnecessary diffs that make finding problems harder)

Help us prioritize! Please react with thumbs-up to issues/PRs you care about most. We look at reaction counts when planning work.

Road-Map / To-Do

There are a number of fairly major features in the pipeline, with no particular time-frames attached yet. In very rough chronological order:

  • [X] Companion radio: UI redesign
  • [X] Repeater + Room Server: add ACL's (like Sensor Node has)
  • [X] Standardise Bridge mode for repeaters
  • Repeater/Bridge: Standardise the Transport Codes for zoning/filtering
  • [X] Core + Repeater: enhanced zero-hop neighbour discovery
  • Core: round-trip manual path support
  • Companion + Apps: support for multiple sub-meshes (and 'off-grid' client repeat mode)
  • Core + Apps: support for LZW message compression
  • Core: dynamic CR (Coding Rate) for weak vs strong hops
  • Core: new framework for hosting multiple virtual nodes on one physical device
  • V2 protocol spec: discussion and consensus around V2 packet protocol, including path hashes, new encryption specs, etc

📞 Get Support

  • Report bugs and request features on the GitHub Issues page.
  • Find additional guides and components on my site.
  • Join MeshCore Discord to chat with the developers and get help from the community.