This week, Ian focused on writing the report. He moved the software flowcharts out of section 2.2.2 and instead introduced the various software and programming languages the project uses. This includes a brief introduction to Python, CircuitPython, Thonny IDE, and programs and methods used by the project.
Ian organized the hardware sections in Chapters 2 and 3 such that modules appear in the same order. Ian also gathered material from progress logs and began implementing it into Chapter 3, mainly focusing on the control module hardware section and on the troubleshooting section.
Ian also took care of any code modifications that were needed. For test 4.1.4, Ian modified the code such that the system will only run cooling mode 2. He also set the battery mode to 3 so that the system remains at full power. This will be for test 4.5.2, where the group will let the system run at full power until the battery drains and the system shuts off.
While uploading these changes to the Raspberry Pi Pico, the filesystem became corrupt, and all files on the board were lost. The device showed up as a USB Drive instead of a CIRCUITPY drive. Luckily, this was an easy fix. Following the troubleshooting guide on the CircuitPython website, Ian ran the following code in the REPL. This erased the filesystem, and the board restarted as an empty CIRCUITPY drive. Once the board was accessible, the project files were copied to the board from the group's Google Drive, and it was good to go.
Comments