Incorrect Patterns + Beginner Questions

[lucas-fern]

I'll preface this by saying this is my first electronics project, so some of the questions I'm asking might be trivial, and some of the stuff I'm doing is probably stupid. Any advice is appreciated and hopefully will be useful to others in a similar position.

I'll start by showing my setup, then some demonstrations of the unexpected behaviour I'm seeing, finally some questions. Hopefully this is written well enough that providing help will be painless for someone with experience 🥰

Products

Products linked to where I purchased them.

• Heltec WiFi ESP32
• 5V 20A Power Supply
• 2m × 144 LED/m WS2812B LED Strip

Setup

(Using Australian 230V power)

Demonstrations

heltecdemo

For this I am expecting to see some kind of rainbow pattern, but instead each LED only lights up as red, green, OR blue, at any given time. Never a combination of multiple colours, though the brightness does vary.

The code for this configuration is unmodified except to change the port, so only the first 144 of my LEDs are active.

strand

This seems to work better, but still not as expected. I took the default strand configuration and updated it for the upload speed of the Heltec board. I also commented out some build_flags and lib_deps which were specific to the m5stick.

With this configuration the LEDs do combine the RGB channels, but instead of scrolling the pattern remains stationary and dims/flickers approx every second.

Code

platformio.ini

Click to Expand

; PlatformIO Project Configuration File
;
;   Build options: build flags, source filter
;   Upload options: custom upload port, speed and extra flags
;   Library options: dependencies, extra library storages
;   Advanced options: extra scripting
;
; Please visit documentation for the other options and examples
; https://docs.platformio.org/page/projectconf.html

[platformio]
data_dir    = ./data
default_envs = strand

[common]
lib_deps        = crankyoldgit/IRremoteESP8266  @ ^2.7.20
                  fastled/FastLED               @ ^3.4.0
                  adafruit/Adafruit BusIO       @ ^1.9.1
                  adafruit/Adafruit GFX Library @ ^1.10.12
                  adafruit/Adafruit ILI9341     @ ^1.5.10                  
                  bblanchon/ArduinoJson         @ ^6.8.14
                  olikraus/U8g2                 @ ^2.28.8
                  joaolopesf/RemoteDebug        @ ^3.0.5
                  kosme/arduinoFFT              @ ^1.5.6
                  me-no-dev/AsyncTCP            @ ^1.1.1
                  thomasfredericks/Bounce2      @ ^2.7.0
                  me-no-dev/ESP Async WebServer @ ^1.2.3
                  Wire                                        ; need because platformio's library dependency finder isn't behaving

[m5stick-c]
lib_deps        = ${common.lib_deps}
                  m5stack/M5StickC     @ ^0.2.3 

[ttgo]
lib_deps        = ${common.lib_deps}
                  https://github.com/Xinyuan-LilyGO/TTGO-T-Display

[m5stick-c-plus]
lib_deps        = ${common.lib_deps}
                  m5stack/M5StickCPlus @ ^0.0.2

[all]
lib_deps        = ${common.lib_deps}
                  ${m5stick-c.lib_deps}
                  ${m5stick-c-plus.lib_deps}

[env]
platform        = espressif32
framework       = arduino
build_type      = debug
build_unflags   = -std=gnu++11

lib_deps        = ${common.lib_deps}
lib_extra_dirs = ${PROJECT_DIR}/lib

; This partition table attempts to fit everything in 4M of flash.
board_build.partitions = partitions_custom.csv

monitor_filters = esp32_exception_decoder

[env:all-deps]
lib_deps      =  ${all.lib_deps}

[env:demo]
board         = esp32dev
monitor_speed = 115200
upload_speed  = 921600
upload_port   = COM7                    ; This will vary by machine
build_flags   = -DDEMO=1
                -std=gnu++17
                -Ofast 

