DOCSLIB.ORG

The Urbi Universal Platform for Robotics

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The Urbi Universal Platform for Robotics The Urbi Universal Platform for Robotics Jean-Christophe Baillie, Akim Demaille, Quentin Hocquet, Matthieu Nottale, Samuel Tardieu Gostai, R&D Lab, 32 Bd Victor, FR-75015 Paris, France http://www.gostai.com lastname @gostai.com Abstract. Robots can free humankind from everyday chores, they can entertain us, and even educate our children. They can carry loads, walk, dance, sing, and express emotions. Hundreds of different robots are al- ready sold in shops, and complex applications are being developed ac- tively around the globe. So why are robots so not present today? In our experience the lack of standard in robotics, be it from the hard- ware or software point of view, makes the development of advanced ap- plications for robotics unproductive. This is very similar to the early days of personal computers, until the emerging of sufficiently widespread Operating Systems increased the return-on-investment for software de- velopment. The Urbi platform sits on top of the large variety of software and/or hardware components for robotics, and provides the user with a unified, standardized, interface with which complex and portable applications can be developed. In this paper, with present the Urbi platform and some of its prominent components. Introduction Urbi is a software platform used to develop portable applications for robotics and artificial intelligence [1, 2]. It is based on a parallel and event-driven script language, and on a distributed component architecture. The lack of standards in robotics makes the Urbi platform particularly sen- sitive to differences of Application Program Interfaces (APIs) between robots, components and so forth. In this paper, we present the Urbi platform and how it achieves its goals. Outline Sect. 1 describes the whole platform, focusing on the problems to solve, and the selected, layered, solutions. On top of it portable applications can be built; Sect. 2 presents some of the applications developed at Gostai. A key com- ponent of the platform is the UrbiScript language1, introduced in Sect. 3. Sect. 4 presents ongoing and future work, and Sect. 5 concludes. 1 A Universal Platform The Urbi platform, including the UrbiScript programming language, was de- signed to be simple and powerful. It targets a wide spectrum of users, starting 1 UrbiScript was formerly known as the Urbi programming language. Workshop Proceedings of SIMPAR 2008 Intl. Conf. on SIMULATION, MODELING and PROGRAMMING for AUTONOMOUS ROBOTS Venice(Italy) 2008 November,3-4 ISBN 978-88-95872-01-8 pp. 580-591 2 Java C++ Matlab UObject Applications client code through liburbi C++/Java (Ex. : urbiLab, remote surveillance...) Urbi Kernel UObject C++ UObject C++ UObject C++ (Ex. : motor) (Ex. : camera) (...) Urbi Engine Operating System Hardware The Urbi server is on top of the Operating System (OS) to abstract from (computer) hardware idiosyncrasies, yet it may be deployed bare-board. The Urbi server (the central rounded-box) is composite: (i) the Urbi engine and the kernel (Sect. 1.1) abstract the Central Processing Unit (CPU) and OS, and (ii) robotics or algorithmic components are unified using the UObject API (Sect. 1.2). Differences in conventions (clockwise? anticlockwise?), units etc. are addressed in Sect. 1.3. The intrinsically concurrent and event based nature of robotic software is fully integrated in the Urbi platform, including in the UrbiScript programming language (Sect. 1.4). Fig. 1. The Urbi platform components from children willing to customize their robots, up to researchers who want to focus on complex scientific problems in robotics rather that on idiosyncrasies of some robot's specific API. As such, the Urbi platform has already reached its goal: its youngest known users are about twelve years old, using UrbiScript a hobbyist won a Sony \best Aibo dance" prize, and dozens of universities throughout the world develop advanced research in robotics using it. Several challenges stand in the way of ease-of-use, starting with the need to cope with a wide range of architectures. The platform was structured to cope with the lack of proper standards for robotics, and to be simple yet powerful. A bird-eye view of its architecture in presented in Fig. 1, and the following sections detail the various components. 1.1 Computer Components To gain CPU independence, UrbiScript runs on top of the Urbi Virtual Machine (UVM), which is part of Urbi server: to port UrbiScript to a new architecture, the UVM only needs to be adapted. The UVM is tailored to work with local Workshop Proceedings of SIMPAR 2008 Intl. Conf. on SIMULATION, MODELING and PROGRAMMING for AUTONOMOUS ROBOTS Venice(Italy) 2008 November,3-4 ISBN 978-88-95872-01-8 pp. 580-591 3 components, or device drivers, developed in low-level languages. UrbiScript is a scripting language: it was designed to develop high-level algorithms and be- haviors from smaller components. For instance, computer-vision primitives are expected to be tailored for a specific robot and written for instance in C++, while UrbiScript is suitable to implement reactive behavior based on vision. The Urbi platform relies on engines to interact with the underlying operating- system. Primitive services such as the UVM are provided by the Urbi kernel, which is a generic library. It is the engine that makes it a complete and runnable Urbi server. The engine launches the main loop and provides a few system- dependent core information to the server, such as time. Thanks to this modeling, the Urbi server can be ported very simply to a wide range of environments (embedded systems, robots, simulators, . ). 1.2 Robotics Components The diversity of hardware components in robots is another source of complexity. In the Urbi platform, it is addressed by the UObject architecture. It installs a standard API on top of low-level device drivers (sensors, actuators, motors and so forth) and of software components (computer vision, voice recognition etc.). Thanks to this API and its associated middle-ware architecture, low-level and/or high-level components can communicate simply, and interact with UrbiScript programs. Existing C/C++ libraries are easily made usable from UrbiScript, and specific code can be written to take advantage of Urbi features such as event-driven programming, timers and variable change notifications. The UOb- ject API can also be used to handle complex data flow between multiple software components thanks to callback functions that are notified when any variable is accessed (read and/or write). The UObject API maximizes code reuse: if a robot is built from off-the-shelf components, so is the Urbi server. UObjects can either be plugged into the server, ensuring maximum reactiv- ity, or be standalone remote processes. Remote UObjects can be local, running on the very robot, or on some slave computer. In the former case the server is protected from faults in the components, and in the latter case, CPU intensive computations can be handled by auxiliary machines. Therefore, before deploy- ing it on a robot, the Urbi server is dimensioned, depending on the available resources. Thanks to these abstractions the server does not know whether it is running on an actual robot, or a simulation thereof. UrbiScript programs run seamlessly on robots and simulators such as Webots [6, 12]. Developing robotic applications without simulators is virtually impossible. They considerably speed-up the de- velopment process: they are cheap and reproducible as opposed to robots that can be very expensive apiece, test suites are easier to write and to automate, etc. They don't even require the robot itself to exist: they provide a means to examine the behavior of a robot during its design. Low-level consistency, while necessary, is not sufficient to maximize the porta- bility of high-level applications. Workshop Proceedings of SIMPAR 2008 Intl. Conf. on SIMULATION, MODELING and PROGRAMMING for AUTONOMOUS ROBOTS Venice(Italy) 2008 November,3-4 ISBN 978-88-95872-01-8 pp. 580-591 4 1.3 High-level Universality One can expect a dramatic increase of the market of hardware and/or software components for robots: motors, sensors, text to speech, voice recognition, nav- igation, face recognition. to name a few. To cope with this variety, the Urbi Naming Standard defines common interfaces (or facets) and naming scheme that must share the UObjects for equivalent components. Thanks to this abstraction, the customer is free to select a particular component seller depending on his own criteria. Subtle differences between components can ruin a multi-million-dollar project [13]. To avoid this, unit support is developed in UrbiScript. The Urbi Naming Standard also defines the orientation axis and so forth, to standardize measure- ments and actions. This document also defines the names and interfaces of limbs and organs for usual robot anatomies: legs, fingers, heads, joints, sensitive skin, accelerometers, gyroscopes etc. These abstraction and standardization layers allow the development of portable applications (on sufficiently similar robots). Games or utilitarian applications are being developed at Gostai: UrbiLab (Sect. 2.2) to create elaborate remote control for any robot, remote surveillance, educative application etc. 1.4 Concurrent and Event Driven Traditional programming languages follow a sequential execution model. Code is executed one statement after the other, ultimately leading to the expected result. Even when threads are used, the code running in each thread follows a strict iterative scheme, and their interaction may be difficult to describe [7]. Robots are designed to evolve in the real world: while they are moving around, they need to be aware of their environment and its possible brutal changes. Un- predictable events such as an animal crossing the robot path need to be asyn- chronously and timely acted upon. While traditional programming languages typically offer limited asynchronous capabilities through signals and callbacks, the Urbi platform integrates them at the heart of the execution model, and the UrbiScript language provides the user with short and intuitive constructs, which we will describe in Sect.
Load more

