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.

RV & marine / Detailed guide

SAILOR6110/6018: routine message queued or sent?

Check whether the routine message is queued or sent, then interpret its icon in the context of the requested confirmation. Preserve the message and timestamp before escalating.

Applies to: SAILOR6110 mini-C GMDSS with SAILOR6018 message terminal and SAILOR3027 antenna; user manual98-154172-B. Not the older6006 display or FleetBroadband150. These are routine observation checks for the authorized onboard operator.

Work through these checks

  1. Read the Outbox

    On the MESSAGE page, open Outbox and select the existing routine message. Manual page 42 says this list holds scheduled messages not yet sent. Record its time and current system status; do not submit duplicate messages as a reception test.

    What the result means: An Outbox entry is scheduled but not yet sent. It is evidence of the queue stage, not completed transmission. Preserve its original time and current status rather than creating a duplicate to force a result.

  2. Interpret Sent Items correctly

    Open Sent Items and select the message. Page 43 distinguishes a pending acknowledgement when Confirmation was requested from an acknowledged message. Without requested Confirmation, the sent icon means sent; it is not proof that a person read the message. Do not apply the separate Distress icons to routine messages.

    What the result means: Interpret a routine Sent Items icon together with its Confirmation request. Pending acknowledgement and acknowledged are distinct when Confirmation was requested; without that request, the sent icon establishes only sent status. None of these labels alone establishes that a person read the message.

  3. Preserve the relevant record

    Sent Items retains up to 1,000 messages; the oldest are automatically removed when that limit is exceeded. A missing old item alone does not prove failed transmission. Follow the vessel’s recordkeeping procedure, noting message time, icon, requested confirmation and active warnings for authorized support. Leave network, LES and safety settings unchanged.

    What the result means: The oldest Sent Items entries are removed after the documented 1,000-message limit is exceeded. A missing old entry therefore cannot determine whether transmission failed. Keep any existing vessel archive and message timeline separate from today’s visible list.

When to stop and get help

Follow the vessel’s operational procedures. Do not press Distress or run distress tests as troubleshooting; preserve operational communications. Do not clear logs, change ocean region, manually overwrite position, update firmware or interrupt power as a trial. Installation, damaged cables and persistent critical errors need authorized service.

Request a U.S. technician ↗

What to tell support

Keep a private record of the routine message time, Outbox or Sent Items location, exact icon, existing Confirmation request, current warnings and any matching vessel archive. Preserve the original message and relevant connection to the event; redact message contents, addresses and vessel/account identifiers before public sharing.

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.