1 device 1 brand

Appello Protocol (FOLLOWIT, CSV)

Appello on TCP 5109: FOLLOWIT, then IMEI, yymmddhhmmss or UTCTIME, signed lat/lon, and an F or L flag.

Positions go to this server

gps.traxelio.com:5109 TCP
I already have a tracker

Connect your tracker

Enter your tracker IMEI to see whether Traxelio recognizes the model before you start setup.

Hardware that speaks this protocol

Devices that speak Appello

Point this protocol at Traxelio

Point Appello at Traxelio

  1. 1

    Capture an Appello fingerprint

    Confirm FOLLOWIT, plus IMEI. Reject a $$ event CSV as Aquila on 5089.

  2. 2

    Point Appello at 5109

    Configure only Appello to TCP 5109. Appello on 5109 is not Aquila on 5089 or Dway on 5150.

  3. 3

    Do not wait for an ACK

    Appello has no reply byte. A parsed F-letter line is enough.

  4. 4

    Prove one Appello fix

    Send one FOLLOWIT, line whose GPS letter is F on 5109 and verify a map point.

Still offline after GPS lock

Appello still not landing

Appello aimed at the wrong port

Appello on 5109 is not Aquila on 5089 or Dway on 5150.

Session up, empty map

Letter F plots. Letter L binds the IMEI and will not plot.

No ACK, assumed dead

This dialect has no reply byte. Check the map, not the socket for an ACK.

FAQ

Appello leftover questions

Does Appello send Aquila $$ event CSV?

No. Appello opens with FOLLOWIT, then the IMEI. Aquila opens with $$ and an event code.

Which letter plots an Appello fix?

F plots. L is lost and will not plot.

What does UTCTIME mean on an Appello line?

The unit omitted a new clock. Traxelio keeps the last known stamp and still reads lat/lon.

Where is the Appello unit id?

Immediately after FOLLOWIT, as the IMEI, before the stamp or UTCTIME.

Can an Appello unit run SMS setup or a controlled-action flow?

This dialect is positions only. One catalogue device is listed (Appello 4P). There is no SMS family on this row.

T
Trax
Online
Say hello to Trax!