Hey @patrickelectric thanks for the answer !!
you didn’t mention anything about time or pressure, so I suppose I was right on those.
To sum up … mavlink messages I need are:
- time - SYSTEM_TIME.time_unix_usec
- depth - VFR_HUD.alt
- pressure - SCALED_PRESSURE2.press_diff
- temperature - SCALED_PRESSURE2.temperature (I use the Bar30 sensor)
- heading - VFR_HUD.heading
please correct me if anything of the above is wrong.
I also encountered some difference between mavlink time and local time (on the system python is reading the messages) - a very small one, but in a case of video timing might be critical.
I also saw this mentioned in Writing telemetry data (specifically, depth) to gopro video? - #5 by mspencer
Is there a workaround on this ??
and what is the status of Add option to set system time via GCS ??
many thanks