SOFTWARE_CONFIGURATION_MISMATCH
Viewing this guide for
Applicable alarms (1)
SOFTWARE_CONFIGURATION_MISMATCH
Likely outcomes — click to expand
Based on 6,059 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 51 ZERP issues filed on these missions)
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| PARALAND ASSY, AIRCRAFT, P2 | 18480 | 3 |
| HOVER AND SERVO AFT STBD(RH) FLEX HARNESS, ZIP, P2 | 0121836 | 1 |
| HOVER AND SERVO FWD STBD(RH) FLEX HARNESS, ZIP, P2 | 0121834 | 1 |
Frequently co-occurring alarms (% of the 6,059 missions above)
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm occurs when software on the vehicle does not match what is expected. This can occur when a software deploy fails, or if hardware is swapped on the vehicle without a software deploy being run afterwards.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
is-this-a-jetpack-6-droid-on-2026-15{"<small><b>Step 1</b></small><br/>Question: Is this alarm showing on a Jetpack 6 ..."}
re-deploy-the-droid-software["<small><b>Step 2</b></small><br/>Action: Re-deploy the Droid software. See UMM..."]
has-the-jetpack-6-droid-issue-resolved{"<small><b>Step 3</b></small><br/>Question: Has the issue resolved on the Droid?"}
the-droid-may-return-to-service("<small><b>Step 4</b></small><br/>Reference: The Droid may return to service.")
re-deploy-the-software-see-umm-chapter["<small><b>Step 5</b></small><br/>Action: Re-deploy the software. See UMM Chapt..."]
has-the-issue-resolved{"<small><b>Step 6</b></small><br/>Question: Has the issue resolved?"}
the-aircraft-may-return-to-service("<small><b>Step 7</b></small><br/>Reference: The Aircraft may return to service.")
escalate-to-p2-embedded-platform-on-call{{"<small><b>Step 8</b></small><br/>Escalation: Escalate to P2 Embedded Platform On C..."}}
escalate-to-p2-embedded-linux-on-call{{"<small><b>Step 9</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call."}}
is-this-a-jetpack-6-droid-on-2026-15 -->|Yes, this is a Jetpack 6 Dr...| re-deploy-the-droid-software
is-this-a-jetpack-6-droid-on-2026-15 -->|No, use the standard vehicl...| re-deploy-the-software-see-umm-chapter
re-deploy-the-droid-software --> has-the-jetpack-6-droid-issue-resolved
has-the-jetpack-6-droid-issue-resolved -->|Yes| the-droid-may-return-to-service
has-the-jetpack-6-droid-issue-resolved -->|No| escalate-to-p2-embedded-linux-on-call
re-deploy-the-software-see-umm-chapter --> has-the-issue-resolved
has-the-issue-resolved -->|Yes| the-aircraft-may-return-to-service
has-the-issue-resolved -->|No| escalate-to-p2-embedded-platform-on-call
style is-this-a-jetpack-6-droid-on-2026-15 fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style re-deploy-the-droid-software fill:#dcfce7,stroke:#22c55e,color:#14532d
style has-the-jetpack-6-droid-issue-resolved fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-droid-may-return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style re-deploy-the-software-see-umm-chapter fill:#dcfce7,stroke:#22c55e,color:#14532d
style has-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-p2-embedded-platform-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-to-p2-embedded-linux-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
1 question >=2026.15
Is this alarm showing on a Jetpack 6 Droid asset on software version 2026.15?
In FleetWrangler, open the Aircraft's Detailed Zip Status and check Jetpack Details. Confirm that the Droid is listed as
NOTE: The Jetpack 6 Droid path is new to 2026.15 Droids.
In FleetWrangler, open the Aircraft's Detailed Zip Status and check Jetpack Details. Confirm that the Droid is listed as
JP6.NOTE: The Jetpack 6 Droid path is new to 2026.15 Droids.
2 action >=2026.15
Re-deploy the Droid software. See UMM Chapter 14.1 Software for steps.
NOTE: Refer to OTA Deployment Failures for Aircraft for failures encountered when deploying.
NOTE: Refer to OTA Deployment Failures for Aircraft for failures encountered when deploying.
3 question >=2026.15
Has the issue resolved on the Droid?
4 reference >=2026.15
The Droid may return to service.
5 action
Re-deploy the software. See UMM Chapter 14.1 Software for steps.
NOTE: Refer to OTA Deployment Failures for Aircraft for failures encountered when deploying.
NOTE: Refer to OTA Deployment Failures for Aircraft for failures encountered when deploying.
6 question
Has the issue resolved?
7 reference
The Aircraft may return to service.
8 escalation
Escalate to P2 Embedded Platform On Call.
9 escalation
Escalate to P2 Embedded Linux 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.