-----BEGIN PGP SIGNED MESSAGE-----
On 11/20/07, mark gross <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 15, 2007 at 10:11:02AM -0800, Jamey Sharp wrote:
> > 4-byte big-endian "ID"
> > 4-byte big-endian timestamp
> > 8 bytes of data
> OK, so now looking at the Rocketview_20050820.log using hexedit which lists
> out the data in 18 byte chunks.
You meant 16, surely.
> I'm not seeing the above record format ...
`hexdump -v 20050820.log` shows me one sensible-looking message per
line, though AFAICT it treats the input as native-endian and can't be
forced to big-endian.
> > Data length is limited to the range 0..8. If RTR is 1, there is no
> > actual data, but the length field can still be in the range 0..8. If RTR
> > is 0, the first "length" bytes of the data have valid data in them.
> Does this mean the record length is variable or the valid data in the
> fixed length record varies?
The amount of valid data varies.
By the way: If you're going to insist on reading the raw data yourself,
you may find useful this list, of record numbers where the flight
computer rebooted and the value of 'jiffies' goes back to near zero. I
used it with csplit.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
-----END PGP SIGNATURE-----
psas-software mailing list