[attachment=1]vibrations flight 1a.jpg[/attachment]
[attachment=2]power flight 1a.jpg[/attachment]
As in the title, I graphed out Power and vibration issues from the drop down list in mission planner. I apologize for the blurriness, I’m running mission planner in a VM on a Mac Retina screen and had to reduce the resolution to get them to upload…
Does this show that I lost power and had a massive vibration as well?
Thank you for looking,
Steve
Please post .log file , not .tlog.
Hmm, Sorry about that, wrong file.
both voltage and currtot(next value) is 0 at that one line, most likely some logging/writing glitch. I would not think too much about it.
Andre-k,
Thank you for the quick reply and help!
Are you sure?
I ask because I am having an issue where my Iris just flys off with no ability to regain control.
Unfortunately, the crashes have only produced zero length files.
So I’m trying to use successful flights to diagnose.
I’m a little hesitant to fly it at all, because I’m worried it won’t hit something and I’ll lose it! How ironic is that? 
I’d like to see what 3dr thinks of it too, because of the nature of what’s happening and any possible bug or warranty issues.
Thanks man,
Steve
yes, I am sure, this goes in the same category as your IMU line:
IMU, 817210, -0.07072348, -9.863644, 8.50345E-25, 2.659501E+36, 7.541347E-29, -5.969283
The insane huge/small values are some sort of error we see , and your voltage/currenttotal zero are probably just 0 because thae are forced into a smaller variable.
If your currentotal, for example - actually were 0 once, it would just start increasing from 0 again.
I do, hovever see small spikes in currenttotal - and have no clue on that variable can drop after those spikes,
Usually one would say that currentotal = currentotal + capacity_used_since_last_time. - so unless capacity used is a negative value - this makes no sense.
so maybe a dev should look at it.
Regarding flyaways, - magnetometer, proper GPS fix are usually the problem, impossible to comment without .log.
I had better luck on complete, fine logs without arifacts with another microSD.
Andre,
Nice explanation, thank you!
Yeah, I figured early on that it might be a GPS issue and LTR, so I stopped using LTR and have stayed in STAB or ALT ever since, unfortunately I still had the issue, so I researched the compass and default settings and reset the params back to Default, although I had only changed the logging levels, and retuned the compass.
So now I’m basically just waiting to see what happens and hope that if it happens again I’ll get logs.
I’ll try a new card as you suggested, do you have a recommendation?.
Thanks,
Steve