Castel Protocol (@@ / 0x4040 SC+CC binary)
Castel on TCP and UDP 5086: @@ / 0x4040, 20-byte id, SC 0x4001 GPS or CC 0x4206 heartbeat, CRC16-X25.
On Traxelio
What Castel trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Castel
Who ships hardware on this wire
Brands using Castel
Point this protocol at Traxelio
Point Castel at Traxelio
-
1
Capture a Castel fingerprint
Confirm a frame that opens @@ (0x4040), not AVL301 L/H/$ and not Cellocator MCGP.
-
2
Point Castel at 5086
Configure only Castel to TCP or UDP 5086. Castel on 5086 is not AVL301 on 5085 or Cellocator on 5033.
-
3
Expect the SC or CC reply
SC login is answered 0x9001. CC login is answered 0x8001. Both close with CRC16-X25 and CR LF.
-
4
Prove one Castel fix
Send one GPS structure whose flags 0x0C bits are set and verify a map point.
Still offline after GPS lock
Castel still not landing
- Castel aimed at the wrong port
Castel on 5086 is not AVL301 on 5085 or Cellocator on 5033.
- No reply, assumed dead
SC login expects 0x9001. CC login expects 0x8001. Check the map after CRC16-X25 CR LF, not a Concox 0x7878 ack.
These symptoms are answered outside this section:
FAQ
Castel leftover questions
Does Castel send Concox 0x7878 frames?
No. Castel opens with @@ then a version byte and a 20-byte id. Concox families use 0x7878 binary login.
Which Castel flags bits plot a fix?
Bits 0x0C of the flags byte. When both are off, the row will not plot.
Does Castel send a reply?
Yes. SC login gets 0x9001. SC heartbeat gets 0x9003. SC alarm gets 0xC007. CC login gets 0x8001. CC heartbeat gets 0x8206. Replies close with CRC16-X25 then CR LF.
Where is the Castel unit id?
Twenty ASCII bytes after the version byte on a @@ frame. MPIP skips the version byte and places the id after the length.
Can a Castel unit run SMS setup or a controlled-action flow?
This dialect is positions only. The Castel SMS family can point the unit at the host. A controlled-action flow is not delivered here.