B2316 Protocol (UDP JSON imei + data[] array)
B2316 on UDP 5230: JSON root imei plus data[] items with tm epoch and gp lon,lat.
On Traxelio
What B2316 trackers do once they are on Traxelio
Point this protocol at Traxelio
Point B2316 at Traxelio
-
1
Use UDP, not TCP
B2316 on this listen is UDP only.
-
2
Aim at 5230
Host plus UDP 5230. Confirm the firewall allows datagrams.
-
3
Send JSON with imei and data
Root imei alone creates no map point. Fill data with tm and gp.
-
4
Keep gp lon then lat
A reversed pair mirrors the track. gp is longitude first.
Still offline after GPS lock
B2316 still not landing
- TCP connection attempts
B2316 on this listen is UDP. Switch transport.
- Posted Austin NB CSV to 5230
Wrong neighbor. Semicolon CSV belongs on Austin NB 5158.
- gp parsed lat then lon
Split gp as longitude then latitude. Reversing mirrors the track.
FAQ
B2316 leftover questions
Does B2316 send Concox 0x7878 frames?
No. B2316 is a JSON object with root imei and a data array. Concox families use 0x7878 binary login.
Which way does the gp field run?
gp is a lon,lat string. Longitude comes first. A lat-first parse mirrors the track.
Why does a B2316 datagram bind without a map fix?
Root imei alone is not a fix. A map point needs a data item with gp, or a later item that can reuse a last known coordinate.
What do B2316 battery buckets mean?
ba values 0 through 4 map to 10, 30, 60, 80, and 100 percent. They are not millivolts.
Can a B2316 unit run SMS setup or a controlled-action flow?
This dialect is positions only. The Mictrack B2316 is the listed device. There is no SMS family on this row.