Logs - Revision history

Joostmeulenbeld: according to plot (which is now a shell script) "plot has been renamed to logplotter", and then exec's $PAPARAZZI_SRC/sw/logalizer/logplotter

2017-11-28T13:35:16Z

according to plot (which is now a shell script) "plot has been renamed to logplotter", and then exec's $PAPARAZZI_SRC/sw/logalizer/logplotter

← Older revision		Revision as of 07:35, 28 November 2017
Line 30:		Line 30:
	==Data Plotting==		==Data Plotting==

	Data stored in log files can be plotted with the [[Plotter]] (<tt>sw/logalizer/~~plot~~</tt> or launchable from the [[Paparazzi Center]]). This tool can plot data from different logs in the same window and data from the same log in different windows. It also offers to export the track as a KML file for [http://earth.google.com Google Earth].		Data stored in log files can be plotted with the [[Plotter]] (<tt>sw/logalizer/logplotter</tt> or launchable from the [[Paparazzi Center]]). This tool can plot data from different logs in the same window and data from the same log in different windows. It also offers to export the track as a KML file for [http://earth.google.com Google Earth].

	==Replay==		==Replay==

IHaveADrone: spelling

2016-07-08T17:02:03Z

spelling

← Older revision		Revision as of 11:02, 8 July 2016
Line 5:		Line 5:
	The log files are stored in the <tt>var/logs/</tt> folder (under <tt>PAPARAZZI_HOME</tt>). A log is split into two files:		The log files are stored in the <tt>var/logs/</tt> folder (under <tt>PAPARAZZI_HOME</tt>). A log is split into two files:
	* A <tt>.log</tt> file, an XML file, which contains a copy of the whole configuration (airframes, flight plans, ...).		* A <tt>.log</tt> file, an XML file, which contains a copy of the whole configuration (airframes, flight plans, ...).
	* A <tt>.data</tt> file, an ascii file, which ~~cfontains~~ the list of the received messages. Each message is time-stamped in milliseconds since the creation of the file and marked with the ID of the sending aircraft.		* A <tt>.data</tt> file, an ascii file, which contains the list of the received messages. Each message is time-stamped in milliseconds since the creation of the file and marked with the ID of the sending aircraft.

	The first part before the type of file of these two files is the same and is build from the date and time at the creation.		The first part before the type of file of these two files is the same and is build from the date and time at the creation.

Ghattenb: /* Replay */

2015-11-27T15:25:19Z

Replay

← Older revision		Revision as of 09:25, 27 November 2015
Line 33:		Line 33:

	==Replay==		==Replay==
	A flight can be replayed with the Log Flight Player (<tt>sw/logalizer/play</tt>, which can be started from the [[Paparazzi Center]]). This agent then is a substitute for the Data Link agent and will send over the bus the messages which had been send by the aircraft while the log was recorded.		A flight can be replayed with the Log Flight Player (<tt>sw/logalizer/play</tt>) which can be started from the [[Paparazzi Center]] (from tools menu to start alone, or from the '''session''' selection box to start a complete replay session with GCS, server and player tool). This agent then is a substitute for the Data Link agent and will send over the bus the messages which had been send by the aircraft while the log was recorded.

	Note: While replaying a log, it is a good idea to disable a new log creation from the server (<tt>-n</tt> option).		Note: While replaying a log, it is a good idea to disable a new log creation from the server (<tt>-n</tt> option).

Openuas: /* NMEA output */

2014-10-09T13:44:45Z

NMEA output

← Older revision		Revision as of 07:44, 9 October 2014
Line 62:		Line 62:
	Standard plots like trajectory, attitude or speed are available for quick reviewing and Matlab's plotting tools can be accessed for plot cosmetics and printing.		Standard plots like trajectory, attitude or speed are available for quick reviewing and Matlab's plotting tools can be accessed for plot cosmetics and printing.

	==NMEA output==		==NMEA log output==
	NMEA output is useful for [[Kinomap]], for example.		NMEA output is useful for [[Kinomap]], for example. Do not confuse this with the application ''ivy2nmea'' live NMEA stream out.

	Two methods exist for generating an NMEA gps log from the paparazzi logs:		Two methods exist for generating an NMEA gps log from the paparazzi logs:

Openuas: /* Replay */

2014-08-19T14:31:22Z

Replay

← Older revision		Revision as of 08:31, 19 August 2014
Line 41:		Line 41:
	If a<tt>.log</tt> file is added behind the replay command on the command line, this log will be loaded on startup immediately.		If a<tt>.log</tt> file is added behind the replay command on the command line, this log will be loaded on startup immediately.

	TIP: If one want to speed up a replay with 4x speedup of the time [[Simulation#Change_the_environment\|Environment Simulator agent, Gaia]] can be used. Launch it from Paparazzi center tools menu "[[Simulation#Change_the_environment\|Environment Simulator]]". Then changing the time scale with the slider or add a commandline option e.g. '''gaia -t 4'''.		TIP: If one want to speed up a replay with 4x speedup of the time [[Simulation#Change_the_environment\|Environment Simulator agent, Gaia]] can be used. Launch it from Paparazzi center tools menu "[[Simulation#Change_the_environment\|Environment Simulator]]". Then changing the time scale with the slider or add a commandline option e.g. ''./gaia -t 4''

Openuas at 14:30, 19 August 2014

2014-08-19T14:30:09Z

← Older revision		Revision as of 08:30, 19 August 2014
Line 5:		Line 5:
	The log files are stored in the <tt>var/logs/</tt> folder (under <tt>PAPARAZZI_HOME</tt>). A log is split into two files:		The log files are stored in the <tt>var/logs/</tt> folder (under <tt>PAPARAZZI_HOME</tt>). A log is split into two files:
	* A <tt>.log</tt> file, an XML file, which contains a copy of the whole configuration (airframes, flight plans, ...).		* A <tt>.log</tt> file, an XML file, which contains a copy of the whole configuration (airframes, flight plans, ...).
	* A <tt>.data</tt> file, an ascii file, which ~~contains~~ the list of the received messages. Each message is time-stamped in milliseconds since the creation of the file and marked with the ID of the sending aircraft.		* A <tt>.data</tt> file, an ascii file, which cfontains the list of the received messages. Each message is time-stamped in milliseconds since the creation of the file and marked with the ID of the sending aircraft.

	The first part before the type of file of these two files is the same and is build from the date and time at the creation.		The first part before the type of file of these two files is the same and is build from the date and time at the creation.

Openuas at 10:18, 19 August 2014

2014-08-19T10:18:44Z

← Older revision		Revision as of 04:18, 19 August 2014
Line 5:		Line 5:
	The log files are stored in the <tt>var/logs/</tt> folder (under <tt>PAPARAZZI_HOME</tt>). A log is split into two files:		The log files are stored in the <tt>var/logs/</tt> folder (under <tt>PAPARAZZI_HOME</tt>). A log is split into two files:
	* A <tt>.log</tt> file, an XML file, which contains a copy of the whole configuration (airframes, flight plans, ...).		* A <tt>.log</tt> file, an XML file, which contains a copy of the whole configuration (airframes, flight plans, ...).
	* A <tt>.data</tt> file, an ascii file, which contains the list of the received messages. Each message is time-stamped in ~~seconds~~ since the creation of the file and marked with the id of the sending aircraft.		* A <tt>.data</tt> file, an ascii file, which contains the list of the received messages. Each message is time-stamped in milliseconds since the creation of the file and marked with the ID of the sending aircraft.

	The ~~basename~~ of these two files is the same and is build from the date and time at the creation.		The first part before the type of file of these two files is the same and is build from the date and time at the creation.

	The lines of the <tt>.data</tt> file are formatted according to the message description listed in the <tt>conf/messages.xml</tt> file. For example, the following line:		The lines of the <tt>.data</tt> file are formatted according to the message description listed in the <tt>conf/messages.xml</tt> file. For example, the following line:

Openuas at 10:16, 19 August 2014

2014-08-19T10:16:55Z

← Older revision		Revision as of 04:16, 19 August 2014
Line 33:		Line 33:

	==Replay==		==Replay==
	A flight can be replayed with the Log Flight Player (<tt>sw/logalizer/play</tt>, ~~launchable~~ from the [[Paparazzi Center]]). This agent then is a substitute for the Data Link agent and will send over the bus the messages which had been send by the aircraft while the log was recorded.		A flight can be replayed with the Log Flight Player (<tt>sw/logalizer/play</tt>, which can be started from the [[Paparazzi Center]]). This agent then is a substitute for the Data Link agent and will send over the bus the messages which had been send by the aircraft while the log was recorded.

	Note: While replaying a log, it is a good idea to disable a new log creation from the server (<tt>-n</tt> option).		Note: While replaying a log, it is a good idea to disable a new log creation from the server (<tt>-n</tt> option).
Line 39:		Line 39:
	When doing a log replay it is very valuable to launch the messages window (in the tools menu) as well. This allows for the use of the the real time plotter and also gives the data from the aircraft to the user.		When doing a log replay it is very valuable to launch the messages window (in the tools menu) as well. This allows for the use of the the real time plotter and also gives the data from the aircraft to the user.

	If the ~~user wishes~~ to speed up a replay ~~gaia~~ can be used ~~(launch~~ from ~~paparazzi centers~~ tools menu~~) to do this by~~ changing the time scale.		If a<tt>.log</tt> file is added behind the replay command on the command line, this log will be loaded on startup immediately.

			TIP: If one want to speed up a replay with 4x speedup of the time [[Simulation#Change_the_environment\|Environment Simulator agent, Gaia]] can be used. Launch it from Paparazzi center tools menu "[[Simulation#Change_the_environment\|Environment Simulator]]". Then changing the time scale with the slider or add a commandline option e.g. '''gaia -t 4'''.


	~~A <tt>.log</tt> file given in the command line will be loaded on startup.~~

	===Output on a serial port===		===Output on a serial port===

Flixr at 19:59, 15 September 2013

2013-09-15T19:59:04Z

← Older revision		Revision as of 13:59, 15 September 2013
Line 14:		Line 14:
	<source lang="xml" >		<source lang="xml" >
	<message name="GPS" ID="8">		<message name="GPS" ID="8">
	<field name="mode" type="uint8" unit="byte_mask" ></~~field~~>		<field name="mode" type="uint8" unit="byte_mask"/>
	<field name="utm_east" type="int32" unit="cm" ></~~field~~>		<field name="utm_east" type="int32" unit="cm"/>
	<field name="utm_north" type="int32" unit="cm" ></~~field~~>		<field name="utm_north" type="int32" unit="cm"/>
	<field name="course" type="int16" unit="decideg" ></~~field~~>		<field name="course" type="int16" unit="decideg"/>
	<field name="alt" type="int32" unit="cm" ></~~field~~>		<field name="alt" type="int32" unit="cm"/>
	...		...
	</message>		</message>

Mbina: added: syntax highlighting

2013-09-15T19:47:01Z

added: syntax highlighting

← Older revision		Revision as of 13:47, 15 September 2013
Line 12:		Line 12:
	3.300 6 GPS 3 36028551 481359212 899 18500 0 -8 960 31 0		3.300 6 GPS 3 36028551 481359212 899 18500 0 -8 960 31 0
	contains a <tt>GPS</tt> message received at time 3.3s, from aircraft 6. According the GPS message description:		contains a <tt>GPS</tt> message received at time 3.3s, from aircraft 6. According the GPS message description:
			<source lang="xml" >
	<message name="GPS" ID="8">		<message name="GPS" ID="8">
	<field name="mode" type="uint8" unit="byte_mask"></field>		<field name="mode" type="uint8" unit="byte_mask" ></field>
	<field name="utm_east" type="int32" unit="cm"></field>		<field name="utm_east" type="int32" unit="cm" ></field>
	<field name="utm_north" type="int32" unit="cm"></field>		<field name="utm_north" type="int32" unit="cm" ></field>
	<field name="course" type="int16" unit="decideg"></field>		<field name="course" type="int16" unit="decideg" ></field>
	<field name="alt" type="int32" unit="cm"></field>		<field name="alt" type="int32" unit="cm" ></field>
	...		...
	</message>		</message>
			</source>

	UTM position is 360285.51m east, 4813592.12m north, course is 89.9° (east), altitude is 185m, ...		UTM position is 360285.51m east, 4813592.12m north, course is 89.9° (east), altitude is 185m, ...
	Note that the appropriate <tt>messages.xml</tt> description, i.e. the one which has been used while the log was created, is itself stored in the associated <tt>.log</tt> file. It may differ from the current one installed in your <tt>conf/</tt> folder.		Note that the appropriate <tt>messages.xml</tt> description, i.e. the one which has been used while the log was created, is itself stored in the associated <tt>.log</tt> file. It may differ from the current one installed in your <tt>conf/</tt> folder.