Tuning Wiki
Browse BMW MINI

ENET is the name used for a passive lead between the BMW 16-pin diagnostic socket and an RJ45 plug on a laptop. AsTools, a seller of the lead, describes it as having no chip: the Ethernet contacts in the socket are wired through to the RJ45, and pin 8 is used to enable Ethernet diagnosis. The same listing aims the lead at F, G and I series cars, and at Mini models on an F platform, and says an E-series car has no Ethernet diagnosis on this socket and needs a K and DCAN lead instead. That is a product listing, not a BMW fitment file. A car is settled by its own socket.

The factory workshop interface remains ICOM. ENET is the direct laptop path, the one E-Sys connection notes describe alongside ICOM. The choice of socket and interface is on the BMW diagnostic connections page. The 16-pin shell itself, including the emissions pins that can still be populated beside these contacts, is on the diagnostic ports page.

Which Ethernet this is

The pairs on this socket are the workshop kind. ISO 13400-4 option 1, drawn on the Diagnostics over IP page, puts the receive pair on pins 3 and 11 and the transmit pair on pins 12 and 13, with pin 8 as the activation line. That is four-wire 100BASE-TX, the same physical layer ISO 13400-3 specifies for the wired vehicle interface. It is not the single-pair 100BASE-T1 used between control units inside the car. The Automotive Ethernet page keeps those two cables apart.

A dissecto note on BMW's own transport says that transport was first used in 2008, on 10BASE-T, and that 100BASE-T appeared in 2015. The same note shows a figure it credits to BMW's G05 general vehicle electronics training. The dates are the note's. They are not a quotation of that training document, which was not available for this page. A lead that only joins the two pairs does not say which of those rates a given car's gateway was built for.

The pinout

The python-doipclient primer treats the ENET lead as an apparent case of ISO 13400-4 option 1, and points at a cable-build guide rather than at a BMW diagram. Blafusel publishes the same option for BMW and gives the cross to an RJ45. Read from the car, pins 3 and 11 are the receive pair and pins 12 and 13 are the transmit pair. A PC's RJ45 pin 1 is that PC's transmit-positive. The cross joins the PC's transmit pair to the car's receive pair.

AsTools names pins 3 and 11 as transmit and pins 12 and 13 as receive, without saying which end those words stand at. That wording matches the laptop end of the same cross: the laptop transmits on the pair that the car receives. The two descriptions are the same wiring, named from opposite ends. Wire colour is not a third pinout. Blafusel prints different colours for TIA-568A and TIA-568B, so the contact numbers below are the ones to follow.

OBD contactISO 13400-4 option 1, from the carPublished ENET cross, at the RJ45
3Receive, positivePin 1, the PC's transmit-positive
11Receive, negativePin 2, the PC's transmit-negative
12Transmit, positivePin 3, the PC's receive-positive
13Transmit, negativePin 6, the PC's receive-negative
8ActivationJoined toward pin 16 through the resistor in the cable guides
16Battery positiveThe other side of that resistor

RJ45 pins 4, 5, 7 and 8 are not the 100BASE-TX data pairs, and this table does not assign them. A Team-BHP build of the same four data contacts also joins an unused brown conductor to OBD pins 4 and 5, the ground pins. Blafusel says joining pins 4 and 5, and joining a ground to the RJ45, is unnecessary, because the Ethernet pairs have no ground conductor of their own. The data-pair cross is the part those guides share. The ground join is the part they do not.

The activation line

Pin 8 is the activation contact in option 1, and the dissecto note calls it the Ethernet activation line for this BMW transport as well as for Diagnostics over IP. The tester method on the Diagnostics over IP page is to sense the resistance between pin 8 and pin 5, signal ground, and then apply 5 V. The ENET leads described in print do something else. Blafusel, the Team-BHP build and a motor-talk note on reaching a CIC all place about 510 ohms between pin 8 and pin 16, so the battery contact pulls the activation line up. Dissecto states the same 510 ohm pull-up, and says that without it there is no IP communication. Blafusel pairs 510 ohms with a 12 V socket and prints a different resistor for 24 V. The BMW lead in these notes is the 12 V case. None of these figures is a quotation of the resistance table in ISO 13400-3. That table stays in the standard.

