Here are events as reported to airdata for the April 9th 2024, 1:42 flight.
Actions pour les commentaires
Publication
S’abonner
Consistent failure on 2nd battery
I haven't flown a mission for about six months, so I am unsure if there were updates that may impact this operation. I've had no hardware changes since my last missions.
I'm flying about 20 acres. On first flight, it reports something about removing waypoints because of some limit. This is new. The flightplan still looked ok so I launched. First flight went well. I landed to swap batteries. Second flight launched and rose to around 98' and stopped there. It just hovered. I canceled and tried again. This repeated many times.
I eventually modified the mission into separate independent missions to collect a similar group of images.
How do I determine what happened and how to avoid this?
Thank you!
-Mike
Vous devez vous connecter pour laisser un commentaire.
5 commentaires
Any thoughts?
Actions pour les commentaires
Sorry about that. I replied to this over the weekend but must not have hit send... Please update to 5.8.1 which has fixes for this issue.
As a side note, I think 90% overlap is too much to be using in these areas. Full Grid should only be used with 70ish% overlap otherwise you end up giving the system too much overlap. Then the processing takes FOREVER which I think you are finding out.
You want to give the system 25ish looks at everything. 35-40 max. This equates to 80% overlap, maybe up to 83%. With 90% overlap you are giving the system 80+ looks. If you then do Full Grid with 90% you are giving the system 160 looks (which is just silly). There is a warning telling you not to upload high overlap Full Grid data.
Actions pour les commentaires
Yes, processing is taking a long while. I'm sorry about that. I should have set the overlap lower. The subject site is three states away, so I will not be able to capture new images.
Unless you've updated in the last week, 5.8.1 was used to capture these.
I'm happy to run tests this weekend if you'd like. Let me know.
-Mike
Actions pour les commentaires
It is always better to be safe than sorry but there are limits!
The original thing you posted about should be fixed with 5.8.1. Please let us know if that is not the case.
Actions pour les commentaires
