Bfeher at 20:49, 11 May 2012

2012-05-11T20:49:01Z

Tfriez at 02:10, 10 May 2012

2012-05-10T02:10:24Z

Tfriez: Created page with "ARDUINO_MEGA_Functions_and_Variables|Functions and Variables
{| |- |Up to 19 additional tasks can execute concurrently with task m..."

2012-05-09T21:24:01Z

Created page with "<yambe:breadcrumb>ARDUINO_MEGA_Functions_and_Variables|Functions and Variables</yambe:breadcrumb> {| |- |Up to 19 additional tasks can execute concurrently with task m..."

New page

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

{|
|-
|Up to 19 additional tasks can execute concurrently with task main within a VEX Cortex user program (and up to 4 additional tasks within a VEX PIC user program). The ‘main’ or ‘primary’ task is automatically started when a user program is run. Execution of other tasks can be started and stopped with the StartTask and StopTask functions. The VEX will share CPU execution time among various tasks by giving each task a “time slice” where it will execute a group of instructions.

Each task can be assigned a priority from 0 to 255. The VEX scheduler gives execution time to the highest priority task that is waiting to run. A round robin scheduling scheme is used when there are multiple tasks ready to run all with the highest priority. Lower priority tasks will not execute until there are no tasks of higher priority that are ready to run.

A task that is waiting for a time period to expire is not ready to run. Once the time period has expired it will again become ready to run. Waiting tasks do not consume any CPU cycles.
|-
|}
 

{{tl|1|1}}
 

== abortTimeslice ==
{| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
|-
| class="functionType"| void abortTimeslice()
|-
| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_void|void]]) Immediately ends the current task time slice and allows another task to be immediately scheduled and executed. Tasks are given CPU execution time so that highest priority tasks get all the CPU time. If there are multiple tasks with the same highest priority then they are given "slices" of CPU time in a round robin fashion. This function will immediately end the current timeslice.
|-
|
{|
|-
|<syntaxhighlight lang="ROBOTC">
abortTimeslice(); // aborts the current time slice of the task
</syntaxhighlight>
|-
|}
|-
|}
 

== hogCPU ==
{| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
|-
| class="functionType"| void hogCPU()
|-
| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_void|void]]) This special function is used to temporarily suspend the normal task scheduler and give all the CPU time to the current task. As long as this task can run, then it will get all of the CPU time until a releaseCPU() function call is made. You can execute the hogCPU() command inside of task main to hog the CPU away from ROBOTC's background driver task.
|-
|
{|
|-
|<syntaxhighlight lang="ROBOTC">
hogCPU(); // suspend every other task and focus 100% on the current task
</syntaxhighlight>
|-
|}
|-
|}
 

== kDefaultTaskPriority ==
{| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
|-
| class="variableType"| const int kDefaultTaskPriority = 7
|-
| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_int|int]]) Constant. The default priority assigned to a task. Equivalent to setting a priority of 7.
|-
|
{|
|-
|<syntaxhighlight lang="ROBOTC">
int myPriority = 0; // creates a variable to hold the task priority value
myPriority = kDefaultTaskPriority; // sets 'myPriority' to 7 (default)
</syntaxhighlight>
|-
|}
|-
|}
 

== kLowPriority ==
{| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
|-
| class="variableType"| const int kLowPriority = 0
|-
| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_int|int]]) Constant. Lowest priority that can be assigned to a task. Equivalent to setting a priority of 0.
|-
|
{|
|-
|<syntaxhighlight lang="ROBOTC">
int myPriority = 0; // creates a variable to hold the task priority value
nSchedulePriority = kLowPriority; // assigns the Priority of the Task to the Lowest Priority
myPriority = nSchedulePriority; // sets the current priority to a variable to view in the debugger
</syntaxhighlight>
|-
|}
|-
|}
 

== kHighPriority ==
{| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
|-
| class="variableType"| const int kLowPriority = 255
|-
| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_int|int]]) Constant. Highest priority that can be assigned to a task. Equivalent to setting a priority of 255.
|-
|
{|
|-
|<syntaxhighlight lang="ROBOTC">
int myPriority = 0; // creates a variable to hold the task priority value
nSchedulePriority = kHighPriority; // assigns the Priority of the Task to the Highest Priority
myPriority = nSchedulePriority; // sets the current priority to a variable to view in the debugger
</syntaxhighlight>
|-
|}
|-
|}
 

== nSchedulePriority ==
{| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
|-
| class="variableType"| word nSchedulePriority
|-
| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_word|word]]) The CPU scheduler priority for the current task. ROBOTC shares CPU execution time among various tasks by giving each task a “time slice” where it will execute a group of instructions. Each task can be assigned a priority from 0 to 255. The scheduler gives execution time to the highest priority task that is waiting to run. A round robin scheduling scheme is used when there are multiple tasks ready to run all with the highest priority. Lower priority tasks will not execute until there are no tasks of higher priority that are ready to run. By default, tasks are assigned a priority value of "7".
|-
|
{|
|-
|<syntaxhighlight lang="ROBOTC">
nSchedulePriority = 100; // assigns the current task with a priority of 100
</syntaxhighlight>
|-
|}
|-
|}
 

