0x0010019D ZIP_EXECUTIVE_V4_GRPC_BRIDGE_NOT_READY
Applicable alarms (2)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for 0x0010019D) as of 2026-10-13
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”The zip and droid communicate wirelessly during delivery using 802.11 “wifi” radios. The vehicles send messages back and forth to each other using a combination of best-effort UDP datagrams and reliable TCP stream connections. The reliable nature means that messages sent over the TCP connection are expected to be buffered and successfully transmitted eventually.
This error code is set whenever the zip’s outgoing TCP connection to the droid is down, and messages that would be buffered and sent are instead being dropped. This can happen when the underlying 802.11 network is disabled or broken at the operating system level, the radio spectrum is totally jammed for an extended period of time, or the underlying wireless tunnel service is disabled or broken.
Note that this error code is expected to be set nominally during phases of the mission that don’t require the droid to move, and the wireless network is intentionally disabled. The error code is only a problem when the CanDroidExecuteMotionCmds capability is necessary.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
power-cycle-the-aircraft-power-cycle-a["<small><b>Step 1</b></small><br/>Action: Power cycle the Aircraft. Power Cyc..."]
is-the-issue-resolved{"<small><b>Step 2</b></small><br/>Question: Is the issue resolved?"}
the-aircraft-may-return-to-service("<small><b>Step 3</b></small><br/>Reference: The Aircraft may return to service.")
escalate-to-avionics-embedded-on-cal{{"<small><b>Step 4</b></small><br/>Escalation: Escalate to avionics embedded on call."}}
power-cycle-the-aircraft-power-cycle-a --> is-the-issue-resolved
is-the-issue-resolved -->|Yes| the-aircraft-may-return-to-service
is-the-issue-resolved -->|No| escalate-to-avionics-embedded-on-cal
style power-cycle-the-aircraft-power-cycle-a fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-issue-resolved fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style escalate-to-avionics-embedded-on-cal fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
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
Open pull requests
There are no open pull requests.