7 changed files with 191 additions and 0 deletions
@ -0,0 +1,5 @@ |
|||||
|
.pio |
||||
|
.vscode/.browse.c_cpp.db* |
||||
|
.vscode/c_cpp_properties.json |
||||
|
.vscode/launch.json |
||||
|
.vscode/ipch |
||||
@ -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" |
||||
|
] |
||||
|
} |
||||
@ -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 |
||||
@ -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 |
||||
@ -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 |
||||
@ -0,0 +1,67 @@ |
|||||
|
#include <Arduino.h> |
||||
|
#include <WiFi.h> |
||||
|
#include <WiFiMulti.h> |
||||
|
#include <WebServer.h> |
||||
|
|
||||
|
WiFiMulti wifiMulti; |
||||
|
const int ledPin = 2; |
||||
|
WebServer server(80); |
||||
|
bool ledState = LOW; |
||||
|
|
||||
|
const char INDEX_HTML[] PROGMEM = R"=====( |
||||
|
<html> |
||||
|
<body> |
||||
|
<h1> ESP32 Ovladani led </h1> |
||||
|
<p> Stav LED: |
||||
|
<button onclick="fetch('/led?state=on')">ZAPNOUT</button> |
||||
|
<button onclick="fetch('/led?state=off')">VYPNOUT</button> |
||||
|
</p> |
||||
|
</body> |
||||
|
</html> |
||||
|
)====="; |
||||
|
|
||||
|
void handleRoot() { |
||||
|
server.send_P(200,"text/html",INDEX_HTML); |
||||
|
} |
||||
|
|
||||
|
void handleLED(){ |
||||
|
String state = server.arg("state"); |
||||
|
if (state == "on") { |
||||
|
digitalWrite(ledPin, HIGH); |
||||
|
Serial.println("LED zapnuta"); |
||||
|
} else if (state == "off"){ |
||||
|
digitalWrite(ledPin, LOW); |
||||
|
Serial.println("LED vypnuta"); |
||||
|
} |
||||
|
server.send(200,"text/plain","OK"); |
||||
|
} |
||||
|
|
||||
|
|
||||
|
void setup() { |
||||
|
Serial.begin(115200); |
||||
|
pinMode(ledPin,OUTPUT); |
||||
|
|
||||
|
WiFi.hostname("esp32-skrabanek"); |
||||
|
wifiMulti.addAP("ive3ap","iveiveive"); |
||||
|
wifiMulti.addAP("KM12X","testtest"); |
||||
|
wifiMulti.addAP("tksteti","ProsimTeNevim"); |
||||
|
|
||||
|
Serial.print("Pripojuji k WiFi."); |
||||
|
while(wifiMulti.run() != WL_CONNECTED){ |
||||
|
delay(400); |
||||
|
Serial.print("."); |
||||
|
} |
||||
|
Serial.println("\nPripojeno"); |
||||
|
Serial.print("IP Adresa:"); |
||||
|
Serial.println(WiFi.localIP()); |
||||
|
|
||||
|
server.on("/",handleRoot); |
||||
|
server.on("/led",handleLED); |
||||
|
|
||||
|
server.begin(); |
||||
|
Serial.println("HTTP server bezi."); |
||||
|
} |
||||
|
|
||||
|
void loop() { |
||||
|
server.handleClient(); |
||||
|
} |
||||
@ -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 |
||||
Loading…
Reference in new issue