diff --git a/08_bluetooth_pwm/.gitignore b/08_bluetooth_pwm/.gitignore new file mode 100644 index 0000000..89cc49c --- /dev/null +++ b/08_bluetooth_pwm/.gitignore @@ -0,0 +1,5 @@ +.pio +.vscode/.browse.c_cpp.db* +.vscode/c_cpp_properties.json +.vscode/launch.json +.vscode/ipch diff --git a/08_bluetooth_pwm/.vscode/extensions.json b/08_bluetooth_pwm/.vscode/extensions.json new file mode 100644 index 0000000..080e70d --- /dev/null +++ b/08_bluetooth_pwm/.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/08_bluetooth_pwm/include/README b/08_bluetooth_pwm/include/README new file mode 100644 index 0000000..49819c0 --- /dev/null +++ b/08_bluetooth_pwm/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/08_bluetooth_pwm/lib/README b/08_bluetooth_pwm/lib/README new file mode 100644 index 0000000..9379397 --- /dev/null +++ b/08_bluetooth_pwm/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/08_bluetooth_pwm/platformio.ini b/08_bluetooth_pwm/platformio.ini new file mode 100644 index 0000000..457ca3e --- /dev/null +++ b/08_bluetooth_pwm/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 diff --git a/08_bluetooth_pwm/src/main.cpp b/08_bluetooth_pwm/src/main.cpp new file mode 100644 index 0000000..917f3b8 --- /dev/null +++ b/08_bluetooth_pwm/src/main.cpp @@ -0,0 +1,40 @@ +#include +#include + +#define LED_PIN 2 + +String device_name = "ESP-PWM-Skrabanek"; +BluetoothSerial SerialBT; + +void setup() { + Serial.begin(115200); + SerialBT.begin(device_name); + pinMode(LED_PIN,OUTPUT); + Serial.println("Bluetooth PWM projekt spusten."); + Serial.println("Prikazy: 'jas:X' (kde X je 0-255)"); +} + +void loop() { + if (SerialBT.available()){ + String input = SerialBT.readStringUntil('\n'); + input.trim(); + input.toLowerCase(); + + if(input.startsWith("jas:")){ + //potřeba získat část za dvojtečkou + String valueStr = input.substring(4); + int value = valueStr.toInt(); //převod na celé číslo + //omezení hodnoty na 0-255 + value = constrain(value,0,255); + analogWrite(LED_PIN,value); + SerialBT.print("Jas nastaven na:"); + SerialBT.println(value); + Serial.printf("BT: Nastaven jas na %d \n",value); + } else if (input == "vypnout") { + analogWrite(LED_PIN,0); + SerialBT.println("LED vypnuta"); + } else { + SerialBT.println("neznamy prikaz"); + } + } +} diff --git a/08_bluetooth_pwm/test/README b/08_bluetooth_pwm/test/README new file mode 100644 index 0000000..9b1e87b --- /dev/null +++ b/08_bluetooth_pwm/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