[env:wrover-demo]
board           = esp-wrover-kit
monitor_speed   = 115200
upload_speed    = 1500000
build_flags     = -DWROVERKIT=1
                  -DDEBUG=1
                  -DUSE_SCREEN=1
                  -DUSE_PSRAM=0
                  -DBOARD_HAS_PSRAM=0
                  -std=gnu++17
                  -Ofast 
                  -mfix-esp32-psram-cache-issue
build_type      = debug
upload_port     = COM10
debug_tool      = ftdi
upload_protocol = ftdi
debug_init_break = 
;upload_protocol = ftdi

[env:ledstrip]
board         = heltec_wifi_kit_32
monitor_speed = 115200
upload_speed  = 921600
upload_port   = COM13                   ; This will vary by machine
build_flags   = -DLEDSTRIP=1
                -DUSE_SCREEN=1
                -std=gnu++17
                -Ofast 

; This is the basic DEMO project, but expanded to work on the M5, which means it can draw to 
; the built in LCD.  It's made so that you can connect to the small 4-pin connector on the M5,
; so it sends power and ground as well as data on PIN 32.

[env:m5demo]
platform      = espressif32wn
board         = m5stick-c
upload_speed  = 1500000
monitor_speed = 115200
upload_port   = COM23                   ; This will vary by machine
build_flags   = -DDEMO=1
                -DUSE_SCREEN=1
                -std=gnu++17
                -Ofast 
lib_deps      = ${m5stick-c.lib_deps}

; This is largely the same as the m5demo above except it links to the PLUS version of the lib
; and defines M5STICKCPLUS=1 

[env:m5plusdemo]
platform      = espressif32
board         = m5stick-c
upload_speed  = 1500000
monitor_speed = 115200
upload_port   = COM4                   ; This will vary by machine
build_flags   = -DDEMO=1
                -DM5STICKCPLUS=1
                -DUSE_SCREEN=1
                -std=gnu++17
                -Ofast 
lib_deps      = ${m5stick-c-plus.lib_deps}

; For low-density setups like a strand of Christmas lights

[env:strand]
platform      = espressif32
board         = heltec_wifi_kit_32
monitor_speed = 115200
upload_speed  = 921600
upload_port   = COM3                   ; This will vary by machine
build_flags   = -DSTRAND=1
;                 -DM5STICKCPLUS=1
                -DUSE_SCREEN=1
                -std=gnu++17
                -Ofast 
; lib_deps      = ${m5stick-c-plus.lib_deps}

[env:heltecdemo]
board         = heltec_wifi_kit_32
monitor_speed = 115200
upload_speed  = 921600
upload_port   = COM3
monitor_port  = COM3
build_flags   = -DDEMO=1
                -DUSE_SCREEN=1
                -std=gnu++17
                -Ofast 

[env:heltecv2demo]                     ; V2 board has 8M flash
board = heltec_wifi_kit_32_v2
monitor_speed = 115200
upload_speed  = 921600
upload_port   = COM3
monitor_port  = COM3
build_flags   = -DDEMO=1
                -DUSE_SCREEN=1
                -std=gnu++17
                -Ofast 

[env:spectrum]
board         = m5stick-c                    ; Requires the M5 Stick C Plus (note the Plus)
upload_speed  = 1500000
monitor_speed = 115200
upload_port   = COM4
build_flags   = -DM5STICKCPLUS=1
                -DUSE_SCREEN=1
                -DSPECTRUM=1
                -D_IR_ENABLE_DEFAULT_=false  ; don't automatically include every remote control decoder
                -DDECODE_NEC=true            ; enable whichever you need for your remote.  Try not disabling above to figure out which it is.
                -std=gnu++17
                -Ofast 
lib_deps      = ${m5stick-c-plus.lib_deps}

[env:spectrumlite]                            ; Sane as SPECTRUM but required a non-Plus M5 Stick
board         = m5stick-c
upload_speed  = 1500000
monitor_speed = 115200
upload_port   = COM15
build_flags   = -DM5STICKC=1
                -DUSE_SCREEN=1
                -DSPECTRUM=1
                -D_IR_ENABLE_DEFAULT_=false  ; don't automatically include every remote control decoder
                -DDECODE_NEC=true            ; enable whichever you need for your remote.  Try not disabling above to figure out which it is.
                -std=gnu++17
                -Ofast 
