> For the complete documentation index, see [llms.txt](https://docs.ceruleansonar.com/c/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ceruleansonar.com/c/sonarview/ardupilot-vehicle.md).

# ArduPilot Vehicle

Some of our devices integrate with an Ardupilot vehicle when parameters are configured correctly. This includes the Omniscan family, the Tracker 650, and the ROVL/Omnitrack. If you have a [mavlink2rest vehicle configured in your session](/c/sonarview/session-configurations/vehicle.md) and connect to one of these views, in the left drawer you will see a button that says "Check Ardupilot Parameters". <br>

<figure><img src="/files/MVmIgPA5SQFaQEVJ8G62" alt=""><figcaption></figcaption></figure>

This will bring up the "Ideal Arudpilot Parameters" dialog. If your parameters differ from our recommendations, you will see a dialog like this:<br>

<figure><img src="/files/34LPqamyas5MEr4dY7GI" alt="" width="212"><figcaption></figcaption></figure>

If you hit "Set Vehicle Parameters", every checked parameter will be set to the value on the far right.

{% hint style="warning" %}
If your parameters differ from our recommendations, certain interactions with the Ardupilot flight controller will not work properly (i.e. setting the position from SonarView)
{% endhint %}

If your parameters do NOT differ from our recommendations, you will see:

<figure><img src="/files/7tCpDsaQ4A1AYc0XndIi" alt=""><figcaption></figcaption></figure>

Additionally, the Omniscan and Tracker 650 views can directly set the position of the ArduPilot vehicle (ROVL view does this automically when selected). <br>