> For the complete documentation index, see [llms.txt](https://docs.incari.com/incari-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.incari.com/incari-studio/toolbox/communication/canopen.md).

# CANopen

## Introduction

The **CANopen Nodes** provide a means for the user to perform several actions within the *CANopen* protocol. *CANopen* is a form of communication that extends the functionality of the [*CAN*](/incari-studio/toolbox/communication/can.md) (Controller Area Network) protocol. It provides a standardized framework for defining communication and application layer protocols for devices and systems employing *CAN* as their underlying physical layer. This standardization facilitates seamless interconnection and interoperability among a diverse range of devices, including but not limited to sensors and motor controllers.

To use the **CANopen Nodes** in **Incari**, the user needs to locate the [**CANopen Attributes**](/incari-studio/modules/project-settings/canopen.md) in **Project Settings** and upload a *DFC* file.

## CANopen Guideline

These are the guidelines for incorporating **CANopen Communication** into a **Project**.

* To properly start a connection, see the [**General Guideline**](/incari-studio/toolbox/communication.md#general-guideline) on the Communication Introduction page.
* Once the connection has been established, there are several **Nodes** that cover important functions of **CAN Communication**.
  * [**CANopen Send**](/incari-studio/toolbox/communication/canopen/canopensend.md) sends a **CANopen** message when triggered.
  * [**On CANopen Receive**](/incari-studio/toolbox/communication/canopen/events/oncanopenreceive.md) executes once a message is received.
* To properly stop a connection, see the [**General Guideline**](/incari-studio/toolbox/communication.md#general-guideline) on the Communications Introduction page.

## Contents

* [**CANopen Send**](/incari-studio/toolbox/communication/canopen/canopensend.md)
* [**CANopen Start**](/incari-studio/toolbox/communication/canopen/canopenstart.md)
* [**CANopen Stop**](/incari-studio/toolbox/communication/canopen/canopenstop.md)
* [**Events**](/incari-studio/toolbox/communication/canopen/events.md)
  * [**On CANopen Receive**](/incari-studio/toolbox/communication/canopen/events/oncanopenreceive.md)
  * [**On CANopen Start**](/incari-studio/toolbox/communication/canopen/events/oncanopenstart.md)
  * [**On CANopen Stop**](/incari-studio/toolbox/communication/canopen/events/oncanopenstop.md)

## External Links

* Introduction to [*CANopen*](https://www.csselectronics.com/pages/canopen-tutorial-simple-intro).
* Differences between [*CAN and CANopen*](https://www.rfwireless-world.com/Terminology/Difference-between-CAN-and-CANopen.html).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.incari.com/incari-studio/toolbox/communication/canopen.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.