1. What did you personally accomplish this week on the project?
This week I shifted from design preparation to implementation work. I refined the FTDI FT2232H software environment and began modularizing my earlier test scripts into distinct components for control and data logging. I improved the raw-byte capture script to handle sustained reads and verified that data can be streamed and saved reliably over longer durations.
I also documented the interfaces between modules — control (GPIO and power-cycling), capture, and reconstruction — so integration with the upcoming PCB firmware will be straightforward. Throughout the week I coordinated with Mars to align timing expectations between the hardware’s MOSFET switching and the FTDI control layer.
2. Is your progress on schedule or behind?
I’m on schedule. With the design review complete, this week’s goals focused on establishing a working modular framework and preparing for hardware arrival. The FTDI environment and sustained logging scripts meet those objectives. No major blockers at this stage.
3. What deliverables do you hope to complete next week?
Next week, I plan to:
-
Add configurable parameters to the logging tool (capture duration, file naming, and data-rate display).
-
Begin implementing a simple command-line interface (CLI) to unify control and logging operations.
-
Develop a test harness that measures FTDI GPIO latency so we can compare it against our < 20 µs target when hardware arrives.