Update documentation
This commit is contained in:
@ -42,7 +42,8 @@
|
||||
<li class="toctree-l2"><a class="reference internal" href="#the-main-differences">The main differences</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#other-features">Other features</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#experimental-features">Experimental features</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#typical-performance">Typical performance</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#battery-life">Battery life</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="#performance">Performance</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li class="toctree-l1"><a class="reference internal" href="installation.html">Installation</a></li>
|
||||
@ -81,14 +82,16 @@
|
||||
<div class="section" id="the-main-differences">
|
||||
<h2>The main differences<a class="headerlink" href="#the-main-differences" title="Permalink to this headline">¶</a></h2>
|
||||
<ul>
|
||||
<li><p><strong>Operates in two modes `gravity monitoring` and `configuration mode`</strong></p>
|
||||
<p>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.</p>
|
||||
<p>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)-</p>
|
||||
<li><p><strong>Operates in two modes gravity monitoring and configuration mode</strong></p>
|
||||
<p>In <code class="docutils literal notranslate"><span class="pre">gravity</span> <span class="pre">monitoring</span></code> 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.</p>
|
||||
<p>In <code class="docutils literal notranslate"><span class="pre">configuration</span> <span class="pre">mode</span></code> 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)</p>
|
||||
<p>You can force the device into <code class="docutils literal notranslate"><span class="pre">configuration</span> <span class="pre">mode</span></code> 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.</p>
|
||||
<p><em>See the configuration section for more information on how to trigger the configuration mode.</em></p>
|
||||
</li>
|
||||
<li><p><strong>Can send data to multiple endpoints at once</strong></p>
|
||||
<p>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.</p>
|
||||
<p>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.</p>
|
||||
<p>Currently the device supports the following endpoints: http (2 differnt), influxdb2 and Brewfather</p>
|
||||
<p>If you want additional targets please raise a feature request in the github repo.</p>
|
||||
</li>
|
||||
@ -143,9 +146,14 @@ However more testing is required. Might add this as an option in the UI.</p>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="section" id="typical-performance">
|
||||
<h2>Typical performance<a class="headerlink" href="#typical-performance" title="Permalink to this headline">¶</a></h2>
|
||||
<p>Since I have the possibility to measaure the performance of different function in the code this is what I have been able to gather.</p>
|
||||
<div class="section" id="battery-life">
|
||||
<h2>Battery life<a class="headerlink" href="#battery-life" title="Permalink to this headline">¶</a></h2>
|
||||
<p>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.</p>
|
||||
<p><em>More on this topics once my tests are done</em></p>
|
||||
</div>
|
||||
<div class="section" id="performance">
|
||||
<h2>Performance<a class="headerlink" href="#performance" title="Permalink to this headline">¶</a></h2>
|
||||
<p>Since I have the possibility to measure the performance of different function in the code this is what I have been able to gather.</p>
|
||||
<p>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
|
||||
temperature would reduce the total runtime with 25%. Sending data over http takes less than 100ms (on my local network) so this is not drawing much power.</p>
|
||||
|
Reference in New Issue
Block a user