From carlos.jillson at sinclair.edu Tue Jan 3 15:25:00 2023 From: carlos.jillson at sinclair.edu (Jillson, Carlos) Date: Tue, 3 Jan 2023 23:25:00 +0000 Subject: [DJI-log-discuss] Unix or GPS timestamps in TXT logs Message-ID: Hello to the mailing list, Trying to find a timestamp in Phantom text logs that I can sync up with Zulu time. I noticed comments referencing Unix timestamps in the documentation for the CUSTOM.updateTime and DETAILS.timestamp values. Uncertain about what exactly those two fields are. DETAILS.timestamp seems to have the same value down the entire column. CUSTOM.updateTime increments, but doesn't seem to be formatted the way I expect for a UNIX timestamp and does not seem to include milliseconds. I'm also interested in how closely the times recorded in the TXT logs correspond to the GPS timestamps output by DatCon/CsvView. Still trying to get djiparsetxt up and running and some of my issues might be related to my use of CsvView to generate what I have now. If that's the case, I'm still interested in hearing more about how the timestamps work as it relates to djiparsetxt. I'm using logs off an Android 7 tablet running a 2.3 version of Pilot and opening them in Excel after conversion. Aircraft is the WM331A and the controller is a GL300F. Thanks for giving this a read. Carlos Jillson Sinclair Community College -------------- next part -------------- An HTML attachment was scrubbed... URL: From finlayson at live555.com Tue Jan 3 19:05:25 2023 From: finlayson at live555.com (Ross Finlayson) Date: Tue, 3 Jan 2023 19:05:25 -0800 Subject: [DJI-log-discuss] Unix or GPS timestamps in TXT logs In-Reply-To: References: Message-ID: <217A6983-C412-4BA7-81E2-30B480F286CD@live555.com> > On Jan 3, 2023, at 3:25 PM, Jillson, Carlos wrote: > > Hello to the mailing list, > > Trying to find a timestamp in Phantom text logs that I can sync up with Zulu time. I noticed comments referencing Unix timestamps in the documentation for the CUSTOM.updateTime and DETAILS.timestamp values. > > Uncertain about what exactly those two fields are. DETAILS.timestamp seems to have the same value down the entire column. CUSTOM.updateTime increments, but doesn't seem to be formatted the way I expect for a UNIX timestamp and does not seem to include milliseconds. Of those two, ?CUSTOM.updateTime? is what you want. It?s an 8-byte little-endian value, in milliseconds. See line 39 of ?parseRecord_CUSTOM.cpp", and line 128 of ?parseFieldWithinRecord.cpp?. Ross Finlayson Live Networks, Inc. http://www.live555.com/