Proj-2015-2016-IndoorGeoloc/Fiche - Revision history

Imad-Seddik.Arrada: /* Week 12 (March 28th - April 3th) */

2016-04-10T16:59:25Z

Week 12 (March 28th - April 3th)

← Older revision		Revision as of 16:59, 10 April 2016
Line 69:		Line 69:

	== Week 12 (March 28th - April 3th) ==		== Week 12 (March 28th - April 3th) ==
	* Android : At this state everything seems to be working, we try to have a better layout of the application and to work on the features.		* Android : At this state everything seems to be working, we try to have a better layout of the application and to work on the features. Looking for how to incorporate indoors map generated manually (thinking of getting official plan of buildings digitalized with MapTiler)
	* Beacon emission : We found out that the currently used STM32f446 bluetooth shield isn't working because it isn't correctly connected. The pins aren't identical, that's why the program won't run. We have to change the boards, so we must get : STM32f401		* Beacon emission : We found out that the currently used STM32f446 bluetooth shield isn't working because it isn't correctly connected. The pins aren't identical, that's why the program won't run. We have to change the boards, so we must get : STM32f401
	* Server (beacon side) : Need to have the androids clients to know which devices can be located, so we need to send them the list of the beacon. This list is generated from the history database. and send to the client via HTTP request. A table of the location of the board is created.		* Server (beacon side) : Need to have the androids clients to know which devices can be located, so we need to send them the list of the beacon. This list is generated from the history database. and send to the client via HTTP request. A table of the location of the board is created.

Imad-Seddik.Arrada: /* Week 13 (April 4th - April 10th) */

2016-04-10T16:57:36Z

Week 13 (April 4th - April 10th)

← Older revision		Revision as of 16:57, 10 April 2016
Line 75:		Line 75:

	== Week 13 (April 4th - April 10th) ==		== Week 13 (April 4th - April 10th) ==

			We start to prepare the final presentation, some parts of the project are still unfinished but we try to get it done before the due date. We try to have tests to show and the report written by the dealine. Everything is quite rushed so we can't really focus on a single problem all at once.
			The test of the presentation consists of showing the detection of a beacon in the room containing three detecting boards. The database where the computed location of the beacon is displayed on the screen. And showing the rendering of beacons locations on the android app. We will also show the indoors map realised thanks to the evacuation plan given by the admninstration of Polytech.

Imad-Seddik.Arrada: /* Week 12 (March 28th - April 3th) */

2016-04-10T16:50:11Z

Week 12 (March 28th - April 3th)

← Older revision		Revision as of 16:50, 10 April 2016
Line 72:		Line 72:
	* Beacon emission : We found out that the currently used STM32f446 bluetooth shield isn't working because it isn't correctly connected. The pins aren't identical, that's why the program won't run. We have to change the boards, so we must get : STM32f401		* Beacon emission : We found out that the currently used STM32f446 bluetooth shield isn't working because it isn't correctly connected. The pins aren't identical, that's why the program won't run. We have to change the boards, so we must get : STM32f401
	* Server (beacon side) : Need to have the androids clients to know which devices can be located, so we need to send them the list of the beacon. This list is generated from the history database. and send to the client via HTTP request. A table of the location of the board is created.		* Server (beacon side) : Need to have the androids clients to know which devices can be located, so we need to send them the list of the beacon. This list is generated from the history database. and send to the client via HTTP request. A table of the location of the board is created.
	* Server (android side) : Facing material difficulties, the eclipse project won't recognize some packages of the project. This delayed the completion of the ~~project~~.		* Server (android side) : Facing material difficulties, the eclipse project won't recognize some packages of the project. This delayed the completion of the mqtt part. Thinking of using another method of send data since the deadline is approaching.

	== Week 13 (April 4th - April 10th) ==		== Week 13 (April 4th - April 10th) ==

Imad-Seddik.Arrada: /* Week 12 (March 28th - April 3th) */

2016-04-10T16:48:58Z

Week 12 (March 28th - April 3th)

← Older revision		Revision as of 16:48, 10 April 2016
Line 70:		Line 70:
	== Week 12 (March 28th - April 3th) ==		== Week 12 (March 28th - April 3th) ==
	* Android : At this state everything seems to be working, we try to have a better layout of the application and to work on the features.		* Android : At this state everything seems to be working, we try to have a better layout of the application and to work on the features.
	Beacon emission : We found out that the currently used STM32f446 bluetooth shield isn't working because it isn't correctly connected. The pins aren't identical, that's why the program won't run. We have to change the boards, so we must get : STM32f401		* Beacon emission : We found out that the currently used STM32f446 bluetooth shield isn't working because it isn't correctly connected. The pins aren't identical, that's why the program won't run. We have to change the boards, so we must get : STM32f401
	Server (beacon side) : Need to have the androids clients to know which devices can be located, so we need to send them the list of the beacon. This list is generated from the history database. and send to the client via HTTP request. A table of the location of the board is created.		* Server (beacon side) : Need to have the androids clients to know which devices can be located, so we need to send them the list of the beacon. This list is generated from the history database. and send to the client via HTTP request. A table of the location of the board is created.
	Server (android side) : Facing material difficulties, the eclipse project won't recognize some packages of the project. This delayed the completion of the project.		* Server (android side) : Facing material difficulties, the eclipse project won't recognize some packages of the project. This delayed the completion of the project.

	== Week 13 (April 4th - April 10th) ==		== Week 13 (April 4th - April 10th) ==