lib_deps      = ${m5stick-c.lib_deps}

[env:ttgo]
board         = esp32dev
upload_speed  = 1500000
monitor_speed = 115200
upload_port   = COM14
build_flags   = -DTTGO=1
                -DUSE_SCREEN=1
                -D_IR_ENABLE_DEFAULT_=false  ; don't automatically include every remote control decoder
                -DDECODE_NEC=true            ; enable whichever you need for your remote.  Try not disabling above to figure out which it is.
                -std=gnu++17
                -Ofast 
lib_deps      = ${ttgo.lib_deps}

[env:xmastrees]
board         = m5stick-c
upload_speed  = 1500000
monitor_speed = 115200
upload_port   = COM11
build_flags   = -DM5STICKCPLUS=1
                -DUSE_SCREEN=1
                -DXMASTREES=1
                -D_IR_ENABLE_DEFAULT_=false  ; don't automatically include every remote control decoder
                -DDECODE_NEC=true            ; enable whichever you need for your remote.  Try not disabling above to figure out which it is.
                -std=gnu++17
                -Ofast 
lib_deps      = ${m5stick-c-plus.lib_deps}

[env:treeset]
board         = m5stick-c
upload_speed  = 1500000
monitor_speed = 115200
upload_port   = COM11
build_flags   = -DM5STICKCPLUS=1
                -DUSE_SCREEN=1
                -DTREESET=1
                -D_IR_ENABLE_DEFAULT_=false  ; don't automatically include every remote control decoder
                -DDECODE_NEC=true            ; enable whichever you need for your remote.  Try not disabling above to figure out which it is.
                -std=gnu++17
                -Ofast 
lib_deps      = ${m5stick-c-plus.lib_deps}

[env:insulators]
board         = m5stick-c
upload_speed  = 1500000
monitor_speed = 115200
upload_port   = COM23
build_flags   = -DM5STICKC=1
                -DUSE_SCREEN=1
                -DINSULATORS=1
                -std=gnu++17
                -Ofast 
lib_deps      = ${m5stick-c.lib_deps}



[env:magicmirror]
board         = m5stick-c
upload_speed  = 1500000
monitor_speed = 115200
upload_port   = COM21
build_flags   = -DM5STICKC=1
                -DUSE_SCREEN=1
                -DMAGICMIRROR=1
                -std=gnu++17
                -Ofast                 
lib_deps      = ${m5stick-c.lib_deps}
                

[env:atomlight]
board         = heltec_wifi_kit_32
monitor_speed = 115200
upload_speed  = 921600
upload_port   = COM10
build_flags   = -DATOMLIGHT=1
                -std=gnu++17
                -Ofast 

[env:brooklynroom]
board         = heltec_wifi_kit_32
monitor_speed = 115200
upload_speed  = 921600
upload_port   = COM10
build_flags   = -DBROOKLYNROOM=1
                -std=gnu++17
                -Ofast 

[env:fanset]
board         = m5stick-c
upload_speed  = 1500000
monitor_speed = 115200
upload_port   = COM3
build_flags   = -DM5STICKC=1
                -DUSE_SCREEN=1
                -DFANSET=1
                -std=gnu++17
                -Ofast 
lib_deps      = ${m5stick-c.lib_deps}

[env:atomi]
board         = heltec_wifi_kit_32
upload_port   = /dev/cu.SLAB_USBtoUART
upload_speed  = 921600
build_flags   = -DATOMISTRING=1 
                -DHELTEC=1
                -DUSE_SCREEN=1
                -std=gnu++17
                -Ofast 

[env:cube]
board         = m5stick-c
upload_speed  = 1500000
monitor_speed = 115200
upload_port   = COM6
build_flags   = -DM5STICKCPLUS=1
                -DUSE_OLED=1
                -DCUBE=1
                -std=gnu++17
                -Ofast 
