Robotics middleware

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Robotics middleware is middleware to be used in complex robot control software systems.

"...robotic middleware is designed to manage the complexity and heterogeneity of the hardware and applications, promote the integration of new technologies, simplify software design, hide the complexity of low-level communication and the sensor heterogeneity of the sensors, improve software quality, reuse robotic software infrastructure across multiple research efforts, and to reduce production costs."[1]

It can be described as "software glue" to make it easier for robot builders focus on their specific problem area.[2]

Robotics middleware projects[edit]

A wide variety of projects for robotics middleware exist, but no one of these dominates - and in fact many robotic systems do not use any middleware.[3] Middleware products rely on a wide range of different standards, technologies, and approaches that make their use and interoperation difficult, and some developers may prefer to integrate their system themselves.[3]

Player Project[edit]

The Player Project (formerly the Player/Stage Project) is a project to create free software for research into robotics and sensor systems.[4] Its components include the Player network server and the Stage robot platform simulators. Although accurate statistics are hard to obtain, Player is one of the most popular open-source robot interfaces in research and post-secondary education.[5] Most of the major intelligent robotics journals and conferences regularly publish papers featuring real and simulated robot experiments using Player and Stage.

RT-middleware[edit]

RT-middleware is a common platform standards for Robots based on distributed object technology.[6] RT-middleware supports the construction of various networked robotic systems by the integration of various network-enabled robotic elements called RT-Components. The specification standard of RT-components is discussed and defined by the Object Management Group (OMG).[7]

Urbi[edit]

Urbi is an open source cross-platform software platform in C++ used to develop applications for robotics and complex systems. It is based on the UObject distributed C++ component architecture. It also includes the urbiscript orchestration language which is a parallel and event-driven script language. UObject components can be plugged into urbiscript and appear as native objects that can be scripted to specify their interactions and data exchanges. UObjects can be linked to the urbiscript interpreter, or executed as autonomous processes in "remote" mode, either in another thread, another process, a machine on the local network, or a machine on a distant network.

MIRO[edit]

Miro is a distributed object oriented framework for mobile robot control, based on CORBA (Common Object Request Broker Architecture) technology. The Miro core components have been developed under the aid of ACE (Adaptive Communications Environment), an object oriented multi-platform framework for OS-independent interprocess, network and real time communication. They use TAO (The ACE ORB) as their ORB (Object Request Broker), a CORBA implementation designed for high performance and real time applications. Currently supported platforms include Pioneers, the B21, some robot soccer robots and various robotic sensors.[8]

Orca[edit]

Orca describes its goals as:

  • to enable software reuse by defining a set of commonly-used interfaces;
  • to simplify software reuse by providing libraries with a high-level convenient API; and
  • to encourage software reuse by maintaining a repository of components.

They also state: "To be successful, we think that a framework with such objectives must be: general, flexible and extensible; sufficiently robust, high-performance and full-featured for use in commercial applications, yet sufficiently simple for experimentation in university research environments."[9]

They describe their approach as:

  • adopts a Component-Based Software Engineering approach without applying any additional architectural constraints
  • uses a commercial open-source library for communication and interface definition
  • provides tools to simplify component development but makes them strictly optional to maintain full access to the underlying communication engine and services
  • uses cross-platform development tools[9]

Orca software is released under LGPL and GPL licenses.

OpenRDK[edit]

OpenRDK is an open-source software framework for robotics for developing loosely coupled modules. It provides transparent concurrency management, inter-process (via sockets) and intra-process (via shared memory) blackboard-based communication and a linking technique that allows for input/output data ports conceptual system design. Modules for connecting to simulators and generic robot drivers are provided.

ROS[edit]

ROS, (Robot Operating System), is a collection of software frameworks for robot software development, providing operating system-like functionality on a heterogeneous computer cluster. ROS provides standard operating system services such as hardware abstraction, low-level device control, implementation of commonly used functionality, message-passing between processes, and package management.

YARP[edit]

YARP is is an open-source software package, written in C++ for interconnecting sensors, processors, and actuators in robots.

See also[edit]

  • RoSta: a European project reaching out to the robotics community to get clearer insights into robotics middleware and architectures.
  • BRICs: a European project that attempts to establish best practices in robot development

References[edit]

  1. ^ Elkady, Ayssam (29 January 2012). "Robotics Middleware: A Comprehensive Literature Survey and Attribute-Based Bibliography". Journal of Robotics. 2012. doi:10.1155/2012/959013. 
  2. ^ "What is Middleware?". Middleware.org. Defining Technology. 2008. Archived from the original on June 29, 2012. Retrieved 2013-08-11. 
  3. ^ a b "Tools, Standards, and Platforms for Commercial Robotics Development: An Adoption Profile". roboticsbusinessreview.com. Retrieved 8 May 2017. 
  4. ^ Gerkey, B., Vaughan, R., and Howard, A. (2003) The Player/Stage Project: Tools for Multi-Robot and Distributed Sensor Systems. Proceedings of the International Conference on Advanced Robotics 317-323
  5. ^ Collet, T. H. J., MacDonald, B. A., and Gerkey, B. (2005) Player 2.0: Toward a practical robot programming framework. Proceedings of the Australasian Conference on Robotics and Automation (ACRA)
  6. ^ Noriaki ANDO, Takashi SUEHIRO, Kosei KITAGAKI, Tetsuo KOTOKU, Woo-Keun Yoon, "RT-Middleware: Distributed Component Middleware for RT (Robot Technology)", 2005 IEEE/RSJ International Conference on Intelligent Robots and Systems (IROS2005), pp.3555-3560, 2005.08, Edmonton, Canada
  7. ^ Robotics Technology Component Specification version 1.0, Object Management Group (OMG)
  8. ^ "MIRO: MIDDLEWARE FOR AUTONOMOUS MOBILEROBOTS". Retrieved 8 May 2017. 
  9. ^ a b "Orca Overview". Retrieved 7 May 2017.