Openlog - Revision history

Openuas: /* About */

2020-07-29T16:54:56Z

About

← Older revision		Revision as of 10:54, 29 July 2020
Line 60:		Line 60:

	=About=		=About=
	In general [http://www.sparkfun.com/products/9530 OpenLog] is a Module from Sparkfun that contains an Atmega328P and a Micro-SD-Slot. It can handle FAT16 and FAT32 microSD cards up to ~~16GB~~. Once installed into the wiring (parallel to the dataradio) it records every message the UAS sends. That is very handy for using it as some kind of blackbox or for data-logging purposes if no Modem was involved. It is also nice for reconstructing what happened after a crash, since the radio-communication is gone, once the plane is near the ground. 2GB is enough to log a comlete season (several hundred flights).		In general [http://www.sparkfun.com/products/9530 OpenLog] is a Module from Sparkfun that contains an Atmega328P and a Micro-SD-Slot. It can handle FAT16 and FAT32 microSD cards up to 64GB with latest version v4. Once installed into the wiring (parallel to the dataradio) it records every message the UAS sends. That is very handy for using it as some kind of blackbox or for data-logging purposes if no Modem was involved. It is also nice for reconstructing what happened after a crash, since the radio-communication is gone, once the plane is near the ground. 2GB is enough to log a comlete season (several hundred flights).
	The general logging is done in two steps: First you record your log using the telemtry in transparent mode, with the openlog-module loaded. the normal paparazzi-protocal does not contain timestamps and the openlog-module adds timestamps to the datastream to have a reference for the time.		The general logging is done in two steps: First you record your log using the telemtry in transparent mode, with the openlog-module loaded. the normal paparazzi-protocal does not contain timestamps and the openlog-module adds timestamps to the datastream to have a reference for the time.
	Second the recorded logs are extracted from the SD-Card to the normal logfiles. For doing so, there is a tool calles openlog2tlm to convert the recorded files to the TLM-format of the SD-logger. Next the created TLM-file is added to the logs by sd2log.		Second the recorded logs are extracted from the SD-Card to the normal logfiles. For doing so, there is a tool calles openlog2tlm to convert the recorded files to the TLM-format of the SD-logger. Next the created TLM-file is added to the logs by sd2log.

Openuas: Cleanup of logger for PPRZ Wiki docs

2015-11-19T15:21:14Z

Cleanup of logger for PPRZ Wiki docs

@@ Line 1: / Line 1: @@
 <categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>Modules</categorytree>
 In general [http://www.sparkfun.com/products/9530 OpenLog] is a Module from Sparkfun that contains an Atmega328P and a Micro-SD-Slot. It can handle FAT16 and FAT32 microSD cards up to 16GB. Once installed into the wiring (parallel to the dataradio) it records every message the UAS sends. That is very handy for using it as some kind of blackbox or for data-logging purposes if no Modem was involved. It is also nice for reconstructing what happened after a crash, since the radio-communication is gone, once the plane is near the ground. 2GB is enough to log a comlete season (several hundred flights).
 The general logging is done in two steps: First you record your log using the telemtry in transparent mode, with the openlog-module loaded. the normal paparazzi-protocal does not contain timestamps and the openlog-module adds timestamps to the datastream to have a reference for the time.

NeoFromMatrix: typo

2015-05-19T20:05:46Z

typo

← Older revision		Revision as of 14:05, 19 May 2015
Line 1:		Line 1:
	<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>Modules</categorytree>		<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>Modules</categorytree>

	In general [http://www.sparkfun.com/products/9530 OpenLog] is a Module from Sparkfun that contains an ~~Atmega324~~ and a Micro-SD-Slot. It can handle FAT16 and FAT32 microSD cards up to 16GB. Once installed into the wiring (parallel to the dataradio) it records every message the UAS sends. That is very handy for using it as some kind of blackbox or for data-logging purposes if no Modem was involved. It is also nice for reconstructing what happened after a crash, since the radio-communication is gone, once the plane is near the ground. 2GB is enough to log a comlete season (several hundred flights).		In general [http://www.sparkfun.com/products/9530 OpenLog] is a Module from Sparkfun that contains an Atmega328P and a Micro-SD-Slot. It can handle FAT16 and FAT32 microSD cards up to 16GB. Once installed into the wiring (parallel to the dataradio) it records every message the UAS sends. That is very handy for using it as some kind of blackbox or for data-logging purposes if no Modem was involved. It is also nice for reconstructing what happened after a crash, since the radio-communication is gone, once the plane is near the ground. 2GB is enough to log a comlete season (several hundred flights).
	The general logging is done in two steps: First you record your log using the telemtry in transparent mode, with the openlog-module loaded. the normal paparazzi-protocal does not contain timestamps and the openlog-module adds timestamps to the datastream to have a reference for the time.		The general logging is done in two steps: First you record your log using the telemtry in transparent mode, with the openlog-module loaded. the normal paparazzi-protocal does not contain timestamps and the openlog-module adds timestamps to the datastream to have a reference for the time.
	Second the recorded logs are extracted from the SD-Card to the normal logfiles. For doing so, there is a tool calles openlog2tlm to convert the recorded files to the TLM-format of the SD-logger. Next the created TLM-file is added to the logs by sd2log.		Second the recorded logs are extracted from the SD-Card to the normal logfiles. For doing so, there is a tool calles openlog2tlm to convert the recorded files to the TLM-format of the SD-logger. Next the created TLM-file is added to the logs by sd2log.

Bshaot at 01:11, 19 May 2015

2015-05-19T01:11:32Z

← Older revision		Revision as of 19:11, 18 May 2015
Line 11:		Line 11:

	The OpenLog is simply connected to the TX-Line of the AP. Once the AP is powered, it starts to record.		The OpenLog is simply connected to the TX-Line of the AP. Once the AP is powered, it starts to record.
	In general there is one Problem with the stock-firmware of the OpenLog. If it gets an escape-character (CTRL+Z) it switches into command-mode and stops logging. But the telemetry stream is nearly ~~arbritary~~. So we have to deactivate this feature, it isn't needed for our application at all. Therefore we have to reprogram the OpenLog. You need an AVR-programmer like the i.e. [http://www.hobbyking.com/hobbycity/store/uh_viewItem.asp?idProduct=21321 usbasp]. You have to wire the ISP to the accoring pins of the OpenLog. You need the avrdude package installed.		In general there is one Problem with the stock-firmware of the OpenLog. If it gets an escape-character (CTRL+Z) it switches into command-mode and stops logging. But the telemetry stream is nearly arbitrary. So we have to deactivate this feature, it isn't needed for our application at all. Therefore we have to reprogram the OpenLog. You need an AVR-programmer like the i.e. [http://www.hobbyking.com/hobbycity/store/uh_viewItem.asp?idProduct=21321 usbasp]. You have to wire the ISP to the accoring pins of the OpenLog. You need the avrdude package installed.

	First you need to checkout the modified OpenLog firmware on github:		First you need to checkout the modified OpenLog firmware on github:

Flixr at 09:38, 15 July 2013

2013-07-15T09:38:30Z

← Older revision		Revision as of 03:38, 15 July 2013
Line 1:		Line 1:
	<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>Modules</categorytree>		<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>Modules</categorytree>

	In general [http://www.sparkfun.com/products/9530 OpenLog] is a Module from Sparkfun that contains an Atmega324 and a Micro-SD-Slot. It can handle ~~FAT-formated files-systems~~ up to ~~2GB~~. Once installed into the wiring (parallel to the dataradio) it records every message the UAS sends. That is very handy for using it as some kind of blackbox or for data-logging purposes if no Modem was involved. It is also nice for reconstructing what happened after a crash, since the radio-communication is gone, once the plane is near the ground. 2GB is enough to log a comlete season (several hundred flights).		In general [http://www.sparkfun.com/products/9530 OpenLog] is a Module from Sparkfun that contains an Atmega324 and a Micro-SD-Slot. It can handle FAT16 and FAT32 microSD cards up to 16GB. Once installed into the wiring (parallel to the dataradio) it records every message the UAS sends. That is very handy for using it as some kind of blackbox or for data-logging purposes if no Modem was involved. It is also nice for reconstructing what happened after a crash, since the radio-communication is gone, once the plane is near the ground. 2GB is enough to log a comlete season (several hundred flights).
	The general logging is done in two steps: First you record your log using the telemtry in transparent mode, with the openlog-module loaded. the normal paparazzi-protocal does not contain timestamps and the openlog-module adds timestamps to the datastream to have a reference for the time.		The general logging is done in two steps: First you record your log using the telemtry in transparent mode, with the openlog-module loaded. the normal paparazzi-protocal does not contain timestamps and the openlog-module adds timestamps to the datastream to have a reference for the time.
	Second the recorded logs are extracted from the SD-Card to the normal logfiles. For doing so, there is a tool calles openlog2tlm to convert the recorded files to the TLM-format of the SD-logger. Next the created TLM-file is added to the logs by sd2log.		Second the recorded logs are extracted from the SD-Card to the normal logfiles. For doing so, there is a tool calles openlog2tlm to convert the recorded files to the TLM-format of the SD-logger. Next the created TLM-file is added to the logs by sd2log.

Flixr: add modules cat

2012-12-30T11:47:15Z

add modules cat

← Older revision		Revision as of 05:47, 30 December 2012
Line 1:		Line 1:
	== ~~Openlog ==~~		<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>Modules</categorytree>

	In general [http://www.sparkfun.com/products/9530 OpenLog] is a Module from Sparkfun that contains an Atmega324 and a Micro-SD-Slot. It can handle FAT-formated files-systems up to 2GB. Once installed into the wiring (parallel to the dataradio) it records every message the UAS sends. That is very handy for using it as some kind of blackbox or for data-logging purposes if no Modem was involved. It is also nice for reconstructing what happened after a crash, since the radio-communication is gone, once the plane is near the ground. 2GB is enough to log a comlete season (several hundred flights).		In general [http://www.sparkfun.com/products/9530 OpenLog] is a Module from Sparkfun that contains an Atmega324 and a Micro-SD-Slot. It can handle FAT-formated files-systems up to 2GB. Once installed into the wiring (parallel to the dataradio) it records every message the UAS sends. That is very handy for using it as some kind of blackbox or for data-logging purposes if no Modem was involved. It is also nice for reconstructing what happened after a crash, since the radio-communication is gone, once the plane is near the ground. 2GB is enough to log a comlete season (several hundred flights).
	The general logging is done in two steps: First you record your log using the telemtry in transparent mode, with the openlog-module loaded. the normal paparazzi-protocal does not contain timestamps and the openlog-module adds timestamps to the datastream to have a reference for the time.		The general logging is done in two steps: First you record your log using the telemtry in transparent mode, with the openlog-module loaded. the normal paparazzi-protocal does not contain timestamps and the openlog-module adds timestamps to the datastream to have a reference for the time.
	Second the recorded logs are extracted from the SD-Card to the normal logfiles. For doing so, there is a tool calles openlog2tlm to convert the recorded files to the TLM-format of the SD-logger. Next the created TLM-file is added to the logs by sd2log.		Second the recorded logs are extracted from the SD-Card to the normal logfiles. For doing so, there is a tool calles openlog2tlm to convert the recorded files to the TLM-format of the SD-logger. Next the created TLM-file is added to the logs by sd2log.
	There is a helper-script that does this job.		There is a helper-script that does this job.

	=== Hardware ===		=== Hardware ===

Line 68:		Line 70:


	[[Category:Software]] [[Category:User_Documentation]]		[[Category:Software]] [[Category:User_Documentation]] [[Category:Modules]]

Christoph at 15:54, 26 June 2012

2012-06-26T15:54:11Z

← Older revision		Revision as of 09:54, 26 June 2012
Line 11:		Line 11:
	In general there is one Problem with the stock-firmware of the OpenLog. If it gets an escape-character (CTRL+Z) it switches into command-mode and stops logging. But the telemetry stream is nearly arbritary. So we have to deactivate this feature, it isn't needed for our application at all. Therefore we have to reprogram the OpenLog. You need an AVR-programmer like the i.e. [http://www.hobbyking.com/hobbycity/store/uh_viewItem.asp?idProduct=21321 usbasp]. You have to wire the ISP to the accoring pins of the OpenLog. You need the avrdude package installed.		In general there is one Problem with the stock-firmware of the OpenLog. If it gets an escape-character (CTRL+Z) it switches into command-mode and stops logging. But the telemetry stream is nearly arbritary. So we have to deactivate this feature, it isn't needed for our application at all. Therefore we have to reprogram the OpenLog. You need an AVR-programmer like the i.e. [http://www.hobbyking.com/hobbycity/store/uh_viewItem.asp?idProduct=21321 usbasp]. You have to wire the ISP to the accoring pins of the OpenLog. You need the avrdude package installed.

	First you need to ~~download~~ the ~~''[[Media~~:~~Booz_gps_brd~~.~~zip\|modified~~ .~~hex~~-~~file for~~ OpenLog~~]]''~~		First you need to checkout the modified OpenLog firmware on github:

			git clone https://github.com/chni/OpenLog.git -b OpenLog_V1_noescape

			then change to the directory where the hexfile is:

			cd OpenLog/Code

			The hexfile is contained by the directory, so you can flash it.

	You should power the OpenLog with the Programmer, not by the LPC in the same time. The programming is done by running		You should power the OpenLog with the Programmer, not by the LPC in the same time. The programming is done by running

Christoph: /* Hardware */

2012-06-26T15:30:53Z

Hardware

← Older revision		Revision as of 09:30, 26 June 2012
Line 9:		Line 9:

	The OpenLog is simply connected to the TX-Line of the AP. Once the AP is powered, it starts to record.		The OpenLog is simply connected to the TX-Line of the AP. Once the AP is powered, it starts to record.
			In general there is one Problem with the stock-firmware of the OpenLog. If it gets an escape-character (CTRL+Z) it switches into command-mode and stops logging. But the telemetry stream is nearly arbritary. So we have to deactivate this feature, it isn't needed for our application at all. Therefore we have to reprogram the OpenLog. You need an AVR-programmer like the i.e. [http://www.hobbyking.com/hobbycity/store/uh_viewItem.asp?idProduct=21321 usbasp]. You have to wire the ISP to the accoring pins of the OpenLog. You need the avrdude package installed.

			First you need to download the ''[[Media:Booz_gps_brd.zip\|modified .hex-file for OpenLog]]''

			You should power the OpenLog with the Programmer, not by the LPC in the same time. The programming is done by running

			avrdude -c usbasp -pm328p -U flash:w:openlog_noescape.hex -Ulfuse:w:0xff:m -Uhfuse:w:0xda:m -Uefuse:w:0x0:m

			After running this, the OpenLog has a custom firmware making it ignore the escape-characters.

	=== Software ===		=== Software ===

Christoph at 11:21, 24 June 2012

2012-06-24T11:21:43Z

← Older revision		Revision as of 05:21, 24 June 2012
Line 1:		Line 1:
	== Openlog ==		== Openlog ==
	In general OpenLog is a Module from Sparkfun that contains an Atmega324 and a Micro-SD-Slot. It can handle FAT-formated files-systems up to 2GB. Once installed into the wiring (parallel to the dataradio) it records every message the UAS sends. That is very handy for using it as some kind of blackbox or for data-logging purposes if no Modem was involved. It is also nice for reconstructing what happened after a crash, since the radio-communication is gone, once the plane is near the ground. 2GB is enough to log a comlete season (several hundred flights).		In general [http://www.sparkfun.com/products/9530 OpenLog] is a Module from Sparkfun that contains an Atmega324 and a Micro-SD-Slot. It can handle FAT-formated files-systems up to 2GB. Once installed into the wiring (parallel to the dataradio) it records every message the UAS sends. That is very handy for using it as some kind of blackbox or for data-logging purposes if no Modem was involved. It is also nice for reconstructing what happened after a crash, since the radio-communication is gone, once the plane is near the ground. 2GB is enough to log a comlete season (several hundred flights).
	The general logging is done in two steps: First you record your log using the telemtry in transparent mode, with the openlog-module loaded. the normal paparazzi-protocal does not contain timestamps and the openlog-module adds timestamps to the datastream to have a reference for the time.		The general logging is done in two steps: First you record your log using the telemtry in transparent mode, with the openlog-module loaded. the normal paparazzi-protocal does not contain timestamps and the openlog-module adds timestamps to the datastream to have a reference for the time.
	Second the recorded logs are extracted from the SD-Card to the normal logfiles. For doing so, there is a tool calles openlog2tlm to convert the recorded files to the TLM-format of the SD-logger. Next the created TLM-file is added to the logs by sd2log.		Second the recorded logs are extracted from the SD-Card to the normal logfiles. For doing so, there is a tool calles openlog2tlm to convert the recorded files to the TLM-format of the SD-logger. Next the created TLM-file is added to the logs by sd2log.

Christoph at 11:16, 24 June 2012

2012-06-24T11:16:16Z

@@ Line 30: / Line 30: @@
 }}
 Then compile, flash your AP and do your flight. Afterwards take the SD-Card from the logger and import the logs:
 [[Category:Software]] [[Category:User_Documentation]]