Repository navigation
feat(render): add an awtrix_mono build for MAX7219 LED module panels - #139
Open
drronnie85 wants to merge 3 commits into
Open
drronnie85 wants to merge 3 commits into
drronnie85 wants to merge 3 commits into
Conversation
Clocks built from chained MAX7219 8x8 modules cannot run the WS2812 driver. The new awtrix_mono environment swaps MatrixRenderer's output for LEDMatrixDriver on the default SPI bus (CS on GPIO 5). The canvas stays full colour: a pixel is lit above a fixed threshold, and brightness drives the chips' intensity register instead of scaling colours, which would push dim pixels under the threshold. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
LEDMatrixDriver fixes SPI at 5 MHz and resends the whole frame every time. On 5 V modules fed from the ESP32's 3.3 V pins that latched single rows wrong now and then, seen as one row blinking on a static picture. A small driver in the renderer runs the bus at AWTRIX_MAX7219_SPI_HZ (1 MHz), sends a row only when it changed and rewrites every register and row once a second, so a module that latched noise recovers on its own. Drops the LEDMatrixDriver dependency. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nged rows" This reverts commit dedb0f1. The row flicker it targeted turned out to be on the power side of the test board (it also showed on AWTRIX 3 and persisted at 1 MHz), so the LEDMatrixDriver version stays as tested. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
A new build environment,
awtrix_mono, for clocks built from chained MAX7219 8×8 LED modules instead of a WS2812 strip.src/media/MatrixRenderer.cpp: underAWTRIX_DISPLAY_MAX7219, the renderer drives LEDMatrixDriver on the default SPI bus (SCK 18, MOSI 23) with CS onAWTRIX_MAX7219_CS_PIN(default 5), one module per 8 columns. The default build is unchanged: the FastLED path is the#elsebranch, byte for byte.mirrorandrotateapply; the other panel settings describe strip wiring and are ignored.pinMatrixis unused.platformio.ini:[env:awtrix_mono]extendsawtrix. Not added to CI or releases.THIRD-PARTY-NOTICES.md,LICENSES/MIT-LEDMatrixDriver.txt, notice exclusion intools/system/components.json.awtrix_monosection indocs/developers/building.md, including the DFPlayer pin overlap (its defaults are GPIO 18/23 too).Why
MAX7219 module chains are a common, cheap way to build a 32×8 clock. A personal AWTRIX 3 fork already drove one through a FastLED_NeoMatrix shim; this brings the same behaviour to NG without touching the portable core.
How it was verified
matrix: MAX7219 x4, CS GPIO 5, and the clock runs the app loop and API normally.pio run -e awtrix_monoandpio run -e awtrixbuild.python tools/system/check_components.pyandpython tools/check_docs_sync.pypass.