> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/xbb020-and-xbb021-manufacturing-description/assembly/enclosure.md).
# Enclosure
1\. Take the box and attach the rubber grommet to the oval hole on the right. It can be difficult to get it there so you have to push and pry with both force and finesse.
2\. Make a small hole (type 3-4mm) in the middle of the grommet.
3\. Screw the cable entry into the threaded hole on the left.
4\. Screw the assembled mounting plate into the box in the 4 corners (screws are included with the mounting plate/box).
5\. Thread the micro-USB connector with the cable through the rubber grommet and attach a cable tie anchor on the right side of the inside of the box.
6\. Approx. 10 cm from the micro-USB connector, attach the cable with a cable tie to the anchor, make a loop with the USB power cable and carefully connect the micro-USB cable to the connector on the BBO (see picture below of finished assembly. NOTE, the picture below is on a WiFi BBO without an Ethernet connector).
7\. Carefully thread the Ethernet connector through the rubber grommet, connect this to the Ethernet socket on the BBO (far right next to the micro-USB connector. NOTE, the Ethernet connector is not included in the picture above).
---
# 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://help.boomerang3.com/xbb020-and-xbb021-manufacturing-description/assembly/enclosure.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.
