init

.gitignore

@@ -0,0 +1,5 @@
+.pio
+.vscode/.browse.c_cpp.db*
+.vscode/c_cpp_properties.json
+.vscode/launch.json
+.vscode/ipch

.travis.yml

@@ -0,0 +1,67 @@
+# Continuous Integration (CI) is the practice, in software
+# engineering, of merging all developer working copies with a shared mainline
+# several times a day < https://docs.platformio.org/page/ci/index.html >
+#
+# Documentation:
+#
+# * Travis CI Embedded Builds with PlatformIO
+#   < https://docs.travis-ci.com/user/integration/platformio/ >
+#
+# * PlatformIO integration with Travis CI
+#   < https://docs.platformio.org/page/ci/travis.html >
+#
+# * User Guide for `platformio ci` command
+#   < https://docs.platformio.org/page/userguide/cmd_ci.html >
+#
+#
+# Please choose one of the following templates (proposed below) and uncomment
+# it (remove "# " before each line) or use own configuration according to the
+# Travis CI documentation (see above).
+#
+
+
+#
+# Template #1: General project. Test it using existing `platformio.ini`.
+#
+
+# language: python
+# python:
+#     - "2.7"
+#
+# sudo: false
+# cache:
+#     directories:
+#         - "~/.platformio"
+#
+# install:
+#     - pip install -U platformio
+#     - platformio update
+#
+# script:
+#     - platformio run
+
+
+#
+# Template #2: The project is intended to be used as a library with examples.
+#
+
+# language: python
+# python:
+#     - "2.7"
+#
+# sudo: false
+# cache:
+#     directories:
+#         - "~/.platformio"
+#
+# env:
+#     - PLATFORMIO_CI_SRC=path/to/test/file.c
+#     - PLATFORMIO_CI_SRC=examples/file.ino
+#     - PLATFORMIO_CI_SRC=path/to/test/directory
+#
+# install:
+#     - pip install -U platformio
+#     - platformio update
+#
+# script:
+#     - platformio ci --lib="." --board=ID_1 --board=ID_2 --board=ID_N

.vscode/extensions.json

@@ -0,0 +1,7 @@
+{
+    // See http://go.microsoft.com/fwlink/?LinkId=827846
+    // for the documentation about the extensions.json format
+    "recommendations": [
+        "platformio.platformio-ide"
+    ]
+}

include/README

@@ -0,0 +1,39 @@
+
+This directory is intended for project header files.
+
+A header file is a file containing C declarations and macro definitions
+to be shared between several project source files. You request the use of a
+header file in your project source file (C, C++, etc) located in `src` folder
+by including it, with the C preprocessing directive `#include'.
+
+```src/main.c
+
+#include "header.h"
+
+int main (void)
+{
+ ...
+}
+```
+
+Including a header file produces the same results as copying the header file
+into each source file that needs it. Such copying would be time-consuming
+and error-prone. With a header file, the related declarations appear
+in only one place. If they need to be changed, they can be changed in one
+place, and programs that include the header file will automatically use the
+new version when next recompiled. The header file eliminates the labor of
+finding and changing all the copies as well as the risk that a failure to
+find one copy will result in inconsistencies within a program.
+
+In C, the usual convention is to give header files names that end with `.h'.
+It is most portable to use only letters, digits, dashes, and underscores in
+header file names, and at most one dot.
+
+Read more about using header files in official GCC documentation:
+
+* Include Syntax
+* Include Operation
+* Once-Only Headers
+* Computed Includes
+
+https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html

lib/README

