Open obasille opened 2 years ago
To have logs enabled in only one file, add #define NRF_LOG_ENABLED 1
on top of that file and change firmware_debug: DEBUG_FLAGS += -DNRF_LOG_ENABLED=1
to 0 in the Makefile
To light up LEDs, either play an animation endlessly or call LEDs::setPixelColors()
with all LEDs set to white for example.
I've added a new screen to the Toolbox that connects to a die and has a button to get the battery level. This is on the "central" branch, not "main".
https://github.com/GameWithPixels/PixelsToolbox/blob/central/src/screens/StatsScreen.tsx
@David-Chernis Please do the following:
Generate graphs of how voltage evolves across time for a few dice with at least 2 set of data per die, for both charging and discharging setup. As a bonus please also add a couple discharging graphs with LEDs off so we can have a look at the power consumption of the board when there is a BLE connection.
Using python, write a script that take as input all the CSV or the spreadsheet (of either charging or discharging setup) files with the battery measurements.
for each data set:
create remainingTimeTable with:
x = voltage
y = remainingTime = maxTime - time at voltage
create averageRemainingTimeTable: for voltage from minRoundedVoltageAcrossAllRuns to maxRoundedVoltageAcrossAllRuns with steps of 0.1V: x = voltage y = average remainingTime across each remainingTimeTable (ignoring those that don't have a value) yError = difference between max and min remainingTime across each remainingTimeTable (ignoring those that don't have a value)
plot the average and error graphs.
Run the script for both charging and discharging set of CSV / spreadsheet files.
Current values were calibrated for a battery type that isn't used anymore.
The current values are stored in
voltages
andlevels
inbattery_controller.cpp
. Those values are use byLookupChargeLevel()
. We need another set of voltages+levels for forLookupChargeLevel()
to use when the battery is charging.