> For the complete documentation index, see [llms.txt](https://docs.motus.org/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motus.org/en/stations/station-equipment.md). # Station Equipment A Motus station consists of three main components: * **Receiver:** this is the computer which records and stores the radio data * **Antennas:** there are several types of antenna designs. They are 'tuned' to listen to a narrow range of frequencies. Each antenna gets its own coaxial cable and depending on the receiver type and listening frequency, it's own 'dongle', or USB devices which listen to a specified frequency range (i.e., software defined radio). * **Power supply:** this provides power to the receiver. Most off-grid stations us solar power, but AC power is most reliable. The number one reason for a station to malfunction is a power failure. --- # 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.motus.org/en/stations/station-equipment.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.