Data Logger - Revision history

Openuas at 10:48, 25 January 2018

2018-01-25T10:48:36Z

← Older revision		Revision as of 04:48, 25 January 2018
Line 21:		Line 21:
	==* [[SDLogger_SPI_Direct\|SD Logger SPI Direct]]==		==* [[SDLogger_SPI_Direct\|SD Logger SPI Direct]]==
	==* [[Micro_logger\|Micro Logger]]==		==* [[Micro_logger\|Micro Logger]]==
	==* [[file_logger\|File Logger (~~Bebop~~)]]==		==* [[file_logger\|File Logger (Parrot Drones)]]==
	==* [[Apogee/v1.00#On-board_Data_Logging\|On-board data logger for Apogee autopilot]]==		==* [[Apogee/v1.00#On-board_Data_Logging\|On-board data logger for Apogee autopilot]]==
	==* [[Openlog\|Openlog]]==		==* [[Openlog\|Openlog]]==

Ghattenb at 16:22, 11 January 2017

2017-01-11T16:22:54Z

← Older revision		Revision as of 10:22, 11 January 2017
Line 3:		Line 3:
	This page describes various '''onboard''' external devices called a "Data logger", that can be connected to the Paparazzi autopilot.		This page describes various '''onboard''' external devices called a "Data logger", that can be connected to the Paparazzi autopilot.

	Such a Data Logger device can be used to store telemetry data to a storage medium on board the aircraft. Such a storage medium can be an SD card or a Flash chip. ~~For now logging is '''not'''~~ done ~~directly~~ by the autopilot itself ~~as the usage of~~ a file system ~~as well as possible lag you might get with a SD storage speed does not fit well~~ with the ~~real-time nature of Autopilots~~.		Such a Data Logger device can be used to store telemetry data to a storage medium on board the aircraft. Such a storage medium can be an SD card or a Flash chip. Logging can eventually be done by the autopilot itself if it is using a (RT)OS and can eventually handle a file system without interfering with the control and navigation tasks.

	Note that not all loggers accept SD HighCapacity(SDHC) cards as storage		Note that not all loggers accept SD HighCapacity(SDHC) cards as storage
Line 11:		Line 11:
	One would naturally first ask; why on on-board logger when we have data over the air?		One would naturally first ask; why on on-board logger when we have data over the air?

	The answer to this is multi-fold; Sometimes it is not possible to log everything over the air because of speed, lag and ~~datavolume~~ limitations of data send wireless over the air. Or one needs to log when there is no telemetry at all in long distance flight. Or one want to log all the RAW IMU data to debug specific scenarios.		The answer to this is multi-fold; Sometimes it is not possible to log everything over the air because of speed, lag and volume limitations of data send wireless over the air. Or one needs to log when there is no telemetry at all in long distance flight. Or one want to log all the RAW IMU data to debug specific scenarios.

	To solve this issue, there are various loggers that can be connected to your Paparazzi Autopilot board.		To solve this issue, there are various loggers that can be connected to your Paparazzi Autopilot board.
Line 19:		Line 19:
	There are numerous logging solutions, both with their pro's and con's; here the options:		There are numerous logging solutions, both with their pro's and con's; here the options:

	~~==* [[twoga-Logga\|TWOGA-Logga]]==~~
	~~==* [[twoglogdedicated\|An dedicated TWOG board for logging]]==~~
	~~==* [[Openlog\|Openlog]]==~~
	==* [[SDLogger_SPI_Direct\|SD Logger SPI Direct]]==		==* [[SDLogger_SPI_Direct\|SD Logger SPI Direct]]==
	==* [[Micro_logger\|Micro Logger]]==		==* [[Micro_logger\|Micro Logger]]==
	==* [[file_logger\|File Logger (Bebop)]]==		==* [[file_logger\|File Logger (Bebop)]]==
			==* [[Apogee/v1.00#On-board_Data_Logging\|On-board data logger for Apogee autopilot]]==
			==* [[Openlog\|Openlog]]==
			==* [[twoga-Logga\|TWOGA-Logga]]==
			==* [[twoglogdedicated\|An dedicated TWOG board for logging]]==

	=Storage format=		=Storage format=

Ewoud at 18:35, 23 August 2016

2016-08-23T18:35:31Z

@@ Line 24: / Line 24: @@
 ==* [[SDLogger_SPI_Direct|SD Logger SPI Direct]]==
 ==* [[Micro_logger|Micro Logger]]==
 =Storage format=
 A more unified method of storing data on the logger, [[Messages_Format#Telemetry_storage_format_for_data_logger|info available here]]
 [[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]]

DaanHoppener at 17:24, 23 August 2016

2016-08-23T17:24:04Z

← Older revision		Revision as of 11:24, 23 August 2016
Line 62:		Line 62:

	'''Step 4:'''		'''Step 4:'''
	~~Firs~~, make sure that your Parrot Bebop is on, and connected. Now the logged .csv files can be retrieved from the Bebop. This is done by opening a browser, and typing <tt> ftp://196.168.42.1/ </tt> in the navigation line. This will take you to the ftp folder on the Bebop. Browse to <tt> /Internal000/ </tt>. Here we can find the <tt>.csv </tt>files, named 00000.csv to <tt> 0000X.csv </tt> depending on the flights you logged. Copy the files to your computer for analysis.		First, make sure that your Parrot Bebop is on, and connected. Now the logged .csv files can be retrieved from the Bebop. This is done by opening a browser, and typing <tt> ftp://196.168.42.1/ </tt> in the navigation line. This will take you to the ftp folder on the Bebop. Browse to <tt> /Internal000/ </tt>. Here we can find the <tt>.csv </tt>files, named 00000.csv to <tt> 0000X.csv </tt> depending on the flights you logged. Copy the files to your computer for analysis.

	[[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]]		[[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]]

DaanHoppener at 17:22, 23 August 2016

2016-08-23T17:22:55Z

← Older revision		Revision as of 11:22, 23 August 2016
Line 62:		Line 62:

	'''Step 4:'''		'''Step 4:'''
	~~Finally~~, the logged .csv files can be retrieved from the Bebop. This is done by opening a browser, and typing <tt> ftp://196.168.42.1/ </tt> in the navigation line. This will take you to the ftp folder on the Bebop. Browse to <tt> /Internal000/ </tt>. Here we can find the <tt>.csv </tt>files, named 00000.csv to <tt> 0000X.csv </tt> depending on the flights you logged. Copy the files to your computer for analysis		Firs, make sure that your Parrot Bebop is on, and connected. Now the logged .csv files can be retrieved from the Bebop. This is done by opening a browser, and typing <tt> ftp://196.168.42.1/ </tt> in the navigation line. This will take you to the ftp folder on the Bebop. Browse to <tt> /Internal000/ </tt>. Here we can find the <tt>.csv </tt>files, named 00000.csv to <tt> 0000X.csv </tt> depending on the flights you logged. Copy the files to your computer for analysis.

	[[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]]		[[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]]

DaanHoppener at 17:19, 23 August 2016

2016-08-23T17:19:48Z

← Older revision		Revision as of 11:19, 23 August 2016
Line 61:		Line 61:
	[[File:Bebop logs.png\|frameless\|Enable data logging in the GCS.]]		[[File:Bebop logs.png\|frameless\|Enable data logging in the GCS.]]

	'''Step 3:'''		'''Step 4:'''
	Finally, the logged .csv files can be retrieved from the Bebop. This is done by opening a browser, and typing <tt> ftp://196.168.42.1/ </tt> in the navigation line. This will take you to the ftp folder on the Bebop. Browse to <tt> /Internal000/ </tt>. Here we can find the <tt>.csv </tt>files, named 00000.csv to <tt> 0000X.csv </tt> depending on the flights you logged. Copy the files to your computer for analysis		Finally, the logged .csv files can be retrieved from the Bebop. This is done by opening a browser, and typing <tt> ftp://196.168.42.1/ </tt> in the navigation line. This will take you to the ftp folder on the Bebop. Browse to <tt> /Internal000/ </tt>. Here we can find the <tt>.csv </tt>files, named 00000.csv to <tt> 0000X.csv </tt> depending on the flights you logged. Copy the files to your computer for analysis

	[[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]]		[[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]]

DaanHoppener: Description added on how to enable internal data logging on the Parrot Bebop.

2016-08-23T17:18:35Z

Description added on how to enable internal data logging on the Parrot Bebop.

← Older revision		Revision as of 11:18, 23 August 2016
Line 28:		Line 28:

	A more unified method of storing data on the logger, [[Messages_Format#Telemetry_storage_format_for_data_logger\|info available here]]		A more unified method of storing data on the logger, [[Messages_Format#Telemetry_storage_format_for_data_logger\|info available here]]

			=Logging Data on the Parrot Bebop=

			Logging data onboard on the Bebop is pretty straight forward, as long as someone takes the time to tell you how. In this case, this guide will have to do. The Bebop drone is equipped with onboard storage, which we use to store the logs.

			'''Step 1:'''
			First, open your <tt> airframe.xml </tt> file (for example in <tt> paparazzi/conf/airframes/TUDELFT/ </tt>). Make sure that under modules, the following lines are uncommented or included: (only <tt> <module name="logger_file"> <define name="FILE_LOGGER_PATH" value="/data/ftp/internal_000"/> </tt> have to be included).

			<source lang="xml">
			<modules main_freq="512">
			<module name="geo_mag"/>
			<module name="air_data"/>
			<module name="send_imu_mag_current"/>
			<module name="logger_file">
			<define name="FILE_LOGGER_PATH" value="/data/ftp/internal_000"/>
			</module>
			</modules>
			</source>

			'''Step 2:'''
			In your logger file include the headers within paparazzi which contain the variables which you would like to log. This is done in the logger c file in <tt> paparazzi/sw/airborne/modules/loggers/file_logger.c </tt>. In this case I want to log data from <tt> stabilization_indi.c </tt>, so the following header should be included:

			<source lang="c">
			#include "firmwares/rotorcraft/stabilization/stabilization_indi.h"
			</source>

			In the file <tt> file_logger.c </tt> you can specify which variables you want to have logged in the same fashion as normal "printf's" would work. The variable names and the variable types (float, int etc.) have to be specified.

			'''Step 3:'''
			Start and stop the file logger by going to the paparazzi ground control station. Then go to > Settings > Modules. Here you can start and stop a log. This is displayed in the picture below:

			[[File:Bebop logs.png\|frameless\|Enable data logging in the GCS.]]

			'''Step 3:'''
			Finally, the logged .csv files can be retrieved from the Bebop. This is done by opening a browser, and typing <tt> ftp://196.168.42.1/ </tt> in the navigation line. This will take you to the ftp folder on the Bebop. Browse to <tt> /Internal000/ </tt>. Here we can find the <tt>.csv </tt>files, named 00000.csv to <tt> 0000X.csv </tt> depending on the flights you logged. Copy the files to your computer for analysis

	[[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]]		[[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]]

Openuas: /* Introduction */

2015-11-19T15:25:35Z

Introduction

← Older revision		Revision as of 09:25, 19 November 2015
Line 1:		Line 1:
	=Introduction=		=Introduction=

	This page describes various onboard external devices called a "Data logger", that can be connected to the Paparazzi autopilot.		This page describes various '''onboard''' external devices called a "Data logger", that can be connected to the Paparazzi autopilot.

	Such a Data Logger device can be used to store telemetry data to a storage medium on board the aircraft. Such a storage medium can be an SD card or a Flash chip. For now logging is '''not''' done directly by the autopilot itself as the usage of a file system as well as possible lag you might get with a SD storage speed does not fit well with the real-time nature of Autopilots.		Such a Data Logger device can be used to store telemetry data to a storage medium on board the aircraft. Such a storage medium can be an SD card or a Flash chip. For now logging is '''not''' done directly by the autopilot itself as the usage of a file system as well as possible lag you might get with a SD storage speed does not fit well with the real-time nature of Autopilots.

Openuas at 15:25, 19 November 2015

2015-11-19T15:25:07Z

← Older revision		Revision as of 09:25, 19 November 2015
Line 13:		Line 13:
	The answer to this is multi-fold; Sometimes it is not possible to log everything over the air because of speed, lag and datavolume limitations of data send wireless over the air. Or one needs to log when there is no telemetry at all in long distance flight. Or one want to log all the RAW IMU data to debug specific scenarios.		The answer to this is multi-fold; Sometimes it is not possible to log everything over the air because of speed, lag and datavolume limitations of data send wireless over the air. Or one needs to log when there is no telemetry at all in long distance flight. Or one want to log all the RAW IMU data to debug specific scenarios.

	To solve this issue, there are various loggers that can be connected to your Paparazzi Autopilot board~~. A short overview can be found on this page~~.		To solve this issue, there are various loggers that can be connected to your Paparazzi Autopilot board.

	=Available Data logger options=		=Available Data logger options=

			There are numerous logging solutions, both with their pro's and con's; here the options:

	==* [[twoga-Logga\|TWOGA-Logga]]==		==* [[twoga-Logga\|TWOGA-Logga]]==
	==* [[twoglogdedicated\|An dedicated TWOG board for logging]]==		==* [[twoglogdedicated\|An dedicated TWOG board for logging]]==
	==* [[Openlog\|Openlog]]==		==* [[Openlog\|Openlog]]==
	==* [SDLogger_SPI_Direct\|SD Logger SPI Direct]==		==* [[SDLogger_SPI_Direct\|SD Logger SPI Direct]]==
	==* [Micro_logger\|Micro Logger]==		==* [[Micro_logger\|Micro Logger]]==

			=Storage format=

	~~https://wiki.paparazziuav.org/wiki/~~Messages_Format#Telemetry_storage_format_for_data_logger		A more unified method of storing data on the logger, [[Messages_Format#Telemetry_storage_format_for_data_logger\|info available here]]

	[[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]]		[[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]]

Openuas at 15:20, 19 November 2015

2015-11-19T15:20:10Z

@@ Line 17: / Line 17: @@
 =Available Data logger options=
-==[[twoga-Logga|TWOGA-Logga]]==
+==* [[twoga-Logga|TWOGA-Logga]]==
-==[[twoglogdedicated|An dedicated TWOG board for logging]]==
+==* [[twoglogdedicated|An dedicated TWOG board for logging]]==
-==[[Openlog|Openlog]]==
+==* [[Openlog|Openlog]]==
+==* [SDLogger_SPI_Direct|SD Logger SPI Direct]==
-There is also direct support for the Sparkfun [http://www.sparkfun.com/products/10216 Logomatic V2.6] board,
+==* [Micro_logger|Micro Logger]==
 https://wiki.paparazziuav.org/wiki/Messages_Format#Telemetry_storage_format_for_data_logger
 [[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]]