commit 5c2e3bcef68bd8299db6893d903b13e1407ad391 Author: lagertonne Date: Mon May 26 17:17:04 2025 +0200 Initial commit diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..89cc49c --- /dev/null +++ b/.gitignore @@ -0,0 +1,5 @@ +.pio +.vscode/.browse.c_cpp.db* +.vscode/c_cpp_properties.json +.vscode/launch.json +.vscode/ipch diff --git a/.vscode/extensions.json b/.vscode/extensions.json new file mode 100644 index 0000000..080e70d --- /dev/null +++ b/.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" + ] +} diff --git a/.vscode/settings.json b/.vscode/settings.json new file mode 100644 index 0000000..033e361 --- /dev/null +++ b/.vscode/settings.json @@ -0,0 +1,3 @@ +{ + "idf.port": "/dev/ttyACM0" +} \ No newline at end of file diff --git a/include/README b/include/README new file mode 100644 index 0000000..49819c0 --- /dev/null +++ b/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 diff --git a/lib/README b/lib/README new file mode 100644 index 0000000..9379397 --- /dev/null +++ b/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 +#include + +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 diff --git a/platformio.ini b/platformio.ini new file mode 100644 index 0000000..592ef95 --- /dev/null +++ b/platformio.ini @@ -0,0 +1,19 @@ +; 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:esp32dev] +platform = espressif32 +board = lolin_c3_mini +framework = arduino +monitor_speed = 115200 +lib_deps = + https://github.com/tesa-klebeband/EasyDMX + https://github.com/forkineye/ESPAsyncE131.git + someweisguy/esp_dmx@^4.1.0 diff --git a/src/main.cpp b/src/main.cpp new file mode 100644 index 0000000..a600be1 --- /dev/null +++ b/src/main.cpp @@ -0,0 +1,90 @@ +#include +#include + +#include + +#define UNIVERSE 1 // First DMX Universe to listen for +#define UNIVERSE_COUNT 2 // Total number of Universes to listen for, starting at UNIVERSE + +const char ssid[] = "neuland"; // Replace with your SSID +const char passphrase[] = "kreismilliways"; // Replace with your WPA2 passphrase + +// ESPAsyncE131 instance with UNIVERSE_COUNT buffer slots +ESPAsyncE131 e131(UNIVERSE_COUNT); + +int transmitPin = 21; +int receivePin = 20; +int enablePin = 10; + +dmx_port_t dmxPort = 1; + +byte data[DMX_PACKET_SIZE]; + +unsigned long lastUpdate = millis(); + +void setup() { + Serial.begin(115200); + + dmx_config_t config = DMX_CONFIG_DEFAULT; + dmx_personality_t personalities[] = {}; + int personality_count = 0; + dmx_driver_install(dmxPort, &config, personalities, personality_count); + + dmx_set_pin(dmxPort, transmitPin, receivePin, enablePin); + + delay(3000); + + // Initialize E1.31 + + // Make sure you're in station mode + WiFi.mode(WIFI_STA); + + Serial.println(""); + Serial.print(F("Connecting to ")); + Serial.print(ssid); + + if (passphrase != NULL) + WiFi.begin(ssid, passphrase); + else + WiFi.begin(ssid); + + while (WiFi.status() != WL_CONNECTED) { + delay(500); + Serial.print("."); + } + + Serial.println(""); + Serial.print(F("Connected with IP: ")); + Serial.println(WiFi.localIP()); + + // Choose one to begin listening for E1.31 data + //if (e131.begin(E131_UNICAST)) // Listen via Unicast + if (e131.begin(E131_MULTICAST, UNIVERSE, UNIVERSE_COUNT)) // Listen via Multicast + Serial.println(F("Listening for data...")); + else + Serial.println(F("*** e131.begin failed ***")); +} + +void loop() { + // unsigned long now = millis(); + //Serial.printf("Sending DMX 0x%02X\n", data[1]); + + + if (!e131.isEmpty()) { + e131_packet_t packet; + e131.pull(&packet); // Pull packet from ring buffer + + //data[1] = packet.property_values[1]; + + Serial.printf("Universe %u / %u Channels | Packet#: %u / Errors: %u / CH1: %u\n", + htons(packet.universe), // The Universe for this packet + htons(packet.property_value_count) - 1, // Start code is ignored, we're interested in dimmer data + e131.stats.num_packets, // Packet counter + e131.stats.packet_errors, // Packet error counter + packet.property_values[1]); // Dimmer data for Channel 1 + + //dmx_wait_sent(dmxPort, DMX_TIMEOUT_TICK); + dmx_write(dmxPort, packet.property_values, DMX_PACKET_SIZE); + } + dmx_send(dmxPort); +} \ No newline at end of file diff --git a/test/README b/test/README new file mode 100644 index 0000000..9b1e87b --- /dev/null +++ b/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