lib_deps      = ${m5stick-c-plus.lib_deps}

globals.h

I've only included the STRAND section since this is the only one I modified. I increased the matrix width and changed the power limit for my power supply (though not sure if I got this right)

Click to Expand

#elif STRAND


    // This is a simple demo configuration.  To build, simply connect the data lead from a WS2812B
    // strip to pin 5.  This does not use the OLED, LCD, or anything fancy, it simply drives the
    // LEDs with a simple rainbow effect as specified in effects.cpp for DEMO.
    //
    // Please ensure you supply sufficent power to your strip, as even the DEMO of 144 LEDs, if set
    // to white, would overload a USB port.

    #define MATRIX_WIDTH            (2*144)  // Was 144
    #define MATRIX_HEIGHT           1
    #define NUM_LEDS                (MATRIX_WIDTH*MATRIX_HEIGHT)
    #define NUM_CHANNELS            1
    #define NUM_RINGS               5
    #define RING_SIZE_0             24
    #define ENABLE_AUDIO            1

    #define POWER_LIMIT_MW          20000*5   // 20A 5V Power Supply - Was 1000

    // Once you have a working project, selectively enable various additional features by setting
    // them to 1 in the list below.  This DEMO config assumes no audio (mic), or screen, etc.

    #define ENABLE_WIFI             0   // Connect to WiFi
    #define INCOMING_WIFI_ENABLED   0   // Accepting incoming color data and commands
    #define TIME_BEFORE_LOCAL       0   // How many seconds before the lamp times out and shows local contexnt
    #define ENABLE_NTP              0   // Set the clock from the web
    #define ENABLE_OTA              0   // Accept over the air flash updates

    #if M5STICKC || M5STICKCPLUS
        #define LED_PIN0 32
    #else
        #define LED_PIN0 5
    #endif

    // The webserver serves files from its SPIFFS filesystem, such as index.html, and those files must be
    // uploaded to SPIFFS with the "Upload Filesystem Image" command before it can work.  When running
    // you should be able to see/select the list of effects by visiting the chip's IP in a browser.  You can
    // get the chip's IP by watching the serial output or checking your router for the DHCP given to 'LEDWifi'

    #define ENABLE_WEBSERVER        0   // Turn on the internal webserver

    #define TOGGLE_BUTTON_1         37
    #define TOGGLE_BUTTON_2         39
    #define NUM_INFO_PAGES          2

Questions

1. How should I resolve the unexpected behaviour with the demo configurations I have tried?
2. What is the expected behaviour? I've found it pretty hard to find any documentation for this project? is there anything other than the README?
3. Do I require other components in my circuit? For safety? To make it function? or otherwise?
4. Are there other elements of the code that I needed to modify before expecting the demo to work (I did set WiFi details in secrets.h and that works when enabled.)
5. What do the parameters NUM_RINGS and RING_SIZE_0 do? And are there others that aren't obvious that I should understand?

Thanks for reading and for any assistance ❤

[Zacharandir]

I can answer question 5. The ring parameters are for using LED rings or looped strips (such as fans) for example if you had 5 fans in a row with 24 LEDs each setting those with NUM_RINGS AND RING_SIZE_0 would make them draw in synch and allow them to show effects across multiple rings. In your case your NUM_RINGS would be set to 0 (or you can comment it out all together) since you just have a single straight strip.

[rbergen]

I can answer question 2, at least with regards to the availability of documentation. It's basically a case of "what you see is what you get". Phrased differently, Dave published the project "as-is with a README".
The project was published to share it with the world, but also to open it up to the contributions of others. In that context, contributions of additional documentation by the community would be most welcome and highly appreciated.

[Zacharandir]

Probably not the best place for it, but have you come across how physical buttons are handled? I see a couple of defines relating to denouncing in main.cpp but have been unable to figure out where the code is that handles on a button press.

[LarryXO]

Perhaps we're going about this in the wrong way. Would someone who has a working Heltec V2 board please post their OS, platformio.ini, and globals.h?