<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[M5Unit Miniscale Questions]]></title><description><![CDATA[<p dir="auto">I recently bought a bunch of M5 hardware and I included the MiniScale just to try out (it was cheap!)...</p>
<p dir="auto">I am using it with a M5Stack Fire 2.7 controller, and once I got the code up and running, I noticed some weird behavior:</p>
<ul>
<li>The weight reading drifts upward over time.  I would estimate it gains a gram every 15-20 minutes.  Is this just the nature of the sensor?</li>
<li>I don't have calibration weights, but I may be able to track some down and run a calibration sketch on it.  However, I have also seen an example sketch (SettingGap.ino) in the library referenced on the docs page (<a href="https://docs.m5stack.com/en/unit/Unit-Mini%20Scales" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.m5stack.com/en/unit/Unit-Mini Scales</a>).  Is there any documentation of what the gap value meaning is?</li>
<li>Is there an example sketch/program that operates like the video embedded near the end of the docs page I referenced above?  It uses an animated scale graphic...</li>
</ul>
]]></description><link>https://community.m5stack.com/topic/6036/m5unit-miniscale-questions</link><generator>RSS for Node</generator><lastBuildDate>Tue, 17 Mar 2026 08:51:02 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/6036.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 31 Jan 2024 01:36:53 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to M5Unit Miniscale Questions on Thu, 09 Jan 2025 19:45:59 GMT]]></title><description><![CDATA[<p dir="auto">I was also struggling with drift and negative values.  I also receive a traceback error when I invoke tare().  The function works, when I go in and edit the python code (removing the parathesis).  I suggested an update to the GitHub.</p>
<p dir="auto">I found the <a href="http://miniscale.py" target="_blank" rel="noopener noreferrer nofollow ugc">miniscale.py</a> definitions in the firmware uiflow-micropython project.  It has more details on the implementation of object class.<br />
<a href="https://github.com/m5stack/uiflow-micropython/blob/master/m5stack/libs/unit/miniscale.py" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/m5stack/uiflow-micropython/blob/master/m5stack/libs/unit/miniscale.py</a></p>
]]></description><link>https://community.m5stack.com/post/27832</link><guid isPermaLink="true">https://community.m5stack.com/post/27832</guid><dc:creator><![CDATA[gconsulting]]></dc:creator><pubDate>Thu, 09 Jan 2025 19:45:59 GMT</pubDate></item><item><title><![CDATA[Reply to M5Unit Miniscale Questions on Mon, 04 Mar 2024 11:37:27 GMT]]></title><description><![CDATA[<p dir="auto">As spiff72 also pointed out, negative weights are displayed as positive. That's quite confusing for our students. For now, I've addressed this by using the raw ADC data as a zero point after an offset (tare). If the value during a measurement is greater than the zero point, then the value of 'scales.getWeight()' is positive. If the value is smaller, then I multiply 'scales.getWeight()' by -1.<br />
I hope that issue is solved in the next library update.</p>
]]></description><link>https://community.m5stack.com/post/24255</link><guid isPermaLink="true">https://community.m5stack.com/post/24255</guid><dc:creator><![CDATA[hazo]]></dc:creator><pubDate>Mon, 04 Mar 2024 11:37:27 GMT</pubDate></item><item><title><![CDATA[Reply to M5Unit Miniscale Questions on Thu, 01 Feb 2024 00:31:05 GMT]]></title><description><![CDATA[<p dir="auto">I partially answered my own question about the "gap" value.  I realized that there was some info on the i2c protocol document that clarified that the gap was equal to (ADC100g - ADC0g)/100<br />
(where ADC0g = the rawADC value with 0g on scale, and ADC100g = rawADC value with 100g on scale)</p>
<p dir="auto">I had a period of time while I was doing some various programming tweaks and found the weight value displayed was climbing much more quickly (maybe 1g every couple of minutes).  The battery was very low at that point, so I did an overnight test where I just left it running while it was charging and found that the displayed weight value on the display was less than 1g.   Really weird!  I wonder if the low voltage was the cause of the rapid drift?</p>
<p dir="auto">I also did some experimenting with the various filter settings (LP Filter, Avg Filter, and EMA filter).  Avg filter seems self-explanatory, LP filter is presumably a low-pass filter (either enabled or disabled), and I had to google what an EMA filter was (exponential moving average).</p>
<p dir="auto">I just wish I could find some more documentation on this thing!  I see some interesting behavior:</p>
<ul>
<li>Weird oscillations when you remove a weight rapidly -- the value drops quickly, overshoots past zero to go slightly negative, and then settles back close to zero (after a cycle or two).</li>
<li>If you lift the scale by the measurement platform, I would have expected the value to go negative, but it actually goes positive instead.  Since I could see it would go negative during the previously mentioned oscillation this caught me my surprise.</li>
<li>I need to figure out how to use the serial plotter in Arduino IDE so I can watch the oscillations.  I swear I see some slow oscillation of the weight reading over longer periods of time (with a constant weight or zero weight on it).</li>
</ul>
]]></description><link>https://community.m5stack.com/post/23580</link><guid isPermaLink="true">https://community.m5stack.com/post/23580</guid><dc:creator><![CDATA[spiff72]]></dc:creator><pubDate>Thu, 01 Feb 2024 00:31:05 GMT</pubDate></item><item><title><![CDATA[Reply to M5Unit Miniscale Questions on Wed, 31 Jan 2024 19:40:04 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://community.m5stack.com/uid/82475">@spiff72</a> Many bathroom scales require you to TAP the scale to boot up.<br />
This not only saves battery but re-calibrates it every time you go to use it.<br />
The continued rise may be</p>
<ol>
<li>weight settling mechanically or</li>
<li>the thin film resistors of the Wheatstone Bridge may be slightly heating or nearby electronics throwing of a little heat and losing calibration.</li>
</ol>
]]></description><link>https://community.m5stack.com/post/23573</link><guid isPermaLink="true">https://community.m5stack.com/post/23573</guid><dc:creator><![CDATA[teastain]]></dc:creator><pubDate>Wed, 31 Jan 2024 19:40:04 GMT</pubDate></item></channel></rss>