From e2f972bbc0a1824ab351d63532ce969aed988b71 Mon Sep 17 00:00:00 2001 From: Magnus Date: Sat, 19 Nov 2022 13:57:16 +0100 Subject: [PATCH] Document updates --- src_docs/source/compiling.rst | 1 + src_docs/source/configuration.rst | 2 +- src_docs/source/functionality.rst | 39 +++++++++++++++++++++++++------ src_docs/source/index.rst | 4 ++-- src_docs/source/releases.rst | 4 ++-- 5 files changed, 38 insertions(+), 12 deletions(-) diff --git a/src_docs/source/compiling.rst b/src_docs/source/compiling.rst index a1e02e2..ef1f668 100644 --- a/src_docs/source/compiling.rst +++ b/src_docs/source/compiling.rst @@ -32,6 +32,7 @@ In the platformio config there are 3 targets defined * gravity32-release: Version for ESP32 mini. * gravity32-c3-release: Version for ESP32 C3 mini. * gravity32-s2-release: Version for ESP32 S2 mini. +* gravity32-lite-release: Version for ESP32 lite (Floaty hardware). .. warning:: The debug target can be unstable and crash the device under certain circumstanses. Excessive logging to the serial port can cause corruption and crashes. diff --git a/src_docs/source/configuration.rst b/src_docs/source/configuration.rst index 082a7c8..d6e391c 100644 --- a/src_docs/source/configuration.rst +++ b/src_docs/source/configuration.rst @@ -10,7 +10,7 @@ One of the following conditions will place the device in ``configuration mode``: - Gyro has not been calibrated - Sleep mode has been disabled in the web interface - Placed in horizontal mode 85-90 degrees -- Charger connected >4.15V (or the value that is configured) +- Charger connected >4.15V (or the value that is configured). This does not work on the Floaty variant due to lack of hardware support. Status diff --git a/src_docs/source/functionality.rst b/src_docs/source/functionality.rst index 695a580..0d49618 100644 --- a/src_docs/source/functionality.rst +++ b/src_docs/source/functionality.rst @@ -157,20 +157,45 @@ The main features See the :ref:`compiling-the-software` for more information. -* **Power measurements** - - I've also create a project to measure the power consumption of the device, but more on this later. - Battery life ------------ -The long term battery test has now been completed. Using a 2200 mA battery and sending data every 5 minutes to a local server on my network. The battery lasted 47 days which is excellent battery life. +For the 1.2 version I have been running some long term battery tests on a few of the boards and also comparing wifi vs Bluetooth. I was using a standard 2200 mA battery +that was fully charged at the start of the tests. All devices started with factory settings with only a change in push destination and sleep interval. -In another test I had a device running with an sleep interval of only 30s with ok wifi connection. The device lasted 12 days which i think is excellent considering the short sleep interval. +For the wifi tests, I was pushing data every 30 seconds to a local influxdb2 server to reduce errors connected to slow response on the server side. The devices +was placed 2 meters from the wifi AP to ensure a good and stable wifi connection (so ideal conditions). -From what I have discovered it's the WIFI connection or latency to internet hosted that has the most impact on the battery life. The typical runtime in the tests above was around 2 seconds. +For the Bluetooth tests I was pusing data every 10 seconds to a linux server. +To make this comparable I measured how many times the device was able to wake up and push data before the battery was dead. I theory the power consumption when in +deep sleep is to low it can almost be ignored for the calculations. So the impact on battery is mainly caused by how long the device is awake. In the most optimal case +this can be as low as 1.5-2.0 seconds but in reality its probably around 3-4 seconds. Wifi consumes a lot of power so Bluetooth is a better option for long battery life. + +.. list-table:: Battery power + :widths: 30 20 20 20 + :header-rows: 1 + + * - Device + - Transmissions + - 30s + - 300s / 15min + * - ESP 8266 (wifi) + - 26,000 + - 9 days + - 90 days + * - ESP32 c3 (wifi) + - 12,000 + - 4 days + - 43 days + * - ESP32 d1 (ble) + - 56,000 + - 20 days + - 196 days + + +As you can see from the table above there is quite some differences between the boards and connection methods. Performance ----------- diff --git a/src_docs/source/index.rst b/src_docs/source/index.rst index 48df0c6..e76969a 100644 --- a/src_docs/source/index.rst +++ b/src_docs/source/index.rst @@ -7,7 +7,7 @@ Welcome to GravityMon ##################### .. note:: - This documentation reflects **v1.2 - beta 2**. Last updated 2022-11-09 + This documentation reflects **v1.2 - beta 2**. Last updated 2022-11-19 What is GravityMon? -------------------- @@ -25,7 +25,7 @@ implements a lot of the features that has been requested in the original iSpindl various reasons. The firmware also supports a iSpindle built using an ESP32 which is pin compatible with esp8266, currently there are 3 options that are -supported ESP32-D1 mini, ESP32-C3 mini and ESP32-S2 mini. See :ref:`hardware`. The more modern hardware will allow better support for SSL and +supported ESP32-D1 mini, ESP32-C3 mini, ESP32-S2 mini, ESP32 lite (floaty). See :ref:`hardware`. The more modern hardware will allow better support for SSL and other memory intensive functions. I started GravityMon because I like to create software and wanted to do some microcontroller programming. I had done a few diff --git a/src_docs/source/releases.rst b/src_docs/source/releases.rst index c454bfb..22f4f74 100644 --- a/src_docs/source/releases.rst +++ b/src_docs/source/releases.rst @@ -8,12 +8,12 @@ v1.2.0 - beta2 Features ++++++++ -* Added option to calculate voltage factor based on measured reference value. +* Updated battery estimation for the various esp32 boards. * Added support for the ESP32 lite board which is used in the Floaty Hydrometer variant. Documentation +++++++++++++ -* Added section about the Floaty hardware +* Added section about the Floaty hardware. v1.2.0 - beta1