first commit

This commit is contained in:
2025-01-10 15:20:33 +08:00
commit 4f5d2aa650
66 changed files with 15921 additions and 0 deletions

5
ESP01-IMAS/.gitignore vendored Normal file
View File

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

10
ESP01-IMAS/.vscode/extensions.json vendored Normal file
View File

@ -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"
]
}

39
ESP01-IMAS/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
ESP01-IMAS/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
ESP01-IMAS/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:esp12e]
platform = espressif8266
board = esp12e
framework = arduino
lib_deps = bblanchon/ArduinoJson@^7.2.1

124
ESP01-IMAS/src/main.cpp Normal file
View File

@ -0,0 +1,124 @@
#include <ESP8266WiFi.h>
#include <ArduinoJson.h>
// Wi-Fi 连接信息
const char *ssid = "Xiaomi_3A40";
const char *password = "112233ww";
// 服务器信息
const char *serverIP = "192.168.31.184"; // 服务器 IP 地址
const int serverPort = 80; // 端口号
const char *requestPath = "/ESP01/getData.php"; // 请求路径
#define Sleep_Pin 2
void setup()
{
Serial.begin(115200);
WiFi.begin(ssid, password);
// 连接到 Wi-Fi
Serial.print("Connecting to Wi-Fi");
while (WiFi.status() != WL_CONNECTED)
{
delay(1000);
Serial.print(".");
}
Serial.println("\nWi-Fi connected!");
pinMode(Sleep_Pin, OUTPUT);
digitalWrite(Sleep_Pin, LOW);
}
void loop()
{
// 确保 Wi-Fi 连接正常
if (WiFi.status() != WL_CONNECTED)
{
Serial.println("Wi-Fi disconnected, reconnecting...");
WiFi.begin(ssid, password);
while (WiFi.status() != WL_CONNECTED)
{
delay(1000);
Serial.print(".");
}
Serial.println("\nReconnected to Wi-Fi!");
}
// 创建客户端
WiFiClient client;
if (client.connect(serverIP, serverPort))
{
Serial.println("Connected to server");
// 发送 GET 请求
client.println(String("GET ") + requestPath + " HTTP/1.1");
client.println(String("Host: ") + serverIP);
client.println("Connection: close");
client.println();
// 等待响应
while (client.connected() || client.available())
{
if (client.available())
{
String line = client.readStringUntil('\n');
if (line == "\r")
{
break; // 头部结束
}
}
}
// 读取 JSON 数据
String jsonData;
while (client.available())
{
jsonData += client.readString();
}
// 打印获取到的 JSON 数据
Serial.println("Received JSON:");
Serial.println(jsonData);
// 解析 JSON 数据
StaticJsonDocument<512> doc;
DeserializationError error = deserializeJson(doc, jsonData);
if (error)
{
Serial.print("Failed to parse JSON: ");
Serial.println(error.c_str());
return;
}
// 提取 JSON 数据
if (doc.containsKey("standby"))
{
String standby = doc["standby"];
Serial.print("Standby mode: ");
Serial.println(standby);
if (standby == "1")
{
Serial.println("Standby mode");
digitalWrite(Sleep_Pin, HIGH); // 打开休眠模式
}
else
{
Serial.println("Normal mode");
digitalWrite(Sleep_Pin, LOW); // 关闭休眠模式
}
}
else
{
Serial.println("Key 'standby' not found in JSON data");
}
}
else
{
Serial.println("Failed to connect to server");
}
// 延时一段时间再发送下一次请求
delay(100);
}

11
ESP01-IMAS/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