# CAN Send Packet

## Overview

![The CAN Send Packet Node.](/files/6vePJSx1LOS7cdzq8WzH)

The **CAN Send Packet Node** is used to send a data **Packet** along the **CAN** network, once a **CAN** `Message` is selected from the **Drop-down Menu**.

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

## Attributes

![The CAN Send Packet Node Attributes.](/files/9BYGV6HzyqMJ3Tg3rMev)

| 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). |
| `Message Name`  | **Drop-down** | The selected `Message` from the uploaded *DBC* file.                                                                                                                  |

## Inputs

| Input             | Type      | Description                                                             |
| ----------------- | --------- | ----------------------------------------------------------------------- |
| *Pulse Input* (►) | **Pulse** | A standard **Input Pulse**, to trigger the execution of the **Node**.   |
| `Signal [n]`      | **Float** | The *Signal* or *Signals* of a *Message* from the specified *DBC* file. |

## 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. |

## Example

To visualize how the **Node** works a bit better, refer to the images below. The first is an example *DBC* file, which would have been added in the **CAN Project Settings**. There are two *Messages* and two *Signals*, each of which correspond to one of the *Messages*.

![DBC File Example.](/files/4qfNLkJ4WEsGnUMtYrjz)

When the connection has been added in **Project Settings** and those changes are saved, the user can select the desired `Message Name` -- here Message1 -- which will make an input appear called `Signal1`. If a *Message* has multiple *Signals* -- for example if Message1 had two *Signals* called Signal1a and Signal1b -- all appear as inputs of the **Node**.

![CAN Send Packet Node with Connection.](/files/pCoUcvuIisgwORjddMz7)

## See Also

* [**CAN Start**](/incari-studio/2024.1/toolbox/communication/can/canstart.md)
* [**CAN Stop**](/incari-studio/2024.1/toolbox/communication/can/canstop.md)

## External Links

* The example [*DBC* file.](https://www.csselectronics.com/pages/can-dbc-file-database-intro)


---

# 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/cansendpacket.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.