Chico: Difference between revisions
Jump to navigation
Jump to search
m (→Preliminaries) |
|||
| Line 6: | Line 6: | ||
The icubsrv laptop has 2 repositories: | The icubsrv laptop has 2 repositories: | ||
* /export/code_64 for the laptop (compiled for | * /export/code_64 for the laptop (compiled for 64bit) | ||
* /export/code_pc104 for the robot (compiled for | * /export/code_pc104 for the robot (compiled for 32bit) | ||
They are anonymous, so changes are not committable (DO NOT CHANGE) | They are anonymous, so changes are not committable (DO NOT CHANGE) | ||
Revision as of 15:43, 4 February 2010
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:
- /export/code_64 for the laptop (compiled for 64bit)
- /export/code_pc104 for the robot (compiled for 32bit)
They are anonymous, so changes are not committable (DO NOT CHANGE)
Everything running with /icub namespace
Maintenance
Software
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.