> For the complete documentation index, see [llms.txt](https://docs.hackerfab.org/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackerfab.org/home/individual-fab-information/carnegie-mellon-university/cmu-updates/matthew-chois-updates/week-8-update.md).
# Week 8 Update
Week 8 Update (3/16)
What was accomplished:
* assembled stepper motor electronics setup, and updated arduino code so that it would revolve precisely ONCE(should work on the final assembly, since we are using the same stepper motor) WITH a button setup
* re-designed spin coater CAD on onshape
* planned out a roadmap on how to assemble electronics(have a single arduino mega controlling everything, or find a way to "link" smaller microcontrollers together)
Roadblocks/issues:
* The cable that needs to be used is micro usb, and there are no cables that I could find that directly connect onto my labtop(only has C cable connections, not sure if there is a micro usb -> usb c cable)
* The stepper motor requires a different voltage from the microcontroller, so either a second power supply is needed for the microcontroller, or a voltage de-regulator(12v to 5v) is required in the electronics setup
TO DOs:
* Once syringe arrives, take measurements of it, before modifying 3d printed parts in previous cad according to those measurements, and begin testing
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.hackerfab.org/home/individual-fab-information/carnegie-mellon-university/cmu-updates/matthew-chois-updates/week-8-update.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.jpg?alt=media&token=044f2613-0159-4951-9e1e-4b10f7553a01)
