MagJack Pin Mapping


I’ll check the terminal mapping against the manufacturer’s drawing, correct the conflicting pins, and verify that the symbol and footprint agree.
Thought for 9 mins 42 sec
Thought for 7 sec
Created 2 tasks.
1/2 Resolve the manufacturer pin map and repair the conflicting part terminals.

Resolve the manufacturer pin map and repair the conflicting part terminals.

Independently verify symbol-to-footprint mapping.

Thought for 16 sec
Awaiting 1 task
"MagJack Pin Mapping" completed.
The manufacturer’s drawing identifies pins 17–20 as LED terminals, not duplicate Ethernet terminals. I’ve given them functional names while preserving the pad numbers and geometry; I’m now checking the complete mapping and symbol.
Thought for 2 mins 42 sec
Thought for 10 sec
Awaiting 1 task
"Ethernet PoE Pin Mapping" completed.
Fixed pins 17–20: they are legitimate LED terminals, now named with their green/orange polarity; verification confirms all 26 terminal-to-pad mappings, with pad geometry preserved. Details are in Terminal Mapping Repair.
Before publishing: the custom symbol’s overlapping shield connection points still need a placed-instance connectivity test; I have not published the part.

Terminal Mapping Repair
Outcome and scope status
Completed: inspect all 26 terminals and electrical pads, research the exact manufacturer drawing, identify pins 17–20, repair their names and descriptions, and read back schematic, layout and symbol. No terminal or pad was deleted. No physical pin number, pad UID, geometry, electrical type or connection was changed. Publishing was not attempted, as instructed.
Pins 17–20 are real LED pins, not duplicates of PoE center taps. LED1 green conducts 19→20 and orange 20→19; LED2 green conducts 17→18 and orange 18→17.
Evidence
Exact manufacturer customer drawing 2250629, title 1X1 4UTG02LET 10G 4POE TAB DOWN SINGLE 4PPOE 120W, sheet 2 circuit and component-side PCB layout. The manufacturer PDF was successfully downloaded with a browser user-agent and rasterized after its image-only contents defeated text extraction. Its sheet 2 visual inspection confirms the complete signal/VC mapping below. The datasheet-query parser could not independently validate the graphical signal numbers; unsupported tool guesses were discarded (including incorrect VC assignments). This is visual drawing verification, not a claim of machine-validated pin-number citations.

circuit

Datasheet identity: ds_aaf4907b04372941f017928fdf961df2753e10a455e87bc2e63ef036de8016f4. Verified LED evidence handle: dsq_818a8f22107c9ddee3e2 / ds1 and ds2. Circuit parser handle dsq_9250657010ace7820549 validates the circuit title only, not its pin map. Local downloaded drawing: /root/work/drawing.pdf on pinmap-review. The stored SnapEDA datasheet URL failed as non-PDF; the exact manufacturer drawing override succeeded. No nearby variant was used.
Full before/after mapping
Pad UID prefixes cross-reference both the initial and final scene-tree reads. All rows have the same physical number before and after. G=green, O=orange, A=anode, K=cathode.

Table


Physical pinBefore nameAfter namePad UID prefixFunction
1TRD1+TRD1+53b83af9PHY pair 1 +
2TRD1-TRD1-b3133284PHY pair 1 -
3TRCT1TRCT149ae14b4PHY-side center tap 1
4TRD2+TRD2+c7a729c8PHY pair 2 +
5TRD2-TRD2-81091428PHY pair 2 -
6TRCT2TRCT2400780edPHY-side center tap 2
7TRD3+TRD3+9bf36b23PHY pair 3 +
8TRD3-TRD3-810b09caPHY pair 3 -
9TRCT3TRCT3c2332fd4PHY-side center tap 3
10TRD4+TRD4+148c42c8PHY pair 4 +
11TRD4-TRD4-208de630PHY pair 4 -
12TRCT4TRCT49793dbc6PHY-side center tap 4
13VC45VC459b7bcf55Cable-side PoE center tap RJ4/5
14VC78VC78118a8395Cable-side PoE center tap RJ7/8
15VC36VC3692ce0f83Cable-side PoE center tap RJ3/6
16VC12VC12a18f9f25Cable-side PoE center tap RJ1/2
1717LED2_G_A_O_K007b97ffLED2 green A / orange K
1818LED2_O_A_G_K67096ac3LED2 orange A / green K
1919LED1_G_A_O_K7d12121aLED1 green A / orange K
2020LED1_O_A_G_K725be2a6LED1 orange A / green K
SH1SHIELDSHIELDf3b0e24aShield solder tab
SH2SHIELDSHIELD65df0c00Shield solder tab
SH3SHIELDSHIELD746d198dShield solder tab
SH4SHIELDSHIELDdaaba7dfShield solder tab
SH5SHIELDSHIELD9306e77fShield solder tab
SH6SHIELDSHIELD0315ca82Shield solder tab
SH1–SH6 are library identifiers for six physical shield tabs, not manufacturer-numbered signal pins. They remain separate terminals. The scene tree also has one unassigned NPTH mounting hole, which is not one of the 26 electrical pads.
Mutations and verification
Commit a9553ec1: renamed four terminal designators as shown above. The footprint labels followed automatically while retaining their UID references. Commit cab1b9aa: added exact LED polarity and not-a-PoE-terminal descriptions to those four terminals. Both edits requested introduced-problem checks; no introduced problems were reported.
Full read-only schematic after edits: 26 terminals; physical pins 1–20 once each plus unique SH1–SH6; zero nets, zero wires, zero no-connects. Full pad scene tree after edits: all 26 electrical pad UID prefixes unchanged, renamed LED pads matched terminal names, positions/sizes/shapes unchanged. LED centers in mm remain 17=(-6.44,-16.46), 18=(-3.90,-16.46), 19=(3.90,-16.46), 20=(6.44,-16.46). Symbol image after edits displays all four new functional LED names. Therefore there was no evidence of duplicated 17–20 terminal identities to remove.
Remaining limitations
Info: the existing default custom SVG asset remains untouched: 2250629-1 2250629-1_0_0 Symbol.svg, UID 3feb57f1-e53e-4542-ae84-4e5f932b135b. Custom SVG uses static graphics and six overlaid shield strokes, and all six shield terminals retain their shared Symbol Pin Position (-57,-214). The generated symbol inspection shows six shield entries separately; actual placed custom-symbol interaction was not tested. Do not treat this repair as validation of shared-shield automatic net propagation or of a host-board PoE power circuit. Connect all intended shield tabs explicitly in a consuming design.
Unattempted: replace/redraw custom SVG, alter shield grouping/geometry, update the stored datasheet link, publish, and host-board electrical qualification. These are not necessary to identify the four reported unknown pins and were left unchanged to preserve the part. The root-property lookup using self was unsupported, so no root Symbol Style change was made. No quality ticket was filed because the reported terminal identities were repairable with supported edits.
  • Outcome and scope status

  • Evidence

  • Full before/after mapping

  • Mutations and verification

  • Remaining limitations