<?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[Run Fipy USB Powerbank]]></title><description><![CDATA[[[topic:post_is_deleted]]]]></description><link>https://forum.pycom.io/topic/3823/run-fipy-usb-powerbank</link><generator>RSS for Node</generator><lastBuildDate>Sat, 11 Jul 2026 05:21:34 GMT</lastBuildDate><atom:link href="https://forum.pycom.io/topic/3823.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 01 Oct 2018 18:31:52 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Run Fipy USB Powerbank on Mon, 01 Oct 2018 19:45:56 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.pycom.io/uid/2810">@tfgm</a> Not directly with the FiPy. You can use a chip like INA219 to monitor the current &amp; voltage at the wire getting in to the device, and then you can determine the mAh that have been consumed, and in combinations with the voltage also the energy. The timing resolution is not very good, mostly limited by the time you allow your code to measure. So you will miss small spikes &amp; drops.<br />
For convenience, there are modules with that chip available.<br />
There are Python drivers from Adafruit and one here, tested on ESP32 and ESP8266: <a href="https://github.com/chrisb2/pyb_ina219" target="_blank" rel="noopener noreferrer nofollow">https://github.com/chrisb2/pyb_ina219</a><br />
Both should be close to Pycom's python. The gap, if at all, should be in the I2C section.</p>
]]></description><link>https://forum.pycom.io/post/22572</link><guid isPermaLink="true">https://forum.pycom.io/post/22572</guid><dc:creator><![CDATA[robert-hh]]></dc:creator><pubDate>Mon, 01 Oct 2018 19:45:56 GMT</pubDate></item></channel></rss>