first commit, added 3 pzem-004 t to detect r,s,t phase, while sending data to esp32 for sending it to server

This commit is contained in:
kicap 2024-05-05 03:28:00 +08:00
commit f58e30b5d8
9 changed files with 237 additions and 0 deletions

BIN
.DS_Store vendored Normal file

Binary file not shown.

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

3
.vscode/settings.json vendored Normal file
View File

@ -0,0 +1,3 @@
{
"cmake.configureOnOpen": false
}

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

19
platformio.ini Normal file
View File

@ -0,0 +1,19 @@
; 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:uno]
platform = atmelavr
board = uno
framework = arduino
lib_deps =
; adafruit/Adafruit SSD1306@^2.5.9
; bblanchon/ArduinoJson@^7.0.4
mandulaj/PZEM-004T-v30@^1.1.2
monitor_speed = 19200

104
src/main.cpp Normal file
View File

@ -0,0 +1,104 @@
#include <PZEM004Tv30.h>
#include <SoftwareSerial.h>
PZEM004Tv30 pzem(6, 7); //fase r
PZEM004Tv30 pzem2(4, 5); //fase s
PZEM004Tv30 pzem3(2, 3); //fase t
SoftwareSerial fromesp32(8, 9);
void setup()
{
Serial.begin(19200);
fromesp32.begin(9600);
Serial.println("..initialized");
}
void checkPzem(String status,float voltage, float current, float power, float energy, float frequency, float pf)
{
String ini = "";
ini += status + ",";
if (voltage != NAN)
{
Serial.print("Voltage: ");
Serial.print(voltage);
Serial.println("V");
ini += String(voltage) + ",";
}
else
{
Serial.println("Error reading voltage");
ini += "err,";
}
if (current != NAN)
{
Serial.print("Current: ");
Serial.print(current);
Serial.println("A");
ini += String(current) + ",";
}
else
{
Serial.println("Error reading current");
ini += "err,";
}
if (power != NAN)
{
Serial.print("Power: ");
Serial.print(power);
Serial.println("W");
ini += String(power) + ",";
}
else
{
Serial.println("Error reading power");
ini += "err,";
}
if (energy != NAN)
{
Serial.print("Energy: ");
Serial.print(energy, 3);
Serial.println("kWh");
ini += String(energy) + ",";
}
else
{
Serial.println("Error reading energy");
ini += "err,";
}
if (frequency != NAN)
{
Serial.print("Frequency: ");
Serial.print(frequency, 1);
Serial.println("Hz");
ini += String(frequency) + ",";
}
else
{
Serial.println("Error reading frequency");
ini += "err,";
}
if (pf != NAN)
{
Serial.print("PF: ");
Serial.println(pf);
ini += String(pf);
}
else
{
Serial.println("Error reading power factor");
ini += "err";
}
ini += "\n";
fromesp32.print(ini);
Serial.println();
delay(2000);
}
void loop()
{
checkPzem("Fase R",pzem.voltage(), pzem.current(), pzem.power(), pzem.energy(), pzem.frequency(), pzem.pf());
checkPzem("Fase S",pzem2.voltage(), pzem2.current(), pzem2.power(), pzem2.energy(), pzem2.frequency(), pzem2.pf());
checkPzem("Fase T",pzem3.voltage(), pzem3.current(), pzem3.power(), pzem3.energy(), pzem3.frequency(), pzem3.pf());
// delay(1500);
}

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