diff options
| author | mrfaptastic <12006953+mrfaptastic@users.noreply.github.com> | 2020-09-06 17:33:39 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-09-06 17:33:39 +0100 |
| commit | 30be56c293132c7aedf4d1f712739a8ddce17ace (patch) | |
| tree | b8bd4f68d65039ad2e87e4fe88469da815015fb2 | |
| parent | c3abd53704a79e392f228fa52211027fc41c7033 (diff) | |
Update README.md
| -rw-r--r-- | README.md | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -105,9 +105,9 @@ Resolutions beyond 128x128 are likely to result in crashes due to memory constra  -## Setting 'Brightness' and Panel Ghosting +## Panel Brightness -By default you don't need to change / set the brightness setting. However, if you do need to this can be changed by calling `setPanelBrightness(XX)` and then `clearScreen()`. +By default you should not need to change / set the brightness setting as the default value (16) is sufficent for most purposes. Brightness can be changed by calling `setPanelBrightness(XX)` and then `clearScreen()`. The value to pass 'setPanelBrightness' must be a value less than MATRIX_WIDTH. For example for a single 64x32 LED Matrix Module, a value less than 64. However, if you set the brightness too high, you may experience ghosting. @@ -123,7 +123,7 @@ void setup() { } ``` -Summary: setPanelBrightness(xx) value can be any number from 0 (display off) to MATRIX_WIDTH-1. So if you are chaining multiple 64x32 panels, then this value may actually be > 64 (or you will have a dim display). +Summary: setPanelBrightness(xx) value can be any number from 0 (display off) to MATRIX_WIDTH-1. So if you are chaining multiple 64x32 panels, then this value may actually be > 64 (or you will have a dim display). Changing the brightness will have a huge impact on power usage.  |
