Robotics middleware: Difference between revisions

Revision as of 02:31, 2 November 2011

Revision as of 04:33, 5 June 2012

Line 1:

{{Multiple issues|intromissing=February 2009|primarysources=February 2009|unreferenced=February 2009}}

'''Robotics middleware''' is [[middleware]] to be used in complex [[robot]] control software systems. It is the ''glue'' software that every system developer wants to use to connect software (and hardware) components together. Often, only ''communication'' between components is considered to be middleware, but this article takes a broader view, by including all ''application-independent'' codecodes that helpshelp system developers in the composition of subsystems into larger systems may also be included.

==General concepts==

==General concepts==

'''Robotics middleware''' is [[middleware]] to be used in complex [[robot]] control software systems. It is the ''glue'' software that every system developer wants to use to connect software (and hardware) components together. Often, only ''communication'' between components is considered to be middleware, but this article takes a broader view, by including all ''application-independent'' code that helps system developers in the composition of subsystems into larger systems.

As ''glue'' code, the middleware should be invisible, and introduce no overhead or extra constraints on the components. This is of course an unreachable [[non-functional requirement|(non-functional)]] design requirement, so compromises have to be made. Different middleware projects mostly differ in which compromises are made (implicitly, most often!) and in which robotics applications are being targeted.