kenchong48
commented
1 year ago data from a run that shows this issue, bin[x] represents 4 different boards that were used. it's possible the board for bin4 had the wrong code on it, given it managed to exceed the hardcoded max file size: https://drive.google.com/drive/folders/1gmaAz5t27SEJzvac58T5dNcL5hANI0-O?usp=share_link
Seeing an issue where a 3hr gap occurs after 3 reading cycles, when the burst number is set to 1. Could be an i2c hang, delay calculation issue, etc timing issues. Looks like it is resetting then starting again later.