P030 / Storage / Connector reference
M.2 physical fit and keying do not establish whether a host supports a particular SATA, PCIe or NVMe device. [C030A]
M.2 is a form-factor family; NVMe describes a different layer.
Claim inspection dates: 2026-10-01, 2026-10-08, 2026-10-11, 2026-10-13, 2026-10-15 · Independent review pending
Record the module length, key arrangement and exact host-slot specification. The schematic is illustrative: neither its length nor contact spacing is an engineering measurement.
Identify the module and socket separately, then check the host’s wired interface.
| Nominal contacts | Not recordedNot recorded in a normalized source-scoped field. Consult the exact part/revision; no value inferred from illustrations. |
|---|---|
| Positions / cavity span | 67 (TE C-2199230 representative M-key socket)S594Recorded source-scoped values; named examples do not describe every family variant or establish compatibility. V143: the named drawing/revision or exact product page only. Recognition and document-role evidence; not a pinout, adapter verdict, dimensioned mating gauge, electrical approval or current installed-device claim. |
| Populated contacts | Not recordedNot recorded in a normalized source-scoped field. Consult the exact part/revision; no value inferred from illustrations. |
| Connector role | card-edgeS033 · S426 · S427 · S427 · S427 · S429 · S429Recorded source-scoped values; named examples do not describe every family variant or establish compatibility. Keyed module card-edge interface family |
| Contact rows | 2 (1-2199230-5)S872Separate exact examples; retain each value’s source, role, axis and part scope. Exact named example 1-2199230-5: M-key M.2 board connector. Exact example only; no universal geometry, electrical compatibility, fabrication approval or wiring instruction. Connector envelope is distinct from existing22x42/80mm card dimensions; no NVMe/SATA capability guarantee. |
|---|---|
| Contact pitch | 0.5 mm manufacturer-reported centerline or mating-interface pitch (1-2199230-5)S872Separate exact examples; retain each value’s source, role, axis and part scope. Exact named example 1-2199230-5: M-key M.2 board connector. Exact example only; no universal geometry, electrical compatibility, fabrication approval or wiring instruction. Connector envelope is distinct from existing22x42/80mm card dimensions; no NVMe/SATA capability guarantee. |
| Dimensions / axis | 22 mm Module format width (2242 module format); 42 mm Module format length (2242 module format); 22 mm Module format width (2280 module format); 80 mm Module format length (2280 module format); 21.9 mm connector length (1-2199230-5); 8.7 mm connector width (1-2199230-5); 4.2 mm connector height (1-2199230-5)S426 · S872Separate exact examples; retain each value’s source, role, axis and part scope. Article 000144170 version 12, Figure 1 examples (b)–(d); no tolerance, connector geometry or clearance inferred. Exact named example 1-2199230-5: M-key M.2 board connector. Exact example only; no universal geometry, electrical compatibility, fabrication approval or wiring instruction. Connector envelope is distinct from existing22x42/80mm card dimensions; no NVMe/SATA capability guarantee. |
| Coupling / latch | Not recordedNot recorded in a normalized source-scoped field. Consult the exact part/revision; no value inferred from illustrations. |
| Keying / polarization | A-key (TE C-2199230 B4 part table); B-key (TE C-2199230 B4 part table); E-key (TE C-2199230 B4 part table); M-key (TE C-2199230 B4 part table)S594Recorded source-scoped values; named examples do not describe every family variant or establish compatibility. V143: the named drawing/revision or exact product page only. Recognition and document-role evidence; not a pinout, adapter verdict, dimensioned mating gauge, electrical approval or current installed-device claim. |
| View convention | Not recordedNot recorded in a normalized source-scoped field. Consult the exact part/revision; no value inferred from illustrations. |
| Contact gender / arrangement | Not recordedNot recorded in a normalized source-scoped field. Consult the exact part/revision; no value inferred from illustrations. |
| Mounting | right-angle surface-mount board connector (1-2199230-5)S872Separate exact examples; retain each value’s source, role, axis and part scope. Exact named example 1-2199230-5: M-key M.2 board connector. Exact example only; no universal geometry, electrical compatibility, fabrication approval or wiring instruction. Connector envelope is distinct from existing22x42/80mm card dimensions; no NVMe/SATA capability guarantee. |
| Shell / form | Not recordedNot recorded in a normalized source-scoped field. Consult the exact part/revision; no value inferred from illustrations. |
| Manufacturer | TE Connectivity (1-2199230-5)S594Recorded source-scoped values; named examples do not describe every family variant or establish compatibility. V143: the named drawing/revision or exact product page only. Recognition and document-role evidence; not a pinout, adapter verdict, dimensioned mating gauge, electrical approval or current installed-device claim. |
| Series | M.2 (1-2199230-5)S594Recorded source-scoped values; named examples do not describe every family variant or establish compatibility. V143: the named drawing/revision or exact product page only. Recognition and document-role evidence; not a pinout, adapter verdict, dimensioned mating gauge, electrical approval or current installed-device claim. |
| Exact part / implementation | 1-2199230-5 (1-2199230-5)S594Recorded source-scoped values; named examples do not describe every family variant or establish compatibility. V143: the named drawing/revision or exact product page only. Recognition and document-role evidence; not a pinout, adapter verdict, dimensioned mating gauge, electrical approval or current installed-device claim. |
| Recorded markings | Not recordedNot recorded in a normalized source-scoped field. Consult the exact part/revision; no value inferred from illustrations. |
Keep this limit: The named multi-key TE drawing is not one universal socket or universal contact count for the whole family. S594 · S594
Read the exact system/board manual for the slot interface, module length, clearance, CPU/firmware and shared resources.
Existing source inspection and AI review remain distinct from independent technical review. A matching form does not establish a safe connection.
Read the view
The mounting hole and contact edge orient this illustration only; no underside, socket opening or approved installation direction is shown.
About the marks: The simplified edge fingers and gap are not a verified key pattern.
What it cannot establish: Do not assign B, M or B+M keying, a module size or NVMe support from this generic board.
Enlargement changes display size only. It does not reveal measured geometry, a pin assignment or an approved mating combination.
Read the underlying references: S033 · S426 · S427. Artwork interpretation remains review-pending.
How to read connector illustrations →Image inspection / P030
1 registered view for this reference. Different part examples are not automatically mates; all remain not to scale and independently unapproved.
(private workspace)P030 / Source-observed physical study
TE C-2199230 B4; M-key representative 1-2199230-5
Socket-side source drawing orientation · Device receptacle
Not to scale. Technical and rights review pending.
Inspect view & provenance (private workspace)Bounded facts, visible unknowns
| Physical checks | Keying, length, mounting and clearance [C030A] |
|---|---|
| Protocol support | Requires host and module evidence [C030A] |
| Nominal format, not mating dimensions | 2242 and 2280 examples label nominal module width and length; check the exact slot and standoff. [C030B] [C030D] |
| Key, interface and firmware | A matching B/M/B+M key is not a SATA, PCIe, NVMe, lane-count or boot guarantee. [C030C] [C030E] |
| Exact-host example | PRIME B550-PLUS AC-HES M.2_1 and M.2_2 have documented CPU/slot-dependent modes. [C030F] [C030G] |
| Source-scoped role and recognition | Read the component role before the key name. An offset key interrupts the socket opening. [C030J] [C030K] [C030L] |
| M.2 protocol mismatch | Host socket and SSD must support the same SATA or PCIe storage transport, beyond physical fit. [C030M] |
| Mechanical dimensions | No independently reviewed mechanical drawing in this release; do not use this page for fabrication. |
| Engineering pinout | Source-checked engineering profile available; independent review pending. Open engineering profile → |
| Verified device list | Not included. Check exact device and accessory documentation. |
This record is an identification starting point. It does not provide measured mating tolerances, electrical approval, or a list of verified device models. Use the original device and accessory documentation to resolve the remaining requirements.
No. M.2 keys and module dimensions address physical fit; host wiring determines SATA versus PCIe availability, and NVMe is the storage command/transport stack. Kingston and the preserved Dell and ASUS references explicitly warn that M.2 key or shape alone cannot prove a shared protocol or host support.
Assuming all M.2 slots accept any NVMe or SATA SSD just because the edge notch lines up.
Full technical reading, sources and related identities →Claim-specific evidence remains in the canonical record. Concept diagrams do not show any safe wiring or mechanical mating geometry.
Pins & wiring
Choose the exact wiring. Pin numbers follow its stated view; a schematic does not establish physical positions. Check your exact device before wiring.
Identify the physical format, keying and mounting; then verify the wired electrical interface, the storage protocol and the exact host’s CPU/firmware/resource conditions. The linked M.2 engineering reference and question guides keep these layers separate. No M.2 contact assignments or measured mating drawing are published.
Read the exact host slot specification and module label; confirm interface, key, length, thickness and retention independently. No universal M.2 speed, SATA/NVMe verdict, card-side mirror view or exact part equivalence is established. Sources: C030J, C030K, C030L. Original qualitative study; independent technical and rights review pending.
The useful distinction
Dell’s version-12 article illustrates 2242 as a nominal 22 × 42 mm module and 2280 as a nominal 22 × 80 mm module. These are module-format examples, not socket mating dimensions. [C030B]
ATP distinguishes M.2 keying from the interface actually wired to a socket: a mechanically matching key alone does not establish SATA or PCIe support. [C030C]
ATP calls for checking module length, mounting position and vertical/component clearance, including single- versus double-sided construction, separately from keying. [C030D]
ATP separates firmware support for NVMe boot from mechanical fit and advises against treating ordinary M.2 installation as hot-plugging. Follow the exact equipment’s power-off and service instructions. [C030E]
The ASUS PRIME B550-PLUS AC-HES manual lists M.2_1 with SATA and PCIe x4 modes: PCIe 4.0 for the named Ryzen 5000/3000 desktop families, and PCIe 3.0 for the named 5000 G-Series/4000 G-Series families. [C030F]
On the same AC-HES board, the chipset-connected M.2_2 is specified for PCIe 3.0 x4 and SATA; both M.2 slot entries list 2242, 2260, 2280 and 22110 modules. [C030G]
StarTech SM2NGFFMBU33 explicitly excludes M.2 NVMe and AHCI PCI-Express SSDs. [C030H]
The SM2NGFFMBU33 sheet lists SATA B-key and SATA B+M-key M.2 drive types. [C030I]
In TE drawing C-2199230 revision B4, the representative shown as 1-2199230-5 is an M-key board socket; the card edge is its counterpart, not the illustrated component. [C030J]
The C-2199230 part table separates A, B, E and M key variants, and the M-key block includes several part suffixes rather than one universal socket. [C030K]
The C-2199230 drawing specifies 67 contact positions with a key interruption; its two solder-tail rows have different counts, so a single visible row is not the total contact inventory. [C030L]
Kingston states that a PCIe M.2 SSD in a SATA-only host socket—or a SATA M.2 SSD in a PCIe-only socket—does not gain the missing protocol merely from physical fit. Consult the system manual for the exact slot interface and any shared-lane restrictions. [C030M]
Flagship atlas STORAGE / HOST SUPPORT
An M.2 module can match the socket key and length yet be unsupported. The host decides whether SATA or PCIe is wired, whether NVMe boots, and what module height and mounting positions fit.
2242 and 2280 are documented nominal module-size classes, not universal board clearances. Evidence: C030B
Matching key shape alone does not establish whether the socket supports SATA or PCIe. Evidence: C030C
Check the installed standoff, component-side clearance and single/double-sided construction. Evidence: C030D
The cited ASUS motherboard gives different PCIe mode descriptions for M.2_1 by CPU family. Evidence: C030F
“M-key NVMe 2280” on a product listing is not sufficient to guarantee the host slot, controller or firmware accepts it.
This is an original editorial decision study tied to existing source-checked claims. The following source inspections have not been renewed by this new page presentation, and none is independent engineering or model-by-model qualification.
Unresolved: Actual device fit, required physical tolerances, pinouts, negotiations, electrical safety and hardware interoperability still require the identified manufacturer's documentation and any necessary independent review.
Decision field guide 07 Key / interface / protocol
A mechanically fitting M.2 module may still be unusable. Slot wiring and storage protocol must be confirmed separately.
Still unknown: The chart does not turn a key shape, “M.2” label or expansion adapter into an approved SSD combination.
Read M.2 versus NVMeExisting evidence: C030A · C030C · C057B source records S033 · S427 · S428. See each source record for its inspection date and scope; graphic interpretation remains pending independent technical and publication review.
Practical reference
Start with the answer. Follow the real distinction, then the source-scoped next check. All evidence dates and publication blockers remain unchanged.
V102Q07 Practical reference
Short answer Mechanical key and module size are only the first gates. The slot’s SATA or PCIe wiring, supported controller/protocol, firmware boot support and mounting clearance must all be checked for the actual host.
| What you are checking | What the cited evidence establishes |
|---|---|
| Module format, for example 2280 | Nominal outline/length designation, not proof of host support |
| Key shape | Physical mating cue, not a promise of SATA or PCIe wiring |
| Host / firmware | Must document supported storage interface and any boot restrictions |
Still unresolved: No universal B-key or M-key compatibility, mechanical tolerance, thermal clearance or NVMe boot guarantee is established.
Existing evidence claims: C030A · C030B · C030C · C030D · C030E. These are editorial field answers over inherited source records, not newly approved specifications.
Neither the source inspection dates nor the evidence dataset has been refreshed. No physical tests, exact-device compatibility approval, pinout or fabrication geometry is implied.
Application notes / Storage / P030
The card format and the supported storage interface are separate checks. SM2NGFFMBU33 is a concrete SATA-only enclosure that excludes NVMe and AHCI PCIe drives.
Identify first
Read the drive model, key and length, then the enclosure’s protocol list.
Still unresolved
Mounting clearance, firmware support and any model-specific length restriction still need confirmation.
Explicit source exclusion · named example only
No: the manufacturer explicitly excludes NVMe and AHCI PCIe SSDs.
Boundary. This is the named enclosure’s interface limit, not a universal M.2 limit.
Next check. Choose an enclosure whose documented interface matches the drive.
S491 · C030H (private workspace)
Not established · named example only
Unknown: a component outline does not identify the interface wired by the host.
Boundary. No unverified laptop model has been assigned an SSD capability.
Next check. Read the laptop’s exact socket specification.
S339 · S033 · C298A (private workspace) · C298C (private workspace)
C030A (private workspace) — M.2 physical fit and keying do not establish whether a host supports a particular SATA, PCIe or NVMe device.
Consumer identification / documented standard or product class only
C030D (private workspace) — ATP calls for checking module length, mounting position and vertical/component clearance, including single- versus double-sided construction, separately from keying.
Physical fit checklist only; no invented height, tolerance, heat-spreader or fabrication dimensions.
C030H (private workspace) — StarTech SM2NGFFMBU33 explicitly excludes M.2 NVMe and AHCI PCI-Express SSDs.
Named SATA-only USB enclosure; the M.2 label or an apparently matching key cannot override this exclusion.
C030I (private workspace) — The SM2NGFFMBU33 sheet lists SATA B-key and SATA B+M-key M.2 drive types.
Named enclosure drive-type list only. Its inconsistent module-length lists are held open, not treated as confirmed 2230 support.
Source interpretation is not independent engineering review, hardware testing, wiring advice or a public-release approval.
PC internals · a documented check
Fit is only one check. Keying, the interface wired to the host slot and firmware support for boot are separate. A B+M notch is not proof of SATA or PCIe support, and an mSATA module is not an M.2 module. C030A · C030C · C030E · C298C
| Check | Documented distinction | Boundary |
|---|---|---|
| Module and socket | Check key, length, mounting and component clearance separately. C030D · C030J | A drawing of a board socket is not a measurement of the card edge. |
| Interface | The module and the particular host slot must support the same interface. C030C | Do not decide SATA versus PCIe from the notch alone. |
| Boot | Firmware support for NVMe boot is a separate requirement. C030E | A physically installed module is not a boot-support verdict. |
| mSATA look-alike | mSATA uses SATA; M.2 includes SATA and PCIe options and uses a different connector. C298C · C298D | A Mini PCIe/mSATA socket outline does not establish its host wiring. |
Keep this limit: Use the equipment maker’s power-off and handling instructions. This is not a hot-plug procedure. C030E
Before you connect
Your next step
Use this reference
Storage & media / Several identities remain possible
Check the exact slot, keying, card and documented storage interface in the existing references.
P030 reference · P298 reference
No registered close-up was selected; an unrelated connector image is not substituted.
Compare look-alikes: Mini PCI Express/mSATA versus M.2
Candidate selection does not confirm the identity or capabilities of your physical item.
Follow the connection
Computer-generated illustration with prior AI visual review. Not a photograph, measurement or compatibility check. Independent technical and rights review pending.
A data connector is not a power connector.
Open field noteCheck the slot specification, not just the notch.
Open field noteUse shape to narrow the candidates, then use documentation to establish function.
Open field note
The shared 52-position socket family does not make Mini PCIe and mSATA electrically interchangeable; host implementation still controls supported signals.
Open field noteCommon questions
Focused explainers
The source trail
AI-assisted inspection is not independent engineering review. Source scope and access limitations are disclosed below. Procedural checklists are editorial requirements, not hardware measurements.
M.2 physical fit and keying do not establish whether a host supports a particular SATA, PCIe or NVMe device.
Kingston · SSD FAQ ↗S033: full source recordInspect review dependencies → (private workspace)Dell’s version-12 article illustrates 2242 as a nominal 22 × 42 mm module and 2280 as a nominal 22 × 80 mm module. These are module-format examples, not socket mating dimensions.
Dell · Differences Between M.2 Cards: M.2 Slots, Keys, Sizes and Types ↗S426: full source recordInspect review dependencies → (private workspace)ATP distinguishes M.2 keying from the interface actually wired to a socket: a mechanically matching key alone does not establish SATA or PCIe support.
ATP Electronics · What is M.2? Keys and Sockets Explained ↗S427: full source recordInspect review dependencies → (private workspace)ATP calls for checking module length, mounting position and vertical/component clearance, including single- versus double-sided construction, separately from keying.
ATP Electronics · What is M.2? Keys and Sockets Explained ↗S427: full source recordInspect review dependencies → (private workspace)ATP separates firmware support for NVMe boot from mechanical fit and advises against treating ordinary M.2 installation as hot-plugging. Follow the exact equipment’s power-off and service instructions.
ATP Electronics · What is M.2? Keys and Sockets Explained ↗S427: full source recordInspect review dependencies → (private workspace)The ASUS PRIME B550-PLUS AC-HES manual lists M.2_1 with SATA and PCIe x4 modes: PCIe 4.0 for the named Ryzen 5000/3000 desktop families, and PCIe 3.0 for the named 5000 G-Series/4000 G-Series families.
ASUS · PRIME B550-PLUS AC-HES User’s Manual ↗S429: full source recordInspect review dependencies → (private workspace)On the same AC-HES board, the chipset-connected M.2_2 is specified for PCIe 3.0 x4 and SATA; both M.2 slot entries list 2242, 2260, 2280 and 22110 modules.
ASUS · PRIME B550-PLUS AC-HES User’s Manual ↗S429: full source recordInspect review dependencies → (private workspace)StarTech SM2NGFFMBU33 explicitly excludes M.2 NVMe and AHCI PCI-Express SSDs.
StarTech.com · SM2NGFFMBU33 SATA M.2 enclosure datasheet ↗S491: full source recordInspect review dependencies → (private workspace)The SM2NGFFMBU33 sheet lists SATA B-key and SATA B+M-key M.2 drive types.
StarTech.com · SM2NGFFMBU33 SATA M.2 enclosure datasheet ↗S491: full source recordInspect review dependencies → (private workspace)In TE drawing C-2199230 revision B4, the representative shown as 1-2199230-5 is an M-key board socket; the card edge is its counterpart, not the illustrated component.
TE Connectivity · TE C-2199230 M.2 socket customer drawing, revision B4 ↗S594: full source recordInspect review dependencies → (private workspace)The C-2199230 part table separates A, B, E and M key variants, and the M-key block includes several part suffixes rather than one universal socket.
TE Connectivity · TE C-2199230 M.2 socket customer drawing, revision B4 ↗S594: full source recordInspect review dependencies → (private workspace)The C-2199230 drawing specifies 67 contact positions with a key interruption; its two solder-tail rows have different counts, so a single visible row is not the total contact inventory.
TE Connectivity · TE C-2199230 M.2 socket customer drawing, revision B4 ↗S594: full source recordInspect review dependencies → (private workspace)Kingston states that a PCIe M.2 SSD in a SATA-only host socket—or a SATA M.2 SSD in a PCIe-only socket—does not gain the missing protocol merely from physical fit. Consult the system manual for the exact slot interface and any shared-lane restrictions.
Kingston · SSD FAQ ↗S033: full source recordInspect review dependencies → (private workspace)Source-qualified next step · P030
What the evidence saysM.2 physical shape does not mean the socket and drive share SATA or PCIe storage protocols.
A general Kingston FAQ does not diagnose an exact computer, BIOS setting, disabled shared lane or damaged drive.
C030M / source-linked claim: Kingston states that a PCIe M.2 SSD in a SATA-only host socket—or a SATA M.2 SSD in a PCIe-only socket—does not gain the missing protocol merely from physical fit. Consult the system manual for the exact slot interface and any shared-lane restrictions.
Storage SSD interface only; not a claim about every M.2 socket or PCIe adapter · Checked 2026-10-15 · No independent approval
Original reader guidance · Not a hardware test, certified connection, independent technical review, or publication approval.
