An HTML5 User Interface for the ASys Robot Control Testbed

Ricardo Sanz

UPM Autonomous Systems Laboratory and Center for Automation and Robotics.

A proposal for a nal grade research project

The Robot Control Testbed (RCT) is a research platform that is part of the the ASLab ASys project. This document summarily describes the RCT as a framework for performing nal grade projects like PFC, TFM or TFG. Some specic project proposals are also described that oer a wide spectrum of possibilities ranging from embedded control systems to software engineering for distributed AI or machine consciousness.
Keywords

autonomy

robotics

engineering

consciousness

his document summarily describes the Robot Control testbed (RCT) research platform that serves as framework for a collection of nal grade, student-sized projects. This is part of the research on robotics platforms for testing the developments in the ASys long term project on autonomous systems. If you are interested in doing your PFC/TFG/TFM in ASLab, please read this document and feel free to ask any question to the ASLab coordinator (ricardo.sanz@upm.es). If you have special, new, challenging, personal ideas of what to do, feel also free to suggest them as research possibilities for your project. Please have in mind that ASLab is a research organisation that tries to build novel and sophisticated systems; and this requieres a wide spectrum of knowledge and ability to deal with the unknown that usually requieres some audacity, courage and boldness from the student.

any kind of mission (Sanz et al., 2000). This implies a wide range of (autonomous) systems to be considered in the research, from robots to industrial process plants or computing systems placed in the cyberspace. Additionally, the ASys science may serve as a systems-centric substrate for theories of natural autonomy that can explain how the human mind works (Collier, 2002). Tools from the AI eld have been extensively explored for intelligent control in the past few decades, improving the adaptivity and eciency of systems. However, as it has been pointed out, they are usually valuable only for a restricted type of problems. Besides, a not negligible amount of tuning for their application to the specic system is usually required. This means that: i) an important part of the adaptivity is still determined at the design stage, and ii) the achieved solution is only partially reusable for other systems, and hardly transferable to other domains. The underlying ideas of the ASys approach are: i) to overcome the previous issues by moving the responsibility for adaptation from design time to systems run time i.e. making the system responsible of its own adaptation, and ii) provide the solution in an architectural form, rather than an algorithmic one, so as to meet the non-functional requirements that appear in these systems.

Engineering Autonomy: the ASys Project

In ASLab we do research on autonomous systems. You can nd more information in our website www.aslab.org. Autonomous systems are systems that are capable of sustained provision of a particular service even in the presence of major uncertainties in the service demand, the context of service execution and the disturbances that the system may be suering from outside or even inside. The Autonomous Systems Project (ASys) of the UPM Autonomous System Laboratory (ASLab) tries to develop universal control technology for autonomy.

ASys

Our autonomy technology evolves from early attempts to apply articial intelligence to control systems (Sanz, 1990), using recent theoretical achievements in the conceptualisation the domain of perception (L opez, 2007), or developments that formalise them into usable software assets, such as an ontology for the engineering of autonomous systems (Bermejo-Alonso, 2010). ASys Project Vision. The project intends the creation of science and technology for universal autonomy. In this context, universal means that the technology shall be eective in augmenting the level of autonomy of any kind of artifact in
www.aslab.org/documents/controlled/A-2014-005.pdf

Model-based Autonomy. The strategy proposed to address adaptation at run-time is that of exploiting cognitive selfcontrol loops, which are control loops based on knowledge. This knowledge is realised in the form of dierent models: of the system, of the environment, and of its mission. This is what we call the model-based view of cognition. The pervasive model-based approach in ASys is twofolded: i) an ASys system will be built using models of it and ii) an ASys system will also exploit models of itself to drive its operation or behaviour. Model-based engineering and model-based behaviour then merge into a single driving concept: model-based autonomy. The main goal: the models the system will use to control its behaviour will eventually be those very same models used by engineers to build it. Models thus constitute the core for our autonomous systems research programme. Unied functional and structural views are considered critical for our research as they provide knowledge about both the intended and the expectable behaviours of the system. The obtained models will be exploited by means of commercial application engines or customised model execution modules. Models will be exercised during runtime to derive the most suitable actions to do. Models are the knowledge that the autonomous agent will use to act properly.

About ASLab
The Autonomous Systems Laboratory is a research group focused on the generation of science and technology for robust autonomy. This is a technical property of systems that make them capable of sustained provision of a particular service even in the presence of major uncertainties in the service demand, the context of service execution and the disturbances that the system may be suering from outside or inside. Find us at www.aslab.org.

ASLAB

March 12, 2014

A-005

v01

15

ASys-Vision-04

Requirements Views

ICe Design

ICe Specication

Asset Base Domain Domain Ontology Domain Ontology Ontology OAsys Ontology

Model
Metamodel Documentation

