Labbook Dutch Nao Team
Error Reports
Bleu hips are squicking.Seems OK September 2015.
- Bleu sound falls away. Loose connector? September 2015.
- Nao's overheats faster when using arms than using legs.
Created Labbook 2016.
December 8, 2015
- Should study YARP as middle-layer, developed for iCub.
- There is a NaoYARP project page on github, but this is 4 years old (based on NaoQi 1.12).
November 28, 2015
November 19, 2015
- Tried the flashed Red and try Tai Chi again. First tried the Nao3 head, but this one is the Z-knikker Penalty mode that cannot be flashed.
- Tried with Noa9 (Burns), but now the Tai Chi fails on the right leg. Robot complains about hot arm. Cannot walk straight, walks a circle to the right.
- Tried Nao4 (Princess), now the Tai Chi fails on the left leg (and falled during walking, could be the power cord).
November 16, 2015
November 11, 2015
October 30, 2015
- Aldebaran requested to flash Red and try Tai Chi again. Downloaded NaoQi v2.1.3.3 and flashed via the Choregraphe->Connection->Advanced. After wakeup Princess said that a new OS was installed succesfully.
- The wake up was executed correctly, although I heard a click in Princess knee. The robot doesn't want to be tested with NaoQi.
- First I couldn't get a connection. Then Bonjour was gone. Restarted my laptop. Now I could connect, but during the preparation of sending the behavior I got the error: PackageManager::_openFileTransferSession module destroyed. Before it had said that there was no /tmp/*/.LastBehavior. Connection was lost, couldn't connect to NaoQi anymore.
September 23, 2015
- Tested Blue with head Nao10/Julia. Blue is marked with hot elbow. No problems with Tai Chi.
- Tested Green with head Nao9/Burns. Green is marked with broken ankle. Difficulty with waking up with right ankle, but once in correct position wake up succeeds. Did Tai Chi: OK. Did Move To: OK. Put the robot on its face and asked for a standup: OK. Seems like the geer of the ankle is reconnected again. Will ask Patrick to redo the test.
- So, for the moment, I will only send Red to Aldebaran.
- Found the github with the Nao-administration.
September 22, 2015
- Tested Bleu. Tai Chi was executed with only a minor problem; the sound sometimes fell away (loose connection of speaker?)
- Tested Rouge. No problems with Tai Chi.
- Tested Purple with head Carlos. No problems with Tai Chi. Put Purple without battery in cabinet.
- Tested White with head Nao1. Sound was off. Made a wireless connection to server. No problems with Tai Chi.
- Tested Diamond with head Nao11/Hooke. No problems with Tai Chi.
- Tested Magneta with head Nao2/DownyJr. No problems with Tai Chi.
- Tested Red with head Nao4/Princess. Problems with Tai Chi, cannot support itself on left leg.
- Tested Cyan with head Nao10/Julia. No problems with Tai Chi. Put back in cabinet without battery (we are short on batteries).
- Tested Emerald with head Nao8/Baratheon. No problems with Tai Chi. Asks for a reboot, due to a firmware update. Still same warning after the reboot. Connected Baratheon to my Aldebaran account for the Aldebaran AppStore.
September 20, 2015
- Combining WeBots and ROS is possible according to the guide of Cyberbotics, although not trivial (there is a standard controller available, but if you want more you have to build a Custom Controller).
September 19, 2015
- First edited the python scripts on nb-udk, but the behavior.xar still contained the altools-code. Modified the code on Bleu, but still the module was not found. Added PYTHONPATH with ~/naoqi/lib/python to the bashrc, but no effect. Made a symbolic link to abcdk in stand_angry_2_emo, but still errors. Even angry_1, which worked yesterday, gives errors. Strange!?
September 18, 2015
- Trying to upload the emotion behaviors to Blue which is running NaoQi 1.14.5. Could only load *.crg files, such as the AugsburgEmotions in DNDD/NaoShare. The Anger_1_emo is a standing emotion. The init fails on a usage of Altools.PoseLibrary.compare positions. Couldn't find any reference to this library, except from this github with nearly all three year old behaviors. The poselibrary is in the Aldebaran Behavior Complementary Development Kit from 2010.
- Installed the Aldebaran Behavior Complementary Development Kit by copying the behavior over the old Anger_1_emo behavior.xar (in /home/nao/behaviors). The kit is installed in /home/nao/naoqi/lib/python/abcdk.
- Created a link to the directory abcdk in behavior-directory stand_anger_1_emo and modified the xar-file with vi. Changed import altools to import abcdk.poselibrary and the call altools.PoseLibary to . The behavior initiates now without errors, I only get warnings about deprecated functions (getJointNames -> getBodyNames) and batteryPowerPluggedChanged and onBatteryMeasure. The first is in abcdk/poselibrary.py Iand abcdk/motiontools.py. Tried to remove the getJointNames warning, but updating both python files (in several abcdk directories) didn't help.
July 5, 2015
- Received the crg from Houda, exported it to a package with Choregraphe 2.1.0 and tried to upload it to the store. At 100% I get a file not found screen, so maybe the package is too big.
- Try what happens with a conversion with the latest version of Choregraphe (2.1.3).
June 18, 2015
- Received the Optitrack Tracker Bundel 6 Flex 13. Software is available for Windows. My drive on nb-udk is full, tried to start pc-udk in the lab. Unfortunatelly, the screen becomes black after the startup screen. By clicking F8 I tried to recover, by doing a system restore. Yet, the images from 2015 and the latest 2014 recovery points gave an error (Px8000ffff).
- Did a memory check (without problems).
- Should try to start in low resolution and try an Nvidia update. Before I could give an update, I finally receive another screen. System is safely restored to one of the 2014 recovery points. Downloaded for the Quadro 600 drivers 356.06 (and installing Java in the background).
- Should try this Windows hotfix.
- Finally solved the issue by disconnecting the VGA cable :-). Did a Nvidia update via Windows Update (automatic detection of NVidia drivers did not work for Chrome).
March 24, 2015
- Received the MacBooks from the ITS Academy. Choreographe 1.12.5 is installed.
- Did not see the NaoIntroduction directory.
- The NaoIntroduction on my memorystick claims: "De voorbeelden in het boek zijn gebaseerd op Choregraphe 1.12.0. De voorbeelden zijn in deze introductie aangepast aan Choregraphe 1.14. " .
- I have 11 Nao robots, 9 chargers and 15 batteries. The Nao robots have the following NaoQi's: 3x 2.1.0.19, 3x 1.14.5, 1x 1.14.0 and 2x bHuman (+ Bleu 1.14.1 and Rouge 1.14.5).
- Upgraded 3 MacBooks to Choregraphe 2.1.0.19 and Python2.7-2.1.0.19 (and added NaoIntroduction-directory).
- Renamed 192.168.1.29 to DownyJr.
- Followed the procedure of cs.mtech.edu to flash the robot. Diskpart didn't seem to work because the ext4-service was active on nb-udk, but on the end I saw that the disk was empty and could be prepared for flashing. Forget to keep the chest button pressed for a long time, but the machines are busy, so it looks like a flash.
- Old resources can be found at community.aldebaran-robotics.com/resources/archives/. Unfortunatelly, no old 2.1.0.19 image. Made a 2.1.2.17 flash-stick, and downloaded Choreographe and PythonSDK.
Previous Labbook