initial import

Author: peterhalicky

.gitignore

@@ -0,0 +1,5 @@
+.pio
+CMakeListsPrivate.txt
+cmake-build-*/ 
+.idea
+*.iml

CMakeLists.txt

@@ -0,0 +1,33 @@
+# !!! WARNING !!! AUTO-GENERATED FILE, PLEASE DO NOT MODIFY IT AND USE
+# https://docs.platformio.org/page/projectconf/section_env_build.html#build-flags
+#
+# If you need to override existing CMake configuration or add extra,
+# please create `CMakeListsUser.txt` in the root of project.
+# The `CMakeListsUser.txt` will not be overwritten by PlatformIO.
+
+cmake_minimum_required(VERSION 3.13)
+set(CMAKE_SYSTEM_NAME Generic)
+set(CMAKE_C_COMPILER_WORKS 1)
+set(CMAKE_CXX_COMPILER_WORKS 1)
+
+project("oxyan" C CXX)
+
+include(CMakeListsPrivate.txt)
+
+if(EXISTS ${CMAKE_CURRENT_SOURCE_DIR}/CMakeListsUser.txt)
+include(CMakeListsUser.txt)
+endif()
+
+add_custom_target(
+    Production ALL
+    COMMAND platformio -c clion run "$<$<NOT:$<CONFIG:All>>:-e${CMAKE_BUILD_TYPE}>"
+    WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}
+)
+
+add_custom_target(
+    Debug ALL
+    COMMAND platformio -c clion debug "$<$<NOT:$<CONFIG:All>>:-e${CMAKE_BUILD_TYPE}>"
+    WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}
+)
+
+add_executable(Z_DUMMY_TARGET ${SRC_LIST})

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

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

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:leonardo]
+platform = atmelavr
+board = leonardo
+framework = arduino
+lib_deps =
+    mathertel/LiquidCrystal_PCF8574 @ ^2.1.0
+    adafruit/Adafruit ADS1X15 @ ^2.4.0

src/main.cpp

@@ -0,0 +1,74 @@
+#include <Arduino.h>
+#include <SPI.h>
+#include <LiquidCrystal_PCF8574.h>
+#include <Adafruit_ADS1X15.h>
+
+#define CAL_COUNT 100
+#define AIR_PCT 20.9
+
+LiquidCrystal_PCF8574 lcd(0x27);
+Adafruit_ADS1115 ads;
+bool isError = false;
+double airMv = 10;
+
+int cmpint16(const void *a, const void *b) {
+    return (*(int16_t *) a - *(int16_t *) b);
+}
+
+void calibrate() {
+    int16_t measurements[CAL_COUNT];
+    for (int &measurement: measurements) {
+        measurement = ads.readADC_Differential_0_1();
+    }
+
+    qsort(measurements, CAL_COUNT, sizeof(int16_t), cmpint16);
+    int32_t sum = 0;
+    int16_t count = 0;
+    for (int i = CAL_COUNT / 10; i < CAL_COUNT - (CAL_COUNT / 10); i++) {
+        sum += measurements[i];
+        count++;
+    }
+
+    auto airAdc = (int16_t)((double)sum / count);
+    airMv = ads.computeVolts(airAdc) * 1000;
+}
+
+void setup() {
+    lcd.begin(16, 2);
+    lcd.setBacklight(255);
+    lcd.home();
+    lcd.clear();
+
+    if (!ads.begin()) {
+        lcd.print("Error initializing ADS1115");
+        isError = true;
+    }
+
+    ads.setGain(GAIN_SIXTEEN);
+    calibrate();
+}
+
+void loop() {
+    if (isError) {
+        delay(100);
+        return;
+    }
+
+    int16_t adcSensor = ads.readADC_Differential_0_1();
+
+    double nowMv = ads.computeVolts(adcSensor) * 1000;
+
+    lcd.clear();
+    lcd.home();
+    lcd.print(nowMv);
+    lcd.print("mV");
+
+    double nowPct = (AIR_PCT / airMv) * nowMv;
+
+    lcd.setCursor(0, 1);
+
+    lcd.print(nowPct);
+    lcd.print("%");
+
+    delay(200);
+}

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