Open osresearch opened 2 months ago
Looking at the energytrace
graphs on Travis' goodwatch wiki, it seems that he was also measuring only a few Hz of updates when the watch was drawing a small number of microamp.
Here is my watch measured by energytrace
with a 5.6k load in parallel (which adds about a 600uA offset) and just the watch by itself. The length of the 1 Hz wakeups is clearly visible in the loaded line, while the unloaded current measurements are so low frequency that they almost blend together.
Maybe add this to the README in a PR?
While trying to optimize the power draw on very low power devices,
energytrace
seems to end up producing far less frequent measurements. With the msp430 removed from the loop and just testing 1k, 2.2k, 5.6k, 10k and 47k load resisters, you can see how the frequency of new measurements drops significantly. By the time the power draw is 50uA or less, it seems that the measurements change at around 2-4 Hz, no matter what the setting is for the update frequency.Is this a fundamental issue with the way the charge pump measurements work? That is what is suggested in this ti forum post:
For the graph above, I've modified
energytrace
to use a 100 Hz update and still see the very low temporal resolution.