> For the complete documentation index, see [llms.txt](https://www.projectpanoptes.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.projectpanoptes.org/build/deploy/camera-focus.md). # Camera Focus How to focus the cameras in a PANOPTES unit. The Canon cameras that are used for PANOPTES do not have an auto-focus mechanism so it is important to set a proper focus *after* all other deployment is complete but before a [polar alignment](/build/deploy/polar-alignment.md). {% hint style="info" %} Note that there are additional camera settings that should be set before the focus. See [Camera Setup](/build/hardware/camera-box/camera-setup.md) for details. {% endhint %} ### Focus The video below shows the general movements for the lens in order to focus the camera. {% embed url="" %} ### Focus Procedure Focusing is currently done via the live-view finder on the back of the camera while looking down into the box. This is sometimes awkward depending on the size of the box and the wiring, but the procedure should work well. {% hint style="warning" %} To focus a camera you will need to be able to view something at or near "infinity". At night this can be actual stars. If you can only focus during the day your unit will need to be able to "see" a distant object, e.g. a distant mountain range, far away lights, etc. {% endhint %} --- # 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://www.projectpanoptes.org/build/deploy/camera-focus.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.