h-elsner
Premium Pilot
- Joined
- Mar 23, 2016
- Messages
- 2,273
- Reaction score
- 1,999
- Location
- Bavaria / Germany
- Website
- h-elsner.mooo.com
This seems to be a problem with DroneLogBook.
Location is alway correct in telemetry files. You have GPS data from copter in Telemetry_*.csv and GPS data from ST16S in RemoteGPS_*.csv. Usually the coptes coordinates are more precise. Altitude contains relative to start level. RemoteGPS has absolute altitude in.
I have proved that many times on different locations. Timestamps are taken from ST16S, local time. If time is set correctly the timestamps are also correct.
If a tool expect UTC then the timestamps are a problem. The difference is then the difference to UTC depending on the timezone.
But as I said above, only from telemetry it is not possible to detect when exactly the copter started and when landed, thus flight duration are also incorrect because it contains time, the copter stands waiting on the ground.
br HE
Edit: One FlightLog file set may contain more than one flight. Batteriy change can be detected by voltage chart.
Location is alway correct in telemetry files. You have GPS data from copter in Telemetry_*.csv and GPS data from ST16S in RemoteGPS_*.csv. Usually the coptes coordinates are more precise. Altitude contains relative to start level. RemoteGPS has absolute altitude in.
I have proved that many times on different locations. Timestamps are taken from ST16S, local time. If time is set correctly the timestamps are also correct.
If a tool expect UTC then the timestamps are a problem. The difference is then the difference to UTC depending on the timezone.
But as I said above, only from telemetry it is not possible to detect when exactly the copter started and when landed, thus flight duration are also incorrect because it contains time, the copter stands waiting on the ground.
br HE
Edit: One FlightLog file set may contain more than one flight. Batteriy change can be detected by voltage chart.
Last edited: