We just modified RNGFND1_TYPE to 0 and then reboot the pixhawk. After rebooting, drone armed on its own and seemed to reach max throttle within seconds (crashed as 2 arms were below a bench). RC switch was on disarm with throttle down. We tried to disarm with RC by flipping arm disarm switch a couple of times. It did not work. It stopped on its own after sometime.
Prearm checks were ON
Attached the log file
2026-02-24 17-04-45.bin (521.6 KB)
Please help to ascertain the cause.
For some reason there are no ARM messages in the log. Also all of the RCOU channels are set to 0 so not sure how motors are spinning, unless you’re using CAN ESCs? There’s no current spike at all either to indicate the motors being on. CTUN.THo (Throttle out) is also set to 0 throughout the entire log.
Did u post the correct log file?
Yes, the log file is correct.
Here is the complete turn of events
Our range finder was faulty. U can see in attached image rangefinder1: No data.
So, we decided to turn it off. We used mavproxy on jetson nano which was on drone connected with FC. Jetson was accessed on terminal through SSH. We routed the mavproxy –out on laptop and connected on mission planner on laptop. Modified the parameter. Rebooted the pixhawk and motors turned ON.
Attached image is from 2nd last log file and this is the link of 2nd last log file on FC: https://drive.google.com/file/d/1oh7uI_7-mlyj0XRdJkcEhpFRNlKDjboY/view
Motors turned on in which log file? If it is first log, then are you using dronecan escs since there’s no RCOU data.
What ESCs are in use? If they run BlHeli32, there is a bug that may be present that can result in spontaneous full throttle at power-up.
Remove the access requirement from the link.
Yeah…removed the access requirement
We are using T motor Air 40 Esc
Not much to see in these logs. The Arm switch is initially high for both and there are no motor outputs being commanded. And as noted there is no ARM field in the log which is odd with the default bitmask.
