Micro logger - Revision history

IHaveADrone: typos

2015-08-18T14:50:04Z

typos

← Older revision		Revision as of 08:50, 18 August 2015
Line 19:		Line 19:
	=How to use it=		=How to use it=
	==Configuration of the module==		==Configuration of the module==
	To configure the messages you want to log, you will need to ~~edite~~ the module c file in : sw/airborne/modules/loggers/high_speed_logger_direct_memory.c. At the top of the file you will have a section containing all the parameters that you can change. Among those you got :		To configure the messages you want to log, you will need to edit the module c file in : sw/airborne/modules/loggers/high_speed_logger_direct_memory.c. At the top of the file you will have a section containing all the parameters that you can change. Among those you got :
	* ERASE_MEMORY_AT_START : if set to 1 the memory will be erased completly when starting a new log. This will take a little bit less than a minute, but afterwards you will be able to log values at a higher rate than if you didn't do it. If you let it to 0, the module is going to erase the memory block by block of 4K when needed.		* ERASE_MEMORY_AT_START : if set to 1 the memory will be erased completly when starting a new log. This will take a little bit less than a minute, but afterwards you will be able to log values at a higher rate than if you didn't do it. If you let it to 0, the module is going to erase the memory block by block of 4K when needed.

Line 26:		Line 26:
	* NBR_VALUES_TO_LOG : the number of messages you want to log. This value is equivalent to the size of the values_to_log array.		* NBR_VALUES_TO_LOG : the number of messages you want to log. This value is equivalent to the size of the values_to_log array.

	* SKIP_X_CALLS_BETWEEN_VALUES : you might want to slow down the logger instead of losing values (because of buffer overflows). if that value is set to 0, a new value of every logged messages will be added to the buffer. If set to 2, we will wait two calls to the module, then during the third one we will ~~writte~~ the values to the buffer. By default this modules is called at 512Hz.		* SKIP_X_CALLS_BETWEEN_VALUES : you might want to slow down the logger instead of losing values (because of buffer overflows). if that value is set to 0, a new value of every logged messages will be added to the buffer. If set to 2, we will wait two calls to the module, then during the third one we will write the values to the buffer. By default this modules is called at 512Hz.

	Then you have two arrays :		Then you have two arrays :
Line 47:		Line 47:
	Then in the GCS you can go in the tab settings, then logger. In this tab you will have only one command to change the status of the module.		Then in the GCS you can go in the tab settings, then logger. In this tab you will have only one command to change the status of the module.

	At the start the module is in idle mode. To start logging you will need to prepare the memory first. To do that simply select the ~~initialise~~ mode and validate. The module will work. To test if the module have completed it's work you can click on the value to the left of the drop down menu. Once completed the status will be back to idle.		At the start the module is in idle mode. To start logging you will need to prepare the memory first. To do that simply select the initialize mode and validate. The module will work. To test if the module have completed it's work you can click on the value to the left of the drop down menu. Once completed the status will be back to idle.

	Then you can start actually logging values by selecting the "start log" mode and validating.		Then you can start actually logging values by selecting the "start log" mode and validating.

Karlito139: /* Logging values */

2014-08-29T08:43:01Z

Logging values

← Older revision		Revision as of 02:43, 29 August 2014
Line 34:		Line 34:

	==Logging values==		==Logging values==
	To use the micro logger you simply need to load the module "'''high_speed_logger_direct_memory'''" in your airframe file. Then you are going to have to add the GUI to your GCS by adding to your settings the file : "'''settings/modules/high_speed_logger_direct_memory.xml'''".		To use the micro logger you simply need to load the module "'''high_speed_logger_direct_memory'''" in your airframe file. You might want to be certain of the frequency at which the module is called by loading it like that :

			<modules main_freq="512">
			<load name="high_speed_logger_direct_memory.xml"/>
			</modules>


			Then you are going to have to add the GUI to your GCS by adding to your settings the file : "'''settings/modules/high_speed_logger_direct_memory.xml'''".

	[[File:GCS mem.png]]		[[File:GCS mem.png]]

Karlito139: /* Reading the values back */

2014-08-28T15:49:19Z

Reading the values back

