Deployed 61d3c7d with MkDocs version: 1.4.2

This commit is contained in:
github-actions[bot]
2023-01-02 22:55:10 +00:00
parent 5c1358a166
commit 365073eea2
7 changed files with 40 additions and 40 deletions

View File

@@ -199,12 +199,12 @@
Example: relative rate of 0.05 m³/minute --> after 20 minutes a maximum change of 20 minutes * 0.05 m³/minute = 1 m³ is possible. That means that a false reading of 1 m³ cannot be detected false after about 20 minutes in this case
Assume, that there might me no change in the meter for hours (e.g. during the night) a much bigger change could also be accepted. </p>
<h4 id="flow-chart">Flow Chart</h4>
<p>[[/images/correct_algo_1.jpg]]</p>
<p>[[/images/correct_algo_2.jpg]]</p>
<p>[[/images/correct_algo_3.jpg]]</p>
<p><img alt="" src="../img/correct_algo_1.jpg" /></p>
<p><img alt="" src="../img/correct_algo_2.jpg" /></p>
<p><img alt="" src="../img/correct_algo_3.jpg" /></p>
<h2 id="checkdigitincreaseconsistency-algorithm">CheckDigitIncreaseConsistency Algorithm</h2>
<p>The check digit increase consistency algorithm is functional for the digits only. Due to the fact, that the rotation might be a little bit earlier or later compared to the zero crossing of the digit before, errors during the reading before and after a zero crossing can be wrong. Therefore a simple algorithm can be applied, checking the consistency of zero crossing and changes in the following digit. This is applied to one after the other digit, starting with the lowest priority digits.</p>
<p>[[/images/correct_algo_zero_crossing.jpg]]</p>
<p><img alt="" src="../img/correct_algo_zero_crossing.jpg" /></p>
</div>
</div><footer>