> 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/lithography-stepper/lithography-stepper-v2.1+-build/enclosure-option.md).

# Enclosure Option

This page describes the design of an enclosure system for the stepper to help block UV light as well as protect the sample from particulate during patterning.

Authors: Italia Grant (<igrant@andrew.cmu.edu>), Kashvi Verma (<kashviv@andrew.cmu.edu>)

<img src="https://2353182699-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXgXjz6D0Vz2o0EOp8JO5%2Fuploads%2FAzgbY3BeghekDkpDdhfK%2Funknown.png?alt=media&amp;token=94bad610-f0eb-434d-bb33-1ada0cf35d09" alt="" height="440" width="331">

It may be helpful to create an enclosure around the stepper to reduce the effects of ambient UV light exposure as well as miscellaneous particulate landing onto the chip. Below is a description of the team's attempt at creating such an enclosure from acrylic.

"The acrylic enclosure is made up of 5 ⅛ in acrylic sheets, as well as a door on the side to make transferring and taking out chips easier. This can be seen below. We measured along each side of the stepper and added an inch and a half in allowance to the measurements. Adding this allowance helps prevent the enclosure from breaking or bumping a piece of the stepper, such as the camera.  The brackets used to hold the enclosure together were 1-inch by 1-inch 3D-printed corner brackets (obtained from [cults3d](https://cults3d.com/en/3d-model/various/internal-corner-bracket-counter-sunk-holes)), which we were able to scale in the 3D printer software (we used Bambu Studio) to be this size. With the pieces figured out, we used OnShape to create a 3D model. When creating the screw holes for the corner brackets, you must take into account the thickness of the acrylic sheet and add the thickness of the acrylic sheet to the length of the corner brackets' edge to the center of the screw hole (as shown below). Once the model was finished, we laser-cut the acrylic sheets and assembled the enclosure using 8 corner brackets with M2.5 full thread socket cap head screws with nuts used to secure them."

<img src="https://2353182699-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXgXjz6D0Vz2o0EOp8JO5%2Fuploads%2FUc5WaNdZn62z0LEJErQI%2Funknown.png?alt=media&amp;token=afb7c1d4-fad9-4bad-a8fe-11316aaf7c18" alt="" height="197" width="612">

<img src="https://2353182699-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXgXjz6D0Vz2o0EOp8JO5%2Fuploads%2FvXSEOOQ5FRFJoO3JQ1LZ%2Funknown.jpeg?alt=media&amp;token=ce2bb824-48f5-4856-b5ba-fa51c51a9aba" alt="" height="168" width="269">

The specific acrylic used is available from McMaster-Carr:

* [24 in x 12 in x ⅛ in Clear Scratch- and UV-Resistant Cast Acrylic Sheet (Quantity: 2)](https://www.mcmaster.com/8560K257/)
* [24 in x 48 in x ⅛ in Clear Scratch- and UV-Resistant Cast Acrylic Sheet (Quantity: 1)](https://www.mcmaster.com/8560K262/)

As of Nov. 2026, the CMU fab has not found it necessary to use the enclosure yet, but as our stepper system improves and we seek to pattern down to smaller feature sizes, we may find it increasingly helpful in order for us to achieve better-functioning devices.


---

# 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/lithography-stepper/lithography-stepper-v2.1+-build/enclosure-option.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.
