commit 51e983a98e6927af48689eb5674dda13cd9fe401 Author: Tropicananass Date: Mon Jan 21 19:14:11 2019 +0100 Initial commit diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..f152028 --- /dev/null +++ b/.gitignore @@ -0,0 +1,5 @@ +.pio +.pioenvs +.piolibdeps +.clang_complete +.gcc-flags.json diff --git a/.travis.yml b/.travis.yml new file mode 100644 index 0000000..7c486f1 --- /dev/null +++ b/.travis.yml @@ -0,0 +1,67 @@ +# Continuous Integration (CI) is the practice, in software +# engineering, of merging all developer working copies with a shared mainline +# several times a day < https://docs.platformio.org/page/ci/index.html > +# +# Documentation: +# +# * Travis CI Embedded Builds with PlatformIO +# < https://docs.travis-ci.com/user/integration/platformio/ > +# +# * PlatformIO integration with Travis CI +# < https://docs.platformio.org/page/ci/travis.html > +# +# * User Guide for `platformio ci` command +# < https://docs.platformio.org/page/userguide/cmd_ci.html > +# +# +# Please choose one of the following templates (proposed below) and uncomment +# it (remove "# " before each line) or use own configuration according to the +# Travis CI documentation (see above). +# + + +# +# Template #1: General project. Test it using existing `platformio.ini`. +# + +# language: python +# python: +# - "2.7" +# +# sudo: false +# cache: +# directories: +# - "~/.platformio" +# +# install: +# - pip install -U platformio +# - platformio update +# +# script: +# - platformio run + + +# +# Template #2: The project is intended to be used as a library with examples. +# + +# language: python +# python: +# - "2.7" +# +# sudo: false +# cache: +# directories: +# - "~/.platformio" +# +# env: +# - PLATFORMIO_CI_SRC=path/to/test/file.c +# - PLATFORMIO_CI_SRC=examples/file.ino +# - PLATFORMIO_CI_SRC=path/to/test/directory +# +# install: +# - pip install -U platformio +# - platformio update +# +# script: +# - platformio ci --lib="." --board=ID_1 --board=ID_2 --board=ID_N diff --git a/include/README b/include/README new file mode 100644 index 0000000..194dcd4 --- /dev/null +++ b/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/lib/README b/lib/README new file mode 100644 index 0000000..6debab1 --- /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 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/platformio.ini b/platformio.ini new file mode 100644 index 0000000..edd3068 --- /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:micro] +platform = atmelavr +board = micro +framework = arduino diff --git a/pro_micro_pinout.jpg b/pro_micro_pinout.jpg new file mode 100644 index 0000000..7030b90 Binary files /dev/null and b/pro_micro_pinout.jpg differ diff --git a/src/main.cpp b/src/main.cpp new file mode 100644 index 0000000..c6c0709 --- /dev/null +++ b/src/main.cpp @@ -0,0 +1,70 @@ +#include +// #include +#include + +#define s * 1000 +#define TOTAL_LINES 4 + +/* Pins */ +/* - analogs */ +unsigned char muxSignal{A1}; +/* - digitals */ +int muxSelector[TOTAL_LINES]{18, 14, 15, 16}; + +/* Components */ +// Multiplexer m(muxSignal, TOTAL_LINES, muxSelector); +AnalogMultiplex multiplexer(A1, {18, 14, 15, 16}); + + +/* Midi links */ +//USBDebugMIDI_Interface midiInterface(115200); + +Analog potentiometers[] = { + {multiplexer.pin(0), MIDI_CC::Channel_Volume, 1}, + {multiplexer.pin(1), MIDI_CC::Channel_Volume, 2}, + {multiplexer.pin(2), MIDI_CC::Channel_Volume, 3}, + {multiplexer.pin(3), MIDI_CC::Channel_Volume, 4} +}; + +/* Values */ +int val[16]; +int ref[16]; + +void setup() { + //Serial.begin(9600); + /*while (Serial.available() == 0){ + delay(.5 s); + }*/ + // for (size_t i = 0; i < 4; i++) { + // ref[i] = m.analogRead(i); + // } + pinMode(0, OUTPUT); + pinMode(1, OUTPUT); +} + +void loop() { + for (size_t i = 0; i < 4; i++) { + val[i] = multiplexer.analogRead(i); + if (val[i] != ref[i]) { + // Serial.print("p["); + // Serial.print(i, DEC); + // Serial.print("] = "); + // Serial.println(val[i], DEC); + ref[i] = val[i]; + + } + } + if (val[2] >= 500) { + digitalWrite(0, HIGH); + } else { + digitalWrite(0, LOW); + } + if (val[0] >= 500) { + digitalWrite(1, HIGH); + } else { + digitalWrite(1, LOW); + } + + MIDI_Controller.refresh(); + //delay(.5 s); +} diff --git a/test/README b/test/README new file mode 100644 index 0000000..df5066e --- /dev/null +++ b/test/README @@ -0,0 +1,11 @@ + +This directory is intended for PIO 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 PIO Unit Testing: +- https://docs.platformio.org/page/plus/unit-testing.html