# ElapsedTime Logic
For now our goal will be to have the motors move forward for 3 seconds. To accomplish this we need to edit our main **While Loop** so that it triggers when the OpMode is active AND the ElapsedTime timer is less than or equal to 3 seconds.
## Setting a Time Limit
Lets start by creating our less than or equal to condition. Grab the from the **Logic** menu.
Next select the  block from the **ElapsedTime** menu. Snap the block into the left side of the block. Using the dropdown menu, change the generic  to the variable we established earlier.
On the other side of our equation, we need to add a block from the **Math** menu. Change the number block to 3.
Right now the is equal to three. Use the arrow next to the equal sign to choose the less than or equal to sign from the dropdown menu.
With our time condition ready, we can set it aside for a moment.
## Modifying Our While Loop
Now let's set up our logic to modify our While Loop.
First, grab an block from the **Logic** menu. The  block we currently have as part of our loop will be moved to the lefthand side.
On the other side, add the block:
This block set will connect where the  block originally was. Now the w**hile loop** will now activate when both conditions of the *AND* block are true.
### Quick Check!
Let's give our OpMode a try and test the following scenarios:
* What happens when hitting play quickly after the initialization button is pressed?
* What happens when hitting play 2 seconds after the initialization button is pressed?
* What happens when hitting play 10 seconds after the initialization button is pressed?
What happens while testing?
You may notice the robot moves different distances depending on how long the wait is between INITIALIZATION and PLAYING the program. But why is that?
Remember our timer starts counting when created. Currently, our program creates our timer during initialization meaning it's counting up before Play is ever pressed. If we wait too long our robot may not do anything at all when clicking Play!
## Resetting the Timer
Not being able to pause between initialization and pressing Play is probably not ideal in most situations. It certainly makes tracking how far the robot will travel more challenging, the opposite of what we'd like ElapsedTime to help us do.
To keep this from happening the timer should be reset once the OpMode is active. Grab the call  block from the ElapsedTime menu and switch it to our runtime variable.
This will be added to our program BELOW the comment and ABOVE the while loop.
Since this is before our loop our robot will complete it once when Play is pressed. Then will complete the check for our while loop.
Test your program again with this change!
{% hint style="success" %}
Now let's explore what happens when we change our time limit to different amounts. You can adjust your time limit by changing the 3 in our  block to a different number.
Consider marking different goals on the floor with tape to practice determining how much time the robot needs to reach it.
{% endhint %}
## Adding Telemetry
In previous parts, we've looked at adding telemetry as a way for the robot to communicate with us. In this situation, it would be helpful for the robot to be able to tell us how much time it has counted so we can make adjustments to our program!
Recall we can find our telemetry block under the utilities menu:
Our  block will snap into our number slot.
For our **key** let's call it "Number of Seconds in Phase 1" for now. This will be useful for distinguishing where in our program our robot is during the next section.
Save your OpMode and give it a try!
---
# 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-3/elapsed-time/elapsedtime-logic.md?ask=
```
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.