Search

To support robust plan execution of autonomous robots in dynamic environments, autonomous robot software should include adaptive and reactive capabilities to cope with the dynamics and uncertainties of the evolving states of real-world environments. However, conventional software architectures such as sense-model-plan-act and behaviour-based paradigms are inadequate for meeting the requirements. A lack of sensing during acting in the sense-model-plan-act paradigm makes the software slow to react to run-time contingencies, whereas the behaviour-based architectures typically fall short in planning of long-range steps and making optimized plan adaptations. This article proposes a hybrid software architecture that maintains both adaptivity and reactivity of robot behaviours in dynamic environments. To implement this architecture, we further present the multi-agent development framework known as AutoRobot, which views the robot software as a multi-agent system in which diverse agent roles collaborate to achieve software functionalities. To demonstrate the applicability and validity of our concrete framework and software architecture, we conduct an experiment to implement a typical case, for example, a robot that autonomously picks up and drops off dishes for remote guests, which requires the robot to plan and navigate in a highly dynamic environment and can adapt its behaviours to unexpected situations.

In a Robot Operating System (ROS) application, robot software is often distributed across multiple networked components, forming the ROS network, where every component acts as server and/or a client, and publishing and/or receiving robot data simultaneously. For indoor robots, a local ROS network, through a Wi-Fi hotspot, is sufficient. But for outdoor robots, a remote ROS network is needed to connect the ROS application to the cloud. Although a number of cloud-based solutions support this, implementing them is challenging, as they need to be configured to facilitate ROS's unique, multidirectional, and simultaneous flow of robot data. This article presents Port Forwarding as an alternative approach, which offers a private, secured, and a direct ROS-to-ROS, eliminating the need for a dedicated middleware and its configuration and setup complexities. But Port Forwarding has its own challenges; chiefly, the beforehand knowledge of Internet addresses of all networked components and the need to update port for...

The paper investigates the concept of software "stability" applied to robot systems. We define "stable" a family of systems modelled, designed and implemented so that specific applications of the family may be developed re-using, adapting and specializing knowledge, architecture and existing components. During the last few years, many ideas and technologies of software engineering (e.g. modularity, OO development and design patterns) were introduced in the development of robotic systems to improve the "stability" property. All these ideas and technologies are important. Nevertheless, they model robotic systems along a unique direction: the functional decomposition of parts. Unfortunately, there are concerns of robotic systems that relate to the systems as a whole hence crosscutting their modular structure. The Aspect Oriented Software Development is a recently emerged approach for modelling, designing and encapsulating the above-mentioned crosscutting concerns (aspects). We contend that stability must be based on a careful domain analysis and on a multidimensional modelling of different and recurring aspects of robot systems.

With the increasing use of general robotic platforms in different application scenarios, modularity and reusability have become key issues in effective robotics programming. In this paper, we present a minimalist approach for designing robot software, in which very simple modules, with well designed interfaces and very little redundancy can be connected through a strongly typed framework to specify and execute different robotics tasks. The evolution of robotics in terms of hardware and software design resembles the evolution of computer science in general. In the 60's, computer science was mostly focused on the hardware, and programs were developed for specific computer architectures, with little chance of reuse. In the last couple of decades, computer architectures, instruction sets and operating systems have become more stable and the focus has shifted from the hardware side to the software side. The development of efficient, modular and reusable code is now mandatory, and the use of modern software engineering is required in any system. This same process is happening now in robotics with the widening availability of stable robotic platforms.