G1 RUS Protocol (masked binary regular/mixed)
G1 RUS on TCP 5244: binary header and version, type regular or mixed, 8-byte IMEI, Y2K clock, and a dataMask location block.
On Traxelio
What G1RUS trackers do once they are on Traxelio
Point this protocol at Traxelio
Point G1RUS at Traxelio
-
1
Capture a G1 RUS fingerprint
Confirm a binary record with header, version, type, and an 8-byte IMEI. Reject 0x7E as Flexible Report.
-
2
Point G1 RUS at 5244
Configure only G1 RUS to TCP 5244. G1 RUS on 5244 is not Flexible Report on 5227 or GL601 on 5257.
-
3
Do not wait for an ACK
G1 RUS has no reply byte. A parsed regular record with lat/lon is enough.
-
4
Prove one G1 RUS fix
Send one regular record whose location mask carries filled lat/lon on 5244 and verify a map point.
Still offline after GPS lock
G1RUS still not landing
- G1 RUS aimed at the wrong port
G1 RUS on 5244 is not Flexible Report 0x7E on 5227 or GL601 TLV on 5257.
- Session up, empty map
The location mask must carry lat/lon and validity bits 5-6 equal 2. Power-only or heartbeat records will not plot.
- No ACK, assumed dead
This dialect has no reply byte. Check the map, not the socket for an ACK.
FAQ
G1RUS leftover questions
Does G1 RUS send Concox 0x7878 frames?
No. G1 RUS is masked binary with type regular or mixed. Concox families use 0x7878 binary login.
Which G1 RUS types plot a fix?
Regular (type 1) and mixed (type 4) batches of regular records. Heartbeat, SMS-forward, and serial do not plot.
Does G1 RUS send an ACK?
No. There is no reply byte. A parsed regular record with lat/lon is enough to plot.
What does a G1 RUS location mask add?
Lat/lon over 1e6, optional speed, course, altitude, HDOP, and VDOP. Validity bits 5-6 must equal 2.
Can a G1 RUS unit run SMS setup or a controlled-action flow?
This dialect is positions only. GoSafe G1RUS is listed. There is no SMS family on this row.