The useful distinction
Recognize it. Then verify it.
A common SAS drive-side connector combines signal and power sections in a 29-circuit interface. [C196A]
Molex part 787170002 is a documented SAS/SATA receptacle example in the existing primary-source record; its connector description alone cannot establish whether a given host controller supports SAS. [C196B]
SFF-8482 revision 2.5 distinguishes the device free plug from fixed backplane and fixed cable receptacles; their roles and retention context are not interchangeable labels. [C196C]
SFF-8482 describes two seven-contact signal sets and a fifteen-contact power set; the second signal set is on the opposite side of the device plug. [C196D]
SFF-8482 revision 2.5 section 5.3 describes backplane insertion sequencing but states that cable hot plugging is not supported by that interface; a familiar plug outline is not a live-cable permission. [C196E]
Exact source example 787170002: contacts: 29 loaded:14signal plus15power. construction: Right-angle female SMT connector; PCB locator and retention. recommended pcb mm: 2.36. Molex marks part as not formally published and limited information. Both pitches are listed without per-contact axis mapping; do not assign one to signal or power without drawing. No physical compatibility, pin map or hardware validation is established. [C196F]
PC internals · a documented check
Does a SAS/SATA connector or adapter prove that my controller supports the drive?
No. A connector description establishes a physical interface, not the controller’s supported protocol. Keep the drive plug, cable receptacle and backplane receptacle distinct, then obtain the exact controller and drive documentation. C196B · C196C
What the documentation establishes—and what still needs checking| Check | Documented distinction | Boundary |
|---|
| Drive-side plug | Documented distinctionSFF-8482 describes two seven-contact signal sets and a fifteen-contact power set. C196D | BoundaryThe second signal set is on the other side of the plug; one visible face is not the whole inventory. |
|---|
| Cable or backplane | Documented distinctionThe specification distinguishes a device free plug from fixed cable and backplane receptacles. C196C | BoundaryDo not label every view as the same component or assume the same retention context. |
|---|
| Host support | Documented distinctionThe Molex 787170002 description is not controller-support evidence. C196B | BoundaryA passive change in connector shape does not supply the missing controller documentation. |
|---|
| Live connection | Documented distinctionSFF-8482 revision 2.5 separates backplane sequencing from cable hot plugging. C196E | BoundaryThat interface does not support cable hot plugging. |
|---|
Check these next
- Identify the drive model, controller/HBA model, backplane model where present and complete cable assembly.
- Find the controller’s explicit drive-interface support and the assembly’s direction and endpoint roles.
- Treat absent controller or hot-service documentation as unresolved—not as permission to connect.
Keep this limit: A backplane hot-plug description is not permission to hot-plug a cable. No SAS-to-SATA support verdict is made here. C196E
Source-scoped identification facts
Each value retains its exact example, role and measurement axis. Facts from different parts must not be combined into an invented component.
Not recorded: Populated contacts, Dimensions / axis, Contact gender / arrangement, Mounting, Coupling / latch, Shell / form, Recorded markings, View convention. Unknown fields stay unknown; illustrations supply no measurements or pin assignments.
Report a correction to these facts →Bounded facts, visible unknowns
Specifications and limits
A boundary, not an omission to guess around.Use the source-backed form or position count only for identification. Resolve ratings, protocol, direction, wiring, cable construction and exact device support from the relevant equipment and component documentation.
What is not established
This field note does not approve a connection, adapter, cable assembly, rewiring scheme or fabricated part. It intentionally omits unsupported pin assignments and mechanical tolerances.
Storage recognition: next evidence check
Identify the drive, controller and fixed connector role. Use the equipment instructions for insertion, removal and power state. No installed-system support, reciprocal SATA/SAS compatibility, current cable assembly or hot-plug permission is established. Sources: C196C, C196D, C196E. Original qualitative study; independent technical and rights review pending.
The source trail
Evidence for this page
AI-assisted inspection is not independent engineering review. Source scope and access limitations are disclosed below. Procedural checklists are editorial requirements, not hardware measurements.
Back to first citation ↑C196ASource checked · pending review
Molex documents a 29-circuit SAS/SATA receptacle example with fourteen signal circuits, fifteen power circuits and SFF-8482/SFF-8680 mating references.
Molex · 78717-0002 SAS/SATA receptacle product page ↗Locator: Product detail and mating-interface fields
Access: public page. Identification/reference scope only. V36 does not convert this source into a universal pinout, fabrication drawing, electrical approval or end-to-end compatibility verdict.
S201: full source recordInspect review dependencies → (private workspace)Claim scope: V36 catalogue-expansion identification fact only; not independent technical approval, fabrication data, wiring instruction or end-to-end compatibility proof.. Next review due 2027-01-03.
Back to first citation ↑C196BSource checked · pending review
Molex part 787170002 is a documented SAS/SATA receptacle example in the existing primary-source record; its connector description alone cannot establish whether a given host controller supports SAS.
Molex · 78717-0002 SAS/SATA receptacle product page ↗Locator: Product detail and mating-interface fields
Access: public page. Identification/reference scope only. V36 does not convert this source into a universal pinout, fabrication drawing, electrical approval or end-to-end compatibility verdict.
S201: full source recordInspect review dependencies → (private workspace)Claim scope: V140 / Source-scoped historical or exact-part identity only. No wiring, pinout, universal fit, cable/terminal assembly, device rating, fabrication or publication approval.. Next review due 2027-01-11.
Back to first citation ↑C196CSource checked · pending review
SFF-8482 revision 2.5 distinguishes the device free plug from fixed backplane and fixed cable receptacles; their roles and retention context are not interchangeable labels.
SNIA · SNIA SFF-8482 Unshielded Dual Port Serial Attachment Connector, revision 2.5 ↗Locator: Rev 2.5, 2018-08-31. Document pp.7–8 terminology/contact sets, p.10 Figure 4-1 device free plug, p.17 section 5.3. PDF zero-based pages 8 and 10 visually inspected.
Access: public pdf text. Specification-level study, not a manufacturer specimen or current hardware. No copied specification figures, dimensioned outlines or terminal assignments.
S598: full source recordInspect review dependencies → (private workspace)Claim scope: 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.. Next review due 2027-01-11.
Back to first citation ↑C196DSource checked · pending review
SFF-8482 describes two seven-contact signal sets and a fifteen-contact power set; the second signal set is on the opposite side of the device plug.
SNIA · SNIA SFF-8482 Unshielded Dual Port Serial Attachment Connector, revision 2.5 ↗Locator: Rev 2.5, 2018-08-31. Document pp.7–8 terminology/contact sets, p.10 Figure 4-1 device free plug, p.17 section 5.3. PDF zero-based pages 8 and 10 visually inspected.
Access: public pdf text. Specification-level study, not a manufacturer specimen or current hardware. No copied specification figures, dimensioned outlines or terminal assignments.
S598: full source recordInspect review dependencies → (private workspace)Claim scope: 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.. Next review due 2027-01-11.
Back to first citation ↑C196ESource checked · pending review
SFF-8482 revision 2.5 section 5.3 describes backplane insertion sequencing but states that cable hot plugging is not supported by that interface; a familiar plug outline is not a live-cable permission.
SNIA · SNIA SFF-8482 Unshielded Dual Port Serial Attachment Connector, revision 2.5 ↗Locator: Rev 2.5, 2018-08-31. Document pp.7–8 terminology/contact sets, p.10 Figure 4-1 device free plug, p.17 section 5.3. PDF zero-based pages 8 and 10 visually inspected.
Access: public pdf text. Specification-level study, not a manufacturer specimen or current hardware. No copied specification figures, dimensioned outlines or terminal assignments.
S598: full source recordInspect review dependencies → (private workspace)Claim scope: 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.. Next review due 2027-01-11.
Back to first citation ↑C196FSource checked · pending review
Exact source example 787170002: contacts: 29 loaded:14signal plus15power. construction: Right-angle female SMT connector; PCB locator and retention. recommended pcb mm: 2.36. Molex marks part as not formally published and limited information. Both pitches are listed without per-contact axis mapping; do not assign one to signal or power without drawing. No physical compatibility, pin map or hardware validation is established.
Molex · 78717-0002 SAS/SATA receptacle product page ↗Locator: Product detail and mating-interface fields
Access: public page. Identification/reference scope only. V36 does not convert this source into a universal pinout, fabrication drawing, electrical approval or end-to-end compatibility verdict.
S201: full source recordInspect review dependencies → (private workspace)Claim scope: Exact named component/family technical construction reference from the full current primary document; geometry, ratings and implementation limits do not transfer to other variants.. Next review due 2027-01-20.
Suggest a correction to this field note →