What the laptop is speaking

On the cars these notes describe, the laptop is not assumed to be speaking ISO 13400. Scapy's BMW contribution calls the protocol HSFZ, High-Speed-Fahrzeug-Zugang, and calls ENET the physical interface for it. The dissecto note describes HSFZ as BMW's own transport for diagnostic services, first used in 2008, with logical addressing of control units, usually on TCP port 6801. Scapy binds that decode to TCP port 6801 and to UDP port 6811. The frame those two sources draw is a four-byte length, a two-byte control word, and then, for a diagnostic message, a one-byte source and a one-byte target. The bytes after that are the diagnostic service. Diagnostics over IP, on the other page, uses a different header, two-byte logical addresses, and a routing-activation exchange before the diagnostic message. A Quantex note on HSFZ makes that contrast explicit: routing activation is not part of this BMW transport, and the addresses are one byte rather than two.

The tester address in the Scapy examples, and the default in the Quantex note, is F4 hexadecimal. Quantex's discovery example uses 10 hexadecimal for the gateway. An E-Sys connection note shows the same shape as an example, a gateway listed as diagnostic address 10 at 169.254.1.1 on TCP port 6801. Those are the addresses in the examples. They are not a BMW document assigning every car to one address.

The IP address the laptop ends up with is described in two ways. The E-Sys note says the car does not hand out addresses, so the adapter falls back to a link-local address in 169.254.0.0/16, and that a 192.168 address means the lead has reached a router or an ICOM, or the adapter has a fixed address. AsTools tells the buyer to leave the port on automatic configuration because the vehicle assigns the address. Both sentences are in print. A session that comes up should be read from the address the adapter actually has.

Later cars can also be Diagnostics over IP on this same connector. The dissecto note says the DoIP pinout is usually the same as the HSFZ pinout, with pin 8 still the activation line, and that DoIP uses port 13400. The E-Sys note says the program searches UDP port 6811 and, for newer cars, port 13400. A lead wired for option 1 does not say which of those two transports the gateway will answer.

Sources

  • BMW ENET OBD2 to RJ45 cable. AsTools. Passive lead, pins 3, 11, 12, 13 and 8, and the F, G and I series scope as that seller states it. Accessed 2026-11-13.
  • DoIP and diagnostic adapters. Blafusel. ISO 13400 option 1 for BMW, the RJ45 cross, 510 ohms between pins 8 and 16 on a 12 V socket, and the note that joining the ground pins is unnecessary. Accessed 2026-11-13.
  • Making an ENET OBD cable. Team-BHP. The same four data contacts, numbered at the RJ45, a 510 ohm resistor between pins 8 and 16, and a ground joined to pins 4 and 5. Accessed 2026-11-13.
  • CIC Ethernet connection note. Motor-Talk attachment. Transmit pair to pins 12 and 13, receive pair to pins 3 and 11, and 510 ohms between pins 8 and 16. The note is about reaching a CIC. Accessed 2026-11-13.
  • Automotive Ethernet primer. python-doipclient. ENET described as an apparent ISO 13400-4 option 1 lead, and the tester's pin 8 method. Accessed 2026-11-13.
  • HSFZ. Scapy contribution. The protocol name, ENET as its physical interface, TCP port 6801 and UDP port 6811. Accessed 2026-11-13.
  • HSFZ and DoIP. dissecto. First use in 2008, the activation line, port 6801, the 510 ohm pull-up, and DoIP on the same style of pinout at port 13400. Accessed 2026-11-13.
  • HSFZ and DoIP compared. Quantex. One-byte addresses, TCP 6801, UDP 6811, and no routing activation. Accessed 2026-11-13.
  • E-Sys over ENET or ICOM. Example gateway at 169.254.1.1 port 6801, link-local addressing, and a search on UDP 6811 and port 13400. Accessed 2026-11-13.

Continue the conversation

If this topic interests you, consider joining the following forums. They host material referenced in this article.