← Older revision		Revision as of 09:49, 28 August 2014
Line 52:		Line 52:
	WARNING !!! : On some boards the UART port is used also by the GPS. The soft behind the GPS might read all the values on the port instead of the logger module. To solve that issue you simply need to use an other UART port for the logger module (configured in : conf/modules/high_speed_logger_direct_memory.xml). The other solution is to move the GPS in you board makefile.		WARNING !!! : On some boards the UART port is used also by the GPS. The soft behind the GPS might read all the values on the port instead of the logger module. To solve that issue you simply need to use an other UART port for the logger module (configured in : conf/modules/high_speed_logger_direct_memory.xml). The other solution is to move the GPS in you board makefile.

	For this operation you will need to get the reader application available [https://github.com/karlito139/lisa_s_logger_reader here].		For this operation you will need to get the reader application available [http://karlito139.github.io/lisa_s_logger_reader/ here]. The source code is available [https://github.com/karlito139/lisa_s_logger_reader here].

	To read the values back you simply need to connect to your autopilot using a serial connexion. Then start the micro logger application, at the top right of the interface you get a drop down menu containing all the serial ports available on your computer, select the one corresponding to your autopilot. Then simply click on the "Dump memory" button. The application is going to fetch all the values stored in the memory (warning this operation might be slow, up to 40 minutes if you used the entire memory).		To read the values back you simply need to connect to your autopilot using a serial connexion. Then start the micro logger application, at the top right of the interface you get a drop down menu containing all the serial ports available on your computer, select the one corresponding to your autopilot. Then simply click on the "Dump memory" button. The application is going to fetch all the values stored in the memory (warning this operation might be slow, up to 40 minutes if you used the entire memory).

	Finally you can click on the export button at the bottom of the window to save the values in a csv file.		Finally you can click on the export button at the bottom of the window to save the values in a csv file.

Karlito139: /* Introduction */

2014-08-28T14:18:41Z

Introduction

← Older revision		Revision as of 08:18, 28 August 2014
Line 11:		Line 11:
	* slower than other loggers		* slower than other loggers


			===Capability===
			This logger is capable of logging the entire IMU (9 axis) on 32 bits values at 512Hz. This is possible when you erase completely the memory at the beginning of the log (ERASE_MEMORY_AT_START set to 1).

			In case of buffer overflow, the reading tool is capable of "rebuilding" the missed values. It is going to put zeros where we missed values.

	=How to use it=		=How to use it=

Karlito139: /* Configuration of the module */

2014-08-28T14:15:37Z

Configuration of the module

← Older revision		Revision as of 08:15, 28 August 2014
Line 21:		Line 21:
	* NBR_VALUES_TO_LOG : the number of messages you want to log. This value is equivalent to the size of the values_to_log array.		* NBR_VALUES_TO_LOG : the number of messages you want to log. This value is equivalent to the size of the values_to_log array.

			* SKIP_X_CALLS_BETWEEN_VALUES : you might want to slow down the logger instead of losing values (because of buffer overflows). if that value is set to 0, a new value of every logged messages will be added to the buffer. If set to 2, we will wait two calls to the module, then during the third one we will writte the values to the buffer. By default this modules is called at 512Hz.

	Then you have two arrays :		Then you have two arrays :

Karlito139: /* Configuration of the module */

2014-08-28T14:12:49Z

Configuration of the module

← Older revision		Revision as of 08:12, 28 August 2014
Line 17:		Line 17:
	* ERASE_MEMORY_AT_START : if set to 1 the memory will be erased completly when starting a new log. This will take a little bit less than a minute, but afterwards you will be able to log values at a higher rate than if you didn't do it. If you let it to 0, the module is going to erase the memory block by block of 4K when needed.		* ERASE_MEMORY_AT_START : if set to 1 the memory will be erased completly when starting a new log. This will take a little bit less than a minute, but afterwards you will be able to log values at a higher rate than if you didn't do it. If you let it to 0, the module is going to erase the memory block by block of 4K when needed.

	* SIZE_OF_LOGGED_VALUES : the number of Bytes that each value logged must be (in memory). You can write a ~~32 bits~~ values in a ~~16 bites~~ slots, you just need to be certain that you don't have any overflows.		* SIZE_OF_LOGGED_VALUES : the number of Bytes that each value logged must be (in memory). You can write a 4 Bytes values in a 2 Bytes slots, you just need to be certain that you don't have any overflows.

	* NBR_VALUES_TO_LOG : the number of messages you want to log.		* NBR_VALUES_TO_LOG : the number of messages you want to log. This value is equivalent to the size of the values_to_log array.

Karlito139: /* Reading the values back */

2014-08-28T07:50:42Z

Reading the values back

← Older revision		Revision as of 01:50, 28 August 2014
Line 45:		Line 45:

	WARNING !!! : On some boards the UART port is used also by the GPS. The soft behind the GPS might read all the values on the port instead of the logger module. To solve that issue you simply need to use an other UART port for the logger module (configured in : conf/modules/high_speed_logger_direct_memory.xml). The other solution is to move the GPS in you board makefile.		WARNING !!! : On some boards the UART port is used also by the GPS. The soft behind the GPS might read all the values on the port instead of the logger module. To solve that issue you simply need to use an other UART port for the logger module (configured in : conf/modules/high_speed_logger_direct_memory.xml). The other solution is to move the GPS in you board makefile.

			For this operation you will need to get the reader application available [https://github.com/karlito139/lisa_s_logger_reader here].

	To read the values back you simply need to connect to your autopilot using a serial connexion. Then start the micro logger application, at the top right of the interface you get a drop down menu containing all the serial ports available on your computer, select the one corresponding to your autopilot. Then simply click on the "Dump memory" button. The application is going to fetch all the values stored in the memory (warning this operation might be slow, up to 40 minutes if you used the entire memory).		To read the values back you simply need to connect to your autopilot using a serial connexion. Then start the micro logger application, at the top right of the interface you get a drop down menu containing all the serial ports available on your computer, select the one corresponding to your autopilot. Then simply click on the "Dump memory" button. The application is going to fetch all the values stored in the memory (warning this operation might be slow, up to 40 minutes if you used the entire memory).

	Finally you can click on the export button at the bottom of the window to save the values in a csv file.		Finally you can click on the export button at the bottom of the window to save the values in a csv file.

Karlito139: /* Reading the values back */

2014-08-28T07:48:56Z

Reading the values back

← Older revision		Revision as of 01:48, 28 August 2014
Line 43:		Line 43:

	[[File:Micro logger.png]]		[[File:Micro logger.png]]

			WARNING !!! : On some boards the UART port is used also by the GPS. The soft behind the GPS might read all the values on the port instead of the logger module. To solve that issue you simply need to use an other UART port for the logger module (configured in : conf/modules/high_speed_logger_direct_memory.xml). The other solution is to move the GPS in you board makefile.

	To read the values back you simply need to connect to your autopilot using a serial connexion. Then start the micro logger application, at the top right of the interface you get a drop down menu containing all the serial ports available on your computer, select the one corresponding to your autopilot. Then simply click on the "Dump memory" button. The application is going to fetch all the values stored in the memory (warning this operation might be slow, up to 40 minutes if you used the entire memory).		To read the values back you simply need to connect to your autopilot using a serial connexion. Then start the micro logger application, at the top right of the interface you get a drop down menu containing all the serial ports available on your computer, select the one corresponding to your autopilot. Then simply click on the "Dump memory" button. The application is going to fetch all the values stored in the memory (warning this operation might be slow, up to 40 minutes if you used the entire memory).

	Finally you can click on the export button at the bottom of the window to save the values in a csv file.		Finally you can click on the export button at the bottom of the window to save the values in a csv file.

Karlito139: /* Configuration of the module */

2014-08-28T07:46:16Z

Configuration of the module

← Older revision		Revision as of 01:46, 28 August 2014
Line 26:		Line 26:
	* values_to_log : containing the pointer to the values to log.		* values_to_log : containing the pointer to the values to log.
	* name_of_the_values : the name of the messages logged. This is simply an aesthetic configuration, for you to know which message were logged.		* name_of_the_values : the name of the messages logged. This is simply an aesthetic configuration, for you to know which message were logged.



	==Logging values==		==Logging values==

Karlito139: /* How to use it */

2014-08-28T07:45:28Z

How to use it

@@ Line 13: / Line 13: @@
 =How to use it=
 ==Logging values==
 To use the micro logger you simply need to load the module "'''high_speed_logger_direct_memory'''" in your airframe file. Then you are going to have to add the GUI to your GCS by adding to your settings the file : "'''settings/modules/high_speed_logger_direct_memory.xml'''".