M2M Protocol (0x0b-offset binary IMEI)
M2M on TCP 5054: 23-byte frames, 0x20 offset except 0x0b, first frame packs the IMEI.
On Traxelio
What M2M trackers do once they are on Traxelio
Point this protocol at Traxelio
Point M2M at Traxelio
-
1
Capture an M2M fingerprint
Confirm a 23-byte binary frame whose bytes subtract 0x20 except a literal 0x0b.
-
2
Point M2M at 5054
Configure only M2M to TCP 5054. M2M on 5054 is not MTX on 5083 or MXT on 5087.
-
3
Complete the M2M IMEI bind
Finish the first-frame packed IMEI on 5054 before expecting map points.
-
4
Prove one M2M fix
Send a later 23-byte record with satellites greater than 0 on 5054 and verify a map point.
Still offline after GPS lock
M2M still not landing
- M2M aimed at the wrong port
M2M on 5054 is not MTX on 5083 or MXT on 5087.
- M2M session up, empty map
On 5054, the first frame only binds the IMEI. Wait for a later 23-byte record whose satellite count is greater than 0.
- Aimed an M2M-Mini at 6054
6054 is another host's number. Traxelio maps this dialect on 5054.
FAQ
M2M leftover questions
Does M2M send Concox 0x7878 frames?
No. M2M uses a fixed 23-byte binary record. Bytes subtract 0x20 except a literal 0x0b. Concox families use 0x7878 login.
How does an M2M unit present its IMEI?
The first 23-byte record carries eight packed-decimal bytes. Those expand to sixteen digits. The leading digit is dropped to leave a 15-digit IMEI.
Why does an M2M session bind without a map fix?
The first record only binds the IMEI. A map point needs a later record whose satellite count is greater than 0. A zero satellite count is cell-only.
What do the 0x40 and 0x80 bits mean on M2M?
After latitude, 0x80 flips longitude west and 0x40 flips latitude south. The remaining low bits start the longitude degrees.
Can an M2M unit run SMS setup or a controlled-action flow?
This dialect is positions only. The M2M-Mini is the listed device. There is no SMS family on this row.