Electronics CAN Sources list

Compute Bay Housing and Wiring Plan v10.5

v10.5, 2026-11-09. Nobotic USV // CD25D Conversion. What is inside the boat's two computer boxes, and the rules that tie them to the rest of the boat. Pi A, on the main battery, runs the boat. Pi B, on the backup battery, is its twin in a second sealed box, with its own watchdog, GPS, motion sensor and satellite modem. The plan also covers the central node, the small control box near the battery that switches loads and triggers releases. The idea: no single electrical event, above all a lightning surge on the main side, may silence both computers. Every backup is there so the boat keeps sailing, not only so it stays safe or calls home. Home for: what is inside the two compute boxes (secs 2 to 4), the watchdogs (sec 4.3), the central node's relay map (sec 11) and command paths (secs 10 and 12), and electronics cooling (secs 2.3, 3.5, 3.6 and 4.4). The final word on the two-island power layout (sec 5), the isolation bridges (sec 6), the lightning watch (sec 13) and the surge rules (sec 14). Elsewhere: every box, its holes and wiring, the sensors, power distribution (bus, fuses, breakers), the emergency bank, nav lights and comms hardware: Electronics and Wiring Plan. Every setting, limit, threshold, timer and address: System Settings Sheet. Parts and prices: Bill of Materials. How a node works inside, with drawings: Node Boxes Explained. Reasons: Design Decisions and Rationale.

TermPlain meaning
IslandA group of gear fed from one battery, with no wire path to the other group
Galvanically isolatedTwo circuits pass information with no metal path between them; the signal crosses as light, magnetism or an electric field
NodeA small team-built box with a microcontroller in it
DiscreteA single on-or-off wire carrying one bit, not data
PoEPower over Ethernet: the network cable carries the device's power and its data
PoE classThe power a PoE device asks for when plugged in (802.3af up to 15.4 W, 802.3at up to 30 W). The switch holds that much aside, used or not
Web APIThe switch's own documented commands, over the network; a Pi program uses them to switch a port on or off
SNMPA standard way to read a network device's state. On the TSW202 it is read-only: for checking, not control
RS-232, RS-485Two wired serial standards most science instruments speak. RS-232 is one device per cable; RS-485 is a shared two-wire line
Normally closed contactA relay contact that is closed while the coil has no power; powering the coil opens it. A normally open contact is the reverse
SacrificialAllowed to die in a lightning strike. Nothing the boat needs to survive depends on it

1. Summary

The design in eight lines, then the build order.

Build order:

  1. On arrival: fit check of carrier, CAN HAT and bracket (sec 3.7).
  2. On the bench: board plates (sec 3.3), CM5 stacks (sec 3.4) and cooling brackets (sec 3.5); prove both M.2 slots with drive and Hailo in together (sec 4.1); the node boards' burn-in (sec 10.2).
  3. In the boat: measure the hull laminate at the three glued spots, glue the Pi A, network switch and VESC A boxes (sec 2.3), bolt the Pi B box (sec 2.2).
  4. Wiring: box contents (sec 4), the islands (sec 5), shields (sec 7), the release channels (sec 10.3), the relay map (sec 11).
  5. First power-up: run the CM5 hard (sec 3.5), pull each Nano (sec 4.3), check the box humidity level (sec 2.4), meter each CAN shield (sec 7), check the detector's false triggers (sec 13.1).

2. Location and mounting

Where the two boxes go and how each is fixed.

2.1 Why inboard, aft of the settee

Both boxes mount inboard, aft of the settee, a few feet apart, on existing structure, with no hull holes, as far from both lightning side straps as space allows. Cable entries go on the bottom face with drip loops (a downward sag, so water drops off instead of following the cable in) hanging 3 to 4 in below the box, below the connectors at a long heel. Pi A, glued to the hull by its back face, is the exception (sec 2.3).

2.2 Mounting the Pi B box

Through-bolted by its back wall to the 3/16 to 1/4 in solid glass panel aft of the settee, with no plywood pad. Pi B makes under 5 W, so it needs no hull cooling. Check first: the bilge pumps mount on the panel's other face, on rubber feet, biased toward the Pi B side (the Gulpers thump). Lay out both faces on one template, and add the box's four holes to the shared drilling template, so a pump foot never lands on a compute-box nyloc.

  1. Tape the spot. Start each hole with the drill in reverse, or a brad point bit, so the gelcoat does not chip.
  2. Drill the four holes slightly oversize for 1/4-20 and epoxy the hole edges.
  3. Bed the box on butyl, for build and trials.
  4. Fit four 1/4-20 316 stainless bolts with nyloc nuts (nuts with a nylon lock ring): EPDM sealing washers (rubber glued to a steel washer) under the heads inside the box, fender washers or a G10 backing strip behind the glass.
  5. Snug the bolts evenly, in passes, until the bedding squeezes out.
  6. At the final fit before departure, re-bed on permanent sealant (5200 class) if a permanent glued joint is wanted.

2.3 Mounting the Pi A box

Glued by its back face to the hull skin below the waterline, for cooling, so its wall stays near sea temperature whatever the cabin does (why: Design Decisions R-8.1C). Where: aft of the settee, as far from both straps and bar runs as space allows, and at least 2 ft from the main battery and motor cables where space allows, for its two IMUs (sec 4.1; 2 ft is a guess at a safe distance). The back face (the base, opposite the lid) goes flat to the hull; entries and the bond stud go on the other faces, with drip loops. Three boxes are glued to the hull for cooling, all the same way:

