@Emmanuel-Goudot Yes, the interrupts are currently connected to the onboard PIC of the Pytrack, which makes it a bit more difficult to manage regarding simply connecting the accelerometer to the ESP32 interrupts. We're working on this and will let you know when it's ready!
The charging chip (BQ24040) doesn't provide this information, you'd need one with a so called "fuel gauge" or a coulomb counter.
The best you can do with the expansion board is track the battery voltage via G3 (which comes from a voltage divider) - see this topic https://forum.pycom.io/topic/226/lopy-adcs/12 - but for LiPo batteries this will be a VERY rough approximation.
@dalecousins thanks so much for this - its a confirmation for me. Last night I tried to charge the battery through another mechnism and found the same thing - once I connected it back up again it was fine. Apparently (I found this out in another post) they havent implemented the deep sleep function in the firmware / API and therefore when I connected up my solar, the battery was draining a LOT faster than I originally expected and the solar couldnt recharge the battery fast enough, and therefore the battery drained too low. Also, FYI, deint the WIFI doesnt actually power it down and therefore will drain the battery quickly too. My solution is now on hold until these things are sorted out.
Disabled Categories are greyed out
This topic will be moved to the category
Looks like your connection to Pycom Forum was lost, please wait while we try to reconnect.