RobAIR2013-RICM4-Groupe1-Suivi - Revision history

Laurene.Guelorget: /* Solution suggested */

2013-04-12T09:45:19Z

Solution suggested

← Older revision		Revision as of 09:45, 12 April 2013
Line 58:		Line 58:
	* Finally, we connect the robot to the network.		* Finally, we connect the robot to the network.

	<br/>		<br/><br/>
	This process is implemented into a loop and is repeated at regular time intervals. If a WiFi network scanned is not in the database, the process restart with a reduced time lapse. If one interface is already connected to a WiFi network, then we try to connect the other interface. In any other case, we connect the interfaces in turn, one after the other. We save the SSID of the network on which an interface is connected in a variable so that we can't connect an interface to a WiFi network already used by the other interface.		This process is implemented into a loop and is repeated at regular time intervals. If a WiFi network scanned is not in the database, the process restart with a reduced time lapse. If one interface is already connected to a WiFi network, then we try to connect the other interface. In any other case, we connect the interfaces in turn, one after the other. We save the SSID of the network on which an interface is connected in a variable so that we can't connect an interface to a WiFi network already used by the other interface.
	<br/><br/>		<br/><br/>

Laurene.Guelorget: /* Solution suggested */

2013-04-12T09:45:12Z

Solution suggested

← Older revision		Revision as of 09:45, 12 April 2013
Line 60:		Line 60:
	<br/>		<br/>
	This process is implemented into a loop and is repeated at regular time intervals. If a WiFi network scanned is not in the database, the process restart with a reduced time lapse. If one interface is already connected to a WiFi network, then we try to connect the other interface. In any other case, we connect the interfaces in turn, one after the other. We save the SSID of the network on which an interface is connected in a variable so that we can't connect an interface to a WiFi network already used by the other interface.		This process is implemented into a loop and is repeated at regular time intervals. If a WiFi network scanned is not in the database, the process restart with a reduced time lapse. If one interface is already connected to a WiFi network, then we try to connect the other interface. In any other case, we connect the interfaces in turn, one after the other. We save the SSID of the network on which an interface is connected in a variable so that we can't connect an interface to a WiFi network already used by the other interface.
	<br/>		<br/><br/>

	=Progress of the project=		=Progress of the project=

Laurene.Guelorget: /* Solution suggested */

2013-04-12T09:45:05Z

Solution suggested

← Older revision		Revision as of 09:45, 12 April 2013
Line 60:		Line 60:
	<br/>		<br/>
	This process is implemented into a loop and is repeated at regular time intervals. If a WiFi network scanned is not in the database, the process restart with a reduced time lapse. If one interface is already connected to a WiFi network, then we try to connect the other interface. In any other case, we connect the interfaces in turn, one after the other. We save the SSID of the network on which an interface is connected in a variable so that we can't connect an interface to a WiFi network already used by the other interface.		This process is implemented into a loop and is repeated at regular time intervals. If a WiFi network scanned is not in the database, the process restart with a reduced time lapse. If one interface is already connected to a WiFi network, then we try to connect the other interface. In any other case, we connect the interfaces in turn, one after the other. We save the SSID of the network on which an interface is connected in a variable so that we can't connect an interface to a WiFi network already used by the other interface.
			<br/>

	=Progress of the project=		=Progress of the project=

Laurene.Guelorget: /* Solution suggested */

2013-04-12T09:44:51Z

Solution suggested

