mirror of
https://github.com/jomjol/AI-on-the-edge-device-docs.git
synced 2025-12-08 12:36:54 +03:00
Deployed 687e75e with MkDocs version: 1.5.3
This commit is contained in:
github-actions[bot]
@@ -9,9 +9,9 @@
|
||||
<link href="../Best-Practice/" rel="prev"/>
|
||||
<link href="../Reference-Image/" rel="next"/>
|
||||
<link href="../img/favicon.ico" rel="icon"/>
|
||||
<meta content="mkdocs-1.5.3, mkdocs-material-9.5.9" name="generator"/>
|
||||
<meta content="mkdocs-1.5.3, mkdocs-material-9.5.18" name="generator"/>
|
||||
<title>Frequently Asked Questions - AI on the Edge Device</title>
|
||||
<link href="../assets/stylesheets/main.f2e4d321.min.css" rel="stylesheet"/>
|
||||
<link href="../assets/stylesheets/main.66ac8b77.min.css" rel="stylesheet"/>
|
||||
<link href="../assets/stylesheets/palette.06af60db.min.css" rel="stylesheet"/>
|
||||
<link crossorigin="" href="https://fonts.gstatic.com" rel="preconnect"/>
|
||||
<link href="https://fonts.googleapis.com/css?family=Roboto:300,300i,400,400i,700,700i%7CRoboto+Mono:400,400i,700,700i&display=fallback" rel="stylesheet"/>
|
||||
@@ -86,7 +86,7 @@
|
||||
<div class="md-header__source">
|
||||
<a class="md-source" data-md-component="source" href="https://github.com/jomjol/AI-on-the-edge-device-docs" title="Go to repository">
|
||||
<div class="md-source__icon md-icon">
|
||||
<svg viewbox="0 0 448 512" xmlns="http://www.w3.org/2000/svg"><!--! Font Awesome Free 6.5.1 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2023 Fonticons, Inc.--><path d="M439.55 236.05 244 40.45a28.87 28.87 0 0 0-40.81 0l-40.66 40.63 51.52 51.52c27.06-9.14 52.68 16.77 43.39 43.68l49.66 49.66c34.23-11.8 61.18 31 35.47 56.69-26.49 26.49-70.21-2.87-56-37.34L240.22 199v121.85c25.3 12.54 22.26 41.85 9.08 55a34.34 34.34 0 0 1-48.55 0c-17.57-17.6-11.07-46.91 11.25-56v-123c-20.8-8.51-24.6-30.74-18.64-45L142.57 101 8.45 235.14a28.86 28.86 0 0 0 0 40.81l195.61 195.6a28.86 28.86 0 0 0 40.8 0l194.69-194.69a28.86 28.86 0 0 0 0-40.81z"></path></svg>
|
||||
<svg viewbox="0 0 448 512" xmlns="http://www.w3.org/2000/svg"><!--! Font Awesome Free 6.5.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M439.55 236.05 244 40.45a28.87 28.87 0 0 0-40.81 0l-40.66 40.63 51.52 51.52c27.06-9.14 52.68 16.77 43.39 43.68l49.66 49.66c34.23-11.8 61.18 31 35.47 56.69-26.49 26.49-70.21-2.87-56-37.34L240.22 199v121.85c25.3 12.54 22.26 41.85 9.08 55a34.34 34.34 0 0 1-48.55 0c-17.57-17.6-11.07-46.91 11.25-56v-123c-20.8-8.51-24.6-30.74-18.64-45L142.57 101 8.45 235.14a28.86 28.86 0 0 0 0 40.81l195.61 195.6a28.86 28.86 0 0 0 40.8 0l194.69-194.69a28.86 28.86 0 0 0 0-40.81z"></path></svg>
|
||||
</div>
|
||||
<div class="md-source__repository">
|
||||
GitHub
|
||||
@@ -111,7 +111,7 @@
|
||||
<div class="md-nav__source">
|
||||
<a class="md-source" data-md-component="source" href="https://github.com/jomjol/AI-on-the-edge-device-docs" title="Go to repository">
|
||||
<div class="md-source__icon md-icon">
|
||||
<svg viewbox="0 0 448 512" xmlns="http://www.w3.org/2000/svg"><!--! Font Awesome Free 6.5.1 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2023 Fonticons, Inc.--><path d="M439.55 236.05 244 40.45a28.87 28.87 0 0 0-40.81 0l-40.66 40.63 51.52 51.52c27.06-9.14 52.68 16.77 43.39 43.68l49.66 49.66c34.23-11.8 61.18 31 35.47 56.69-26.49 26.49-70.21-2.87-56-37.34L240.22 199v121.85c25.3 12.54 22.26 41.85 9.08 55a34.34 34.34 0 0 1-48.55 0c-17.57-17.6-11.07-46.91 11.25-56v-123c-20.8-8.51-24.6-30.74-18.64-45L142.57 101 8.45 235.14a28.86 28.86 0 0 0 0 40.81l195.61 195.6a28.86 28.86 0 0 0 40.8 0l194.69-194.69a28.86 28.86 0 0 0 0-40.81z"></path></svg>
|
||||
<svg viewbox="0 0 448 512" xmlns="http://www.w3.org/2000/svg"><!--! Font Awesome Free 6.5.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M439.55 236.05 244 40.45a28.87 28.87 0 0 0-40.81 0l-40.66 40.63 51.52 51.52c27.06-9.14 52.68 16.77 43.39 43.68l49.66 49.66c34.23-11.8 61.18 31 35.47 56.69-26.49 26.49-70.21-2.87-56-37.34L240.22 199v121.85c25.3 12.54 22.26 41.85 9.08 55a34.34 34.34 0 0 1-48.55 0c-17.57-17.6-11.07-46.91 11.25-56v-123c-20.8-8.51-24.6-30.74-18.64-45L142.57 101 8.45 235.14a28.86 28.86 0 0 0 0 40.81l195.61 195.6a28.86 28.86 0 0 0 40.8 0l194.69-194.69a28.86 28.86 0 0 0 0-40.81z"></path></svg>
|
||||
</div>
|
||||
<div class="md-source__repository">
|
||||
GitHub
|
||||
@@ -193,48 +193,51 @@
|
||||
My device reboots frequently. What can I do?
|
||||
</span>
|
||||
</a>
|
||||
<nav aria-label="My device reboots frequently. What can I do?" class="md-nav">
|
||||
<ul class="md-nav__list">
|
||||
</li>
|
||||
<li class="md-nav__item">
|
||||
<a class="md-nav__link" href="#how-accurate-are-the-detections">1.1.1
|
||||
<a class="md-nav__link" href="#bad-webui-responsiveness-what-can-i-do">1.2
|
||||
<span class="md-ellipsis">
|
||||
Bad WebUI Responsiveness. What can I do?
|
||||
</span>
|
||||
</a>
|
||||
</li>
|
||||
<li class="md-nav__item">
|
||||
<a class="md-nav__link" href="#how-accurate-are-the-detections">1.3
|
||||
<span class="md-ellipsis">
|
||||
How accurate are the detections?
|
||||
</span>
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
</nav>
|
||||
</li>
|
||||
<li class="md-nav__item">
|
||||
<a class="md-nav__link" href="#my-numbers-are-not-correctly-detected-what-can-i-do">1.2
|
||||
<a class="md-nav__link" href="#my-numbers-are-not-correctly-detected-what-can-i-do">1.4
|
||||
<span class="md-ellipsis">
|
||||
My numbers are not correctly detected. What can I do?
|
||||
</span>
|
||||
</a>
|
||||
</li>
|
||||
<li class="md-nav__item">
|
||||
<a class="md-nav__link" href="#how-can-i-ensure-invalid-numbers-are-never-reported">1.3
|
||||
<a class="md-nav__link" href="#how-can-i-ensure-invalid-numbers-are-never-reported">1.5
|
||||
<span class="md-ellipsis">
|
||||
How can I ensure invalid numbers are never reported?
|
||||
</span>
|
||||
</a>
|
||||
</li>
|
||||
<li class="md-nav__item">
|
||||
<a class="md-nav__link" href="#even-after-i-have-setup-everything-perfect-there-is-a-false-reading-especially-around-the-zero-crossing-roll-over-to-next-number">1.4
|
||||
<a class="md-nav__link" href="#even-after-i-have-setup-everything-perfect-there-is-a-false-reading-especially-around-the-zero-crossing-roll-over-to-next-number">1.6
|
||||
<span class="md-ellipsis">
|
||||
Even after I have setup everything perfect there is a false reading - especially around the zero crossing (roll over to next number)
|
||||
</span>
|
||||
</a>
|
||||
</li>
|
||||
<li class="md-nav__item">
|
||||
<a class="md-nav__link" href="#pre-value">1.5
|
||||
<a class="md-nav__link" href="#pre-value">1.7
|
||||
<span class="md-ellipsis">
|
||||
Pre-Value
|
||||
</span>
|
||||
</a>
|
||||
</li>
|
||||
<li class="md-nav__item">
|
||||
<a class="md-nav__link" href="#rate-too-high-read">1.6
|
||||
<a class="md-nav__link" href="#rate-too-high-read">1.8
|
||||
<span class="md-ellipsis">
|
||||
"Rate too high - Read: ..."
|
||||
</span>
|
||||
@@ -644,48 +647,51 @@
|
||||
My device reboots frequently. What can I do?
|
||||
</span>
|
||||
</a>
|
||||
<nav aria-label="My device reboots frequently. What can I do?" class="md-nav">
|
||||
<ul class="md-nav__list">
|
||||
</li>
|
||||
<li class="md-nav__item">
|
||||
<a class="md-nav__link" href="#how-accurate-are-the-detections">1.1.1
|
||||
<a class="md-nav__link" href="#bad-webui-responsiveness-what-can-i-do">1.2
|
||||
<span class="md-ellipsis">
|
||||
Bad WebUI Responsiveness. What can I do?
|
||||
</span>
|
||||
</a>
|
||||
</li>
|
||||
<li class="md-nav__item">
|
||||
<a class="md-nav__link" href="#how-accurate-are-the-detections">1.3
|
||||
<span class="md-ellipsis">
|
||||
How accurate are the detections?
|
||||
</span>
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
</nav>
|
||||
</li>
|
||||
<li class="md-nav__item">
|
||||
<a class="md-nav__link" href="#my-numbers-are-not-correctly-detected-what-can-i-do">1.2
|
||||
<a class="md-nav__link" href="#my-numbers-are-not-correctly-detected-what-can-i-do">1.4
|
||||
<span class="md-ellipsis">
|
||||
My numbers are not correctly detected. What can I do?
|
||||
</span>
|
||||
</a>
|
||||
</li>
|
||||
<li class="md-nav__item">
|
||||
<a class="md-nav__link" href="#how-can-i-ensure-invalid-numbers-are-never-reported">1.3
|
||||
<a class="md-nav__link" href="#how-can-i-ensure-invalid-numbers-are-never-reported">1.5
|
||||
<span class="md-ellipsis">
|
||||
How can I ensure invalid numbers are never reported?
|
||||
</span>
|
||||
</a>
|
||||
</li>
|
||||
<li class="md-nav__item">
|
||||
<a class="md-nav__link" href="#even-after-i-have-setup-everything-perfect-there-is-a-false-reading-especially-around-the-zero-crossing-roll-over-to-next-number">1.4
|
||||
<a class="md-nav__link" href="#even-after-i-have-setup-everything-perfect-there-is-a-false-reading-especially-around-the-zero-crossing-roll-over-to-next-number">1.6
|
||||
<span class="md-ellipsis">
|
||||
Even after I have setup everything perfect there is a false reading - especially around the zero crossing (roll over to next number)
|
||||
</span>
|
||||
</a>
|
||||
</li>
|
||||
<li class="md-nav__item">
|
||||
<a class="md-nav__link" href="#pre-value">1.5
|
||||
<a class="md-nav__link" href="#pre-value">1.7
|
||||
<span class="md-ellipsis">
|
||||
Pre-Value
|
||||
</span>
|
||||
</a>
|
||||
</li>
|
||||
<li class="md-nav__item">
|
||||
<a class="md-nav__link" href="#rate-too-high-read">1.6
|
||||
<a class="md-nav__link" href="#rate-too-high-read">1.8
|
||||
<span class="md-ellipsis">
|
||||
"Rate too high - Read: ..."
|
||||
</span>
|
||||
@@ -707,7 +713,22 @@
|
||||
<li>Unstable hardware - see <a href="../Hardware-Compatibility">Hardware Compatibility</a>.</li>
|
||||
</ul>
|
||||
<p>There is a dedicated page about this: <a href="../Frequent-Reboots/">Frequent Reboots</a>.</p>
|
||||
<h3 id="how-accurate-are-the-detections"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.1.1</span> How accurate are the detections?</h3>
|
||||
<h2 id="bad-webui-responsiveness-what-can-i-do"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.2</span> Bad WebUI Responsiveness. What can I do?</h2>
|
||||
<p>This is usually due to hardware or WLAN issues. There are already many entries in discussion section, some of which have good tipps.</p>
|
||||
<p>Possible checks / ideas:
|
||||
- ESP32CAM hardware antenna design is very poor in connection with camera frequency.
|
||||
-> Simple test: When the device is in operation, putting your thumb on the camera connector and the directly adjacent components should make the device respond more quickly.
|
||||
-> Possible optimization: Here, an attempt was made to dampen the frequency influences somewhat by shielding. But I've never tried that myself...
|
||||
https://www.reddit.com/r/esp32/comments/r9g5jc/fixing_ymmv_the_poor_frame_rate_on_the_esp32cam/
|
||||
- WLAN channel: Preferably use 1, 6 or 11
|
||||
- Performance can vary depending on the AP manufacturer. If necessary, check with a mobile hotspot or other device to exclude AP influence
|
||||
- Use an external antenna
|
||||
- Avoid VLAN, currently not fully supported
|
||||
- Temporarily deactivate virus scanner / firewall on the end device for testing purpose
|
||||
- Use sufficiently dimensioned power supply
|
||||
- Use a branded SD card (formatted with Windows, MAC often causes problems)</p>
|
||||
<p>Check <a href="https://github.com/jomjol/AI-on-the-edge-device/discussions">discussion section</a> for possible further tipps.</p>
|
||||
<h2 id="how-accurate-are-the-detections"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.3</span> How accurate are the detections?</h2>
|
||||
<p>It is hard to give a specific accuracy number. It depends on many factors, e.g.</p>
|
||||
<ul>
|
||||
<li>How in-focus is your camera?</li>
|
||||
@@ -718,12 +739,12 @@
|
||||
</ul>
|
||||
<p>Anecdotally, the authors of this page have great success with the meter. While the AI algorithm itself is not perfect and sometimes returns <code>NaN</code> or incorrect values, other post-processing / prevalue / sanity checks help ensure such invalid values are filtered out. With the correct settings, one author has been running this device for 1 month without any incorrect values reported. </p>
|
||||
<p>See the FAQs below for more details and configuration hints.</p>
|
||||
<h2 id="my-numbers-are-not-correctly-detected-what-can-i-do"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.2</span> My numbers are not correctly detected. What can I do?</h2>
|
||||
<h2 id="my-numbers-are-not-correctly-detected-what-can-i-do"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.4</span> My numbers are not correctly detected. What can I do?</h2>
|
||||
<ul>
|
||||
<li>There is a dedicated page about the correct setting <a href="../ROI-Configuration/">ROI Configuration</a>.</li>
|
||||
<li>This page also includes the instructions for gathering new images for the training.</li>
|
||||
</ul>
|
||||
<h2 id="how-can-i-ensure-invalid-numbers-are-never-reported"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.3</span> How can I ensure invalid numbers are never reported?</h2>
|
||||
<h2 id="how-can-i-ensure-invalid-numbers-are-never-reported"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.5</span> How can I ensure invalid numbers are never reported?</h2>
|
||||
<p>As mentioned above, the AI algorithm is not perfect. Sometimes it may read an incorrect value.</p>
|
||||
<p>We can tune the software to <em>almost</em> never report an incorrect value. There is a tradeoff though: the software may report <em>stale</em> values - i.e. it will drop incorrect values for a potentially long period of time, resulting in the meter reading being outdated by hours. If never receiving an incorrect value is important to you, consider tolerating this tradeoff.</p>
|
||||
<p>You can change the following settings to reduce incorrect readings (but potentially increase staleness of data):</p>
|
||||
@@ -732,7 +753,7 @@
|
||||
<li>Change <code>PostProcessing</code> configuration option <code>MaxRateType</code> to be time based instead of absolute. Set <code>MaxRateValue</code> to something realistic (e.g. <code>5</code> gal/min). You can often find the max flow rate your meter supports directly on the cover.</li>
|
||||
<li>Reduce <code>AutoTimer</code> configuration option <code>Interval</code> to the lowest it can be (e.g. <code>3</code> min). The more often you take readings, the less likely for data staleness to occur.</li>
|
||||
</ul>
|
||||
<h2 id="even-after-i-have-setup-everything-perfect-there-is-a-false-reading-especially-around-the-zero-crossing-roll-over-to-next-number"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.4</span> Even after I have setup everything perfect there is a false reading - especially around the zero crossing (roll over to next number)</h2>
|
||||
<h2 id="even-after-i-have-setup-everything-perfect-there-is-a-false-reading-especially-around-the-zero-crossing-roll-over-to-next-number"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.6</span> Even after I have setup everything perfect there is a false reading - especially around the zero crossing (roll over to next number)</h2>
|
||||
<ul>
|
||||
<li>The roll over behavior is different for the different meters. E.g.:</li>
|
||||
<li>Rolling over start with different previous position (e.g. at 7, 8 or 9)</li>
|
||||
@@ -754,11 +775,11 @@
|
||||
<li>To handle this, a parametrized setting would be needed. This is rather complicated to implement as subtle changes make a relevant difference. Currently this is not implemented.
|
||||
So please be a bit patient with your meter :-)</li>
|
||||
</ul>
|
||||
<h2 id="pre-value"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.5</span> Pre-Value</h2>
|
||||
<h2 id="pre-value"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.7</span> Pre-Value</h2>
|
||||
<p>PreValue is here a bit missleading, because normally it is the same as the last value. In the next round of reading it will be used to check nagtive rates, high rates (MaxRateValue / MaxRateType) and CheckDigitIncreaseConsistency (dig-class11 only). Either from a previous correctly identified value or manual setting by the user.</p>
|
||||
<p>If you use post processes, enable the pre-value. The pre-value must be set at first time. Set it to the current raw value. </p>
|
||||
<p>If the device runs in errors, the pre-value will not be updated, as long as the <code>preValueAgeStartup</code> time between the last valid value (or startup time) and current time is not exceeded. After it the preValue will be set again, if no other error occured. So the device can not run in an endless error, like high rate.</p>
|
||||
<h2 id="rate-too-high-read"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.6</span> "Rate too high - Read: ..."</h2>
|
||||
<h2 id="rate-too-high-read"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.8</span> "Rate too high - Read: ..."</h2>
|
||||
<p>In configuration you can set the <code>MaxRateValue</code> and <code>MaxRateType</code>. The settings suppress improbably high values that can come from false readings. To do this, the value must be set correctly depending on your meter.</p>
|
||||
<p>Before doing this, you should be clear about the type of rating you want to use.</p>
|
||||
<ul>
|
||||
@@ -797,6 +818,6 @@ and <a href="https://github.com/haverland/Tenth-of-step-of-a-meter-digit/wiki/Co
|
||||
<div class="md-dialog__inner md-typeset"></div>
|
||||
</div>
|
||||
<script id="__config" type="application/json">{"base": "..", "features": [], "search": "../assets/javascripts/workers/search.b8dbb3d2.min.js", "translations": {"clipboard.copied": "Copied to clipboard", "clipboard.copy": "Copy to clipboard", "search.result.more.one": "1 more on this page", "search.result.more.other": "# more on this page", "search.result.none": "No matching documents", "search.result.one": "1 matching document", "search.result.other": "# matching documents", "search.result.placeholder": "Type to start searching", "search.result.term.missing": "Missing", "select.version": "Select version"}}</script>
|
||||
<script src="../assets/javascripts/bundle.8fd75fb4.min.js"></script>
|
||||
<script src="../assets/javascripts/bundle.3220b9d7.min.js"></script>
|
||||
</body>
|
||||
</html>
|
||||
Reference in New Issue
Block a user