Chico head - Revision history

Mtaiana: /* Known problems */

2014-03-24T20:10:06Z

Known problems

← Older revision		Revision as of 20:10, 24 March 2014
Line 42:		Line 42:
	* Sometimes the iCubInterface gets stuck because it stops being able to communicate with some of the boards. It happened once on Mar. 21 2014 while the head seemed to be the limit of one of the joints. That joint was not actuated any more, while the others remained actuated. A similar problems seems to be happening on Vizzie.<br>		* Sometimes the iCubInterface gets stuck because it stops being able to communicate with some of the boards. It happened once on Mar. 21 2014 while the head seemed to be the limit of one of the joints. That joint was not actuated any more, while the others remained actuated. A similar problems seems to be happening on Vizzie.<br>
	[[Image:ChicoHeadCommunicationProblem.png\|300px]] Click on the image to see the high resolution version.<br>		[[Image:ChicoHeadCommunicationProblem.png\|300px]] Click on the image to see the high resolution version.<br>
	* Something can block one application (typically the terminal and gedit) for 10..20 seconds. ~~<span style="color:#FF0000">~~ (~~This might have been caused by~~ a ~~malfunctioning~~ board ~~for~~ the ~~facial expressions~~. ~~The problem is being investigated.)</span>~~		* Something can block one application (typically the terminal and gedit) or parts of the system for 10..20 seconds. The problem was worse when we had the old faulty facial expression board connected to the system, but persists now with the new board and persists even (possibly to a lesser extent), when such board is not connected to the system.
	The freezing seems to be triggered both by some disk read and write operations.		The freezing seems to be triggered both by some disk read and write operations.
	The system is still responsive, the affected application freezes, other applications can also freeze at that time if they need to access the disk (I suppose).		The system is still responsive, the affected application freezes, other applications can also freeze at that time if they need to access the disk (I suppose).
	It doesn't give problems to the demos once they have been started.		It doesn't give problems to the demos once they have been started.
	* It is common to get this USB-related error at boot time:		* It was common to get this USB-related error at boot time, after changing the facial expression board for the new one and using different USB cables/connection on PC104, the error doesn't appear any more:
	>>USB 3-2: device descriptor read/64, error -71		>>USB 3-2: device descriptor read/64, error -71
	>>device not accepting address 4, error -71		>>device not accepting address 4, error -71

Mtaiana: /* Demos */

2014-03-24T20:05:59Z

Demos

← Older revision		Revision as of 20:05, 24 March 2014
Line 30:		Line 30:
	* Scripts 1 and 2 start the YARP server and the iCubInterface (used for moving the robot).		* Scripts 1 and 2 start the YARP server and the iCubInterface (used for moving the robot).
	* Scripts 3_1..3_3 start the right camera, start a viewer and connect the two.		* Scripts 3_1..3_3 start the right camera, start a viewer and connect the two.
	* ~~<span style="color:#FF0000"> NOT WORKING AT THE MOMENT.</span>~~ Scripts 4_1..4_4 start the emotion system and cycle emotions in a fixed sequence.		* Scripts 4_1..4_4 start the emotion system and cycle emotions in a fixed sequence.
	* Script 6 moves the head and the eyes in a fixed sequence.		* Script 6 moves the head and the eyes in a fixed sequence.

	All of this was running together smoothly on Feb. 6 2014.<br>		All of this was running together smoothly on Feb. 6 2014.<br>
	On Mar. 21 2014 the facial expression system was not working at all. The YARP driver could not be initialized and the board emitted a weird sound when approached with a finger. Once the associated USB port was disconnected, the delays in accessing the USB stick ~~seemed to vanish~~. It is possible that the broken board was jamming the USB system.		On Mar. 21 2014 the facial expression system was not working at all. The YARP driver could not be initialized and the board emitted a weird sound when approached with a finger. Once the associated USB port was disconnected, the delays in accessing the USB stick greatly reduced. It is possible that the broken board was contributing to the known USB problems by jamming the USB system. <br>
			The board was substituted on Mar. 24 2014 and is now working smoothly. While we were at it, we also fixed the lower eyelid which was loose.

	==Known problems==		==Known problems==

Mtaiana at 15:07, 21 March 2014

2014-03-21T15:07:19Z