← Older revision		Revision as of 09:44, 12 April 2013
Line 52:		Line 52:
	[[File:program.png\|400px\|left\|thumb\|global functioning of our program]]		[[File:program.png\|400px\|left\|thumb\|global functioning of our program]]
	Our program follows several steps:		Our program follows several steps:
	* First, the program scans and searches for all available networks in range thanks to the iwlist UNIX command. The command iwlist allows us		* First, the program scans and searches for all available networks in range thanks to the iwlist UNIX command. The command iwlist allows us to view lots of information about a wireless card and its connectivity. We use the scan option which is a privileged operation (root only). This option gives us the list of Access Points and Ad-Hoc cells in range, and information about them (such as the SSID, quality, frequency, type of encoding, etc.).
	to view lots of information about a wireless card and its connectivity. We use the scan option which is a privileged operation (root only). This option gives us the list of Access Points and Ad-Hoc cells in range, and information about them (such as the SSID, quality, frequency, type of encoding, etc.).
	* After that, the program puts the SSID, the quality of the signal (the signal strength) and the index (an ID number to identify the WiFi network) in a file.		* After that, the program puts the SSID, the quality of the signal (the signal strength) and the index (an ID number to identify the WiFi network) in a file.
	* Then, by parsing this file, the list of available networks are ordered by signal strength into a data structure.		* Then, by parsing this file, the list of available networks are ordered by signal strength into a data structure.

Laurene.Guelorget: /* Solution suggested */

2013-04-12T09:44:18Z

Solution suggested

← Older revision		Revision as of 09:44, 12 April 2013
Line 50:		Line 50:
	To ensure that the robot stays connected at all time, we wrote a program in language C and we created several data structures to manage the WiFi networks. This program of WiFi roaming will be executed on the Ubuntu tablet that will be on the robot.		To ensure that the robot stays connected at all time, we wrote a program in language C and we created several data structures to manage the WiFi networks. This program of WiFi roaming will be executed on the Ubuntu tablet that will be on the robot.

	[[File:program.png\|400px\|left\|thumb\|~~Roaming~~ ~~process~~]]		[[File:program.png\|400px\|left\|thumb\|global functioning of our program]]
	Our program follows several steps:		Our program follows several steps:
	* First, the program scans and searches for all available networks in range thanks to the iwlist UNIX command. The command iwlist allows us		* First, the program scans and searches for all available networks in range thanks to the iwlist UNIX command. The command iwlist allows us
Line 59:		Line 59:
	* Finally, we connect the robot to the network.		* Finally, we connect the robot to the network.

			<br/>
	This process is implemented into a loop and is repeated at regular time intervals. If a WiFi network scanned is not in the database, the process restart with a reduced time lapse. If one interface is already connected to a WiFi network, then we try to connect the other interface. In any other case, we connect the interfaces in turn, one after the other. We save the SSID of the network on which an interface is connected in a variable so that we can't connect an interface to a WiFi network already used by the other interface.		This process is implemented into a loop and is repeated at regular time intervals. If a WiFi network scanned is not in the database, the process restart with a reduced time lapse. If one interface is already connected to a WiFi network, then we try to connect the other interface. In any other case, we connect the interfaces in turn, one after the other. We save the SSID of the network on which an interface is connected in a variable so that we can't connect an interface to a WiFi network already used by the other interface.

Laurene.Guelorget: /* Solution suggested */

2013-04-12T09:43:30Z

Solution suggested

