FIELD GUIDESource-led reference

P233 / Network / Connector

M12 D-coded Ethernet connector

M12 D-coded Ethernet uses a 4-position keyed M12 interface in the documented Phoenix Contact implementation.

Also called M12 D-coded M12 D code D-coded M12 Ethernet

An M12 shell does not identify the coding; D-coded and X-coded Ethernet interfaces are different keyed forms.

Look for

Read the coding and compare the internal key/position pattern instead of relying on the M12 threaded shell alone.

Claim inspection dates: 2026-10-05, 2026-10-11, 2026-10-15 · Independent review pending

Image inspection / P233

See the view. Check its scope.

1 registered view for this reference. Different part examples are not automatically mates; all remain not to scale and independently unapproved.

Qualitative oblique exterior study of Phoenix Contact 1561797, M12 D-coded male cable end. Named component role only; not to scale and not a wiring diagram. (private workspace)

P233 / Source-observed physical study

Phoenix Contact 1561797

Phoenix Contact 1561797

Oblique exterior, connection end at left; simplified contact features · Cable plug / cable end

Not to scale. Technical and rights review pending.

Inspect view & provenance (private workspace)

Network notes / Industrial / P233

What does the named D-coded Ethernet cable actually establish?

FIELD NOTES 05

Phoenix Contact 1561797 documents a four-position D-coded M12-to-RJ45 cable at 100 Mbps. Its M12 end and RJ45 end have separate listed protection ratings. That evidence describes the cable, not an arbitrary port, PoE service or working network.

Identify first

Read the part and the device.

Use the complete part number, D coding, position count and opposite end together. The threaded exterior alone is not the coding identifier.

Still unresolved

Keep this requirement open.

Host protocol, power delivery, mating accessory, installation sealing and operation with an unidentified endpoint remain unqualified.

Explicit source exclusion · named example only

Does cable 1561797 have the same protection entry at both ends?

The manufacturer lists IP65/IP67 for the M12 end and IP20 for the RJ45 end.

Boundary. Explicit difference in the named listing; not an evaluation of an installed assembly.

Next check. Read the protection requirement and mating accessory for each exposed junction.

S500 · C018D (private workspace)

Documented support · named example only

Is 1561797 documented as a D-coded M12-to-RJ45 Ethernet cable?

Yes; four-position D coding and 100 Mbps are specified for this named cable.

Boundary. Product capability only, not a measured link or PoE approval.

Next check. Match the exact host, cable ends and intended operating requirements.

S500 · C233C (private workspace)

Before choosing the cable or component

  1. Match the exact equipment socket coding and the cable’s opposite end.
  2. Read the named cable’s speed and separate end-protection entries.
  3. Confirm host-vendor support and any power requirements independently.
Read the evidence and its scope · 3 observations

C233A (private workspace) — Phoenix Contact documents an M12 D-coded Ethernet plug with 4 positions and IEC 61076-2-101 designation.

V39 catalogue-expansion identification fact only; not independent technical approval, fabrication data, wiring instruction, protocol guarantee or end-to-end compatibility proof.

S237

C233C (private workspace) — Phoenix Contact identifies cable 1561797 as a four-position D-coded M12 to RJ45 Ethernet assembly and lists a 100 Mbps transmission speed. This is a named cable specification, not a verdict for all D-coded ports.

V121 named-product or explicitly scoped manufacturer distinction only; no wiring instruction, independent engineering approval or end-to-end compatibility guarantee.

S500

C018D (private workspace) — For Phoenix Contact cable 1561797, the manufacturer lists IP65/IP67 under the M12 end and IP20 under the RJ45 end. The M12 end rating does not establish the same protection for the RJ45 end or a complete installation.

V121 named-product or explicitly scoped manufacturer distinction only; no wiring instruction, independent engineering approval or end-to-end compatibility guarantee.

S500

Source interpretation is not independent engineering review, hardware testing, wiring advice or a public-release approval.

