> 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/machines/dual-pmsm-motors-vdq-advanced-command.md).

# Dual PMSM Motors VDQ Advanced Command

## Description

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-a56a588887d24bbc373fe68880d9bb43c4828849%2Fsps-ehs-vdq-cmd.png?alt=media" alt=""><figcaption></figcaption></figure>

The **Dual PMSM Motors VDQ Advanced Command** block, located in the **eFPGAsim/External circuit editor workflow/machines/Tools** library, provides a way to change values sent to the FPGA during the execution of the simulation.

With the VDQ model, this block allows the user to:

* Update Ra, Rb and Rc values
* Force Ld and Lq values
* Force Id and Iq values at the table Input
* Force the theta angle to a position
* Update the cut-off frequency of the Vabc monitoring filter
* Force the flux value

The purpose of this block is to concatenate the values in a standard bus signal which can be read by advanced command capable blocks such as the [PMSM VDQ model block](https://www.opal-rt.com/docs/rt-lab/simulink-blocks-reference/efpgasim-library/simulink-sps-workflow/machines/dual-pmsm-motors-vdq.md).

## Mask parameters

This block has no parameters.

## Inputs

Inputs of this block should always be constants block.

Using the RT-LAB variable monitor, it is possible to change the values send to the FPGA by changing the constants values.

## Outputs

The output must be connected to an advanced command capable block port such as the [PMSM VDQ model block](https://www.opal-rt.com/docs/rt-lab/simulink-blocks-reference/efpgasim-library/simulink-sps-workflow/machines/dual-pmsm-motors-vdq.md).


---

# 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/machines/dual-pmsm-motors-vdq-advanced-command.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.
