Minor updates to docs
This commit is contained in:
@ -4,18 +4,21 @@ Functionallity
|
||||
The main differences
|
||||
--------------------
|
||||
|
||||
* **Operates in two modes `gravity monitoring` and `configuration mode`**
|
||||
* **Operates in two modes gravity monitoring and configuration mode**
|
||||
|
||||
In gravity monitoring mode it behaves just like the iSpindle, it wakes up at regular intervals, measure angle/tile, temperature, calculates gravity and pushes the data to defined endpoints.
|
||||
In ``gravity monitoring`` mode it behaves just like the iSpindle, it wakes up at regular intervals, measure angle/tile, temperature, calculates gravity and pushes the data to defined endpoints.
|
||||
|
||||
In configuration mode the device is always active and the webserver is active. Here you can view the angle/tilt values, change configuration options and more. When in this mode you can also interact with the device
|
||||
via an REST API so data can be pushed to the device via scripts (see API section for more information)-
|
||||
In ``configuration mode`` the device is always active and the webserver is active. Here you can view the angle/tilt values, change configuration options and more. When in this mode you can also interact with the device
|
||||
via an REST API so data can be pushed to the device via scripts (see API section for more information)
|
||||
|
||||
You can force the device into ``configuration mode`` while measuring gravity. This is useful when calibrating the device so you dont needs to wait for the device to wake up and push the data. The entire calibration
|
||||
sequence can be handled via the web interface without need for additional software tools.
|
||||
|
||||
*See the configuration section for more information on how to trigger the configuration mode.*
|
||||
|
||||
* **Can send data to multiple endpoints at once**
|
||||
|
||||
The orignial iSpindle can only have one destination, this sofware will push data to all defined endpoints so in theory you can use them all. However this will consume a lot of battery power so use only as many as needed.
|
||||
The original iSpindle can only have one destination, this software will push data to all defined endpoints so in theory you can use them all. However this will consume a lot of battery power so use only as many as needed.
|
||||
|
||||
Currently the device supports the following endpoints: http (2 differnt), influxdb2 and Brewfather
|
||||
|
||||
@ -73,10 +76,19 @@ Experimental features
|
||||
|
||||
*See the compile section for more information.*
|
||||
|
||||
Typical performance
|
||||
-------------------
|
||||
|
||||
Since I have the possibility to measaure the performance of different function in the code this is what I have been able to gather.
|
||||
Battery life
|
||||
------------
|
||||
|
||||
I'm currently measuring battery life of v0.5 but previous versions have been able to measure gravity for a 2-3 weeks without issues. Using 900 seconds as interval.
|
||||
|
||||
*More on this topics once my tests are done*
|
||||
|
||||
|
||||
Performance
|
||||
-----------
|
||||
|
||||
Since I have the possibility to measure the performance of different function in the code this is what I have been able to gather.
|
||||
|
||||
The typical runtime in a measurement cycle is approx 2 seconds and in some cases it can take up to 6-8 seconds but this is mainly related to establishing the WIFI connection. So stable wifi is
|
||||
essential for long batterylife. Out of the 2 seconds of run-time the major time is spent on gyro readings (1.3s) and temperature measurements of (0.6s) so using the gyro sensor for measureing
|
||||
|
@ -11,8 +11,8 @@ Welcome to GravityMon's documentation!
|
||||
Preliminary documentation. This is work in progress. This documentation reflects **v0.5**
|
||||
|
||||
|
||||
GravityMon is a replacement firmare for the iSpindle hardware. It's used to measure gravity in beer and show the progress
|
||||
of fermentation.
|
||||
GravityMon is a replacement firmare for the iSpindle firmware, it uses the same hardware configuration so
|
||||
you can easily switch between them. It's used to measure gravity in beer and show the progress of fermentation.
|
||||
|
||||
For more information on this topic and function please visit https://www.ispindel.de.
|
||||
|
||||
@ -35,7 +35,7 @@ be found here; https://github.com/mp-se/gravitymon
|
||||
The main differences:
|
||||
---------------------
|
||||
|
||||
* Operates in two modes `gravity monitoring` and `configuration mode`
|
||||
* Operates in two modes ``gravity monitoring`` and ``configuration mode``
|
||||
* Send data to multiple endpoints when pushing data.
|
||||
* Automatic temperature adjustment of gravity reading
|
||||
* OTA support from local webserver
|
||||
|
@ -9,7 +9,11 @@ here; https://docs.espressif.com/projects/esptool/en/latest/esp32/
|
||||
|
||||
The basic command for flashing on Windows is;
|
||||
|
||||
``esptool.py --port COM4 write_flash 0x0 firmware.bin``
|
||||
``esptool.py --port COM4 write_flash 0 firmware.bin``
|
||||
|
||||
If there are issues you can try do erase the flash first using this command;
|
||||
|
||||
``esptool.py --port COM4 erase_flash``
|
||||
|
||||
In the /bin directory you will find 3 different firmware builds;
|
||||
|
||||
|
Reference in New Issue
Block a user