Erstes Commit ...

vscode/RamsachMp3Glocke/.gitignore

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

vscode/RamsachMp3Glocke/.vscode/extensions.json

@@ -0,0 +1,7 @@
+{
+    // See http://go.microsoft.com/fwlink/?LinkId=827846
+    // for the documentation about the extensions.json format
+    "recommendations": [
+        "platformio.platformio-ide"
+    ]
+}

vscode/RamsachMp3Glocke/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

vscode/RamsachMp3Glocke/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 <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

vscode/RamsachMp3Glocke/platformio.ini

@@ -0,0 +1,16 @@
+; 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:d1_mini_pro]
+platform = espressif8266
+board = d1_mini_pro
+framework = arduino
+monitor_speed = 115200
+lib_deps = salvadorrueda/SerialMP3Player@^1.1.0

vscode/RamsachMp3Glocke/src/main.cpp

@@ -0,0 +1,100 @@
+#include "SerialMP3Player.h"
+
+#define TX D3
+#define RX D2
+#define BUTTON D1
+
+#define STARTED_STRING "Status: playing"
+#define STOPPED_STRING "Status: stopped"
+#define MAX_PLAYTIME 60000
+
+unsigned long lastpressed = 0;
+unsigned long pressed_cycles = 0;
+unsigned long lastreleased = 0;
+const unsigned long wait_until_next_pressed = 100;
+
+SerialMP3Player mp3(RX,TX);
+
+bool button_pressed(unsigned int button_pin){
+  static bool buttons_state = false;
+  if(millis() - lastpressed > wait_until_next_pressed)
+  {
+    if(digitalRead(button_pin) == LOW)
+    {
+      pressed_cycles++;
+      lastpressed = millis();
+      buttons_state = true;
+    }
+    else{
+      pressed_cycles = 0;
+      lastreleased = millis();
+      buttons_state = false;
+    }
+  }
+  return(buttons_state);
+}
+
+void setup() {
+  Serial.begin(115200);     // start serial interface
+  pinMode(BUTTON,INPUT_PULLUP);
+
+  mp3.begin(9600);        // start mp3-communication
+  delay(500);             // wait for init
+
+  mp3.sendCommand(CMD_SEL_DEV, 0, 2);   //select sd-card
+  delay(500);             // wait for init
+  mp3.setVol(30);
+}
+
+// the loop function runs over and over again forever
+unsigned long started_plying = 0;
+bool playing = false;
+void loop() {
+  
+ 
+  if(true == button_pressed(BUTTON))
+  {
+    playing = false;
+    mp3.play(1);
+    started_plying = millis(); 
+    Serial.println("");          
+    Serial.println("Song playing started!");
+    while((playing == false) && (millis()-started_plying < MAX_PLAYTIME))
+    {
+      delay(100);
+      mp3.qStatus();
+      if (mp3.available()){
+        String answer = mp3.decodeMP3Answer();
+        if(answer.indexOf(STARTED_STRING) > -1)
+        {
+          playing = true;
+          Serial.println("Song started!");
+        }
+      }
+    }
+
+    while((playing == true) && (millis()-started_plying < MAX_PLAYTIME))
+    {
+      delay(100);
+      mp3.qStatus();
+      if (mp3.available()){
+        String answer = mp3.decodeMP3Answer();
+        if(answer.indexOf(STOPPED_STRING) > -1)
+        {
+          playing = false;
+          Serial.println("Song finished!");
+        }
+
+      }
+    }
+
+    if(playing == true)
+      mp3.stop();
+    Serial.println("Song playing done!");
+
+    while(true == button_pressed(BUTTON))
+    {
+        delay(100);
+    }
+  }
+}

vscode/RamsachMp3Glocke/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