> For the complete documentation index, see [llms.txt](https://dev.solid-run.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.solid-run.com/solidsense/solidsense-other-articles/solidsense-n8-compact-rs485-and-can-bus.md).

# SolidSense N8 Compact RS485 and CAN bus

{% hint style="info" %}
On SolidSense OOB image RS485 and CAN utilities are already built-in
{% endhint %}

## Test CAN bus communication

**1. Enable device can0 (for ex):**

```
ip link set can0 up type can bitrate xxxxxx
```

* (ex: 125000)

**2. Bring the CAN interface up:**

```
ifconfig can0 up
```

{% hint style="info" %}
To discover your CAN bus interface name, please run ‘ ip link show ’.
{% endhint %}

**3. To start testing the CanBUS, you have to install the can-utils package by running:**

```
sudo apt-get install -y can-utils 
```

* For more information, please follow the [CAN-Utils](https://github.com/linux-can/can-utils), which are available for Debian/Ubuntu etc

**4. Print all data received by CAN interface to “can\_test” file (for ex):**

```
candump can0 >> /tmp/can_test &
```

**5. Send data to the bus by executing (for ex):**

```
cansend can0 "123#1234"
```

**6. Check received data by opening “can\_test” file:**

```
cat /tmp/can_test
```

## Test RS-485 communication

An example for testing RS485 communication:

**1. Open a test file “rs485\_test”**

```
rs485conf -e 1 /dev/ttymxc2
touch /tmp/rs485_test
stty -F /dev/ttymxc2 raw -echo -echoe -echok
```

**3. Print received data to “rs485\_test” file:**

```
cat /dev/ttymxc2 > /tmp/rs485_test &
echo "rs485" > /dev/ttymxc2
```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://dev.solid-run.com/solidsense/solidsense-other-articles/solidsense-n8-compact-rs485-and-can-bus.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.