Jump to content

Robotics middleware

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Bruyninc~enwiki (talk | contribs) at 14:00, 28 January 2009 (First summary on this complex topic ...). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

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. At a conceptual level, a complex robot controller has components that each serve one of the following four concerns:

  • Communication:
  • Computation:
  • Configuration:
  • Coordination:

Composing two or more components that each belong to one of these categories is an architectural design activity that has to balance a large amount of functional and non-functional requirements (performance, compositionality,…). The robotics research community has come up with a large number of (open source) projects that claim to provide good solutions to this component composition problem. This article presents an overview of the relevant issues to be considered in the design and use of such middleware, and also provides an annotated list of middleware projects with an evaluation of which design constraints they took (or did not take) into account, and about how well they perform.