> 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/fab-toolkit/spincoater/spin-coater-v1-build-to-do.md).

# Spin Coater V1 Build (to do)

Here is a [BOM](https://docs.google.com/spreadsheets/d/1n8dB-Vh3pZN99sLe7-j91mzc43uWQ1A1lQEvetoBo_8/edit?gid=0#gid=0) of our most recent spin coater V1 build. More info to come soon!

* Collect all necessary measurements of the current spin-coater to create the new 3D mode.
* Finalize an updated 3D model that includes the servo mount and any necessary adjustments to the lid design.
* Order required components, including a servo motor, necessary mounting brackets, and plastic material for a redesigned lid.
* Cut and prepare the new lid, ensuring proper fit and clearance for rotation
* Assemble all components and build the initial prototype.
* Conduct preliminary functionality tests, focusing on servo movement and integration with the claw mechanism.
* Optimize servo rotation angles and positioning to maximize clearance while minimizing occupied space.
* Conduct final system tests to verify smooth automation and reliable lid operation.
* Implement necessary refinements and finalize the design for long-term use.


---

# 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/fab-toolkit/spincoater/spin-coater-v1-build-to-do.md?ask=<question>&goal=<user_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.