[DJI-log-discuss] Welcome to the "dpi-log-discuss" mailing list

[Quaddy McDamage]

Either decompile the tool, or decompile Dji Go.

Probably better with Dji Go.
Use the "nosecneo" version. Search for strings like "DJIFlightRecord_" to
locate the correct class.
It will take some time to understand how the logging works, though. Most
symbols are obscured.

2018-08-15 2:23 GMT+02:00 Ross Finlayson <finlayson at live555.com>:

> Thank you for subscribing to this mailing list.  I hope you’ve found the
> “djiparsetxt” (and “generateKML”) utilities useful in analyzing your ‘.TXT’
> log files.  And if any of you have been able to improve upon the ‘reverse
> engineering’, please let us know.
>
> In particular, I’d like to figure out how to get the second half of the
> ‘scramble table’.  Right now, we have 0x1000 (i.e., 4096) rows of the table
> - which is enough to decode record types <= 0x10.  But this is only half of
> what we need.  We also need (at least) another 0x1000 rows - enough to
> decode record types 0x11 through 0x20.
>
> The (closed-source, Windows tool) “TXTlogToCSVtool.exe” is apparently able
> to parse “MC_PARAM” (0x13) and “APP_SER_WARN” (0x18) records - so it seems
> that they know how to get the second half of the ‘scramble table’.  (But
> unfortunately the developer of that tool has chosen not to reveal any
> details about this.)
>
> Any ideas?
>
>         Ross.
>
>
> --
> DJI-log-discuss mailing list
> DJI-log-discuss at lists.live555.com
> http://ns.live555.com/mailman/listinfo/dji-log-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ns.live555.com/pipermail/dji-log-discuss/attachments/20180815/5eba7f04/attachment.html>