Denis Evstratov

Thanks a lot Mr. Samek! i got it now: the QV scheduler will invoke the AO1 when either timer event or mode activation event comes into the AO1 queue (provided that AO1 has a priority higher then other ready-for-run AOs). Then, it is up to the AO1's state machine to decide what to do, depending on the event and the current state. Best Denis

Thanks a lot Mr. Samek! i got it now: the QV scheduler will invoke the AO1 when either timer event or mode activation event comes into the AO1 queue (provided that AO1 has a priority higher then other ready-for-run AOs). Then, it is up to the AO1 state machine to decide what to do, depending on the event and the current state. Best Denis

Thanks a lot Mr. Samek! i got it now: the QV scheduler will invoke the AO1 when either timer event or mode activation event comes (provided that AO1 has a priority higher then other ready-for-run AOs). Then, it is up to the AO1 state machine to decide what to do, depending on the event and the current state. Best Denis

Thanks a lot Mr. Samek! i got it now: the QV scheduler will invoke the AO1 when either timer event or mode activation event comes. Then, it is up to the AO1 state machine to decide what to do, depending on the event and the current state. Best Denis

Thanks a lot for the prompt reply, Mr. Samek. it means that the AO1 state machine should analyse if there are both ACTIVATE event and timer's event to really execute the thread of AO1. If one is missing, then nothing should happen. Denis

Thanks a lot for the prompt reply, Mr. Samek. it means that the AO1 state machine should analyse if there are both ACTIVATE event and timer's event to really execute the thread of AO1. If one is missing, then nothing should happen. Denis

Thanks a lot for the prompt reply, Mr. Samek. So AO1 will have two events in its queue: one from the timer and another from AO2. The scheduler extracts the first event (from the timer) and invokes AO1, and then the AO1 state machine processes the second event (from AO2). This should work nicely. Somehow I had the impression that only one event could be processed during a single scheduler cycle, but in this case both events are handled sequentially from the queue. Thanks again! Denis