Piligrim on HTTP 5059: /bingps 0xF1/0xF2 packed GPS (sats >= 3), or /push.do $GPRMC with A-status; HTTP 200 text OK.
On Traxelio
Hardware that speaks this protocol
Point this protocol at Traxelio
Confirm an HTTP POST to /bingps with type 0xF1 or 0xF2, or to /push.do with a $GPRMC sentence.
Configure only Piligrim to HTTP 5059. Piligrim on 5059 is not Plugin on 5192 or T55 on 5005.
Traxelio answers CONFIG: OK, ADDLOG: OK, INFORM: OK, BINGPS: OK, or PUSH.DO: OK. A 200 is not a map point.
Send one /bingps 0xF1 record with at least 3 satellites, or one /push.do $GPRMC whose status is A, and verify a map point.
Still offline after GPS lock
Piligrim on 5059 is not Plugin on 5192 or T55 on 5005.
/config, /addlog, and /inform never plot. /bingps needs sats >= 3. /push.do needs RMC status A.
BINGPS: OK and PUSH.DO: OK are HTTP 200 text. Check the map for a 0xF1 fix or an A-status RMC, not the OK body.
FAQ
No. Piligrim is HTTP: /bingps with type 0xF1 or 0xF2, or /push.do with $GPRMC.
/bingps with type 0xF1 or 0xF2 and at least 3 satellites, or /push.do with $GPRMC status A.
CONFIG: OK. /addlog answers ADDLOG: OK. /inform answers INFORM: OK. Those paths do not plot.
A plots. V is void and will not plot.
This dialect is positions only. There is no SMS family on this row.