ua1zbe/MeshCore-RelayRadio
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Add MeshCore relay_radio firmware for Heltec T114
Some checks failed
Build and deploy Docs site to GitHub Pages / github-pages (push) Has been cancelled
Details
Run Unit Tests / test (push) Has been cancelled
Details
PR Build Check / build (Heltec_v3_companion_radio_ble) (push) Has been cancelled
Details
PR Build Check / build (Heltec_v3_repeater) (push) Has been cancelled
Details
PR Build Check / build (Heltec_v3_room_server) (push) Has been cancelled
Details
PR Build Check / build (LilyGo_Tlora_C6_repeater_) (push) Has been cancelled
Details
PR Build Check / build (PicoW_repeater) (push) Has been cancelled
Details
PR Build Check / build (RAK_4631_companion_radio_ble) (push) Has been cancelled
Details
PR Build Check / build (RAK_4631_repeater) (push) Has been cancelled
Details
PR Build Check / build (RAK_4631_room_server) (push) Has been cancelled
Details
PR Build Check / build (Tbeam_SX1276_repeater) (push) Has been cancelled
Details
PR Build Check / build (wio-e5-mini_repeater) (push) Has been cancelled
Details
PR Build Check / build (wio_wm1110_repeater) (push) Has been cancelled
Details

Browse Source
This commit is contained in:
ua1zbe
2026-06-09 15:36:22 +03:00
commit cdd9d32fb5
787 changed files with 108699 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
docs/number_allocations.md Normal file
View File

@@ -0,0 +1,22 @@
# Number Allocations
This document lists unique numbers/identifiers used in various MeshCore protocol payloads.
# Group Data Types
The `PAYLOAD_TYPE_GRP_DATA` payloads have a 16-bit data-type field, which identifies which application the packet is for.
To make sure multiple applications can function without interfering with each other, the table below is for reserving various ranges of data-type values. Just modify this table, adding a row, then submit a PR to have it authorised/merged.
NOTE: the range FF00 - FFFF is for use while you're developing, doing POC, and for these you don't need to request to use/allocate.
Once you have a working app/project, you need to be able to demonstrate it exists/works, and THEN request type IDs. So, just use the testing/dev range while developing, then request IDs before you transition to publishing your project.
| Data-Type range | App name | Contact |
|-----------------|-----------------------------|-------------------------------------------------------------------|
| 0000 - 00FF | -reserved for internal use- | |
| 0100 | MeshCore Open | zsylvester@monitormx.com — https://github.com/zjs81/meshcore-open |
| 0110 - 011F | Ripple | ripple_biz@protonmail.com — https://buymeacoffee.com/ripplebiz |
| FF00 - FFFF | -reserved for testing/dev- | |
(add rows, inside the range 0100 - FEFF for custom apps)