V117 / READER FIELD GUIDE / COPPER NETWORKS

Before you connect or replace

Industrial M12 coding is not optional

Phoenix Contact describes a four-position M12 D-coded Ethernet example; an X-coded example has eight positions. Their coding and connector implementation must follow the exact machine interface.

Three checks and exact source trail ↗

Editorial decision guidance only. A connector identity or nominal pitch does not establish approved mating, safe wiring or a supported device combination.

Inspect the named exterior · Phoenix Contact 1561797
Qualitative oblique exterior study of Phoenix Contact 1561797, M12 D-coded male cable end. Named component role only; not to scale and not a wiring diagram.
Not to scale. Simplified exterior and contact features; no pin numbering, wire assignments, tolerances, mating clearance or manufacturing dimensions. Qualitative exterior; not to scale.

M12 D-coded male cable end; Oblique exterior, connection end at left; simplified contact features. Manufacturer product photograph 244868 inspected 11 October 2026. Original interpretation of the named exterior; not a measured drawing or a copied photograph.

Original source-scoped paraphrase and qualitative vector interpretation; no manufacturer raster artwork republished. Independent technical and rights review remains pending.

S500 · Read the network notes →

The useful distinction

Recognize it. Then verify it.

M12 D-coded Ethernet uses a 4-position keyed M12 interface in the documented Phoenix Contact implementation. [C233A]

Phoenix Contact identifies cable 1561797 as a four-position D-coded M12 to RJ45 Ethernet assembly and lists a 100 Mbps transmission speed. This is a named cable specification, not a verdict for all D-coded ports. [C233C]

