3 devices 3 brands

DSF22 Protocol (batched binary TCP/UDP)

DSF22 binary on Traccar 5236 TCP+UDP: short LE id, multi-fix batches, fuel, single-byte 0x01 ack.

See port and setup first

Connect your tracker

Check this IMEI here, then continue on Connect to verify your email and finish setup.

Browse 3 supported devices

Quick answers

Stock Traccar port?

5236 TCP and UDP.

Ack shape?

Single byte 0x01.

Batching?

Unsigned count then repeated position records.

DSF22 on Traccar port 5236 registers TCP and UDP with Dsf22FrameDecoder. Dsf22ProtocolDecoder skips a 2-byte header, binds on a 16-bit LE id, reads a count, then loops positions: lat/lon ×1e7, unix time, kph→knots speed, fuel/1000, status bits (ignition, in1, out1, jamming). Server replies with a lone 0x01 byte.

Batch binary + fuel

Not Dualcam’s media state machine on 5232 and not Continental’s MSG_STATUS on 5161 — DSF22 identity is short-id batched fixes + 0x01 ack on 5236.

Catalogue stance

Stock Traccar reference. positions_only.

Setup walkthrough

  1. 1

    Match TCP vs UDP to firmware

    Wrong transport on 5236 looks like total silence.

  2. 2

    Register the short numeric id

    Bind uses 16-bit LE id, not a 15-digit IMEI string.

  3. 3

    Capture a multi-fix batch

    Count byte >1 proves batching; fuel short follows speed.

  4. 4

    Confirm 0x01 leave path

    Missing ack causes replay storms on UDP especially.

Setup

Public setup commands

Use these rows only after confirming the tracker password and SIM settings. Command families can differ between brands even when they use the same protocol.

Setup guidance

Connection supported

gps.traxelio.com:5236 3 example models
DSF10 DSF21 DSF22

Traxelio can receive this model, but public SMS setup depends on SIM or model settings.

Reference

Configuration reference

Parameter Value
Port 5236

Telemetry fields

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

All Models

All DSF22 Devices (3)

Start with the strongest matches, then use pagination or brand pages for the full compatibility list.

DSF10

DSF10

DSF21

DSF21

DSF22

DSF22

Compatible Brands

Brands Using DSF22 Protocol

DSF10

1 device

DSF21

1 device

DSF22

1 device

Common troubleshooting

IMEI-style id never binds

Use the 16-bit device id the frame carries — not a fabricated 15-digit IMEI.

Sent to Dualcam 5232

Camera MSG_INIT/DATA will not parse DSF22 batches — move to 5236.

Jamming alarm noise

Status bit 6 maps ALARM_JAMMING in the open decoder; verify RF before discarding the unit.

Explore More

Other Protocols

Dualcam

1 device

Continental

1 device

Fleetguide

1 device
View All Trackers

FAQ

Frequently Asked Questions

Does DSF22 carry camera files?

No. Camera/media messaging is Dualcam on 5232.

Support tier?

positions_only.

Connect DSF22 tracker
T
Trax
Online
Say hello to Trax!