← Older revision		Revision as of 15:07, 21 March 2014
Line 47:		Line 47:
	* It is common to get this USB-related error at boot time:		* It is common to get this USB-related error at boot time:
	>>USB 3-2: device descriptor read/64, error -71		>>USB 3-2: device descriptor read/64, error -71
	>>device not accepting ~~addres~~ 4, error -71		>>device not accepting address 4, error -71
	>>device not accepting ~~addres~~ 5, error -71		>>device not accepting address 5, error -71
	After which the system booted normally.		After which the system booted normally.
	It seems to happen every time that the USB connector for the facial expression is connected to the board.		It seems to happen every time that the USB connector for the facial expression is connected to the board.
Line 88:		Line 88:
	*The demos work out of the box.		*The demos work out of the box.
	*The keyboard layout is Portuguese both for the real terminals and the X session.		*The keyboard layout is Portuguese both for the real terminals and the X session.
	*The browser doesn't write ~~chache~~ to the disk (freezing at almost every click)		*The browser doesn't write cache to the disk (freezing at almost every click)
	*The sources lists have been updated, so more packages can be installed.		*The sources lists have been updated, so more packages can be installed.
	*Added the readme file		*Added the readme file

Mtaiana at 15:06, 21 March 2014

2014-03-21T15:06:23Z

← Older revision		Revision as of 15:06, 21 March 2014
Line 54:		Line 54:
	Even if the system is started and run without the facial expression connector plugged in, the system still freezes.		Even if the system is started and run without the facial expression connector plugged in, the system still freezes.

	====USB ~~PEN DRIVE TEST~~====		====USB pen drive test====
	* I ran hdparm 4 times and got these results (with low variation):		* I ran hdparm 4 times and got these results (with low variation):
	$ sudo hdparm -tT /dev/sda		$ sudo hdparm -tT /dev/sda
Line 85:		Line 85:
	*Once the face detector+gaze demo was working on this platform. Maybe it could be restored with little effort.		*Once the face detector+gaze demo was working on this platform. Maybe it could be restored with little effort.

	==~~IMPROVEMENTS SINCE PREVIOUS IMAGE~~==		==Improvements since previous bootable image==
	*The demos work out of the box.		*The demos work out of the box.
	*The keyboard layout is Portuguese both for the real terminals and the X session.		*The keyboard layout is Portuguese both for the real terminals and the X session.

Mtaiana: /* Known problems */

2014-03-21T15:04:48Z

Known problems

← Older revision		Revision as of 15:04, 21 March 2014
Line 40:		Line 40:
	* Turning on the robot with a cable plugged into the ethernet connector in the head of the robot gets the system stuck. You can plug the cable in after boot and initialize the ethernet connection with: sudo dhclient eth0.		* Turning on the robot with a cable plugged into the ethernet connector in the head of the robot gets the system stuck. You can plug the cable in after boot and initialize the ethernet connection with: sudo dhclient eth0.
	* Sometimes the iCubInterface gets stuck because it stops being able to communicate with some of the boards. It happened once on Mar. 21 2014 while the head seemed to be the limit of one of the joints. That joint was not actuated any more, while the others remained actuated. A similar problems seems to be happening on Vizzie.<br>		* Sometimes the iCubInterface gets stuck because it stops being able to communicate with some of the boards. It happened once on Mar. 21 2014 while the head seemed to be the limit of one of the joints. That joint was not actuated any more, while the others remained actuated. A similar problems seems to be happening on Vizzie.<br>
	[[Image:ChicoHeadCommunicationProblem.png\|~~100px~~]]<br>		[[Image:ChicoHeadCommunicationProblem.png\|300px]] Click on the image to see the high resolution version.<br>
	* Something can block one application (typically the terminal and gedit) for 10..20 seconds. <span style="color:#FF0000"> (This might have been caused by a malfunctioning board for the facial expressions. The problem is being investigated.)</span>		* Something can block one application (typically the terminal and gedit) for 10..20 seconds. <span style="color:#FF0000"> (This might have been caused by a malfunctioning board for the facial expressions. The problem is being investigated.)</span>
	The freezing seems to be triggered both by some disk read and write operations.		The freezing seems to be triggered both by some disk read and write operations.

Mtaiana: /* Known problems */

2014-03-21T15:04:01Z

Known problems

