MarekZegare4 149693c928 docs refactor
2026-05-28 10:54:09 +02:00
2025-01-13 14:07:48 +11:00
2026-03-20 15:56:09 +08:00
2026-05-28 10:54:09 +02:00
2026-05-23 23:52:04 +02:00
2025-01-13 14:07:48 +11:00
2025-06-05 20:35:40 +12:00
2026-02-03 13:47:43 +13:00
2026-03-20 10:23:51 +11:00
2026-03-23 14:26:56 +01:00
2025-01-20 10:20:42 +11:00
2025-01-25 23:09:09 +11:00
2026-03-31 00:51:15 +13:00
2026-05-28 10:54:09 +02:00
2025-03-03 18:08:00 +13:00

Plus firmware for Seeed Wio Tracker L1

This branch extends the official MeshCore companion radio firmware for the Seeed Wio Tracker L1.

Join the discussion on the offical MeshCore discord: https://discord.gg/sdhYArU2jr

E-ink case Oled case


Feature highlights

  • Extended language support with native Unicode rendering and input (Lemon font) alongside the original ASCII mode (Default font with transliteration)

  • Messages Screen — view and send messages, open message details, reply with quick messages or custom text, per-channel notification and melody overrides

  • Favourites Dial — pin up to six contacts for quick access from the home screen

  • Settings Screen — configure display, sound, home page order, radio and system settings

  • Clock Screen — view time and date plus up to three configurable sensor values

  • Screen Lock — lock the device to prevent accidental keypresses, with a lock screen showing time and sensor data

  • Tools Screen — GPS trail recording and export, ringtone editor, auto-reply bot, and more

Firmware Variants

Two firmware builds are published with each release:

Variant Display File
OLED SSD1306 / SH1106 128 × 64 WioTrackerL1_companion_dual_*.uf2
E-ink GxEPD2 250 × 122 WioTrackerL1Eink_companion_dual_*.uf2

Both variants are built from a single codebase and share the same feature set. The dual in the filename means a single binary supports both BLE and USB serial — there are no separate BLE/USB builds.

Warning

When migrating from official/custom firmware, backup your data and perform factory reset to prevent conflicts with existing settings and data:

  1. Open device settings in the companion app and download data backup
  2. Go to MeshCore Flasher website
  3. Select "Wio Tracker L1 Pro"
  4. Choose any of the firmware variant
  5. Perform "Erase flash"

Development

This fork tracks the upstream MeshCore repository. To prevent upstream changes from overwriting this README during merges, README.md is protected via .gitattributes. After cloning, run once:

git config merge.ours.driver true

Display Screenshot Tool

Note

The screenshot feature requires the ENABLE_SCREENSHOT build flag to be enabled. Add -D ENABLE_SCREENSHOT to your PlatformIO build flags, then recompile and flash the firmware.

The firmware supports capturing the current display contents and transmitting it over USB serial. This is useful for debugging, remote monitoring, or creating documentation.

Important: When the device is connected to the companion app, the USB serial port is not available for communication. To use the screenshot tool, ensure the device is not connected to the companion app.

Usage:

  1. Build and flash firmware with -D ENABLE_SCREENSHOT build flag enabled

Example for the OLED dual firmware:

PLATFORMIO_BUILD_FLAGS="-D ENABLE_SCREENSHOT" pio run -e WioTrackerL1_companion_dual -t upload
  1. Connect the device to your computer via USB (ensure no companion app connection)

  2. Install dependencies and run the screenshot tool. To manage python and python dependencies, use uv: https://docs.astral.sh/uv/

    cd tools
    uv run tools/screenshot.py
    

    Options:

    • --port PORT — Serial port to use (default: auto-detect)
    • --scale SCALE — Upscale factor for the output image (1=no upscale, 2=2x, 3=3x, 4=4x, etc.; default: 1)
  3. In the tool's interactive menu, press S to capture a screenshot

  4. The tool will save the screenshot as a PNG file in tools/pngs/ with a timestamp-based filename

How it works:

  • The tool sends the CMD_GET_SCREENSHOT command (66) to the device
  • The device responds with RESP_CODE_SCREENSHOT (29) containing the framebuffer data
  • The framebuffer is transmitted in chunks (128×64 display = 1024 bytes, split across multiple frames)
  • The tool reassembles the chunks and converts them to a PNG image
Description
Companion firmware fork — offline GPS navigation (waypoints, compass, GPX export) on top of LoRa mesh messaging.
Readme 14 MiB
Languages
C 60.1%
C++ 37.9%
Python 1.4%
Shell 0.3%
HTML 0.3%