Crash, Crash, Crash again!

Joined
Jan 2, 2017
Messages
9
Reaction score
0
Age
42
My solo has decided out of no where to start yawing/spinning out of control upon takeoff and control is unrecoverable. I can can get it to the ground but with it spinning it just crashes or flips. 4 crashes so far.

I have factory reset both the bird and the controller along with opening her up and checking all connections and still the issue persists. Any ideas what I should be looking for as the issue or how to troubleshoot without having to crash it again and again?

Upgrades to the bird are the mRo GPS and the microtek wifi cards.
 
It did fly right for at least a month with about 15+ flights.
I can pull the logs if needed and will provide more details.
 
Nothing changed. All mods had been used for at least 5+ flights.

I did run mission planner as I was working on balancing the motors. I thought maybe I clicked something in it that changed settings. But after the factory reset and still the issue, I don't think that's the case now.
 
Spinning is going to generally be motor related. Either a motor is not running up to speed or bad prop or other issue making 1 motor not providing needed thrust. A while back we had someone with a prop issue. Can't remember the details on it though.
 
  • Like
Reactions: pyrate
I tried 2 different prop sets and both had the issue. I have noticed one motor from the beginning though that was not as smooth as the other 3. Maybe I need to swap to T-motors already.
 
You have to be VERY careful when in Mission Planner. Also I'm not quite sure if doing a reset restores all of the factory settings. When connected to Mission Planner it's best to save current configuration to a file, before doing anything else. I've found sometimes I leave my mouse pointer in the wrong place, then try to scan down the page, and wind up changing a setting.
 
  • Like
Reactions: RichWest
There was a thread here awhile back from someone who discovered that a factory reset DOES NOT reset all parameters that could be changed in Mission Planner, etc.

If you were just turning your motors on and off for balancing, it's doubtful that you accidentally changed anything.
 
Try resetting the stock parameters.

Solo stock parameters reset procedure

Connect to the SoloLink WiFi network
Open Tower
Go to Menu >> Setting >> Telemetry Connection Type >> UDP
Go back to the main screen >> Click on Connect
Go to Menu >> Parameters
Look and change SYSID_SW_MREV to 0
From option on the top, select Upload (folder with Up arrow)
Disconnect and reboot Solo

After you do that, connect using Solo App and re do Compass and Level Calibration

(12:09 Made this a little easier to follow)
 
Last edited:
  • Like
Reactions: Edgarpro12
Did you save the default parameters before changing things?

When one is using MP the first thing to do should be saving the existing working parameters; then going back is easy.

Running through the motor tests listening and watching for differences should show if there is an motor issue.
 
I did not save the defaults unfortunately, as I was only going to play with the motors. I did check out most of the menus in MP though so it may be possible I clicked something accidentally.

I will reset to stock params using ZdroneZ suggestion and report back today.
 
To echo this very important advice from Frank Foster: "I've found sometimes I leave my mouse pointer in the wrong place, then try to scan down the page, and wind up changing a setting."

With Mission Planner, it is very easy to touch the scroll wheel on your mouse, and accidentally change the value of a parameter.
 
Jon,
The yaw is controlled by increasing or decreasing two of the motor RPMs in diagonal.
So basically depending on the IMU readings, the controller decides if there is an unrequested yaw, to stop it by increasing the throttle on the motors on one of the diagonals and decrease the throttle on the other two motors (the other diagonal). This change is usually done simultaneously for all motors so the Solo actually stays on the same altitude (assuming there is no controlled maneuver at that time).

The short story:

If you see the Solo unstable by roll and pitch:
- if you have somehow changed the gain on one of the motors
- defective or damaged ballbearing tightening only one of the motors
In the above cases the drone will try to stabilize using the other 3 motors, however a quad cannot perfectly balance only by 3 props (with the current level of DJI and 3DR tech :) )

If the Solo is stable by Roll and Pitch, but still do uncontrollable Yaw:
- defective IMU sensor or compass/GPS depending on the mode you are flying with.
You can try to compensate that in manual flight by introducing yaw in the opposite direction.

Nearly impossible causes:
- broken or cut prop - I can assure you that you cannot miss this issue. Each motor is doing about 3lbs (1.5kg) max thrust, so the controller have all that power to stop potential yaw. So unless half of the prop is missing, you are ok :)
 
I am happy to report that resetting the parameters as ZdroneZ suggested did the trick, and Solo is back in the air nice and stable. Thanks to all who helped me get out of this mess and provided great information.

I diffed out the changes in parameters vs the bad set, and default set (before level and compass calibration). Below are the bad settings that got updated if anyone wants to chime in as to which one in particular would cause this yaw/spin issue.