← Older revision		Revision as of 15:04, 21 March 2014
Line 40:		Line 40:
	* Turning on the robot with a cable plugged into the ethernet connector in the head of the robot gets the system stuck. You can plug the cable in after boot and initialize the ethernet connection with: sudo dhclient eth0.		* Turning on the robot with a cable plugged into the ethernet connector in the head of the robot gets the system stuck. You can plug the cable in after boot and initialize the ethernet connection with: sudo dhclient eth0.
	* Sometimes the iCubInterface gets stuck because it stops being able to communicate with some of the boards. It happened once on Mar. 21 2014 while the head seemed to be the limit of one of the joints. That joint was not actuated any more, while the others remained actuated. A similar problems seems to be happening on Vizzie.<br>		* Sometimes the iCubInterface gets stuck because it stops being able to communicate with some of the boards. It happened once on Mar. 21 2014 while the head seemed to be the limit of one of the joints. That joint was not actuated any more, while the others remained actuated. A similar problems seems to be happening on Vizzie.<br>
	[[Image:ChicoHeadCommunicationProblem.png\|~~100pix~~]]<br>		[[Image:ChicoHeadCommunicationProblem.png\|100px]]<br>
	* Something can block one application (typically the terminal and gedit) for 10..20 seconds. <span style="color:#FF0000"> (This might have been caused by a malfunctioning board for the facial expressions. The problem is being investigated.)</span>		* Something can block one application (typically the terminal and gedit) for 10..20 seconds. <span style="color:#FF0000"> (This might have been caused by a malfunctioning board for the facial expressions. The problem is being investigated.)</span>
	The freezing seems to be triggered both by some disk read and write operations.		The freezing seems to be triggered both by some disk read and write operations.

Mtaiana: /* Known problems */

2014-03-21T15:03:37Z

Known problems

← Older revision		Revision as of 15:03, 21 March 2014
Line 40:		Line 40:
	* Turning on the robot with a cable plugged into the ethernet connector in the head of the robot gets the system stuck. You can plug the cable in after boot and initialize the ethernet connection with: sudo dhclient eth0.		* Turning on the robot with a cable plugged into the ethernet connector in the head of the robot gets the system stuck. You can plug the cable in after boot and initialize the ethernet connection with: sudo dhclient eth0.
	* Sometimes the iCubInterface gets stuck because it stops being able to communicate with some of the boards. It happened once on Mar. 21 2014 while the head seemed to be the limit of one of the joints. That joint was not actuated any more, while the others remained actuated. A similar problems seems to be happening on Vizzie.<br>		* Sometimes the iCubInterface gets stuck because it stops being able to communicate with some of the boards. It happened once on Mar. 21 2014 while the head seemed to be the limit of one of the joints. That joint was not actuated any more, while the others remained actuated. A similar problems seems to be happening on Vizzie.<br>
	[[Image:ChicoHeadCommunicationProblem.png]]<br>		[[Image:ChicoHeadCommunicationProblem.png\|100pix]]<br>
	* Something can block one application (typically the terminal and gedit) for 10..20 seconds. <span style="color:#FF0000"> (This might have been caused by a malfunctioning board for the facial expressions. The problem is being investigated.)</span>		* Something can block one application (typically the terminal and gedit) for 10..20 seconds. <span style="color:#FF0000"> (This might have been caused by a malfunctioning board for the facial expressions. The problem is being investigated.)</span>
	The freezing seems to be triggered both by some disk read and write operations.		The freezing seems to be triggered both by some disk read and write operations.

Mtaiana: /* readme.txt */

2014-03-21T15:01:08Z

readme.txt

Mtaiana: /* Known problems */

2014-03-21T14:58:08Z

Known problems