@@ -0,0 +1,46 @@
+
+This directory is intended for project specific (private) libraries.
+PlatformIO will compile them to static libraries and link into executable file.
+
+The source code of each library should be placed in a an own separate directory
+("lib/your_library_name/[here are source files]").
+
+For example, see a structure of the following two libraries `Foo` and `Bar`:
+
+|--lib
+|  |
+|  |--Bar
+|  |  |--docs
+|  |  |--examples
+|  |  |--src
+|  |     |- Bar.c
+|  |     |- Bar.h
+|  |  |- library.json (optional, custom build options, etc) https://docs.platformio.org/page/librarymanager/config.html
+|  |
+|  |--Foo
+|  |  |- Foo.c
+|  |  |- Foo.h
+|  |
+|  |- README --> THIS FILE
+|
+|- platformio.ini
+|--src
+   |- main.c
+
+and a contents of `src/main.c`:
+```
+#include <Foo.h>
+#include <Bar.h>
+
+int main (void)
+{
+  ...
+}
+
+```
+
+PlatformIO Library Dependency Finder will find automatically dependent
+libraries scanning project source files.
+
+More information about PlatformIO Library Dependency Finder
+- https://docs.platformio.org/page/librarymanager/ldf.html

platformio.ini

@@ -0,0 +1,21 @@
+; 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
+
+[env:esp32doit-devkit-v1]
+platform = espressif32
+board = ttgo-t1
+framework = arduino
+monitor_port = COM[12345678]
+monitor_speed = 115200
+lib_deps = 
+	lennarthennigs/Button2@^1.4.1
+	fastled/FastLED@^3.3.3
+	sstaub/Ticker@^3.2.0
+	bertmelis/Ticker-esp32@^1.1.0

src/main.cpp

