# MAVLink Start

## Overview

![The MAVLink Start Node.](/files/fqDIw8VDzSA7cuYu2js2)

The **MAVLink Start Node** opens communication with a **MAVLink** serial port that has already been set up in [**Project Settings**](/incari-studio/2023.1/modules/project-settings/mavlink.md) and starts the *heartbeat*, which is done automatically with no action required by the user.

**MAVLink Communication** in **Incari** is available as a plugin and is enabled as default. However, in the case that it is disabled in the **Plugins Editor**, it will not appear in the **Project Settings** and **MAVLink Start** will not show up in the [**Toolbox**](https://github.com/cgi-studio-gmbh/incari-doc/blob/2023.1/overview.md). Please refer to the [**Plugins Editor**](/incari-studio/2023.1/modules/plugins.md) to find out more information.

It is important to note that while the **MAVLink Start Node** starts a **MAVLink** connection, it may not completely finish establishing said connection when the **Node** is executed. This could lead to the **Logic** attached to its **Output Pulse** to not work even though there is technically nothing wrong. In order to avoid this, it is highly suggested to use the [**On MAVLink Start Node**](/incari-studio/2023.1/toolbox/communication/mavlink/events/on-mavlink-start.md) instead. This way, the **Logic** will only execute once the **MAVLink** connection has definitely been established.

Again, the user must first use the **MAVLink Start Node** to open the connection. Separately, the **On MAVLink Start Node** can be used to execute the desired **Communication Logic**.

![MAVLink Start and On MAVLink Start Configuration.](/files/xuOvOJgInkxdaiNMXdus)

[**Scope**](https://github.com/cgi-studio-gmbh/incari-doc/blob/2023.1/toolbox/communication/overview.md#scopes): **Project**, **Scene**.

## Attributes

![The MAVLink Start Node Attributes.](/files/EWKMggzjKmT1Nqvp1Q9C)

| Attribute       | Type          | Description                                                                                                                                                                           |
| --------------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Configuration` | **Drop-Down** | The desired *MAVLink* serial port, which refers back to the selections made under *MAVLink* in the [**Project Settings**](/incari-studio/2023.1/modules/project-settings/mavlink.md). |

## Inputs

| Input             | Type      | Description                                                           |
| ----------------- | --------- | --------------------------------------------------------------------- |
| *Pulse Input* (►) | **Pulse** | A standard **Input Pulse**, to trigger the execution of the **Node**. |

## Outputs

| Output             | Type      | Description                                                                                                                            |
| ------------------ | --------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| *Pulse Output* (►) | **Pulse** | A standard **Output Pulse**, to move onto the next **Node** along the **Logic Branch**, once this **Node** has finished its execution. |

## See Also

* [**MAVLink Stop**](/incari-studio/2023.1/toolbox/communication/mavlink/mavlink-stop.md)
* [**On MAVLink Start**](/incari-studio/2023.1/toolbox/communication/mavlink/events/on-mavlink-start.md)

## External Links

* What is a [*heartbeat*?](https://mavlink.io/kr/services/heartbeat.html)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.incari.com/incari-studio/2023.1/toolbox/communication/mavlink/mavlink-start.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.