← Older revision		Revision as of 09:43, 12 April 2013
Line 50:		Line 50:
	To ensure that the robot stays connected at all time, we wrote a program in language C and we created several data structures to manage the WiFi networks. This program of WiFi roaming will be executed on the Ubuntu tablet that will be on the robot.		To ensure that the robot stays connected at all time, we wrote a program in language C and we created several data structures to manage the WiFi networks. This program of WiFi roaming will be executed on the Ubuntu tablet that will be on the robot.

			[[File:program.png\|400px\|left\|thumb\|Roaming process]]

	Our program follows several steps:		Our program follows several steps:
	�* First, the program scans and searches for all available networks in range thanks to the iwlist UNIX command. The command iwlist allows us		* First, the program scans and searches for all available networks in range thanks to the iwlist UNIX command. The command iwlist allows us
	to view lots of information about a wireless card and its connectivity. We use the scan option which is a privileged operation (root only). This option gives us the list of Access Points and Ad-Hoc cells in range, and information about them (such as the SSID, quality, frequency, type of encoding, etc.).		to view lots of information about a wireless card and its connectivity. We use the scan option which is a privileged operation (root only). This option gives us the list of Access Points and Ad-Hoc cells in range, and information about them (such as the SSID, quality, frequency, type of encoding, etc.).
	* After that, the program puts the SSID, the quality of the signal (the signal strength) and the index (an ID number to identify the WiFi network) in a file.		* After that, the program puts the SSID, the quality of the signal (the signal strength) and the index (an ID number to identify the WiFi network) in a file.
	�* Then, by parsing this ~~�le~~, the list of available networks are ordered by signal strength into a data structure.		* Then, by parsing this file, the list of available networks are ordered by signal strength into a data structure.
	* Next, we compare the SSID to a database of past used and known networks to get the password for the WiFi network.		* Next, we compare the SSID to a database of past used and known networks to get the password for the WiFi network.
	�* Finally, we connect the robot to the network.		* Finally, we connect the robot to the network.

	This process is implemented into a loop and is repeated at regular time intervals. If a WiFi network scanned is not in the database, the process restart with a reduced time lapse. If one interface is already connected to a WiFi network, then we try to connect the other interface. In any other case, we connect the interfaces in turn, one after the other. We save the SSID of the network on which an interface is connected in a variable so that we can't connect an interface to a WiFi network already used by the other interface.		This process is implemented into a loop and is repeated at regular time intervals. If a WiFi network scanned is not in the database, the process restart with a reduced time lapse. If one interface is already connected to a WiFi network, then we try to connect the other interface. In any other case, we connect the interfaces in turn, one after the other. We save the SSID of the network on which an interface is connected in a variable so that we can't connect an interface to a WiFi network already used by the other interface.

Laurene.Guelorget: /* Material */

2013-04-12T09:42:55Z

Material

← Older revision		Revision as of 09:42, 12 April 2013
Line 46:		Line 46:
	For that, a congestion window is kept for each path. After that, the congestion management is the same as in classic TCP.		For that, a congestion window is kept for each path. After that, the congestion management is the same as in classic TCP.

			=Solution suggested=
	=Material=

	* 1 [[Lego_Mindstorm_NXT \| Lego Mindstorm NXT]] Robot
			To ensure that the robot stays connected at all time, we wrote a program in language C and we created several data structures to manage the WiFi networks. This program of WiFi roaming will be executed on the Ubuntu tablet that will be on the robot.
	* 2 Intel ExoPC Slate

	* 1 USB Sound card

	* 1 [[XBox_Kinect \| XBox Kinect]]
			Our program follows several steps:
	* 1 Lidar
			�* First, the program scans and searches for all available networks in range thanks to the iwlist UNIX command. The command iwlist allows us
	* 2 DIY stereoscopic cameras
			to view lots of information about a wireless card and its connectivity. We use the scan option which is a privileged operation (root only). This option gives us the list of Access Points and Ad-Hoc cells in range, and information about them (such as the SSID, quality, frequency, type of encoding, etc.).
			* After that, the program puts the SSID, the quality of the signal (the signal strength) and the index (an ID number to identify the WiFi network) in a file.
			�* Then, by parsing this �le, the list of available networks are ordered by signal strength into a data structure.
			* Next, we compare the SSID to a database of past used and known networks to get the password for the WiFi network.
			�* Finally, we connect the robot to the network.

			This process is implemented into a loop and is repeated at regular time intervals. If a WiFi network scanned is not in the database, the process restart with a reduced time lapse. If one interface is already connected to a WiFi network, then we try to connect the other interface. In any other case, we connect the interfaces in turn, one after the other. We save the SSID of the network on which an interface is connected in a variable so that we can't connect an interface to a WiFi network already used by the other interface.

	=Progress of the project=		=Progress of the project=

Laurene.Guelorget: /* WiFi roaming */

2013-04-12T09:39:37Z

WiFi roaming

