# Programming Motor Telemetry

## Motors and Telemetry&#x20;

Recall that **telemetry** is the process of collecting and transmitting data. There is a lot of useful information our motors could send back to us, but to start let's have it output the power based on the joystick's movement.&#x20;

Similar to what we did for our servo program, let's add a <img src="/files/-MWBJfpbTuatRMfbhnlO" alt="" data-size="original"> block from the telemetry menu to the end of our ![](/files/9JmuqmIVva0NqYySaYlc) loop:

<figure><img src="/files/HwtwcQGeNVPRmnoFkRkN" alt=""><figcaption></figcaption></figure>

From the DcMotor menu pullout the ![](/files/UMSLYwqOpGB3x4y2RGDw) block . Drag the block and attach it to the number **parameter** on the telemetry blocks.&#x20;

Change the key parameter to "Motor Power"&#x20;

<figure><img src="/files/rHmlxkGS4cNinlUHWJYB" alt=""><figcaption></figcaption></figure>

When the OpMode is run the telemetry block will display the current power based on the joysticks movement. Give it a try!

## Full Program

<figure><img src="/files/WWLlPIRYwJODeavAo1zD" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.revrobotics.com/duo-control/hello-robot-blocks/part-1/programming-motors/programming-motor-telemetry.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
