Nao: Difference between revisions

From Intelligent Materials and Systems Lab

Line 6: Line 6:


==How to set up?==
==How to set up?==
We used to use C++ and Python API for software development. Shortly how we started.
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:
<ol>
<ol>
<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>
<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>

Revision as of 23:34, 4 February 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 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 putting Naos to 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 Choreographe). Shortly on how we started:

  1. Get the latest version from http://users.aldebaran-robotics.com/, if you have robot with some kind of needed hardware configuration get it from your cd.
  2. For SDK installations follow 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 for Python.
  3. And continue with tutorials and examples...

What problems have we faced?

Versions

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.

Versions2

Useful to know that Aldebaran has made a list of function which have been changed [1].