> 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/simulink-blocks-reference/efpgasim-library/simulink-sps-workflow/2-inputs-dot-product-configuration.md).

# 2 inputs dot product configuration

## Description

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2FHN1fdgmdrVYyxxzcsQv8%2Fimage.png?alt=media&amp;token=0efe1ac3-affd-4c7f-af24-d24a02671f56" alt=""><figcaption></figcaption></figure>

The **two inputs dot product** block, located in the **cpuhilios\_lib** library, is used to configure 8 2-input dot product (DP2). Results from DP2 are sent through SFP link to an other eHS core.

Result of each DP2 is equal to: Signal1 \* Gain1 + Signal2 \* Gain2

## Mask parameters

{% columns %}
{% column %}

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2FyBQmqz6p89buQEyvxF1Y%2Fimage.png?alt=media&amp;token=0cfedae2-019e-4b8a-81c9-87661ab3fa4f" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column %}

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2FJxYuKev7v5NK1V6TtV8Z%2Fimage.png?alt=media&amp;token=9ef3c962-0166-455e-babb-99d81fa454d7" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

{% tabs %}
{% tab title="DP2 #n" %}

| Parameter          | Description                                                             |
| ------------------ | ----------------------------------------------------------------------- |
| **Signal 1 and 2** | This is used to choose which measurement from eHS is used.              |
| **Gain 1 and 2**   | This indicates the gain to apply to Signal 1 and Signal 2 respectively. |
| {% endtab %}       |                                                                         |

{% tab title="Configuration" %}

| Parameter                      | Description                                                                                                                                                                                                          |
| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Controller name**            | Links this block to an OpCtrl block by entering the same 'Controller Name' as specified in the OpCtrl block. The OpCtrl block controls initialization of the settings of one specific FPGA-based card in the system. |
| **LoadIn port number**         | This should reflect the LoadIn port used to configure the block on the FPGA.                                                                                                                                         |
| **Signal name list selection** | This value is used to populate the different popup list for the measurement configuration.                                                                                                                           |
| **Custom signal name list**    | This value is used to give custom signal list to the popup list for the measurement configuration.                                                                                                                   |
| **Sampling time**              | This value is the sampling time of the simulation.                                                                                                                                                                   |
| {% endtab %}                   |                                                                                                                                                                                                                      |
| {% endtabs %}                  |                                                                                                                                                                                                                      |

## Inputs

This block has no input

## Outputs

| Output | Description                                                                                                                                                                                                                     |
| ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Status | <p>Returns the following values:<br>0: No error.<br>-1: Block could not be matched with an OpCtrl block (check the 'controller Name' value), or card initialization problem.<br>-2: Internal memory initialization problem.</p> |

## Characteristics and limitations <a href="#heading-title-text" id="heading-title-text"></a>

| Direct Feedthrough   | N/A |
| -------------------- | --- |
| Discrete sample time | YES |
| XHP support          | YES |
| Work offline         | NO  |


---

# 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/simulink-blocks-reference/efpgasim-library/simulink-sps-workflow/2-inputs-dot-product-configuration.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.
