WORK ACCOMPLISHED:
Parts List: This week I focused on creating an extensive document that details our choices for hardware components, especially the Raspberry Pi, GPS and IMU. I’ve decided on a model for the RPi and I’ve narrowed it down to two models for the GPS and IMU each.
My decision making criteria were: Price, Accuracy, and Ease of Communication. We’re going to be leveraging the Qwiic ecosystem that SparkFun provides with their components which removes the need for soldering. They’re also daisy chain able, but with the Qwiic HAT for the Pi, we might not need to do that.
I spent a lot of time envisioning how the different parts of the board will communicate. One concern I had is that the Qwiic HAT will take up all the pins on the RPi’s GPIO header. Two of those pins (UART) would be needed to communicate with the VESC (speed controller). After some further research, I discovered that Pi 5 has a UART connector separate from the pins on the GPIO header. I’m not yet sure if that’ll be sufficient for communicating with the VESC.
Additionally, the GPS and IMU components I’ve been looking at don’t have well documented Python Packages. I had been hoping to use Python but Arduino libraries for these components have better documentation.
PROGRESS:
I’m currently on schedule with my tasks. We planned to have a finalized parts list by Monday (09/23) and we’re on track to completing it after a few discussions with course staff.
NEXT WEEK’S DELIVERABLES:
Next week, I plan to focus on outlining the software stack for the RPi, sensors and motors. I’d like to make an additional block diagram focusing on the software components on the Pi that will connect to the webapp, poll the sensors and signal the VESC(if needed).
I would like to get my hands on a Pi5 as soon as possible so we can begin preliminary tests like connecting to the website, creating logs, etc. We can borrow one from the course inventory so I will put in a request ASAP.