[DJI-log-discuss] Drone Type

big dog ifusereqtrue at gmail.com
Tue Jul 28 01:41:51 PDT 2020


Hi Ross,

Thanks for detailing this, appreciate it.

Let me parse some more logs, that particular sample was someone else. I
have been parsing mavic2 logs that come back as unknown, i'll play around
with known device logs to be sure using your code sample.

Let me get back to you on this one.

Thanks.

On Tue, Jul 28, 2020 at 6:33 PM Ross Finlayson <finlayson at live555.com>
wrote:

>
>
> > On Jul 28, 2020, at 6:33 PM, big dog <ifusereqtrue at gmail.com> wrote:
> >
> > Hi Ross,
> >
> > Thank you and done:
> >
> > PRINT DRONE HERE:
> >
> 02:01:03:01:17:30:33:5a:31:34:33:37:31:33:34:00:00:00:00:00:00:52:65:64:20:43:61:74:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:d8:a3:b4:81:5b:01:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:30:35:4c:55:30:31:39:39:53:50:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:b8:
> > DONE
> >
> > How does one convert the output to something readable?
>
> It’s already readable - as binary data, displayed in hexadecimal.
>
> For example, the first byte - RECOVER.droneType.RAW - is 0x02
>
> The second byte - RECOVER.appType.RAW - is 0x01
>
> The next three bytes - RECOVER.appVersion - are 0x03 0x01 0x17 (in
> little-endian order).
>
> Etc.
>
> Our code (in “interpretationTables.cpp”) currently thinks that a
> “RECOVER.droneType.RAW” value of 0x02 means "P3 Standard”.  If that’s not
> correct, let me know, and I’ll update the code.
>
>
> Ross Finlayson
> Live Networks, Inc.
> http://www.live555.com/
>
>
> --
> 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/20200728/a1316552/attachment.htm>


More information about the DJI-log-discuss mailing list