commit 9614ac4c9a305a8ff860b87a9a5d9b8882033331 Author: patha Date: Mon Oct 31 12:36:49 2022 +0100 initialer 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/README.md b/README.md new file mode 100644 index 0000000..e69de29 diff --git a/include/README b/include/README new file mode 100644 index 0000000..194dcd4 --- /dev/null +++ b/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/lib/README b/lib/README new file mode 100644 index 0000000..6debab1 --- /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 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 +#include + +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 diff --git a/platformio.ini b/platformio.ini new file mode 100644 index 0000000..a46db7b --- /dev/null +++ b/platformio.ini @@ -0,0 +1,15 @@ +; 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:nanoatmega328] +platform = atmelavr +board = nanoatmega328 +framework = arduino +lib_deps = z3t0/IRremote@^4.0.0 diff --git a/src/main.cpp b/src/main.cpp new file mode 100644 index 0000000..93a53c9 --- /dev/null +++ b/src/main.cpp @@ -0,0 +1,97 @@ +#include + +// Übernahme aus .ino Datei, korrekte Library sollte installiert sein, vermutlich haben sich die Funktionen geändert (muss korrigiert werden) + +int IRpin=7; +IRrecv IR(IRpin); +decode_results cmd; + +int PWMPin1=3; +int PWMPin2=9; +int Bright1=255; +int Bright2=255; + +float dfact1=1; +float dfact2=1; + +String mycom; + + +void setup() { + Serial.begin(9600); + IR.enableIRIn(); + + pinMode(PWMPin1,OUTPUT); + pinMode(PWMPin2,OUTPUT); + +} + +void loop() { + analogWrite(PWMPin1,Bright1*dfact1); + analogWrite(PWMPin2,Bright2*dfact2); + + while (IR.decode(&cmd)==0) { + } + + Serial.println(cmd.value,HEX); + delay(10); + IR.resume(); + + if (cmd.value==0xE0E036C9){ + mycom="A"; + Serial.print(mycom); + } + + if (cmd.value==0xE0E028D7){ + mycom="B"; + Serial.print(mycom); + } + + if (cmd.value==0xE0E0A857){ + mycom="C"; + Serial.print(mycom); + } + + if (cmd.value==0xE0E06897){ + mycom="D"; + Serial.print(mycom); + } + + if (mycom=="A"){ + if(dfact1==0){ + dfact1=0.06; + } + dfact1=dfact1*1.1; + if(dfact1>1){ + dfact1=1; + } + } + + if (mycom=="B"){ + dfact1=dfact1*0.9; + if(dfact1<0.06){ + dfact1=0; + } + } + + + if (mycom=="C"){ + if(dfact2==0){ + dfact2=0.06; + } + dfact2=dfact2*1.1; + if(dfact2>1){ + dfact2=1; + } + } + + if (mycom=="D"){ + dfact2=dfact2*0.9; + if(dfact2<0.06){ + dfact2=0; + } + } + + + +} \ 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