Re: Timing

On Wed, 4 Dec 2002 [email protected] wrote:

[...]
> But hand design of events/states machines is boring and error prone as soon as
> their size becomes big which happens very fast, in particular when we specify
> parallel activities of components.
>
> Thus a high level textual and/or graphical FSM specification and generation
> tool should be used, e.g. Esterel, Statecharts or so...
>
For example. One of the things I'd like to see in Orocos II is to design
and implement such support for robotics tasks. I know INRIA has done
quite some things in this respect, so concrete suggestions or summaries
from your side would be very welcome. For example: what are still the
open problems? What is "easy"? What is doable but error-prone? Etc.

Herman

-- 
  K.U.Leuven, Mechanical Engineering, Robotics Research Group
<http://people.mech.kuleuven.ac.be/~bruyninc> Tel: +32 16 322480