3.6.0-rc1 Unable to disarm using RC or by waiting (auto disarm)


I’m not sure if this is related to 3.6.0* update, but I haven’t seen this before.

I had an issue where the drone was not able to disarm after landing, but kept looping following states until remote disarm or taking off back to air.

2018-06-08 16:02:16.132 DATA_LAND_COMPLETE_MAYBE
2018-06-08 16:02:17.015 DATA_LAND_COMPLETE
2018-06-08 16:02:17.026 DATA_NOT_LANDED
2018-06-08 16:02:17.331 DATA_LAND_COMPLETE_MAYBE
… and so on…

Only way to disarm the drone was to use MissionPlanner Actions to call remote disarm.

On the chart the red is EV.id and green line is CTUN.Alt.

What could cause this kind of behavior? What to do to avoid that?

Could some one tell me more about this parameter PILOT_THR_BHV and could it help in this kind of situations. PILOT_THR_BHV was 0 at that time.

Please see LOG.

I’m having trouble disarming as well…I had replaced my esc’s…no other change…I was using 3.5.x at the time, now I’m on 3.6…same thing happens…can’t disarm.

Maybe Pixhawk is not recognizing a low enough throttle position? I’m using a Taranis X9D, with a spring-center throttle.

In the past I was able to disarm just fine.

OK…maybe I just figured it out…I recalibrated the radio/sticks/switches, and now I can disarm just fine…must have had something to do with changing the ESC’s…I had DJI e300’s, and switched to a Lumenier 4-in-1 50a x 4:

Nevermind…I can’t disarm again.