Test flying my recently returned P3P after a gimbal board failure is proving to be scary. The a/c came back with version 1.8 on the RC and 1.5.30+ on the bird. The app on my iPad WiFi only mini is 3.1.4.
First time out I became a bit nervous when the No Image Transmission warning came up for several seconds with an imageless view on the mini. After a short flight I noticed while checking settings that the image on the mini was doing a some kind of refresh from the top of the screen down every 4 or so seconds; this would dissolve into a pixilated partial green screen very briefly. I examined the video and it looks to have shown up on the SD card(not the colored artifact but the interruption/refresh looking anomaly. I have a tin can and string internet connection so rather than go to a friend's house to update firmware for the GO app I decided to re-link the controller. During the flight test all imagery looked normal and I used auto takeoff. I went to rotate and got no response. all stick inputs were ignored and thankfully it remained at a 6 foot hover, having taken off from a card table. I couldn't get it to shut down and wound up having to pull the battery after grabbing the landing gear. this resulted in a motor overheat warning. I will be heading over to that friend's house to try to update the GO app later but thought I'd ask here if anyone else had seen this issue.
First time out I became a bit nervous when the No Image Transmission warning came up for several seconds with an imageless view on the mini. After a short flight I noticed while checking settings that the image on the mini was doing a some kind of refresh from the top of the screen down every 4 or so seconds; this would dissolve into a pixilated partial green screen very briefly. I examined the video and it looks to have shown up on the SD card(not the colored artifact but the interruption/refresh looking anomaly. I have a tin can and string internet connection so rather than go to a friend's house to update firmware for the GO app I decided to re-link the controller. During the flight test all imagery looked normal and I used auto takeoff. I went to rotate and got no response. all stick inputs were ignored and thankfully it remained at a 6 foot hover, having taken off from a card table. I couldn't get it to shut down and wound up having to pull the battery after grabbing the landing gear. this resulted in a motor overheat warning. I will be heading over to that friend's house to try to update the GO app later but thought I'd ask here if anyone else had seen this issue.
