Skip to content
  1. May 06, 2014
    • 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
  2. Feb 14, 2014
  3. Nov 05, 2013
  4. Sep 26, 2013
  5. Aug 26, 2013
  6. Jul 16, 2013
  7. Jun 13, 2013
  8. Jun 10, 2013
  9. Jun 09, 2013
  10. May 14, 2013
  11. Apr 25, 2013
  12. Apr 17, 2013
  13. Apr 16, 2013
  14. Apr 11, 2013
    • 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
  15. Sep 16, 2012
  16. Sep 13, 2012
  17. Sep 07, 2012
  18. Apr 17, 2012
  19. Mar 06, 2012
  20. Mar 01, 2012
  21. Feb 26, 2012
  22. Feb 20, 2012
  23. Feb 18, 2012
  24. Feb 14, 2012
  25. Feb 13, 2012
  26. Feb 08, 2012
  27. Feb 07, 2012
  28. Jan 11, 2012
  29. Jan 09, 2012
  30. Dec 12, 2011
  31. Dec 10, 2011
  32. Dec 09, 2011
  33. Oct 07, 2011
  34. Sep 20, 2011
Loading