Difference between revisions of "Proj-2013-2014-RobAIR-2"

From air
Jump to navigation Jump to search
 
(23 intermediate revisions by the same user not shown)
Line 12: Line 12:
   
 
*Departement : [http://www.polytech-grenoble.fr/ricm.html RICM 4], [[Polytech Grenoble]]
  
*Departement : [http://www.polytech-grenoble.fr/ricm.html RICM 4], [[Polytech Grenoble]]
  +
  +
= Related documents =
  +
  +
* How to create your own robot : [[Proj-2013-2014-RobAIR-2/How_to_create_robAIR|here]]
  +
* How to install ROS and run your first package : [[Proj-2013-2014-RobAIR-2/getStarted|here]]
  +
* How to configure and launch your robot : [[Proj-2013-2014-RobAIR-2/How_to_configure_robAIR|here]]
  +
* Our report : [[File:Projet-robAir.pdf|here]]
   
 
= Project objectives =
  
= Project objectives =
   
  +
*Build the new robAIR with his new architecture and sensors
−
Not decided yet (in progress...)
  
  +
*Create a strong documentation in order to help future students and apprentices in robotics to build their own robot
   
 
= Software Requirements Specification =
  
= Software Requirements Specification =
   
−
The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.
 +
* The Software Requirements Specification (SRS) can be found [[Proj-2013-2014-RobAIR-2/SRS|here]].
   
  +
= Progress of the project =
   
  +
The project started January 14th, 2013.
−
'''Read first:'''
  
−
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
  
−
* http://en.wikipedia.org/wiki/Software_requirements_specification
  
−
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]
  
   
  +
== Week 1 (January 13th - January 19th) ==
−
{|class="wikitable alternance"
  
  +
*Project discovery
−
|+ Document History
  
  +
*Research on related projects (previous years: [http://air.imag.fr/index.php/RobAIR2013 2013], [http://air.imag.fr/index.php/RobAIR2012 2012])
−
|-
  
  +
*Learning of ROS: [http://www.ros.org/ Official website]
−
|
  
−
!scope="col"| Version
  
−
!scope="col"| Date
  
−
!scope="col"| Authors
  
−
!scope="col"| Description
  
−
!scope="col"| Validator
  
−
!scope="col"| Validation Date
  
−
|-
  
−
!scope="row" |
  
−
| 0.1.0
  
−
| TBC
  
−
| TBC
  
−
| TBC
  
−
| TBC
  
−
| TBC
  
   
  +
== Week 2 (January 20th - January 26th) ==
−
|}
  
  +
*Learning of ROS (in progress)
  +
*Installation of ROS packages on Ubuntu (in progress)
  +
*Assembly of two new RobAIRs (they will be named soon...) (in progress)
   
  +
== Week 3 (January 27th - February 2nd) ==
  +
*Assembly of two new RobAIRs (they will be named soon...)
  +
*Beginning of the redaction of Software Requirements Specification
  +
*ROS environment installed on Ubuntu
  +
*RobAIR can now move by itself ! (debug in progress)
  +
*Meeting with Amr Alyafi (effective code obtained)
   
  +
== Week 4 (February 3rd - February 7th) ==
−
==1. Introduction==
  
  +
*Integration of basic sensors (infrareds and ultrasonics)
−
====1.1 Purpose of the requirements document====
  
  +
*Debug of Amr Alyafi code (a lot of variable are written directly in the code, so it's not portative at all...)
−
====1.2 Scope of the product====
  
−
====1.3 Definitions, acronyms and abbreviations====
  
−
====1.4 References====
  
−
====1.5 Overview of the remainder of the document====
  
−
==2. General description==
  
−
====2.1 Product perspective====
  
−
====2.2 Product functions====
  
−
====2.3 User characteristics====
  
−
====2.4 General constraints====
  
−
====2.5 Assumptions and dependencies====
  
−
==3.Specific requirements, covering functional, non-functional and interface requirements==
  
−
* document external interfaces,
  
−
* describe system functionality and performance
  
−
* specify logical database requirements,
  
−
* design constraints,
  
−
* emergent system properties and quality characteristics.
  
   
  +
== Week 5 (February 10th - February 14th) ==
−
====3.1 Requirement X.Y.Z (in Structured Natural Language)====
  
  +
*Installation and configuration of Arduino IDE
−
'''Function''':
  
  +
*Basic sketch test ( diode, sensor )
  +
*Meeting with Amr Alyafi in order to check if everything is plugged and installed corretly
  +
*Switch Meduino card to Arduino Mega 25.60 card in order to solve transfer problems
  +
*Implementation, debug and test of arduino sketches and ros code using only one ultrasonic sensor
  +
*RobAIR works! <br> http://www.youtube.com/watch?v=g5XhrDY0tFI&feature=youtu.be
   
  +
== Week 6 (February 17th - February 22th) ==
−
'''Description''':
  
  +
*Installation of 5 other ultrasonic sensors
  +
*Adaptation of arduino code and ros cos for our installation ( with pin and trigger numbers )
  +
*Debug
  +
*All sensors finally work
  +
*Presentation of RobAIR at Polytech Open Day the 22th
   
  +
== Week 7 (February 24th - February 28th) ==
−
'''Inputs''':
  
  +
*Installation of 8 infrared sensors
  +
*Adaptation of arduino code and ros cos for our installation ( with pin trigger numbers )
  +
*Debug ( in progress )
   
  +
== Week 8 (March 10th - March 14th) ==
−
'''Source''':
  
  +
*Mid-Project presentation in order to check the advanced
  +
*Final debug of infrared sensors
  +
*Installation of lidar with library
   
  +
== Week 9 (March 17th - March 21th) ==
−
'''Outputs''':
  
  +
*We tried several package, and Hokuyo Node was the best one.
  +
*Lidar works, but isn't doing what we expected, there is only cloud point and it's not generating a sort of map.
  +
*We are currently working on RVIZ configurations, because previous configs was cfg files and not rviz files.
   
  +
== Week 10 (March 24th - March 28th) ==
−
'''Destination''':
  
  +
*Still working on rviz and lidar, trying to figure out why we cant get map from the lidar
  +
*Rework on the script to launch robAir, in order to use our config on Hokuyo and RVIZ
   
  +
== Week 11 (March 31th - April 4th) ==
−
'''Action''':
  
  +
*Scripts are finished
−
* Natural language sentences (with MUST, MAY, SHALL)
  
  +
*Rework on the robAIR hardware, so that the connecting branches are clean
−
* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
  
  +
*Repairing of the wheel that is not working properly
−
* Mathematical Notations
  
  +
*Meeting with Amr Alyafi in order to know how the lidar is working to generate a map
−
* Tabular notations for several (condition --> action) tuples
  
  +
*It seems like we cant generate a map with lidar, so we will try to use a kinect
   
  +
== Week 12 (April 7th - April 9th) ==
−
'''Non functional requirements''':
  
  +
*Trying to install Kinect, but it's currently not working
−  
  +
*Finalisation of everything, in order to have a clean project for the presentation
−
'''Pre-condition''':
  
  +
*Creation of presentation, flyer, poster
−  
−
'''Post-condition''':
  
−  
−
'''Side-effects''':
  
−  
−
==4. Product evolution==
  
−  
−
==5. Appendices==
  
−  
−
====5.1. SRS structure====
  
−
The document is based on template of the Software Requirements Specification (SRS) inspired of the IEEE/ANSI 830-1998 Standard.
  
−  
−
'''References:'''
  
−
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
  
−
* http://en.wikipedia.org/wiki/Software_requirements_specification
  
−
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]
  
−  
−
==6. Index==
  
−  
−
= Progress of the project =
  
−  
−
The project started January 14th, 2013.
  
−  
−
== Week 1 (January 13th - Janurary 19th) ==
 
−
*Project discovery
  
−
*Research on related projects (previous years: [http://air.imag.fr/index.php/RobAIR2013 2013], [http://air.imag.fr/index.php/RobAIR2012 2012])
  
−
*learning of ROS: [http://www.ros.org/ Official website]
  

Latest revision as of 09:45, 9 April 2014

Introduction

The Robair project aims to develop a platform for robotic telepresence used for both teaching ambient intelligence and testing low cost (ie well below the price of market platforms) of service robotics in real environments. This platform aims extensible and open source (open software, open hardware, open design, open data).

More information on Project RobAIR

Team

  • Tutors : Didier Donsez, Amr Alyafi
  • Members : David Levayer, Paul Mariage

Related documents

  • How to create your own robot : here
  • How to install ROS and run your first package : here
  • How to configure and launch your robot : here
  • Our report : File:Projet-robAir.pdf

Project objectives

  • Build the new robAIR with his new architecture and sensors
  • Create a strong documentation in order to help future students and apprentices in robotics to build their own robot

Software Requirements Specification

  • The Software Requirements Specification (SRS) can be found here.

Progress of the project

The project started January 14th, 2013.

Week 1 (January 13th - January 19th)

Week 2 (January 20th - January 26th)

  • Learning of ROS (in progress)
  • Installation of ROS packages on Ubuntu (in progress)
  • Assembly of two new RobAIRs (they will be named soon...) (in progress)

Week 3 (January 27th - February 2nd)

  • Assembly of two new RobAIRs (they will be named soon...)
  • Beginning of the redaction of Software Requirements Specification
  • ROS environment installed on Ubuntu
  • RobAIR can now move by itself ! (debug in progress)
  • Meeting with Amr Alyafi (effective code obtained)

Week 4 (February 3rd - February 7th)

  • Integration of basic sensors (infrareds and ultrasonics)
  • Debug of Amr Alyafi code (a lot of variable are written directly in the code, so it's not portative at all...)

Week 5 (February 10th - February 14th)

  • Installation and configuration of Arduino IDE
  • Basic sketch test ( diode, sensor )
  • Meeting with Amr Alyafi in order to check if everything is plugged and installed corretly
  • Switch Meduino card to Arduino Mega 25.60 card in order to solve transfer problems
  • Implementation, debug and test of arduino sketches and ros code using only one ultrasonic sensor
  • RobAIR works!
    http://www.youtube.com/watch?v=g5XhrDY0tFI&feature=youtu.be

Week 6 (February 17th - February 22th)

  • Installation of 5 other ultrasonic sensors
  • Adaptation of arduino code and ros cos for our installation ( with pin and trigger numbers )
  • Debug
  • All sensors finally work
  • Presentation of RobAIR at Polytech Open Day the 22th

Week 7 (February 24th - February 28th)

  • Installation of 8 infrared sensors
  • Adaptation of arduino code and ros cos for our installation ( with pin trigger numbers )
  • Debug ( in progress )

Week 8 (March 10th - March 14th)

  • Mid-Project presentation in order to check the advanced
  • Final debug of infrared sensors
  • Installation of lidar with library

Week 9 (March 17th - March 21th)

  • We tried several package, and Hokuyo Node was the best one.
  • Lidar works, but isn't doing what we expected, there is only cloud point and it's not generating a sort of map.
  • We are currently working on RVIZ configurations, because previous configs was cfg files and not rviz files.

Week 10 (March 24th - March 28th)

  • Still working on rviz and lidar, trying to figure out why we cant get map from the lidar
  • Rework on the script to launch robAir, in order to use our config on Hokuyo and RVIZ

Week 11 (March 31th - April 4th)

  • Scripts are finished
  • Rework on the robAIR hardware, so that the connecting branches are clean
  • Repairing of the wheel that is not working properly
  • Meeting with Amr Alyafi in order to know how the lidar is working to generate a map
  • It seems like we cant generate a map with lidar, so we will try to use a kinect

Week 12 (April 7th - April 9th)

  • Trying to install Kinect, but it's currently not working
  • Finalisation of everything, in order to have a clean project for the presentation
  • Creation of presentation, flyer, poster
Retrieved from "https://air.imag.fr/index.php?title=Proj-2013-2014-RobAIR-2&oldid=17021"