Differences

This shows you the differences between two versions of the page.

--- wiki:news:02jan2015 [2015/05/14 15:55] – [Weaving the state machines and the library part together] pmueller
+++ wiki:news:02jan2015 [2015/05/14 15:57] – [How to treat with longer lasting tasks] pmueller
@@ Line 190: / Line 190: @@
 ===== How to treat with longer lasting tasks =====
-Execution time for handling events should be as short as possible. Longer lasting tasks should be split into chunks. Take the temperature measurement as an example. The temperature sensor TMP100 requires about 320ms conversion time according to the data sheet. The uC shouldn't wait and burn CPU cycles but either wait in low-power mode or process other events. This can easily be done by starting the conversion in one state (''Step1'') and then start a timer. If it time-outs we simply read the conversion result (''Step2'').
+Execution time for handling events should be as short as possible. Longer lasting tasks should be split into chunks. Take the temperature measurement as an example. The temperature sensor TMP100 requires about 320ms conversion time according to the data sheet. The uC shouldn't wait and burn CPU cycles but either wait in low-power mode or process other events. This can easily be done by starting the conversion in one state (''Step1'') and then start a timer and enter low-power mode. If the timer fires we pick-up the conversion result (''Step2'') and process it further.
 Another example is the wake-up procedure of the radio. After finishing low-power mode it takes a while before it is ready. Readiness is signalled via a transition of the RTS pin from high to low. After switching on the radio in state ''Step2a'' the level change crenate an irq and sends the event ''evFallingEdgeRTS''.