This is not a bash Litchi thread. I really rely on it so I'm posting to help understand what could be a serious issue regarding something that's not supposed to happen.
One thing that has always given me confidence in waypoint missions is that they keep flying the mission even if signal is lost. It won't be stranded out there. Then this happened:
Flying a fairly short test mission around my house. Just testing POI and gimbal control. I've run it before although this is the first time since I installed the DBS mod. About half way through the mission - at a point where I have seen signal problems before (not sure why. it's not far and it's not over any houses) I am watching the iPhone display and before my eyes I see the top box switch from F-WP to Atti then back to F-WP then to Atti again and back to F-WP again. This all happens within a couple seconds. Then - and this is what bothers me the most - the AC just went into a hover. The green box says F-WP but it's not moving anymore. I move the gimbal to make sure things aren't frozen on my display and the camera moves. So I have full video and data downlink, full RC control but it's just hovering. I got no mission ended callout but then again I don't remember hearing any of my altitude and battery callouts either. Maybe volume was down. Anyhow whenever I've gotten those mission ended callouts the thing still continued the mission.
If I can't get to the bottom of this then I don't know if I can trust sending this on a waypoint mission that might lose signal if it's possible to get stranded out there. Any help analyzing this would be appreciated.
Here is the link to the phantom log viewer:
Phantom Log Viewer - PhantomHelp.com
Here is the airdata (healthy drones) link:
Airdata UAV - Flight Data Analysis for Drones
I'd be happy to provide any other info as needed.
Bill
Edit, I definitely did not accidentally flick the S1 switch. Oddly enough the phantom log viewer just shows it settling into P-GPS mode. I know for sure I was staring at F-WP in the display after that flip flop happened.
One thing that has always given me confidence in waypoint missions is that they keep flying the mission even if signal is lost. It won't be stranded out there. Then this happened:
Flying a fairly short test mission around my house. Just testing POI and gimbal control. I've run it before although this is the first time since I installed the DBS mod. About half way through the mission - at a point where I have seen signal problems before (not sure why. it's not far and it's not over any houses) I am watching the iPhone display and before my eyes I see the top box switch from F-WP to Atti then back to F-WP then to Atti again and back to F-WP again. This all happens within a couple seconds. Then - and this is what bothers me the most - the AC just went into a hover. The green box says F-WP but it's not moving anymore. I move the gimbal to make sure things aren't frozen on my display and the camera moves. So I have full video and data downlink, full RC control but it's just hovering. I got no mission ended callout but then again I don't remember hearing any of my altitude and battery callouts either. Maybe volume was down. Anyhow whenever I've gotten those mission ended callouts the thing still continued the mission.
If I can't get to the bottom of this then I don't know if I can trust sending this on a waypoint mission that might lose signal if it's possible to get stranded out there. Any help analyzing this would be appreciated.
Here is the link to the phantom log viewer:
Phantom Log Viewer - PhantomHelp.com
Here is the airdata (healthy drones) link:
Airdata UAV - Flight Data Analysis for Drones
I'd be happy to provide any other info as needed.
Bill
Edit, I definitely did not accidentally flick the S1 switch. Oddly enough the phantom log viewer just shows it settling into P-GPS mode. I know for sure I was staring at F-WP in the display after that flip flop happened.