@@ -0,0 +1,193 @@
+// DotStarTest
+// This example will cycle between showing four pixels as Red, Green, Blue, White
+// and then showing those pixels as Black.
+//
+// There is serial output of the current state so you can confirm and follow along
+//
+
+#include <FastLED.h>
+#include <Button2.h>
+#include <Ticker.h>
+
+void (*LCD_fun)(void);
+
+const uint16_t PixelCount = 118; // this example assumes 4 pixels, making it smaller will cause a failure
+
+// make sure to set this to the correct pins
+const uint8_t DotDataPin = 27;  
+
+#define colorSaturation 128
+#define BRIGHTNESS  50
+
+#define MAX_ITER 2000000
+
+CRGBArray<PixelCount> strip;
+// for hardware SPI (best performance but must use hardware pins)
+//NeoPixelBus<DotStarBgrFeature, DotStarSpiMethod> strip(PixelCount);
+
+// DotStars that support RGB color and a overall luminance/brightness value
+// NeoPixelBus<DotStarLbgrFeature, DotStarMethod> strip(PixelCount, DotClockPin, DotDataPin);
+// DotStars that support RGBW color with a seperate white element
+//NeoPixelBus<DotStarWbgrFeature, DotStarMethod> strip(PixelCount, DotClockPin, DotDataPin);
+
+CRGB red(colorSaturation, 0, 0);
+CRGB green(0, colorSaturation, 0);
+CRGB blue(0, 0, colorSaturation);
+CRGB white(colorSaturation);
+CRGB black(0);
+CRGB white1(10,10,10);
+CRGB white2(30,30,30);
+CRGB white3(60,60,60);
+CRGB white4(90,90,90);
+
+CRGB yellow1(255,255,254);
+CRGB yellow2(255,250,205);
+CRGB yellow3(255,250,182);
+CRGB yellow4(255,250,172);
+
+CRGB Aqua(0,255,255);
+CRGB Black(0,0,0);
+CRGB Blue(0,0,255);
+CRGB Cream(255,251,240);
+CRGB Grey(128,128,128);
+CRGB Fuchsia(255,0,255);
+CRGB Green(0,128,0);
+CRGB Lime_green(0,255,0);
+CRGB Maroon(128,0,0);
+CRGB Navy(0,0,128);
+CRGB Olive_green(128,128,0);
+CRGB Purple(255,0,255);
+CRGB Red(255,0,0);
+CRGB Silver(192,192,192);
+CRGB Teal(0,128,128);
+CRGB White(255,255,255);
+CRGB rgbArrayL[] = {Aqua, Black, Blue, Cream, Grey, Fuchsia, Green, Lime_green,Maroon,Navy, Olive_green,Purple,Red,Silver,Teal,White};
+// for use with RGB DotStars when using the luminance/brightness global value
+// note that its range is only 0 - 31 (31 is full bright) and 
+// also note that it is not useful for POV displays as it will cause more flicker
+
+#define BUTTON_1 0
+void timer_funct();
+
+Button2 btn1(BUTTON_1);
+Ticker timer(timer_funct, 250,0, MILLIS);
+// Position of snake
+static unsigned int n;
+static unsigned int typeOfSnake;
+static unsigned int numberOfSnakes=5;
+static CRGB LEDonColor;
+static CRGB LEDoffColor;
+
+CRGB rgbArray[] = {red, blue, green, white};
+
+void timer_funct()
+{
+  Serial.println("Timer");
+  LCD_fun();
+}
+
+void LCD_snake()
+{
+  // set the colors
+  Serial.print("Snake:");Serial.println(n);
+  for (int i=0;i < PixelCount;i++) {
+    strip[i] = rgbArrayL[(i + n) % sizeof(rgbArrayL)];
+  }
+  n++;
+  FastLED.show();
+}
+
+void LCD_blink_color()
+{
+  Serial.print("Blink:");Serial.println(n);
+  if (n % 2)
+    for (int i=0;i < PixelCount;i++) {
+      strip[i] = LEDonColor;
+  } else {
+    for (int i=0;i < PixelCount;i++) {
+      strip[i] = LEDoffColor;
+    }
+  }
+  n++;
+  FastLED.show();
+}
+
+unsigned int t;
+
+void setup()
+{
+  Serial.begin(115200);
+  while (!Serial); // wait for serial attach
+
+  Serial.println();
+  Serial.println("Initializing...");
+  Serial.flush();
+
+  // this resets all the neopixels to an off state
+  FastLED.addLeds<NEOPIXEL,DotDataPin>(strip, PixelCount);
+  FastLED.setBrightness( BRIGHTNESS );
+
+  FastLED.showColor(white);
+  FastLED.show();
+
+  Serial.println();
+  Serial.println("Running...");
+
+  LCD_fun = &LCD_snake;
+  LCD_fun();
+  timer.start();
+
+  btn1.setClickHandler([](Button2 & b) {
+    Serial.println("Button press");
+    typeOfSnake++;
+    t = typeOfSnake % numberOfSnakes;
+    switch (t)
+    {
+      case 0:
+        FastLED.setBrightness(100);
+        LCD_fun = &LCD_snake;
+        break;
+      case 1:
+        LEDonColor=yellow1;
+        LEDoffColor=yellow1;
+        FastLED.setBrightness(10);
+        LCD_fun = &LCD_blink_color;
+        break;
+      case 2:
+        LEDonColor=yellow2;
+        LEDoffColor=yellow2;
+        FastLED.setBrightness(20);
+        LCD_fun = &LCD_blink_color;
+        break;
+      case 3:
+        LEDonColor=yellow3;
+        LEDoffColor=yellow3;
+        FastLED.setBrightness(30);
+        LCD_fun = &LCD_blink_color;
+        break;
+      case 4:
+        LEDonColor=yellow4;
+        LEDoffColor=yellow4;
+        FastLED.setBrightness(40);
+        LCD_fun = &LCD_blink_color;
+        break;
+      default:
+        break;
+        // default statements
+      }
+    });
+
+    btn1.setLongClickHandler([](Button2 & b) {
+      Serial.println("Long press");
+      LEDonColor=black;
+      LEDoffColor=black;
+      LCD_fun = &LCD_blink_color;
+    });
+
+}
+
+void loop()
+{
+  btn1.loop();
+  timer.update();
+}

test/README

@@ -0,0 +1,11 @@
+
+This directory is intended for PIO Unit Testing and project tests.
+
+Unit Testing is a software testing method by which individual units of
+source code, sets of one or more MCU program modules together with associated
+control data, usage procedures, and operating procedures, are tested to
+determine whether they are fit for use. Unit testing finds problems early
+in the development cycle.
+
+More information about PIO Unit Testing:
+- https://docs.platformio.org/page/plus/unit-testing.html