Skip to content

Reposition After Droid Left Behind

published HW: P2

On software release 2026.15, a Zip Executive persistent-state bug can prevent a maintenance reposition after an Aircraft has left its Droid behind. The Aircraft can appear to be in a state where the Droid is neither stowed nor correctly recognized as left behind, so the maintenance reposition may fail until Zip Executive restarts.

The intended workaround is to restart Zip Executive without rebooting the rest of the Aircraft stack, then attempt the maintenance reposition. A reboot mission may be rejected by the same bug, and a full Aircraft power cycle can restart distro and leave the winch cutter reporting the wrong terminal state for this recovery path.

1 question
Which software version are you on?

Did this guide help you get unblocked?

Open suggestions

There are no open suggestions.

Open pull requests

There are no open pull requests.