Mirror/AI-on-the-edge-device-docs
1
0
Fork 0
mirror of https://github.com/jomjol/AI-on-the-edge-device-docs.git synced 2025-12-09 13:06:56 +03:00
Code Issues Packages Projects Releases Wiki Activity

.

Browse Source
This commit is contained in:
CaCO3
2025-04-16 20:54:52 +02:00
parent 922e07ac4f
commit 85a5689a3b
6 changed files with 9 additions and 88 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/FAQs.md
View File

@@ -1,7 +1,6 @@
# Frequently Asked Questions
## My device reboots frequently. What can I do?
There are several reasons for frequent reboots:
* Frequent HTML requests
@@ -12,7 +11,6 @@ There is a dedicated page about this: [Frequent Reboots](Frequent-Reboots.md).
## Bad WebUI responsiveness. What can I do?
This is usually due to hardware or WLAN issues. There are already many entries in discussion section, some of which have good tipps.
Possible checks / ideas:
@@ -33,7 +31,6 @@ Check [discussion section](https://github.com/jomjol/AI-on-the-edge-device/discu
## How accurate are the detections?
It is hard to give a specific accuracy number. It depends on many factors, e.g.
* How in-focus is your camera?
@@ -48,7 +45,6 @@ See the FAQs below for more details and configuration hints.
## My numbers are not correctly detected. What can I do?
* There is a dedicated page about the correct setting [ROI Configuration](ROI-Configuration.md).
* This page also includes the instructions for gathering new images for the training.
@@ -65,7 +61,6 @@ You can change the following settings to reduce incorrect readings (but potentia
* Reduce `AutoTimer` configuration option `Interval` to the lowest it can be (e.g. `3` min). The more often you take readings, the less likely for data staleness to occur.
## Even after I have setup everything perfect there is a false reading - especially around the zero crossing (roll over to next number)
* The roll over behavior is different for the different meters. E.g.:
* Rolling over start with different previous position (e.g. at 7, 8 or 9)
* The neutral position (no rolling) is not perfectly at zero, but rather at something like 7.9 or 8.1, even if it should be exactly 8
@@ -81,7 +76,6 @@ You can change the following settings to reduce incorrect readings (but potentia
So please be a bit patient with your meter :-)
## Pre-Value
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.
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.
@@ -89,7 +83,6 @@ If you use post processes, enable the pre-value. The pre-value must be set at fi
If the device runs in errors, the pre-value will not be updated, as long as the `preValueAgeStartup` 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.
## "Rate too high - Read: ..."
In configuration you can set the `MaxRateValue` and `MaxRateType`. 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.
Before doing this, you should be clear about the type of rating you want to use.
@@ -103,7 +96,6 @@ If there is an interval of 5 minutes between readings and a MaxRateValue of 1, a
- RateChange: the difference is `> 1 / 5`
## Train on my own images
Look at [Learn models with your own images](https://jomjol.github.io/AI-on-the-edge-device-docs/Learn-models-with-your-own-images/)
and [Cookbook running the jupyter notebook with my own data](https://github.com/haverland/Tenth-of-step-of-a-meter-digit/wiki/Cookbook-running-the-jupyter-notebook-with-my-own-data).