and developed products (ontologies, models, views, engines) shall be determined and possible adaptations and extensions shall also be considered. The denition and the consolidation of architectural patterns that capture ways of organising components in functional subsystems is critical. As a generalisation strategy, the dierent elements considered in the ASys research programme will be assessed in dierent testbed systems: mobile robots, a chemical reactor, etc. An integrated approach to engineering autonomy. The strategy to follow to materialise the ASys vision is the construction of a systems engineering framework (Johnson, 1997) that can support the engineering processes associated with the construction of autonomous systems. Figure 1 summarily depicts the entities, tooling and activities involved in this process. It integrates the previously discussed ideas: an architecture-centric design approach, a methodology to engineer autonomous systems based on models, and an asset base of modular elements to ll in the roles specied in the architectural patterns. The engineering process covers from the initial capture of application requirements and domain knowledge, to the implementation of the nal product i.e. the autonomous system. The ASys vision suggests that the self-x competences (Sanz et al., 2005) that are necessary to increase system autonomy and resilience, can be based on the models used in the engineering of the system. As depicted in gure 1, the autonomous system Model is transformed, by synthesis, in 1) the Autonomous System and 2) the run-time Model of itself that it uses during its operation. The central part of gure 1 shows this process where the Model is transformed into the Autonomous System. The Integrated Control Environment (ICe) toolset shall be used to exploit an asset base to sustain this engineering process. The asset base contains : ASys Ontology: An ontology of the domain of general autonomous systems. This serves as the core ontological substrate for all ASys elements. Domain Ontologies: Domain ontologies focused in the different application domains of ASys. The two domains that are the current focus of the work are process control systems and mobile robotics. Design Patterns: Reusable functional designs of subsystems of the autonomous agent. Components: Reusable software implementations that can be used to play the roles specied by the patterns. The ICe tool supports several activities: Specication: The specication of the ASys concerns the intended use and autonomy properties for the agent. Design: The design species the architectural organization of the agent using the ASys pattern language as design vocabulary. Synthesis: The synthesis produces both the agent implementation obtaining components for the pattern roles and the run-time model by means of model transformation methods. Documentation: The capture of all reference material that may remain somewhat hidden due to the automated nature of some of the processes. Deployment: Deployment of the ASys and run-time models in real operational conditions. Operation: Operation of the ASys through an RCP-based user interface. Asset Management: Management of the asset base including incorporation of new assets specically developed for concrete applications.
R. Sanz

ICe

Pattern Pattern Pattern

ICe Synthesis

Documentation

Component Component Component

Autonomous System
Engine
Model Metamodel

ICe Deployment

Engine

ICe Asset Management

ICe Operation

Figure 1 Tasks and products in the overall ASys vision (adapted from (Sanz et al., 2008))

The ASys Architectural Approach. Focusing on the systems architecture is focusing on the structural properties that constitute the more pervasive and stable properties of the system (Shaw and Garlan, 1996). Architectural aspects are what critically determine the nal capabilities of any information processing technology, such as control systems. ASys seek for an architectural solution derives from its intention to address all the domain of autonomy, and therefore for the developed technology to be of general applicability, so it be usable to develop control systems for any plant, e.g. continuous process plants, air-trac control or mobile robots; and to meet the critical demands for dependability and survivavility, because they critically depend on the systems architecture. In addition, architecture-based development oers the following advantages:
Systems can be built in a rapid, cost-eective manner

by importing (or generating) externally developed components. It is possible to predict global qualities of the nal system by analysing the architecture. The development of product lines sharing the same architectural design is easier and cheaper. Restrictions on design variability make the design process more productive and less prone to faults. ASys is thus interested in domain variations of architectural designs for their application to dierent autonomous systems. A reference architecture is an architecture where the structures and respective elements and relations provide templates to derive concrete architectures in a particular domain or in a family of software systems, and can be expressed in a reference architecture model. The ASys approach is strongly conceptual and architecturecentric. The suitability of extant control and cognitive control architectures and how they match the ASys research ideas
2 www.aslab.org/documents/controlled/A-2014-005.pdf

The Robot Control Testbed

ASys technology tries to be universal, i.e. of applicability to dierent applications in dierent domains. The Robot Control Testbed (RCT) is a collection of mobile robot systems that are used to test the technologies that we develop. In parallel, the Process Control Testbed (PCT) is a continuous process control system that we use to test the applicability of the technology in the domain of industrial chemical processes. Al the project proposal described here are related to the RCT. The main robot robot that we have selected for the PCT is a well known Pioneer 2AT8 robot (see Figure 2). We call it Higgs. The Pioneer 2AT-8 is a mobile robot made by ActivMedia Robotics. It is a skid-steering vehicle with lightweight aluminium body and four pneumatic wheels propelled by four reversible DC motors, equipped with high-resolution optical encoders for precise position and speed sensing and advanced dead-reckoning. Electronic devices aboard are controlled by a Hitachi H8S microcontroller. Additional computing boards provide extra computing capabilities for open implementation of on-board software.

Higgs User Interface

