Homtecs Protocol (id_R mac CSV)
Homtecs on UDP 5104: id_R plus 8-hex MAC, yymmdd, hhmmss, sats, N/S E/W lat/lon, fix digit greater than 0 plots.
On Traxelio
What Homtecs trackers do once they are on Traxelio
Point this protocol at Traxelio
Point Homtecs at Traxelio
-
1
Capture a Homtecs fingerprint
Confirm ASCII that places _R after the unit id and then eight hex digits, not $GPRS or *ID.
-
2
Point Homtecs at 5104
Configure only Homtecs to UDP 5104. Homtecs on 5104 is not Haicom on 5063 or Idpl on 5110.
-
3
Do not wait for an ACK
Homtecs has no reply byte. A parsed CSV is enough.
-
4
Prove one Homtecs fix
Send one line whose fix digit is greater than 0 on 5104 and verify a map point.
Still offline after GPS lock
Homtecs still not landing
- Homtecs aimed at the wrong port
Homtecs on 5104 is not Haicom $GPRS on 5063 or Idpl *ID on 5110.
- Session up, empty map
The fix digit must be greater than 0. Digit 0 binds and will not plot.
- No ACK, assumed dead
This dialect has no reply byte. Check the map, not the socket for an ACK.
FAQ
Homtecs leftover questions
Does Homtecs send Concox 0x7878 frames?
No. Homtecs is ASCII that places _R after the unit id, then eight hex digits and NMEA lat/lon. Concox families use 0x7878 binary login.
Which Homtecs fix digit plots?
Any digit greater than 0 plots. Digit 0 binds and will not plot.
Does Homtecs send an ACK?
No. There is no reply byte. A parsed id_R line is the whole handshake.
Where is the Homtecs unit id?
Before _R. A second bind key is that same id plus _R plus the eight hex digits.
Can a Homtecs unit run SMS setup or a controlled-action flow?
This dialect is positions only. Homtecs H20 is the listed device. There is no SMS family on this row.