Revision as of 22:06, 9 May 2017 edit Snori (talk \| contribs) Extended confirmed users, Pending changes reviewers 33,043 edits fix ← Previous edit		Revision as of 22:06, 9 May 2017 edit undo Snori (talk \| contribs) Extended confirmed users, Pending changes reviewers 33,043 edits tidier Next edit →
Line 2: :"''...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\|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> ~~to make it easier for robot builders focus on their specific problem area.~~ ==Robotics middleware projects==

Robotics middleware: Difference between revisions