Bfeher at 20:49, 11 May 2012

2012-05-11T20:49:56Z

Tfriez: Created page with "ARDUINO_MEGA_Functions_and_Variables|Functions and Variables
{| |- |An internal 32-bit clock is maintained by the VEX firmware. It..."

2012-05-09T21:29:42Z

Created page with "<yambe:breadcrumb>ARDUINO_MEGA_Functions_and_Variables|Functions and Variables</yambe:breadcrumb> {| |- |An internal 32-bit clock is maintained by the VEX firmware. It..."

New page

<yambe:breadcrumb>ARDUINO_MEGA_Functions_and_Variables|Functions and Variables</yambe:breadcrumb>
 

{|
|-
|An internal 32-bit clock is maintained by the VEX firmware. It counts in units of 1-millisecond. Four timers (T1, T2, T3, and T4) are built using this timing capability. These four timers can be individually reset to zero within a program. Theses timers are useful for measuring elapsed time of events.

16-bit integers are the default variable type for ROBOTC on the VEX. All of the timing functions operate with 16-bit signed variables. This does mean that caution should be exercised in programming to avoid overflow of timer values. A 16-bit signed variable has positive values in the range 0 to 32,767 and programs should periodically reset any timers that they use to prevent overflow.

32-bit integers are the default variable type for ROBOTC on the Cortex. All of the timing functions operate with 32-bit signed variables. A 32-bit signed variable has positive values in the range 0 to 2,147,483,648 and programs should periodically reset any timers that they use to prevent overflow.
|-
|}
 

{{tl|1|1}}
 

== ClearTimer ==
{| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
|-
| class="functionType"| void ClearTimer(TTimers theTimer)
|-
| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_void|void]]) Timers start counting as soon as the CORTEX is powered on. A user's program should reset a timer before using it, so use this function to reset the value of the specified timer to zero.
|-
|
{| class="parameterTable" cellpadding="5%" width="100%"
! width="20%" style="border-style: solid; border-width: 0px 0px 1px 0px"|Parameter
! width="60%" style="border-style: solid; border-width: 0px 0px 1px 0px"|Explanation
! width="20%" style="border-style: solid; border-width: 0px 0px 1px 0px"|Data Type
|-
| style="border-style: solid; border-width: 1px 0px 0px 0px"|''theTimer''
| style="border-style: solid; border-width: 1px 0px 0px 0px"|The timer to clear.
| style="border-style: solid; border-width: 1px 0px 0px 0px"|[[Data_Types#dataType_TTimers|TTimers]]
|-
|}

Timers:
*T1
*T2
*T3
*T4
|-
|
{|
|-
|<syntaxhighlight lang="ROBOTC">
ClearTimer(T1); // resets the value of Timer "T1" back to zero seconds
</syntaxhighlight>
|-
|}
|-
|}
 

== nClockMinutes ==
{| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
|-
| class="variableType"| word nClockMinutes
|-
| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_word|word]]) This read/write variable provides access to the CORTEX clock described above. The value ranges from 0 to 1439 before it wraps around back to 0. Note: there are 1440 minutes in 24 hours.
|-
|
{|
|-
|<syntaxhighlight lang="ROBOTC">
int varClock; // creates a variable
varClock = nClockMinutes; // stores the current value of the CORTEX Clock to a variable
</syntaxhighlight>
|-
|}
|-
|}
 

== nPgmTime ==
{| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
|-
| class="variableType"| const long nPgmTime
|-
| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_long|long]]) This variable contains the value of the lower 16-bits of the internal 1-msec clock. This variable is reset when user program first starts running. This clock does not increment when the program is in a debugger "suspended" state which is useful during single step debugging as the clock does not increment.
|-
|
{|
|-
|<syntaxhighlight lang="ROBOTC">
int varPgmTime; // creates a variable
varPgmTime = nPgmTime; // stores the current value of nPgmTime to a variable
</syntaxhighlight>
|-
|}
|-
|}
 

== nSysTime ==
{| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
|-
| class="variableType"| const long nSysTime
|-
| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_long|long]]) This variable contains the value of the lower 16-bits of the internal 1-msec clock. This variable is reset when CORTEX is first powered on.
|-
|
{|
|-
|<syntaxhighlight lang="ROBOTC">
int varSysTime; // creates a variable
varSysTime = nSysTime; // stores the current value of nSysTime to a variable
</syntaxhighlight>
|-
|}
|-
|}
 

