I just had a couple of crash due to current setting on FS logic. Here the events:
Drone has low battery voltage: RTL is triggered and aircraft starts to climb
pilot abort RTL by changing flight mode to Loiter
Drone has now critical battery voltage, LAND is triggered and aircraft start to descent ( let’s says from 10m)
RX lost link and system read RC fail-safe ( sbus trigger fail-safe), drone start RTL procedure, climb back to 20m then battery is too low and crash.
I would like to change setting is such a way that if system is already in land mode, will continue but also if battery is OK and RX lost link, normal RTL is triggered.
As alternative, change setting in such a way that if critical battery voltage is triggered, RTL from fail-safe is ignored
If a if a low battery fail safe is over ridden by a loss of RC fail safe you want to be able to switch back the the low battery Ffail safe so the aircraft will land.
You cannot do that because during a loss of RC, the RC link is NON OPERATIONAL.
If you disable the loss of RC fail safe, during a loss of RC condition the aircraft will continue to fly all of the way to the scene of the crash.
The bottom line is, it is apparent to me that you have the low battery fail safe set too low. This leaves insufficient battery capacity for a safe RTL.
I think so. It was introduced to cover at least following scenarios:
If operator has manually switched to LAND, then he indeed want the vehicle to land and don’t want landing to be interrupted by RC failsafe (that is pretty possible if landing away of the operator location)
If LAND is engaged by a failsafe event
I personally tested the 1-st scenario, but not 2-nd.
No , i think you are miss understand , you said critical batter after Rx failsafe it means you change rtl when battery is critical and after Rx fs so it means once again rtl proceed.
Regarding less the low or critical battery failsafe, if in failsafe and Land mode is selected, with the correct fs_option is possible to act in such a way that Rx RTL failsafe is ignored
I am thinking out loud, but maybe it could be discussed, as some work has been done but it seems that it is not completely consolidated. There could be a fs inheritance, that could go from hover, srtl, rtl, land… so if one system triggers a more strict type of fs then it changes from one to another. If the fs type is less strict in this inheritance, ghen it is not changed. It could be the same for not allowed modes. In this case if the system cannot change to smart rtl then automatically it would change to the next more strict mode, maybe rtl. Then the fs options could be easier to set.
I think you didn’t get my point.
I would let choose any fs option, as it is now, but if two failsafe modes are triggered, the selected mode should not be the last triggered, but the most restrictive.
If battery is critical low RTL shouldn’t be launched at all if it requires to climb. As I understand You are trying to cover scenario when battery is getting low and You are far far away from launch site and are forced to land somewhere else. Lowering the altitude is causing RX loss in this case?