bluetooth 3LED

06_esp_bluetooth_blink/.gitignore

@@ -0,0 +1,5 @@
+.pio
+.vscode/.browse.c_cpp.db*
+.vscode/c_cpp_properties.json
+.vscode/launch.json
+.vscode/ipch

06_esp_bluetooth_blink/.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"
+    ]
+}

06_esp_bluetooth_blink/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

06_esp_bluetooth_blink/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 <Foo.h>
+#include <Bar.h>
+
+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

06_esp_bluetooth_blink/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:esp32dev]
+platform = espressif32
+board = esp32dev
+framework = arduino
+monitor_speed = 115200

06_esp_bluetooth_blink/src/main.cpp

@@ -0,0 +1,79 @@
+#include <Arduino.h>
+#include <BluetoothSerial.h>
+
+#define LED1_PIN 18
+#define LED2_PIN 19
+#define LED3_PIN 21
+
+String device_name = "ESP-Skrabanek";
+BluetoothSerial SerialBT;
+
+void setup() {
+    Serial.begin(115200);
+    SerialBT.begin(device_name);
+    Serial.printf("Zarizeni \"%s\" spusteno",device_name.c_str());
+    pinMode(LED1_PIN,OUTPUT);
+    pinMode(LED2_PIN,OUTPUT);
+    pinMode(LED3_PIN,OUTPUT);
+    //zajištení vypnutí LED při zapnutí
+    digitalWrite(LED1_PIN,LOW);
+    digitalWrite(LED2_PIN,LOW);
+    digitalWrite(LED3_PIN,LOW);
+}
+
+void loop() {
+  if (SerialBT.available()){
+    String command = SerialBT.readStringUntil('\n');
+    command.trim();
+    if (command.equalsIgnoreCase("on")){
+        digitalWrite(LED1_PIN,HIGH);
+        digitalWrite(LED2_PIN,HIGH);
+        digitalWrite(LED3_PIN,HIGH);
+        SerialBT.println("LED 1+2+3 zapnuty");
+        Serial.println("LED 1+2+3 zapnuty");
+    } 
+    else if (command.equalsIgnoreCase("1on")){
+        digitalWrite(LED1_PIN,HIGH);
+        SerialBT.println("LED 1 zapnuta");
+        Serial.println("LED 1 zapnuta");
+    }
+    else if (command.equalsIgnoreCase("2on")){
+        digitalWrite(LED2_PIN,HIGH);
+        SerialBT.println("LED 2 zapnuta");
+        Serial.println("LED 2 zapnuta");
+    }
+    else if (command.equalsIgnoreCase("3on")){
+        digitalWrite(LED3_PIN,HIGH);
+        SerialBT.println("LED 3 zapnuta");
+        Serial.println("LED 3 zapnuta");
+    } 
+    else if (command.equalsIgnoreCase("off")){
+        digitalWrite(LED1_PIN,LOW);
+        digitalWrite(LED2_PIN,LOW);
+        digitalWrite(LED3_PIN,LOW);
+        SerialBT.println("LED 1+2+3 vypnuty");
+        Serial.println("LED 1+2+3 vypnuty");
+    }
+    else if (command.equalsIgnoreCase("1off")){
+        digitalWrite(LED1_PIN,LOW);
+        SerialBT.println("LED 1 vypnuta");
+        Serial.println("LED 1 vypnuta");
+    }
+    else if (command.equalsIgnoreCase("2off")){
+        digitalWrite(LED2_PIN,LOW);
+        SerialBT.println("LED 2 vypnuta");
+        Serial.println("LED 2 vypnuta");
+    }
+    else if (command.equalsIgnoreCase("3off")){
+        digitalWrite(LED3_PIN,LOW);
+        SerialBT.println("LED 3 vypnuta");
+        Serial.println("LED 3 vypnuta");
+    }
+    else {
+        SerialBT.println("spatny prikaz");
+        SerialBT.println("Dostupne prikazy: on, off, 1on, 1off, 2on, 2off, 3on, 3off");
+        Serial.println("uzivatel zadal chybny prikaz");
+    }
+    
+  }
+}

06_esp_bluetooth_blink/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