[DJI-log-discuss] Drone Type

[big dog]

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?

Thanks.


On Mon, Jul 27, 2020 at 10:47 AM Ross Finlayson <finlayson at live555.com>
wrote:

>
>
> > On Jul 27, 2020, at 12:19 PM, big dog <ifusereqtrue at gmail.com> wrote:
> >
> > Hi,
> >
> > I am troubleshooting the drone type information but struggling with my
> limited c++ knowledge. In my log the drone type is unknown, this is a mavic
> 2.
> >
> > I can see interpretationTables.cpp and i see mavic 2 is missing, am i
> right in assuming that an int is output and mapped to a string?
> >
> > Per my previous email about printing out information, i have put the
> following in the parseRecord_RECOVER.cpp at the top of the function:
> >
> > for (u_int8_t const* p = ptr; p < limit; ++p) fprintf(stderr, "PRINT
> DRONE HERE:%02x", *p);
> > fprintf(stderr, "PRINT DRONE: \n");
>
> Suggestion: Change this code to the following:
>         fprintf(stderr, "PRINT DRONE HERE:\n”);
>         for (u_int8_t const* p = ptr; p < limit; ++p) fprintf(stderr,
> “%02x:", *p);
>         fprintf(stderr, “\nDONE\n”);
>         exit(0);
>
> If you do this, you’ll see output that shows the very first RECOVER
> record, but none more.
>
> Send us the output that you see - between "PRINT DRONE HERE:” and “DONE”.
>
>
> 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/1ea1e0b0/attachment.htm>