feat: 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"
+    ]
+}

README.md

@@ -0,0 +1,28 @@
+# DMX Controller
+
+# Lessons learned
+
+- Man kann super Serial1 als Ausgang verwenden
+- 
+
+# About DMX
+
+- Baud 250.000
+
+## About the Whadda DMX512 / Velleman VMA432
+
+- Voltage: 5V
+- Pins:
+  - GND - Ground
+  - VCC - 5V
+  - NC - Not connected
+  - SIG - Input for the controller, UART TX
+
+## UART on the ESP8266 NodeMCU
+
+- UART0
+  - RX = GPIO3 RX
+  - TX = GPIO1 TX
+- UART1
+  - RX = No RX
+  - TX = GPIO2 D4

include/README

@@ -0,0 +1,37 @@
+
+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 convention is to give header files names that end with `.h'.
+
+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 the executable file.
+
+The source code of each library should be placed in a separate directory
+("lib/your_library_name/[Code]").
+
+For example, see the structure of the following example libraries `Foo` and `Bar`:
+
+|--lib
+|  |
+|  |--Bar
+|  |  |--docs
+|  |  |--examples
+|  |  |--src
+|  |     |- Bar.c
+|  |     |- Bar.h
+|  |  |- library.json (optional. for 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
+
+Example contents of `src/main.c` using Foo and Bar:
+```
+#include <Foo.h>
+#include <Bar.h>
+
+int main (void)
+{
+  ...
+}
+
+```
+
+The PlatformIO Library Dependency Finder will find automatically dependent
+libraries by scanning project source files.
+
+More information about PlatformIO Library Dependency Finder
+- https://docs.platformio.org/page/librarymanager/ldf.html

platformio.ini

@@ -0,0 +1,16 @@
+; 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:esp12e]
+platform = espressif8266
+board = nodemcuv2
+framework = arduino
+lib_deps =
+    rickgg/ESPDMX

src/main.cpp

@@ -0,0 +1,87 @@
+#include <Arduino.h>
+#include <ESPDMX.h>
+
+DMXESPSerial dmx;
+
+void setup()
+{
+  Serial.begin(9600);
+  dmx.init(512);
+  delay(200);
+}
+
+struct Command
+{
+  bool valid;
+  int address;
+  int value;
+};
+
+Command readCommand()
+{
+  static String buffer = "";
+  Command result = {false, 0, 0};
+
+  while (Serial.available() > 0)
+  {
+    char c = Serial.read();
+
+    if (c == '\n')
+    {
+      String line = buffer;
+      buffer = "";
+
+      line.trim();
+      if (line.length() == 0)
+        return result;
+
+      int eqPos = line.indexOf('=');
+      if (eqPos == -1)
+        return result;
+
+      String left = line.substring(0, eqPos);
+      String right = line.substring(eqPos + 1);
+
+      left.trim();
+      right.trim();
+
+      if (!left.length() || !right.length())
+        return result;
+
+      int address = left.toInt();
+      int value = right.toInt();
+
+      if (address >= 0 && address < 512 &&
+          value >= 0 && value < 256)
+      {
+
+        result.valid = true;
+        result.address = address;
+        result.value = value;
+      }
+
+      return result;
+    }
+    else
+    {
+      if (buffer.length() < 64)
+      {
+        buffer += c;
+      }
+    }
+  }
+
+  return result;
+}
+
+void loop()
+{
+  Command command = readCommand();
+  if (command.valid)
+  {
+    dmx.write(command.address, command.value);
+  }
+
+  dmx.update();
+  delay(1);
+}

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