Unexplained crash with 2.74b , need help

Hey Guys

Just came back from flying field after a bad unexplained crash. it was a new flying wing airframe and started this morning by following the manual on roll/pitch and yaw tuning.  First of we calibrated the Baro meter to report 0 meters on the ground and then we calibrated the airspeed sensor. What was strange was that we had to lower the airspeed ratio to 0.1 to get the airspeed sensor to report 0 ms a sec. ( my main opinion for the crash)

We proceeded with the first test fly by wire A to see if the roll and pitch was working correctly. we saw that the reaction time was very slow and I proceeded to try change the rate for this. Before i could change anything loiter seemed to pick its own direction and headed full speed( 144kmp) in that direction. when we switched to RTL the plane made two loops in the air and crashed. can anyone look at the Tlogs and confirm reason for crash? the red block below shows the uncontrolled flight path before crash.

totalflight.jpg?width=700

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

Join diydrones

Email me when people reply –

Replies

  • Hi,

    I think nobody else wrote this (here): A not quite zero airspeed reading while the plane is stationary is okay. It just has to agree with groundspeed at flight speeds and at no wind.

    The reason for the nonzero readings is that the airspeed is proportional to the square root of the ram pressure. The square root of a very small number is a not really so small number, so even the slightest sensor noise near zero will calculate to a few km/h.

    EDIT: Okay a 10 m/s reading on the ground is not normal.

    Regards

    Soren

  • Developer

    Hi Johann,

    That isn't version 2.74b, it looks like version 2.73.

    What was strange was that we had to lower the airspeed ratio to 0.1 to get the airspeed sensor to report 0 ms a sec. ( my main opinion for the crash)

    yep, that was indeed the main issue. The smallest reasonable ARSPD_RATIO is 1.0. It means the airspeed was reading completely wrong and you're plane didn't really stand a chance.

    To fix the zero you need to redo the airspeed preflight calibration (there is a menu item in mission planner for preflight calibration). Reducing the ratio isn't the right fix.

    Cheers, Tridge

  • Johann, You were right in your theory about the air speed  cal being wrong. From your own words you set the airspeed ratio to get zero on the ground. You need to re read the instructions

    I didn't plot any graphs, just played back you tlog. You air speed was working on the ground whist your plane was sitting pointed into the wind, ~ 4 m/s from NNE?  I fast forward to where you started flying and saw an AS of ~-4 m/s, due to your calibration  error. This surely did mess with any navigation modes(loiter, auto), but not FBWA or STAB.

    There is some confusion on the modes you where in. After the loiter where it was heading south with a strong wind, it entered stab, then manual, did some unplanned aerobatics and finally leveled out heading southwest and probably at a range where you could not see it very well from behind. It briefly went to STAB mode and then to a short failsafe. You lost your TX at ~ 385 meters and kinda started turning back, then it must have got signal again and you were in FBWA and surely couldn't see it at 667 meters. Did you crash into a swimming pool?

    I always have audible  alerts from the MP using a usb loud speaker on my GS computer. I can here it from 50 ft. I consider it a necessity for safe operations. Or you need a reliable assistant on the GS while the pilot keeps the plane in view. Don't have a spotter what the plane and you operating the GS with the TX around your neck.

    Any how be safe and preplan a little better. There is a lot that can go wrong very quickly. You need to be prepared, I have never crashed due to auto pilot errors, not because I haven't had any, but because I was always ready to fly in manual mode. And always have a plight plan set up around your field and use AUTO instead of LOITER. It can get crazy easier if things are not tuned.

    Good luck and be safe.

  • Never mind I think I have it now

    2013-09-15 16-59 174.log

  • Pieter please explain how and i will do it
  • Johan, Pieter

    Here are the two logs on the flash that i can see in the same time our fly way / crash happend.

    If it is not the correct one please tell me and i will look for the correct ones

    2013-09-15 08-21-02.rlog

    2013-09-15 08-21-02.tlog

    https://storage.ning.com/topology/rest/1.0/file/get/3692830275?profile=original
  • The thing is.. in the params I extracted from your log the airspeed ratio is 1.9936..
    Do you have a dataflash log? The telemetry log graph in missionplanner is a PITA to work with.

This reply was deleted.

Activity

DIY Robocars via Twitter
Videos from the ICRA autonomous racing workshop are now available: https://linklab-uva.github.io/icra-autonomous-racing/
yesterday
DIY Robocars via Twitter
RT @SmallpixelCar: Prepared race track for Warm Spring Raceways @wsraceways and looking forward to test my new car at RAMS RC @ramsaicar fa…
Jun 6
DIY Robocars via Twitter
RT @f1tenth: Trying out some nasty blocking maneuvers 🏎️🤖 #f1tenth #autonomousracing https://t.co/nMTstsaogM
Jun 5
DIY Robocars via Twitter
May 27
DIY Robocars via Twitter
RT @araffin2: I will talk this Saturday from 18:00 to 19:00 Paris time for the @diyrobocars community about learning to race in hours using…
May 27
DIY Robocars via Twitter
RT @a1k0n: Luckily the infeasible hairpin problem was easily reproducible in simulation and I could test the fix before bringing the car ba…
May 26
DIY Robocars via Twitter
RT @a1k0n: Another problem was that I was over-constraining the car's allowed accelerations, so it didn't think it could turn as tight as i…
May 26
DIY Robocars via Twitter
RT @a1k0n: Breaking the map up into two halves worked, but I had to be more careful about separating the inner track from outer. There's se…
May 26
DIY Robocars via Twitter
RT @a1k0n: Here's a datalog for my fastest lap of the day. Lap timer is tiny window lower-left. https://t.co/myrlWWrKUY
May 26
DIY Robocars via Twitter
May 26
DIY Robocars via Twitter
RT @a1k0n: Here was my car's POV. Man this track is confusing in first-person! After the incident my camera was all scuffed up and I was af…
May 23
DIY Robocars via Twitter
RT @circuitlaunch: Loved seeing so many familiar (masked) faces at Circuit Launch today for our first in person @diyrobocars in over a year…
May 22
DIY Robocars via Twitter
RT @circuitlaunch: Last but not least, mystery guest @BostonDynamics Spot took to the track @diyrobocars He enjoyed the #brazilianbbq too 😂…
May 22
DIY Robocars via Twitter
RT @SmallpixelCar: Today’s race @circuitlaunch for @diyrobocars with @a1k0n Was busy in the morning and did not get a chance to tune camera…
May 22
DIY Robocars via Twitter
RT @a1k0n: This was epic. My car was barely working this morning, had to make a lot of changes and extremely dirty hacks. Post-race analysi…
May 22
DIY Robocars via Twitter
DIY Robocars @ Circuit Launch, 3/7/2020 https://twitch.tv/diyrobocars
May 22
More…