Phantom 4 Advanced. Today I had the drone on a table inside with props on and motors spinning (just idling). Controller and GO4 app all connected as well at same time.
The avoidance sensors were beeping at me as about 1m in front of the drone was an object. The sound was annoying me. So, in the Go4 app I turned off the sensors. All good the beeping stopped.
After a while I decided to turn the sensors back on. It wouldn't. I set the sensor slider to green (on) and it looked like it was on but once I closed the screen and went back in to check it was deselected again. So I repeated this a few times trying to turn on the sensors again. Same thing happened over and over (looked on but back out and back in - it was still off).
It is at this point and randomly I got a warning message (now in atti mode) and then all of a sudden the motors turned off and props stopped spinning. The drone had shut the motors off without input from controller sticks or Go4 app. Incidentally, I could now turn on the sensors again properly (the setting stuck this time while motors were stopped).
At the time I just thought that's really odd and like some bug perhaps. Then a scary thought made me consider this some more... is there any 'feature' in the phantom 4's that could possibly automatically and without input from sticks or Go4 app (auto land for eg), turn off the motors while spinning/ideling (like a timeout feature if motors started but not taken off after a certain time its auto stops the motors). Alternatively what caused the motors to randomly shut down without being instructed to. BTW battery was at 60% and cells were perfectly aligned at the time (new battery).
The scary part if this can not be explained leads me to think software bug in Go4 app caused motors shut down while spinning (what if it was in the air at the time).
I am going to try and repeat the steps that led to this just out of curiosity but hoping someone can explain a simple cause.
The avoidance sensors were beeping at me as about 1m in front of the drone was an object. The sound was annoying me. So, in the Go4 app I turned off the sensors. All good the beeping stopped.
After a while I decided to turn the sensors back on. It wouldn't. I set the sensor slider to green (on) and it looked like it was on but once I closed the screen and went back in to check it was deselected again. So I repeated this a few times trying to turn on the sensors again. Same thing happened over and over (looked on but back out and back in - it was still off).
It is at this point and randomly I got a warning message (now in atti mode) and then all of a sudden the motors turned off and props stopped spinning. The drone had shut the motors off without input from controller sticks or Go4 app. Incidentally, I could now turn on the sensors again properly (the setting stuck this time while motors were stopped).
At the time I just thought that's really odd and like some bug perhaps. Then a scary thought made me consider this some more... is there any 'feature' in the phantom 4's that could possibly automatically and without input from sticks or Go4 app (auto land for eg), turn off the motors while spinning/ideling (like a timeout feature if motors started but not taken off after a certain time its auto stops the motors). Alternatively what caused the motors to randomly shut down without being instructed to. BTW battery was at 60% and cells were perfectly aligned at the time (new battery).
The scary part if this can not be explained leads me to think software bug in Go4 app caused motors shut down while spinning (what if it was in the air at the time).
I am going to try and repeat the steps that led to this just out of curiosity but hoping someone can explain a simple cause.