Marine Electronics Commissioning and Sea Trials

The most expensive mistake in a marine electronics project is treating the moment the display lights up as the finish line.

Wiring determines whether a device can work. Commissioning determines whether it works correctly — and almost every configuration that matters is invisible from the outside. Which GNSS receiver is the network actually using? Does the depth read below the keel or below the transducer? Is the wind sensor's alignment offset entered? Is the radar's bearing offset compensating for a heading error that will change when the compass is recalibrated?

Commissioning is a stage with a checklist. Here it is.

#Stage 1: dockside

#Network integrity

• confirm exactly two terminators on the NMEA 2000 backbone
• measure network voltage at the backbone extremity, not the injection point
• confirm every device appears in the network device list
• resolve duplicate or conflicting sources
• set device instances correctly — this is what keeps port and starboard engines, and multiple tanks, correctly labelled
• record firmware versions for every device

#Power

• measure supply voltage at each device's own terminals
• run the windlass, thruster and engine start and watch for voltage sag at the displays
• confirm each circuit's protection rating and accessibility
• record the fuse and breaker schedule

See marine DC power for the underlying principles.

#Source selection

This is the step most often skipped and most often the cause of later confusion. Explicitly verify which device supplies:

Then check that the VHF is receiving position, because a DSC distress alert without position is a materially worse alert.

#Sensor configuration

• depth offset measured, set, verified against a known depth, and labelled with its convention — see depth sounders and transducers
• speed calibration started, to be completed on the sea trial
• wind alignment offset entered
• GNSS compass baseline offset entered
• tank and engine calibrations entered
• MMSI programmed into the VHF and any AIS transceiver, and confirmed correct for the vessel
• AIS static data entered: name, callsign, vessel type, dimensions and antenna position

#Autopilot pre-checks

• drive direction correct — a reversed drive is dangerous and easy to create
• rudder limits set with mechanical clearance
• rudder reference calibrated if fitted
• clutch or engagement operating correctly
• manual override and instant disengagement tested and understood by the crew

#Stage 2: sea trial

Pick a day with enough sea state to be meaningful and enough sea room to abort. Allow half a day.

#Position and heading

• confirm position against known harbour features and charted marks
• compare heading against a transit, a leading line or a known bearing
• check heading stability through a turn and at rest
• compare course over ground against heading and note the difference in known current — this is the sanity check that both sensors are behaving, as the GNSS guide explains.

#Depth and speed

• verify bottom tracking at rest, at cruising speed, and on both tacks on a sailing yacht
• complete the speed-through-water calibration on reciprocal runs to cancel current
• confirm sea temperature if provided
• verify the shallow and deep depth alarms actually sound

#Radar

• confirm the radar transmits and the picture is sensible on short and medium ranges
• overlay radar on the chart near a well-charted coastline and check alignment
• correct the heading source first, then apply any residual radar bearing offset
• adjust range and timing alignment if the manufacturer provides it
• learn the appearance of headlands, buoys, yachts, ships and rain — the training that makes radar useful in fog happens here, in daylight
• tune sea and rain clutter controls and note the settings that work honestly, without suppressing real targets

See marine radar.

#AIS

• confirm reception of nearby targets
• confirm transmission — the simplest check is asking a nearby vessel, a marina, or using a reputable shore-based receiver to confirm your MMSI and static data appear correctly
• set the CPA and TCPA profiles for harbour, coastal, offshore and poor visibility rather than accepting defaults

#Autopilot

This is the longest part of the trial and the most important on a shorthanded boat.

• run the manufacturer's automatic learn or dockside-to-sea calibration sequence
• steer to compass in flat water and confirm the pilot holds without hunting
• increase sea state and check response, rudder gain and counter-rudder behaviour
• test in a following and quartering sea, which is where an undersized or poorly tuned pilot reveals itself
• test wind modes on a sailing yacht, on both tacks, and confirm true wind is sensible
• test tack and gybe functions
• test route following, and confirm it prompts rather than turning autonomously at waypoints
• measure actual current draw in calm and in a seaway — this number goes into the energy budget
• confirm instant disengagement works under load

See marine autopilots.

#Alarms and edge cases

• set and verify depth, cross-track, arrival, CPA/TCPA and anchor alarms at useful thresholds
• confirm alarm audibility from the helm, the cockpit and the sleeping cabin
• test behaviour on loss of GNSS — physically disconnect the primary source and observe what the system does
• test behaviour on loss of heading
• test the backup navigation path: open the tablet, confirm offline charts, confirm it has a position

That last group is the one nobody does, and it is the group that determines what the boat does on a bad night.

#Stage 3: documentation

Leave aboard, physically and in a cloud folder:

• power distribution diagram and fuse list
• NMEA 2000 network diagram with terminator and injection points
• Ethernet diagram with switch locations and spare ports
• device list with models, serial numbers and firmware versions
• MMSI and AIS static data as programmed
• all calibration values and offsets, including the depth offset convention
• source selection as configured
• alarm thresholds and the profile definitions
• transducer type and location
• manuals, or links to them
• the commissioning date and who did the work

This pack is what makes the boat troubleshootable by someone who did not install it — including you, in three years, at night.

#Post-commissioning discipline

• Do not update firmware immediately before a significant passage. Updates have been known to reset source selection and calibration.
• Re-verify source selection after every update, as a standing habit
• Re-check radar alignment annually, and after any mast or antenna work
• Re-verify the depth offset after any haul-out or transducer work
• Sea trial before the passage, not on it.

#Bottom line

Wiring gets the boxes talking. Commissioning makes them tell the truth. Budget a dockside session, a proper sea trial and an afternoon of documentation — and treat the day the display lights up as roughly the halfway point.