My 2.5-week old Mavic 2 Pro has turned itself on twice. And I'm a new flyer ("pilot" would be a stretch at this point), having only flown a drone twice. I have flown RC airplanes. The last time it turned itself on was two nights ago (Saturday, 23Jan) after its last flight. I've powered it on at times on my desk since, but no flying.
Before trying to figure this out and before flying (low and safe) to try to replicate the problem, would it would make sense to save drone-generated data NOW so last Saturday's events don't get lost in a mountain of data or erased (not sure when new data starts to overwrite old)?
I've read here TXT files only record if the phone, controller, and drone are connected and, furthermore, TXT files only run from motor start to motor stop. So as the drone was off when it randomly started up and I'm pretty sure the controller was off, then the TXT logs might not be helpful (Go 4 was on as I was in its Editor). Though, TXT might have detected something odd at the end of the flight preceding the random power-up? But, DAT apparently logs from power on to power off and might have caught something odd either at the shutdown prior to the random start-up OR right at the random startup.
So, under Assistant 2 for Mavic/Log Export (normal mode) I exported all instead of just Saturday hoping going back to the beginning might help. It is apparently a 3 GB? DAT file. BUT, "Advanced Mode" has "Flight Record & Sensing," "Navigation," "Gimbal," "Camera," "FAM," "System 1," and "System 2" categories. Would any of these more likely be more helpful DATs than the "normal" mode export in figuring out a random turn-on problem??? If so, please let me know. And, am I thinking straight that DAT is the way to go seeing neither the drone nor controller were on so TXT wouldn't have caught the random power ups?
Thanks.
Before trying to figure this out and before flying (low and safe) to try to replicate the problem, would it would make sense to save drone-generated data NOW so last Saturday's events don't get lost in a mountain of data or erased (not sure when new data starts to overwrite old)?
I've read here TXT files only record if the phone, controller, and drone are connected and, furthermore, TXT files only run from motor start to motor stop. So as the drone was off when it randomly started up and I'm pretty sure the controller was off, then the TXT logs might not be helpful (Go 4 was on as I was in its Editor). Though, TXT might have detected something odd at the end of the flight preceding the random power-up? But, DAT apparently logs from power on to power off and might have caught something odd either at the shutdown prior to the random start-up OR right at the random startup.
So, under Assistant 2 for Mavic/Log Export (normal mode) I exported all instead of just Saturday hoping going back to the beginning might help. It is apparently a 3 GB? DAT file. BUT, "Advanced Mode" has "Flight Record & Sensing," "Navigation," "Gimbal," "Camera," "FAM," "System 1," and "System 2" categories. Would any of these more likely be more helpful DATs than the "normal" mode export in figuring out a random turn-on problem??? If so, please let me know. And, am I thinking straight that DAT is the way to go seeing neither the drone nor controller were on so TXT wouldn't have caught the random power ups?
Thanks.