WINCH_COMMS_MISSING
Background
Section titled “Background”This guide should be followed when WINCH_COMMS_MISSING check fails.
This failure usually means that it is unclear whether the issue is due to a bad Ethernet connection or a bad power connection.
Check both, the Ethernet connection and, if needed, the power connection using the linked guides below.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
inspect-winch-comms["<small><b>Step 1</b></small><br/>Action: Start by checking the Distro-to-Winch..."]
was-comms-issue-detected{"<small><b>Step 2</b></small><br/>Question: Did the previous inspection step dete..."}
is-the-issue-resolved{"<small><b>Step 3</b></small><br/>Question: Did replacement of the bad HW resolve..."}
proceed-to-power-inspection["<small><b>Step 4</b></small><br/>Action: Continue troubleshooting by following..."]
power-inspection-outcome{"<small><b>Step 5</b></small><br/>Question: Did the previous inspection step dete..."}
is-the-issue-resolved-post-power{"<small><b>Step 6</b></small><br/>Question: Did replacement of the bad HW resolve..."}
return-to-service("<small><b>Step 7</b></small><br/>Reference: The Aircraft may return to service.")
escalate-to-fw-platform{{"<small><b>Step 8</b></small><br/>Escalation: Escalate to P2 Firmware Platform On C..."}}
inspect-winch-comms --> was-comms-issue-detected
was-comms-issue-detected -->|Yes| is-the-issue-resolved
was-comms-issue-detected -->|No| proceed-to-power-inspection
is-the-issue-resolved -->|Yes| return-to-service
is-the-issue-resolved -->|No| proceed-to-power-inspection
proceed-to-power-inspection --> power-inspection-outcome
power-inspection-outcome -->|Yes| is-the-issue-resolved-post-power
power-inspection-outcome -->|No| escalate-to-fw-platform
is-the-issue-resolved-post-power -->|Yes| return-to-service
is-the-issue-resolved-post-power -->|No| escalate-to-fw-platform
style inspect-winch-comms fill:#dcfce7,stroke:#22c55e,color:#14532d
style was-comms-issue-detected fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style is-the-issue-resolved fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style proceed-to-power-inspection fill:#dcfce7,stroke:#22c55e,color:#14532d
style power-inspection-outcome fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style is-the-issue-resolved-post-power fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style escalate-to-fw-platform fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
Follow DISTRO_TO_WINCH_ETHERNET_LINK_INTEGRITY to determine whether the comms-missing fault was caused by a broken, damaged, loose, or intermittent Ethernet link between the Distro and the Winch.
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.