> For the complete documentation index, see [llms.txt](https://docs.adti.camera/adti-45cmf-module-quick-start-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adti.camera/adti-45cmf-module-quick-start-guide/mavlink-and-geo-tagging-qgroundcontrol-2.md).
# MAVlink and Geo-tagging (QGroundControl) #2
This page will show you how to connect the camera to pixhawk for MAVlink QGC
The ADTi 45CMF cameras can work directly with ADTI POS \&CTRL Unit for MAVlink QGC, if you are using standard PX4 or Ardupilot firmware and standard QGC for ground control software, you do not need to do any another work, simply connnect the camera with POS & CTRL Unit, choose the right IP address inyour video feed device such as GCS or you PC (192.168.144.100 ) and then connect and power on.
you will see the video feed, as well as QGC will automatically download the camera QGC user interface.
1. **Hardware Connections , you will need:**
1Flight controller with PX4 or ardupilot and compatible with QGC
2\) ADTi 45CMF Camera
3\) ADTi POS Unit [(Camera POS & CTRL Units)](https://www.adti.camera/product-page/camera-pos-ctrl-units-for-direct-geotagging)
4\) Cable for connecting the camera
5\) Cable for connecting the flight controller
2. **Please review the following video for details:**
{% embed url="" %}
---
# 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.adti.camera/adti-45cmf-module-quick-start-guide/mavlink-and-geo-tagging-qgroundcontrol-2.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.