From 171031de0a4058d7872599fe05ffd0e5649912b0 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Wed, 16 Apr 2025 18:55:22 +0000 Subject: [PATCH] Deployed 85a5689 with MkDocs version: 1.6.1 --- Choosing-the-Model/index.html | 23 -------------------- Frequent-Reboots/index.html | 1 - Neural-Network-Types/index.html | 38 ++++++++++++++++----------------- search/search_index.json | 2 +- 4 files changed, 20 insertions(+), 44 deletions(-) diff --git a/Choosing-the-Model/index.html b/Choosing-the-Model/index.html index d5f533c..4cca155 100644 --- a/Choosing-the-Model/index.html +++ b/Choosing-the-Model/index.html @@ -284,17 +284,6 @@ Analog pointer models -
  • 1.3 @@ -774,17 +763,6 @@ Analog pointer models -
  • 1.3 @@ -875,7 +853,6 @@ The dig-class100 is a standard classification model. Each tenth ste

    Look here for a list of digit images used for the training.

    1.2 Analog pointer models

    -

    1.2.1 ana-class100 and ana-cont

    For pointers on water meters use the analog models:

    You can choose between two models:

    diff --git a/Frequent-Reboots/index.html b/Frequent-Reboots/index.html index 6d3bdd4..9d2ec04 100644 --- a/Frequent-Reboots/index.html +++ b/Frequent-Reboots/index.html @@ -955,7 +955,6 @@ There is noting you can do about it, beside testing different hardware.

    1.0.1.1.1 Bad or insufficient power supply

    A good and stabilized power supply is essential to have error free operation. The device is quite picky in terms of proper power supply. Especially the wifi module have some load spikes which the power supply needs to cover. If the power is not stable enough, the brwonout mechanism is protecting against strange behaviour and force a reboot whenever the voltage drops below a specific level. You can see this in random reboots which indication is logfile: --> Reset reason: Brownout

    -

    1.0.2 Repeating boot loops

    Repeating boot loops at the same situation during the flow has a systematic problem either in the hardware or the configuration. It usually happens during initialization state or processing the first round as there all needed parts of the firmware have been loaded for the first time.

    To identify the root cause the logfiles, the reduced web interface, the red board LED or the serial log of the UART interface (no remote access, USB access needed) is helpful.

    diff --git a/Neural-Network-Types/index.html b/Neural-Network-Types/index.html index 57bb15b..cfab1e5 100644 --- a/Neural-Network-Types/index.html +++ b/Neural-Network-Types/index.html @@ -400,7 +400,7 @@
  • 1.3.1.1 - Types of counters trained: + Types of counters trained
    • @@ -450,7 +450,7 @@
  • 1.3.2.1 - Types of counters trained: + Types of counters trained
    • @@ -464,10 +464,10 @@
  • 1.3.2.3 - CNN Technical details: + CNN Technical details -