English
EnglishEspañolFrançaisالعربيةDeutschPortuguêsItalianoفارسیBahasa IndonesiaاردوTiếng ViệtBahasa MelayuRomânăΕλληνικάहिन्दीNederlandsTürkçePolskiไทยУкраїнськаРусскийČeština한국어বাংলা日本語简体中文繁體中文FilipinoKiswahiliSvenskaעבריתSuomiDanskMagyarNorsk bokmålதமிழ்

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

Satellite internet / Detailed guide

EXPLORER540: LED off after installation

Read the EXPLORER540 Rev K installation-phase LED, authorized web-interface data state, active alerts and idle intervals, then collect current and historical evidence separately.

Applies to: EXPLORER540, original98-148232-K (2023), sections2.5,4.4 and5.5.2. Match hardware, firmware and subscription. EXPLORER325/510/710 and optional cellular configurations have different boundaries. Idle power save: section3.6.3. Evidence collection: Rev K sections 4.12.1–4.12.3 and 5.6.

Match your symptom

What you seeWhat to do next
LED alone is the only symptomStart with the installation phase and existing web status.
The outage follows an idle intervalCompare configured timing without holding the web interface open as a test.
An alert or historical event is reportedSeparate current Alerts from Event log history before handing over the evidence.

Work through these checks

  1. Interpret the LED in its installation phase

    Before completion: rapid green is startup, flashing yellow pointing, flashing green network verification and steady green Ready. After successful installation the LED is disabled; off alone does not prove power failure.

    What the result means: A dark LED after a completed installation is compatible with normal operation. The same observation before completion has a different meaning; establish the phase and web status rather than diagnosing from the light alone.

  2. Read the data state without starting a session

    A running Standard data connection has its own information in the web interface. Data suspended can indicate temporary blockage. Automatic Context Activation determines automatic connection after installation; do not enable it simply to investigate an outage.

    What the result means: Network registration and an existing running or suspended data connection are separate evidence. Record the displayed state as it is; enabling automatic activation or creating a new session would change the condition being investigated.

  3. Preserve the active alert

    During installation steady yellow is a warning and steady red an error. Read the exact web warning rather than using color alone. After installation the active-alert symbol is the useful source of current event details.

    What the result means: An entry in the current Alerts list identifies an active event. Its exact identifier and text give support more useful evidence than a color; a past entry in Event log alone does not establish that the alert remains active.

  4. Compare outages with the configured idle interval

    Idle power save deregisters and closes down after configured inactivity. An open web interface counts as activity, so watching it can prevent the symptom. Review the documented wake-up method and UTC schedule with the installer; do not change power-control pins or send wake commands as an unapproved test.

    What the result means: A timing match can support an idle-power-save explanation, but observing through an open web interface keeps the terminal active. Failure to reproduce sleep while watching the interface therefore does not rule out the configured idle behavior.

  5. Collect current and historical evidence separately

    Support > Alerts lists active events; Event log also contains normal operation and past, cleared alerts. Compare those records with UTC call/data session times under Control panel > Logs. In Support > Diagnostics report, Generate report then Download report saves an evidence package; allow a few minutes. Keep it private and share with authorized support. Do not delete logs or restart the deployed link to collect it.

    What the result means: Keep the current alert list and historical event/session records distinct. Normal or cleared events in history are not automatically current faults; a private diagnostic report preserves context without deleting logs or restarting the link.

When to stop and get help

Stop when the next check needs physical antenna access, enclosure opening, rewiring, repointing, power-control changes, a reset or restarting installation. Preserve the deployed M2M link and hand the observations to its authorized installer. Do not generate paid test traffic or change settings to make an indication appear.

Request a U.S. technician ↗

What to tell support

Build one timeline: exact model and Rev K document, completed or incomplete installation, observed LED pattern and time, web network/data state, active event identifier and text, and the corresponding UTC session or historical event times. Note whether the web interface was open during an idle observation. Keep diagnostic files, credentials and precise site coordinates private for authorized support.

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.