← Insights

Probe Interconnect

Two boards, both correct, and five volts on a Raspberry Pi

Each board passed review on its own. Mated, the module's 5 V rail lands on a 3.3 V Raspberry Pi header — a fault that exists only in the connection between them.

2026-09-17 · 4 min · Story

An Accordion M1 carrier takes a plug-in Mini-PSU precision module. Review either board on its own and it is correct. The fault only exists once they are mated — in the connector between them.

The same contacts, two different nets

The module’s 5 V rail sits on four contacts of a 60-contact connector. On the carrier side, those four positions are not one net: one is the intended 5 V rail, and the other three are general-purpose I/O. Three of them reach a 3.3 V I/O expander and a line on a Raspberry Pi 40-pin header. A fourth contact puts the module’s 3.3 V onto another Pi line.

So the module drives 5 V into pins the carrier treats as 3.3 V logic. Each board is internally consistent — the single-board review signs both off — because neither board is wrong about itself. The disagreement is between them.

Reviewing the connection, not the boards

This is what Probe Interconnect looks at: the mapping across a connector, contact by contact, rather than either schematic alone. On this pair it reported 20 agreements, 9 contradictions, and 31 contacts it could not compare and said so, instead of guessing.

The nine contradictions are the ones that matter here — the 5 V-onto-3.3 V collisions that neither board could reveal by itself, and that a reviewer flipping between two correct schematics is unlikely to catch by eye.

A board can be correct and still be wrong about what it’s plugged into. The fault lives in the mating, so that’s where you have to look.

See how Probe reviews a board

Probe reads the netlist, the datasheets and the BOM, and reviews the design against spec — self-hosted, with every finding cited. Your design never leaves your network.

Book a demo of Probe

Show us your board — we review it and go through the findings together.

Prefer to email? info@esharp.se