first commit

This commit is contained in:
kicap 2024-08-03 12:49:49 +08:00
commit 4955f57652
9 changed files with 259 additions and 0 deletions

5
.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
.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"
]
}

BIN
image.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.1 MiB

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:esp12e]
platform = espressif8266
board = esp12e
framework = arduino
; lib_deps = arduino-libraries/ArduinoHttpClient@^0.6.1

5
readme.md Normal file
View File

@ -0,0 +1,5 @@
# Traffic Light Disfunctio Monitoring (ESP8266)
### traffic light disfunction monitoring, this esp8266 receive data from arduino uno using serial communication because of limitation of uno .
![alt text](image.png)

128
src/main.cpp Normal file
View File

@ -0,0 +1,128 @@
#include <Arduino.h>
#include "SoftwareSerial.h"
#include <ESP8266WiFi.h>
#include <ESP8266HTTPClient.h>
const int ledPin = 2; // GPIO2 is typically the onboard LED pin on ESP8266
const char *ssid = "Bismillah";
const char *password = "1234567890";
// const char *ssid = "KARAN";
// const char *password = "12345679";
WiFiClient client;
SoftwareSerial fromUno(13, 15); // RX, TX
void setup()
{
Serial.begin(9600);
fromUno.begin(9600);
// Initialize the LED pin as an output
pinMode(ledPin, OUTPUT);
digitalWrite(ledPin, HIGH); // Turn off LED initially
Serial.println();
Serial.println();
Serial.print("Connecting to ");
Serial.println(ssid);
WiFi.begin(ssid, password);
while (WiFi.status() != WL_CONNECTED)
{
delay(500);
Serial.print(".");
}
Serial.println("");
Serial.println("WiFi connected");
Serial.println("IP address: ");
Serial.println(WiFi.localIP());
digitalWrite(ledPin, LOW); // Turn on LED to indicate Wi-Fi connected
}
void loop()
{
if (WiFi.status() == WL_CONNECTED)
{
digitalWrite(ledPin, LOW); // Turn on LED to indicate Wi-Fi connected
String data = "";
while (fromUno.available() > 0)
{
data += char(fromUno.read());
// delay(1);
}
// Serial.println(data);
// Ensure the data string is properly terminated
data.trim();
// Split the data string by commas
int commaIndex1 = data.indexOf(',');
String light = data.substring(0, commaIndex1);
int commaIndex2 = data.indexOf(',', commaIndex1 + 1);
String pln = data.substring(commaIndex1 + 1, commaIndex2);
int commaIndex3 = data.indexOf(',', commaIndex2 + 1);
String value1 = data.substring(commaIndex2 + 1, commaIndex3);
int commaIndex4 = data.indexOf(',', commaIndex3 + 1);
int commaIndex5 = data.indexOf(',', commaIndex4 + 1);
String value2 = data.substring(commaIndex3 + 1, commaIndex4);
String value3 = data.substring(commaIndex4 + 1, commaIndex5);
String value4 = data.substring(commaIndex5 + 1);
// Ensure no extra data is included
value4 = value4.substring(0, value4.indexOf('\n') >= 0 ? value4.indexOf('\n') : value4.length());
// Construct the JSON payload
String jsonSend = "{\"light\":\"" + light + "\",\"pln\":\"" + pln + "\",\"value1\":\"" + value1 + "\",\"value2\":\"" + value2 + "\",\"value3\":\"" + value3 + "\",\"no\":\"" + value4 + "\"}";
Serial.println(jsonSend);
HTTPClient http;
http.begin(client, "http://traffic-light2.kicap-karan.com/");
http.addHeader("Content-Type", "application/json");
int httpResponseCode = http.POST(jsonSend);
if (httpResponseCode > 0)
{
Serial.print("HTTP Response code: ");
Serial.println(httpResponseCode);
}
else
{
Serial.print("Error code: ");
Serial.println(httpResponseCode);
}
http.end();
delay(1000);
}
else
{
Serial.println("WiFi is disconnected, attempting to reconnect");
digitalWrite(ledPin, HIGH);
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());
digitalWrite(ledPin, LOW); // Turn on LED to indicate Wi-Fi connected
}
else
{
Serial.println("");
Serial.println("Failed to reconnect to WiFi");
}
}
}

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