HARTING describes D coding as a keyed industrial Ethernet form, distinct from X coding. Its named M12 D-coded four-core cable assembly is listed for 10/100 Mbit/s use; this is not the rating of every M12 device. [C233D]

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 contacts4S237Source-backed nominal position count: 4.
Positions / cavity span4 (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 roleStraight 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 / arrangementmale (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.
Mountingcable (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 / polarizationD 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 / formshielded (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.
ManufacturerPhoenix 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 / implementationPhoenix 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 conventionManufacturer 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 →

Bounded facts, visible unknowns

Specifications and limits

M12 D-coded Ethernet connector facts and limitations
Documented identificationM12 D-coded Ethernet connector; 4 positions in the documented product. [C233A]
Mechanical dimensionsNo independently reviewed mechanical drawing in V39; do not use this page for fabrication, fit testing or tolerance work.
Engineering pinoutSource-checked engineering profile available; independent review pending. Open engineering profile →
Verified device listNot included. Check exact device and accessory documentation.
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.

Before you connect

What to check

  1. Identify the exact connector family and variant from the equipment or cable documentation.
  2. Keep shape, contact count, protocol, electrical rating and device support as separate facts.
  3. Do not force, rewire or adapt a connector from this recognition record; resolve the remaining requirements first.
Trace a supported connection class →

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.

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 variant

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.
M12 D-coded Ethernet connector engineering boundaryUse 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.SCHEMATIC · physical positions unconfirmedNot to scale · check the named wiring and device manual1: TD+ (single_source)12: RD+ (single_source)23: TD- (single_source)34: RD- (single_source)4powergrounddataConfigshieldNCUnknown
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
PinSignalWhat it doesStatus
1TD+Signal conductor. Pair, polarity and direction follow this named wiring.Single source
Sources
2RD+Signal conductor. Pair, polarity and direction follow this named wiring.Single source
Sources
3TD-Signal conductor. Pair, polarity and direction follow this named wiring.Single source
Sources
4RD-Signal conductor. Pair, polarity and direction follow this named wiring.Single source
Sources
Sources (1)

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.
M12 D-coded Ethernet connector engineering boundaryNumbered contacts of the specified female equipment port. No rear/solder-side mirror or spatial position is inferred.SCHEMATIC · physical positions unconfirmedNot to scale · check the named wiring and device manual1: Tx+ (device_specific)12: Rx+ (device_specific)23: Tx- (device_specific)34: Rx- (device_specific)4powergrounddataConfigshieldNCUnknown
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
PinSignalWhat it doesStatus
1Tx+Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
2Rx+Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
3Tx-Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
4Rx-Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
Sources (1)

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.

Your next step

Move from the form to the requirement.

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 ↑
C233ASource checked · pending review

Phoenix Contact documents an M12 D-coded Ethernet plug with 4 positions and IEC 61076-2-101 designation.

Phoenix Contact · M12 D-coded Ethernet cable product ↗

Locator: M12 connection fields and standards
Access: public page. Identification/reference scope only. V39 does not convert this source into a universal pinout, fabrication drawing, electrical approval, protocol guarantee or end-to-end compatibility verdict.

S237: full source recordInspect review dependencies → (private workspace)

Claim scope: V39 catalogue-expansion identification fact only; not independent technical approval, fabrication data, wiring instruction, protocol guarantee or end-to-end compatibility proof.. Next review due 2027-01-03.

Back to first citation ↑
C233CSource checked · pending review

Phoenix Contact identifies cable 1561797 as a four-position D-coded M12 to RJ45 Ethernet assembly and lists a 100 Mbps transmission speed. This is a named cable specification, not a verdict for all D-coded ports.

Phoenix Contact · Phoenix Contact 1561797 — end-specific network and protection scope ↗

Locator: Product description; Interfaces; Connector / Connection 1 and Connection 2; linked product photograph 244868 and male-side drawing 144634
Access: public page. Named 1561797 M12 D-coded to RJ45 cable only; separate end ratings must not be projected onto the complete installation. No raw HTML or manufacturer image archive is represented as retained.

S500: full source recordInspect review dependencies → (private workspace)

Claim scope: V121 named-product or explicitly scoped manufacturer distinction only; no wiring instruction, independent engineering approval or end-to-end compatibility guarantee.. Next review due 2027-01-09.

Back to first citation ↑
C233DSource checked · pending review

HARTING describes D coding as a keyed industrial Ethernet form, distinct from X coding. Its named M12 D-coded four-core cable assembly is listed for 10/100 Mbit/s use; this is not the rating of every M12 device.

HARTING Technology Group · HARTING circular connector coding and application distinctions ↗

Locator: Circular coding: A-coded, D-coded, K-coded, S-coded, X-coded, Y-coded sections
Access: public page. Visible manufacturer facts are source-scoped and may change; confirm the exact component/revision and documented applicability; no independent technical certification is claimed.

S647: full source recordHARTING Technology Group · HARTING M12 D-coded 100 Mbps cable assembly, article 21 34 939 3477 010 ↗

Locator: Product details: identification/version; 4-core D coding; 10/100 Mbps technical characteristics
Access: public page. Visible manufacturer facts are source-scoped and may change; confirm the exact component/revision and documented applicability; no independent technical certification is claimed.

S648: full source recordInspect review dependencies → (private workspace)

Claim scope: V178 Coding-class distinction plus named D cable; not universal host/link-speed guarantee. Original bounded manufacturer paraphrase; publication and technical review pending.. Next review due 2027-01-13.

Suggest a correction to this field note →

Put this field note to work.

Add to discovery trayRecord an unsaved candidate (private workspace)

Compare look-alikes: M12 D-coded versus X-coded Ethernet · M8 D-coded versus M12 D-coded · M12 D-, X- and Y-coded data/hybrid forms

Candidate selection does not confirm the identity or capabilities of your physical item.

NETWORK & INDUSTRIAL / COMPONENT → VARIANT → SERVICE

Name the part. Then the connection.

Compare source-observed component roles, keep exact mating exclusions visible, and distinguish connector identity from equipment service and protection conditions.

Read the network component reference →

Evidence behind this page

Scope first. Source second. Approval separate.

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

Page scope: catalogue_expansion_v39

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 4 source scopes, access limits and dates

S237 · M12 D-coded Ethernet cable product

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

Within inspection window

Scoped support: Documents an M12 D-coded Ethernet plug with 4 positions and IEC 61076-2-101 designation.

Not established / limitations: Identification/reference scope only. V39 does not convert this source into a universal pinout, fabrication drawing, electrical approval, protocol guarantee or end-to-end compatibility verdict.

Locator: M12 connection fields and standards

S500 · Phoenix Contact 1561797 — end-specific network and protection scope

Phoenix Contact · Manufacturer / product-owner domain · inspected 2026-10-11 · due 2027-01-09

Within inspection window

Scoped support: Named 1561797 M12 D-coded to RJ45 cable only; separate end ratings must not be projected onto the complete installation.

Not established / limitations: Named 1561797 M12 D-coded to RJ45 cable only; separate end ratings must not be projected onto the complete installation. No raw HTML or manufacturer image archive is represented as retained.

Locator: Product description; Interfaces; Connector / Connection 1 and Connection 2; linked product photograph 244868 and male-side drawing 144634

S647 · HARTING circular connector coding and application distinctions

HARTING Technology Group · Unclassified publisher domain · inspected 2026-10-15 · due 2027-01-13

Within inspection window

Scoped support: Manufacturer-authored class-level application/coding comparisons; not exact mating, terminal assignments or power ratings for arbitrary parts

Not established / limitations: Visible manufacturer facts are source-scoped and may change; confirm the exact component/revision and documented applicability; no independent technical certification is claimed.

Locator: Circular coding: A-coded, D-coded, K-coded, S-coded, X-coded, Y-coded sections

S648 · HARTING M12 D-coded 100 Mbps cable assembly, article 21 34 939 3477 010

HARTING Technology Group · Unclassified publisher domain · inspected 2026-10-15 · due 2027-01-13

Within inspection window

Scoped support: One named one-meter female-to-female cable assembly; no proof of host support or other cable assemblies

Not established / limitations: Visible manufacturer facts are source-scoped and may change; confirm the exact component/revision and documented applicability; no independent technical certification is claimed.

Locator: Product details: identification/version; 4-core D coding; 10/100 Mbps technical characteristics

Trace 3 claims to their source records

C233A · P233

Phoenix Contact documents an M12 D-coded Ethernet plug with 4 positions and IEC 61076-2-101 designation.

Claim scope: V39 catalogue-expansion identification fact only; not independent technical approval, fabrication data, wiring instruction, protocol guarantee or end-to-end compatibility proof.

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

C233C · P233

Phoenix Contact identifies cable 1561797 as a four-position D-coded M12 to RJ45 Ethernet assembly and lists a 100 Mbps transmission speed. This is a named cable specification, not a verdict for all D-coded ports.

Claim scope: V121 named-product or explicitly scoped manufacturer distinction only; no wiring instruction, independent engineering approval or end-to-end compatibility guarantee.

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

C233D · P233

HARTING describes D coding as a keyed industrial Ethernet form, distinct from X coding. Its named M12 D-coded four-core cable assembly is listed for 10/100 Mbit/s use; this is not the rating of every M12 device.

Claim scope: V178 Coding-class distinction plus named D cable; not universal host/link-speed guarantee. Original bounded manufacturer paraphrase; publication and technical review pending.

Source links: S647 · S648 · Evidence trail → (private workspace)

Prepare this page for review → (private workspace)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.

Industrial coding field check · M12 D · data

Is every M12 Ethernet cable the same?

Short answer No. The D-coded M12 form is distinct from X-coded M12, even when both use an M12 threaded family.

Verify next

Read the coding of both documented parts, cable direction, and exact device port speed before ordering.

Not yet established

The D-coded class does not establish compatibility with any specific X-coded, A-coded, Y-coded or power port.

Show source-checked observations (not independently approved)

Symbolic reference, not connector gauging, manufacturing dimensions, wiring, approved mating, hardware test or publication approval.

Compare all eight industrial coding questions →