# CAN Start

## Overview

![The CAN Start Node.](/files/WbzMFZIXfjiR7toKmQPx)

The **CAN Start Node** starts communication with a **CAN** connection that has already been set up in [**Project Settings**](/incari-studio/2024.1/modules/project-settings/can.md).

It is important to note that while the **CAN Start Node** starts a **CAN** 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 CAN Start Node**](/incari-studio/2024.1/toolbox/communication/can/events/oncanstart.md) instead. This way, the **Logic** will only execute once the **CAN** connection has definitely been established.

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

![CAN Start and On CAN Start Configuration.](/files/rXqWzgZG7QlxnkSfjIW1)

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

## Attributes

![The CAN Start Node Attributes.](/files/LvTUlYoR64lpd3Q8iXZz)

| Attribute       | Type          | Description                                                                                                                                                           |
| --------------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Configuration` | **Drop-down** | The identifying connection name that will be used, which is one that was set up in the [**Project Settings**](/incari-studio/2024.1/modules/project-settings/can.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

* [**CAN Stop**](/incari-studio/2024.1/toolbox/communication/can/canstop.md)
* [**CAN Send Packet**](/incari-studio/2024.1/toolbox/communication/can/cansendpacket.md)


---

# 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/2024.1/toolbox/communication/can/canstart.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.