Posted on

Jayden’s Status Report for 10/17

Accomplish

This week I focused on the Design Review Report, specifically narrowing our specifications as we have decided to focus on making the Capsure device used by pool players. The most important piece I worked on was the Design Requirements since I needed to balance feasibility with sufficiency, while also making sure that it was well defended. I assisted Clarence with soldering the battery for the ESP32.

Progress/Schedule

In terms of the software component, we are still slightly ahead of schedule. However the more time-variant portion will be to establish a reliable connection between the ESP32 with the device. Now that our use case has narrowed and the design is flushed out, the application integration should be easier to debug when problems arise.

Deliverables

This week I want to test out the ESP32 camera parameters which include resolution, frame rate, compression rates and power consumption. These matter a lot because in the design requirements the numbers were calculated using optimistic values and estimates from online, but it is likely that the measured ones will deviate slightly so we will need to adjust our calculations accordingly.

 

Posted on

Jayden’s Status Report for 10/03

Accomplish

This week, while we wait for the ESP32 to arrive, I focused on making the phone software robust against failures the real board could cause.

The device client now sends one request at a time, retries when the device reports it is busy, and pauses status updates during transfers.
Downloads now resume where they left off, and each clip is checked for size and parsed before the app tells the device it can free the space.
The app now gives the user clear instructions, such as turning on the Wi-Fi switch, instead of generic errors.
I also added security checks to validate clip IDs coming from the device, accepting only local network addresses. Finally, I updated the mock device so it behaves more like the ESP32 and can simulate dropped transfers. That way these cases are tested before the hardware arrives.

Progress/Schedule

We are still slightly ahead of schedule on software. The hardware hasn’t blocked progress, because the work moved to edge cases and reliability that would otherwise have been found during integration.

Deliverables

The next deliverable is still an end-to-end Wi-Fi transfer from a real ESP32 to the Expo Go app, now tested against the single-client and interrupted-transfer cases. After that, I’ll connect the settings screen to real device readings (battery percentage, temperature, and storage remaining), and work with Ankita on per-device Wi-Fi credentials.

Posted on

Jayden’s Status Report for 9/26

Accomplish

This week I focused on the scaffolding of the phone side of CapSure, to set up the development environment and transfer over a video wirelessly on a mock application. The app successfully renders and is able to download videos, and I also locked the open transfer architecture questions to using WiFi gated by a physical switch, after reasoning about the user flow within the application.

Progress/Schedule

In terms of software, we are slightly ahead of schedule as I have shown that the current software stack is likely to work, however we will have to wait until the ESP32 arrives before I can adjust the transfer protocol to match the device.

Deliverables

The next main deliverable on my end is a fully flushed out connection over a real board over Wifi, even without the camera it would be an accomplishment to be able to transfer data from an ESP to an ExpoGo app. Additionally, functionality to change the app from a mock to real displays including battery percentage, temperature and memory remaining.

Posted on

Jayden’s Status Report for 9/19

Accomplish

Did more extensive research on the software constraints for the project. The ESP32 will use Bluetooth Low Energy (BLE) but we should still have Wi-Fi for transfers fast enough to meet our requirements. For development I have chosen to use ESP-IDF in cursor for AI assistance, which will hold an http server and wifi endpoint. I am also choosing to use Swift with Xcode since I have had experience there.

Progress/Schedule

So far, everything is on schedule and we are stretching tasks forward from the gantt chart to frontload work and increase parallelization.

Deliverables

Next week I’ll set up the software stack and design a MVP software architecture with transfer protocols in the Design Review, and also determine how the phone should join the device’s Wi-fi/connection, because a new potential issue is that user’s don’t want the friction of switching Wifis.