Difference between revisions of "Logs"
HectoPascal (talk | contribs) |
HectoPascal (talk | contribs) (→Format) |
||
Line 5: | Line 5: | ||
The log files are stored in the <tt>var/logs/</tt> folder (under <tt>PAPARAZZI_HOME</tt>). A log is splitted in two files: | The log files are stored in the <tt>var/logs/</tt> folder (under <tt>PAPARAZZI_HOME</tt>). A log is splitted in 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. | * 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. | ||
The basename of these two files is the same and is build from the date and time at the creation. | The basename 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 | |||
{{ | |||
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: | |||
{{ | |||
<message name="GPS" ID="8"> | |||
<field name="mode" type="uint8" unit="byte_mask"></field> | |||
<field name="utm_east" type="int32" unit="cm"></field> | |||
<field name="utm_north" type="int32" unit="cm"></field> | |||
<field name="course" type="int16" unit="decideg"></field> | |||
<field name="alt" type="int32" unit="cm"></field> | |||
... | |||
</message> | |||
}} | |||
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: The <tt>.data</tt> files may be huge (about 4M per hour with a standard telemetry configuration). They can be efficiently compressed. The tools described in the next sections handle most of the compressed format (.zip, .gz, .bz2, ...). The bzip2 compression seems to perform better than others on these files. | Note: The <tt>.data</tt> files may be huge (about 4M per hour with a standard telemetry configuration). They can be efficiently compressed. The tools described in the next sections handle most of the compressed format (.zip, .gz, .bz2, ...). The bzip2 compression seems to perform better than others on these files. |
Revision as of 00:14, 29 August 2007
On each launch, the server creates a log of all the messages sent by the aircraft. This log can be used to analyse flight data and to replay the flight.
Format
The log files are stored in the var/logs/ folder (under PAPARAZZI_HOME). A log is splitted in two files:
- A .log file, an XML file, which contains a copy of the whole configuration (airframes, flight plans, ...).
- A .data 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.
The basename of these two files is the same and is build from the date and time at the creation.
The lines of the .data file are formatted according to the message description listed in the conf/messages.xml file. For example, the following line Template:3.300 6 GPS 3 36028551 481359212 899 18500 0 -8 960 31 0 contains a GPS message received at time 3.3s, from aircraft 6. According the GPS message description: {{
<message name="GPS" ID="8"> <field name="mode" type="uint8" unit="byte_mask"></field> <field name="utm_east" type="int32" unit="cm"></field> <field name="utm_north" type="int32" unit="cm"></field> <field name="course" type="int16" unit="decideg"></field> <field name="alt" type="int32" unit="cm"></field>
...
</message>
}} UTM position is 360285.51m east, 4813592.12m north, course is 89.9° (east), altitude is 185m, ... Note that the appropriate messages.xml description, i.e. the one which has been used while the log was created, is itself stored in the associated .log file. It may differ from the current one installed in your conf/ folder.
Note: The .data files may be huge (about 4M per hour with a standard telemetry configuration). They can be efficiently compressed. The tools described in the next sections handle most of the compressed format (.zip, .gz, .bz2, ...). The bzip2 compression seems to perform better than others on these files.
Data Plotting
Data stored in log files can be plotted with the Plotter (sw/logalizer/plot 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 Google Earth.