ACRO_BAL_PITCH , 0.250000
ACRO_BAL_ROLL , 0.250000
ACRO_RP_P , 5.600000
ACRO_YAW_P , 1.800000
AHRS_TRIM_X , 0.018147
AHRS_TRIM_Y , 0.008333
ANGLE_MAX , 2649.000000
ATC_ACCEL_P_MAX , 50400.000000
ATC_ACCEL_R_MAX , 50400.000000
ATC_ACCEL_Y_MAX , 12600.000000
COMPASS_DIA2_X , 0.968792
COMPASS_DIA2_Y , 1.067666
COMPASS_DIA2_Z , 0.969664
COMPASS_DIA_X , 1.056315
COMPASS_DIA_Y , 1.049558
COMPASS_DIA_Z , 0.970788
COMPASS_ODI2_X , -0.049564
COMPASS_ODI2_Y , -0.003396
COMPASS_ODI2_Z , 0.002920
COMPASS_ODI_X , 0.024735
COMPASS_ODI_Y , 0.010715
COMPASS_ODI_Z , -0.042192
COMPASS_OFS2_X , -38.827374
COMPASS_OFS2_Y , 84.543938
COMPASS_OFS2_Z , 86.246162
COMPASS_OFS_X , -85.999916
COMPASS_OFS_Y , 36.340153
COMPASS_OFS_Z , 123.691299
FENCE_ALT_MAX , 120.000000
FENCE_RADIUS , 0.000000
FRAME , 3.000000
GND_ABS_PRESS , 101203.351563
GND_TEMP , 24.269428
INS_ACC2OFFS_X , 0.059225
INS_ACC2OFFS_Y , -0.302268
INS_ACC2OFFS_Z , 1.028521
INS_ACC2SCAL_X , 1.035993
INS_ACC2SCAL_Y , 1.041044
INS_ACC2SCAL_Z , 1.004688
INS_ACC3OFFS_X , 0.093708
INS_ACC3OFFS_Y , -0.122340
INS_ACC3OFFS_Z , -0.818816
INS_ACC3SCAL_X , 0.999938
INS_ACC3SCAL_Y , 0.998889
INS_ACC3SCAL_Z , 0.992297
INS_ACCOFFS_X , 0.007829
INS_ACCOFFS_Y , 0.351049
INS_ACCOFFS_Z , -0.057026
INS_ACCSCAL_X , 1.007704
INS_ACCSCAL_Y , 0.995108
INS_ACCSCAL_Z , 0.989293
INS_GYR2OFFS_X , -0.003961
INS_GYR2OFFS_Y , -0.028506
INS_GYR2OFFS_Z , -0.029795
INS_GYR3OFFS_X , -0.022774
INS_GYR3OFFS_Y , -0.006698
INS_GYR3OFFS_Z , 0.003446
INS_GYROFFS_X , -0.001576
INS_GYROFFS_Y , -0.027051
INS_GYROFFS_Z , -0.011459
MIS_TOTAL , 3.000000
PILOT_ACCEL_Z , 180.000000
PILOT_VELZ_MAX , 240.000000
RC_FEEL_RP , 36.000000
RTL_ALT , 4800.000000
SR0_RAW_SENS , 20.000000
WPNAV_ACCEL , 340.000000
WPNAV_ACCEL_Z , 160.000000
WPNAV_LOIT_JERK , 1800.000000
WPNAV_LOIT_MAXA , 412.000000
WPNAV_LOIT_MINA , 163.000000
WPNAV_LOIT_SPEED , 900.000000
WPNAV_SPEED , 1100.000000
WPNAV_SPEED_DN , 240.000000
WPNAV_SPEED_UP , 320.000000
 
FRAME
I am happy to report that resetting the parameters as ZdroneZ suggested did the trick, and Solo is back in the air nice and stable. Thanks to all who helped me get out of this mess and provided great information.

I diffed out the changes in parameters vs the bad set, and default set (before level and compass calibration). Below are the bad settings that got updated if anyone wants to chime in as to which one in particular would cause this yaw/spin issue.

