Re: A working document

On Thu, 27 Dec 2001, Cezary Zielinski wrote:

[...]
> > For instance, a module could run perfectly on a machine with much CPU,
> > but I could completely fail on another machine, or if the CPU gets
> > overloaded.
> > Not all the components  are interrested in such temporal properties, but
> > for the lowest (real-time) level, I think it's important. Don't you?
> >
>
> Such a feature of the system would be usefull, but quite difficult to
> implement as we are taking of measuring time with high resoluton (e.g. less
> than 1 ms). If a system is not able to execute the srvo loop in prescribed
> time (e.g. 1 ms) will it be able to measure time with that resolution? RTOS
> usually depend on timeslices. For slow CPUs thay can be 10ms or 50ms. The
> other problem is that the fact that the CPU is too slow would emerge at
> run-time.

I would not spend any effort at trying to get Orocos functionality
working for ``underpowered'' systems. It should run at at least 1kHz
on a modern CPU (Intel, AMD, PowerPC, Alpha, ...), but not on less.

Herman