When to create a task?

[jg_spitfire (Jairo)]

Hi,

Sorry for the delay, and thanks for reply, I will start with the easy part

@richard-damon

If the updata can be done quickly, in the interval between data aquisitions, then the collecting task can just do the update in its loop.

this is exactly how is done, each sensor updates the variable were its data is saved after every read and the task_tx_mqtt() only takes those variables to create the message to be sent to the server

Now, about the task_read_gps() and task_check_rx_mqtt():

@richard-damon

Most GPSes will send a message every time they get a data update, so if you set a task to block on getting that message, processes it, then block again, is much better than waiting a second, then seeing if you got a message, and if so, processes it. You might as well process the data right when it comes in.

@richard-damon

The same for the mqtt reception. rather than blocking for a second, and then seeing if something is there, use a blocking read

But, use a blocking read for each of those tasks is valid only if they have the same priority right?, because for example if task_check_rx_mqtt() has lower priority it must wait until task_read_gps() gets the data to run