Sean-bumble-bee
Captain
Flight distance : 15997 ft
United Kingdom
Offline
|
DAT's run from drone switch-on to drone switch-off. The next drone switch-on starts a new DAT.
txt's run from motor start to motor stop. The next motor start starts a new txt.
If you sync you may lose DATs.
Some time-stamps are in the 24 hour clock and others are in the 12 hour clock, this can be confusing if you sort them by their time-stamps.
Here, UK, some time-stamps differ by 1hr which may be the due to GMT vs BST (local summer time) (I think this is connected to the time zone connected to GPS but am not certain.)
If you open the .txt with the likes of CsvView you will see, and or find, that the DAT number is referenced, either or both, in the summary presented by CsvView or in the csv that is available from CsvView. (Look for "index").
i have never worked out conclusively what happens if a flight spans a disconnection but I may have separated flights and disconnections mixed up in my head.
I think I sometimes get a pair of DATs for one switch on, one being tiny and the other large. I do also sometimes get two DATs, of equal size, with one being in the 24hr clock and the other being in the 12hr clock, this is separate from the 12hr vs 24hr clock noted in line 4. (These may depended on the phone and or the app version used, I have several phones that I use with Go4.)
If you are looking at the numbers in the names of the DAT's remember, the DAT-name's number increments when the drone is switched on irrespective of whether or not a phone or the controller is connected.
DAT's and txt's are recorded to the phone ONLY when the phone is in contact with the drone, if the phone is not connected for an entire log then the log is, I think, lost.
Also, an RC1A controller ceates DAT's, an RC1B cintroller does not.
From memory a secondary controller does not create a DAT and might not create a .txt/
|
|