> For the complete documentation index, see [llms.txt](https://docs.influxtechnology.com/support_guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.influxtechnology.com/support_guides/product-tutorial-videos/rebel-dash/rebel-dash-tutorial-videos/how-to-display-signal-in-the-rebel-dash.md).

# How to display signal in the Rebel Dash

{% embed url="<https://youtu.be/_R3nQFmrTCY>" %}

The Rebel Dash is part of our compact, highly flexible, rugged CAN bus products. The Rebel Dash is designed to be integrated with the Rebel range of data loggers but can be used as a standalone CAN display.

The Rebel Dash is a freely distributable application for standalone CAN signal display configuration (using a DBC file). This video explains how to display signal in the Rebel Dash.

The Rebel Dash exemplifies a product that is both easy to install and easy to use. For example, the Rebel Dash is automatically switched on or off by the Rebel data logger during sleep mode so, no user intervention is required.

With a straightforward mounting system, you can be monitoring vehicle CAN data graphically within minutes.

with Dialog software, a rebel dash can be configured in few clicks. In this video, we will learn how to configure a rebel dash in Dialog software.


---

# 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://docs.influxtechnology.com/support_guides/product-tutorial-videos/rebel-dash/rebel-dash-tutorial-videos/how-to-display-signal-in-the-rebel-dash.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.