== time1 ==
{| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
|-
| class="variableType"| long time1[TTimers timer]
|-
| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_long|long]]) This array holds the current value of the respective timers. Each of the timer values can be retrieved in units of 1, 10 and 100 milliseconds depending on which array is used. For example, time1[T1] retrieves the value of timer T1 in units of 1-msec and time10[T1] retrieves the value using a 10-msec tick. And time100[T1] retrieves the value using 100-msec tick. Note that the arrays are “linked”. Setting time1[T1] = 0; will also reset the value of time10[T1] and time100[T1]. The value returned is a signed integer, so each array will meet its upper bounds at a value of 32,768 ticks.
|-
|
{| class="parameterTable" cellpadding="5%" width="100%"
! width="20%" style="border-style: solid; border-width: 0px 0px 1px 0px"|Parameter
! width="60%" style="border-style: solid; border-width: 0px 0px 1px 0px"|Explanation
! width="20%" style="border-style: solid; border-width: 0px 0px 1px 0px"|Data Type
|-
| style="border-style: solid; border-width: 1px 0px 0px 0px"|''timer''
| style="border-style: solid; border-width: 1px 0px 0px 0px"|A timer to use.
| style="border-style: solid; border-width: 1px 0px 0px 0px"|[[Data_Types#dataType_TTimers|TTimers]]
|-
|}

Timers:
*T1
*T2
*T3
*T4
|-
|
{|
|-
|<syntaxhighlight lang="ROBOTC">
int valTime1, valTime10, valTime100; // create three integers to read the value of the timer

valTime1 = time1[T1]; //Gets the value of Timer T1 in 1ms increments and stores it in a variable
valTime10 = time10[T1]; //Gets the value of Timer T1 in 10ms increments and stores it in a variable
valTime100 = time100[T1]; //Gets the value of Timer T1 in 100ms increments and stores it in a variable
</syntaxhighlight>
|-
|}
|-
|}
 

== time10 ==
{| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
|-
| class="variableType"| long time10[TTimers timer]
|-
| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_long|long]]) This array holds the current value of the respective timers. Each of the timer values can be retrieved in units of 1, 10 and 100 milliseconds depending on which array is used. For example, time1[T1] retrieves the value of timer T1 in units of 1-msec and time10[T1] retrieves the value using a 10-msec tick. And time100[T1] retrieves the value using 100-msec tick. Note that the arrays are “linked”. Setting time1[T1] = 0; will also reset the value of time10[T1] and time100[T1]. The value returned is a signed integer, so each array will meet its upper bounds at a value of 32,768 ticks.
|-
|
{| class="parameterTable" cellpadding="5%" width="100%"
! width="20%" style="border-style: solid; border-width: 0px 0px 1px 0px"|Parameter
! width="60%" style="border-style: solid; border-width: 0px 0px 1px 0px"|Explanation
! width="20%" style="border-style: solid; border-width: 0px 0px 1px 0px"|Data Type
|-
| style="border-style: solid; border-width: 1px 0px 0px 0px"|''timer''
| style="border-style: solid; border-width: 1px 0px 0px 0px"|A timer to use.
| style="border-style: solid; border-width: 1px 0px 0px 0px"|[[Data_Types#dataType_TTimers|TTimers]]
|-
|}

Timers:
*T1
*T2
*T3
*T4
|-
|
{|
|-
|<syntaxhighlight lang="ROBOTC">
int valTime1, valTime10, valTime100; // create three integers to read the value of the timer

valTime1 = time1[T1]; //Gets the value of Timer T1 in 1ms increments and stores it in a variable
valTime10 = time10[T1]; //Gets the value of Timer T1 in 10ms increments and stores it in a variable
valTime100 = time100[T1]; //Gets the value of Timer T1 in 100ms increments and stores it in a variable
</syntaxhighlight>
|-
|}
|-
|}
 

== time100 ==
{| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
|-
| class="variableType"| long time100[TTimers timer]
|-
| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_long|long]]) This array holds the current value of the respective timers. Each of the timer values can be retrieved in units of 1, 10 and 100 milliseconds depending on which array is used. For example, time1[T1] retrieves the value of timer T1 in units of 1-msec and time10[T1] retrieves the value using a 10-msec tick. And time100[T1] retrieves the value using 100-msec tick. Note that the arrays are “linked”. Setting time1[T1] = 0; will also reset the value of time10[T1] and time100[T1]. The value returned is a signed integer, so each array will meet its upper bounds at a value of 32,768 ticks.
|-
|
{| class="parameterTable" cellpadding="5%" width="100%"
! width="20%" style="border-style: solid; border-width: 0px 0px 1px 0px"|Parameter
! width="60%" style="border-style: solid; border-width: 0px 0px 1px 0px"|Explanation
! width="20%" style="border-style: solid; border-width: 0px 0px 1px 0px"|Data Type
|-
| style="border-style: solid; border-width: 1px 0px 0px 0px"|''timer''
| style="border-style: solid; border-width: 1px 0px 0px 0px"|A timer to use.
| style="border-style: solid; border-width: 1px 0px 0px 0px"|[[Data_Types#dataType_TTimers|TTimers]]
|-
|}

Timers:
*T1
*T2
*T3
*T4
|-
|
{|
|-
|<syntaxhighlight lang="ROBOTC">
int valTime1, valTime10, valTime100; // create three integers to read the value of the timer

valTime1 = time1[T1]; //Gets the value of Timer T1 in 1ms increments and stores it in a variable
valTime10 = time10[T1]; //Gets the value of Timer T1 in 10ms increments and stores it in a variable
valTime100 = time100[T1]; //Gets the value of Timer T1 in 100ms increments and stores it in a variable
</syntaxhighlight>
|-
|}
|-
|}
 

== wait1Msec ==
{| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
|-
| class="functionType"| void wait1Msec(const long nMSec)
|-
| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_void|void]]) Program execution will wait for the specified number of clock units. Units are in 1-millisecond counts. The maximum interval that can be specified is 32.767 seconds. An alternative, and far less efficient, method to perform a wait is to continually execute a tight code loop looking to see if a timer has reached the desired interval. It is best to use the wait function to insert a programmed delay in a program because tasks that are waiting do not consume any CPU cycles. This makes the most number of CPU cycles available for other tasks.
|-
|
{| class="parameterTable" cellpadding="5%" width="100%"
! width="20%" style="border-style: solid; border-width: 0px 0px 1px 0px"|Parameter
! width="60%" style="border-style: solid; border-width: 0px 0px 1px 0px"|Explanation
! width="20%" style="border-style: solid; border-width: 0px 0px 1px 0px"|Data Type
|-
| style="border-style: solid; border-width: 1px 0px 0px 0px"|''nMSec''
| style="border-style: solid; border-width: 1px 0px 0px 0px"|The amount of milliseconds to wait.
| style="border-style: solid; border-width: 1px 0px 0px 0px"|[[Data_Types#dataType_long|long]]
|-
|}
|-
|
{|
|-
|<syntaxhighlight lang="ROBOTC">
wait1Msec(1000); // the program will wait for 1 second before moving on (1ms * 1000)
</syntaxhighlight>
|-
|}
|-
|}
 

== wait10Msec ==
{| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
|-
| class="functionType"| void wait10Msec(const int nTenMSec)
|-
| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_void|void]]) Program execution will wait for the specified number of clock units. Units are in 10-millisecond counts. The maximum interval that can be specified is 327.67 seconds. An alternative, and far less efficient, method to perform a wait is to continually execute a tight code loop looking to see if a timer has reached the desired interval. It is best to use the wait function to insert a programmed delay in a program because tasks that are waiting do not consume any CPU cycles. This makes the most number of CPU cycles available for other tasks.
|-
|
{| class="parameterTable" cellpadding="5%" width="100%"
! width="20%" style="border-style: solid; border-width: 0px 0px 1px 0px"|Parameter
! width="60%" style="border-style: solid; border-width: 0px 0px 1px 0px"|Explanation
! width="20%" style="border-style: solid; border-width: 0px 0px 1px 0px"|Data Type
|-
| style="border-style: solid; border-width: 1px 0px 0px 0px"|''nTenMSec''
| style="border-style: solid; border-width: 1px 0px 0px 0px"|The amount of milliseconds to wait, measured in 10-millisecond counts.
| style="border-style: solid; border-width: 1px 0px 0px 0px"|[[Data_Types#dataType_int|int]]
|-
|}
|-
|
{|
|-
|<syntaxhighlight lang="ROBOTC">
wait10Msec(1000); // the program will wait for 10 seconds before moving on (10ms * 1000)
</syntaxhighlight>
|-
|}
|-
|}

← Older revision		Revision as of 20:49, 11 May 2012
Line 1:		Line 1:
−	<yambe:breadcrumb>ARDUINO_MEGA_Functions_and_Variables\|Functions and Variables</yambe:breadcrumb>	+	{{DISPLAYTITLE:2560 (MEGA) Timing Functions}}
		+	<yambe:breadcrumb self="2560 (MEGA) Timing">ARDUINO_MEGA_Functions_and_Variables\|Functions and Variables</yambe:breadcrumb>
	<br />		<br />

ARDUINO MEGA Functions Timing - Revision history

Bfeher at 20:49, 11 May 2012

Tfriez: Created page with "ARDUINO_MEGA_Functions_and_Variables|Functions and Variables {| |- |An internal 32-bit clock is maintained by the VEX firmware. It..."

Tfriez: Created page with "ARDUINO_MEGA_Functions_and_Variables|Functions and Variables
{| |- |An internal 32-bit clock is maintained by the VEX firmware. It..."