The pysense and pytrack are nice samples of how to use the xxPy modules.
IMHO It would benefit pycom if they publish the schematics. It will serve as inspiration for new pycom based products. Now it is a source of frustration and wasted hours of figuring out how it is all interconnected.
Also the datasheets are far from complete. We have a low power device that can be put in deep sleep (uA) but on the other hand (some versions) need a power supply of over 500mA. Documentation needs some care.
It looks like they are growing (to) fast as a company with (to) many products to support at this moment. I'm a bit reluctant to put the modules in a real product at this moment. Are there pycom oem module based products on the market yet?
Are you sure that it's actually a protection circuit at 2.1V, and not simply the battery failing due to its chemistry
Yes, I fed power supply voltages directly through the LiPo connector and measured the output into a 100mA load at Vin + Ground on the Py connector. When input voltage at battery terminal dropped below 2.1V, Vin + GND became 0v.
@jmarcelino I have now got an MSP430 to log my data and now need it to wake up my Sipy, send a number to the Sipy before the Sipy sends a sigfox message. As I am using the mps430 SPI for accelerometer reading I only have I2c available for the communication. Do you know if I2c communication is possible at different clock speeds? also will i encounter any problems as the devices uses afferent languages? or any other problems i may encounter?
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.