init commit

.gitignore

@@ -0,0 +1,5 @@
+.pio
+.vscode/.browse.c_cpp.db*
+.vscode/c_cpp_properties.json
+.vscode/launch.json
+.vscode/ipch

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

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

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 <Foo.h>
+#include <Bar.h>
+
+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

platformio.ini

@@ -0,0 +1,17 @@
+; 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:esp01_1m]
+platform = espressif8266
+board = esp01_1m
+framework = arduino
+lib_deps = 
+	gioblu/PJON@^13.1
+	bblanchon/ArduinoJson@^7.4.2

src/main.cpp

@@ -0,0 +1,104 @@
+#include <Arduino.h>
+#include<PJON.h>
+#include <PJONAny.h>
+#include <PJONSoftwareBitBang.h>
+
+#define RECEIVER 1
+#define SBBPIN 12
+
+String topic = "pjon/44";
+
+// put function declarations here:
+
+void publishMqtt(PJONAny, uint8_t, String, String );
+void receiver_function(uint8_t , uint16_t length, const PJON_Packet_Info);
+void error_handler(uint8_t, uint16_t);
+long getDistance();
+
+
+// Strategy
+StrategyLink<SoftwareBitBang> link;
+
+
+// Bus Address
+PJONAny bus(44);
+
+// Ultraschallsensor Pins
+const int trigPin = 5;   // z. B. GPIO5
+const int echoPin = 18;  // z. B. GPIO18
+
+
+struct mqttMessage {
+  uint8_t method; // 0: publish 1: subscribe
+  char topic[250];
+  char message[512];
+};
+
+mqttMessage receiveBuffer;
+bool receivedFlag = false;
+
+void setup() {
+  // put your setup code here, to run once:
+
+  link.strategy.set_pin(SBBPIN);
+  bus.strategy.set_link(&link);
+  bus.set_error(error_handler);
+  bus.set_receiver(receiver_function);
+  bus.begin();
+}
+
+void loop() {
+  // put your main code here, to run repeatedly:
+  bus.update();
+  publishMqtt(bus,RECEIVER, topic,String(getDistance()));
+
+  if (receivedFlag) {
+    receivedFlag = false;
+  }
+
+}
+
+
+long getDistance() {
+  digitalWrite(trigPin, LOW);
+  delayMicroseconds(2);
+  digitalWrite(trigPin, HIGH);
+  delayMicroseconds(10);
+  digitalWrite(trigPin, LOW);
+  long duration = pulseIn(echoPin, HIGH);
+  long distance = duration / 58; // Entfernung in cm
+  return distance;
+}
+
+
+
+
+
+
+
+
+
+
+// JSONMqtt funktions
+
+void publishMqtt(PJONAny bus, uint8_t destAddress, String topic, String message ){
+  mqttMessage mqMessage;
+  mqMessage.method = 0;
+  topic.toCharArray(mqMessage.topic, topic.length());
+  message.toCharArray(mqMessage.message, message.length());
+  bus.send(destAddress,&mqMessage,sizeof(mqMessage));
+}
+
+void receiver_function(uint8_t *payload, uint16_t length, const PJON_Packet_Info &packet_info) {
+
+  /* Copy received data in buffer */
+  memcpy(&receiveBuffer, payload, sizeof(receiveBuffer));
+  receivedFlag = true;
+
+};
+void error_handler(uint8_t code, uint16_t data, void *custom_pointer) {
+  if(code == PJON_CONNECTION_LOST) {
+    Serial.print("Connection lost with device id ");
+    Serial.println(bus.packets[data].content[0], DEC);
+  }
+};

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