Imad-Seddik.Arrada: /* Week 12 (March 28th - April 3th) */

2016-04-10T16:48:36Z

Week 12 (March 28th - April 3th)

← Older revision		Revision as of 16:48, 10 April 2016
Line 70:		Line 70:
	== Week 12 (March 28th - April 3th) ==		== Week 12 (March 28th - April 3th) ==
	* Android : At this state everything seems to be working, we try to have a better layout of the application and to work on the features.		* Android : At this state everything seems to be working, we try to have a better layout of the application and to work on the features.
			Beacon emission : We found out that the currently used STM32f446 bluetooth shield isn't working because it isn't correctly connected. The pins aren't identical, that's why the program won't run. We have to change the boards, so we must get : STM32f401
			Server (beacon side) : Need to have the androids clients to know which devices can be located, so we need to send them the list of the beacon. This list is generated from the history database. and send to the client via HTTP request. A table of the location of the board is created.
			Server (android side) : Facing material difficulties, the eclipse project won't recognize some packages of the project. This delayed the completion of the project.

	== Week 13 (April 4th - April 10th) ==		== Week 13 (April 4th - April 10th) ==

Imad-Seddik.Arrada: /* Week 11 (March 21th - March 27th) */

2016-04-10T16:30:34Z

Week 11 (March 21th - March 27th)

← Older revision		Revision as of 16:30, 10 April 2016
Line 66:		Line 66:
	* Android : Research on how to parse the location file received from the server.		* Android : Research on how to parse the location file received from the server.
	* Server (beacon side) : Creating the database storing the positions. Having some tests positions, trying to figure out how to restrain the number of position in the database. Creating another one to store the most recent ones ?		* Server (beacon side) : Creating the database storing the positions. Having some tests positions, trying to figure out how to restrain the number of position in the database. Creating another one to store the most recent ones ?
	* Server (android side) : Encountering some problems with the libraries. Some are really incomplete, we gave up the idea of using the mosquitto library. Paho seems to be functionning on our small tests. Still needs to be ~~incorporate~~ in the project.		* Server (android side) : Encountering some problems with the libraries. Some are really incomplete, we gave up the idea of using the mosquitto library. Paho seems to be functionning on our small tests. Still needs to be incorporated in the project.

	== Week 12 (March 28th - April 3th) ==		== Week 12 (March 28th - April 3th) ==

Imad-Seddik.Arrada: /* Week 11 (March 21th - March 27th) */

2016-04-10T16:30:14Z

Week 11 (March 21th - March 27th)

← Older revision		Revision as of 16:30, 10 April 2016
Line 65:		Line 65:
	* Beacon emission : We work on the correction of the detection and the weight of the signals. Trying to add a function resetting the list of detected beacons in order to reduce the quotity of message to one per beacon (T_Time_Out). Check if after second scan with TimeOut we get data in less time if there is only one device.		* Beacon emission : We work on the correction of the detection and the weight of the signals. Trying to add a function resetting the list of detected beacons in order to reduce the quotity of message to one per beacon (T_Time_Out). Check if after second scan with TimeOut we get data in less time if there is only one device.
	* Android : Research on how to parse the location file received from the server.		* Android : Research on how to parse the location file received from the server.
			* Server (beacon side) : Creating the database storing the positions. Having some tests positions, trying to figure out how to restrain the number of position in the database. Creating another one to store the most recent ones ?
	* Server (beacon side) :
			* Server (android side) : Encountering some problems with the libraries. Some are really incomplete, we gave up the idea of using the mosquitto library. Paho seems to be functionning on our small tests. Still needs to be incorporate in the project.
	* Server (android side) :

	== Week 12 (March 28th - April 3th) ==		== Week 12 (March 28th - April 3th) ==

Imad-Seddik.Arrada: /* Week 10 (March 14th - March 20th) */

2016-04-10T16:25:34Z

Week 10 (March 14th - March 20th)

