If you go with QP, you will need at least one interrupt: the periodic system clock tick interrupt. This is no different really from any RTOS kernel, which also needs a periodic system clock tick to keep track of the time. I meant interrupts that influence the statemachine. (We will run it on the linux system, if that changes anything.) I saw that you create a thread in the linux port. It this thread necessary for the state machine to work or is it just for timer-events? We would like to have the...
We dont have any interrupts. So that wouldnt be a problem. But of course it is better to keep the option open. In case of event queuing, how would I know when the event processing is finished to collect the output? We need to send out all output of a cycle at once.
Thanks for your prompt and detailed explanation! This helped alot. The guarded transition triggered by a tick event might be feasible if we stick to the concept of an input-driven state-machine. Is the statemachine single threaded if I would use the dispatch function like in the calculator example?
Hello, we have a system with a main loop of the following form: 1. read system state as input for statemachine decisions and calculations 2. step statemachine (execute a function in the active state of all hiearchy levels to trigger transitions based on inputs and set output) 3. send output (partly actions to take, partly calculations of states that depend on statemachine state) to system Is this kind of architecture possible with QP? In the examples, you often use timeouts for this, but I dont want...
Hello, we have a system with a main loop of the following form: read system state as input for statemachine decisions and calculations step statemachine (execute a function in the active state of all hiearchy levels to trigger transitions based on inputs and set output) * send output (partly actions to take, partly calculations of states that depend on statemachine state) to system Is this kind of architecture possible with QP? In the examples, you often use timeouts for this, but I dont want to...
Hallo, we have a system with a main loop of the following form: read system state as input for statemachine decisions and calculations step statemachine (execute a function in the active state of all hiearchy levels to trigger transitions based on inputs and set output) * send output (partly actions to take, partly calculations of states that depend on statemachine state) to system Is this kind of architecture possible with QP? In the examples, you often use timeouts for this, but I dont want to...