0x0002003F: DROID_ERROR_AUTO_KIOSK_APPROACH_FIDUCIALS_NOT_DETECTED
This alarm is covered by this guide. Applicable alarms (2)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for 0x0002003F) 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 approach fiducials help the droid align itself with the zipping point in preparation for entering the funnel. This error code is activated when the droid is unable to see the approach fiducials due to a dirty camera, damage/obstruction, bad calibration, nav error, excessive motion (like due to wind), or survey error.

CORRECT: Clean approach fiducials installed correctly with the droid descending in the correct position.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
did-droid-descend-between-tether-guides{"<small><b>Step 1</b></small><br/>Question: Look at the video logs from the droid..."}
escalate-zipping-point-survey-reversal{{"<small><b>Step 2</b></small><br/>Escalation: If the droid descended 'behind' the t..."}}
are-dot-patterns-on-fiducials-correct{"<small><b>Step 3</b></small><br/>Question: **Are the dot patterns on the fiducia..."}
escalate-fiducial-hardware-error{{"<small><b>Step 4</b></small><br/>Escalation: If the fiducial patterns do not match..."}}
does-invalid-calibration-jump-true{"<small><b>Step 5</b></small><br/>Question: Open the log plot template 'Droid Nav..."}
return-zipping-point-service-calibrate-droid["<small><b>Step 6</b></small><br/>Action: Return the zipping point to service a..."]
escalate-to-p2-navigation-on-call{{"<small><b>Step 7</b></small><br/>Escalation: Escalate to P2 Nav On Call."}}
did-droid-descend-between-tether-guides -->|Yes| are-dot-patterns-on-fiducials-correct
did-droid-descend-between-tether-guides -->|No| escalate-zipping-point-survey-reversal
are-dot-patterns-on-fiducials-correct -->|Yes| does-invalid-calibration-jump-true
are-dot-patterns-on-fiducials-correct -->|No| escalate-fiducial-hardware-error
does-invalid-calibration-jump-true -->|Yes| return-zipping-point-service-calibrate-droid
does-invalid-calibration-jump-true -->|No| escalate-to-p2-navigation-on-call
style did-droid-descend-between-tether-guides fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-zipping-point-survey-reversal fill:#fef3c7,stroke:#f59e0b,color:#78350f
style are-dot-patterns-on-fiducials-correct fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-fiducial-hardware-error fill:#fef3c7,stroke:#f59e0b,color:#78350f
style does-invalid-calibration-jump-true fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-zipping-point-service-calibrate-droid fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-p2-navigation-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.




Does the INVALID_CALIBRATION graph ever jump to TRUE?

Healthy INVALID_CALIBRATION Graph
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.