Chico: Difference between revisions

From ISRWiki
Jump to navigation Jump to search
No edit summary
(→‎iCub health checkup week: move to Archive subpage)
 
(67 intermediate revisions by 5 users not shown)
Line 1: Line 1:
= Chico Instructions =
This article describes '''Chico''' (code-name iCubLisboa01, [http://wiki.icub.org/wiki/ICub_versions iCub version] 1.2.1), the whole-body humanoid robot of [[Vislab]].


== Preliminaries ==
''For demo instructions, refer to [[iCub instructions]].''


ICub has a PC104 with a flash disk. configured to 10.10.1.50
''Note: see [[Chico/Archive]] about historical information.''
it mounts the repositories that are on the laptop 10.10.1.51


the laptop has 2 repositories
TODO: to be completed and updated, in particular the firmware information below is obsolete.


/export/code_64 for the laptop (compiled for 32bit)
= Preliminaries =
/export/code_pc104 for the robot (compiled for 64bit)


they are anonymous, so changes are not commitable (DO NOT CHANGE)
* the iCub has a [[pc104|PC104]] with a flash disk configured with IP 10.10.1.50
* it mounts the repositories that are on the '''icub-laptop''' machine (10.10.1.53)


pass icub icub
= Maintenance =


everything running with root namespace
== Arm fine calibration ==


== Running a demo ==
Refer to http://wiki.icub.org/wiki/ArmFineCalibration


1- Turn on the laptop
Basically, with yarpmotorgui set the arm joints to [-90 15 15 90]. Visually compare the arm angles with the reference picture.
run the yarp server
"yarp server"


== Hardware ==


2- Turn on the robot
CAN 0, board 14 is just a spare board that lies in Chico's head (inherited from the design of the previous version of the head), not being used at the moment. It can slow down the CAN communication because the board is present and responding. If needed, we can disconnect it as shown:
it will mount the repository


[[Image:ICub_headV2_CAN0_board14_disconnected.jpg|600px|How to disconnect board 14.]]


3- Start yarp run
When a joint/encoder breaks, refer to [[Chico joint calibration]].


/iCub/app/default/scripts/
== Firmware ==
./icub-cluster.sh run
./icub-cluster.sh check
there must be 3 ok messages


if some problem
Keep same Release and Version numbers; only increment Build number. Refer to [http://wiki.icub.org/wiki/Firmware this page] from the official iCub manual, using the following script:
./icub-cluster.sh check
  ./updateRobot.sh updateLisboa01.txt
./icub-cluster.sh stop
killall yarp


killall yarp on pc104
[[Category:Robots]]
 
[[Category:Vislab]]
./icub-cluster.sh run
 
 
4- turn on cameras
 
cameras start
 
cameras stop
 
 
5- Run iCubInterface (hardware except cameras)
 
open a pc104 console
 
iCubInterface --config $ICUB_ROOT/app/iCubLisboa01/conf/icubSafe.ini
wait for all boards to answer ( < 1 min )
 
control^C to cancel
 
 
6- Run demo
 
iCubDemoY3 --config /app/demoy3/fullBody.txt
 
[[Category:Robots]][[Category:Vislab]]

Latest revision as of 16:02, 10 July 2017

This article describes Chico (code-name iCubLisboa01, iCub version 1.2.1), the whole-body humanoid robot of Vislab.

For demo instructions, refer to iCub instructions.

Note: see Chico/Archive about historical information.

TODO: to be completed and updated, in particular the firmware information below is obsolete.

Preliminaries

  • the iCub has a PC104 with a flash disk configured with IP 10.10.1.50
  • it mounts the repositories that are on the icub-laptop machine (10.10.1.53)

Maintenance

Arm fine calibration

Refer to http://wiki.icub.org/wiki/ArmFineCalibration

Basically, with yarpmotorgui set the arm joints to [-90 15 15 90]. Visually compare the arm angles with the reference picture.

Hardware

CAN 0, board 14 is just a spare board that lies in Chico's head (inherited from the design of the previous version of the head), not being used at the moment. It can slow down the CAN communication because the board is present and responding. If needed, we can disconnect it as shown:

How to disconnect board 14.

When a joint/encoder breaks, refer to Chico joint calibration.

Firmware

Keep same Release and Version numbers; only increment Build number. Refer to this page from the official iCub manual, using the following script:

 ./updateRobot.sh updateLisboa01.txt