BoxNotes
Pi AThe CM5 heat block and its gap pad ride the glued back wall (sec 3.5)
Network switch box: a third CXCESNS aluminum box (sec 3.1), wired to nothing (Electronics and Wiring Plan A6a)Holds only the TSW202 switch and its supply, clipped to a DIN rail on a long side wall, not glued: the floor is too shallow, since the TSW202 is 4.8 in deep (122 mm, datasheet) and the box 3.9 in. Their heat, about 5 to 15 W in all, runs rail to box wall to glued face to hull
VESC A box (the motor controller's): a fourth CXCESNS aluminum box, 11.8 x 8.3 x 3.9 in, wired to nothing (sec 4.4)Its floor is the cooling plate, glued straight to the hull

There is no motor cooler plate: the motor's water jacket is filled and plugged (Build Guide sec 5.2). The glue bed carries heat. For every hull-glued bed, thicken the epoxy with the #120 aluminum-oxide grit on hand (12 lb, bought; none to buy) as the only filler, loaded to about half the mix (Mike, 2026-10-26). Never 3M 5200, never 404 and never microballoons under a heat path. Glue the flat back face, never a side wall, and put the glands in the side walls near the lid. Check first: at the boat, measure the hull laminate thickness at each of the three spots.

  1. Grind the hull spot to dull glass.
  2. Sand the box back to bare aluminum and wet it out with plain epoxy at once: aluminum re-skins with oxide in minutes. Wet the hull face with plain epoxy too.
  3. Bed the box in the thickened epoxy, filling the hull curve with no voids.
  4. Glass a tab around the edge.
  5. Add a strap, or bolts into a glued-on pad, as the backup against peeling.

2.4 Condensation in the Pi A box

The cold wall is on purpose, so the box is built for the water that forms on it:

Desiccant is a first-setup aid, not the protection. Open: whether Pi A also needs a desiccant pack once its back sits on the cold hull; the hull laminate measurements settle it.

3. Enclosures

The boxes, how they seal, and the plate, stack and cooling inside them.

3.1 The boxes

Two identical CXCESNS aluminum junction boxes on one drilling template: 11.8 x 8.3 x 3.9 in, IP66 with a silicone gasket, about $66 each on Amazon. A third of the same box, ordered, holds the network switch at the stern, with its own hole schedule (Electronics and Wiring Plan A6a). The four lid screws tie lid to body well enough at lightning frequencies (below about 30 MHz) that the aluminum shields the wiring inside. Scrape to bare metal under the lid screws and at the bond stud (where the lightning wire lands). Wiring to the lightning copper: the Pi A box gets one 6 AWG bond spur (a short wire to the lightning ground network) under the Lightning Ground System Guide's substantial metal rule. The Pi B box gets none (sec 5.2).

3.2 Sealed, with no vent

Each box carries a desiccant pack and an internal humidity sensor, and every board is conformal coated (a thin varnish that keeps salt damp off the copper). No vent: the box sits in a dry cabin, so its glands stay dry, and a sealed box keeps its desiccant working longer (Electronics and Wiring Plan sec 3).

3.3 The board plate

A 1/8 in (3 mm) G10/FR-4 plate (stiff fiberglass sheet that does not conduct) carries all the boards in each box. On the bench:

  1. Cut a blank about 11.2 x 7.6 in, to ride on the ledge holes along both long walls.
  2. Transfer the ledge holes by paper rubbing, not from the vendor drawing. The corner posts are lid screws.
  3. Mount the boards on standoffs that bolt through with nuts, in any material. The plate is the insulation, so nothing needs tapping and no stray metal can short anything.
  4. Assemble the loaded plate before it goes in the box.

3.4 Stacking rule for the CM5

Each CM5 stack, carrier and CAN HAT, is bolted through standoffs at every level.

3.5 Cooling the CM5

The heat path: SoC (the main processor chip), heat pad, flat aluminum block, gap pad, box wall: the hull-glued back wall on the Pi A box, a sidewall on the Pi B box. The gap pad is Thermal Grizzly Minus Pad 8 (bought): 4 x 4 in sheets, 0.04 in (1.0 mm) and 0.08 in (2.0 mm) thick; one sheet cuts into four cooler-size pads. The pads do not conduct electricity, so the single-ground-reference rule holds.

  1. Stand the carrier upright on a slotted 1/8 in 6061 aluminum L-bracket, about 3 x 3 x 4 in, with two slotted base holes, bolted to the plate.
  2. A flat face goes against the pad, never the finned Pi cooler.
  3. Stack pads to fill any gap up to 1/8 in.
  4. Put a wave spring or spring-loaded screws in the clamp path, so a pad going flat over time cannot bleed off the clamping force.
  5. Slide the bracket in its slots to squash the pad about a quarter of its thickness. Press contact only. No fasteners into the box wall.
  6. After first power-up, run the CM5 hard for ten minutes. The wall over it should feel warm.

SoC temperature is a trended health number in the readings sent home.

3.6 Heat budget

About 30 W in the Pi A box (SSD and Hailo) and under 5 W in the Pi B box leave through a painted shell that runs 27 to 36 F (15 to 20 C) above cabin air.

Cabin airInterior resultVerdict
77 F (25 C)SSD near 117 F, CM5 near 136 FComfortable
113 to 122 F (45 to 50 C, sealed boat, tropical sun)153 to 162 FAbove the SSD comfort line, and near the CM5 throttle at 185 F (85 C)

The second row is why Pi A is glued to the hull. Pass/fail is the compute-box heat test in Build Guide sec 11.1: box interior at or below 122 F (50 C), with a 122 F simulated cabin and the hull spot at sea temperature.

3.7 Fit check on arrival

Before anything else, hold the upright carrier plus CAN HAT against the box width and check the bracket footprint.

4. Box contents

What goes in each compute box, the watchdogs that restart the computers, and what is kept out.

4.1 Pi A box (main island)

Pi A (every hole: Electronics and Wiring Plan A1): a CM5 (Raspberry Pi Compute Module 5) 8 GB / 32 GB on the carrier on hand, booting from its onboard eMMC memory chip. Its clock is capped at about 2.0 GHz in config.txt, below the CM5's 2.4 GHz top, so it runs cooler and lasts longer (System Settings Sheet sec 10). With it:

USB. Pi A's two USB ports take the lead from the USB hub box beside Pi A (entry S) and Iridium A's USB isolator (its cable in at entry 7). What is in the hub box: Electronics and Wiring Plan A1a; the serial addresses: System Settings Sheet sec 9.

The wing's CAN adapter: a DSD TECH SH-C30G isolated USB to CAN adapter (candleLight, so Linux sees a standard CAN port) for the wing trim actuator's own CAN link, in the hub box on a hub port (Mike, 2026-10-20). It is needed because both CAN HAT channels carry the boat's two buses. Its 120 ohm switch on. Pi A's control of the trim actuator so depends on the hub, as the wing's two readers do; Pi B has its own adapter for when it commands (sec 4.2). The wing's command path: sec 10.2. Iridium A: its own USB cable, through a USB isolator. The cable SparkFun ships with the RockBLOCK is an FTDI USB to serial cable (TTL-232R-3V3), its USB to serial chip molded into the USB plug. Plans: Box Plans v10.5/Iridium A Box v10.5.pdf and Box Plans v10.5/Iridium B Box v10.5.pdf.

  1. Cut the cable 8 in from the modem's small plug, inside the Iridium box, and rejoin it there in lever connectors, so the modem takes its 5 V from the box's Mean Well, never from USB (Electronics and Wiring Plan A11).
  2. Bring it into the Pi A box at entry 7, by the Altelix 4-port split gland it shares with the hub's lead (entry S; two ports plugged).
  3. Plug it into a DSD TECH SH-G01A USB isolator (ADuM3160; 1,500 V power and 2,500 V signal isolation, 400 mA out) inside the box, and the isolator into Pi A's second USB port (Mike, 2026-10-20), so a hung hub cannot cut off the main satellite link.
  4. Tie down and stake the isolator by the USB rule (below).

Never plug the cable straight into the hub or a Pi. If it is too short, a USB extension goes on the Pi side of the isolator, never between the cable and the isolator. The modem's ground is tied to the lightning copper through its antenna stub, so a plain USB link would tie Pi A to the copper; the isolator stops that path and passes only data. It cannot power the modem: the 9603 needs a supply of at least 500 mA and the isolator gives 400 mA, so it powers only the chip in the plug. The modem shows up as a USB serial port at 19,200 baud (System Settings Sheet sec 9). USB rule. Every USB plug in the box (the hub lead, Iridium A's isolator and the RockBLOCK cable's plug in it) hangs no weight.

  1. Clamp each cable to the plate within 2 in of the plug.
  2. Stake the plug body with a dab of removable adhesive. Zip ties are fine for cables; board stacks use their screws.
  3. The hub takes a detachable USB lead, not a captive cable: clamp and stake its hub end the same way in the hub box.
  4. At the hub, zip ties also hold every plug in its port (Mike, 2026-10-19). The hub sits on standoffs (short spacer posts; the M3 nylon kit on hand) so the ties pass under it; each tie wraps round the hub body and across the plug grips.

The hub's screw-lock holes (threaded holes beside the ports, for cables with locking screws) are not used, and no screw-lock cables are bought. Watchdog WD-A: an Arduino Nano Every (on hand), main island, on its own 5 V from a Pololu D36V6F5 (sec 4.3).

The kill line's wiring. It lands on the VESC's servo plug PPM pin, active low (System Settings Sheet sec 2).

  1. At Pi A: the PC817 output's V2 on the cable's kill core, its G on the ground core.
  2. At the VESC: the kill core on the servo plug's PPM pin, the ground core on the servo plug's GND beside it.
  3. In the harness: a 10k resistor (from the resistor kit on hand) from the COMM plug's 3.3V to PPM. It holds the line high (motor allowed) whenever the PC817 is off, so a loose kill wire cannot stop the motor.

The safe-mode wire. One wire inside the Pi A box from a WD-A output pin to Pi A header pin 37 (GPIO26), through a resistor pair so the Pi sees about 3 V, not 5 V: the 15k in the wire, the 22k from pin 37 to ground (swapped, the pin would see only about 2 V). No new box hole. WD-A sets it before the restart that starts safe mode (sec 4.3); a dead WD-A, a cut wire or no wire reads as a normal start. Pi A's motor kill pin, when assigned, must not use pin 37. GPS A: a hiBCTR NEO-7M module (bought in a 4-pack; two fly, two are Boat 2 stock): TTL serial at 3.3 to 5 V, SMA antenna, single-band GPS with GLONASS, good to a few yards, position only. Only the antenna coax crosses the box wall. The board has a soldered 5-pin male header and no bare holes. On the bench:

  1. Check the board's pin order.
  2. Put one 4-pin Dupont housing (the RLECS 4-pin female leads, bought) on VCC, GND, TX and RX; PPS unused. Seat it fully.
  3. Run a zip tie lengthwise over the plug and around the board, so it cannot back off.
  4. Tie the cable to the plate within about 1 in.
  5. Add a dab of electronics-safe silicone or hot glue.

Push-on pins are banned only in release logic (Electronics and Wiring Plan sec 4), and the boat wiring standard's solder rule (ABYC E-11) does not apply, since the Dupont pins are crimped. Not done: unsoldering the header to fit screw terminals (more bench work for a small gain). IMU A1 and IMU A2: two BNO085s on the same I2C pair (I2C: a two-wire data link between boards), A2 set to the BNO085's second address.

  1. Put one at each end of the plate, as far from the converter as space allows (the box's distance from the battery and motor cables: sec 2.3).
  2. Mount each flat and square to the plate, rigidly, with an arrow on the plate marking the board's forward axis.
  3. Enter each one's own heading offset and roll and pitch level offsets (System Settings Sheet sec 7).

When A1 and A2 disagree past the set limit (System Settings Sheet sec 7), Pi A falls back to the GPS track and gyro, flags it and sends an alarm home. Heading comes from the three BNO085 IMUs (bought; the third, IMU B, is in the Pi B box) and the GPS track. Not fitted: the ZED-F9P moving-base heading pair and its UART; an IMU elsewhere in the boat (it guards only against magnetic trouble near the Pi A box, and costs a long I2C run, unreliable past about 3 ft, a box hole and a sealed box; Design Decisions R-8.2A). Storage, solid state only: one 4 TB NVMe SSD (WD Blue 4 TB, bought) in the carrier, for the readings log and the sound archive. Neither the drive nor the Hailo rides USB.

Logging: SQLite on the SSD for the structured readings (10 Hz IMU, GPS and VESC; 1 Hz environment; camera frames on events), in WAL mode, with a daily checkpoint and a monthly compaction. Compressed batches go home over Starlink; the fallback is the last 24 hr as a position-only line by Iridium SBD (short burst data, Iridium's small-message service). Power section: one small branch on its own auto-reset breaker at the busbar (Electronics and Wiring Plan sec 7.6), wired in this order: breaker, TVS surge diode, terminal strip, WD-A's relay, converter (the Mean Well DDR-60L-5), carrier. Terminal strips; no MEGA fuse, no blade-fuse block. WD-A's relay contact sits in the 24 V feed ahead of the converter; WD-A's own D36V6F5 takes its 24 V ahead of the relay (sec 4.3).

4.2 Pi B box (backup island)

The backup computer, with its own watchdog, GPS, IMU and satellite link, all on the backup battery. Pi B (every hole: Electronics and Wiring Plan A2): a CM5 on its carrier with its own Waveshare 2-CH CAN FD HAT, stack staked.

Watchdog WD-B: an Arduino Nano Every on the emergency bank, on its own 5 V from a Pololu D36V6F5 (sec 4.3). It:

WD-B's serial line to Pi B runs through a logic level converter. Both wires go through one HiLetgo 4-channel logic level converter board (from the 10-pack on hand, bought 2026-10-06) in the Pi B box, its 5 V side to WD-B and its 3.3 V side to Pi B (Mike, 2026-11-02: "i think the converter board sounds more reliable"). It is needed because that line carries the backup battery reading, a 5 V Nano output into a 3.3 V Pi pin; it also gives Pi B's 3.3 V send a clean 5 V at WD-B. Pi A's heartbeat runs Pi to WD-A only and needs nothing. Drawn in Box Plans v10.5/Pi B Box v10.5.pdf. WD-B never cuts Pi B's power for lightning (sec 13). GPS B: the second NEO-7M, emergency powered, its coax entering this box, wired like GPS A (sec 4.1), so Pi B always has live position, in command or as the beacon. IMU B: the third BNO085, mounted and set like IMU A1 and A2: flat and square, a forward arrow on the plate, its own heading offset and roll and pitch level offsets (System Settings Sheet sec 7). Iridium B: linked like Iridium A (sec 4.1): its own cut RockBLOCK cable, the modem on the Iridium B box's Mean Well, the USB plug into a second DSD TECH SH-G01A USB isolator (one of two bought) in a Pi B USB port. The cable enters at entry 7 in a split gland. Iridium B's 24 V comes from its own 5 A auto-reset breaker on the backup battery board (Electronics and Wiring Plan A10). Pi B's own link to the wing actuator: a second DSD TECH SH-C30G isolated USB to CAN adapter (Amazon B0CDGGBZDT) inside the box, on a Pi B USB port, joins the wing trim actuator's own CAN link as a third drop, tapping the wing CAN pair at the wing box, not at the hub box (Mike, 2026-11-04; Electronics and Wiring Plan A17). Its 120 ohm switch is off, since its run is a branch. Its cable enters by entry 4 (Electronics and Wiring Plan A2). Pi B uses it only when it is in command; the two Pis never both command the actuator. Pi B's USB then carries two things: Iridium B's isolator and this adapter. Bilge pump 2 is on Pi B's side. Pump 2 runs from the backup battery at all times (sec 5.2), so its manual-on and running line belong to Pi B's side, not the central node (the node's opto inputs share one common with the main 0 V). WD-B watches the running line. Pi B keeps pump 2's manual-on, so shore can run it, and runs its monthly 5-second exercise. Nothing from Pi B or shore stops pump 2 (sec 5.2). Open: where pump 2's two signal wires enter on Pi B's side, and which relay module switches its manual-on. The backup converter's remote on/off is Pi B's too: Pi B turns the converter on only when the main side is truly dead, never just because it took command (sec 5.2). Inter-box link: only the main-island-alive discrete from WD-A, through an optocoupler (a HiLetgo PC817 board). No heading UART between the boxes. Not fitted: an ADuM1201 isolator for either Iridium line; each modem reaches its Pi over USB through a USB isolator (secs 4.1 and 4.2).

4.3 The watchdogs: default ON, and recovery

Two watchdogs, one per island, hardware only. Both rail switches default ON: the switch conducts while the watchdog is dead, and the watchdog must act to cut or cycle power, so a dead watchdog leaves its computer powered.

Bench check: pull the Nano out of its carrier and confirm the computer stays up. Safe mode, the restart rule. When WD-A restarts Pi A for the third time within about an hour (the count: System Settings Sheet sec 10), it first sets the safe-mode wire (sec 4.1), and Pi A starts from its safe copy on the eMMC.

Open: whether the CM5's startup reads the header pin to pick the safe copy; Ken's check on a real CM5, in the software repo, settles it (a fallback is written up there). Handover, take-back and hand-back. One computer commands at a time (why: Design Decisions R-9.2A).

The handover numbers: System Settings Sheet sec 10. The failover reset and every signed command come over Iridium or Starlink (HMAC: a secret-key signature that proves a command is genuine). The watchdogs take no command from shore, on purpose: shore's commands go to the computers. Remote recovery is that signed reset plus reimaging over Iridium (authenticated rsync, then a watchdog-run swap that reverts by itself on a failed update). Software built to take a hard power cut (WD-A's rail cycle is the only way to reboot a hung computer):

Not fitted: a pre-cut warning wire from WD-A (the safe-mode wire only picks which copy starts) and a flush-on-warning handler.

4.4 What is deliberately NOT in these boxes

Everything below lives outside the two compute boxes, on purpose.

Not in the boxesWhere it lives
Central node: the release channels and the release enable relay on its own 30 A module, the four cord puller reversing relays, monitoring, the Ewellix drive and its power-cut relay, the two 8-channel relay modules (sec 11), the two YRDZXG 24 to 12 V converters (bow lantern; post whites), fuses F1, F2 and F4, the post wind meter's 5 V regulator, and the post cables' landings (Boat 1 has no aft junction box)One box (the TICONN clear-lid box, sec 10.2) near the battery, busbars and compute area. The post lights cable, the post wind meter cable and rudder encoder A's lead each run in one piece to the node, the way the horn pair runs (secs 10.2 and 11; Electronics and Wiring Plan A3). If the node box has no room, the two sealed light converters (wire leads) sit on the hull right beside the node. Open: whether the two light converters fit inside the node box; laying out the node settles it
Release Node B (sec 12)The stern
Battery watchman (SBMS0 + JK balancer, on no bus, controls nothing)The BMS box as bought, beside the battery box (Electronics and Wiring Plan A4)
USB hub (fed from Pi A's 5 V), the 12 V converter for the SDI-12 sensors, the dAISy, the science serial adapters, the wing reader and the wing's CAN adapter (secs 4.1 and 10.2)Its own small box beside Pi A (Electronics and Wiring Plan A1a)
MOTU M2, the hydrophone's USB audio boxIts own box; only its USB lead enters the hub box, by one of the hub box's three glands, to a hub port (Mike, 2026-10-20). Open: the MOTU M2's own box; picking it settles it
FSESC boxNot fitted on either boat
Network switch box: only the TSW202 switch, with its SFP module, and its 54 V supply, both on a DIN rail on a side wall (sec 2.3)The stern, an aluminum box glued to the hull
Network surge board: the five Ethernet surge protectors and their ground barA small board on a bulkhead near the deck, where the outside network cables first come inside (Electronics and Wiring Plan A6a)
VESC A (VESC B and its phase-transfer contactor are Boat 2 only)Its own sealed CXCESNS aluminum box on the cockpit web at the motor, its floor glued to the hull (below)
Iridium modem ASmall box near Pi A, main bank; isolated 5 V (sec 13.3); USB through an isolator in the Pi A box to Pi A's second USB port (sec 4.1)
Iridium modem BSmall box near Pi B, emergency bank, on the backup battery board's 5 A breaker; isolated 5 V (sec 13.3); USB to Pi B through an isolator (sec 4.2)
The wet lab box (a small node that switches each wet lab part and reads its sensors)Beside the wet lab (Electronics and Wiring Plan A18)
AS3935 detector mini-boxWithin 3 ft of Pi B
The Starlink MiniBare on the aft deck, with no box (Electronics and Wiring Plan A13); its Cat6 runs to the TSW202 at the stern
The PoE light driver (PoE Texas AT-LED-24V, bare board)Its own small dry box, on TSW202 port 6
The wing's eight slip ring wires: the trim actuator's 24 V and CAN, the tip wind meter's RS-485 and the wing compass's RS-485The wing box below the deck, where the wing's wires enter the hull: three hull cables leave the can by three PG9 glands in its wall and go down through their own deck gland into the box (Electronics and Wiring Plan A17; the can's glands: Wing Can Spec Sheet)

Full contents and every wall entry: Electronics and Wiring Plan Appendix A (A3 for the central node, A6a for the network switch box). Cooling the switch and the motor controller. Both sit in the same CXCESNS aluminum box, glued to the hull in the heat-carrying epoxy of sec 2.3 (the switch box: Electronics and Wiring Plan A6a). The VESC A box sits on the cockpit web at the motor; its floor is the cooling plate, glued straight to the hull, with no separate plate and no hole in the floor.

Full build: Electronics and Wiring Plan A7 and Box Plans v10.5/VESC A Box v10.5.pdf (the full-size drilling template for Boat 2 is Old/Flipsky Hole Pattern 2026-10-26.pdf). Both boxes are wired to nothing and stay off the Lightning Ground System Guide's list of metal wired to the lightning copper (its sec 6.2).

5. Two island power layout

No single electrical event, above all a lightning surge on the main rail, may kill both computers. So there is no copper power path and no shared space between the islands: each has its own box, computer, watchdog, GPS and Iridium voice path.

5.1 Main island

The 32 kWh main bank, Pi A, VESC A (VESC B is Boat 2 only), the MPPT bank, the central node and its relay modules, the rudder actuator, and every normal load. Pi A runs the boat. The central node, steering, the wing box and both release buses sit on the backup-fed bar of the main bus board (sec 5.2), still on the main side and its negative. The rudder actuator is one Ewellix CAHB-22 at the 13 in station (Steering System Handbook sec 3): 2,250 lbf (10,000 N), 11.8 in stroke, 24 V DC, self-locking screw, built-in position feedback, no CAN, driven by the central node (sec 10.2). No backup actuator, no FSESC, no encoder B, no pull-pins on Boat 1. BOAT 2 ONLY: the Thomson Electrak HD24B026 is a CAN device; on the emergency bank its transceiver ground would tie the islands together, so steering stays on the main island.

5.2 Backup island

The backup battery always runs Pi B's side, and keeps the boat steering when the main side dies. The bank: the bought Dyness 24V 100Ah LiFePO4, 2,560 Wh, with its built-in 100 A BMS with low-temperature cutoff (the bank, its restraint, terminal boots and 30 A ANL fuse: Electronics and Wiring Plan A10). Its own solar charges it through its own SmartSolar 75/10: two 50 W flexible panels in series, glued flat like the deck array (Build Guide sec 4.4). What it powers. Always: the Pi B box (Pi B, WD-B, GPS B, IMU B), Iridium modem B, the detector mini-box and bilge pump 2. Only when the main side is dead: the backup-fed bar on the main bus board, through the backup converter (below).

Bilge pump 2 (Gulper 320, about 3.25 A) is fed from the Dyness at all times, on 14/2 from the roll on hand. Wiring and mounting: Electronics and Wiring Plan A10; the pumps: Build Guide sec 3.6.

The backup converter: a Victron Orion-Tr Smart 24/24-17 isolated (ORI242440120, 400 W, 17 A; Amazon B07YN4LGR9; not the plain B07DQ5SCQM, not the non-isolated ORI242440140), backup battery in, main side out, onto the backup-fed bar. Wiring: Electronics and Wiring Plan sec 7.6 and A10.

The backup-fed bar is a small bar pair on Boat 1's installed main bus board. It carries five lines, each on its own breaker:

LineLoadBreaker
2Release Node B30 A
3The central node15 A
4Release bus A: the cord pullers and horn A30 A
5Steering20 A
14The wing box5 A

It is fed from the branch bar through a Victron Argodiode 80-2SC one-way diode block (about 0.3 to 0.45 V drop), so the converter cannot feed the whole main side, and from the converter's output. Line 13, the Orion-Tr 24/24-5 feed into the backup battery, stays on the branch bar, never on the backup-fed bar, or the two converters would feed each other. Detail: Electronics and Wiring Plan sec 7.6. The two bridges between the batteries.

The floating negative is wired to nothing. It touches the world only through its own two 50 W panels, the two isolated Orion-Tr converters, and the isolation bridges of sec 6. So the Pi B box gets NO bond spur to the lightning copper, ever; its lid screws are its only lid-to-body connection, and that is correct. Operation. Pi B sleeps most of the time, waking on its own clock alarm a few minutes each hour to copy state over Ethernet (the schedule: System Settings Sheet sec 10); WD-B can force it awake. When Pi A loses a part or goes silent, Pi B takes command with the main side still alive (sec 4.3), and the backup converter stays off. On the backup battery alone (the main side dead), the boat steers or drifts, anywhere on the route (Boat 1 never reaches the Southern Ocean):

The levels and timers: System Settings Sheet sec 4. The energy: sec 5.3.

5.3 Backup island power budget

What the backup battery spends a day, and what its two panels bring back.

LoadDrawWh/day
WD-B (Nano Every + its D36V6F5)~0.3 W continuous~7
Iridium B, listen standby~0.2 to 0.3 W~5 to 7
Pi B, duty cycled ~8%~3 to 3.5 W awake~10 to 15
Pi B shut down (~92%), with its start-up settings (System Settings Sheet sec 10)~0.01 W~0.2
GPS B~0.3 W duty cycled with Pi B~1 to 2
Bilge pump 2's Ultima switch, standbyNot publishedNot known
Design point, normal operation (without the unknown)~25 to 32
Pi B in command, main side alivePi B awake full time~60 to 85 more, made up by running the Orion-Tr longer (sec 11)
Steer, backup alone (a guess)Pi B awake, rudder moves, converter and node on for each move, the hourly wing check, pump 2 standby~145 to 165
Drift, backup alone (a guess)Pi B waking every 3 hours~20 to 35
em-trak (AIS) on the backup (a guess)~6 W in all, with the converter and node kept on~150 more

What the two 50 W panels gather (computed with a system factor K of 0.72):

WeatherWh/day
A gale (peak sun hours 0.5 to 1.2)about 36 to 86
Boat 1's winter crossing eastabout 70 to 220
Typical mid-latitude weatherabout 252 to 360
The tradesabout 320 to 400
A Southern Ocean summerabout 108 to 180

So solar carries the design point in nearly all weather, and drift everywhere. Steering on the backup alone runs a surplus in the trades and mid-latitudes; in the winter crossing east or a long gale the battery can run down to the converter's cutoff, and the boat drifts until the panels refill it. The bank alone covers about two to nearly three months of total darkness at ~25 to 32 Wh/day: 2,560 Wh rated, about 2,050 Wh usable from 90 to 10 percent, about 64 to 82 days.

6. Isolation bridges

The islands talk only through galvanically isolated paths:

PathHow it is isolated
CAN, both busesEach HAT's onboard 5 kV isolation. Each bus is a separate barrier crossing
EthernetTransformer isolated on each port, by the standard. Each Pi runs its own Cat6 to the TSW202; the five deck and near-deck cables reach it through Ethernet surge protectors (Lightning Ground System Guide sec 7.4). A strike may still kill the switch, costing Starlink, the cameras and the Pi-to-Pi Ethernet, not both Pis
Inter-box link (main-island-alive discrete only)One optocoupler on one M12 cordset (sec 4.2)
Orion-Tr Isolated 24/24-5Transformer isolated, sacrificial (sec 5.2)
Backup converter (Orion-Tr Smart 24/24-17 isolated)Transformer isolated; on only while the main side is dead (sec 5.2)
Pi B's wing CAN adapterThe DSD TECH SH-C30G's own isolation, as on Pi A's (sec 4.2)
Bilge pump 2's float switchThe Ultima switch's sealed sensors never touch the water, so the bilge water does not join the two sides (sec 5.2)
StorageThe SSD attaches to Pi A only. Pi B keeps a copy of the essential state (position, mission phase, recent readings), refreshed over Ethernet each wake

These bridges close the rail path only. Antenna line surges and ground shifts are handled by the surge rules (sec 14), the metal boxes, and keeping the two Iridium chains apart.

7. Grounding and shields

Three rules decide where boxes, circuits and cable shields may touch the lightning copper.

  1. Chassis to lightning network. The Pi A box gets one 6 AWG Layer 2 bond spur to the nearest ground network point, on its own stud and nut, carrying nothing except during a strike. The Pi B box gets none (sec 5.2).
  2. Circuit ground to chassis: never. The main negative touches the network exactly once, at the battery junction (Lightning Guide). A second tie at a box would close a loop that strike current runs through the electronics. So boards sit on insulated standoffs, and plates and boxes carry no circuit current.
  3. Cable shields.

First-setup check: on each CAN drop, meter from the far shield end to the Pi A stud for continuity (budget cordsets sometimes leave the shield out, and a shield tied at neither end is an antenna).

8. Wall hole schedules

Every hole in both compute boxes, with its gland and drill size, is in the Electronics and Wiring Plan: Appendix A1 for Pi A, A2 for Pi B, and the rules for every entry at the head of Appendix A (Pi B's entries all on its bottom face, Pi A's on any face but the glued back face; no M12 receptacles on any box). No load current passes through either box except its own feed and, in Pi A, the USB hub's 5 V lead (entry 12): the boxes pass buses, radio, coax and USB only. Switched loads and their harness live at the central node and the aft junction.

8.1 Pi A box (ten entries in nine holes, + bond stud)

Electronics and Wiring Plan A1. Entries 5, 9, 10, 13 and 14 are not drilled. The watchman and science lines, the dAISy's coax and the wing cable enter the USB hub's own box (A1a). Pi A takes two holes for the hub box: entry 12 for the hub's 5 V lead out, and one Altelix 4-port split gland shared by entry S (the hub's USB lead) and entry 7 (Iridium A's RockBLOCK USB cable, to its isolator inside), two ports plugged (sec 4.1).

8.2 Pi B box (9 entries)

Electronics and Wiring Plan A2. Entry 7 takes Iridium B's USB cable in a split gland (sec 4.2). Entry 4 takes the cable for Pi B's own wing CAN adapter (sec 4.2). Where pump 2's two signal wires enter is open (sec 4.2).

9. Cabling and routing rules

The cabling rules are wiring, and their home is the Electronics and Wiring Plan. What this plan leans on, in one line each:

9.1 CAN cable and layout

One straight backbone per bus in NMEA 2000 Micro-C cable, molded tees and terminator plugs. The house bus takes its 12 V once, from its own busbar branch (line 8), never from inside a Pi box; the em-trak's bus interface draws from it. The control bus has no power feed: on every control drop the red core is cut back and taped at both ends, and the black core lands on the device's CAN ground as the ground reference. Electronics and Wiring Plan secs 5.1 to 5.3.

9.2 Two buses

Control and house, so a babbling device cannot delay steering or throttle traffic. Only the Pis touch both, each across its own isolation barrier (sec 6), and the battery watchman is on no bus: Electronics and Wiring Plan sec 5.4.

9.3 Loop area rules

Supply and return in one jacket, one lashed bundle per route, runs along the centerline, no spare coiled in a circle: Electronics and Wiring Plan sec 7.7. They are the first lever against lightning (sec 14.2).

9.4 Ferrites

Genuine mix 31, only on the cables that leave the cabin (about 11 boat wide), glued down, never hanging on the cable: Electronics and Wiring Plan sec 7.5.

10. Command layout

How each computer command reaches its device, and what each device does when commands stop.

10.1 The command patterns

Every device the boat can command uses one of these patterns. No safety default depends on a message arriving: every actuator has a named node, a named bus and a safe place to sit with no power.

#PatternHow it worksWho uses it
1CAN with a translator nodeThe device is dumb (burn wire, solenoid, relay coil, DC motor) and the central node drives it by plain wireRelease channels, switched loads, the Ewellix steering actuator
2CAN nativeThe controller is built into the device and the Pi talks to it in its own dialectVESC A in VESC format, keeping its three separate layers: CAN, a UART backup and a discrete GPIO kill line (Build Guide sec 5.1); the em-trak in NMEA 2000 (Boat 2's Electrak in J1939); the wing trim actuator in J1939, on its own short CAN link, from Pi A through the wing's CAN adapter or from Pi B through its own when it commands (sec 10.2)
3Direct lineData-heavy talk on private serial, USB or EthernetIridium x2, dAISy, GPS, Starlink, the PoE cameras, the TSW202 (Web API out, SNMP back), the science instruments on FTDI serial, the wing's tip wind meter and compass on the wing reader (sec 10.2), and the SBMS0 text stream
4RadioA radio link to a deviceNobody: the wing's trim actuator, tip wind meter and compass are wired down through the slip ring

The watchdogs work the other way: the Pis report heartbeats, and the watchdogs hold the rails. The Pi says what it wants; devices do the mechanics. Every device has a planned answer to command silence:

DeviceAnswer to silence
Ewellix steering actuatorThe self-locking screw holds position; the drive has no power
VESCRamps to zero
Release channelsStay disabled: enable relay open, every MOSFET off (no burn-wire short relays)
Wing trim actuator (Thomson Electrak MD)Stops and holds on CAN silence (Wing Trim Actuator Installation Guide sec 5). Strong wind still swings the tail flap straight against its give-way spring, so feathering needs no power and no command
Switched-load relaysDrop out with the node (sec 11)

10.2 Node platform

The three team-built nodes: the central node here, the minimal Release Node B at the stern (sec 12), and the wet lab box beside the wet lab, which switches each wet lab part on Pi A's orders (Electronics and Wiring Plan A18; Flow-Through Wet Lab Design sec 10). How a node works inside, with drawings: Node Boxes Explained. Box contents, entries and monitoring: Electronics and Wiring Plan sec 4.1 and A3. The central node's box: the TICONN IP67 clear-lid box, 17.7 x 13.8 x 7.9 in outside (inside 16-7/8 x 12-7/8 x 7-1/2 in), with a grid mounting plate, $94.99 (Amazon B0BZR3M8PK), ordered 2026-11-02; one box, not two. Its layout: Box Plans v10.5/Central Node v10.5.pdf. The processor: an STM32 G4 on a NUCLEO-G431KB (about $20), in a Nano screw-terminal carrier with a CAN transceiver breakout, picked for CAN on the chip and the team's Rust tools (Embassy).

The expander: the Nano header's 22 pins are not enough, so one MCP23017 I2C expander board, screw-terminal version (~$6), adds 16 on/off lines over the Nucleo's two-wire I2C link.

Pin map: 19 native pins used, none spare; A2, A4 and A5 never used. Every solder link stays as shipped (Mike, 2026-11-09: no fine hand work at the bench). From the factory (ST manual UM2397, Table 9) A2 reaches no chip pin (SB14 open), and A4 and A5 are joined to the I2C pair on D4 and D5 (SB2, SB3), so A2, A4 and A5 are never used; the firmware sets the chip pins behind A4 and A5 (PA5, PA6) as floating inputs. A7 (PA2) stays tied to the USB serial link (SB1), so the USB serial console is not used: programming still works, and logs go over CAN.

PinUse
D0Wind in: the post's Calypso CMI1018 (USART1 receive only; the meter sends on its own at the data rate set once with Calypso's PC app, so the node never writes to it; the cable's green core is parked on its own block). Its cable runs in one piece from the meter on the post to the node (Electronics and Wiring Plan A3 entry 17, port b); its 5 V comes from its own Pololu D36V6F5 in the node, behind fuse F1 (1 A), fed from the node's 24 V, never 24 V into the meter, so the meter is on only while the node's feed is on
D2, D10CAN TX and CAN RX
D4, D5I2C data and clock: the expander, the BME280 and the humidity board
D6Rudder encoder A (timer input). Its Belden 6504FE lead runs in one piece from the rudder stock to the node (Electronics and Wiring Plan A3 entry 17, port c); its 3.3 V from the node
D9Steering PWM (TIM1, 20 kHz)
D13Steering direction. It is the boot pin: at the bench, meter it at power-up and confirm nothing pulls it high
A0Steering current sense
A1Ewellix position wiper
D111-wire chain 1 (the battery probes: the cell-temperature trip)
D121-wire chain 2 (air)
D3The release enable relay's coil (its own 30 A single-channel module, sec 10.3)
D7, D8, A3, A6, A7, D1Release gates for channels 1, 2, 3, 4, 5 and 6
A2, A4, A5Never used (above)

The release gates avoid D12 and D5 (pulled high at reset) and D13 (the boot pin). A7 also reaches the USB chip's serial input through SB1; if that input carries a pull-up, the MOSFET board's own pull-down still holds the gate off (a guess: about 0.7 V with a 10k pull-down against a 40k pull-up); each MOSFET board's own pull-down holds its gate off until the firmware starts. The release lines and the release enable relay never move off native pins. No soldering on the boat.

Board preparation, in order:

  1. A week of powered burn-in, all the node boards as one lot.
  2. A heat cycling check.
  3. Conformal coat.
  4. Stake each board in its carrier (after burn-in).
  5. Seal it in its box.

The node's own hardware watchdog (the STM32's) restarts the node if it hangs (its timeout: System Settings Sheet sec 10). On the backup side Pi B can also power-cycle the node by cycling the backup converter (sec 5.2). Steering command path. The computer in command (Pi A, or Pi B when it commands, sec 4.3) sends the rudder target over the control bus to the central node. The node drives the Ewellix CAHB-22 through the Pololu G2 24v13 drive (hardware and wiring: Electronics and Wiring Plan sec 5.6): it sets the direction, ramps the drive up, holds it, and stops at the target reading. The move limits and the stall-stop numbers: System Settings Sheet sec 3.

BOAT 2 ONLY: the backup is an aux rudder, not a second actuator, on release channels 7 to 9 (sec 10.3). Boat 2 keeps one pull-pin, on its primary actuator, so a dead actuator can let the rudder trail for the aux rudder. The Thomson Electrak primary and the aux-rudder Electrak take position commands over native J1939, straight from Pi A, on the main bank; the Electrak's own overload cut-out is the backstop. The backup VESC's phase-transfer contactor takes signed commands only, its coil pulsed by the central node from the main bank. No FSESC box on either boat. The wing's command path. The wing's program runs on the computer in command: Pi A, or Pi B when it commands. The trim actuator (Thomson Electrak MD, CNO control option, MD24A025-0050CNO) stays on its own short CAN link through the slip ring, kept off the boat's two buses, and speaks J1939 (settings: System Settings Sheet sec 8). The MD sleeps under 2 mA, so its 24 V feed is not switched. The wing-tip wind meter (Calypso ULP CMI1017, RS-485) and the wing compass (WitMotion HWT905, RS-485, on its own pair) come down to the hull as well; the post's CMI1018 (UART/I2C) runs on its own cable straight to the central node (pin map above).

The wing box to hub box cable (its full spec: Electronics and Wiring Plan A17; Wire and Cable Buy List C8): Mike's shielded Cat6 on hand (nothing to buy), one run of about 5 ft (the wing box and the hub box both sit mid-boat), one gland at each end.

10.3 Release node channel steps

One solenoid channel, repeated per channel on both release nodes: all screw-terminal modules, all landings on DIN rail screw terminals (the Erayco UK2.5B and MELIFE kits on hand). The power path:

  1. The feed: 12/2 from the main bus board's backup-fed bar, on its own 30 A auto-reset breaker (line 4 for release bus A, line 2 for Release Node B; sec 5.2; Electronics and Wiring Plan sec 7.6), so the backup converter can trigger either horn and run the cord pullers with the main side dead. No fuse in the feed. A fuse there would have to pass the burn current (12.5 A per horn, 25 A with both), so it would be about the size of the breaker and protect nothing more, while adding one more part that can blow or corrode open and stop a release.
  2. The enable relay: on both nodes, its own HiLetgo 24 V 30 A single-channel relay module (central node: its coil on Nucleo pin D3). Not on the 8-channel board: that board's changeover contacts are rated about 7 A at 30 V DC (Songle's datasheet; the board's relays are taken to be Songle SRD-24VDC-SL-C, inferred), and a burn wire draws 12.5 A for up to 60 s.
  3. The release bus terminal strip, dead until enabled.
  4. Release bus to solenoid positive.
  5. Solenoid negative to a MOSFET switch module load terminal. Low-side switching, 3.3 V logic input driven straight by the STM32 pin, signal ground alongside. Each module's DC+ is fed from the release bus (the board carries a regulator and an opto). The modules: the GODIYMODULES XY-GMOS-002 "600W MOS" boards (Amazon B0DWRW4YHZ, bought 2026-08-24), the four that switch the drogue lid horns being central node release channels 1 and 2 and Release Node B's two: two MOSFETs in parallel, 10 A continuous at room temperature, 15 A with added heat sinking, triggered by 3.0 to 24 V high (just under the Nucleo's 3.3 V high). A horn draws 12.5 A. The boards stay as bought and the burn keeps its full enable window (Mike, 2026-11-02: a wire that burns in 1 s does no harm, but a wet wire may take 15 s, so a 10 s stop could cause a failure; the boards are one-time use, so a board that burns out after the strap is cut costs the mission nothing).
  6. A 1N5408 flyback diode across the solenoid terminals under the screws, striped end to positive. On the four cord puller channels (3 to 6) the diode sits instead on the reversing relay's input side, from the MOSFET drain to the release bus, so it works in both directions.

Cord puller reverse, for shore tests (channels 3 to 6).

Cord puller run time and fire guard. Each pull runs a set time, then stops, with no stall sensing (System Settings Sheet sec 5). A slow-blow fuse per puller, on the plus side, between the release bus and its reversing relay's input, is the fire guard (Electronics and Wiring Plan sec 4.1). On the plus side it also catches a chafed puller + core shorted onto its cable's shield, whose drain sits at 0 V. Not fitted on either node (do not re-propose): normally closed short relays across the burn wires and their daily continuity check (the release bus is dead until the enable relay closes, and each channel also needs its MOSFET on; nothing checks the burn wires between launch and use); confirmation microswitches and relay-state readback (the node knows what it commanded, and the speed drop and the aft camera confirm that the drogue is out). Release sequence (the command words are ENABLE and RELEASE):

  1. A signed ground command arrives.
  2. The Pi in command sends ENABLE.
  3. Node closes the enable relay and reports.
  4. Pi sends RELEASE, channel n.
  5. Node raises the gate and reports (no short to open, no confirmation input).
  6. The enable timer runs out and kills the bus.

One release bus at a time: the central node's channel first, then Release Node B's only if the first does not confirm, never both at once (what the small-branch fuse sees: Electronics and Wiring Plan sec 7.6). With the main side dead both horns are triggered from the backup converter, one at a time, steering paused for the burn (sec 5.2). Channels across the two release nodes (Electronics and Wiring Plan sec 4.3 owns the full map):

NodeChannels
Release Node B (stern)The drogue horn-B channels only (sec 12)
Central nodeThe drogue horn-A channels, and the four release actuators for the Jordan series drogue (JSD, the long line of small cloth cones streamed from the stern in a storm). Channels 7-9 are reserved for Boat 2's aux rudder, unwired on Boat 1; the pull-pin channels 10-15 and the trim-decouple channel 16 are retired

Open: the burn wire gauge, 28 or 30 AWG nichrome; the wet bake-off at 24 V settles it (Transom Drogue Box Guide sec 9). Open, BOAT 2 ONLY: the pull-pin solenoid's stroke and force; the pin geometry at fit-out sets them.

11. Distribution switching

This section owns the switched-load channel map. The Electronics and Wiring Plan, the Box Wiring Sheets, Node Boxes Explained, the lid labels and the firmware follow this table. Print the map on the lid. The central node has two 24 V 8-channel relay modules.

Timers and times for these channels: System Settings Sheet secs 1 and 5.

#ChannelNote
1Starlink powerNormally open. Its own 16/2 runs straight from the node to the Starlink Mini's DC input
2Science payload groupNormally open. Switches the wet lab's own 15 A line from the bus bar (Electronics and Wiring Plan sec 7.6), not the node's feed. On only around each wet lab burst, so the wet lab draws nothing between bursts (timing: System Settings Sheet sec 5); the wet lab box (Electronics and Wiring Plan A18) switches each part inside that window. Its own 16/2 runs straight from the node to the wet lab box. Open: confirm podlink does not already own that switching; settle it before the channel is wired
3Side and stern nav lightsNormally closed contact, so it fails ON (below). Right after the contact, at the node, each light has its own 1 A slow-blow fuse, so nothing leaves the node on channel 3 unfused: F2 for the stern light, whose 24 V goes up the post on three cores of the post lights cable; F4 for the bow lantern, through its own 24 to 12 V converter at the node, then a 12/2 straight forward to the bow. On from the computed sunset to sunrise, and by day too while fog mode is on (below)
4em-trak AIS transponderOn demand, through its normally closed contact, so it fails ON. Its own 16/2 runs straight from the node to the em-trak. The dAISy receiver is always on, unswitched
5SpareNo load. The release enable relay, which powers the release bus, is on its own 30 A single-channel module, coil on a native Nucleo pin, never the expander; normally open, so dead, the release bus is dead (sec 10.3)
6Bilge pump 1 manual-onNormally open. Rides the red core of the bilge 18/4, which runs straight from the node to both pumps; the cable's white and fourth cores go unused at the node (pump 2's signals are on Pi B's side, sec 4.2). Joins pump 1's + terminal after its Water Witch, no diode
7The two all-round motoring whitesNormally open contact, its fuse, then straight to the whites' 24 to 12 V converter at the node, with no relay between; the whites' 12 V goes up the post on the post lights cable. On only when it is dark (channel 3's sunset-to-sunrise rule) AND the motor is running; in fog mode, whenever the motor runs (below)
8SpareNo load. There is no charge stop (below)
9Camera port UV-CSecond module. Normally closed contact, so it fails ON (below)
10Orion-Tr float charger (emergency bank)Second module. Normally open contact, so it fails OFF (below)
11Cord puller reverse (test only)Second module. Normally open contact: the coils of the four DPDT reversing relays (sec 10.3). On only under a shore test command; forward is the release direction
12SpareSecond module, no driver (its expander pin now drives channel 13). No load: bilge pump 2 runs from the backup battery, so its manual-on and its monthly 5-second exercise are on Pi B's side (sec 4.2)
13HornSecond module, driven from the expander (PB3). Normally open: a dead node leaves the horn silent. The contact feeds the horn's 24 V through a 5 A inline fuse. Sounded by signed shore command, and by fog mode: one long blast of 4 to 6 seconds every 2 minutes (below)
14 to 16No driverSecond module. Expander pins PB4 to PB7 read Water Witch 1's state, opto input 2 (spare), the release bus readback and the steering drive's fault line (sec 10.2)

Output fuses. Five 5 x 20 mm slow-blow fuses in DIN rail holders on the node's rail, each right after its relay contact, plus channel 3's two:

ChannelFuseNote
1 Starlink5 A
3 nav lightsF2 (stern light) 1 A and F4 (bow lantern) 1 ARight after its normally closed contact
4 em-trak2 AThe B921 averages 135 mA and peaks at 2 A at 12 V (published); about half that at 24 V (inferred)
6 bilge pump 1's manual-on5 AThe same as the pump's own breaker
7 the whites' converter0.5 ARaised to 1 A only if the converter's switch-on trips 0.5 A
9 UV-C0.5 AThe smallest in the kit; the LEDs draw about 20 mA
13 horn5 A inlineIn its row above

Why: a short on an unfused output trips the node's own 15 A breaker, and channels 3, 4 and 9 fail ON, so a short there would come back at every reset and lock the node out. No fuse on channel 2 (its own 15 A breaker upstream), on channels 10 and 11 (inside the cabin, a few milliamps) or on the spare channels 5, 8 and 12. Fuses from the QBGTFAK kit on hand (Amazon B09685NBKH); holders from the MECCANIXITY DIN rail pack (bought 2026-10-10, $15.87). Every DIN fuse holder at the node: twelve. The four cord puller fuses (sec 10.3), the five switched-output fuses above, F1 (the post wind meter, 1 A, ahead of its 5 V regulator), F2 (the stern light, 1 A) and F4 (the bow lantern, 1 A). With the wet lab box's five, that is seventeen boat wide. The TSW202 network switch is on no channel. It is always on from line 6, its own 20 A breaker on the branch bar (Electronics and Wiring Plan sec 7.6): dropping it would blind Starlink and cut the Pi-to-Pi Ethernet. Not fitted: a white strobe. Do not re-propose: it is not a legal navigation light, and a flashing white light is a distress signal under US inland rules. Channel 3 fails ON.

A dead Pi never leaves the boat dark. If the node hears nothing from either Pi for the set time (the Pi-silence timer, System Settings Sheet sec 1), it turns the nav lights on by itself and keeps them on until a Pi is back. On the backup battery alone the node runs from the converter only for rudder moves, readings, the hourly wing check, and while the lights or the em-trak are wanted. Each time it powers up that way it keeps its fail-ON channels (3, 4 and 9) off unless wanted (sec 5.2; System Settings Sheet sec 4). Channel 7 does NOT fail on: an all-round white shown while not motoring is the wrong picture. The whites come on only when it is dark and the motor runs, not whenever the motor runs (Mike, 2026-10-08): the rules ask for lights only from sunset to sunrise and in poor visibility; daytime whites cost only about 1.5 W. Fog mode, from parts already aboard. It turns on by itself when fog is likely: the air close to its dew point at very high humidity, worked out from the HygroVUE 10's temperature and humidity, or the air's dew point above the sea temperature from the wet lab (sea fog). The thresholds: System Settings Sheet sec 5.

Channel 8 is spare: there is no charge stop (Mike, 2026-11-01; do not re-propose).

Camera port UV-C is on channel 9, switched in software on a timer (System Settings Sheet sec 5), not by a hardware timer, through the normally closed contact, so a dead node leaves the UV on nonstop and the window stays clear. Orion-Tr is on channel 10, normally open, so it fails OFF.

No current telemetry on these channels. No branch carries a current meter, the Pi A box feed included. Both Iridium modem feeds are hard wired always on, never switched, so no distribution failure can cost the voice. Pi rail switching belongs to the watchdogs, never this board. The switched-load runs each leave by their own gland, every one straight to its load: three 16/2 to Starlink, the wet lab box and the em-trak, the bow lantern's 12/2 and the bilge 18/4 (Electronics and Wiring Plan A3 entries 5 to 9); the post lights cable (channels 3 and 7) leaves by the split gland at entry 17. When the node fails. Nothing that keeps the boat alive runs through the relay boards except the nav lights, which fail ON. Propulsion, steering, the battery watchman, bilge pump 1 (on its own Water Witch; only its manual-on is on this board), bilge pump 2 (on the backup battery, sec 5.2), the network switch and Iridium never run through this board.

What failsWhat happensKeeps sailing?
Node dead (the Nucleo or the expander dies) with its feed liveThe relays drop out. Loads on normally open contacts go OFF, the Orion-Tr and the puller reverse among them; the nav lights, the em-trak and the camera port UV-C stay ON (normally closed); the release bus stays dead. The node's hardware watchdog restarts a hung node (sec 10.2)Yes once the restart works; a node that stays dead ends steering and drogue release for both computers
The node's feed lostEvery switched load goes OFF, the nav lights, the em-trak and the UV-C too, since their contacts are fed from that feed, and the post wind meter with them (its 5 V comes from the node's 24 V); the release bus stays deadYes when the whole main side is dead, since Pi B then feeds the node from the backup battery through the converter (sec 5.2). With the main side alive and the node's feed or the backup-fed bar lost, Pi A hands command to Pi B (sec 4.3)

Open: whether Pi B then turns the converter on to feed a dead backup-fed bar while the rest of the main side is alive; settled in the single-point review.

12. Who may release what

Every release path is three things in series: the command source, a separate enable relay powered only during a valid enabled window that times out by itself, and the release driver. Two independent faults are required to release. Release circuits are dead when idle: enable relay open, every MOSFET off (sec 10.3). Two nodes carry the release channels.

ChannelWho may release itWhy
JSD deploy (the nichrome coils part the lid strap)Signed ground command only. No path the boat can take by itselfDeployment is forecast driven with hours to days of lead, and the two always-on Iridium chains, and Starlink when it is on, keep the link. Deploy drogue is on the shore command list (Build Guide sec 8.3)
JSD release (the cord puller pulls the T8 trigger line)Signed ground command only. Never by the boat alone, even with no shore link: the drogue stays on until shore sends the release, however long that takes (Mike, 2026-11-01: slower is safer; do not re-propose)It cannot be undone, and there is no time pressure. It fails toward held: the puller's self-locking worm motor cannot be back-driven, so power loss leaves the drogue attached
BOAT 2 ONLY: the primary actuator's one pull-pin, and the aux rudder release (neither on Boat 1)Same enable-then-release two-step lockAux rudder deployment is never automatic (Routing Guide 11.4)

13. Lightning watch (no shutdown)

The boat does not shut down for lightning (Mike, 2026-10-02). Nothing is turned off; the boat keeps sailing, steering and logging through a storm. Not fitted: a go-dark mode. Do not re-propose it. Why:

Feathering stays with wind speed: the wing's program and the give-way spring at the tail flap handle it. What protects the boat from lightning is the copper path, the two isolated compute islands and the surge parts (Lightning Ground System Guide). The research: Reference/reports/USV lightning risk and protection.md.

13.1 Detector

The sensor: an AS3935 Franklin sensor on a Playing With Fusion SEN-39003 board (bought).

The lead: Belden 6504FE (22 AWG, six cores, foil shield and drain wire), under 3 ft, a PG7 gland at each box. The board's own wiring (the screw block on its pin row, the two jumpers that pick I2C, the nylon mounting): Electronics and Wiring Plan A12; plan Box Plans v10.5/Detector Mini Box v10.5.pdf.

  1. Five cores used: red 5 V, black ground, blue IRQ to WD-B pin D2 (Claude's pick; no WD-B pin map exists yet), green SCL to A5, white SDA to A4.
  2. Cut the brown core back flush inside the jacket at both ends.
  3. Land the drain wire at the WD-B end only, on the island's floating negative; at the detector cut it back and tape it.

What it is for: logging storms, setting the satellite check to every 15 minutes while strikes are heard (sec 13.4), and starting the post-strike audit after a very close strike (sec 13.2). Strike strength is not used: the detector's energy number has no physical meaning by its maker's datasheet, and a strong far strike reads like a weak near one. Keep it as far from the VESC as the lead allows: motor controllers are the classic source of false triggers. Bench-check the false-trigger rate with VESC A running before fixing the spot; if it is bad, move it forward on a small node with an isolated transceiver.

13.2 Post-strike audit

After a very close strike is logged, the POST_STRIKE audit walks every device, every surge protector that still reports, and the radio-link quality numbers, and reports a protection status to ground (Routing Guide sec 11.8). The meter checks at the dock: Lightning Ground System Guide sec 8.4.

13.3 Hardware and exclusions

The only new hardware is the detector mini-box.

Never touched by any mode: bilge pumps, their float switch paths (Water Witch 1, pump 2's Ultima switch) and the battery watchman. No gas sensors (do not re-propose); the cell-temperature trip on the pack probes is the battery trip.

Two weather satellites map every lightning flash and post the data free: NOAA's GOES lightning mapper (GLM; the Americas and the oceans beside them, under 20 seconds old, on AWS) and EUMETSAT's MTG Lightning Imager (Europe, Africa, most of the Atlantic and part of the Indian Ocean, from the EUMETSAT Data Store). They give real strike positions, about 5 miles accurate. Software only; no new hardware.

Size and power. A GLM file covers 20 seconds and runs about 150 to 210 KB, so 2 minutes is about 1.2 MB and 10 minutes about 6 MB; under 1 GB a month. A Starlink window is about 3.3 Wh; the 15-minute checks run only while strikes are heard, mostly in the tropics, where the panels make far more than the boat uses (Build Guide sec 4.6). The Starlink plan is picked at launch: check its data allowance against this. Where it does not work: no free map covers the west Pacific, Australia and the east Indian Ocean (roughly 70 E to 170 E, worked out from where the two satellites sit), or wherever Starlink is off or down. There the boat's own detector is the only lightning watch.

14. Surge protection rules (Layer 3)

The rules for every surge part on the boat, then the part on each conductor. Rule zero: no relays. Then four rules:

  1. Nothing sacrificial on a survival channel. Stubs or isolation only.
  2. Gas discharge tubes only where they age open and sit behind a backup.
  3. MOV-class clamping only as thermal disconnect modules, which cut themselves off when the clamp inside overheats. Never bare. Plain modules, no status contacts, no remote signal: nothing can be done about a burnt clamp at sea. Every clamp is checked with a meter at each refit and at the post-strike check (Lightning Ground System Guide sec 7.6).
  4. Convenience channels may be called sacrificial.
TermPlain meaning
TVSA fast clamp diode that catches a small spike and holds the voltage down
MOVA ceramic block that dumps a large surge, and wears out doing it
SPDAny surge protection device, used as the general word
Quarter-wave stubA shaped piece of coax that shorts lightning frequencies to ground while passing the radio signal. Nothing in it can wear out

The boat does not shut down for lightning (sec 13). These rules, the wiring rules and the copper path are what protect it. Per-conductor detail and the on-hand parts: Lightning Ground System Guide sec 7.

14.1 By conductor

Iridium A and B coax: quarter-wave stub arrestors, Fairview FMSP1066 or PolyPhaser TSX class; nothing in them can fail. What is on hand: Lightning Guide sec 7.1. AIS: no arrestor and no changeover relay: nothing AIS is above deck. The em-trak transmit whip stands under the panel-free deck patch, the receive antenna is short and below deck, and the receivers are cheap. GPS coax, both chains: no arrestor and no bias tee. A plain stub is impossible, because the receivers feed DC up the coax to their active antennas. Not fitted: DC-pass gas tubes. Do not re-propose: one that fails shorted silently kills its antenna while still looking healthy. The protection instead: two independent chains (different receivers, antennas and boxes), the ferrite at the wall, and a cheap receiver cross-checked against Starlink's own position fix (Lightning Guide sec 7.3). Starlink and cameras: an Ethernet surge protector on each of the five cables that run on deck or near it, on a small board on a bulkhead near the deck where those cables first come inside (Electronics and Wiring Plan A6a), so a surge on one cable does not take the switch (Lightning Ground System Guide sec 7.4). Starlink and the cameras themselves stay expendable. CAN, both buses: TVS on the HATs. At the central node, Release Node B and wet lab box drops, a Taidacent RS-12V/2S DIN-rail surge module (all three on hand; the wet lab box's is one of the two bought 2026-10-07), not SM712 chips. Iridium USB links: a DSD TECH SH-G01A USB isolator at the Pi end of each modem's USB cable (secs 4.1 and 4.2). On data lines isolation beats clamping, and it keeps the islands apart. VESC UART and kill pair: unprotected, by choice (Mike, 2026-09-07). Battery bus surge modules: two Boartechs 2-pole DC modules, 48-70 V class (Amazon B0DFBPBW1R, $16.17 each, bought 2026-09-27). Not fitted: the graded MOV ladder of four modules stepped at about 35, 40, 45 and 56 V DC, all above the 29 V charge ceiling, which no US seller offers.

Solar strings: PV-type surge modules, Type 2, with a heat cutoff (the Phoenix Contact or Citel class), plain, no remote signal, one per charge controller, on a short DIN rail just below it on the main bus board, across its PV + and PV - (Reference/Solar Surge Wiring 2026-10-12).

Backup island: its own TVS at the Pi B DC-DC, at WD-B's D36V6F5, and on the detector lead, all referenced to the island's floating negative, never to the ground network. The detector lead is a 5 V line, so its TVS is a 5 V part, across red and black inside the Pi B box. Open: which 5 V TVS part; picking one settles it. A 1.5KE33CA sits across bilge pump 2's feed at the backup battery board, since its cable runs to the bilge (sec 5.2). Remote driver boxes: TVS on each power input. Release lines need nothing extra: they are dead until their node's enable relay closes (sec 10.3). The wing box: every wire from the slip ring gets a fuse or a surge part at the wing box's entries, so a strike on the mast stops there and does not reach the other boxes. The CAN pair to the trim actuator and the two RS-485 pairs, to the tip wind meter and the wing compass, get a Taidacent RS-12V/2S surge module each where they enter the hull, and the 24 V pair its 5 A fuse and a 1.5KE33CA (Wing Power System sec 8.7). The 1.5KE33CA conducts from 31.4 V. The three data pairs then end at isolated readers in the USB hub box (sec 10.2).

14.2 Beyond components

Ranked levers that add no parts that can fail:

  1. Routing (the loop area rules, Electronics and Wiring Plan sec 7.7) attacks induced energy before any clamp has to act.
  2. The lightning map in the ERA5 routing pipeline picks where to cross the ITCZ by satellite flash counts: the largest single lever on exposure.
  3. Radio link health (Iridium signal quality, GPS carrier-to-noise, Starlink SNR) is trended in the readings sent home, so unseen coax decay becomes a watched number.
  4. Clamp ratings are bought one energy class above requirement.
  5. A POST_STRIKE state (sec 13.2): after logged very close activity it checks every device and the radio health and reports a protection status to shore, which can steer away from more lightning for the rest of the leg.

15. Connector and materials standards

Glands, connectors, cable rules and greases are wiring; their home is the Electronics and Wiring Plan sec 7 (gland sizes and drills 7.1, grouped entries 7.2, the disconnect rule 7.3, everything else and the greases 7.4). The two rules this plan leans on: every box entry is a nylon IP68 gland, and no M12 receptacle sits on any box.

16. Open items

Open questions for this guide are in Pending Amendments v10.6.