# CAN

![The CAN Settings.](https://4263346935-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLnh3x8s9fddWeG8TaAug%2Fuploads%2Fgit-blob-8b1c05b8d0328b0a05f947baad96eba634e04b6e%2Fprojsettscan20241.png?alt=media)

The **CAN Settings** cover the necessary data to provide functionality to the [**CAN Nodes**](https://docs.incari.com/incari-studio/2024.1/toolbox/communication/can).

`Name` is an identifying name chosen at the user's discretion. This will show up in the **Nodes** as a choice for the `Configuration` **Attribute**.

`Baud Rate (Windows - PCAN)` is the speed of the communication for the channel. More information about this metric can be found in the **External Links** section.

`Channel (Windows - PCAN)` is the USB port that *CAN* is connected to on *Windows*.

`Interface (Linux - SocketCAN)` is the identifying name of the *CAN* Bus. *Virtual CAN* is also possible within **Incari**. This is only used for Linux.

Furthermore, the `Channel` and `Interface` can both be specified, in the case that the user's platform is different than the target platform. If there is no difference in platforms, only one needs to be filled in.

A `DBC File` needs to be uploaded and selected. This `DBC File` is a vital part of the **CAN** protocol, as it stores all data regarding the connections between devices.

`Is Autostart` can be enabled or disabled and dictates when the channel is run (from the beginning of an application's life cycle or when the appropriate **Nodes** are used).

It is worth noting that **Incari** supports both the [*base (or standard) frame format*](https://en.wikipedia.org/wiki/CAN_bus#Base_frame_format) and the [*extended frame format*](https://en.wikipedia.org/wiki/CAN_bus#Extended_frame_format).

## See Also

* [**CAN Nodes**](https://github.com/cgi-studio-gmbh/incari-doc/blob/2024.1/modules/toolbox/communication/can/README.md)

## External Links

* More information on the [*Baud metric*](https://en.wikipedia.org/wiki/Baud).