Deployed c47475d with MkDocs version: 1.4.2

This commit is contained in:
github-actions[bot]
2023-03-28 13:08:08 +00:00
parent b86ef47954
commit fe169f36ed
3 changed files with 2 additions and 31 deletions

View File

@@ -119,14 +119,6 @@
</li>
<li class="toctree-l1 current"><a class="reference internal current" href="./">Error Debugging</a>
<ul class="current">
<li class="toctree-l2"><a class="reference internal" href="#rebooting">Rebooting</a>
<ul>
<li class="toctree-l3"><a class="reference internal" href="#general-remark">General Remark</a>
</li>
<li class="toctree-l3"><a class="reference internal" href="#getting-deeper-inside">Getting deeper inside</a>
</li>
</ul>
</li>
<li class="toctree-l2"><a class="reference internal" href="#often-observed-problems">Often observed problems</a>
<ul>
<li class="toctree-l3"><a class="reference internal" href="#hardware-failure">Hardware failure</a>
@@ -200,34 +192,13 @@
<div class="section" itemprop="articleBody">
<h1 id="error-debugging">Error Debugging</h1>
<h2 id="rebooting">Rebooting</h2>
<h5 id="general-remark">General Remark</h5>
<ol>
<li>
<p>Due to the rather complex code with a lot of external libraries and the limited availability of memory a reboot of the device from time to time is "normal". Background are memory leakages and therefore running out of free memory. </p>
</li>
<li>
<p>The hardware of the ESP32CAM has a varying quality. I have one and the same hardware with a reboot range from every 5 detection runs to up to 250 detection runs. </p>
</li>
</ol>
<h5 id="getting-deeper-inside">Getting deeper inside</h5>
<p>Have a look into the log file (<code>/log/message/...</code>). </p>
<ul>
<li>If the log file is very short you need to enable a enhanced logging in the <code>config.ini</code> (Debug --&gt; <code>logfile = true</code>) . </li>
</ul>
<p>Analyze the debugging output of the serial interface</p>
<ul>
<li>Connect a serial to USB interface (like for flashing) and make a logging of the serial communication</li>
<li>There are a lot more intermediate information and the lines before the reboot tell you, where the firmware fails</li>
</ul>
<p><strong>If you make an issue about this, please post these two information additionally</strong> </p>
<p><strong>Don't forget to remove your WLAN password in the serial log</strong></p>
<h2 id="often-observed-problems">Often observed problems</h2>
<h3 id="hardware-failure">Hardware failure</h3>
<ul>
<li>Camera not working --&gt; check the interface, test another module</li>
<li>Low cost module with only 2MB of PSRAM instead of 4MB --&gt; image taking will fail first. This will never work due to too low memory</li>
</ul>
<p>More information in terms of hardware, component and basic configuration issues can be found here: <a href="https://jomjol.github.io/AI-on-the-edge-device-docs/Frequent-Reboots/">Reboot reasons</a></p>
<h3 id="roi-misaligned">ROI misaligned</h3>
<p><img src="https://user-images.githubusercontent.com/108122193/188264361-0f5038ce-d827-4096-93fb-5907d3b072b4.png" width=30% height=30%></p>
<p>This typically happens if you have suboptimal "Alignment Marks". A very simple and working solution is to put put higly contrasted stickers on your meter and put "Alignment Marks" on it (see picture below)</p>

File diff suppressed because one or more lines are too long

Binary file not shown.