Difference between revisions of "RoboCup"
|Line 70:||Line 70:|
Revision as of 10:38, 18 August 2016
This page is currently being developed
- Integration (Team Leader): Francisco Javier Rodríguez Lera
- Navigation and Control: Francisco Martín Rico
- Manipulation: Fernando Casado García, Alvaro Moreno García,
- Navigation: Jesús Balsa Comerón, Jonathan Gines Claveo, Francisco Javier Gutierrez-Maturana
- Perception: Diego García Ordás, Alvaro Moreno García, Francisco Javier Gutierrez-Maturana
- Team Director: Vicente Matellán Olivera
– Robot name: RB1
- . Base: Robotnik (Dinamixel Motors)
- . Vision Sensors: RGB-D Xtion
- . Range sensors: Frontal laser
- . Dialogue Sensors: Directional microphone Rode Rycote , Loudspeakers
- . Manipulation: 7DOF arm. Dynamixel Pro servos. Workspace: 70 cm
- . Computer Description: Intel Core i7 with 8 GB of RAM and a 200 GB of disk
- . Torso: +40
- . Head: pan-tilt head.
– Development framework: ROS
- . Vision: ork, findobject
- . Dialogue: Pocketsphinx
- . BellRecognition: pyaudio
- . Manipulation: MoveIt, self developements.
- . Navigation: Ros stack, self developements.
– Robot Control: Finite State Machine (FSM) using Bica
The video presents a surveillance task in our lab. It shows the navigation approach of OrbiOne robot (RB1-robotnik robot) in our apartment.
The robot navigates different apartment rooms in order to check user availability (living room and bedroom), visits (apartment front door after the doorbell rings) or alarm situation (fridge open-door alarm).
Quiz Game and Context Awareness
Trivia game between user and robot. The conversation is interrupted by a ringbell.
We have a three layer architecture based on ROS and BICA . The lower layer corresponds to ROS, and is in charge of hardware management. The intermediate layer provides the robot skills in order to carry out specific duties (perception, navigation,...). The top layer presents BICA. It is a component-based for generating behaviors architecture. This node coordinates the various capabilities of the robot depending on the task to be carried out by the robot. Figure 2 shows the overall architecture of the software we have developed for participating in the RoCKIn competition.