Connection

Hanterill reaches the vehicle with ISO 13400 Diagnostics over IP (DoIP). Physically, that is ordinary Ethernet from your computer to a passive cable in the OBD-II port.

The cable

A passive ENET cable wires specific OBD-II pins to a standard RJ45 plug. It contains no electronics. It is not an ELM327, not a J2534 interface, and not a Bluetooth adapter. The cable itself needs no driver.

Typical chain:

OBD-II connector
  -> ENET cable
  -> RJ45
  -> USB-C Ethernet adapter
  -> Laptop

Network settings

DoIP uses link-local addressing. In most cases the vehicle and adapter negotiate automatically and no manual IP configuration is needed. If your operating system holds the interface waiting for DHCP, set the adapter to link-local / automatic private addressing.

Hanterill discovers the vehicle with a UDP vehicle identification request on port 13400, then opens a TCP connection on the same port and performs routing activation before any diagnostic request.

If the vehicle does not appear

• Confirm the vehicle is at ignition-on.
• Confirm the RJ45 is in an Ethernet port, not a USB-only port.
• Disable any VPN or firewall rule that blocks UDP 13400.
• Try a different Ethernet adapter. Some USB adapters drop link-local traffic.
• Check that no other diagnostic tool holds the DoIP socket.

Wireless

Some vehicles expose DoIP over their own Wi-Fi access point. Where that is available and Hanterill supports it, the same discovery and routing steps apply over the wireless interface.