English
EnglishEspañolFrançaisالعربيةDeutschPortuguêsItaliano

Your country is detected for each new visit. You can choose your country and language.

Satellite internet / Detailed guide

9602-NAL: startup error or SBD session fault?

Preserve startup output before retrying. Separate serial access, initialization errors and completed SBD sessions so a host-interface fault is not mistaken for a satellite outage.

Applies to: 9602-NAL, Version C, 451-92695-001C. This is an integrated SBD transceiver, not a consumer internet router. Distinguish it from 9602-A, 9602-AB and a bare Iridium module. Work from an installed host system and its existing logs.

Match your symptom

What you seeWhat to do next

Work through these checks

  1. Locate the earliest startup evidence

    Use the host’s existing capture to locate the first response after its recorded power-up. Preserve the lines before and after the fault, not just the final ERROR. Compare with a known working capture from the same installation if available; a different integration is not a reliable baseline.

    What the result means: Observation only for an authorized installed system. Do not probe connector pins, rewire power, inject AT commands, clear message buffers or reset stored profiles. Host configuration and electrical diagnosis belong to the integrator. Keep device identifiers, payloads and recipient details private.

  2. Keep serial settings with the capture

    Record the configured host port, cable/interface description and serial settings from the integrator’s documentation. Do not guess a working configuration by trying random settings. The manual says this device does not support autobaud; that makes the documented baseline important when output is absent or unreadable.

    What the result means: Observation only for an authorized installed system. Do not probe connector pins, rewire power, inject AT commands, clear message buffers or reset stored profiles. Host configuration and electrical diagnosis belong to the integrator. Keep device identifiers, payloads and recipient details private.

  3. Separate failure from missing completion

    Preserve any HARDWARE FAILURE line in full. Keep the session result together with the preceding host event, so support can see whether initialization, local access or a later transmission stage failed. A generic ERROR without context is insufficient to select a replacement part.

    What the result means: Observation only for an authorized installed system. Do not probe connector pins, rewire power, inject AT commands, clear message buffers or reset stored profiles. Host configuration and electrical diagnosis belong to the integrator. Keep device identifiers, payloads and recipient details private.

  4. Escalate without losing the baseline

    Send official support and the system integrator a private copy of the timeline, exact model, document number and current host configuration. Ask them to identify the failing stage before authorizing changes. Preserve an original capture and a separate redacted public copy; do not clear the evidence merely to make the warning disappear.

    What the result means: Observation only for an authorized installed system. Do not probe connector pins, rewire power, inject AT commands, clear message buffers or reset stored profiles. Host configuration and electrical diagnosis belong to the integrator. Keep device identifiers, payloads and recipient details private.

When to stop and get help

Observation only for an authorized installed system. Do not probe connector pins, rewire power, inject AT commands, clear message buffers or reset stored profiles. Host configuration and electrical diagnosis belong to the integrator. Keep device identifiers, payloads and recipient details private.

Request a U.S. technician ↗

What to tell support

Observation only for an authorized installed system. Do not probe connector pins, rewire power, inject AT commands, clear message buffers or reset stored profiles. Host configuration and electrical diagnosis belong to the integrator. Keep device identifiers, payloads and recipient details private.

Original troubleshooting guidance based on the official sources below. Menu names can change. This is an independent guide, not a manufacturer service bulletin or a bench-tested repair.