Laipac Protocol ($EAVSYS / $AVRMC / $ECHK)
Laipac on TCP 5048: $EAVSYS identity, $AVRMC fixes with A/R/P, plus $ECHK heartbeat.
On Traxelio
What Laipac trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Laipac
Point this protocol at Traxelio
Point Laipac at Traxelio
-
1
Capture a Laipac fingerprint
Confirm $EAVSYS or $AVRMC with a * XOR checksum. This is not L100 ATL hash-lines on 5112.
-
2
Point Laipac at 5048
Configure only Laipac to TCP 5048. Laipac on 5048 is not L100 on 5112.
-
3
Bind the Laipac unit id
Complete $EAVSYS on 5048 before expecting map points.
-
4
Prove one Laipac fix
Send one $AVRMC with validity A, R, or P on 5048 and verify a map point.
Still offline after GPS lock
Laipac still not landing
- Laipac aimed at the wrong port
Laipac on 5048 is not L100 on 5112.
- Laipac session up, empty map
On 5048, $EAVSYS and $ECHK do not plot. Wait for an $AVRMC whose validity is A, R, or P.
- V-status $AVRMC
V is void. A, R, or P are the valid letters on this dialect.
FAQ
Laipac leftover questions
Does Laipac send Concox 0x7878 frames?
No. Laipac is ASCII. A unit sends $EAVSYS, $AVRMC, or $ECHK with a star XOR checksum.
What does $EAVSYS carry?
The unit id, ICCID, and an optional phone. It binds the row. It does not plot a new coordinate.
Which $AVRMC letters plot a fix?
A, R, and P (any case) are valid. V will not plot. A lowercase letter is answered with $EAVACK.
What is $ECHK?
A heartbeat. The same line is echoed back. It is not a map point.
Can a Laipac unit run SMS setup or a controlled-action flow?
This dialect is positions only. Catalogue devices include S911 locators and StarFinder AIRE. There is no SMS family on this row.