search

mavlink / qgroundcontrol

Cross-platform ground control station for drones (Android, iOS, Mac OS, Linux, Windows)
http://qgroundcontrol.io
3.28k stars 3.61k forks source link

Flight Data Replay Runs at 6 Times Faster #6791

Closed rollysing closed 5 years ago

rollysing commented 6 years ago

The *.mavlink telemetry file is played at six times faster than normal speed. This is true with current stable v3.4.0 and tried it with v3.3.2, 3.3.0, 3.2.0. Had to go back to v3.0 for it to play in normal speed as default. Tried this in Windows 8.1 and 10 Pro PCs. Attached is the mavlink file and video. Telemetry was created with Pixhawk 1, PX4 v1.6.5 (I think).

032817 Ranger EX QGC VTOL.zip

https://youtu.be/_w3TQu-kGQA

Please advise.

Thanks,

Antiheavy commented 6 years ago

Replay is super convenient (logs already stored locally) and useful. A place for ideas for future improvements could be this old feature request: https://github.com/mavlink/qgroundcontrol/issues/5730

DonLakeFlyer commented 6 years ago

Hmm, possibly a windows only thing (which would notbe unusual). I've been using replay a bunch on OSX, Linux without problems.

DonLakeFlyer commented 6 years ago

I tested window using a log file generated from SITL flight and it worked fine. The problem seems to be specific to the attached log files. How are you getting these telemtry log files with a .mavlink extension? QGC hasn't used that extension for a while now.

rollysing commented 6 years ago

That was generated Mar 28, 2017. As mentioned, I had to go back to QGC v3.0 so it replays at normal speed. So, you're saying that if I generate a new log with the new version that its replay would be normal? If that's the case, then I'll try it next time I fly. Thanks.

DonLakeFlyer commented 6 years ago

So, you're saying that if I generate a new log with the new version that its replay would be normal? If that's the case, then I'll try it next time I fly. Thanks.

I believe so. Log replay was pretty screwed up for a while. But in the last 6 months or so I've cleaned it up. So I can see how really old logs might be strange.

DonLakeFlyer commented 5 years ago

@rollysing I believe this has been fixed. If you can reproduce with log files created from latest daily builds you can reopen.