commit 126c6a93d8deba8056fa72b7900fc59fd0ff49ab Author: Eddy de Vink Date: Sat Jul 11 00:31:05 2026 +0200 Initial commit diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..17cbf52 --- /dev/null +++ b/.gitignore @@ -0,0 +1,2 @@ +.pio/ +*~ diff --git a/README.md b/README.md new file mode 100644 index 0000000..e1a68b5 --- /dev/null +++ b/README.md @@ -0,0 +1,25 @@ +# USB Toggle + +ESP8266 (Wemos D1 Mini) firmware om een relais te schakelen via seriële USB. + +## Gebruik + +Sluit aan via USB en stuur commando's: + +```bash +./relay 1 # relais aan +./relay 0 # relais uit +``` + +## Pinnen + +| Component | GPIO | +|-----------|------| +| Relais | 0 | +| LED | LED_BUILTIN | + +## Build & Flash + +```bash +pio run --target upload --upload-port /dev/cu.usbserial-2110 +``` 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..4fa4a6d --- /dev/null +++ b/platformio.ini @@ -0,0 +1,14 @@ +; 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:d1_mini] +platform = espressif8266 +board = d1_mini +framework = arduino diff --git a/relay b/relay new file mode 100755 index 0000000..9dc0ae8 --- /dev/null +++ b/relay @@ -0,0 +1,3 @@ +#!/bin/bash +[ $# -ne 1 ] || [ "$1" != "0" -a "$1" != "1" ] && { echo "Usage: relay 0|1"; exit 1; } +python3 -c "import serial; s=serial.Serial('/dev/cu.usbserial-2110',115200,timeout=2); s.write(b'$1'); print(s.read(10).decode())" diff --git a/src/main.cpp b/src/main.cpp new file mode 100644 index 0000000..6842ccd --- /dev/null +++ b/src/main.cpp @@ -0,0 +1,28 @@ +#include + +#define RELAY_PIN 0 +#define LED_PIN LED_BUILTIN + +void setup() { + pinMode(RELAY_PIN, OUTPUT); + pinMode(LED_PIN, OUTPUT); + digitalWrite(RELAY_PIN, LOW); + digitalWrite(LED_PIN, HIGH); + Serial.begin(115200); + Serial.println("Ready — send 1 (on) or 0 (off)"); +} + +void loop() { + if (Serial.available() > 0) { + char c = Serial.read(); + if (c == '1') { + digitalWrite(RELAY_PIN, HIGH); + digitalWrite(LED_PIN, LOW); + Serial.println("ON"); + } else if (c == '0') { + digitalWrite(RELAY_PIN, LOW); + digitalWrite(LED_PIN, HIGH); + Serial.println("OFF"); + } + } +} 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