-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
INAV 7.1.0 failed to turn off motors when disarm the quadcopter #10009
Comments
I would like to add that I am using a DJI remote with original air unit. |
In the video it looks to me like the props stopped? |
Also, could you please attach your diff. |
Hello sensei-hacker, believe me when I tell you that it fell with the motors running and began to jump and bounce until the battery was fired and it separated from the drone. If you pay attention, the left arm seems stopped but the right one can be seen rotating. I'm attaching it too. a photo of my thigh a stopped engine can't do this |
Ouch! I believe you. Just double checking because the video looked stopped - but the limited frame rate of video can do that. Got a diff? |
INAV_7.1.0_cli_20240506_202528.txt this file is the diff |
Not being able to disarm is usually caused by being in failsafe. Was there any indication failsafe was active which would have triggered a RTH (probably RTH landing given it was at the home position) ? |
Not that I know of, I had not yet activated position hold, when I noticed that it was going up without control and did not respond to the motor stick, I activated the disarm switch |
I have watched the video again in slow motion and it seems that if the motors stop until it hits the floor and there they are activated again and it flip over. After that I heard the motors working and I could feel it hit in many places until I felt it hit the thigh and then stopped when the battery came off |
You're right, the motors did stop spinning in the video then started again when it landed upright on the floor. So it did disarm but then somehow managed to rearm. Are you sure you didn't accidently rearm again ? |
I doubt I was able to activate it again, the only thing I can add is that in addition to the propellers damaged, two GPS/MAG cables were cut, well I guess I'll repair it and try again in an open space to see how it behaves. |
The only way I can see that it rearmed is if the RC link was lost when it hit the ground and the Arming channel changed to the arm state before Failsafe kicked in. I've had this happen before when the Arming channel wasn't set up properly (The plane was disarmed on the ground when I switched the radio off by mistake causing it to ream and try and do a failsafe RTH) Is this possible ? |
I don't know, I can't guarantee this. I checked the DJI log and until the last moment the battery was disconnected, they reported that the RC was on ch 4. but in fact the motors are activated when it hits the ground, I was also able to observe with filmora9 that when it is falling I have my hands on the sticks |
are you using dji rc? |
yes I am using a DJI FPV Remote Controller V1 |
now that I think about it . That the drone has started to rise uncontrollably and that it could be due to interference from satellites here in Israel? Since the only thing I had activated was PH and that INAV 7.1, which does not require the barometer? since before it was always very stable |
Hello, I have a quad with Matek 722-SE that has already flown about five times very well and stable with a lot of stability, the position and altitude hold, today when I wanted to fly it it shot out of control and I immediately used the switch to disarm it, it started to go down but the engines did not turn off as expected and it fell backwards with the engines at maximum, bouncing and jumping across the floor, even causing me some cuts on my thigh, until it stopped when the battery came off. I want to comment on this because it bothered me. It seemed very strange that the engines were not turned off, the only thing I can add is a video with what happened because the FC did not have a memory card at that time
https://youtu.be/KZ1lo_wYR_I
The text was updated successfully, but these errors were encountered: