E233 · Source-scoped pinout variants

M12 D-coded Ethernet connector engineering reference

D-coded M12 Ethernet family; V40 publishes the four-position/coding boundary only.

Open field note Source trail

Source checked · no independent review claimed · Fabrication approved: no

M12 D-coded Ethernet connector engineering boundary original orientation schematic — Original pinout diagram; read the exact variant and view below. Not to scale.

Contact count

4

M12 D-coded Ethernet interface

Mating boundary

Shape is not the verdict.

M12 D-coded plug ↔ compatible M12 D-coded receptacle

Orientation

How to read this profile

No face-view position locator is published in V40; coding and count do not establish wiring orientation.

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.

Documented examples; not a mating drawing or compatibility approval
Nominal contacts	4S237Source-backed nominal position count: 4.
Positions / cavity span	4 (Claim C233A); 4 (Claim C233B); 4 (Claim C233C); 4 (Phoenix Contact 1561797 / connection 1 (M12 end))S237 · S256 · S500 · S500Source-scoped examples are separate; select the exact variant and measured axis. V39 catalogue-expansion identification fact only; not independent technical approval, fabrication data, wiring instruction, protocol guarantee or end-to-end compatibility proof. V40 engineering-reference fact only; independent human review remains pending. This claim does not approve fabrication, rewiring, substitution, electrical safety, protocol support or end-to-end compatibility. V121 named-product or explicitly scoped manufacturer distinction only; no wiring instruction, independent engineering approval or end-to-end compatibility guarantee. Phoenix Contact 1561797 / connection 1 (M12 end). Named primary-source example only. Identification facts do not certify mating, electrical compatibility, fabrication or powered use.
Connector role	Straight M12 cable plug; other assembly end is RJ45 (Phoenix Contact 1561797 / connection 1 (M12 end))S500Source-scoped examples are separate; select the exact variant and measured axis. Phoenix Contact 1561797 / connection 1 (M12 end). Named primary-source example only. Identification facts do not certify mating, electrical compatibility, fabrication or powered use.
Contact gender / arrangement	male (Phoenix Contact 1561797 / connection 1 (M12 end))S500Source-scoped examples are separate; select the exact variant and measured axis. Phoenix Contact 1561797 / connection 1 (M12 end). Named primary-source example only. Identification facts do not certify mating, electrical compatibility, fabrication or powered use.
Mounting	cable (Phoenix Contact 1561797 / connection 1 (M12 end))S500Source-scoped examples are separate; select the exact variant and measured axis. Phoenix Contact 1561797 / connection 1 (M12 end). Named primary-source example only. Identification facts do not certify mating, electrical compatibility, fabrication or powered use.
Keying / polarization	D coding (Phoenix Contact 1561797 / connection 1 (M12 end))S500Source-scoped examples are separate; select the exact variant and measured axis. Phoenix Contact 1561797 / connection 1 (M12 end). Named primary-source example only. Identification facts do not certify mating, electrical compatibility, fabrication or powered use.
Shell / form	shielded (Phoenix Contact 1561797 / connection 1 (M12 end))S500Source-scoped examples are separate; select the exact variant and measured axis. Phoenix Contact 1561797 / connection 1 (M12 end). Named primary-source example only. Identification facts do not certify mating, electrical compatibility, fabrication or powered use.
Manufacturer	Phoenix Contact (Phoenix Contact 1561797 / connection 1 (M12 end))S500Source-scoped examples are separate; select the exact variant and measured axis. Phoenix Contact 1561797 / connection 1 (M12 end). Named primary-source example only. Identification facts do not certify mating, electrical compatibility, fabrication or powered use.
Exact part / implementation	Phoenix Contact 1561797 / connection 1 (M12 end) (Phoenix Contact 1561797 / connection 1 (M12 end))S500Source-scoped examples are separate; select the exact variant and measured axis. Phoenix Contact 1561797 / connection 1 (M12 end). Named primary-source example only. Identification facts do not certify mating, electrical compatibility, fabrication or powered use.
View convention	Manufacturer caption: male side / M12 pin-assignment view (Phoenix Contact 1561797 / connection 1 (M12 end))S500Source-scoped examples are separate; select the exact variant and measured axis. Phoenix Contact 1561797 / connection 1 (M12 end). Named primary-source example only. Identification facts do not certify mating, electrical compatibility, fabrication or powered use.

Not recorded: Populated contacts, Contact rows, Contact pitch, Dimensions / axis, Coupling / latch, Series, Recorded markings. Unknown fields stay unknown; illustrations supply no measurements or pin assignments.

Recorded variant and source limits

Position/contact count and any example-component pitch do not establish a universal pinout, cable construction or protocol capability.
No fabrication dimensions or face-view pin locator is published unless explicitly stated.
Phoenix Contact 4-contact D-coded Ethernet / PROFINET: Use numbered contacts in Phoenix catalog p.40 male/female insert drawings. The viewing direction is not explicitly labeled mating versus termination; no rear-side mirror is asserted.
Balluff BNI EIP-508-005-Z015-013 female EtherNet/IP port: Numbered contacts of the specified female equipment port. No rear/solder-side mirror or spatial position is inferred.

Report a correction to these facts →

Pins & wiring

Pinout

Choose the exact wiring. Pin numbers follow its stated view; a schematic does not establish physical positions. Check your exact device before wiring.

Dark pinout view

What the status labels mean

Confirmed: Recorded research passes agree within this variant; this is not independent human review or hardware validation.
Single source: Only one underlying document, or one pass, supports this assignment.
Device-specific: Supported for the named equipment or wiring only. Check your device’s manual.
Unverified: Missing or conflicting evidence. Do not wire from this row.
Not connected: The source explicitly says NC, no contact or no pin for this wiring.

Wiring variantPhoenix Contact 4-contact D-coded Ethernet / PROFINET

Phoenix Contact 4-contact D-coded Ethernet / PROFINET

View and evidence limits

Use numbered contacts in Phoenix catalog p.40 male/female insert drawings. The viewing direction is not explicitly labeled mating versus termination; no rear-side mirror is asserted.

P233 M12 D-coded Ethernet — **Agree**: 1 Tx+, 2 Rx+, 3 Tx-, 4 Rx- — A: Phoenix Contact catalog. B: Balluff BNI EIP-508-005-Z015-013 manual. Different manufacturers independently support the numeric Ethernet assignment; neither establishes an explicitly labeled rear/mating-side drawing or arbitrary device capabilities.
MDI-X/crossover, PoE, device support and an explicitly labeled rear/mating-side convention are not established by this map.

Schematic only · physical contact positions unconfirmed. Original drawing · not to scale. Scroll sideways if needed.

Phoenix Contact 4-contact D-coded Ethernet / PROFINET — source-scoped contact map
Pin	Signal	What it does	Status
1	TD+	Signal conductor. Pair, polarity and direction follow this named wiring.	Single source Sources
2	RD+	Signal conductor. Pair, polarity and direction follow this named wiring.	Single source Sources
3	TD-	Signal conductor. Pair, polarity and direction follow this named wiring.	Single source Sources
4	RD-	Signal conductor. Pair, polarity and direction follow this named wiring.	Single source Sources

Sources (1)

S801 · Phoenix Contact · Data connectors — Product overview 2026
2026 edition; document 52004990; no separate revision observed | MNR 1803315/2026-01-15/14; 3012793056 · p.41, Assignment: PROFINET/EtherCAT/Sercos and Assignment: Ethernet, 4-pos. D-coded; p.40 male/female insert diagrams

Balluff BNI EIP-508-005-Z015-013 female EtherNet/IP port

Device-specific wiring. Check your device’s manual before connecting or applying power.

View and evidence limits

Numbered contacts of the specified female equipment port. No rear/solder-side mirror or spatial position is inferred.

P233 M12 D-coded Ethernet — **Agree**: 1 Tx+, 2 Rx+, 3 Tx-, 4 Rx- — A: Phoenix Contact catalog. B: Balluff BNI EIP-508-005-Z015-013 manual. Different manufacturers independently support the numeric Ethernet assignment; neither establishes an explicitly labeled rear/mating-side drawing or arbitrary device capabilities.
The manual identifies a female port and supplies a numbered diagram/table, but does not label that diagram as a mating-face or rear view. Use the contact numbers; spatial handedness is not established here.

Schematic only · physical contact positions unconfirmed. Original drawing · not to scale. Scroll sideways if needed.

Balluff BNI EIP-508-005-Z015-013 female EtherNet/IP port — source-scoped contact map
Pin	Signal	What it does	Status
1	Tx+	Signal conductor. Pair, polarity and direction follow this named wiring.	Device-specific Sources
2	Rx+	Signal conductor. Pair, polarity and direction follow this named wiring.	Device-specific Sources
3	Tx-	Signal conductor. Pair, polarity and direction follow this named wiring.	Device-specific Sources
4	Rx-	Signal conductor. Pair, polarity and direction follow this named wiring.	Device-specific Sources

Sources (1)

S802 · Balluff · BNI EIP-508-005-Z015-013 EtherNet/IP IP67 modules User’s Guide
955066_AC • EN • L22 · Printed p. 6 (PDF p. 7), §3.3 Electrical Connection, Ethernet IP Interface — M12, D-coded, female pin table

Unknowns stay unknown.

Position/contact count and any example-component pitch do not establish a universal pinout, cable construction or protocol capability.
No fabrication dimensions or face-view pin locator is published unless explicitly stated.

Your next step

Use the detail without guessing past its limits.

Read the connector field note Recognition clues and practical checks.Work through a connection Keep exact equipment and cable requirements separate.

Source trail

Claims and sources

C233Bsource checked

Phoenix Contact identifies D-coded M12 Ethernet connectors as a four-position family in its data-connector material.

Phoenix Contact · M12 Ethernet pin-assignment overview ↗
M12 Ethernet connector overview · Engineering-reference scope only. V40 does not turn this source into fabrication approval, electrical safety approval, protocol guarantee, safe substitution or end-to-end compatibility proof.

C808Fsource checked

Phoenix Contact 4-contact D-coded Ethernet / PROFINET: original contact normalization. Statuses distinguish comparison agreement, source limits and named-device wiring.

Phoenix Contact · Data connectors — Product overview 2026 ↗
p. 41, M12 pin assignments and wire colors, Assignment: Ethernet, 8-pos. X-coded Signal table; female drawing p. 40; p. 44, M8 pin assignments and wire colors, Assignment: PROFINET, 4-pos., D-coded Signal table and D-coded male/female drawings; p.41, Assignment: Ethernet, 8-pos. X-coded table; p.40 Female, 8-pos., X-coded diagram; p.41, Assignment: PROFINET/EtherCAT/Sercos and Assignment: Ethernet, 4-pos. D-coded; p.40 male/female insert diagrams; p.44, Assignment: PROFINET, 4-pos. D-coded table and male/female diagrams · Source scope and unresolved evidence are preserved in the engineering variant.

C808Gsource checked

Balluff BNI EIP-508-005-Z015-013 female EtherNet/IP port: original contact normalization. Statuses distinguish comparison agreement, source limits and named-device wiring.

Balluff · BNI EIP-508-005-Z015-013 EtherNet/IP IP67 modules User’s Guide ↗
Printed p. 6 (PDF p. 7), §3.3 Electrical Connection, Ethernet IP Interface — M12, D-coded, female pin table; Printed p. 7 (PDF p. 8), §3 First Steps, Port — M12, A-coded, female pin table and ports 0–7 applicability table · Source scope and unresolved evidence are preserved in the engineering variant.

3 source records support this profile. No independent engineering review or hardware validation is claimed.

Evidence behind this page

