diff --git a/Batteriewaechter_Reciever/.gitignore b/Batteriewaechter_Reciever/.gitignore new file mode 100644 index 0000000..89cc49c --- /dev/null +++ b/Batteriewaechter_Reciever/.gitignore @@ -0,0 +1,5 @@ +.pio +.vscode/.browse.c_cpp.db* +.vscode/c_cpp_properties.json +.vscode/launch.json +.vscode/ipch diff --git a/Batteriewaechter_Reciever/.vscode/extensions.json b/Batteriewaechter_Reciever/.vscode/extensions.json new file mode 100644 index 0000000..080e70d --- /dev/null +++ b/Batteriewaechter_Reciever/.vscode/extensions.json @@ -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" + ] +} diff --git a/Batteriewaechter_Reciever/include/README b/Batteriewaechter_Reciever/include/README new file mode 100644 index 0000000..194dcd4 --- /dev/null +++ b/Batteriewaechter_Reciever/include/README @@ -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 diff --git a/Batteriewaechter_Reciever/lib/README b/Batteriewaechter_Reciever/lib/README new file mode 100644 index 0000000..6debab1 --- /dev/null +++ b/Batteriewaechter_Reciever/lib/README @@ -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 +#include + +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 diff --git a/Batteriewaechter_Reciever/platformio.ini b/Batteriewaechter_Reciever/platformio.ini new file mode 100644 index 0000000..bff5e79 --- /dev/null +++ b/Batteriewaechter_Reciever/platformio.ini @@ -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 diff --git a/Batteriewaechter_Reciever/src/main.cpp b/Batteriewaechter_Reciever/src/main.cpp new file mode 100644 index 0000000..1f4e09c --- /dev/null +++ b/Batteriewaechter_Reciever/src/main.cpp @@ -0,0 +1,45 @@ +#include +#include +#include +#include + +//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); + } + } +} diff --git a/Batteriewaechter_Reciever/test/README b/Batteriewaechter_Reciever/test/README new file mode 100644 index 0000000..9b1e87b --- /dev/null +++ b/Batteriewaechter_Reciever/test/README @@ -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 diff --git a/Batteriewaechter_Sender/.gitignore b/Batteriewaechter_Sender/.gitignore new file mode 100644 index 0000000..89cc49c --- /dev/null +++ b/Batteriewaechter_Sender/.gitignore @@ -0,0 +1,5 @@ +.pio +.vscode/.browse.c_cpp.db* +.vscode/c_cpp_properties.json +.vscode/launch.json +.vscode/ipch diff --git a/Batteriewaechter_Sender/.vscode/extensions.json b/Batteriewaechter_Sender/.vscode/extensions.json new file mode 100644 index 0000000..080e70d --- /dev/null +++ b/Batteriewaechter_Sender/.vscode/extensions.json @@ -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" + ] +} diff --git a/Batteriewaechter_Sender/include/README b/Batteriewaechter_Sender/include/README new file mode 100644 index 0000000..194dcd4 --- /dev/null +++ b/Batteriewaechter_Sender/include/README @@ -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 diff --git a/Batteriewaechter_Sender/lib/README b/Batteriewaechter_Sender/lib/README new file mode 100644 index 0000000..6debab1 --- /dev/null +++ b/Batteriewaechter_Sender/lib/README @@ -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 +#include + +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 diff --git a/Batteriewaechter_Sender/platformio.ini b/Batteriewaechter_Sender/platformio.ini new file mode 100644 index 0000000..4895a19 --- /dev/null +++ b/Batteriewaechter_Sender/platformio.ini @@ -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 diff --git a/Batteriewaechter_Sender/src/main.cpp b/Batteriewaechter_Sender/src/main.cpp new file mode 100644 index 0000000..a6efafa --- /dev/null +++ b/Batteriewaechter_Sender/src/main.cpp @@ -0,0 +1,114 @@ +#include +#include +#include +#include +#include +#include +#include + +#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"); + } + } \ No newline at end of file diff --git a/Batteriewaechter_Sender/test/README b/Batteriewaechter_Sender/test/README new file mode 100644 index 0000000..b94d089 --- /dev/null +++ b/Batteriewaechter_Sender/test/README @@ -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