initial commit

.gitignore

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

.vscode/extensions.json

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

.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+    "git.ignoreLimitWarning": true
+}

.vscode/tasks.json

@@ -0,0 +1,13 @@
+{
+	"version": "2.0.0",
+	"tasks": [
+		{
+			"type": "PlatformIO",
+			"task": "Upload",
+			"problemMatcher": [
+				"$platformio"
+			],
+			"label": "PlatformIO: Upload"
+		}
+	]
+}

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,18 @@
+; 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:esp01_1m]
+platform = espressif8266
+board = esp01_1m
+framework = arduino
+lib_deps = 
+	adafruit/Adafruit IS31FL3731 Library@^2.0.0
+	adafruit/Adafruit GFX Library@^1.11.3
+monitor_speed = 9600

src/main.cpp

@@ -0,0 +1,112 @@
+#include <Arduino.h>
+#include <Wire.h>
+#include <Adafruit_GFX.h>
+#include <Adafruit_IS31FL3731.h>
+#include <ESP8266WiFi.h>
+
+using namespace std;
+
+const char* HOSTNAME="led_test";
+const char* SSID="ncc74656";
+const char* PSK="Rw7qfY5tmtaWbXaWQ5aMSRkF";
+
+#define NUM_SCREENS 2
+#define BRIGHTNESS 8
+
+Adafruit_IS31FL3731 matrix0 = Adafruit_IS31FL3731();
+#if NUM_SCREENS>=2
+Adafruit_IS31FL3731 matrix1 = Adafruit_IS31FL3731();
+#endif
+#if NUM_SCREENS>=3
+Adafruit_IS31FL3731 matrix2 = Adafruit_IS31FL3731();
+#endif
+#if NUM_SCREENS>=4
+Adafruit_IS31FL3731 matrix3 = Adafruit_IS31FL3731();
+#endif
+
+void setup() {
+  // set up I2C
+  Wire.pins(0,2); // SDA on GPIO0, SCL on GPIO2
+  Wire.begin(0,2);
+
+  // // connect to network
+  // WiFi.hostname(HOSTNAME);
+  // WiFi.begin(SSID, PSK);
+  // while (WiFi.status()!=WL_CONNECTED)
+  //   delay(500);
+
+  // connect to display(s)
+  if (! matrix0.begin(0x74)) 
+    while (1);
+  #if NUM_SCREENS>=2
+  if (! matrix1.begin(0x75)) 
+    while (1);
+  #endif
+  #if NUM_SCREENS>=3
+  if (! matrix2.begin(0x76)) 
+    while (1);
+  #endif
+  #if NUM_SCREENS>=4
+  if (! matrix3.begin(0x77)) 
+    while (1);
+  #endif
+}
+
+void loop() {
+
+  String msg="The quick brown fox jumps over the lazy dog.";
+  //String msg="   Hellorld!   ";
+
+  msg="    "+msg+"    ";
+  matrix0.setRotation(0);
+  matrix0.setTextSize(1);
+  matrix0.setTextWrap(false);
+  matrix0.setTextColor(BRIGHTNESS,0);
+  matrix0.clear();
+  #if NUM_SCREENS>=2
+  msg="    "+msg+"    ";
+  matrix1.setRotation(0);
+  matrix1.setTextSize(1);
+  matrix1.setTextWrap(false);
+  matrix1.setTextColor(BRIGHTNESS,0);
+  matrix1.clear();
+  #endif
+  #if NUM_SCREENS>=3
+  msg="    "+msg+"    ";
+  matrix2.setRotation(0);
+  matrix2.setTextSize(1);
+  matrix2.setTextWrap(false);
+  matrix2.setTextColor(BRIGHTNESS,0);
+  matrix2.clear();
+  #endif
+  #if NUM_SCREENS>=4
+  msg="    "+msg+"    ";
+  matrix3.setRotation(0);
+  matrix3.setTextSize(1);
+  matrix3.setTextWrap(false);
+  matrix3.setTextColor(BRIGHTNESS,0);
+  matrix3.clear();
+  #endif
+
+  for (int i=0; i<msg.length()-4*NUM_SCREENS; i++)
+  {
+    String segment=msg.substring(i, i+4*NUM_SCREENS);
+    for (int8_t x=0; x>-6; x--) {
+      matrix0.setCursor(x,0);
+      matrix0.print(segment);
+      #if NUM_SCREENS>=2
+      matrix1.setCursor(x-16,0);
+      matrix1.print(segment);
+      #endif
+      #if NUM_SCREENS>=3
+      matrix2.setCursor(x-32,0);
+      matrix2.print(segment);
+      #endif
+      #if NUM_SCREENS>=4
+      matrix3.setCursor(x-48,0);
+      matrix3.print(segment);
+      #endif
+      delay(25);
+    }
+  }
+}

test/README

@@ -0,0 +1,11 @@
+
+This directory is intended for PlatformIO Test Runner 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 PlatformIO Unit Testing:
+- https://docs.platformio.org/en/latest/advanced/unit-testing/index.html