"Partially answering myself:
mavlink_attitude_t.yaw follows the trigonometric convention and ranges 0 to 2pi rads (0 to 180 deg). Once converted into degrees and subtracted
from 90, can be used to correct mavlink_gps_raw_int.cog (course over the…"
"Looking at the values, one strange observation:
The values of mavlink_global_position_int_t.hdg ("Compass heading in degrees *100) range between
3470 and 12070, while the values of mavlink_gps_raw_int_t.cog (course over ground), also in…"
"Thanks, I would have not been able to find out that information on my own.
I keep on documenting.
1. mavlink_attitude_t.yaw, as it is in rad, should I assume that the 0 is pointing E and goes counterclokwise?
2. mavlink_vfr_hud_t :…"
You forgot including the AM/PM field in your program, times are not in 24h format in the input txt files (unfortunately)
Actually, it would be better writing YYYY/MM/DD HH:MM:SS.xxx in 24h in your csv files.
"I'm using arduplane, but I assume that for this purpose the variables are the same.
I'm finding most of the variables I need defined in
Would it be possible that in a new version the program will have a default output filename automatically set using
the prefix of the input filename + .csv? The user could always modify this filename, but
most often this default would be…"
"Well, at least we would decrease the error in a 50%. Also, newer gps models to be connected to the APM will be
able to transfer info at higher rates. Some of the current bluetooth gps units transmit at 10Hz right now. So having
the time as accurate…"
This does not solve the problem of linking other sensors because there is no way to link the elapsed usecs to the actual time: the starting time is recorded in secs only.
We cannot know the time that corresponds to the elapsed 409810452 usec…"
"Andrew, I'm afraid I do not fully understand. Does this mean that you can modify your program to report milliseconds or not? Alternatively, is there another field that I could use in the output table so that I can
calculate time in milliseconds in…"
"Thanks for this program, as the txt and csv files from MisionPlanner are too complex.
Is there any way we could have the Time field with milliseconds? i.e. having1:55:09.345 instead of just 1:55:09. Note that currently, with the time in seconds,we…"