NMEA 2000 Configuration

← Configuration · Equipment Register · Circuit Register

Network segments and power

Owner-confirmed, 6 November 2026: Ragtime has one NMEA 2000 network with two segments, A and B. Both segments have power injection behind the DC panel (DCP). The segments are joined by a power isolator (EQ-063) that passes CAN data while separating their positive supplies (owner-confirmed). This describes the owner-reported arrangement, not an independently traced electrical installation.

SegmentPower injection locationHistorical panel referenceStill to establish
ABehind DCP — owner-confirmedR1, handwritten “NMEA 2K A” under NAV INSTRShared 10 A CB-007 confirmed; local fuses, feed wiring and injection hardware untraced
BBehind DCP — owner-confirmedY1, handwritten “NMEA 2K B” under NAV INSTRShared 10 A CB-007 confirmed; local fuses, feed wiring, injection hardware and clock identity untraced

The panel aliases come from the historical connector schedule; the latest confirmation establishes the two segment names and injection locations, not continuity through those particular connectors. R1 and Y1 identify clamp lever colours and group positions, not conductor insulation colours.

Shared NAV INSTR supply

Owner-confirmed, 6 November 2026: Both segment A and segment B power injections are fed by one common 10 A NAV INSTR breaker CB-007 on the main DC panel. DC-N2K-01 identifies the common protected supply; DC-N2K-02 and DC-N2K-03 identify the feeds to A and B respectively. These are functional circuit identities, not additional protective devices.

The two segments share that breaker’s switching/protection; their positive backbone supplies remain separated at the A/B power isolator. Separate downstream fuses, any additional switches, split-point wiring, conductor sizes and negative-return routes have not yet been established. The 10 A breaker rating is owner-reported, not an assessment of cable or network component protection suitability.

Network and equipment inventory to complete

  • Record the physical backbone and drop routes, junctions and terminator positions.
  • Identify the power isolator’s manufacturer/model and physical location, and document its pin-level connections. CAN data continuity and positive-supply separation are owner-confirmed; negative/shield continuity and galvanic isolation have not been established.
  • Trace the common CB-007 output to the two injection feeds, identify any local fuses/additional switches and record conductor sizes and return paths. The shared 10 A NAV INSTR breaker is now owner-confirmed.
  • Link each connected device to its equipment record, segment and drop connection. Record bus power, separate operating supply, and any bus-interface power requirement independently; network attachment alone does not establish how a device is powered.
  • Record manufacturer power/load figures separately from onboard measurements and calculate segment loads once device allocation and power boundaries are known.

A and B are network segment labels, not physical equipment IDs. The physical power isolator is recorded separately as EQ-063. Segment A and B device allocations are recorded below; physical connections, cable lengths, any local protection and the isolator’s model/location still require documentation.

Segment A — connected equipment and power

Owner-confirmed, 6 November 2026: Segment A provides data-only connections for the Icom M510 VHF and ATB-1 AIS, and data plus bus power for the previously documented Yacht Devices YDWG-02 wireless gateway. The owner subsequently confirmed this is the complete segment A device list.

EquipmentNMEA 2000 segmentConnection roleOperating power source
EQ-003 — Icom M510 VHFAData only (owner-confirmed)Separate DC supply: DC-COM-02, FU-001, EQ-057 way 1
EQ-004 — ATB-1 AISAData only (owner-confirmed)Separate DC supply: DC-COM-04, FU-003, EQ-057 way 3
EQ-064 — Yacht Devices YDWG-02 wireless gatewayAData and power (owner-confirmed)NMEA 2000 segment A bus supply, injected behind DCP

The data-only classifications above record the owner’s installation description; interface/adapter details and pin-level power connections have not been traced. Gateway load/LEN, drop-cable routes, junction positions and segment A injection hardware and any local protection remain to be documented. Separate COM power circuits remain distinct from the NMEA 2000 data connection.

Segment B — connected equipment

Owner-confirmed, 6 November 2026: The owner confirms that the listed segment B devices are bus-powered except NAC-3, whose segment B connection is for data and whose operating power comes from its separate autopilot feed. The companionway console clock is also powered by segment B; its data connectivity has not been confirmed. This clarification supersedes the earlier blanket “all powered by the bus” description for NAC-3.

Equipment / owner labelSegmentBus power / separate supply
EQ-065 — Garmin GPS 24xdBSegment B bus — owner-confirmed
EQ-066 — B&G WS310BSegment B bus — owner-confirmed
EQ-067 — B&G DST-810BSegment B bus — owner-confirmed
EQ-068 — Orca Core 2BSegment B bus — owner-confirmed
EQ-069 — B&G Triton 2 autopilot controllerBSegment B bus — owner-confirmed
EQ-070 — B&G Triton 2 MFD 1BSegment B bus — owner-confirmed
EQ-071 — B&G Triton 2 MFD 2BSegment B bus — owner-confirmed
EQ-072 — B&G Triton 2 MFD 3BSegment B bus — owner-confirmed
EQ-073 — B&G NAC-3BData only; separate autopilot operating supply via DC-PIL-01 — owner-confirmed
EQ-074 — Yacht Devices “YD RA?” — model to confirmBSegment B bus — owner-confirmed
EQ-075 — Companionway console clockB power connection; data connection not confirmedSegment B — owner-confirmed

NAC-3 supply distinction, owner-confirmed: DC-PIL-01 supplies NAC-3 operating power separately from its segment B data connection. Exact power wiring, protection and any network-interface consumption remain to be documented; no measured zero bus load is claimed.

The three Triton 2 MFDs have separate stable equipment IDs. Their physical positions remain to be assigned to MFD 1, 2 and 3. “YD RA?” is retained as an uncertain owner label; YDRA-01 rudder adaptor is a tentative match to earlier discussion, pending model confirmation. Sensor interface hardware, including the WS310 connection into the network, has not yet been inventoried. Equipment names reproduce the owner’s labels; exact nameplate variants remain to be recorded.

Historical configuration notes — July 2025

The notes below are retained as historical configuration information. They do not establish the current device inventory, segment allocation or power arrangement; the YDAP-04 notes require reconciliation with the later NAC-3 installation.

Ocean Signal ATB-1

The ATB-1 AIS transponder produces NMEA2000 PGNs and is also capable of hosting an NMEA 0183 web server that can be used as a data source for connected applications such as the Garmin Boating App, AKA Navionics.

The boating apps connection to the TCP server hosted by the ATB-1 proved far too unreliable, with continnual disconnections, A UDP server would provide a much more stable service, but is not provided by the ATB-1 (or if it is, it is not documented well at all)

Our solution is to use the YDWG-02 NMEA 2000 Wireless gateway which allows us to configure a UDP server on a commonly recoginsed port 10110.

This server has provided reliable AIS target integration with the boating APP.

The ATB-1

Yacht Devices

Configuration settings to YD devices can be made using CANView and udating “Installation Description 2” in the Device properties.

Commands are in the format YD: [Command] [Param 1] [Param 2]

The following configuration setting have been applied:

YDAP-04

SettingNotes
YD:SIMRAD ONThis allows the Autopilot page in the B&G Triton2 MFD to display Autopilot information