← Older revision		Revision as of 09:39, 12 April 2013
Line 36:		Line 36:
	<br/>In this figure, we can see how roaming will work in our project. Our robot possesses two interfaces (wlan0 and wlan1) and at all time, it is connected to at least one Access Point. First, the robot is connected to the Router1 on wlan0. By moving, the robot receives signals from other Access Points. The Router2's signal is stronger so the robot connects its free interface (in this example, wlan1) to Router2. It can then disconnect itself from the Router1 Access Point. This process goes on as the robot moves around.		<br/>In this figure, we can see how roaming will work in our project. Our robot possesses two interfaces (wlan0 and wlan1) and at all time, it is connected to at least one Access Point. First, the robot is connected to the Router1 on wlan0. By moving, the robot receives signals from other Access Points. The Router2's signal is stronger so the robot connects its free interface (in this example, wlan1) to Router2. It can then disconnect itself from the Router1 Access Point. This process goes on as the robot moves around.

	<br/><br/><br/><br/><br/><br/><br/><br/><br/>		<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>

	==Multipath Transmission Control Protocol==		==Multipath Transmission Control Protocol==

Laurene.Guelorget: /* WiFi roaming */

2013-04-12T09:39:31Z

WiFi roaming

← Older revision		Revision as of 09:39, 12 April 2013
Line 34:		Line 34:

	[[File:roaming.png\|400px\|left\|thumb\|Roaming process]]		[[File:roaming.png\|400px\|left\|thumb\|Roaming process]]
	<br/>In ~~the~~ figure ~~above~~, we can see how roaming will work in our project. Our robot possesses two interfaces (wlan0 and wlan1) and at all time, it is connected to at least one Access Point. First, the robot is connected to the Router1 on wlan0. By moving, the robot receives signals from other Access Points. The Router2's signal is stronger so the robot connects its free interface (in this example, wlan1) to Router2. It can then disconnect itself from the Router1 Access Point. This process goes on as the robot moves around.		<br/>In this figure, we can see how roaming will work in our project. Our robot possesses two interfaces (wlan0 and wlan1) and at all time, it is connected to at least one Access Point. First, the robot is connected to the Router1 on wlan0. By moving, the robot receives signals from other Access Points. The Router2's signal is stronger so the robot connects its free interface (in this example, wlan1) to Router2. It can then disconnect itself from the Router1 Access Point. This process goes on as the robot moves around.

	<br/><br/><br/><br/><br/><br/><br/><br/>		<br/><br/><br/><br/><br/><br/><br/><br/><br/>

	==Multipath Transmission Control Protocol==		==Multipath Transmission Control Protocol==

Laurene.Guelorget: /* WiFi roaming */

2013-04-12T09:39:18Z

WiFi roaming

← Older revision		Revision as of 09:39, 12 April 2013
Line 34:		Line 34:

	[[File:roaming.png\|400px\|left\|thumb\|Roaming process]]		[[File:roaming.png\|400px\|left\|thumb\|Roaming process]]
	In the figure above, we can see how roaming will work in our project. Our robot possesses two interfaces (wlan0 and wlan1) and at all time, it is connected to at least one Access Point. First, the robot is connected to the Router1 on wlan0. By moving, the robot receives signals from other Access Points. The Router2's signal is stronger so the robot connects its free interface (in this example, wlan1) to Router2. It can then disconnect itself from the Router1 Access Point. This process goes on as the robot moves around.		<br/>In the figure above, we can see how roaming will work in our project. Our robot possesses two interfaces (wlan0 and wlan1) and at all time, it is connected to at least one Access Point. First, the robot is connected to the Router1 on wlan0. By moving, the robot receives signals from other Access Points. The Router2's signal is stronger so the robot connects its free interface (in this example, wlan1) to Router2. It can then disconnect itself from the Router1 Access Point. This process goes on as the robot moves around.

	<br/><br/><br/>		<br/><br/><br/><br/><br/><br/><br/><br/>

	==Multipath Transmission Control Protocol==		==Multipath Transmission Control Protocol==