Applies to: RockFLEET Assured with an installed NMEA 0183/2000 Power Hub. Not the older RockFLEET tracker.
Match your symptom
| What you see | What to do next |
|---|---|
| Identify the installed hub option | Privately record terminal and hub labels, firmware, chart-plotter model, interface type, time of last local output and last cloud report, and the exact symptom. Redact vessel positions, account credentials and configuration secrets from public images. Mark what was observed directly and what was reported by another operator. |
| Read forwarding state before changing it | These checks prepare a technical handoff; they do not decide which position is safe for navigation. Preserve the bridge’s approved position sources, alarms and fleet settings. Do not inject test positions, disable alerts, rewire the hub or reset the system during vessel operation. The bridge team and authorized installer handle navigation and commissioning decisions. |
| Compare local and cloud evidence | Privately record terminal and hub labels, firmware, chart-plotter model, interface type, time of last local output and last cloud report, and the exact symptom. Redact vessel positions, account credentials and configuration secrets from public images. Mark what was observed directly and what was reported by another operator. |
| Prepare support before updates | These checks prepare a technical handoff; they do not decide which position is safe for navigation. Preserve the bridge’s approved position sources, alarms and fleet settings. Do not inject test positions, disable alerts, rewire the hub or reset the system during vessel operation. The bridge team and authorized installer handle navigation and commissioning decisions. |
Work through these checks
Identify the installed hub option
The Power Hub NMEA option is fixed at manufacture. Ask the installer to match the label and commissioning record; a software reset is not evidence that an incompatible interface can be converted. Record any replacement since the last successful output.
What the result means: Privately record terminal and hub labels, firmware, chart-plotter model, interface type, time of last local output and last cloud report, and the exact symptom. Redact vessel positions, account credentials and configuration secrets from public images. Mark what was observed directly and what was reported by another operator.
Read forwarding state before changing it
The OEM configuration page flags nmeaForwardEnabled as a chart-output prerequisite and documents a false shipping value. Have the authorized installer compare the actual saved configuration with the intended interface. Do not paste its NMEA 2000 example into an NMEA 0183 installation or change alarm settings just to clear a symptom.
What the result means: These checks prepare a technical handoff; they do not decide which position is safe for navigation. Preserve the bridge’s approved position sources, alarms and fleet settings. Do not inject test positions, disable alerts, rewire the hub or reset the system during vessel operation. The bridge team and authorized installer handle navigation and commissioning decisions.
Compare local and cloud evidence
If an authorized operator can see a recent cloud report, record its time beside the local display failure. If neither path works, say so rather than labeling the antenna defective. Ask support to identify the next observation that distinguishes configuration, local integration and reporting service; keep each result tied to the same terminal and time window.
What the result means: Privately record terminal and hub labels, firmware, chart-plotter model, interface type, time of last local output and last cloud report, and the exact symptom. Redact vessel positions, account credentials and configuration secrets from public images. Mark what was observed directly and what was reported by another operator.
Prepare support before updates
Ground Control documents separate firmware components and configuration updates. Capture the installed versions and intended change first. Its local update process is for experienced personnel or work with support; Cloudloop access uses data. A version mismatch is a question for support, not permission to force an update on an operating vessel.
What the result means: These checks prepare a technical handoff; they do not decide which position is safe for navigation. Preserve the bridge’s approved position sources, alarms and fleet settings. Do not inject test positions, disable alerts, rewire the hub or reset the system during vessel operation. The bridge team and authorized installer handle navigation and commissioning decisions.
When to stop and get help
These checks prepare a technical handoff; they do not decide which position is safe for navigation. Preserve the bridge’s approved position sources, alarms and fleet settings. Do not inject test positions, disable alerts, rewire the hub or reset the system during vessel operation. The bridge team and authorized installer handle navigation and commissioning decisions.
What to tell support
Privately record terminal and hub labels, firmware, chart-plotter model, interface type, time of last local output and last cloud report, and the exact symptom. Redact vessel positions, account credentials and configuration secrets from public images. Mark what was observed directly and what was reported by another operator.
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.