Where to start...... I received my P4P on 17 of December and since then, except 2-3 good and enjoyable flights, all I had was problems.....
1. Clicking gimbal. I noticed immediately that the ribbon cable was making that noise, but after searching the net for a while I realized that this is a common problem and decided not to ask for a replacement unit as I needed the craft for some surveying missions and dindt have time ti waste. Of course that doesn’t mean that I am happy about it.
2. On my second or third flight, the controller lost aircraft signal at about 800m distance from home and (using 2.4GHz) and started the RTH, after a few seconds I noticed that my controller was linked again with craft, but I didn’t have any video signal on my phone device (black screen with noise). The only think I had, was the telemetry readings. Then I noticed that the craft climbed at 156m (500ft, over maximum allowed height of 400ft here in Greece). I couldn’t do anything as I didn’t have video signal and I couldn’t see it. When I had the craft in sight I disengaged RTH and landed it manually. Even this time I didn’t do anything as I thought that a firmware release could solve that problem.
3. AND finaly….. On 4th of January I tried to fly an autonomous mission to start some surveying projects that I had to do. One day before I tried it inflight data mapper app and the craft completed the mission perfectly. The day of the incident (same place same mission) I switched on the craft connected it to my remote, opened DJI GO 4 to check everything was OK, and after that I used Datamapper to upload the mission data to craft. The craft took off normally, started to climb at planned altitude and it started heading to starting point of mission as supposed. Unfortunately after 1-2 minutes in the air, it continued flying straight and I lost view of it behind a hill. I realized then, that the app got stuck and I didn’t have signal on the controller (App freezed). I immediately pressed RTH on the controller, closed the app and loaded DJI GO4, but it was too late and impossible to connect as the aircraft was away behind a hill and out of site. After waited for 25 mins on the spot (in case RTH worked as supposed), I took my car and drove around the hill having switched on the controller. 30 minutes later the remote controller linked with the aircraft and I was able to locate it in a remote hill side 900m from launch point. The access was not so easy so it took me 2 hours to collect it from a high bush. There was no obvious damage to the craft (except from a scratch on one prop and a broken prop mount), so I suppose that it didn't crash, but landed slowly somehow. I am sure that it did not start the mission as I didn't found any photographs in the sd card, Since the craft is brand new and the purpose that I bought it is to use it for autonomous flights for surveying it is important to know what went wrong, so to prevent accidents in the future.
I contacted DJI support and after one week they asked me to send it to Germany!! and wait 15-20days to check it out. No further details unfortunately. I am very frustrated and don't know what to do. I didn’t ask for repairs, I didn’t ask for guarantee coverage for broken prop mount and damaged prop (in fact I bought the P4 parts already). I just asked to evaluate the craft flight data to see if there is something wrong and if using my craft is dangerous. If something is wrong i suppose that my dealer should arrange with DJI for a replacement product, else they should inform me to continue using it. I am afraid that I paid 1700€ for the craft, + extra batteries + sd cards + car charger + replacement parts (2200€ total) to do work with it and now I have to wait for a month or more. And of course I paid DJI care refresh for 12 months (minus one of course).
BTW in the new Dji assistant software, DJI released a viewer for DAT files. From that I was able to read the data of the craft. For the RTH altitude problem I was able to see that the craft considered that the initial (home) altitude was -76m (from sea level)!! so when it lost signal climbed 76m to reach 0 level and another 80m (instead of 40 that I had preconfigured)!!
The flyaway issue was caused, as GPS status parameter changed to 0 level. At that same time the satellite count was 18 – 20!. Also the datamapper app log, shows the correct coordinates of the flyaway course. This is something that need investigating. I don’t know Does anyone had the same or similar issue?
|