From caf947723e19a2cbe2a811c4096b723735295e9f Mon Sep 17 00:00:00 2001 From: Lyubomir Penev Date: Thu, 25 Sep 2025 13:49:04 +0200 Subject: [PATCH] Initialized --- .gitignore | 5 + .vscode/extensions.json | 10 ++ include/README | 37 ++++++++ lib/README | 46 +++++++++ platformio.ini | 14 +++ src/main.cpp | 206 ++++++++++++++++++++++++++++++++++++++++ test/README | 11 +++ 7 files changed, 329 insertions(+) create mode 100644 .gitignore create mode 100644 .vscode/extensions.json create mode 100644 include/README create mode 100644 lib/README create mode 100644 platformio.ini create mode 100644 src/main.cpp create mode 100644 test/README 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..58921d4 --- /dev/null +++ b/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:nano_33_iot] +platform = atmelsam +board = nano_33_iot +framework = arduino diff --git a/src/main.cpp b/src/main.cpp new file mode 100644 index 0000000..a8d5d21 --- /dev/null +++ b/src/main.cpp @@ -0,0 +1,206 @@ +#include + +int USER_STEPS = 5; +int STAFF_STEPS = 25; + +int maxVolume = 100; +int userVolume = 100; +int potPosition = 64; +int oldUserVolume = userVolume; + +void volumeUp(); +void volumeDown(); + +void setup() +{ + pinMode(11, OUTPUT); // Green + pinMode(12, OUTPUT); // Red LED (D4) + pinMode(LED_BUILTIN, OUTPUT); // Green LED + + pinMode(2, INPUT); // SW1 + pinMode(4, INPUT); // SW2 + + // RF Receiver + pinMode(A0, INPUT); // Remote Button D + pinMode(A1, INPUT); // Remote Button C + pinMode(A2, INPUT); // Remote Button B + pinMode(A3, INPUT); // Remote Button A + + pinMode(10, OUTPUT); // D10 - CS + pinMode(9, OUTPUT); // D9 - U/D + digitalWrite(10, HIGH); + digitalWrite(9, LOW); + + for (int i = 0; i < 64; i++) + { + volumeUp(); + } +} + +void loop() +{ + switch (maxVolume) + { + case 100: + digitalWrite(11, HIGH); + digitalWrite(12, LOW); + digitalWrite(LED_BUILTIN, LOW); + break; + case 75: + digitalWrite(11, LOW); + digitalWrite(12, HIGH); + digitalWrite(LED_BUILTIN, LOW); + break; + case 50: + digitalWrite(11, LOW); + digitalWrite(12, LOW); + digitalWrite(LED_BUILTIN, HIGH); + break; + case 25: + digitalWrite(11, HIGH); + digitalWrite(12, HIGH); + digitalWrite(LED_BUILTIN, HIGH); + break; + } + + // SW1 - Staff Volume Up + if (!digitalRead(2)) + { + if (maxVolume < 100) + { + maxVolume += STAFF_STEPS; + delay(300); + } + } + + // SW2 - Staff Volume Down + if (!digitalRead(4)) + { + if (maxVolume > 0) + { + maxVolume -= STAFF_STEPS; + + if (userVolume > maxVolume) + { + userVolume = maxVolume; + oldUserVolume = userVolume; + } + delay(300); + } + } + + // Remote D - Mute + if (digitalRead(A0)) + { + + // Check if we are in a muted state + if (oldUserVolume > userVolume) + { + if (oldUserVolume > maxVolume) + { + userVolume = maxVolume; + } + else + { + userVolume = oldUserVolume; + } + } + else + { + oldUserVolume = userVolume; + userVolume = 0; + } + + delay(300); + } + + // Remote A - Significantly Lower Volume + if (digitalRead(A3)) + { + if (oldUserVolume > userVolume) + { + if (oldUserVolume > maxVolume) + { + userVolume = maxVolume; + } + else + { + userVolume = oldUserVolume; + } + } + else + { + oldUserVolume = userVolume; + userVolume = 15; + } + + delay(300); + } + + // Remote B - Volume Up + if (digitalRead(A2) && !(oldUserVolume > userVolume)) + { + volumeUp(); + + if ((userVolume + USER_STEPS) > maxVolume) + { + userVolume = maxVolume; + oldUserVolume = userVolume; + } + else + { + userVolume += USER_STEPS; + oldUserVolume = userVolume; + } + + delay(300); + } + + // Remote C - Volume Down + if (digitalRead(A1) && !(oldUserVolume > userVolume)) + { + volumeDown(); + + if ((userVolume - USER_STEPS) < 0) + { + userVolume = 0; + oldUserVolume = userVolume; + } + else + { + userVolume -= USER_STEPS; + oldUserVolume = userVolume; + } + + delay(300); + } +} + +void volumeUp() +{ + digitalWrite(9, HIGH); + delay(1); + digitalWrite(10, LOW); + delay(1); + digitalWrite(9, LOW); + delay(1); + digitalWrite(9, HIGH); + delay(1); + digitalWrite(10, HIGH); + delay(1); + digitalWrite(9, LOW); + digitalWrite(10, HIGH); +} + +void volumeDown() +{ + digitalWrite(9, LOW); + delay(1); + digitalWrite(10, LOW); + delay(1); + digitalWrite(9, HIGH); + delay(1); + digitalWrite(9, LOW); + delay(1); + digitalWrite(10, HIGH); +} \ 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