first commit

This commit is contained in:
kicap 2024-08-15 02:47:45 +08:00
commit 6d20228bbd
8 changed files with 230 additions and 0 deletions

7
.gitignore vendored Normal file
View File

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

BIN
image.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 96 KiB

39
include/README Normal file
View File

@ -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

46
lib/README Normal file
View File

@ -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 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 <Foo.h>
#include <Bar.h>
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

15
platformio.ini Normal file
View File

@ -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:esp01_1m]
platform = espressif8266
board = esp01_1m
framework = arduino
monitor_speed = 115200

5
readme.md Normal file
View File

@ -0,0 +1,5 @@
## shrimp-embankment-esp-01
#### the esp-01 receive data from arduino uno and send it to node js server
![alt text](image.png)

107
src/main.cpp Normal file
View File

@ -0,0 +1,107 @@
#include <Arduino.h>
#include <ESP8266WiFi.h>
#include <ESP8266HTTPClient.h>
// WiFi credentials
const char *ssid = "KARAN";
const char *password = "12345679";
WiFiClient client;
void setup()
{
Serial.begin(115200);
Serial.println("ESP-01 ready");
WiFi.begin(ssid, password);
while (WiFi.status() != WL_CONNECTED)
{
delay(500);
Serial.println("Connecting to WiFi..");
}
Serial.println("Connected to the WiFi network");
Serial.println(WiFi.localIP());
Serial.println("Starting up...");
delay(2000);
}
void loop()
{
if (WiFi.status() == WL_CONNECTED)
{
String IncomingStr = "";
while (Serial.available() > 0)
{
char in = Serial.read();
IncomingStr += in;
delay(2);
}
if (IncomingStr.length() > 0)
{
IncomingStr = IncomingStr.substring(0, IncomingStr.indexOf('\n'));
String jsonSent = "{\"value\": \"" + IncomingStr + "\"}";
// Initialize HTTP client
HTTPClient http;
http.begin(client, "http://192.168.20.45:3006");
http.addHeader("Content-Type", "application/json");
int httpResponseCode = http.POST(jsonSent);
if (httpResponseCode > 0)
{
Serial.print("HTTP Response code: ");
Serial.println(httpResponseCode);
String payload = http.getString();
Serial.println(payload);
}
else
{
Serial.print("Error code: ");
Serial.println(httpResponseCode);
}
// Close connection
http.end();
delay(1000);
}
// Send data to Arduino
Serial.println("Hello from ESP-01!");
}
else
{
// Reconnect to WiFi if disconnected
WiFi.begin(ssid, password);
// Wait for connection
int timeout = 0;
while (WiFi.status() != WL_CONNECTED && timeout < 20)
{ // wait for 10 seconds max
delay(500);
Serial.print(".");
timeout++;
}
if (WiFi.status() == WL_CONNECTED)
{
Serial.println("");
Serial.println("Reconnected to WiFi");
Serial.println("IP address: ");
Serial.println(WiFi.localIP());
}
else
{
Serial.println("");
Serial.println("Failed to reconnect to WiFi");
}
}
delay(2000);
}

11
test/README Normal file
View File

@ -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