Cautela Protocol (line CSV type,imei,date,lat,lon)
Cautela on TCP 5160: type,imei then dd,mm,yy, latitude before longitude, and hhmm with no seconds.
On Traxelio
What Cautela trackers do once they are on Traxelio
Point this protocol at Traxelio
Point Cautela at Traxelio
-
1
Capture a Cautela fingerprint
Confirm a CSV line type,imei,dd,mm,yy,lat,lon,hhmm. Extra columns after hhmm are ignored.
-
2
Point Cautela at 5160
Configure only Cautela to TCP 5160. Cautela on 5160 is not Avema on 5171 or Auro on 5096.
-
3
Do not wait for an ACK
Cautela has no reply byte. A parsed lat/lon pair is enough.
-
4
Prove one Cautela fix
Send one line whose latitude sits before longitude and verify a map point.
Still offline after GPS lock
Cautela still not landing
- Cautela aimed at the wrong port
Cautela on 5160 is not Avema on 5171 or Auro on 5096.
- Map inverted vs Avema docs
Cautela is latitude then longitude. Avema on 5171 is longitude then latitude.
- Date parse failure
Expect three numbers dd,mm,yy. A single yyyymmddhhmmss stamp is Avema, not Cautela.
FAQ
Cautela leftover questions
Does Cautela send an ACK?
No. There is no reply byte. A parsed lat/lon pair is the whole handshake.
What order are Cautela coordinates?
Latitude then longitude. Longitude first is Avema, not Cautela.
Does Cautela need a ***** marker?
No. That marker belongs to Auro. Cautela is bare CSV.
Which CSV field binds a Cautela unit?
The second field, the IMEI. The first field is a type digit and is discarded.
Can a Cautela unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.