Battery/Descending Issue

[RailHawk2018]

While returning to the recovery location, and despite being fully charged at the start of the flight, the drone refused to land and would only descend at a vertical speed of approximately 0.5 mph. This continued until the battery reached 4% at which time the aircraft did land within normal operating parameters.

Anyone else have this issue or have a solution to the problem?

Thanks in advance.

 

[SkyPhotos]

This has happened to me repeatedly, Autel has taken a look at the logs and they "look fine" and therefore I was imagining this behavior.
I'm guessing this is related somehow to poor obstacle avoidance somehow, because the partial workaround I is to fly up and yaw the drone to a different direction, and then try again.

Or just wait for automated RTH landing, which seems to override everything.


Some issues with the RTH: it is altitude independent. I've been landing, and the low battery RTH triggered in the last 4 feet of landing. The M4T then quickly moved to the original landing spot about 10 feet away, narrowly missing me, and then landing.


The other issue I saw was on resuming a paused grid mission. Per Autel, it "resumed the mission at an altitude below ground level and not at the original height" due to a software error, for which I had to trigger and pay for Autel Care to get my drone back after 5 weeks in the shop and a 3 month diagnostic process. I am actually still waiting to receive it. Hopefully this third replacement drone will not need a new motherboard, strobe, replacement battery, etc like the others.

 

[RailHawk2018]

Thank you for your reply. This is very helpful. If my team have any further incidents, I’ll post in this thread.

My team have 20 Max4N across our system and we’ve had three incidents in the last four weeks.

Thanks again!