TRICONEX 3625 Digital Output Control Module

TRICONEX 3625

TRICONEX 3625

TRICONEX 3625

TRICONEX 3625 Create a task and start the task scheduler

Let's take a look at the basic structure of the TRICONEX 3625 project.

1. First, include the Arduino FreeRTOS Header file as

#Include% 3 carduino_ Free tos H% 3E

2. Give the Function prototype of all functions you wrote for execution, and write them as

Void task 1 (void * PV parameters); Void task 2 (void * PV parameters)

3. Now, in the invalid setting () function, create a task and start the task scheduler.

In order to create a task, the xTaskCreate() API is called to set a function with specific parameters/arguments.

XTaskCreate (task function_t pvTaskCode, const char * const pcName, uint16_t usStackDepth, void * pvParameters, UBaseType_t uxPriority, task handle_t * pxCreatedTask);

When creating any task, 6 parameters should be passed. Let's take a look at what these arguments are

TRICONEX 3625: It is just a pointer to the function that implements the task (in fact, it is just the name of the function).

Computer Name: A descriptive name for the task. FreeRTOS does not use this. Including it is purely for debugging purposes.

UsStackDepth: Each task has its own unique stack, which is assigned by the kernel when the task is created. This value specifies the number of words that the stack can hold, rather than the number of bytes. For example, if the stack is 32 bits wide and usStackDepth is passed in as 100, 400 bytes of stack space (100 * 4 bytes) will be allocated in RAM. Use it wisely because Arduino Uno only has 2k bytes of memory.

PV parameter: Task input parameter (can be blank).

UX Priority: The priority of the task (0 is the lowest priority).

PxCreated Task: It can be used to pass a handle to the task being created. Then, this handle can be used to reference tasks in API calls, such as changing task priority or deleting tasks (which can be empty).