commit 6a2c1eeb3e15a02e0e250a7716851bc76ea6686d Author: Daniel Date: Thu Apr 16 15:16:23 2026 +0200 Initilize diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..89cc49c --- /dev/null +++ b/.gitignore @@ -0,0 +1,5 @@ +.pio +.vscode/.browse.c_cpp.db* +.vscode/c_cpp_properties.json +.vscode/launch.json +.vscode/ipch diff --git a/.vscode/extensions.json b/.vscode/extensions.json new file mode 100644 index 0000000..080e70d --- /dev/null +++ b/.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/include/README b/include/README new file mode 100644 index 0000000..49819c0 --- /dev/null +++ b/include/README @@ -0,0 +1,37 @@ + +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 convention is to give header files names that end with `.h'. + +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/lib/README b/lib/README new file mode 100644 index 0000000..9379397 --- /dev/null +++ b/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 the executable file. + +The source code of each library should be placed in a separate directory +("lib/your_library_name/[Code]"). + +For example, see the structure of the following example libraries `Foo` and `Bar`: + +|--lib +| | +| |--Bar +| | |--docs +| | |--examples +| | |--src +| | |- Bar.c +| | |- Bar.h +| | |- library.json (optional. for 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 + +Example contents of `src/main.c` using Foo and Bar: +``` +#include +#include + +int main (void) +{ + ... +} + +``` + +The PlatformIO Library Dependency Finder will find automatically dependent +libraries by scanning project source files. + +More information about PlatformIO Library Dependency Finder +- https://docs.platformio.org/page/librarymanager/ldf.html diff --git a/platformio.ini b/platformio.ini new file mode 100644 index 0000000..6147e54 --- /dev/null +++ b/platformio.ini @@ -0,0 +1,21 @@ +; 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:receiver] +platform = espressif32 +board = esp32-s3-devkitc-1 +framework = arduino + +monitor_speed = 115200 +upload_speed = 921600 +upload_protocol = esptool + +lib_deps = + jgromes/RadioLib \ No newline at end of file diff --git a/src/main.cpp b/src/main.cpp new file mode 100644 index 0000000..d206217 --- /dev/null +++ b/src/main.cpp @@ -0,0 +1,103 @@ +#include +#include +#include + +// ========================= +// Heltec WiFi LoRa 32 V3 / ESP32-S3 + SX1262 +// ========================= +static const int LORA_CS = 8; +static const int LORA_DIO1 = 14; +static const int LORA_RST = 12; +static const int LORA_BUSY = 13; + +// Typische SPI-Pins auf dem Heltec V3 +static const int LORA_SCK = 9; +static const int LORA_MISO = 11; +static const int LORA_MOSI = 10; + +SX1262 radio = new Module(LORA_CS, LORA_DIO1, LORA_RST, LORA_BUSY); + +// ========================= +// Ausgaenge +// ========================= +static const int BUZZER_PIN = 4; +static const int LED_PIN = 5; + +// Tone/LEDC fuer ESP32 +static const int BUZZER_CHANNEL = 0; +static const int BUZZER_RESOLUTION = 8; + +void alarmOutput(uint16_t durationMs = 1500) { + digitalWrite(LED_PIN, HIGH); + ledcWriteTone(BUZZER_CHANNEL, 2000); // 2 kHz + + delay(durationMs); + + ledcWriteTone(BUZZER_CHANNEL, 0); + digitalWrite(LED_PIN, LOW); +} + +void setup() { + Serial.begin(115200); + delay(2000); + + Serial.println(); + Serial.println("=== Empfaenger startet ==="); + + pinMode(LED_PIN, OUTPUT); + digitalWrite(LED_PIN, LOW); + + ledcSetup(BUZZER_CHANNEL, 2000, BUZZER_RESOLUTION); + ledcAttachPin(BUZZER_PIN, BUZZER_CHANNEL); + ledcWriteTone(BUZZER_CHANNEL, 0); + + SPI.begin(LORA_SCK, LORA_MISO, LORA_MOSI, LORA_CS); + + int state = radio.begin(868.0); + if (state != RADIOLIB_ERR_NONE) { + Serial.print("LoRa init fehlgeschlagen, Code: "); + Serial.println(state); + while (true) { + delay(1000); + } + } + + radio.setBandwidth(125.0); + radio.setSpreadingFactor(9); + radio.setCodingRate(5); + radio.setOutputPower(10); + radio.setCurrentLimit(80.0); + radio.setCRC(true); + + Serial.println("LoRa bereit."); + Serial.println("Warte auf Nachrichten..."); +} + +void loop() { + String msg; + int state = radio.receive(msg); + + if (state == RADIOLIB_ERR_NONE) { + Serial.println("Empfang: JA"); + Serial.print("Nachricht: "); + Serial.println(msg); + + Serial.print("RSSI: "); + Serial.print(radio.getRSSI()); + Serial.println(" dBm"); + + Serial.print("SNR: "); + Serial.print(radio.getSNR()); + Serial.println(" dB"); + + if (msg == "ALARM") { + Serial.println("ALARM erkannt -> LED + Summer AN"); + alarmOutput(); + } + + Serial.println("-------------------------"); + } else if (state != RADIOLIB_ERR_RX_TIMEOUT) { + Serial.print("Empfangsfehler, Code: "); + Serial.println(state); + } +} \ No newline at end of file diff --git a/test/README b/test/README new file mode 100644 index 0000000..9b1e87b --- /dev/null +++ b/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