> 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/working-docs/cmu-updates/matthew-chois-updates/week-12-update.md).

# Week 12 Update

What was Accomplished:

* Developed the Demo 2 presentation for updates
* Tested STEPs for electronics with the stepper motor
* Updated the clamp mechanism for the mounting system

Roadblocks:

<figure><img src="/files/dVCVamJxzXVLmSk1vLBH" alt=""><figcaption><p>The clamp hole clearances were too large, so will try decreasing and testing</p></figcaption></figure>

* Potential issue with the limit of the stepper motor not being calibrated properly(will eventually add a nut as a true limiter)
* The clamp mechanism is still not as great as I want( the print was slightly defected, and will replace)

Plans for next week:

* print new syringe pump WITH mounting holes and cad mounting system for lab automation
* Work with callum to finalize touches on liquid handling mounting for the tubing


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hackerfab.org/home/working-docs/cmu-updates/matthew-chois-updates/week-12-update.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.