Différences entre versions de « SBK-unexpected-data »
Sauter à la navigation
Sauter à la recherche
| Ligne 18 : | Ligne 18 : | ||
[[Fichier:SBK-unexpected-data-02.png]] | [[Fichier:SBK-unexpected-data-02.png]] | ||
| − | A close inspection reveal that "180" value is the | + | A close inspection reveal that "180" value is not a temperature but the next iteration number. |
[[Fichier:SBK-unexpected-data-03.png]] | [[Fichier:SBK-unexpected-data-03.png]] | ||
{{SBK-TRAILER}} | {{SBK-TRAILER}} | ||
Version du 6 juillet 2024 à 22:50
Forewords
The SBK Datalogger generates CSV files that can be imported into spreadsheet (see this tutorial on Spreadsheet usage).
Upon condition, charting may reveal few data deviating from standard/common values.
This tutorial shows: why it happens, how to identify the data, how to fix it and what to do to avoids such situation.
The unexpected data
Drawing the data of the temperature sensor (content of the CSV) reveal an unexpected value.
By exploring the data, we can locate that value of 180 °C.
A close inspection reveal that "180" value is not a temperature but the next iteration number.
Written by Meurisse D. for MCHobby