The focus of this PFC is the construction of a new user interface for the visualisation and control of the robot state. This may include some physical parameters but also information about the state of the control system of the robot. There are two current implementations:
One is based on the extant user interfaces oered by the

ROS middleware and its associated stacks. This is a localised/distributed interface that runs atop the ROS middleware and hence requires it for execution (hence limiting the portability of the UI, esp. to Linux/Ubuntu hosts). The second one the Android Robot Interface (ARI) run atop an android device (see Figure 3).

Figure 3 A screen capture of the ARI user interface for Higgs.

Read the PFC by Alberto Gonzlez to know about the different issues in the Higgs testbed (Gonz alez, 2013). Read the PFC by Javier Mata to know about the Android user interface (Mata, 2013).

Figure 2.2: Pioneer 2-AT8 (Higgs) with onboard systems

Figure 2 The Higgs Pioneer 2AT robot.

An HTML5 version of the Higgs User Interface

The purpose of the HTML5 Higgs User Interface project is to develop a pure-HTML5 variant of the user interface for Higgs. This will enable the remote use of the robot from any browser able to handle this language.

The Pioneer 2AT robot has also other equipment that is used for dierent technology evaluation missions:
Two sonar arrays, each with eight transducers that pro-

14 of 45

vide object detection and range information for collision avoidance. Two frontal and rear bumpers. An stereo camera sometimes replaced by a monocular camera to explore alternative designs. R-2010-008 v 0.1 Draft / Higgs Manual / ASLab.org A laser rangender. A GPS positioning system. A compass and accelerometers. Wireless communications.

HTML5 is a future standard for the WWW by the World Wide Web Consortium. www.ww3.org

With this robot we explore to what extent our autonomy software improves the performance of the robot in the execution of its missions. In particular we explore to what extent, making Higgs self-aware can improve the robustness and resilience of the robot (Sanz et al., 2007; Hern andez, 2013).
R. Sanz

HTML5 is a future HTML standard by the World Wide Web Consortium (W3C). The current version is not yet an approved specication but just a W3C Candidate Recommendation. See http://www.w3.org/TR/html5/ for detailed information about the specication.
ASLab March 12, 2014 A-005 v01 3

This specication denes the 5th major revision of the core language of the World Wide Web: the Hypertext Markup Language (HTML). In this version, new features are introduced to help Web application authors, and special attention has been given to dening clear conformance criteria for user agents in an eort to improve interoperability.

References
Bermejo-Alonso, J. (2010). OASys: An Ontology for Autonomous Systems. PhD thesis, Departamento de Autom atica, Universidad Polit ecnica de Madrid. Collier, J. (2002). What is autonomy? International Journal of Computing Anticipatory Systems, 12:212221. Gonz alez, A. (2013). Implementaci on de un banco de pruebas para el marco de la arquitectura OM (the operative mind architecture). Proyecto Fin de Carrera. Universidad Polit ecnica de Madrid - Autonomous Systems Laboratory. Hern andez, C. (2013). Model-based Self-awareness Patterns for Autonomy. PhD thesis, Escuela T ecnica Superior de Ingenieros Industriales - Universidad Polit ecnica de Madrid. Johnson, R. E. (1997). Frameworks = (components + patterns). Commun. ACM, 40(10):3942. L opez, I. (2007). A Framework for Perception in Autonomous Systems. PhD thesis, Departamento de Autom atica, Universidad Polit ecnica de Madrid. Mata, J. (2013). ARI - android robot interface. Proyecto Fin de Carrera. Universidad Polit ecnica de Madrid - Autonomous Systems Laboratory. Sanz, R. (1990). Arquitectura de Control Inteligente de Procesos. PhD thesis, Universidad Polit ecnica de Madrid.

Sanz, R., G omez, J., Hern andez, C., and Alarc on, I. (2008). Thinking with the body: Towards hierarchical scalable cognition. In Handbook of Cognitive Science: An Embodied Approach. Elsevier. Sanz, R., L opez, I., and Bermejo-Alonso, J. (2007). A rationale and vision for machine consciousness in complex controllers. In Chella, A. and Manzotti, R., editors, Articial Consciousness, pages 141155. Imprint Academic. Sanz, R., L opez, I., Bermejo-Alonso, J., Chinchilla, R., and Conde, R. (2005). Self-x: The control within. In Proceedings of IFAC World Congress 2005. Sanz, R., Mat a, F., and Gal an, S. (2000). Fridges, elephants and the meaning of autonomy and intelligence. In IEEE International Symposium on Intelligent Control, ISIC2000, Patras, Greece. Shaw, M. and Garlan, D. (1996). Software Architecture. An Emerging Discipline. Prentice-Hall, Upper Saddle River, NJ.

Ricardo Sanz
UPM Autonomous System Laboratory www.aslab.org www.rsanz.com Contact: ricardo.sanz@upm.es

aslab

www.aslab.org/documents/controlled/A-2014-005.pdf

R. Sanz