Hi,

I was flying a new quadcopter on Friday to test the Auto flight mode. I had a successful first mission and I tried to replicate it. Since my last waypoint was facing the opposite direction from takeoff and the RTL kept this heading, I manually rotated the copter to face the initial takeoff heading. In that moment I saw that the EKF text in my flight HUD became red, and when I clicked it I saw that the velocity bar was completely filled with red (the image below is just for reference since I don't know how to replicate it).

2427b16e369a17aeac2ff1315f91a6ddedea7974.png

After that, I waited a couple of minutes since I knew I couldn't fly with that error. The red bar disappeared and it all seemed normal, so I changed to Alt. Hold in order to arm, and then to Auto to repeat the mission from the beginning.

A couple of seconds after taking off I saw again the velocity bar completely filled with red, and when the copter reached my target altitude (20 m), it started going sideways (in a completely random direction), instead of going forward to the first waypoint. I had no other option but to change it to Alt. Hold, take back control and land the copter manually. Luckily, nothing worse happened.

Finally, I restarted the Pixhawk by unplugging and plugging the batteries and it all went back to normal. I did 2 more Auto missions without any issues and that was it.

Moreover, I found this post reply which shows something similar to what happened to me, but in his case, it was combined with compass errors, which I don't have. What he mentions regarding velocity errors is that he has a peak in the speed measured by his GPS. It appears that I also have that peak during takeoff.

3691348899?profile=original

I'm worried since this was completely random and it could have been really bad hadn't I changed the flight mode to manual. Is there a way to prevent this issue? Is there an explanation to this? I hope you can help me shed some light on this issue (the flight log is attached). Thanks a lot in advance.

2017-06-30 16-24-53.bin

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Activity

DIY Robocars via Twitter
Sunday
DIY Robocars via Twitter
Saturday
DIY Robocars via Twitter
Saturday
DIY Robocars via Twitter
RT @f1tenth: Say hi to our newest #F1TENTH creation for @ieee_ras_icra next week in Philly. It’s going to be huge! 😎 🔥 @AutowareFdn @PennEn…
Saturday
DIY Robocars via Twitter
May 11
DIY Robocars via Twitter
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Noticed my car zigzagged in last run. It turned out to be the grass stuck in the wheel and made the odometry less accura…
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Test my car. RTK GPS worked great. Thanks @emlid for their support. https://t.co/EkQ6qmjmWR
May 8
DIY Drones via Twitter
RT @chr1sa: @kane That's @diydrones circa 2009. Still have a box of those Canon cameras that we used to strap into planes, just like this.…
May 3
DIY Robocars via Twitter
RT @chr1sa: Our next @diyrobocars race is going to be outside at a real RC racetrack in Fremont on May 28. Fully autonomous racing, head-to…
Apr 30
DIY Robocars via Twitter
RT @f1tenth: Our Spring 2022 F1TENTH course @PennEngineers is coming to an end with a head-to-head race as a big finale. So proud of our st…
Apr 26
DIY Robocars via Twitter
RT @DanielChiaJH: I wrote a thing! Throughout the development of my @diyrobocars car I've been using @foxglovedev Studio to visualize and d…
Apr 23
DIY Robocars via Twitter
RT @SmallpixelCar: My new car for high speed. Low body, everything ( @NVIDIAEmbedded Jetson Xavier NX, @emlid RTK GPS, IMC) under the deck…
Apr 23
DIY Robocars via Twitter
Apr 21
DIY Robocars via Twitter
RT @f1tenth: F1TENTH Race training setup @PennEngineers for our upcoming ICRA2022 @ieee_ras_icra competition. @OpenRoboticsOrg @IndyAChalle…
Apr 21
DIY Robocars via Twitter
RT @fatcatFABLAB: Proud to be hosting a restarted DIY Robocars NYC Meetup April 26. Come by if you want to talk about and race self-driving…
Apr 17
More…