14 devices 5 brands

Castel Protocol (@@ / 0x4040 SC+CC binary)

Castel dual TCP/UDP binary on Traccar 5086: @@ / 0x4040 header, SC OBD types 0x1001/0x4001… and CC branch.

Connect your tracker

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

Quick answers

Stock Traccar port?

5086 TCP and UDP.

Header?

Little-endian 0x4040 (@@).

GPS SC type?

0x4001 among a large OBD/alarm type set.

Castel on Traccar port 5086 listens on TCP and UDP. Frames are little-endian length-based; header short 0x4040 (@@) leads into versioned SC or CC bodies. SC covers login 0x1001, heartbeat 0x1003, GPS 0x4001, PID/OBD 0x4002/0x4005, alarms 0x4007, fuel 0x400E, comprehensive 0x401F. Engine stop/resume exist in Traccar’s encoder — Traxelio still marks positions_only.

SC/CC binary on 5086

AVL301 on neighboring 5085 is L/H/$. Cellocator on 5033 uses MCGP. Castel’s @@/0x4040 plus OBD-heavy SC map is the differentiator.

Catalogue stance

Stock Traccar reference. No Traxelio full-support or immobilizer delivery claim.

Setup walkthrough

  1. 1

    Open 5086 TCP or UDP to match firmware

    Castel registers both; mismatch drops packets.

  2. 2

    Capture @@ / 0x4040

    Wrong magic means you are on AVL301 or Cellocator instead.

  3. 3

    Start with login 0x1001 / GPS 0x4001

    OBD PID frames are secondary after a live GPS type.

  4. 4

    Keep immobilizer expectations offline

    Traccar encoder hooks ≠ Traxelio command product.

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:5086 4 example models

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

Reference

Configuration reference

Parameter Value
Port 5086

Telemetry fields

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

Common troubleshooting

Aimed at 5085 AVL301

L/H/$ will not parse Castel — use 5086.

OBD without GPS

PID types enrich telemetry; maps still need 0x4001 (or comprehensive) GPS content.

Assuming engine stop works here

Catalogue remains positions_only on Traxelio.

FAQ

Frequently Asked Questions

UDP supported in stock Traccar?

Yes — CastelProtocol adds both TCP and UDP TrackerServers on 5086.

Support tier?

positions_only.

T
Trax
Online
Say hello to Trax!