Scope first. Source second. Approval separate.

3 linked sources · 3 scoped claims · 0 sources with inspection/access flags.

Page scope: Original V40 engineering boundary schematic; not to scale and not a fabrication, gauging, wiring or mating-face locator drawing.

Assessment 2026-10-22 · earliest scheduled source review 2027-01-03. This is a recorded-date assessment, not a live source check. Page-level independent review is not established by this panel.

Inspect 3 source scopes, access limits and dates

S256 · M12 Ethernet pin-assignment overview

Phoenix Contact · Manufacturer / product-owner domain · inspected 2026-10-05 · due 2027-01-03

Within inspection window

Scoped support: Engineering scope: D-coded M12 is treated as a four-position Ethernet family and X-coded M12 as an eight-position Ethernet family. V40 publishes contact-count and coding boundaries only; no face-view pin locator is inferred.

Not established / limitations: Engineering-reference scope only. V40 does not turn this source into fabrication approval, electrical safety approval, protocol guarantee, safe substitution or end-to-end compatibility proof.

Locator: M12 Ethernet connector overview

S801 · Data connectors — Product overview 2026

Phoenix Contact · Manufacturer / product-owner domain · inspected 2026-10-21 · due 2027-01-19

Within inspection window

Scoped support: Exact named pinout variant only; not capability or compatibility approval.

Not established / limitations: Source scope and unresolved evidence are preserved in the engineering variant.

Locator: p. 41, M12 pin assignments and wire colors, Assignment: Ethernet, 8-pos. X-coded Signal table; female drawing p. 40; p. 44, M8 pin assignments and wire colors, Assignment: PROFINET, 4-pos., D-coded Signal table and D-coded male/female drawings; p.41, Assignment: Ethernet, 8-pos. X-coded table; p.40 Female, 8-pos., X-coded diagram; p.41, Assignment: PROFINET/EtherCAT/Sercos and Assignment: Ethernet, 4-pos. D-coded; p.40 male/female insert diagrams; p.44, Assignment: PROFINET, 4-pos. D-coded table and male/female diagrams

S802 · BNI EIP-508-005-Z015-013 EtherNet/IP IP67 modules User’s Guide

Balluff · Unclassified publisher domain · inspected 2026-10-21 · due 2027-01-19

Within inspection window

Scoped support: Exact named pinout variant only; not capability or compatibility approval.

Not established / limitations: Source scope and unresolved evidence are preserved in the engineering variant.

Locator: Printed p. 6 (PDF p. 7), §3.3 Electrical Connection, Ethernet IP Interface — M12, D-coded, female pin table; Printed p. 7 (PDF p. 8), §3 First Steps, Port — M12, A-coded, female pin table and ports 0–7 applicability table

Trace 3 claims to their source records

C233B · P233

Phoenix Contact identifies D-coded M12 Ethernet connectors as a four-position family in its data-connector material.

Claim scope: V40 engineering-reference fact only; independent human review remains pending. This claim does not approve fabrication, rewiring, substitution, electrical safety, protocol support or end-to-end compatibility.

Source links: S256 · Evidence trail → (private workspace)

C808F · P233

Phoenix Contact 4-contact D-coded Ethernet / PROFINET: original contact normalization. Statuses distinguish comparison agreement, source limits and named-device wiring.

Claim scope: Pinout variant only; see comparison and per-contact status. Not fabrication approval.

Source links: S801 · Evidence trail → (private workspace)

C808G · P233

Balluff BNI EIP-508-005-Z015-013 female EtherNet/IP port: original contact normalization. Statuses distinguish comparison agreement, source limits and named-device wiring.

Claim scope: Pinout variant only; see comparison and per-contact status. Not fabrication approval.

Source links: S802 · Evidence trail → (private workspace)

Prepare this page for review →Read the evidence method →

Recorded evidence only. An inspection date, publisher label, source link or generated packet is not independent technical review, hardware testing, fabrication approval or a compatibility verdict.