← Older revision		Revision as of 16:25, 10 April 2016
Line 60:		Line 60:
	* Android : Looking for similar projects such as OpenLevelUp. We were thinking of using the same structure of file to describe a building. Some projects are likely to help us develop our app : [[https://github.com/HugoBA/GeoDrawerAndroid\|GeoDrawerAndroid]]. The following libraries are used : [[https://github.com/mapsforge/mapsforge\|OSMDroid]], [[https://github.com/MKergall/osmbonuspack\|OSMBonusPack]]		* Android : Looking for similar projects such as OpenLevelUp. We were thinking of using the same structure of file to describe a building. Some projects are likely to help us develop our app : [[https://github.com/HugoBA/GeoDrawerAndroid\|GeoDrawerAndroid]]. The following libraries are used : [[https://github.com/mapsforge/mapsforge\|OSMDroid]], [[https://github.com/MKergall/osmbonuspack\|OSMBonusPack]]
	* server (beacon side) : Working on how to transform the data and how to store them on a distant server, we have been advised to lend one from an amazon-server : [[https://aws.amazon.com/fr/\|amazon-server]]. This way we could try executing more realistic tests.		* server (beacon side) : Working on how to transform the data and how to store them on a distant server, we have been advised to lend one from an amazon-server : [[https://aws.amazon.com/fr/\|amazon-server]]. This way we could try executing more realistic tests.
	* server (android side) : Studying the libraries proposed by Mosquitto and Paho (for the clients). Mosquitto seems to be designed ~~for~~ only server use.		* server (android side) : Studying the libraries proposed by Mosquitto and Paho (for the clients). Mosquitto seems to be designed only for server use. Trying to get some tests to work.

	== Week 11 (March 21th - March 27th) ==		== Week 11 (March 21th - March 27th) ==

Imad-Seddik.Arrada at 10:34, 6 April 2016

2016-04-06T10:34:07Z

← Older revision		Revision as of 10:34, 6 April 2016
Line 48:		Line 48:
	* Beacon emission : board receives BLE packets (sorting them between different MAC addresses) and then computes the ratio of signal strengh over signal average strengh.		* Beacon emission : board receives BLE packets (sorting them between different MAC addresses) and then computes the ratio of signal strengh over signal average strengh.
	* Server (beacon side) : allow the transmission of data (in a raw state) to the server which will compute the distance according to the RSSI formula		* Server (beacon side) : allow the transmission of data (in a raw state) to the server which will compute the distance according to the RSSI formula
	* Server (android side) : Development of the MQTT server sending position to the Android clients		* Server (android side) : Development of the MQTT server sending position to the Android clients [[ http://dalelane.co.uk/blog/?p=1599\|MQTT server]]
	* Android : we found that the Android library OSMDroid might help us doing the rendering of a map on smartphones. Using leaflet could also help us empiling multiple objects		* Android : we found that the Android library OSMDroid might help us doing the rendering of a map on smartphones. Using leaflet could also help us empiling multiple objects

	== Week 9 (March 7th - March 13th) ==		== Week 9 (March 7th - March 13th) ==
	Presentation support : [[File:Mi_parcours.pdf]]		Presentation support : [[File:Mi_parcours.pdf]]
			<br />
	Preparation of the presentation.		Preparation of the presentation.

	== Week 10 (March 14th - March 20th) ==		== Week 10 (March 14th - March 20th) ==
			* Beacon emission : Research on compilation STM32.
	* Android : Looking for similar project such as OpenLevelUp. We were thinking of using the same structure of file to describe a building.
			* Android : Looking for similar projects such as OpenLevelUp. We were thinking of using the same structure of file to describe a building. Some projects are likely to help us develop our app : [[https://github.com/HugoBA/GeoDrawerAndroid\|GeoDrawerAndroid]]. The following libraries are used : [[https://github.com/mapsforge/mapsforge\|OSMDroid]], [[https://github.com/MKergall/osmbonuspack\|OSMBonusPack]]
			* server (beacon side) : Working on how to transform the data and how to store them on a distant server, we have been advised to lend one from an amazon-server : [[https://aws.amazon.com/fr/\|amazon-server]]. This way we could try executing more realistic tests.
			* server (android side) : Studying the libraries proposed by Mosquitto and Paho (for the clients). Mosquitto seems to be designed for only server use.

	== Week 11 (March 21th - March 27th) ==		== Week 11 (March 21th - March 27th) ==
			* Beacon emission : We work on the correction of the detection and the weight of the signals. Trying to add a function resetting the list of detected beacons in order to reduce the quotity of message to one per beacon (T_Time_Out). Check if after second scan with TimeOut we get data in less time if there is only one device.
			* Android : Research on how to parse the location file received from the server.
			* Server (beacon side) :
			* Server (android side) :

	== Week 12 (March 28th - April 3th) ==		== Week 12 (March 28th - April 3th) ==
			* Android : At this state everything seems to be working, we try to have a better layout of the application and to work on the features.

	== Week 13 (April 4th - April 10th) ==		== Week 13 (April 4th - April 10th) ==

Imad-Seddik.Arrada at 15:37, 5 April 2016

2016-04-05T15:37:34Z

@@ Line 41: / Line 41: @@
 * Beacon emission : board receives BLE packets (sorting them between different MAC addresses) and then computes the ratio of signal strengh over signal average strengh.
-* Server (android side) : /TODO
+* Server (android side) : Development of the MQTT server sending position to the Android clients
 == Week 8 (February 29th - March 6th) ==
 == Week 9 (March 7th - March 13th) ==
 Presentation support : [[File:Mi_parcours.pdf]]