Hello,
Sorry if this should be two threads, however I noticed both issues this morning while doing some test flights.
Firstly, I was doing a little warm-up sight flying using DJI GO and kept getting strange "obstacle detected" warnings at 60 m AGL with nothing but blue sky around the P4 Pro. As I continued these warnings became more frequent until the bird came to a complete halt a couple of times, always while facing directly into the low morning sun coming over the nearby mountain ridge. As I normally use Litchi Waypoint for all my longer flights, I am now concerned that the P4 could be stopped by the sun beyond video or Tx range, and just sit there with me unaware of any issue until it ran out of battery or too little to RTH, etc.
Another thing I noticed today, that I had missed previously, is that the bird seems to pause/slow down at each Litchi waypoint before resuming cruise speed. The possible issue with this is I was planning on dealing with flying long missions over irregular mountain terrain by using lots of waypoints i.e. every 30 to 50 m over rough ground, then using the batch edit of altitude relative to ground to create a terrain-following track. This will not work if the bird has to slow down and accelerate at each of a hundred or so waypoints, as it will burn up the battery much faster than flying at cruise speed with only a few waypoints to deal with. Does this mean I am back to creating a track using fewer waypoints at all the high and low points using Google Earth then importing it? I was hoping to use Litchi Hub directly using the "high-density" waypoints idea to avoid having to transfer from GE to Litchi.
Sorry for the long-winded post. Any ideas?
Sorry if this should be two threads, however I noticed both issues this morning while doing some test flights.
Firstly, I was doing a little warm-up sight flying using DJI GO and kept getting strange "obstacle detected" warnings at 60 m AGL with nothing but blue sky around the P4 Pro. As I continued these warnings became more frequent until the bird came to a complete halt a couple of times, always while facing directly into the low morning sun coming over the nearby mountain ridge. As I normally use Litchi Waypoint for all my longer flights, I am now concerned that the P4 could be stopped by the sun beyond video or Tx range, and just sit there with me unaware of any issue until it ran out of battery or too little to RTH, etc.
Another thing I noticed today, that I had missed previously, is that the bird seems to pause/slow down at each Litchi waypoint before resuming cruise speed. The possible issue with this is I was planning on dealing with flying long missions over irregular mountain terrain by using lots of waypoints i.e. every 30 to 50 m over rough ground, then using the batch edit of altitude relative to ground to create a terrain-following track. This will not work if the bird has to slow down and accelerate at each of a hundred or so waypoints, as it will burn up the battery much faster than flying at cruise speed with only a few waypoints to deal with. Does this mean I am back to creating a track using fewer waypoints at all the high and low points using Google Earth then importing it? I was hoping to use Litchi Hub directly using the "high-density" waypoints idea to avoid having to transfer from GE to Litchi.
Sorry for the long-winded post. Any ideas?