== releaseCPU ==
{| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
|-
| class="functionType"| void releaseCPU()
|-
| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_void|void]]) This special function is used to resume the normal task schedule. It cancels the effect of a previous releaseCPU() function call.
|-
|
{|
|-
|<syntaxhighlight lang="ROBOTC">
releaseCPU(); // resume other tasks and return control to the task scheduler
</syntaxhighlight>
|-
|}
|-
|}
 

== StartTask ==
{| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
|-
| class="functionType"| void StartTask(void TaskID, const short nTaskPriority)
|-
| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_void|void]]) A functional call to start or restart the execution of a specific task. The nPriority command is optional, and can be used to assign a priority to a task at the time the task is told to start executing. If the nPriority command is not specified, the task will start with a default priority of "7".
|-
|
{| 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 1px 0px"|''TaskID''
| style="border-style: solid; border-width: 1px 0px 1px 0px"|The ID of the task to start.
| style="border-style: solid; border-width: 1px 0px 1px 0px"|[[Data_Types#dataType_void|void]]
|-
| style="border-style: solid; border-width: 0px 0px 0px 0px"|''nTaskPriority''
| style="border-style: solid; border-width: 0px 0px 0px 0px"|The priority to start the task with (optional).
| style="border-style: solid; border-width: 0px 0px 0px 0px"|[[Data_Types#dataType_short|short]]
|-
|}
|-
|
{|
|-
|<syntaxhighlight lang="ROBOTC">
StartTask(MoveArm, 10); // starts the task named "MoveArm" with a priorty of 10
</syntaxhighlight>
|-
|}
|-
|}
 

== StopAllTasks ==
{| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
|-
| class="functionType"| void StopAllTasks()
|-
| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_void|void]]) A function call to stop every task running, including the main program task.
|-
|
{|
|-
|<syntaxhighlight lang="ROBOTC">
StopAllTasks(); // stops all tasks currently running and exits the current program
</syntaxhighlight>
|-
|}
|-
|}
 

== StopTask ==
{| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
|-
| class="functionType"| void StopTask(void TaskID)
|-
| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_void|void]]) A functional call to start or restart the execution of a specific task. The nPriority command is optional, and can be used to assign a priority to a task at the time the task is told to start executing. If the nPriority command is not specified, the task will start with a default priority of "7".
|-
|
{| 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"|''TaskID''
| style="border-style: solid; border-width: 1px 0px 0px 0px"|The ID of the task to stop.
| style="border-style: solid; border-width: 1px 0px 0px 0px"|[[Data_Types#dataType_void|void]]
|-
|}
|-
|
{|
|-
|<syntaxhighlight lang="ROBOTC">
StopTask(MoveArm); // stops the task named "MoveArm"
</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) Task Control}}
		+	<yambe:breadcrumb self="2560 (MEGA) Task Control">ARDUINO_MEGA_Functions_and_Variables\|Functions and Variables</yambe:breadcrumb>
	<br />		<br />

@@ Line 4: / Line 4: @@
 {|
 |-
-|Up to 19 additional tasks can execute concurrently with task main within a VEX Cortex user program (and up to 4 additional tasks within a VEX PIC user program). The ‘main’ or ‘primary’ task is automatically started when a user program is run. Execution of other tasks can be started and stopped with the <span class="keywordBI">StartTask</span> and <span class="keywordBI">StopTask</span> functions. The VEX will share CPU execution time among various tasks by giving each task a “time slice” where it will execute a group of instructions.
+|Up to 3 additional tasks can execute concurrently with task main within an Arduino user program. The ‘main’ or ‘primary’ task is automatically started when a user program is run. Execution of other tasks can be started and stopped with the <span class="keywordBI">StartTask</span> and <span class="keywordBI">StopTask</span> functions. The Arduino will share CPU execution time among various tasks by giving each task a “time slice” where it will execute a group of instructions.
-Each task can be assigned a priority from 0 to 255. The VEX scheduler gives execution time to the highest priority task that is waiting to run. A round robin scheduling scheme is used when there are multiple tasks ready to run all with the highest priority. Lower priority tasks will not execute until there are no tasks of higher priority that are ready to run.
+Each task can be assigned a priority from 0 to 255. The Arduino scheduler gives execution time to the highest priority task that is in queue to run code. A round robin scheduling scheme is used when there are multiple tasks ready to run all with the highest priority. Lower priority tasks will not execute until there are no tasks of higher priority that are queuing.
 A task that is waiting for a time period to expire is not ready to run. Once the time period has expired it will again become ready to run. Waiting tasks do not consume any CPU cycles.

ARDUINO MEGA Functions Task Control - Revision history

Bfeher at 20:49, 11 May 2012

Tfriez at 02:10, 10 May 2012

Tfriez: Created page with "ARDUINO_MEGA_Functions_and_Variables|Functions and Variables {| |- |Up to 19 additional tasks can execute concurrently with task m..."

Tfriez: Created page with "ARDUINO_MEGA_Functions_and_Variables|Functions and Variables
{| |- |Up to 19 additional tasks can execute concurrently with task m..."