From 36c4eafd108916d5faf9cc27f9742e1f1162df14 Mon Sep 17 00:00:00 2001 From: Ben Hastings Date: Wed, 10 Jan 2024 12:41:54 +0100 Subject: [PATCH] device 2 started --- .../mega-2560/BioSensor/.gitignore | 5 ++ .../mega-2560/BioSensor/README.md | 6 +++ .../mega-2560/BioSensor/include/README | 39 ++++++++++++++++ .../mega-2560/BioSensor/lib/README | 46 +++++++++++++++++++ .../mega-2560/BioSensor/platformio.ini | 14 ++++++ .../mega-2560/BioSensor/src/main.cpp | 42 +++++++++++++++++ .../mega-2560/BioSensor/test/README | 11 +++++ 7 files changed, 163 insertions(+) create mode 100644 workshops/arduino-programming/real-examples/mega-2560/BioSensor/.gitignore create mode 100644 workshops/arduino-programming/real-examples/mega-2560/BioSensor/README.md create mode 100644 workshops/arduino-programming/real-examples/mega-2560/BioSensor/include/README create mode 100644 workshops/arduino-programming/real-examples/mega-2560/BioSensor/lib/README create mode 100644 workshops/arduino-programming/real-examples/mega-2560/BioSensor/platformio.ini create mode 100644 workshops/arduino-programming/real-examples/mega-2560/BioSensor/src/main.cpp create mode 100644 workshops/arduino-programming/real-examples/mega-2560/BioSensor/test/README diff --git a/workshops/arduino-programming/real-examples/mega-2560/BioSensor/.gitignore b/workshops/arduino-programming/real-examples/mega-2560/BioSensor/.gitignore new file mode 100644 index 0000000..89cc49c --- /dev/null +++ b/workshops/arduino-programming/real-examples/mega-2560/BioSensor/.gitignore @@ -0,0 +1,5 @@ +.pio +.vscode/.browse.c_cpp.db* +.vscode/c_cpp_properties.json +.vscode/launch.json +.vscode/ipch diff --git a/workshops/arduino-programming/real-examples/mega-2560/BioSensor/README.md b/workshops/arduino-programming/real-examples/mega-2560/BioSensor/README.md new file mode 100644 index 0000000..89ec332 --- /dev/null +++ b/workshops/arduino-programming/real-examples/mega-2560/BioSensor/README.md @@ -0,0 +1,6 @@ + Reads a digital signal from a heart rate sensor and displays the value on a row of LEDs as an intensity guage. + + The data is also written to an SD card, albeit at a different rate to which the LED array is updated. + + + ## Parts List \ No newline at end of file diff --git a/workshops/arduino-programming/real-examples/mega-2560/BioSensor/include/README b/workshops/arduino-programming/real-examples/mega-2560/BioSensor/include/README new file mode 100644 index 0000000..194dcd4 --- /dev/null +++ b/workshops/arduino-programming/real-examples/mega-2560/BioSensor/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/workshops/arduino-programming/real-examples/mega-2560/BioSensor/lib/README b/workshops/arduino-programming/real-examples/mega-2560/BioSensor/lib/README new file mode 100644 index 0000000..6debab1 --- /dev/null +++ b/workshops/arduino-programming/real-examples/mega-2560/BioSensor/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/workshops/arduino-programming/real-examples/mega-2560/BioSensor/platformio.ini b/workshops/arduino-programming/real-examples/mega-2560/BioSensor/platformio.ini new file mode 100644 index 0000000..67e8cb2 --- /dev/null +++ b/workshops/arduino-programming/real-examples/mega-2560/BioSensor/platformio.ini @@ -0,0 +1,14 @@ +; 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:megaatmega2560] +platform = atmelavr +board = megaatmega2560 +framework = arduino diff --git a/workshops/arduino-programming/real-examples/mega-2560/BioSensor/src/main.cpp b/workshops/arduino-programming/real-examples/mega-2560/BioSensor/src/main.cpp new file mode 100644 index 0000000..3aeffac --- /dev/null +++ b/workshops/arduino-programming/real-examples/mega-2560/BioSensor/src/main.cpp @@ -0,0 +1,42 @@ +#include + +const int numberOfLEDs = 2; +const int LEDArrayPins[] = {3, LED_BUILTIN}; + +const int Sensorpin = 13; + +void setup() { + for (byte i = 0; i < numberOfLEDs; i++){ // set LED pins as output + pinMode(LEDArrayPins[i], OUTPUT); + } + + Serial.begin(9600); +} + +void loop() { + // read digital value + const int maxValue = 200; + const int minValue = 50; + int digitalValue = 19;//random(minValue, maxValue); // simulate sensor with random number + + // scale digital value to between 0 and 1 + float scaledValue = (digitalValue - minValue)/float(maxValue); + + // determine number of LEDs to light + int numberToLight = scaledValue * numberOfLEDs + 1; + + // light up corresponging number of LEDs + for (byte i = 0; i < numberOfLEDs; i++){ //loop over LEDs + if (i < numberToLight){ + digitalWrite(LEDArrayPins[i], HIGH); + } + else{ + digitalWrite(LEDArrayPins[i], LOW); + } + } + String debugLine = "digitalValue: " + String(digitalValue) + " scaledValue: " + String(scaledValue) + " numberToLight: " + String(numberToLight); + Serial.println(debugLine); + + delay(5000); + } + diff --git a/workshops/arduino-programming/real-examples/mega-2560/BioSensor/test/README b/workshops/arduino-programming/real-examples/mega-2560/BioSensor/test/README new file mode 100644 index 0000000..9b1e87b --- /dev/null +++ b/workshops/arduino-programming/real-examples/mega-2560/BioSensor/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