As such, the software support provided for defining missions is becoming a more important feature in the selection of a robot by end-users. Robots are also evolving from single-purpose machines to general, multi-purpose, and configurable devices. Nowadays, the task of defining missions is moving from the robotic manufacturer to the end-users, who are far from being experts in robotics. For instance, logical languages, such as LTL, CTL, or other intricate, logic-based formalisms to specify missions, are complex for users with low expertise in formal and logical languages.
![robotc commands list cortex 2.0 robotc commands list cortex 2.0](https://image3.slideserve.com/6274660/robotc-features-l.jpg)
As such, a mission coordinates the so-called skills of robots, which represent lower-level behaviors.ĭeveloping missions requires substantial expertise. Specifically, a mission is a description of the high-level behavior a robot must perform. Specifying the behavior of a robot, typically called the robot’s mission, is far from trivial. Įngineering robotics control software is challenging. Personal service robots are expected to exceed 22.1 million units in 2019 and 61.1 million units in 2022, while the sales for agricultural robots are projected to grow by 50% each year.ĭifferent techniques have been proposed for engineering the various aspects of robotic behavior, such as interoperability at the human-robot (or human-swarm) level and at the software-component level in middlewares, or multi-robot target detection and tracking. According to a 2019 press release Footnote 1 at the International Federation of Robotics, the sales of robots for professional use, such as autonomous guided vehicles, inspection, and maintenance robots increased by 32%. Autonomous service robots replace humans in repetitive, laborious, or dangerous activities, often by interacting with humans or other robots. Over the last decades, robots became increasingly present in our everyday life. We believe that our results are valuable to practitioners and researchers designing the next generation of mission specification languages in the vibrant domain of mobile robots. We explore the design space of these languages and their environments, identify their concepts, and organize them as features in a feature model. We present a survey of 30 mission specification environments for mobile robots that come with a visual and end-user-oriented language. In this paper, we contribute in this direction. To this end, we need to improve our empirical understanding of the current state-of-the-art of such languages and their environments. Improving these environments and languages for specifying missions toward simplicity and flexibility is crucial. As such, the software support for defining missions is becoming an increasingly relevant criterion when buying or choosing robots. Since end-users usually lack such skills, many commercial robots are nowadays equipped with environments and domain-specific languages tailored for end-users. However, with the current state-of-the-art, defining missions is non-trivial and typically requires dedicated programming skills.
![robotc commands list cortex 2.0 robotc commands list cortex 2.0](https://i.ytimg.com/vi/aH2bp21FKtc/maxresdefault.jpg)
As such, the task of defining the robot’s mission is moving from professional developers and roboticists to the end-users. Fulfilling complex missions in different contexts and environments, robots are promising instruments to support our everyday live. Mobile robots are becoming increasingly important in society.