Arduino/Batteriewaechter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

initialer comit files

Browse Source
This commit is contained in:
patha
2022-10-31 12:30:34 +01:00
parent 30dd829f2a
commit 66eed20551
14 changed files with 414 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
Batteriewaechter_Reciever/.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
Batteriewaechter_Reciever/.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
Batteriewaechter_Reciever/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
Batteriewaechter_Reciever/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 a 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
Batteriewaechter_Reciever/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:nanoatmega328]
platform = atmelavr
board = nanoatmega328
framework = arduino
lib_deps = nrf24/RF24@^1.4.5

45
Batteriewaechter_Reciever/src/main.cpp Normal file
View File

@@ -0,0 +1,45 @@
#include <Arduino.h>
#include <SPI.h>
#include <nRF24L01.h>
#include <RF24.h>
//SCK-> PIN13, MISO->PIN12, MOSI->PIN11
const int CEPin=6;
const int CSNPin=8;
const int LedPin=2;
RF24 radio(CEPin,CSNPin); //CE, CSN
const byte address[6] = "00001";
int Signal=1;
void setup() {
Serial.begin(9600);
pinMode(LedPin,OUTPUT);
radio.begin();
radio.openReadingPipe(0, address);
radio.setPALevel(RF24_PA_MAX);
radio.startListening();
}
void loop() {
Serial.println("Radio available?");
delay(1000);
if(radio.available()) {
Serial.println("Radio available");
radio.read(&Signal, sizeof(Signal));
if(Signal==1){
digitalWrite(LedPin,HIGH);
Serial.println("Empfange");
Serial.println(Signal);
}
else{
digitalWrite(LedPin,LOW);
Serial.println("Empfange");
Serial.println(Signal);
}
}
}

11
Batteriewaechter_Reciever/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

5
Batteriewaechter_Sender/.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
Batteriewaechter_Sender/.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
Batteriewaechter_Sender/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
Batteriewaechter_Sender/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 a 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

18
Batteriewaechter_Sender/platformio.ini Normal file
View File

@@ -0,0 +1,18 @@
; 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:nanoatmega328]
platform = atmelavr
board = nanoatmega328
framework = arduino
lib_deps =
nrf24/RF24@^1.4.2
adafruit/Adafruit SH110X@^2.1.6
adafruit/Adafruit GFX Library@^1.11.2

114
Batteriewaechter_Sender/src/main.cpp Normal file
View File

@@ -0,0 +1,114 @@
#include <Arduino.h>
#include <SPI.h>
#include <nRF24L01.h>
#include <RF24.h>
#include <Wire.h>
#include <Adafruit_SH110X.h>
#include <Adafruit_GFX.h>
#define i2c_Address 0x3c //initialize with the I2C addr 0x3C Typically eBay OLED's
#define SCREEN_WIDTH 128 // OLED display width, in pixels
#define SCREEN_HEIGHT 64 // OLED display height, in pixels
#define OLED_RESET -1 // QT-PY / XIAO
Adafruit_SH1106G display = Adafruit_SH1106G(SCREEN_WIDTH, SCREEN_HEIGHT, &Wire, OLED_RESET);
int RelaisPin=2;
int VoltPin=A1;
int alarm;
int Signal=1;
float Spannung;
float R1=30000;
float R2=7500;
float Vout;
float Vin;
//SCK-> PIN13, MISO->PIN12, MOSI->PIN11
const int CEPin=7;
const int CSNPin=8;
RF24 radio(CEPin,CSNPin); //CE, CSN
const byte address[6] = "00001";
void Startbildschirm(){
display.clearDisplay(); //Display löschen
display.setTextColor(SH110X_WHITE); //Textfarbe
display.setTextSize(2); //Textgröße
display.setCursor(25,5);
display.print("Battery");
display.setCursor(35,35);
display.print("Guard");
display.display();
}
void Anzeige(){
display.clearDisplay(); //Display löschen
display.setTextColor(SH110X_WHITE); //Textfarbe
display.setTextSize(2); //Textgröße
display.setCursor(20,5);
display.print("Voltage:");
display.setCursor(30,35);
display.print(Vin);
display.setCursor(100,35);
display.print("V");
display.display();
}
void Anzeige2(){
display.clearDisplay(); //Display löschen
display.setTextColor(SH110X_WHITE); //Textfarbe
display.setTextSize(2); //Textgröße
display.setCursor(35,25);
display.print("Alarm!");
display.display();
}
void setup() {
Serial.begin(9600);
Wire.begin(); //SDA -> A4, CLK -> A5
display.begin(i2c_Address, true);
Startbildschirm();
delay(5000);
pinMode(RelaisPin,OUTPUT);
pinMode(VoltPin,INPUT);
radio.begin();
radio.openWritingPipe(address);
radio.setPALevel(RF24_PA_LOW);
radio.stopListening();
}
void loop() {
Spannung=analogRead(VoltPin);
Vout=Spannung*5/1024;
Vin=Vout/(R2/(R1+R2));
while(Vin>10.5){
Spannung=analogRead(VoltPin);
Vout=Spannung*5/1024;
Vin=Vout/(R2/(R1+R2));
Anzeige();
delay(1000);
}
digitalWrite(RelaisPin,HIGH);
Anzeige2();
alarm=1;
while(alarm==1){
if (Signal==1){
Signal=0;
}
else {
Signal=1;
}
radio.write(&Signal, sizeof(Signal));
delay(1000);
Serial.println(Signal);
Serial.println("Sende");
}
}

11
Batteriewaechter_Sender/test/README Normal file
View File

@@ -0,0 +1,11 @@
This directory is intended for PlatformIO Unit Testing 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/page/plus/unit-testing.html