For more information about this bug, visit
A new bug was added:
Summary: Orocos components do not have an 'Error' state
Product: RTT
Version: 1.2.0
Platform: All
URL: http://www.orocos.org/stable/documentation/rtt/v1.2.x/do
c-xml/orocos-components-manual.html#fig-component-states
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Real-Time Toolkit (RTT)
AssignedTo: orocos-dev [..] ...
ReportedBy: peter [dot] soetens [..] ...

The Orocos component state diagram does not list an 'Error' state. Error states
are reached when the component fails to proceed in the current state without
external intervention. For example, the component is supposed to run at a
frequency of 1000Hz but can not meet that QoS. Or a component is supposed to
access a hardware device, but the Operating system reports an error. In that
case, it must be possible for the component to enter an Error state such that
an external supervisor can detect this error condition and take action.

In the error state, the component does not react to events nor does it execute
its calculations. A special method in the interface must allow an external
suppervisor to 'reset' the component to the 'Stopped'/'Configured' or
'PreOperational' state in case of complete failure of recovery.

I know that current TaskContext/TaskCore users silently ignore run-time error
conditions today, but any input upon the reasoning above is welcome.

--
(this mail is best viewed with a fixed font)
Configure bugmail: https://www.fmtc.be/orocos-bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--
Orocos-Dev mailing list
Orocos-Dev [..] ...
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm