1. 07 May, 2014 1 commit
  2. 06 May, 2014 1 commit
    • Bryant Mairs's avatar
      QGC data logging now records small MAVLink messages. · 321f21f2
      Bryant Mairs authored
      Previously MAVLink data streams recorded by QGC would use a fixed block size of the maximum MAVLink message length and fill in only the bytes written by the message. This wasted space, make manual parsing difficult, and broke compatibility with scripts provided in the MAVLink project (issue #174).
      
      This patch alters logging to output only a packed data stream (64-bit big endian unix timestamp in microseconds since epoch + MAVLink message) instead of the unpacked data stream previously output. Additionally the previous logging code used the system endianness for packing in the timestamp, this has now been switched to always be big endian regardless of platform. All the documentation specifies big endian, so the code now follows the docs here.
      
      Additionally data playback has been modified to playback both the new packed data streams as well as the old data streams, even those with improper endianness for their timestamps.
      
      Finally, a variety of bugs have been fixed, along with some additional features and user experience changes, hopefully for the better. All existing functionality has been preserved as well.
      321f21f2
  3. 14 Feb, 2014 1 commit
  4. 05 Nov, 2013 1 commit
  5. 26 Sep, 2013 1 commit
  6. 26 Aug, 2013 1 commit
  7. 16 Jul, 2013 1 commit
  8. 13 Jun, 2013 1 commit
  9. 10 Jun, 2013 2 commits
  10. 09 Jun, 2013 2 commits
  11. 14 May, 2013 2 commits
  12. 25 Apr, 2013 1 commit
  13. 17 Apr, 2013 1 commit
  14. 16 Apr, 2013 1 commit
  15. 11 Apr, 2013 1 commit
    • Christopher Hrabia's avatar
      Revert last change on new logfile structure and added nulling of buffer. · 50c36bb5
      Christopher Hrabia authored
      The reason for this is, because the last change in the file structure is buggy, it was only written the message length of the buffer to the file and missed to add the length for the timestamp.
      For fixing this problem it would be possible to insert something like
      
      len += sizeof(quint64);
      
      after:
      
      int len = mavlink_msg_to_send_buffer(buf+sizeof(quint64), &message);
      
      But I think a consistent file structure has more adavatages for a logfile over a more compressed structure.
      E.g. it would be necessary to go through all packages to proceed a jump during a replay.
      Additional the LogPlayer was not updated during the last 7 month since the logfile structure was changed (even it was buggy)...
      
      If filesize is really a problem I would recommend to change the logfile handling in a way of writting a temporary consistend
      logfile and compress it afterwards (QCompress) like done by many programs
      50c36bb5
  16. 16 Sep, 2012 1 commit
  17. 13 Sep, 2012 2 commits
  18. 07 Sep, 2012 1 commit
  19. 17 Apr, 2012 1 commit
  20. 06 Mar, 2012 1 commit
  21. 01 Mar, 2012 1 commit
  22. 26 Feb, 2012 1 commit
  23. 20 Feb, 2012 1 commit
  24. 18 Feb, 2012 2 commits
  25. 14 Feb, 2012 1 commit
  26. 13 Feb, 2012 1 commit
  27. 08 Feb, 2012 1 commit
  28. 07 Feb, 2012 1 commit
  29. 11 Jan, 2012 1 commit
  30. 09 Jan, 2012 1 commit
  31. 12 Dec, 2011 1 commit
  32. 10 Dec, 2011 2 commits
  33. 09 Dec, 2011 1 commit
  34. 07 Oct, 2011 1 commit