Difference between revisions of "BoSL Board Debug"
| Line 9: | Line 9: | ||
Observed the 2 groups for one week. The result is both groups had some ones stop logging, 2 in NEW group and 2 in OLD group. | Observed the 2 groups for one week. The result is both groups had some ones stop logging, 2 in NEW group and 2 in OLD group. | ||
The conclusion is: delay(1200) is not the cause of stop logging. | The conclusion is: delay(1200) is not the cause of stop logging. | ||
| + | <br> | ||
A logbook for the trouble shooting was created on the google drive, find it [https://docs.google.com/spreadsheets/d/14nkBCIQ-oUG154t5BQf20QshVCk1C5ATlpUIRlaCJDo here]. | A logbook for the trouble shooting was created on the google drive, find it [https://docs.google.com/spreadsheets/d/14nkBCIQ-oUG154t5BQf20QshVCk1C5ATlpUIRlaCJDo here]. | ||
Revision as of 03:33, 6 July 2023
Stop logging issue
The BoSL Board stops logging from time to time is a big pain. The team decided to find the root cause and solve the problem.
Trouble shooting history
31th May 2023
20 BoSL boards were setup for trouble shooting. 10 run the original BoSL_logging.ino code, each one with a tag (OLD_1, OLD_2, ...), let's call them OLD group. Another 10 run Dave's new version code BoSL_VEL_Dave_290523.ino, each one with a tag (NEW_1, NEW_2, ...), let's call them NEW group. The major difference between OLD and NEW group is the NEW group's code delays longer to pull Sim7000 powerkey down to power off Sim7000. Because we suspect that some MCUs run slowly and the delay(1200) is less than accurate 1200ms, so sometimes Sim7000 may not really power off and the result is the Sim7000 runs out of order.
8th June 2023
Observed the 2 groups for one week. The result is both groups had some ones stop logging, 2 in NEW group and 2 in OLD group.
The conclusion is: delay(1200) is not the cause of stop logging.
A logbook for the trouble shooting was created on the google drive, find it here.
