winch_cutter_deployed_in_zipping_point
Viewing this guide for
Applicable alarms (1)
winch_cutter_deployed_in_zipping_point
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last 90 days as of 2026-10-13
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
assign-the-v4-zipping-point-inspect-zip["<small><b>Step 1</b></small><br/>Action: Assign the V4 Zipping Point: Inspect..."]
look-at-the-details-of-the-completed-dl{"<small><b>Step 2</b></small><br/>Question: Check the asset's mission history in ..."}
let-ranger-know-inspection-is-complete["<small><b>Step 3</b></small><br/>Action: Let the ranger know that they can res..."]
what-caused-it{"<small><b>Step 4</b></small><br/>Question: Is the issue software or hardware rel..."}
software-issue-reboot["<small><b>Step 5</b></small><br/>Action: Assign the V4 Zipping Point: Reboot ..."]
hardware-issue-system{"<small><b>Step 6</b></small><br/>Question: What system is the issue with?"}
hardware-drawer-replace["<small><b>Step 7</b></small><br/>Action: Assign the V4 Zipping Point: Replace..."]
hardware-console-responsive{"<small><b>Step 8</b></small><br/>Question: Is the console responsive?"}
hardware-console-responsive-reboot["<small><b>Step 9</b></small><br/>Action: Assign the V4 Zipping Point: Reboot ..."]
hardware-console-unresponsive-reset["<small><b>Step 10</b></small><br/>Action: Assign the V4 Zipping Point: Power C..."]
hardware-console-replace["<small><b>Step 11</b></small><br/>Action: Assign the V4 Zipping Point: Replace..."]
hardware-other-escalate{{"<small><b>Step 12</b></small><br/>Escalation: Escalate to Zipping Point On Call."}}
notify-ranger-not-to-return-asset["<small><b>Step 13</b></small><br/>Action: In the incident channel, notify the r..."]
confirm-that-log-offload-is-happening["<small><b>Step 14</b></small><br/>Action: Confirm that log offload is happening..."]
did-ranger-find-issue-during-inspection{"<small><b>Step 15</b></small><br/>Question: Did the ranger find any issue during ..."}
what-caused-it-after-inspection{"<small><b>Step 16</b></small><br/>Question: Is the issue software or hardware rel..."}
software-issue-reboot-after-inspection["<small><b>Step 17</b></small><br/>Action: Assign the V4 Zipping Point: Reboot ..."]
hardware-issue-system-after-inspection{"<small><b>Step 18</b></small><br/>Question: What system is the issue with?"}
hardware-drawer-replace-after-inspection["<small><b>Step 19</b></small><br/>Action: Assign the V4 Zipping Point: Replace..."]
hardware-console-responsive-after-inspection{"<small><b>Step 20</b></small><br/>Question: Is the console responsive?"}
hardware-console-responsive-reboot-after-inspection["<small><b>Step 21</b></small><br/>Action: Assign the V4 Zipping Point: Reboot ..."]
hardware-console-unresponsive-reset-after-inspection["<small><b>Step 22</b></small><br/>Action: Assign the V4 Zipping Point: Power C..."]
hardware-console-replace-after-inspection["<small><b>Step 23</b></small><br/>Action: Assign the V4 Zipping Point: Replace..."]
hardware-other-escalate-after-inspection{{"<small><b>Step 24</b></small><br/>Escalation: Escalate to Zipping Point On Call."}}
review-the-droid-center-camera-video-lo{"<small><b>Step 25</b></small><br/>Question: Review the droid center camera video ..."}
video-obstruction-is-the-obstruction-now{"<small><b>Step 26</b></small><br/>Question: Is the obstruction now cleared?"}
video-obstruction-yes-return-to-service["<small><b>Step 27</b></small><br/>Action: Return the zipping point to service."]
video-obstruction-no-clear-or-escalate["<small><b>Step 28</b></small><br/>Action: If the obstruction can be easily clea..."]
video-droid-caught-on-tether-guides{"<small><b>Step 29</b></small><br/>Question: Was the droid stable and controlled w..."}
video-tether-yes-stable-approach{"<small><b>Step 30</b></small><br/>Question: Was anything found wrong with the app..."}
video-tether-yes-fiducial-issue-found{{"<small><b>Step 31</b></small><br/>Escalation: If further clarification is needed to..."}}
video-tether-no-fiducial-issue-escalate{{"<small><b>Step 32</b></small><br/>Escalation: Escalate to P2 Droid Autonomy On Call."}}
video-tether-no-unstable-approach["<small><b>Step 33</b></small><br/>Action: If the droid could not control itself..."]
video-droid-landed-on-platform-never-too{"<small><b>Step 34</b></small><br/>Question: Were the DOOR_CLOSE_FAILED/topics/..."}
video-door-error-yes-refer-to-guides("<small><b>Step 35</b></small><br/>Reference: Refer to those guides for further act...")
video-door-error-no-escalate-autonomy{{"<small><b>Step 36</b></small><br/>Escalation: Escalate to P2 Droid Autonomy On Call."}}
video-camera-cuts-out-escalate{{"<small><b>Step 37</b></small><br/>Escalation: Escalate to Zipping Point On Call."}}
assign-the-v4-zipping-point-inspect-zip --> look-at-the-details-of-the-completed-dl
look-at-the-details-of-the-completed-dl -->|Yes| notify-ranger-not-to-return-asset
look-at-the-details-of-the-completed-dl -->|No| let-ranger-know-inspection-is-complete
let-ranger-know-inspection-is-complete --> what-caused-it
what-caused-it -->|Software| software-issue-reboot
what-caused-it -->|Hardware| hardware-issue-system
hardware-issue-system -->|Drawer| hardware-drawer-replace
hardware-issue-system -->|Console| hardware-console-responsive
hardware-issue-system -->|Other| hardware-other-escalate
hardware-console-responsive -->|Yes| hardware-console-responsive-reboot
hardware-console-responsive -->|No| hardware-console-unresponsive-reset
hardware-console-responsive-reboot --> hardware-console-replace
hardware-console-unresponsive-reset --> hardware-console-replace
notify-ranger-not-to-return-asset --> confirm-that-log-offload-is-happening
confirm-that-log-offload-is-happening --> did-ranger-find-issue-during-inspection
did-ranger-find-issue-during-inspection -->|Yes| what-caused-it-after-inspection
did-ranger-find-issue-during-inspection -->|No| review-the-droid-center-camera-video-lo
what-caused-it-after-inspection -->|Software| software-issue-reboot-after-inspection
what-caused-it-after-inspection -->|Hardware| hardware-issue-system-after-inspection
hardware-issue-system-after-inspection -->|Drawer| hardware-drawer-replace-after-inspection
hardware-issue-system-after-inspection -->|Console| hardware-console-responsive-after-inspection
hardware-issue-system-after-inspection -->|Other| hardware-other-escalate-after-inspection
hardware-console-responsive-after-inspection -->|Yes| hardware-console-responsive-reboot-after-inspection
hardware-console-responsive-after-inspection -->|No| hardware-console-unresponsive-reset-after-inspection
hardware-console-responsive-reboot-after-inspection --> hardware-console-replace-after-inspection
hardware-console-unresponsive-reset-after-inspection --> hardware-console-replace-after-inspection
review-the-droid-center-camera-video-lo -->|Obstruction in path of droid| video-obstruction-is-the-obstruction-now
review-the-droid-center-camera-video-lo -->|Droid got caught on tether ...| video-droid-caught-on-tether-guides
review-the-droid-center-camera-video-lo -->|Droid landed on platform an...| video-droid-landed-on-platform-never-too
review-the-droid-center-camera-video-lo -->|Camera cuts out| video-camera-cuts-out-escalate
video-obstruction-is-the-obstruction-now -->|YES| video-obstruction-yes-return-to-service
video-obstruction-is-the-obstruction-now -->|NO| video-obstruction-no-clear-or-escalate
video-droid-caught-on-tether-guides -->|Yes| video-tether-yes-stable-approach
video-droid-caught-on-tether-guides -->|No| video-tether-no-unstable-approach
video-tether-yes-stable-approach -->|YES| video-tether-yes-fiducial-issue-found
video-tether-yes-stable-approach -->|NO| video-tether-no-fiducial-issue-escalate
video-droid-landed-on-platform-never-too -->|Yes| video-door-error-yes-refer-to-guides
video-droid-landed-on-platform-never-too -->|No| video-door-error-no-escalate-autonomy
style assign-the-v4-zipping-point-inspect-zip fill:#dcfce7,stroke:#22c55e,color:#14532d
style look-at-the-details-of-the-completed-dl fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style let-ranger-know-inspection-is-complete fill:#dcfce7,stroke:#22c55e,color:#14532d
style what-caused-it fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style software-issue-reboot fill:#dcfce7,stroke:#22c55e,color:#14532d
style hardware-issue-system fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style hardware-drawer-replace fill:#dcfce7,stroke:#22c55e,color:#14532d
style hardware-console-responsive fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style hardware-console-responsive-reboot fill:#dcfce7,stroke:#22c55e,color:#14532d
style hardware-console-unresponsive-reset fill:#dcfce7,stroke:#22c55e,color:#14532d
style hardware-console-replace fill:#dcfce7,stroke:#22c55e,color:#14532d
style hardware-other-escalate fill:#fef3c7,stroke:#f59e0b,color:#78350f
style notify-ranger-not-to-return-asset fill:#dcfce7,stroke:#22c55e,color:#14532d
style confirm-that-log-offload-is-happening fill:#dcfce7,stroke:#22c55e,color:#14532d
style did-ranger-find-issue-during-inspection fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style what-caused-it-after-inspection fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style software-issue-reboot-after-inspection fill:#dcfce7,stroke:#22c55e,color:#14532d
style hardware-issue-system-after-inspection fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style hardware-drawer-replace-after-inspection fill:#dcfce7,stroke:#22c55e,color:#14532d
style hardware-console-responsive-after-inspection fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style hardware-console-responsive-reboot-after-inspection fill:#dcfce7,stroke:#22c55e,color:#14532d
style hardware-console-unresponsive-reset-after-inspection fill:#dcfce7,stroke:#22c55e,color:#14532d
style hardware-console-replace-after-inspection fill:#dcfce7,stroke:#22c55e,color:#14532d
style hardware-other-escalate-after-inspection fill:#fef3c7,stroke:#f59e0b,color:#78350f
style review-the-droid-center-camera-video-lo fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style video-obstruction-is-the-obstruction-now fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style video-obstruction-yes-return-to-service fill:#dcfce7,stroke:#22c55e,color:#14532d
style video-obstruction-no-clear-or-escalate fill:#dcfce7,stroke:#22c55e,color:#14532d
style video-droid-caught-on-tether-guides fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style video-tether-yes-stable-approach fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style video-tether-yes-fiducial-issue-found fill:#fef3c7,stroke:#f59e0b,color:#78350f
style video-tether-no-fiducial-issue-escalate fill:#fef3c7,stroke:#f59e0b,color:#78350f
style video-tether-no-unstable-approach fill:#dcfce7,stroke:#22c55e,color:#14532d
style video-droid-landed-on-platform-never-too fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style video-door-error-yes-refer-to-guides fill:#f3e8ff,stroke:#a855f7,color:#581c87
style video-door-error-no-escalate-autonomy fill:#fef3c7,stroke:#f59e0b,color:#78350f
style video-camera-cuts-out-escalate fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
1 action
Assign the V4 Zipping Point: Inspect Zipping Point after Droid Left Behind (DLB) work order due immediately, create an incident channel, coordinate with SE2 in the
#service-engineering-fire-dispatch channel, and let the ranger know that the inspection has been assigned. 2 question
Check the asset's mission history in Baraza. Have any other DLBs occurred in the last 24 hours?
3 action
Let the ranger know that they can resolve the discrepancy once the inspection is complete, unless an issue is found that they cannot mitigate.
4 question
Is the issue software or hardware related?
5 action
Assign the V4 Zipping Point: Reboot Zipping Point - Ranger work order. If the issue persists, escalate to Zipping Point On Call.
6 question
What system is the issue with?
7 action
Assign the V4 Zipping Point: Replace Drawer work order. If the issue persists, escalate to Zipping Point On Call.
8 question
Is the console responsive?
9 action
Assign the V4 Zipping Point: Reboot Zipping Point - Ranger work order.
10 action
Assign the V4 Zipping Point: Power Cycle work order.
11 action
Assign the V4 Zipping Point: Replace Console work order. If the issue persists, escalate to Zipping Point On Call.
12 escalation
Escalate to Zipping Point On Call.
13 action
In the incident channel, notify the ranger not to return the asset to service, even if it passes inspection.
14 action
Confirm that log offload is happening:
SSH into Smart Cart/Log Offloader
1. Open Terminal.
2. Type in
3. Type
4. It should respond with which droid is connected to the smart cart, and repeatedly send updates about how many GB of logs are left to offload. If you do not see that the droid is connected, or if the number of GB of logs does not go down after some time, use Droid Log Offloading Troubleshooting.
SSH into Smart Cart/Log Offloader
1. Open Terminal.
2. Type in
ssh zipline@p2-smart-cart-XX for smart carts or ssh zipline@p2-droid-cart-X for log offloaders. It may open a window and require you to log into tailscale.3. Type
check_log_offloading <password> - remember to replace <password> with the actual password.4. It should respond with which droid is connected to the smart cart, and repeatedly send updates about how many GB of logs are left to offload. If you do not see that the droid is connected, or if the number of GB of logs does not go down after some time, use Droid Log Offloading Troubleshooting.
15 question
Did the ranger find any issue during inspection?
16 question
Is the issue software or hardware related?
17 action
Assign the V4 Zipping Point: Reboot Zipping Point - Ranger work order. If the issue persists, escalate to Zipping Point On Call.
18 question
What system is the issue with?
19 action
Assign the V4 Zipping Point: Replace Drawer work order. If the issue persists, escalate to Zipping Point On Call.
20 question
Is the console responsive?
21 action
Assign the V4 Zipping Point: Reboot Zipping Point - Ranger work order.
22 action
Assign the V4 Zipping Point: Power Cycle work order.
23 action
Assign the V4 Zipping Point: Replace Console work order. If the issue persists, escalate to Zipping Point On Call.
24 escalation
Escalate to Zipping Point On Call.
25 question
Review the droid center camera video logs from the mission. If it is a night mission, it may help to also view the logs from the left or right cameras. What happened before the DLB occurred?
26 question
Is the obstruction now cleared?
27 action
Return the zipping point to service.
28 action
If the obstruction can be easily cleared, ask the ranger to clear it, document the issue in the discrepancy, and return the zipping point to service. If not, escalate to Zipping Point On Call.
29 question
Was the droid stable and controlled while approaching the zipping point?
30 question
Was anything found wrong with the approach fiducials or droid tether guides during inspection OR can you see anything wrong with them in the video logs?
31 escalation
If further clarification is needed to resolve the issue, escalate to Zipping Point On Call.
32 escalation
Escalate to P2 Droid Autonomy On Call.
33 action
If the droid could not control itself, the issue is likely unrelated to the zipping point. Return the zipping point to service, but tag P2 Droid Autonomy On Call and let them know that the droid was unable to control itself while approaching the zipping point.
34 question
Were the DOOR_CLOSE_FAILED or DOOR_OPEN_FAILED error codes present?
35 reference
Refer to those guides for further action.
36 escalation
Escalate to P2 Droid Autonomy On Call.
37 escalation
Escalate to Zipping Point On Call.
Resolution note
This plaintext block is ready to paste into the Resolution Note field on the ZERP issue you're working. The permalink below gives engineering review access to the full step-by-step timeline including any back-navigation; share it if the case needs a deeper look.
Permalink:
Session is too large to fit in a URL. Use Download session JSON to share the timeline out-of-band.
Did this guide help you get unblocked?
Open suggestions
There are no open suggestions.
Open pull requests
There are no open pull requests.