OBD Dongle Protocol

Binary OBD-II plug-in dongle protocol on Traccar TCP 5115, distinct from VT200 trip-bin frames.

Connect your tracker

Enter the tracker IMEI first, then verify your email and continue setup.

Quick answers

Port?

TCP 5115.

Install style?

OBD-II plug-in.

ASCII?

Binary decoder.

Commands?

None on ObdDongleProtocol.

Same as VT200?

No — 5115 vs 5143.

ObdDongle is the Traccar binary path for plug-in OBD-II units on TCP 5115. It is the “cigarette-lighter / OBD port” install story: no loom splicing, power from the diagnostic connector, binary frames into ObdDongleProtocolDecoder.

VT200 is not a synonym

VT200 on 5143 publishes tripStart/hardBrake vocabulary. ObdDongle may coexist in the same shop drawer but must not share the listener.

Setup walkthrough

  1. 1

    Seat the dongle firmly in OBD-II

    Partial seats cause brownouts that look like 'server issues'.

  2. 2

    APN via vendor app/SMS

    Then host:5115.

  3. 3

    Drive around the block

    Many dongles sleep without motion/ACC.

  4. 4

    Capture binary sample

    Hex, not assumed ASCII.

  5. 5

    Note vehicle power behaviour

    Some ports die with ignition — expected.

Reference

Configuration reference

Parameter Value
Port 5115

Telemetry fields

GPS Location Speed Altitude Heading / Direction Street Address GPS Accuracy Ignition Status Odometer / Mileage Battery Level

Common troubleshooting

Dies when ignition off

OBD power switched — hardware trait, not map failure.

VT200 trip fields expected

Wrong protocol expectation — retarget.

Fits mechanically, silent

APN or still on vendor cloud.

Explore More

Other Protocols

VT200

2 devices

Iotm

3 devices

Xexun

12 devices
View All Trackers

FAQ

Frequently Asked Questions

Why separate from generic 'OBD' marketing?

Traccar’s concrete decoder/port pair is ObdDongle/5115 — marketing words are not ports.

UDP?

Stock ObdDongle is TCP.

Connect Obddongle tracker
T
Trax
Online
Say hello to Trax!