← Older revision		Revision as of 14:58, 21 March 2014
Line 39:		Line 39:
	* The ethernet adapter on the bottom of the robot does not work.		* The ethernet adapter on the bottom of the robot does not work.
	* Turning on the robot with a cable plugged into the ethernet connector in the head of the robot gets the system stuck. You can plug the cable in after boot and initialize the ethernet connection with: sudo dhclient eth0.		* Turning on the robot with a cable plugged into the ethernet connector in the head of the robot gets the system stuck. You can plug the cable in after boot and initialize the ethernet connection with: sudo dhclient eth0.
			* Sometimes the iCubInterface gets stuck because it stops being able to communicate with some of the boards. It happened once on Mar. 21 2014 while the head seemed to be the limit of one of the joints. That joint was not actuated any more, while the others remained actuated. A similar problems seems to be happening on Vizzie.

	* Something can block one application (typically the terminal and gedit) for 10..20 seconds. <span style="color:#FF0000"> (This might have been caused by a malfunctioning board for the facial expressions. The problem is being investigated.)</span>		* Something can block one application (typically the terminal and gedit) for 10..20 seconds. <span style="color:#FF0000"> (This might have been caused by a malfunctioning board for the facial expressions. The problem is being investigated.)</span>
	The freezing seems to be triggered both by some disk read and write operations.		The freezing seems to be triggered both by some disk read and write operations.

Mtaiana: /* Known problems */

2014-03-21T14:55:56Z

Known problems

← Older revision		Revision as of 14:55, 21 March 2014
Line 52:		Line 52:
	Even if the system is started and run without the facial expression connector plugged in, the system still freezes.		Even if the system is started and run without the facial expression connector plugged in, the system still freezes.

	USB PEN DRIVE TEST		====USB PEN DRIVE TEST====
	* I ran hdparm 4 times and got these results (with low variation):		* I ran hdparm 4 times and got these results (with low variation):
	$ sudo hdparm -tT /dev/sda		$ sudo hdparm -tT /dev/sda

← Older revision		Revision as of 15:01, 21 March 2014
Line 18:		Line 18:

	=readme.txt=		=readme.txt=
	~~This~~ is the content of the readme.txt file in the home directory of Chico head:		The remaining of this page is the content of the readme.txt file in the home directory of Chico head (That file is not updated, it was generated on Feb. 6 2014):

	Log in: like the one for the iCub		Log in: like the one for the iCub
Line 33:		Line 33:
	* Script 6 moves the head and the eyes in a fixed sequence.		* Script 6 moves the head and the eyes in a fixed sequence.

	All of this was running together smoothly on Feb. 6 2014.		All of this was running together smoothly on Feb. 6 2014.<br>
	On Mar. 21 2014 the facial expression system was not working at all. The YARP driver could not be initialized and the board emitted a weird sound when approached with a finger. Once the associated USB port was disconnected, the delays in accessing the USB stick seemed to vanish. It is possible that the broken board was jamming the USB system.		On Mar. 21 2014 the facial expression system was not working at all. The YARP driver could not be initialized and the board emitted a weird sound when approached with a finger. Once the associated USB port was disconnected, the delays in accessing the USB stick seemed to vanish. It is possible that the broken board was jamming the USB system.

Line 39:		Line 39:
	* The ethernet adapter on the bottom of the robot does not work.		* The ethernet adapter on the bottom of the robot does not work.
	* Turning on the robot with a cable plugged into the ethernet connector in the head of the robot gets the system stuck. You can plug the cable in after boot and initialize the ethernet connection with: sudo dhclient eth0.		* Turning on the robot with a cable plugged into the ethernet connector in the head of the robot gets the system stuck. You can plug the cable in after boot and initialize the ethernet connection with: sudo dhclient eth0.
	* Sometimes the iCubInterface gets stuck because it stops being able to communicate with some of the boards. It happened once on Mar. 21 2014 while the head seemed to be the limit of one of the joints. That joint was not actuated any more, while the others remained actuated. A similar problems seems to be happening on Vizzie.		* Sometimes the iCubInterface gets stuck because it stops being able to communicate with some of the boards. It happened once on Mar. 21 2014 while the head seemed to be the limit of one of the joints. That joint was not actuated any more, while the others remained actuated. A similar problems seems to be happening on Vizzie.<br>
			[[Image:ChicoHeadCommunicationProblem.png]]<br>
	* Something can block one application (typically the terminal and gedit) for 10..20 seconds. <span style="color:#FF0000"> (This might have been caused by a malfunctioning board for the facial expressions. The problem is being investigated.)</span>		* Something can block one application (typically the terminal and gedit) for 10..20 seconds. <span style="color:#FF0000"> (This might have been caused by a malfunctioning board for the facial expressions. The problem is being investigated.)</span>
	The freezing seems to be triggered both by some disk read and write operations.		The freezing seems to be triggered both by some disk read and write operations.