> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/rt-lab/simulation-control-monitoring-and-logging/interact-using-dashboards/interact-with-data-points-via-panels/data-point-compatibility.md).

# Data Point Compatibility

You don’t need to know these details to use Dashboards, but they explain why some data points may not appear when creating connections.

**Key Rules:**

* **COMMAND → PARAMETER**\
  Both ends send and receive updates. Multiple COMMAND points can connect to one PARAMETER; the latest COMMAND value updates the PARAMETER. COMMAND points are found in command widgets.
* **DISPLAY → INPUT or OUTPUT**\
  DISPLAY points only receive updates. Multiple DISPLAY points can connect to one INPUT or OUTPUT. DISPLAY points are found in display widgets.

**Compatibility Requirements:**

* Follow the allowed directions (e.g., OUTPUT → DISPLAY).
* Data types must match (e.g., REAL, BOOLEAN).
* Sizes must match for non-scalar data.
* Points cannot belong to the same standard or Simulink model.
* A “To” data point can only have one connection.
* Vector elements must connect to another vector element or a widget.


---

# 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://www.opal-rt.com/docs/rt-lab/simulation-control-monitoring-and-logging/interact-using-dashboards/interact-with-data-points-via-panels/data-point-compatibility.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.
