Christopher Van HooseandClaude Fable 5
08c9f2b822
North was wrong on hardware, and the device's own saved state said why. Its stored centre was (-0.3875, -3.465) where four measured headings put the true centre at (-0.340, -3.378): out by 0.099 G against a horizontal field of only 0.27 G. Replaying the measured readings through that centre gives -1 deg of error at north, -12 at east, -18 at south and +22 at west -- errors that swing with direction, which is a wrong centre, not a wrong formula. align and mirror were both 0, so the axis mapping was doing its job. Min/max midpoints only find the centre from a COMPLETE sweep and are skewed by whichever extreme was missed; with a bias ~7x the field here, a tenth of a Gauss of skew is a third of the whole signal. Calibration now fits the sphere that the samples actually lie on -- |p - c|^2 = r^2 is linear in (c, r^2-|c|^2), so it is a 4x4 solve over running sums with no sample storage, which matters inside a 256 KB app heap. Coordinates are accumulated relative to the first sample because Lua here is single-precision and squaring raw values near 3.5 G throws away the precision the fit depends on. The fit is checked before it is saved: a singular system (a flat spin, where the centre is undetermined along z) or a radius outside Earth's 0.25-0.65 G band is refused with a reason, leaving the previous calibration alone -- the old code would happily save the garbage. The toast now reports the fitted field strength, which is the number that says whether a calibration is any good, and the progress line shows the sample count. Also adds a D key: the calibration in use, the raw vector, the horizontal components and the stored align/mirror, so a wrong heading can be read off the screen instead of guessed at. Harness: the fit recovers a simulated bias exactly, and a flat-only spin is refused without touching the saved values. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
A real touchscreen UI for your mesh radio. · open source · GPL-3.0
Touch-UI MeshCore companion-radio firmware for the LilyGo T-Deck / T-Deck Plus, Heltec V4 + TFT and eight other boards (ESP32-S3).
An LVGL touch UI — map, chat, contacts, channels, settings — split out of
meshcomod. The app depends on a
MeshCore fork via PlatformIO lib_deps.
Boards
See DEVICES.md for the full support matrix, install paths and per-board status.
- LilyGo T-Deck / T-Deck Plus — env
LilyGo_TDeck_companion_radio_touch(stable) - Heltec V4 + TFT + CHSC6x touch — env
heltec_v4_tft_companion_radio_usb_tcp_touch(stable) - Tanmatsu (ESP32-P4) — built from
tanmatsu/(ESP-IDF), ships via the Tanmatsu app store — sideload guide for running your own build - Elecrow ThinkNode M9 — env
ThinkNode_M9_companion_radio_touch(beta) — keyboard & d-pad guide - RAK WisMesh Tap V2 (RAK3312) — env
rak_tap_v2_companion_radio_touch(beta) - LilyGo T-Lora Pager — envs
tlora_pager_lr1121_companion_radio_touch/tlora_pager_sx1262_companion_radio_touch(stable) — keyboard shortcuts - Heltec V4-R8 + Expansion Kit V2 — env
heltec_v4_r8_tft_companion_radio_usb_tcp_touch(stable) - LilyGo T-Display P4 — built from
tdisplay_p4/(ESP-IDF); AMOLED by default,WADA_P4_LCD=1for the TFT-LCD SKU - Attaky Mesh Series — env
attaky_mesh_series_companion_radio_touch(beta)
Architecture
This repo holds only the app: the companion_radio glue, the ui-touch
LVGL UI, each board's glue/variants, and platformio.ini. The MeshCore
core is not vendored here — it's pulled as a library via lib_deps from the
ALLFATHER-BV/meshcomod monorepo
(the same repo as the non-touch firmware), pinned by a lean source-only core-*
git tag. The touch-app files this repo owns (TouchPrefsStore, WifiRuntimeStore,
the transports, …) are dropped from the lib via -DMC_VENDORED_TOUCH_APP so they
aren't compiled twice. The build is byte-identical to the original in-tree
meshcomod firmware.
Build
PlatformIO pulls the core fork and all libraries automatically:
pio run -e heltec_v4_tft_companion_radio_usb_tcp_touch # Heltec V4 TFT
pio run -e LilyGo_TDeck_companion_radio_touch # LilyGo T-Deck
# or just `pio run` to build both
Flash with the NVS-preserving 4-component chain (bootloader / partitions /
boot_app0 / firmware at 0x0 / 0x8000 / 0xe000 / 0x10000) so saved Wi-Fi
credentials survive — not a merged image, which 0xFF-pads and wipes NVS.
Contributing
Contributions are welcome — see CONTRIBUTING.md. One topic per PR; inbound contributions are accepted under the project's GPL-3.0 license.
License
GPL-3.0-or-later — see LICENSE. wadamesh is copyleft: anyone who distributes a build or a fork must also make their source available under the GPL. This keeps the UI open and concentrates community effort instead of fragmenting it into closed forks.
wadamesh incorporates and depends on MeshCore (MIT, © Scott Powell / rippleradios.com) and other third-party components — see NOTICE for the full list and their licenses. MeshCore-derived files keep their MIT notices; the combined work is distributed under the GPL (MIT is GPL-compatible). The MeshCore fork that wadamesh builds against stays MIT on purpose, so its Wi-Fi/BLE hooks remain upstreamable to MeshCore.