Robotics middleware: Difference between revisions

Content deleted Content added
Nsv7 (talk | contribs)
Citation bot (talk | contribs)
m Alter: url, template type. Add: issue, volume, journal, date, pages, author pars. 1-6. Removed URL that duplicated unique identifier. Formatted dashes. | You can use this bot yourself. Report bugs here.| Activated by User:Headbomb
Line 1:
{{external links|date=May 2018}}
'''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.''"<ref>{{cite journal|last1=Elkady|first1=Ayssam|title=Robotics Middleware: A Comprehensive Literature Survey and Attribute-Based Bibliography|journal=Journal of Robotics|date=29 January 2012|volume=2012|pages=1–15|doi=10.1155/2012/959013|url=https://www.hindawi.com/journals/jr/2012/959013/|ref=959013}}</ref>
 
It can be described as "software glue" to make it easier for robot builders focus on their specific problem area.<ref name="MW-00">{{Cite web|title=What is Middleware? |url=http://www.middleware.org/whatis.html |publisher=Defining Technology |work=Middleware.org |year=2008 |accessdate=2013-08-11 |deadurl=unfit |archiveurl=https://web.archive.org/web/20120629211518/http://www.middleware.org/whatis.html |archivedate=June 29, 2012 }}</ref>
 
==Robotics middleware projects==
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.<ref name=tools>{{cite web|title=Tools, Standards, and Platforms for Commercial Robotics Development: An Adoption Profile|url=https://www.roboticsbusinessreview.com/uncategorized/tools-standards-and-platforms-for-commercial-robotics-development/|website=roboticsbusinessreview.com|accessdate=8 May 2017|date=October 2009}}</ref> 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.<ref name=tools/>
 
===Player Project===
Line 21:
[https://www.openhub.net/p/miro-middleware/ 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 [[Autonomous research robot|Pioneers]], the B21, some robot soccer robots and various robotic sensors.<ref>{{cite webjournal|title=MIRO: MIDDLEWARE FOR AUTONOMOUS MOBILEROBOTS|journal=Ifac Proceedings Volumes|volume=34|issue=9|pages=297–302|url=https://www.academia.edu/31375091/Miro_Middleware_for_autonomous_mobile_robots|accessdate=8 May 2017|last1=Palm|first1=Günther|last2=Kraetzschmar|first2=Gerhard|last3=Simon|first3=Steffen|last4=Sablatnög|first4=Stefan|last5=Utz|first5=Hans|last6=Enderle|first6=Stefan}}</ref>
 
===Orca===