... | ... | @@ -38,7 +38,7 @@ All functions are available on the `scheduling` object after including `Scheduli |
|
|
### Functions related to the uninterruptible synchronous task
|
|
|
|
|
|
* `int8_t defineUninterruptibleSynchronousTask(void (*periodic_task)(), uint32_t task_period_us, scheduling_interrupt_source_t int_source)`
|
|
|
* `void startUninterruptibleSynchronousTask()`
|
|
|
* `void startUninterruptibleSynchronousTask(bool manage_data_acquisition)`
|
|
|
|
|
|
### Functions related to the asynchronous tasks
|
|
|
|
... | ... | @@ -55,7 +55,7 @@ First call `scheduling.defineUninterruptibleSynchronousTask()`, passing as first |
|
|
|
|
|
Check the return value of the function, if it is `-1`, there have been an error defining the task.
|
|
|
|
|
|
If the return value is `0`, you can later call `scheduling.startUninterruptibleSynchronousTask()` to launch the task.
|
|
|
If the return value is `0`, you can later call `scheduling.startUninterruptibleSynchronousTask()` to launch the task. By default, launching the Uninterruptible task will also start [Data Acquisition](Modules/Data acquisition). This function has a facultative parameter, that can be set to `false` in order to instruct the module that we do not want it to manage Data Acquisition.
|
|
|
|
|
|
## Asynchronous tasks
|
|
|
|
... | ... | |