> For the complete documentation index, see [llms.txt](https://guides.privatesolution.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.privatesolution.org/dma-card-setup/aim-devices.md).

# Aim Devices

**Private Solutions Aim Devices & Accessories** — browse the input devices and companion hardware currently offered in the catalog. Models use different connections and are not automatically interchangeable; check the exact listing before choosing.

### What you will find

* **Input devices:** Kmnet, Makcu, and Ferrum options.
* **Companion hardware:** Mini PC, Thunderbolt dock, and SSD options, depending on current stock.

### Before ordering

1. Open the [Aim & Accessories catalog](https://privatesolution.org/products/#hardware-aim) and note the exact product/model.
2. Check the product details for the supported connection type and any host/device requirements.
3. Use the manufacturer or seller instructions for wiring and power. Use the correct data cable and clearly labeled ports; a charge-only cable will not carry data.
4. Confirm the operating system recognizes the device before adding other accessories. Change one cable or port at a time if troubleshooting.

### Not sure which one fits?

Compare the current [Aim & Accessories](https://privatesolution.org/products/#hardware-aim) and [bundle options](https://privatesolution.org/products/#hardware-bundle). For a compatibility check, [open a Private Solutions Discord ticket](https://discord.gg/XFEkf2kV26) and include the exact model, your PC setup, and what you want to connect.


---

# 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://guides.privatesolution.org/dma-card-setup/aim-devices.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.