Nao: Difference between revisions

From Intelligent Materials and Systems Lab

No edit summary
 
(29 intermediate revisions by 2 users not shown)
Line 3: Line 3:
We are a team of people who are interested in robotics, software part of robotics to be more precise. After Robotex 2012 competition we wanted to do something cool and challenging, so we ended up playing around with 4 Nao robots who just waited to be found :)
We are a team of people who are interested in robotics, software part of robotics to be more precise. After Robotex 2012 competition we wanted to do something cool and challenging, so we ended up playing around with 4 Nao robots who just waited to be found :)


Our goal is to prepare Naos for [http://www.robocup.org/robocup-soccer/standard-platform/ Robocup Standard Platform] competition. But, whether or not we are able to succeed, we will make an effort to learn as much as possible through putting Naos to do something useful and pleasant.
Our goal is to prepare the Naos for [http://www.robocup.org/robocup-soccer/standard-platform/ Robocup Standard Platform] competition. But, whether or not we are able to succeed, we will make an effort to learn as much as possible through making the Naos do something useful and pleasant.


==How to set up?==
 
We used to use C++ and Python API for software development (and also played around with [https://developer.aldebaran-robotics.com/resources/tutorial/nao-first-steps/ Choreographe]). Shortly on how we started:
== Our solutions to some important problems ==
<ol>
*[[Nao_segmentation|Image segmentation and blob detection]]
<li>Get the latest version from [http://users.aldebaran-robotics.com/ http://users.aldebaran-robotics.com/], if you have robot with some kind of needed hardware configuration get it from your cd.</li>
*[[Nao_line_detection|Line detection]]
<li>For SDK installations follow [http://www.aldebaran-robotics.com/documentation/dev/cpp/install_guide.html#cpp-install-guide http://www.aldebaran-robotics.com/documentation/dev/cpp/install_guide.html#cpp-install-guide] for C++ and [http://www.aldebaran-robotics.com/documentation/dev/python/install_guide.html#python-install-guide http://www.aldebaran-robotics.com/documentation/dev/python/install_guide.html#python-install-guide] for Python.</li>
*[[Getting-real-world-coordinates-from-image-frame|Getting real world coordinates from the image]]
<li>And continue with tutorials and examples...</li>
*[[Nao_localization|Localization]]
</ol>
 
== How To ==
Developing software for Nao is full of challanges. Here we have some tutorials/instructions that might help you get started with the basic things.<br>
 
*[[Setup_Nao | How to start with Nao?]]
 
*[http://www.aldebaran-robotics.com/documentation/nao/upgrade.html Upgrade Nao - link to Aldebaran guide.]
 
*[[Start_learning_robotics | How to start learning robotics?]]
 
*[[Nao_Module | How to build a module?]]
 
*[[Nao_Keyboard_Control_Python | How to use keyboard to walk Nao around?]]
 
*[[Coping_with_Linux | How to cope with linux?]]
 
*[[Set_up_Opencv | How to set up OpenCV?]]


==What problems have we faced?==
==What problems have we faced?==
===Versions===
===Beginnings "Big Unknown"===
We started with Naos having version 1.12 everything and started learning from the default reference of SDK 1.14. We noticed it but didn't think that it would make a lot of difference... Wrong! Aldebaran is very actively advancing it's software. We had many problems with modules not existing on Nao etc and overall have spent a lot of time on it. So update and work with the newest and the coolest modules, or go to [https://developer.aldebaran-robotics.com/doc/1-12/ref/index.html API 1.12 reference] to avoid some frustration.
As you are reading this you are on the right direction:) We found also useful to read other users' tutorials especially wiki from [http://robotica.unileon.es/mediawiki/index.php/Nao_tutorial_1:_First_steps Robotics Group of the University of León].
===Versions2===
 
Useful to know that Aldebaran has made a list of function which have been changed [http://www.aldebaran-robotics.com/documentation/dev/cpp/tutos/porting_to_1.12.html].
===Version differences===
We started with Naos having version 1.12 everything and started learning from the default reference of SDK 1.14. We noticed it but didn't think that it would make a lot of difference... Wrong! Aldebaran is very actively advancing it's software. We had many problems with modules not existing on Nao etc and overall have spent a lot of time on it. So update and work with the newest and the coolest modules, or go to [https://developer.aldebaran-robotics.com/doc/1-12/ref/index.html API 1.12 reference] to avoid some frustration. A good tutorial is [http://www.aldebaran-robotics.com/documentation/nao/upgrade.html here].<br><br>
 
It is also useful to know that Aldebaran has made a list of function which have been changed [http://www.aldebaran-robotics.com/documentation/dev/cpp/tutos/porting_to_1.12.html].<br><br>
 
<b>N.B</b><br>
When updating Naos, don't forget updating the SDK, cross-toolchain, qibuild etc. If you do, you might encounter some errors that are really hard to interpret. One of such errors occoured when a module was built using the old version of Atom-cross-toolchain. When Naoqi tried loading the module, it gave:<br>
<code>libboost_signals-mt-1_45.so.1.45.0: cannot open shared object file: No such file or directory</code><br><br>
 
==="Hidden" files in users.aldebaran-robotics.com===
Getting state of art software for nao you can visit [http://users.aldebaran-robotics.com/ http://users.aldebaran-robotics.com/]. Login. Go Software > Download > All Downloads > Navigate there (all software isn't on the front page!).
 
 
===UTNAOtool misbehaviors===
Issues:
* Nao load up doesn't load everything correctly - have to make a Naoqi restart everything to be loaded correctly.
* Tool crashes on many uses. eg: Generate color table,

Latest revision as of 20:52, 15 August 2013

Summary

We are a team of people who are interested in robotics, software part of robotics to be more precise. After Robotex 2012 competition we wanted to do something cool and challenging, so we ended up playing around with 4 Nao robots who just waited to be found :)

Our goal is to prepare the Naos for Robocup Standard Platform competition. But, whether or not we are able to succeed, we will make an effort to learn as much as possible through making the Naos do something useful and pleasant.


Our solutions to some important problems

How To

Developing software for Nao is full of challanges. Here we have some tutorials/instructions that might help you get started with the basic things.

What problems have we faced?

Beginnings "Big Unknown"

As you are reading this you are on the right direction:) We found also useful to read other users' tutorials especially wiki from Robotics Group of the University of León.

Version differences

We started with Naos having version 1.12 everything and started learning from the default reference of SDK 1.14. We noticed it but didn't think that it would make a lot of difference... Wrong! Aldebaran is very actively advancing it's software. We had many problems with modules not existing on Nao etc and overall have spent a lot of time on it. So update and work with the newest and the coolest modules, or go to API 1.12 reference to avoid some frustration. A good tutorial is here.

It is also useful to know that Aldebaran has made a list of function which have been changed [1].

N.B
When updating Naos, don't forget updating the SDK, cross-toolchain, qibuild etc. If you do, you might encounter some errors that are really hard to interpret. One of such errors occoured when a module was built using the old version of Atom-cross-toolchain. When Naoqi tried loading the module, it gave:
libboost_signals-mt-1_45.so.1.45.0: cannot open shared object file: No such file or directory

"Hidden" files in users.aldebaran-robotics.com

Getting state of art software for nao you can visit http://users.aldebaran-robotics.com/. Login. Go Software > Download > All Downloads > Navigate there (all software isn't on the front page!).


UTNAOtool misbehaviors

Issues:

  • Nao load up doesn't load everything correctly - have to make a Naoqi restart everything to be loaded correctly.
  • Tool crashes on many uses. eg: Generate color table,