Recommended publications
  • Survey of Robot Programming Languages
    Survey of Robot Programming Languages Seminar Report Submitted in partial fulfilment of the requirements for the degree of Master of Technology by Anirban Basumallik Roll No : 09305008 under the guidance of Prof. Kavi Arya Department of Computer Science and Engineering Indian Institute of Technology, Bombay April 2010 Abstract At the present moment the field of Robotics is extremely varied. The nature of tasks that robots can perform are very distributed and hence controlling or programming different robots need different methods. Many vendors have tried to provide a common platform by abstracting out the differences. In this report we carry out a survey of the different Robot Programming Languages available in the market and assess their pros and cons. Finally, we come up with the needs of a desirable robotics platform that can ease the task of programmers in programming a class of robots more succinctly and effectively. 1 CONTENTS CONTENTS Contents 1 Introduction 3 1.1 Robot Programming Platform . 3 1.2 Need for a Platform . 3 2 Microsoft Robotics Developer Studio 3 2.1 DSS . 4 2.2 CCR . 5 2.3 VPL . 6 2.4 VSE . 7 2.5 Others . 8 2.6 Pros, Cons and buzz . 8 3 Player/Stage 9 3.1 Player Goals and Design . 9 3.2 Stage simulation environment . 10 3.3 Working . 11 3.4 Pros, Cons and buzz . 12 4 URBI 12 4.1 Design philosophy . 12 4.2 URBI Technology . 13 4.3 Pros, Cons and buzz . 14 5 OROCOS 15 5.1 Design philosophy . 15 5.2 Pros, Cons and buzz .
    [Show full text]
  • GNU/Linux AI & Alife HOWTO
    GNU/Linux AI & Alife HOWTO GNU/Linux AI & Alife HOWTO Table of Contents GNU/Linux AI & Alife HOWTO......................................................................................................................1 by John Eikenberry..................................................................................................................................1 1. Introduction..........................................................................................................................................1 2. Symbolic Systems (GOFAI)................................................................................................................1 3. Connectionism.....................................................................................................................................1 4. Evolutionary Computing......................................................................................................................1 5. Alife & Complex Systems...................................................................................................................1 6. Agents & Robotics...............................................................................................................................1 7. Statistical & Machine Learning...........................................................................................................2 8. Missing & Dead...................................................................................................................................2 1. Introduction.........................................................................................................................................2
    [Show full text]
  • Concurrency Patterns for Easier Robotic Coordination
    Concurrency Patterns for Easier Robotic Coordination Andrey Rusakov∗ Jiwon Shin∗ Bertrand Meyer∗† ∗Chair of Software Engineering, Department of Computer Science, ETH Zurich,¨ Switzerland †Software Engineering Lab, Innopolis University, Kazan, Russia fandrey.rusakov, jiwon.shin, [email protected] Abstract— Software design patterns are reusable solutions to Guarded suspension – are chosen for their concurrent nature, commonly occurring problems in software development. Grow- applicability to robotic coordination, and evidence of use ing complexity of robotics software increases the importance of in existing robotics frameworks. The paper aims to help applying proper software engineering principles and methods such as design patterns to robotics. Concurrency design patterns programmers who are not yet experts in concurrency to are particularly interesting to robotics because robots often have identify and then to apply one of the common concurrency- many components that can operate in parallel. However, there based solutions for their applications on robotic coordination. has not yet been any established set of reusable concurrency The rest of the paper is organized as follows: After design patterns for robotics. For this purpose, we choose six presenting related work in Section II, it proceeds with a known concurrency patterns – Future, Periodic timer, Invoke later, Active object, Cooperative cancellation, and Guarded sus- general description of concurrency approach for robotics pension. We demonstrate how these patterns could be used for in Section III. Then the paper presents and describes in solving common robotic coordination tasks. We also discuss detail a number of concurrency patterns related to robotic advantages and disadvantages of the patterns and how existing coordination in Section IV.
    [Show full text]
  • Architecture of a Software System for Robotics Control
    Architecture of a software system for robotics control Aleksey V. Shevchenko Oksana S. Mezentseva Information Systems Technologies Dept. Information Systems Technologies Dept. Stavropol City, NCFU Stavropol City, NCFU [email protected] [email protected] Dmitriy V. Mezentsev Konstantin Y. Ganshin Information Systems Technologies Dept. Information Systems Technologies Dept. Stavropol City, NCFU Stavropol City, NCFU [email protected] [email protected] Abstract This paper describes the architecture and features of RoboStudio, a software system for robotics control that allows complete and simulta- neous monitoring of all electronic components of a robotic system. This increases the safety of operating expensive equipment and allows for flexible configuration of different robotics components without changes to the source code. 1 Introduction Today, there are no clear standards for robotics programming. Each manufacturer creates their own software and hardware architecture based on their own ideas for optimizing the development process. Large manufacturers often buy their software systems from third parties, while small ones create theirs independently. As a result, the software often targets a specific platform (more often, a specific modification of a given platform). Thus, even minor upgrades of an existing robotic system often require a complete software rewrite. The lack of universal software products imposes large time and resource costs on developers, and often leads to the curtailment of promising projects. Some developers of robotic systems software partially solve the problem of universal software using the free Robotics Operation System (ROS), which also has limitations and is not always able to satisfy all the requirements of the manufacturers. 2 Equipment The research was conducted using two robots produced by the SPA "Android Technics" the "Mechatronics" stand and the full-size anthropomorphic robot AR-601E (figure 1).
    [Show full text]
  • Improvements in the Native Development Environment for Sony AIBO
    Special Issue on Improvements in Information Systems and Technologies Improvements in the native development environment for Sony AIBO Csaba Kertész Tampere University of Applied Sciences (TAMK), Research Department, Tampere, Finland Vincit Oy, Tampere, Finland installing a new bootloader. With these changes, i-Cybie can Abstract — The entertainment robotics have been on a peak be programmed in C under Windows and the sensors are with AIBO, but this robot brand has been discontinued by the accessible, but the SDK was abandoned in pre-alpha state with Sony in 2006 to help its financial position. Among other reasons, frequent freezes and almost no documentation. the robot failed to enter into both the mainstream and the robotics research labs besides the RoboCup competitions, A South Korean company (Dongbu Robot) sells a robot dog however, there were some attempts to use the robot for [3], which has a similar hardware configuration to AIBO, but rehabilitation and emotional medical treatments. A native Genibo does not have an open, low level software software development environment (Open-R SDK) was provided development environment, making impractical for researches. to program AIBO, nevertheless, the operating system (Aperios) Currently, there is no such an advanced and highly induced difficulties for the students and the researchers in the sophisticated quadruped system on the market like AIBO. If software development. The author of this paper made efforts to update the Open-R and overcome the problems. More the shortcomings of the software environment can be fixed, the enhancements have been implemented in the core components, robot can be used for upcoming research topics.
    [Show full text]
  • Programming Robots for Activities of Everyday Life
    Thesis for The Degree of Licentiate of Engineering Programming Robots for Activities of Everyday Life Swaib Dragule Division of Software Engineering Department of Computer Science & Engineering Chalmers University of Technology and Gothenburg University Gothenburg, Sweden, 2021 Programming Robots for Activities of Everyday Life Swaib Dragule Copyright ©2021 Swaib Dragule except where otherwise stated. All rights reserved. Department of Computer Science & Engineering Division of Software Engineering Chalmers University of Technology and Gothenburg University Gothenburg, Sweden This thesis has been prepared using LATEX. Printed by Chalmers Reproservice, Gothenburg, Sweden 2021. ii ”Smiling to someone is an act of charity.” - Prophet Muhammad (P.B.U.H) iv v Abstract Text-based programming remains a challenge to novice programmers in all programming domains, including robotics. The use of robots is gaining considerable traction in several domains since robots are capable of assisting humans in repetitive and hazardous tasks. Soon robots will commonly be used in tasks-of-everyday-life in homes, hotels, airports, and museums. However, robotic missions have been either predefined or programmed using low-level APIs, making mission specification task-specific and error-prone. To harness the full potential of robots, it must be possible to define missions for specific application domains as needed. The specification of missions of robotic applications should be performed via easy-to-use, accessible ways, and at the same time, be accurate and unambiguous. Simplicity and flexibility in programming such robots are important since end-users come from diverse domains, not necessarily with sufficient programming knowledge. The main objective of this licentiate thesis is to empirically understand the state-of-the-art in languages and tools used for specifying robot missions by end-users.
    [Show full text]
  • Tag: Job Control in Urbiscript
    Tag: Job Control in urbiscript Jean-Christophe Baillie Akim Demaille Quentin Hocquet Matthieu Nottale May 7, 2010 Abstract The Urbi software platform for the development of applications for robots relies heavily on concur- rency. While concurrent programs have existed for decades, there is still no universal consensus for the proper means to control the complexity of parallelism. This paper presents some innovating features of Urbi: syntactic constructs to support concurrent jobs, and tags, used to control them. Urbi SDK is a software platform used to develop portable applications for robotics and artificial intel- ligence (Baillie, 2005). It is based on UObjects, a distributed component architecture, and on urbiscript, a parallel and event-driven scripting language. It’s current architecture has already described elsewhere (Baillie et al., 2008), this paper focuses on one specific feature of urbiscript: job control. Today, any computer runs many programs concurrently. The Operating System is in charge of provid- ing each process with the illusion of a fresh machine for it only, and of scheduling all these concurrent processes. In robots, jobs not only run concurrently, they collaborate. Each process is a piece of a complex behavior that emerges from the coordination/orchestration of these jobs. The Urbi platform aims to provide the developers with a convenient framework to orchestrate concur- rent, collaborating, tasks. Outline Section 1 introduces some of the features of urbiscript for parallel programming; it concludes on the common need for a high-level job control. Section 2 presents tags, the cornerstone of job control in Urbi. A real world example is presented in Section 3: safe interruption of the Nao walk.
    [Show full text]
  • Programming Robots with Events Truong Giang Le, Dmitriy Fedosov, Olivier Hermant, Matthieu Manceny, Renaud Pawlak, Renaud Rioboo
    Programming Robots With Events Truong Giang Le, Dmitriy Fedosov, Olivier Hermant, Matthieu Manceny, Renaud Pawlak, Renaud Rioboo To cite this version: Truong Giang Le, Dmitriy Fedosov, Olivier Hermant, Matthieu Manceny, Renaud Pawlak, et al.. Programming Robots With Events. 4th International Embedded Systems Symposium (IESS), Jun 2013, Paderborn, Germany. pp.14-25, 10.1007/978-3-642-38853-8_2. hal-00924489 HAL Id: hal-00924489 https://hal.inria.fr/hal-00924489 Submitted on 7 Jan 2014 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Distributed under a Creative Commons Attribution| 4.0 International License Programming Robots with Events Truong-Giang Le1, Dmitriy Fedosov2, Olivier Hermant3, Matthieu Manceny1, Renaud Pawlak4, and Renaud Rioboo5 1 LISITE - ISEP, 28 rue Notre-Dame des Champs, 75006 Paris, France 2 Saint-Petersbourg University of Aerospace Instrumentation, 67 Bolshaya Morskaya street, 190000, Saint Petersburg, Russia 3 CRI - MINES ParisTech, 35 rue ST-Honor´e, 77300 Fontainebleau, France 4 IDCapture, 2 rue Duphot, 75001 Paris, France 5 ENSIIE, 1 square de la R´esistance, F-91025 Evry´ CEDEX, France {le-truong.giang,matthieu.manceny}@isep.fr, {dvfdsv,renaud.pawlak}@gmail.com, [email protected], [email protected] Abstract.
    [Show full text]
  • Robotstadium: Online Humanoid Robot Soccer Simulation Competition
    RobotStadium: Online Humanoid Robot Soccer Simulation Competition Olivier Michel1,YvanBourquin1, and Jean-Christophe Baillie2 1 Cyberbotics Ltd., PSE C - EPFL, 1015 Lausanne, Switzerland [email protected], [email protected] http://www.cyberbotics.com 2 Gostai SAS, 15 rue Vergniaud 75013 Paris, France [email protected] http://www.gostai.com Abstract. This paper describes robotstadium: an online simulation con- test based on the new RoboCup Nao Standard League. The simulation features two teams with four Nao robots each team, a ball and a soccer field corresponding the specifications of the real setup used for the new RoboCup Standard League using the Nao robot. Participation to the contest is free of charge and open to anyone. Competitors can simply register on the web site and download a free software package to start programming their team of soccer-playing Nao robots. This package is based on the Webots simulation software, the URBI middleware and the Java programming language. Once they have programmed their team of robots, competitors can upload their program on the web site and see how their team behaves in the competition. Matches are run every day and the ranking is updated accordingly in the ”hall of fame”. New simulation movies are made available on a daily basis so that anyone can watch them and enjoy the competition on the web. The contest is running online for a given period of time after which the best ranked competitors will be selected for a on-site final during the next RoboCup event. This contest is sponsored by The RoboCup federation, Aldebaran Robotics, Cyberbotics and Gostai.
    [Show full text]
  • Software Architecture for an Exploration Robot Based on Urbi
    Software architecture for an exploration robot based on Urbi Jean-Christophe Baillie, Akim Demaille, Guillaume Duceux, David Filliat, Quentin Hocquet, Matthieu Nottale To cite this version: Jean-Christophe Baillie, Akim Demaille, Guillaume Duceux, David Filliat, Quentin Hocquet, et al.. Software architecture for an exploration robot based on Urbi. 6th National Conference on Control Architectures of Robots, INRIA Grenoble Rhône-Alpes, May 2011, Grenoble, France. 12 p. inria- 00599674 HAL Id: inria-00599674 https://hal.inria.fr/inria-00599674 Submitted on 10 Jun 2011 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Software architecture for an exploration robot based on Urbi Jean-Christophe Baillie1 Akim Demaille1 Guillaume Duceux1,2 David Filliat2 Quentin Hocquet1 Matthieu Nottale1 1Gostai S.A.S., 15 rue Jean-Baptiste Berlier, 75013 Paris. 2ENSTA ParisTech, Unit´e Electronique´ et Informatique, 32 boulevard Victor,75739 Paris Cedex 15. May 10, 2011 Abstract We present the software architecture of a mobile robot whose goal is to autonomously explore an unknown indoor environment and to build a semantic map containing high-level information. This robot was developed under the Panoramic and Active Camera for Ob- ject Mapping (PACOM) project whose goal is to participate in the French exploration and mapping contest CAROTTE.
    [Show full text]
  • Nao®, the Ideal Partner for Research and Education
    ACADEMICS EDITION NAO®, THE IDEAL PARTNER FOR RESEARCH Fully programmable AND EDUCATION IN THE FIELD OF ROBOTICS Multiple sensors Onboard computer Remote control Friendly design and lightweight Nao Academics Edition key features - 25 Degrees of Freedom - Two prehensile hands - x86 AMD Geode 500 Mhz CPU - 256 MB SDRAM / 2 GB Flash memory - Wi-Fi 802.11b and ethernet port - 2x 30 FPS CMOS videocam res. 640x480 - Vision processing capacities - Two loudspeakers and English vocal synthesis - Supports multiple programming environments Comes with software and complete documentation After 3 years of research, Aldebaran RoboticsTM has developed Nao® a 58 cm (23’’) tall biped robot. It’s a unique combination of hardware and software in a great design. Nao stands tall in all points amongst its robotic brethren. The hardware has been built from the ground up with the latest technologies providing great fluidity in its movements and offering a wide range of sensors. Platform agnostic, it can be programmed and controlled using Linux, Windows or Mac OS and comes with complete software and documentation. All-in-one MOVEMENT humanoid Nao comes with 25 degrees of freedom for great mobility. The inertial sensor provides great stability while moving and enables positioning within space. Sonars and FSRs allow Nao to detect its environment and to navigate seamlessly. robot His state-of-the-art onboard actuators give Nao extreme precision in its movements. INTERACTION Nao features embedded software modules allowing text to speech, sound localization, visual pattern and coloured shape detection, obstacle detection (based on the two channel sonar system) and visual effects or communication through the many LEDs.
    [Show full text]
  • Simple Concurrency for Robotics with the Roboscoop Framework
    Simple Concurrency for Robotics with the Roboscoop Framework Andrey Rusakov Jiwon Shin Bertrand Meyer Chair of Software Engineering Department of Computer Science ETH Zurich,¨ Switzerland fandrey.rusakov, jiwon.shin, [email protected] Abstract— Concurrency is inherent to robots, and using enables even novice programmers to program concurrent concurrency in robotics can greatly enhance performance of the robotic software. Current Roboscoop contains behaviors and robotics applications. So far, however, the use of concurrency in tools necessary for the operation of differential drive robots robotics has been limited and cumbersome. This paper presents Roboscoop, a new robotics framework based on Simple Concur- and has been tested on two different robots. rent Object Oriented Programming (SCOOP). SCOOP excludes This paper is organized as follows: After presenting related data races by construction, thereby eliminating a major class of work in Section II, the paper presents the core of Roboscoop concurrent programming errors. Roboscoop utilizes SCOOP’s framework in Section III. Section IV presents an example of concurrency and synchronization mechanisms for coordination using Roboscoop for the task of exploring an unknown area. in robotics applications. We demonstrate Roboscoop’s simplicity by comparing Roboscoop to existing middlewares and evaluate Section V compares Roboscoop against other middlewares Roboscoop’s usability by employing it in education. and also presents an evaluation of Roboscoop in education. The paper concludes with final remarks in Section VI. I. INTRODUCTION Advanced robotic systems are composed of many com- II. RELATED WORK ponents that can operate concurrently. Running these com- In the last decade, many middlewares have been pro- ponents concurrently would enable robots to meet their full posed to ease the development of robotic coordination and potential.
    [Show full text]