ACRO_BAL_PITCH , 0.250000
ACRO_BAL_ROLL , 0.250000
ACRO_RP_P , 5.600000
ACRO_YAW_P , 1.800000
AHRS_TRIM_X , 0.018147
AHRS_TRIM_Y , 0.008333
ANGLE_MAX , 2649.000000
ATC_ACCEL_P_MAX , 50400.000000
ATC_ACCEL_R_MAX , 50400.000000
ATC_ACCEL_Y_MAX , 12600.000000
COMPASS_DIA2_X , 0.968792
COMPASS_DIA2_Y , 1.067666
COMPASS_DIA2_Z , 0.969664
COMPASS_DIA_X , 1.056315
COMPASS_DIA_Y , 1.049558
COMPASS_DIA_Z , 0.970788
COMPASS_ODI2_X , -0.049564
COMPASS_ODI2_Y , -0.003396
COMPASS_ODI2_Z , 0.002920
COMPASS_ODI_X , 0.024735
COMPASS_ODI_Y , 0.010715
COMPASS_ODI_Z , -0.042192
COMPASS_OFS2_X , -38.827374
COMPASS_OFS2_Y , 84.543938
COMPASS_OFS2_Z , 86.246162
COMPASS_OFS_X , -85.999916
COMPASS_OFS_Y , 36.340153
COMPASS_OFS_Z , 123.691299
FENCE_ALT_MAX , 120.000000
FENCE_RADIUS , 0.000000
FRAME , 3.000000
GND_ABS_PRESS , 101203.351563
GND_TEMP , 24.269428
INS_ACC2OFFS_X , 0.059225
INS_ACC2OFFS_Y , -0.302268
INS_ACC2OFFS_Z , 1.028521
INS_ACC2SCAL_X , 1.035993
INS_ACC2SCAL_Y , 1.041044
INS_ACC2SCAL_Z , 1.004688
INS_ACC3OFFS_X , 0.093708
INS_ACC3OFFS_Y , -0.122340
INS_ACC3OFFS_Z , -0.818816
INS_ACC3SCAL_X , 0.999938
INS_ACC3SCAL_Y , 0.998889
INS_ACC3SCAL_Z , 0.992297
INS_ACCOFFS_X , 0.007829
INS_ACCOFFS_Y , 0.351049
INS_ACCOFFS_Z , -0.057026
INS_ACCSCAL_X , 1.007704
INS_ACCSCAL_Y , 0.995108
INS_ACCSCAL_Z , 0.989293
INS_GYR2OFFS_X , -0.003961
INS_GYR2OFFS_Y , -0.028506
INS_GYR2OFFS_Z , -0.029795
INS_GYR3OFFS_X , -0.022774
INS_GYR3OFFS_Y , -0.006698
INS_GYR3OFFS_Z , 0.003446
INS_GYROFFS_X , -0.001576
INS_GYROFFS_Y , -0.027051
INS_GYROFFS_Z , -0.011459
MIS_TOTAL , 3.000000
PILOT_ACCEL_Z , 180.000000
PILOT_VELZ_MAX , 240.000000
RC_FEEL_RP , 36.000000
RTL_ALT , 4800.000000
SR0_RAW_SENS , 20.000000
WPNAV_ACCEL , 340.000000
WPNAV_ACCEL_Z , 160.000000
WPNAV_LOIT_JERK , 1800.000000
WPNAV_LOIT_MAXA , 412.000000
WPNAV_LOIT_MINA , 163.000000
WPNAV_LOIT_SPEED , 900.000000
WPNAV_SPEED , 1100.000000
WPNAV_SPEED_DN , 240.000000
WPNAV_SPEED_UP , 320.000000

FRAME did you in.
Instead of a value of 1 which means an X configuration, your Solo thought it was an H frame and so your motor mixing was slightly off. :)
 
Jon,
The yaw is controlled by increasing or decreasing two of the motor RPMs in diagonal.
So basically depending on the IMU readings, the controller decides if there is an unrequested yaw, to stop it by increasing the throttle on the motors on one of the diagonals and decrease the throttle on the other two motors (the other diagonal). This change is usually done simultaneously for all motors so the Solo actually stays on the same altitude (assuming there is no controlled maneuver at that time).

The short story:

If you see the Solo unstable by roll and pitch:
- if you have somehow changed the gain on one of the motors
- defective or damaged ballbearing tightening only one of the motors
In the above cases the drone will try to stabilize using the other 3 motors, however a quad cannot perfectly balance only by 3 props (with the current level of DJI and 3DR tech :) )

If the Solo is stable by Roll and Pitch, but still do uncontrollable Yaw:
- defective IMU sensor or compass/GPS depending on the mode you are flying with.
You can try to compensate that in manual flight by introducing yaw in the opposite direction.

Nearly impossible causes:
- broken or cut prop - I can assure you that you cannot miss this issue. Each motor is doing about 3lbs (1.5kg) max thrust, so the controller have all that power to stop potential yaw. So unless half of the prop is missing, you are ok :)
I just had a crash that was the result of "Solo unstable by roll and pitch." I checked the rotation of the motors and motor 01 turned hard. When I spun the motor it freed and is the same as the others now. After the the crash, I found the Solo upside down in the dirt so something could have gotten in to the motor as a result of the crash but your post makes me think that something may have been in there that caused the crash.
 

Members online

No members online now.

Forum statistics

Threads
13,093
Messages
147,741
Members
16,048
Latest member
ihatethatihavetomakeanacc