# Connector families

> Why Probe asks which connector a placement is, how the family vocabulary works, and how the answer unlocks pinout checks.

_Source: E-Sharp (esharp.se) · Probe guide_


A connector often carries a standardised pinout, but the netlist doesn't say which standard. So Probe asks which **connector family** a placement follows — and the answer unlocks checks that otherwise can't run.

## Why Probe asks which connector it is

The netlist knows *what* is connected, but not *which standard* the connector should follow. When you (or your assistant) state the family, Probe can compare the actual connectivity against the standard's pinout and raise deviations.

## The family vocabulary

Families come from a **closed vocabulary** — a fixed library of known connector families, not free text. That keeps answers comparable across boards. Some answers **close the question** outright (the pinout is then unambiguously determined); others need a variant or side to complete them.

## Standards with variant and side

For families that exist in several variants or orientations, you also state which — e.g. FMC, M.2, CompactPCI Serial, PXIe or VME exist in forms where **variant and position** decide the pinout. Saying "it's an M.2" isn't enough if keying and side change what the pins mean.

## Part level or placement level

You can declare the family at **part level** (this article is always this family) or at **placement level** (this specific connector on this specific board). Placement level is right when the same physical connector is used differently on different boards.

## Private families from your own specification

If you have an internal connector standard that isn't in the public vocabulary, a **private family** can be defined from your own specification, so your boards can be checked against it the same way.

## What it gives you

With the family set, Probe can run the pinout checks — it catches, for example, when a placement's connectivity deviates from the standard's pinout, or when a candidate connector hasn't been referenced against a standard at all. As always: the deviation is pinned at the connector and carries its source.

---

Related: [what Probe finds](/en/probe/what-probe-finds) and interconnect review between boards (see [Interconnect and the seam](/en/probe/support/interconnect-and-the-seam)).

*Probe is E-Sharp's design-review engine. Probe doesn't reason on its own — the AI in your own tool does the reasoning and you make the technical call.*
