> For the complete documentation index, see [llms.txt](https://docs.freeflysystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.freeflysystems.com/products/products/alta-x/untitled-5/external-computer.md).

# External Computer

## External Computer Mounting

<table data-header-hidden><thead><tr><th width="160"></th><th></th><th></th><th data-hidden data-type="files"></th></tr></thead><tbody><tr><td></td><td></td><td></td><td></td></tr><tr><td>1.</td><td>To mount an external computer, first open the chassis.  Directions for opening the chassis can be found in the maintenance section.</td><td></td><td></td></tr><tr><td>2.</td><td>Once the chassis is open use the 32x32 mm hole pattern in the lower chassis plate  to mount the computer.  The hole pattern is sized for M3 bolts. </td><td><img src="https://lh3.googleusercontent.com/GM4WWcYwP87bxoz6QxyzHwP1K6eJiqNFBJKgU0282UP7EiRpzEZ53pJZbi-Md2g9vjTVjYH5_mQLJbpalbMGbl2JA-U082ykDBcW_rSWKZVcAc3_i6eWuE8vyj9SfXO0uktEBrRy" alt=""></td><td></td></tr><tr><td>3.</td><td>After mounting the external computer and routing its power and I/O cables, close the chassis.</td><td></td><td></td></tr><tr><td>4.</td><td>TELEM1 and TELEM 2 are internal UART for ext computer integration. Both are exposed as 6pin GH. By Default TELEM1 is typically plugged into the FRX Pro. TELEM2 is shared with wifi, so wifi can't be used if you connect anything to TELEM2. SET_TEL1_BAUD or SET_TEL2_BAUD is how you would adjust baud rates.</td><td></td><td></td></tr></tbody></table>

## Power & Comms

Power is available from a few sources:

* 5V from expansion ports (see Expansion Ports section)
* 5V or 12V DC-DC converters

Communication to the aircraft is currently available through the Mavlink on the expansion port labelled "UART" (see expansion ports sections)


---

# 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.freeflysystems.com/products/products/alta-x/untitled-5/external-computer.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.