diff --git a/IR-capture-KBSim/.gitignore b/IR-capture-KBSim/.gitignore new file mode 100644 index 0000000..89cc49c --- /dev/null +++ b/IR-capture-KBSim/.gitignore @@ -0,0 +1,5 @@ +.pio +.vscode/.browse.c_cpp.db* +.vscode/c_cpp_properties.json +.vscode/launch.json +.vscode/ipch diff --git a/IR-capture-KBSim/.vscode/extensions.json b/IR-capture-KBSim/.vscode/extensions.json new file mode 100644 index 0000000..0f0d740 --- /dev/null +++ b/IR-capture-KBSim/.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/IR-capture-KBSim/include/README b/IR-capture-KBSim/include/README new file mode 100644 index 0000000..194dcd4 --- /dev/null +++ b/IR-capture-KBSim/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/IR-capture-KBSim/lib/README b/IR-capture-KBSim/lib/README new file mode 100644 index 0000000..6debab1 --- /dev/null +++ b/IR-capture-KBSim/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/IR-capture-KBSim/platformio.ini b/IR-capture-KBSim/platformio.ini new file mode 100644 index 0000000..23d81a4 --- /dev/null +++ b/IR-capture-KBSim/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:digispark-tiny] +platform = atmelavr +board = digispark-tiny +framework = arduino diff --git a/IR-capture-KBSim/src/main.cpp b/IR-capture-KBSim/src/main.cpp new file mode 100644 index 0000000..f37772b --- /dev/null +++ b/IR-capture-KBSim/src/main.cpp @@ -0,0 +1,29 @@ +#include + +int irPin=5; + +void setup() +{ + pinMode(irPin,INPUT); + pinMode(1,OUTPUT); + //Serial.begin(9600); + digitalWrite(1,HIGH); + //Serial.println("You pressed a button"); + delay(1000); + digitalWrite(1,LOW); +} + +void loop() +{ + + if(pulseIn(irPin,LOW)) + { + //button pressed + delay(100); + digitalWrite(1,HIGH); + //Serial.println("You pressed a button"); + delay(1000); + digitalWrite(1,LOW); + } + +} diff --git a/IR-capture-KBSim/test/README b/IR-capture-KBSim/test/README new file mode 100644 index 0000000..b94d089 --- /dev/null +++ b/IR-capture-KBSim/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 diff --git a/SSD1306_i2c/.gitignore b/SSD1306_i2c/.gitignore new file mode 100644 index 0000000..89cc49c --- /dev/null +++ b/SSD1306_i2c/.gitignore @@ -0,0 +1,5 @@ +.pio +.vscode/.browse.c_cpp.db* +.vscode/c_cpp_properties.json +.vscode/launch.json +.vscode/ipch diff --git a/SSD1306_i2c/.vscode/extensions.json b/SSD1306_i2c/.vscode/extensions.json new file mode 100644 index 0000000..0f0d740 --- /dev/null +++ b/SSD1306_i2c/.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/SSD1306_i2c/include/README b/SSD1306_i2c/include/README new file mode 100644 index 0000000..194dcd4 --- /dev/null +++ b/SSD1306_i2c/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/SSD1306_i2c/lib/README b/SSD1306_i2c/lib/README new file mode 100644 index 0000000..6debab1 --- /dev/null +++ b/SSD1306_i2c/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/SSD1306_i2c/platformio.ini b/SSD1306_i2c/platformio.ini new file mode 100644 index 0000000..446aa93 --- /dev/null +++ b/SSD1306_i2c/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:esp32doit-devkit-v1] +platform = espressif32 +board = esp32doit-devkit-v1 +framework = arduino +lib_deps = adafruit/Adafruit SSD1306@^2.4.0 +lib_ldf_mode = chain+ \ No newline at end of file diff --git a/SSD1306_i2c/src/main.cpp b/SSD1306_i2c/src/main.cpp new file mode 100644 index 0000000..4eaff61 --- /dev/null +++ b/SSD1306_i2c/src/main.cpp @@ -0,0 +1,42 @@ +/********* + Rui Santos + Complete project details at https://randomnerdtutorials.com +*********/ + +// I connected SCK to D22 and SDA to D21 - but all I get is a weird pattern - is the dislay broken? + +#include +#include +#include +#include +#include + +#define SCREEN_WIDTH 128 // OLED display width, in pixels +#define SCREEN_HEIGHT 64 // OLED display height, in pixels + +// Declaration for an SSD1306 display connected to I2C (SDA, SCL pins) +Adafruit_SSD1306 display(SCREEN_WIDTH, SCREEN_HEIGHT, &Wire, -1); + +void setup() { + Serial.begin(115200); + + if(!display.begin(SSD1306_SWITCHCAPVCC, 0x3C)) { // Address 0x3D for 128x64 + Serial.println(F("SSD1306 allocation failed")); + for(;;); + } + delay(2000); + display.clearDisplay(); + display.display(); + + display.setTextSize(2); + display.setTextColor(WHITE); + display.setCursor(0, 10); + // Display static text + display.println("Hello, world!"); + display.display(); +} + +void loop() { + +} + diff --git a/SSD1306_i2c/test/README b/SSD1306_i2c/test/README new file mode 100644 index 0000000..b94d089 --- /dev/null +++ b/SSD1306_i2c/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 diff --git a/tasmota.bin b/tasmota.bin new file mode 100644 index 0000000..ff2ddcc Binary files /dev/null and b/tasmota.bin differ diff --git a/tasmotizer.cfg b/tasmotizer.cfg new file mode 100644 index 0000000..99b0e35 --- /dev/null +++ b/tasmotizer.cfg @@ -0,0 +1,15 @@ +[General] +AP=JoNelsDarlings +Broker=mqtt.ddns.kawomi.com +FriendlyName=tasmotaFN +FullTopic=%prefix%/%topic%/ +MQTTUser= +Module=Generic +ModuleMode=0 +Port=1883 +Template= +Topic=tasmotaTop +gbMQTT=true +gbModule=false +gbRecWifi=false +gbWifi=true