Chico: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 27: | Line 27: | ||
When a joint/encoder breaks, refer to [[Chico joint calibration]]. | When a joint/encoder breaks, refer to [[Chico joint calibration]]. | ||
== iCub health checkup week == | |||
On March 1st 2011 we decided to test the robot for one week, to assess its current "health" state. The results of the test are stored in [[iCubHealthCheckupWeek_03_2011]]. | |||
[[Category:Robots]] | [[Category:Robots]] | ||
[[Category:Vislab]] | [[Category:Vislab]] | ||
Revision as of 14:50, 2 March 2011
Preliminaries
- the iCub has a PC104 with a flash disk configured to 10.10.1.50
- it mounts the repositories that are on the icubsrv Dell XPS laptop (10.10.1.51, username icub)
- there is a visualization support machine, the black Tsunami laptop chico3 (10.10.1.53) to be used for demos.
The icubsrv laptop has 2 repositories:
- /exports/code-64 for the laptop (compiled for 64bit)
- /exports/code-pc104 for the robot (compiled for 32bit)
Everything running with /icub namespace
Maintenance
Software
Updating YARP and iCub on Chico
Refer to pc104#Repositories on icubsrv laptop.
CMake bug
Due to a CMake bug, whenever you compile something that features icubmoddev (the successor to yarpdev), you need to run CMake configure once; exit; without deleting the cache, run CMake configure again and proceed. So far, this is relevant for the pc104 as well as for machines that have to run other icubmoddev instances, e.g., a server running iKinArmCtrl.
Hardware
When a joint/encoder breaks, refer to Chico joint calibration.
iCub health checkup week
On March 1st 2011 we decided to test the robot for one week, to assess its current "health" state. The results of the test are stored in iCubHealthCheckupWeek_03_2011.