I just received my first ever drone, a P4P. I followed the instructions and updated the firmware in the drone and in the RC yesterday. I charged fully the RC and 2 flight batteries, both new DJI batteries. I went to a large field today for initial tests. The P4P powered on just fine and streamed video as expected. I took a few test pictures and videos and they were fine. I was very cautious and stayed within about 100m distance and 10m altitude. I just used manual controls during this outing with the exception of trying auto launch and land both of which worked fine (by that I mean hit the buttons in the app to launch and land). The bird behaved well in flight and appeared very stable.
Now for my problems.
1) the gimbal overload warning came on a few times. physically the gimbal is completely free moving on both axes when powered off. Also, I never rotated the craft quickly, but on several occasions the leg came into view. In spite of that the gimbal appeared to work fine and the video was quite smooth. It just seems that it was very slow to catch up to an aircraft rotation. Perhaps this is not a "problem", but it would be nice to hear that this is normal behaviour.
2) this is a BIG problem. The flight battery status is usually missing from the display in the APP and querying it shows it is N/A. I say usually because I have been experimenting with it here at my desk and sometimes when I reinitialize everything it will be there and rational (i.e., the values are sensible and in sync with the battery's status indicators) only to disappear for no obvious reason after a minute or so. On at least one occasion it came back only to disappear again. This was a static test with no props and the bird sitting on my desk so there was no movement to "jiggle' anything. This behavior is identical for both batteries, so it is not a battery issue. Obviously this is a major problem -- not knowing your battery status during flight.
This was purchased from a high quality source (B&H) so I can return it and rebuy it. Any advice? Is this a known issue with a fix? BTW: I rechecked today that no new firmware or app update appeared after I set everything up yesterday.
I will say that the app appears to be a bit on the buggy side. For example when I used it to auto land the bird, it seemed to be unable to get out of the autoland mode. To take off again I had to do so manually (I assume if I had closed and reopened the app all would be well)
Your input would be most welcome.
Richard
Now for my problems.
1) the gimbal overload warning came on a few times. physically the gimbal is completely free moving on both axes when powered off. Also, I never rotated the craft quickly, but on several occasions the leg came into view. In spite of that the gimbal appeared to work fine and the video was quite smooth. It just seems that it was very slow to catch up to an aircraft rotation. Perhaps this is not a "problem", but it would be nice to hear that this is normal behaviour.
2) this is a BIG problem. The flight battery status is usually missing from the display in the APP and querying it shows it is N/A. I say usually because I have been experimenting with it here at my desk and sometimes when I reinitialize everything it will be there and rational (i.e., the values are sensible and in sync with the battery's status indicators) only to disappear for no obvious reason after a minute or so. On at least one occasion it came back only to disappear again. This was a static test with no props and the bird sitting on my desk so there was no movement to "jiggle' anything. This behavior is identical for both batteries, so it is not a battery issue. Obviously this is a major problem -- not knowing your battery status during flight.
This was purchased from a high quality source (B&H) so I can return it and rebuy it. Any advice? Is this a known issue with a fix? BTW: I rechecked today that no new firmware or app update appeared after I set everything up yesterday.
I will say that the app appears to be a bit on the buggy side. For example when I used it to auto land the bird, it seemed to be unable to get out of the autoland mode. To take off again I had to do so manually (I assume if I had closed and reopened the app all would be well)
Your input would be most welcome.
Richard
