From af0f794756279c72b58d33f90e3b7fac6ca082d1 Mon Sep 17 00:00:00 2001 From: Torsten Ruger Date: Sun, 20 Jun 2021 12:57:47 +0300 Subject: [PATCH] . --- fan_control/.gitignore | 5 ++++ fan_control/.vscode/extensions.json | 7 ++++++ fan_control/README.md | 35 ++++++++++++++++++++++++++ fan_control/include/README | 39 +++++++++++++++++++++++++++++ fan_control/platformio.ini | 14 +++++++++++ fan_control/src/main.cpp | 12 +++++++++ fan_control/test/README | 11 ++++++++ 7 files changed, 123 insertions(+) create mode 100644 fan_control/.gitignore create mode 100644 fan_control/.vscode/extensions.json create mode 100644 fan_control/README.md create mode 100644 fan_control/include/README create mode 100644 fan_control/platformio.ini create mode 100644 fan_control/src/main.cpp create mode 100644 fan_control/test/README diff --git a/fan_control/.gitignore b/fan_control/.gitignore new file mode 100644 index 0000000..89cc49c --- /dev/null +++ b/fan_control/.gitignore @@ -0,0 +1,5 @@ +.pio +.vscode/.browse.c_cpp.db* +.vscode/c_cpp_properties.json +.vscode/launch.json +.vscode/ipch diff --git a/fan_control/.vscode/extensions.json b/fan_control/.vscode/extensions.json new file mode 100644 index 0000000..0f0d740 --- /dev/null +++ b/fan_control/.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" + ] +} diff --git a/fan_control/README.md b/fan_control/README.md new file mode 100644 index 0000000..2dd1af7 --- /dev/null +++ b/fan_control/README.md @@ -0,0 +1,35 @@ +# Testing platforio and esp + +## Rationale + +I notices that i have to start smaller, make test. + +Also, while python was great, the library handling was (really) _bad_ . + +Since PlatformIO finally allows to add code to git and share it i chose that +over plain Arduino. + +And the Basic is such an unbeatable package of esp, power supply, relay and case. +Even with ce mark. So here we go... + +## File structure + +This whole directory is a PlatformIO project. Testing . . . + +I am not sure what parts are machine specific and thus have to be left out. + +## Esp + +Or to be precise a SonOff Basic v1.3 is the target. + +I have this wired with an UNO as a programmer according to https://www.youtube.com/watch?v=qOztsbEfg1g +This just bridges the uno and uses its usb chip to pass the programm on. +The net says a usb to TTL programmer is the "normal" way, just have not bought one. + +## Code + +The actual code i am trying to write will use the Basic to switch a Fan. + +I will add 2 DHT22 in a case like this https://www.thingiverse.com/thing:4852992 + +The sketch will simply compare temeratures and switch the relay on/off diff --git a/fan_control/include/README b/fan_control/include/README new file mode 100644 index 0000000..194dcd4 --- /dev/null +++ b/fan_control/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 diff --git a/fan_control/platformio.ini b/fan_control/platformio.ini new file mode 100644 index 0000000..dc3d6f0 --- /dev/null +++ b/fan_control/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:sonoff_basic] +platform = espressif8266 +board = sonoff_basic +framework = arduino diff --git a/fan_control/src/main.cpp b/fan_control/src/main.cpp new file mode 100644 index 0000000..c5a5906 --- /dev/null +++ b/fan_control/src/main.cpp @@ -0,0 +1,12 @@ +#include + +void setup() +{ + Serial.begin(9600); +} + +void loop() +{ + Serial.println("Hello world!"); + delay(1000); +} \ No newline at end of file diff --git a/fan_control/test/README b/fan_control/test/README new file mode 100644 index 0000000..b94d089 --- /dev/null +++ b/fan_control/test/README @@ -0,0 +1,11 @@ + +This directory is intended for PlatformIO 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 PlatformIO Unit Testing: +- https://docs.platformio.org/page/plus/unit-testing.html