ESP32 Display Panel

Unified workspace for the ESP32 display-panel device and the panel protocol work that feeds into it. The active firmware lives in the top-level firmware/, tools/, panels/, and apps/ paths; older panel experiments are preserved under legacy/ with clearer names so they can be mined without cluttering the current device path.

Only test panels and controllers that you own or are explicitly authorized to inspect.

Supported Families

Family	Status	Notes
Hanover	Working reference target	Sends arbitrary 8-pixel-high bitmap frames over 4800 baud RS485.
Mobitec	Working via templates	Sends text by patching known-good captured timelines; arbitrary bitmap output is not supported.
Lumiplan	Active investigation	Logic captures and ESP32 display/bridge experiments are preserved here.

Layout

panels/
  hanover/       protocol notes and adapter entry point
  mobitec/       protocol notes, template notes, and adapter entry point
  lumiplan/      investigation notes and adapter placeholder

firmware/
  esp32-dual-rs485-monitor/       dual-baud sniffer/timeline player
  esp32-lumiplan-display-test/    TFT + RS485 phone/editor experiment

tools/
  bridge/        combined Hanover/Mobitec bridge CLI
  capture/       capture and sigrok analysis helpers
  mobitec/       Mobitec-specific packet/timeline utilities

apps/
  capture-viewer/  browser viewer for decoded capture summaries

legacy/
  esp32-rs485-panel-lab/  former esp32-rs485 repo, minus bulky capture runs
  mobitec-esp32-bridge/   former PlatformIO Mobitec bridge repo
  esp32-mobitec-scratch/  non-Git Mobitec scripts and firmware sketches

data/
  captures/lumiplan/  raw Lumiplan captures and analysis notes

docs/
  hardware/      wiring and transceiver guidance
  protocols/     bridge/protocol notes
  getting-started/

Quick Start

Run the protocol round-trip tests:

C:\Users\admin\.platformio\penv\Scripts\python.exe .\tools\bridge\panel_bridge.py self-test

Preview a Hanover frame without hardware:

C:\Users\admin\.platformio\penv\Scripts\python.exe .\tools\bridge\panel_bridge.py send-hanover "SVT Communication" --dry-run

Preview a Mobitec timeline patch without hardware:

C:\Users\admin\.platformio\penv\Scripts\python.exe .\tools\bridge\panel_bridge.py send-mobitec "SVT Communication" --dry-run

Build the current ESP32 Lumiplan/TFT experiment:

cd .\firmware\esp32-lumiplan-display-test
C:\Users\admin\.platformio\penv\Scripts\pio.exe run

Design Direction

The long-term shape is one ESP32 device with a neutral sign editor that renders messages into a common bitmap/timeline model, then hands that model to per-family adapters:

editor project -> renderer -> sign adapter -> firmware/player -> panel

Hanover is the reference adapter because it accepts arbitrary 96x8-style bitmap content. Mobitec stays template/timeline based until we fully understand its native layout protocol. Lumiplan remains capture-led until the bus is confidently identified.